1) I am not convinced this document does updated RFC 4412. RFC 4412 creates the namespace. This document merely adds new items to the IANA registry created by that document. The document header should be modified accordingly, and the following text in the abstract also corrected:
This document intends to update RFC 4412, as a Proposed Standard document if published by the RFC-Editor. 2) I believe the abstract could usefully summarise the new namespaces that are created (in the same way as most drafts that define new headers identify them in the abstract). 3) In section 3, I do not see the need to include the following text in the document, as it is already in RFC 4412, for which all the requirements apply, not just this one. As stated in Section 9 of RFC 4412 [RFC4412], an IANA registered namespace SHOULD NOT change the number, and MUST NOT change the relative priority order, of its assigned priority-values. 4) NIT. Tag all mentions of RFC4412 as references. Regards Keith _______________________________________________ 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
