I agree with John here. I would include an informative reference to RFC 3427 indicating that any draft that requires option tags for a package would need to have the status required for option tag registration.
regards Keith > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Elwell, John > Sent: Thursday, November 20, 2008 1:16 AM > To: Eric Burger; SIP List > Subject: Re: [Sip] INFO Framework: Tags > > Eric, > > If an individual package requires an option tag, that option > tag could be defined in the RFC that defines the package, > which would need to be standards track. I don't think we need > to say anything about this. > > Similar situation for media tags, except that RFC would not > need to be standards track. > > John > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of > > Eric Burger > > Sent: 20 November 2008 00:48 > > To: SIP List > > Subject: [Sip] INFO Framework: Tags > > > > Do we want to specify media tags to indicate package support? > > > > Do we want to specify SIP option tags to require Info > Package support? > > > > Comments welcome. > > > _______________________________________________ > 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 > _______________________________________________ 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
