[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
CAP issue: Fallback/fanout to iTIP
- "Fallback/fanout to iTIP" concerns:
If a CAP request must get turned into iTIP then some extra coding must
(ie: rewriting the proper ATTENDEE and ORGANIZER values from cap://...
mailto:.. ). Since this may happen anywhere down stream from the
originating CS, it is not guaranteed that the mapping/rewrites are
or correct; they are 'assumed' to be usable ("or the request is
back."). Unfortunately correctness is only positively done at the
point and not @ Yahoo on the way to Lotus. There are also cases like
or encrypted data that would prevent this from being either doable or
the risk of voiding the signature. (from Bruce)
I think that, in general, it is too difficult of a problem for us to
provide instructions in CAP as to how a given implementation can
guarantee a correct mapping between an email address (a mailto: calid)
and a CAP calid. That responsibility lies at some point between a
messaging server and a calendar server and will likeley involve a
directory server. I think we should explicitly not attempt solve that
problem in CAP and leave this to implementations.
Thoughts on this?
title:Judge, Jury, and Executioner