Using the following RFC 6665 section B.27 snippet to help clarify section 5.4.2, it sounds like an event packages that wants to include Event parameters containing Call-ID and To/From tags will need to introduce different names to reflect the same thing.
RFC 6665 section B.27: "Clarified scope of "Event" header field parameters. In RFC 3265, the scope is ambiguous, which causes problems with the registry in RFC 3968. The new text ensures that "Event" header field parameters are unique across all event packages." > -----Original Message----- > From: Brett Tate [mailto:br...@broadsoft.com] > Sent: Wednesday, June 17, 2015 3:30 PM > To: 'sip-implementors@lists.cs.columbia.edu' > Subject: RFC 6665: Event header parameters > > Hi, > > What does RFC 6665 section 5.4.2 mean concerning "MUST NOT be reused > with any other event package". For instance, RFC 4235 registered > call-id, to-tag, and from-tag; can those parameters be used by other > event packages? > > Thanks, > Brett > > ----- > > RFC 6665 section 5.4.2: > > "Any "Event" header field parameters defined by an event package > MUST be registered in the "Header Field Parameters and Parameter > Values" registry defined by [RFC3968]. An "Event" header field > parameter, once registered in conjunction with an event package, > MUST NOT be reused with any other event package." _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
