2015
DOI: 10.17487/rfc7515
|View full text |Cite
|
Sign up to set email alerts
|

JSON Web Signature (JWS)

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
55
0
1

Year Published

2017
2017
2022
2022

Publication Types

Select...
4
2
1

Relationship

1
6

Authors

Journals

citations
Cited by 89 publications
(56 citation statements)
references
References 29 publications
0
55
0
1
Order By: Relevance
“…The Via 'received-realm' header field parameter value is represented as a combination of an operator identifier whose value represents the adjacent network and a serialized JSON Web Signature (JWS) [RFC7515]. The JWS Payload consists of the operator identifier and other SIP information element values.…”
Section: Conventionsmentioning
confidence: 99%
See 3 more Smart Citations
“…The Via 'received-realm' header field parameter value is represented as a combination of an operator identifier whose value represents the adjacent network and a serialized JSON Web Signature (JWS) [RFC7515]. The JWS Payload consists of the operator identifier and other SIP information element values.…”
Section: Conventionsmentioning
confidence: 99%
“…The procedures for encoding the JWS and calculating the signature are defined in [RFC7515]. As the JWS Payload information is found in other SIP information elements, the JWS Payload is detached from the serialized JWS conveyed in the header field parameter, as described in Appendix F of [RFC7515].…”
Section: Conventionsmentioning
confidence: 99%
See 2 more Smart Citations
“…The specification builds on the JSON Web Token (JWT) format [RFC7519] in order to provide a self-contained token that can be optionally signed using JSON Web Signature (JWS) [RFC7515] and/or encrypted using JSON Web Encryption (JWE) [RFC7516].…”
Section: Introduction and Overviewmentioning
confidence: 99%