Re: CAP & Latency

[Bruce_Kahn@xxxxxxxx]

Paul replied in part with:
>Existing examples of this include large corporations which service their internet
>mail through a large gateway mail machine and don't want the outside world to
>know the names of internal machines and consider it a service so that
>others don't have to keep track if someone moves machines within a company.
>
>They also can provide the mapping from "droyer" to the more readable "Doug.Royer"
>on the outgoing address.

There is one slight difference I think you may have overlooked.  They rewrite meta information NOT the acutal data.  If they rewrote the actual data it would blow signed emails and be totally impossible in the encrypted data case.

In CAP and iCalendar we do not have the concept of unencapsulated data;  all iCalendar/CAP messages are 'self contained'.  There are good reasons for this (ie: Clipboard copy/paste).  There are also drawbacks to this (the CS cannot make simple rewrites w/o mucking w/the data itself).

Another subtle difference is that the rewritting server belongs to the same 'domain' that Doug does.  You wont find, say, myriad.com rewriting Dougs software.com address!  In Dougs diagram, CS-1 is doing the rewrite for CUA-1.  However in the CAP case, it could be CS-2 (or an intermediate CS-1.5) that does the CAP->iTIP conversion and and such CANNOT do a rewrite safely!  (Assuming CS-1 didnt do a rewrite already that is).

All this digresses though from the base issue I originally raised: The 'fallback' from CAP to iTIP case has some handwaiving that needs to be cleared up.  As Doug already noted, there are still areas that need fleshing out still.  This is one of them.

Bruce
===========================================================================
Bruce Kahn                                INet: Bruce_Kahn@iris.com
Iris Associates                          Phone: 978.392.5335
Westford, MA, USA 01886                    FAX: and nothing but the FAX...
Standard disclaimers apply, even where prohibited by law...

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature