I'm splitting this thread, to make it easier for my feeble brain to follow
This thread is, do we specify crypto in geopriv?
> >>> One of the things we also agreed on (almost too readily it seems)
> >>> is that the latter is NOT going to be specified by geopriv.
> >>> We probably will offer guidelines on appropriate choices, but
> >>> because we agreed that transport was not on the table, precise
> >>> crypto is not on the table. I think this is a very helpful thing
> >>> if the entire group agrees.
> >> i suspect that one cares about whether the box is locked or not,
> >> and whether the checks in it are signed, irrespective whether the
> >> box is carried by car or by plane.
> > If the protocol the object is used with provides "adequate"
> > crypto, then the object should not provide any additional crypto.
>
> i suspect that the trust association(s) of the transport will not
> be the same as the trust association(s) of the material being
> transported. i am told that this little difference often raises
> its head.
>
>
SIP needs to provide location information for a number of
useful applications.
SIP Provides a way to authenticate, and provide confidentiality
for SIP messages between two end user devices (UAs).
We propose to place the location object in the SIP message.
We assert that the mechanisms in SIP (the new version recently
approved by the IESG) are sufficient for the purpose.
Brian
Received on Wed Mar 20 11:39:15 2002
This archive was generated by hypermail 2.1.8 : Thu Jan 22 2004 - 12:32:22 EST