RFC 3968

Document history

Date	Version	By	Text
2005-01-04	02	(System)	This was part of a ballot set with: draft-ietf-sip-uri-parameter-reg
2005-01-04	02	Amy Vezza	State Changes to RFC Published from RFC Ed Queue by Amy Vezza
2005-01-04	02	Amy Vezza	[Note]: 'RFC 3968 BCP 98' added by Amy Vezza
2004-12-21	02	(System)	RFC published
2004-06-29	02	Amy Vezza	State Changes to RFC Ed Queue from Approved-announcement sent by Amy Vezza
2004-06-28	02	Amy Vezza	IESG has approved and state has been changed to 'Approved-Announcement sent' by Amy Vezza.
2004-06-28	02	Amy Vezza	Closed "Approve" ballot
2004-06-28	02	Allison Mankin	Note: went through mailing list, minutes and checked chairs on the RFC Editor note about IANA Considerations.
2004-06-28	02	Allison Mankin	Note field has been cleared by Allison Mankin
2004-06-25	02	Allison Mankin	[Note]: 'Approved with two RFC Editor Notes: Universal Resource -> Uniform Resource in title Specification Required -> IETF Consensus in parameters doc. This was the intent, that ... [show all] [Note]: 'Approved with two RFC Editor Notes: Universal Resource -> Uniform Resource in title Specification Required -> IETF Consensus in parameters doc. This was the intent, that header parameters (like the values) must include publication in an IETF RFC, not in a non-IETF spec.' added by Allison Mankin
2004-06-25	02	(System)	Removed from agenda for telechat - 2004-06-24
2004-06-24	02	Amy Vezza	[Ballot Position Update] New position, No Objection, has been recorded for Harald Alvestrand by Amy Vezza
2004-06-24	02	Allison Mankin	State Changes to Approved-announcement to be sent::Point Raised - writeup needed from Approved-announcement to be sent by Allison Mankin
2004-06-24	02	Allison Mankin	State Changes to Approved-announcement to be sent from IESG Evaluation by Allison Mankin
2004-06-24	02	Bill Fenner	[Ballot Position Update] New position, No Objection, has been recorded for Bill Fenner by Bill Fenner
2004-06-24	02	Thomas Narten	[Ballot Position Update] New position, No Objection, has been recorded for Thomas Narten by Thomas Narten
2004-06-24	02	Jon Peterson	[Ballot Position Update] New position, Yes, has been recorded for Jon Peterson by Jon Peterson
2004-06-24	02	Alex Zinin	[Ballot comment] > 3. Use of the Registry ... > Registered SIP header field parameters and parameter values are to be > considered "reserved words". In order to preserve ... [show all] [Ballot comment] > 3. Use of the Registry ... > Registered SIP header field parameters and parameter values are to be > considered "reserved words". In order to preserve interoperability, > registered parameters and parameter values MUST be used in a manner > consistent with that described in their defining RFC. The MUST above reads a bit like that for smb's evil bit. I.e. is this a requirement for implementations of all registered params? What is it doing here?
2004-06-24	02	Alex Zinin	[Ballot Position Update] New position, No Objection, has been recorded for Alex Zinin by Alex Zinin
2004-06-24	02	Margaret Wasserman	[Ballot Position Update] New position, No Objection, has been recorded for Margaret Wasserman by Margaret Wasserman
2004-06-23	02	David Kessens	[Ballot Position Update] New position, No Objection, has been recorded for David Kessens by David Kessens
2004-06-23	02	Russ Housley	[Ballot Position Update] New position, No Objection, has been recorded for Russ Housley by Russ Housley
2004-06-22	02	Ted Hardie	[Ballot Position Update] Position for Ted Hardie has been changed to No Objection from Undefined by Ted Hardie
2004-06-22	02	Ted Hardie	[Ballot comment] In the parameter registry document, I think this text: Parameters that can appear in different header fields MAY have the same name. However ... [show all] [Ballot comment] In the parameter registry document, I think this text: Parameters that can appear in different header fields MAY have the same name. However, parameters that can appear in the same header field MUST have different names. needs to be clarified. I read it as saying that the registry may include the same name multiple times, provided that each instance is attached to a different header field. If a parameter with a specific name is already associated with a specific header, a new parameter may not be registered under that name. If that is correct, using language that describes the registry actions is probably a good idea for this document; if it is not correct, I am not sure what to suggest. While I don't wish to block the document on this, I do wonder why the uri parameter registry did not include columns for "applies to SIP URIs" and "applies to SIPS URIs" instead of advice to consult the specification. I would certainly not suggest allowing the same parameter to appear twice with different semantics, one for SIP and one for SIPS, but the choice to elide the applicability from the registry seems odd.
2004-06-22	02	Ted Hardie	[Ballot comment] In the parameter registry document, I think this text: Parameters that can appear in different header fields MAY have the same name. However ... [show all] [Ballot comment] In the parameter registry document, I think this text: Parameters that can appear in different header fields MAY have the same name. However, parameters that can appear in the same header field MUST have different names. needs to be clarified. I read it as saying that the registry may include the same name multiple times, provided that each instance is attached to a different header field. If a parameter with a specific name is already associated with a specific header, a new parameter may not be registered under that name. If that is correct, using language that describes the registry actions is probably a good idea for this document; if it is not correct, I am not sure what to suggest.
2004-06-22	02	Ted Hardie	[Ballot Position Update] New position, Undefined, has been recorded for Ted Hardie by Ted Hardie
2004-06-18	02	Steven Bellovin	[Ballot Position Update] New position, No Objection, has been recorded for Steve Bellovin by Steve Bellovin
2004-06-18	02	Scott Hollenbeck	[Ballot Position Update] New position, No Objection, has been recorded for Scott Hollenbeck by Scott Hollenbeck
2004-06-17	02	Allison Mankin	[Note]: 'IANA reviewed (IESG list mail 20040602).Â ' added by Allison Mankin
2004-06-17	02	Allison Mankin	[Note]: 'IANA reviewed (IESG list mail 20040602).Â Slightly tweaking Security Considerations in RFC Editor Note.' added by Allison Mankin
2004-06-17	02	Allison Mankin	Placed on agenda for telechat - 2004-06-24 by Allison Mankin
2004-06-17	02	Allison Mankin	State Changes to IESG Evaluation from Waiting for Writeup by Allison Mankin
2004-06-17	02	Allison Mankin	[Note]: 'IANA reviewed (IESG list mail 20040602). Slightly tweaking Security Considerations in RFC Editor Note.' added by Allison Mankin
2004-06-17	02	Allison Mankin	[Ballot Position Update] New position, Yes, has been recorded for Allison Mankin
2004-06-17	02	Allison Mankin	Ballot has been issued by Allison Mankin
2004-06-17	02	Allison Mankin	Created "Approve" ballot
2004-06-17	02	(System)	New version available: draft-ietf-sip-parameter-registry-02 (diff from -01)
2004-06-15	01	Allison Mankin	Note field has been cleared by Allison Mankin
2004-06-03	01	(System)	State has been changed to Waiting for Writeup from In Last Call by system
2004-06-02	01	Michelle Cotton	IANA Last Call Comments: Note the spelling error in paragraph 3 (dissimialr) Upon approval of this document, the IANA will create a new sub-registry for ... [show all] IANA Last Call Comments: Note the spelling error in paragraph 3 (dissimialr) Upon approval of this document, the IANA will create a new sub-registry for sip header field parameters. This registry will be placed at the following: <http://www.iana.org/assignments/sip-parameters>
2004-05-20	01	Amy Vezza	Last call sent
2004-05-20	01	Amy Vezza	State Changes to In Last Call from Last Call Requested by Amy Vezza
2004-05-20	01	Allison Mankin	[Note]: 'Note sip-parameter-registry has a garbled format at the end and both documents need a revised id-nits check because I waited to Last Call them ... [show all] [Note]: 'Note sip-parameter-registry has a garbled format at the end and both documents need a revised id-nits check because I waited to Last Call them until knowing that IANA was going to be able to handle large registries again.' added by Allison Mankin
2004-05-20	01	Allison Mankin	State Changes to Last Call Requested from AD Evaluation by Allison Mankin
2004-05-20	01	Allison Mankin	Last Call was requested by Allison Mankin
2004-05-20	01	(System)	Ballot writeup text was added
2004-05-20	01	(System)	Last call text was added
2004-05-20	01	(System)	Ballot approval text was added
2004-05-20	01	Allison Mankin	State Change Notice email list have been change to <b>gonzalo.camarillo@ericsson.com, rohan@cisco.com, dean.willis@softarmor.com, jon.peterson@neustar.biz from
2004-04-05	01	Allison Mankin	State Changes to AD Evaluation from Publication Requested by Allison Mankin
2003-12-22	01	Dinara Suleymanova	Draft Added by Dinara Suleymanova
2003-11-25	01	(System)	New version available: draft-ietf-sip-parameter-registry-01 (diff from -00)
2003-08-22	00	(System)	New version available: draft-ietf-sip-parameter-registry-00

The Internet Assigned Number Authority (IANA) Header Field Parameter Registry for the Session Initiation Protocol (SIP) RFC 3968

Document history

The Internet Assigned Number Authority (IANA) Header Field Parameter Registry for the Session Initiation Protocol (SIP)
RFC 3968