Web Push Identifiers
Registration Procedure(s)
- IETF Review
Reference
- RFC 8030: Generic Event Delivery Using HTTP Push
Available Formats
| URN | Description | Contact | Index Value | Reference |
|---|---|---|---|---|
| urn:ietf:params:push | This link relation type is used to identify a resource for sending push messages. | The WEBPUSH WG of the IETF (webpush@ietf.org) | N/A | RFC 8030 |
| urn:ietf:params:push:set | This link relation type is used to identify a collection of push message subscriptions. | The WEBPUSH WG of the IETF (webpush@ietf.org) | N/A | RFC 8030 |
| urn:ietf:params:push:receipt | This link relation type is used to identify a resource for receiving delivery confirmations for push messages. | The WEBPUSH WG of the IETF (webpush@ietf.org) | N/A | RFC 8030 |
VAPID Authentication Scheme Parameters
Registration Procedure(s)
- Specification Required
Expert(s)
- Martin Thomson
Reference
- RFC 8292: Voluntary Application Server Identification (VAPID) for Web Push
Available Formats
| Parameter Name | Purpose | Header Field(s) | Reference |
|---|---|---|---|
| t | JWT authentication token | Authorization | RFC 8292, Section 3.1 |
| k | signing key | Authorization | RFC 8292, Section 3.2 |