oauth2.dev

sip_date

IESG

Registry Context

`sip_date` is a sIP Date header field value claim.

Technical Summary

Session Initiation Protocol (SIP) Via Header Field Parameter to Indicate Received Realm Section 5.4 defines `sip_date` for JWT claim sets with the registry description: SIP Date header field value.

When Used

Used in JWTs that follow Session Initiation Protocol (SIP) Via Header Field Parameter to Indicate Received Realm Section 5.4.

Normative Requirements

JWS payload

MUST
1
  1. 8055 - Section 5.4

    include the `sip_date` claim with the SIP Date header field value encoded as NumericDate..

    Condition: When constructing the RFC 8055 JWS payload.

    The following claims MUST be included in the JWS Payload

Validation Guidance

error

When processing `sip_date`, apply the syntax and semantics from Session Initiation Protocol (SIP) Via Header Field Parameter to Indicate Received Realm Section 5.4.

info

Treat `sip_date` as profile-specific unless the JWT explicitly follows the referenced specification.

Reference

Details

Entry Id
sip_date
Claim Name
sip_date
Claim Description
SIP Date header field value
Change Controller
IESG
Reference
RFC8055, RFC3261