Re: FW: I-D Action:draft-kaplan-sip-asserter-identity-01.txt

Hadriel Kaplan <[email protected]>
Newsgroups gmane.ietf.sip
Message-ID <E6C2E8958BA59A4FB960963D475F7AC314E8BE9C73@mail>
Hey John,
Thanks for reviewing the draft!  I was thinking that basically the asserter should decide what it wants to sign, but I think you're right that a default list would be good. 

-hadriel

> -----Original Message-----
> From: Elwell, John [mailto:[email protected]]
> Sent: Tuesday, March 10, 2009 5:29 AM
> 
> An interesting draft, perhaps useful in two ways: first in the way you
> intend (as asserter ID in closed domains or federations of closed
> domains), but secondly some aspects might be relevant for inclusion in
> an eventual solution to the SIP-Identity problem, notably the means of
> selecting particular body parts and SDP attributes to sign.
> 
> On that particular issue, I am not sure whether the asserter is in a
> position to decide on a request-by-request basis which body parts and
> SDP attributes to sign, since it cannot know what downstream entities
> are likely to need to do to those fields, so we may need some guidance
> (e.g., a default list of things to sign).

_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [email protected] for questions on current sip
Use [email protected] for new developments on the application of sip
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.