Fries, Steffen wrote: > > - 1 Introduction (page 3) > > maybe it is worth mentioning in the introduction already that this ID > only considers "call by reference" for the assertions and does not provide > means for sending the assertion directly.
Sure, we can do that. Though note that perhaps in the longer term it'll depend on the resolution to the issue of whether the spec remains strictly call-by-reference or evolves to include call-by-value. i.e. see..
[Sip] wrt SIP Saml Review by Jiri Kuthan - "missing scenarios" http://www1.ietf.org/mail-archive/web/sip/current/msg19793.html > - 3.1 SAML assertions (page 7) > "Explaining how the assertion was made, for example. " Sounds like an > example would follow, > which does not. I suggest removing "for example" > > - 4 Specification scope (page 9), in the discussion paragraph: > "However, The ..." -> should be "However, the ..." > "participating entites ..." -> "participating entities ..." > > - 5. Emplying SAML in SIP (page 11) > "seperatey" -> "separately" > > - 6.1.2 Profile Overview (page 14) > "Although this profile is overview is cast in terms of a SIP INVITE > ..." There is something wrong with this sentence > > - 6.1.3.2 (page 19) > procedes -> proceeds I've entered all these editorial comments into the sip-saml tracker (under "bug").. http://www.tschofenig.com:8080/saml-sip/[EMAIL PROTECTED]&@group=priority&@filter=status&@columns=id,activity,title,creator,assignedto,status&status=-1,1,2,3,4,5,6,7 thanks for your review, =JeffH _______________________________________________ Sip mailing list https://www1.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
