9. IANA Considerations
9. IANA Considerations
This protocol defines new HTTP header fields in Section 9.1. New link relation types are identified using the URNs defined in Section 9.2. Port registration is defined in Section 9.3.
9.1. Header Field Registrations
HTTP header fields are registered within the "Message Headers" registry maintained at https://www.iana.org/assignments/message-headers/.
This document defines the following HTTP header fields, and the following entries have been added to the "Permanent Message Header Field Names" registry ([RFC3864]):
| Header Field Name | Protocol | Status | Reference |
|---|---|---|---|
| TTL | http | standard | Section 5.2 |
| Urgency | http | standard | Section 5.3 |
| Topic | http | standard | Section 5.4 |
The change controller is: "IETF ([email protected]) - Internet Engineering Task Force".
9.2. Link Relation URNs
This document registers URNs for use in identifying link relation types. These have been added to a new "Web Push Identifiers" registry according to the procedures in Section 4 of [RFC3553]; the corresponding push sub-namespace has been entered in the "IETF URN Sub-namespace for Registered Protocol Parameter Identifiers" registry.
The "Web Push Identifiers" registry operates under the IETF Review policy [RFC5226].
Registry name: Web Push Identifiers
URN Prefix: urn:ietf:params:push
Specification: RFC 8030 (this document)
Repository: http://www.iana.org/assignments/webpush-parameters/
Index Value: Values in this registry are URNs or URN prefixes that start with the prefix urn:ietf:params:push. Each is registered independently.
Registrations in the "Web Push Identifiers" registry include the following information:
URN: A complete URN or URN prefix.
Description: A summary description.
Contact: Email for the person or group making the registration.
Index Value: As described in [RFC3553]
Reference: A reference to a specification describing the semantics of the URN or URN prefix.
URN prefixes that are registered include a description of how the URN is constructed. This is not applicable for specific URNs.
These values are entered as the initial content of the "Web Push Identifiers" registry.
URN: urn:ietf:params:push
Description: This link relation type is used to identify a resource for sending push messages.
Contact: The WEBPUSH WG of the IETF ([email protected])
Reference: RFC 8030 (this document)
URN: urn:ietf:params:push:set
Description: This link relation type is used to identify a collection of push message subscriptions.
Contact: The WEBPUSH WG of the IETF ([email protected])
Reference: RFC 8030 (this document)
URN: urn:ietf:params:push:receipt
Description: This link relation type is used to identify a resource for receiving delivery confirmations for push messages.
Contact: The WEBPUSH WG of the IETF ([email protected])
Reference: RFC 8030 (this document)
9.3. Service Name and Port Number Registration
Service names and port numbers are registered within the "Service Name and Transport Protocol Port Number Registry" maintained at https://www.iana.org/assignments/service-names-port-numbers/.
In accordance with [RFC6335], IANA has assigned the System Port number 1001 and the service name webpush.
Service Name: webpush
Port Number: 1001
Transport Protocol: tcp
Description: HTTP Web Push
Assignee: The IESG ([email protected])
Contact: The IETF Chair ([email protected])
Reference: RFC 8030 (this document)