rfc9725v3.txt		rfc9725.txt
	skipping to change at line 1053 ¶		skipping to change at line 1053 ¶
	(Section 6.3)		(Section 6.3)
	* "WebRTC-HTTP Ingestion Protocol (WHIP) Extension URNs" registry		* "WebRTC-HTTP Ingestion Protocol (WHIP) Extension URNs" registry
	(Section 6.4)		(Section 6.4)
	6.3. WebRTC-HTTP Ingestion Protocol (WHIP) URNs Registry		6.3. WebRTC-HTTP Ingestion Protocol (WHIP) URNs Registry
	The "WebRTC-HTTP Ingestion Protocol (WHIP) URNs" registry is used to		The "WebRTC-HTTP Ingestion Protocol (WHIP) URNs" registry is used to
	manage entries within the "urn:ietf:params:whip" namespace. The		manage entries within the "urn:ietf:params:whip" namespace. The
	registration procedure is "Specification Required" [RFC8126]. The		registration procedure is "Specification Required" [RFC8126]. The
	registry contains the following fields: URI, Description, Reference,		registry contains the following fields: URN, Name, Reference, IANA
	IANA Registry Reference, and Change Controller. This document is		Registry Reference, and Change Controller. This document is listed
	listed as the reference.		as the reference.
	The registry contains a single initial entry:		The registry contains a single initial entry:
	URI: urn:ietf:params:whip:ext		URN: urn:ietf:params:whip:ext
	Description: WebRTC-HTTP Ingestion Protocol (WHIP) extension URNs		Name: WebRTC-HTTP Ingestion Protocol (WHIP) extension URNs
	Reference: Section 6.4 of RFC 9725		Reference: Section 6.4 of RFC 9725
	IANA Registry Reference: See "WebRTC-HTTP Ingestion Protocol (WHIP)		IANA Registry Reference: See "WebRTC-HTTP Ingestion Protocol (WHIP)
	Extension URNs" on <https://www.iana.org/assignments/whip>		Extension URNs" on <https://www.iana.org/assignments/whip>
	Change Controller: IETF		Change Controller: IETF
	6.4. WebRTC-HTTP Ingestion Protocol (WHIP) Extension URNs Registry		6.4. WebRTC-HTTP Ingestion Protocol (WHIP) Extension URNs Registry
	The "WebRTC-HTTP Ingestion Protocol (WHIP) Extension URNs" registry		The "WebRTC-HTTP Ingestion Protocol (WHIP) Extension URNs" registry
	is used to manage entries within the "urn:ietf:params:whip:ext"		is used to manage entries within the "urn:ietf:params:whip:ext"
	namespace. The registration procedure is "Specification Required"		namespace. The registration procedure is "Specification Required"
	[RFC8126]. The registry contains the following fields: URI,		[RFC8126]. The registry contains the following fields: URN, Name,
	Description, Reference, IANA Registry Reference, and Change		Reference, IANA Registry Reference, and Change Controller. This
	Controller. This document is listed as the reference.		document is listed as the reference.
	A WHIP extension URN is used as a value in the "rel" attribute of the		A WHIP extension URN is used as a value in the "rel" attribute of the
	Link header as defined in Section 4.9 for the purpose of signaling		Link header as defined in Section 4.9 for the purpose of signaling
	the WHIP extensions supported by the WHIP endpoint. WHIP extension		the WHIP extensions supported by the WHIP endpoint. WHIP extension
	URNs have an "ext" type.		URNs have an "ext" type.
	6.5. Registering WHIP URNs and WHIP Extension URNs		6.5. Registering WHIP URNs and WHIP Extension URNs
	This section defines the process for registering new URNs in the		This section defines the process for registering new URNs in the
	"WebRTC-HTTP Ingestion Protocol (WHIP) URNs" registry (Section 6.3)		"WebRTC-HTTP Ingestion Protocol (WHIP) URNs" registry (Section 6.3)
	skipping to change at line 1151 ¶		skipping to change at line 1151 ¶
	made available for review and comments by posting the request to		made available for review and comments by posting the request to
	the <wish@ietf.org> mailing list.		the <wish@ietf.org> mailing list.
	* Ensure that any other request for a code point does not conflict		* Ensure that any other request for a code point does not conflict
	with work that is active or already published by the IETF.		with work that is active or already published by the IETF.
	6.5.3. Registration Template		6.5.3. Registration Template
	A WHIP extension URN is defined by completing the following template:		A WHIP extension URN is defined by completing the following template:
	URN: A unique URN for the WHIP extension (e.g.,		URN: A unique URN (e.g., "urn:ietf:params:whip:ext:example:server-
	"urn:ietf:params:whip:ext:example:server-sent-events")		sent-events")
	Name: A descriptive name of the WHIP extension (e.g., "Sender Side		Name: A descriptive name (e.g., "Sender Side events")
	events")
	Reference: A formal reference to the publicly available		Reference: A formal reference to the publicly available
	specification		specification
	IANA Registry Reference: For parameters defined in an IETF Standards		IANA Registry Reference: The registry related to the new URN
	Track document, list the RFC number. For parameters defined by
	other organizations or in non-IETF documents, provide a stable,
	publicly available reference (such as a URL or document ID). If
	multiple specifications define or update the parameter, list all
	relevant references.
	Change Controller: For Standards Track documents, this is "IETF".		Change Controller: For Standards Track documents, this is "IETF".
	Otherwise, this is the name of the person or body that has change		Otherwise, this is the name of the person or body that has change
	control over the specification.		control over the specification.
	7. References		7. References
	7.1. Normative References		7.1. Normative References
	[FETCH] WHATWG, "Fetch", WHATWG Living Standard,		[FETCH] WHATWG, "Fetch", WHATWG Living Standard,
End of changes. 7 change blocks.
	18 lines changed or deleted		12 lines changed or added
This html diff was produced by rfcdiff 1.48.