draft-kaplan-sip-secure-call-id-00
"DRAGE, Keith (Keith)" <[email protected]>
| Newsgroups | gmane.ietf.sip |
|---|---|
| Message-ID | <28B7C3AA2A7ABA4A841F11217ABE78D6757BE70A@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com> |
On: http://tools.ietf.org/id/draft-kaplan-sip-secure-call-id-00.txt I believe the essential question at the moment is: "Do people see this as something that solves problems or not?". However can I point out the process implications. The draft as currently provided updates RFC 3261 in my view. That essentially makes it SIP-CORE if the WG / charter changes go ahead. The draft appears to claim that it corrects a problem in RFC 3261? Is it an essential correction? If so it should possible form part of our essential corrections process, rather than ultimately generating a second draft. Doing so would certainly make some of the documentation implications in the slides as currently stated easier. So, is it an essential correction or a SIP extension? I would claim there are no other standards track SIP documents. regards Keith _______________________________________________ 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