Session Initiation Protocol (SIP) Via Header Field Parameter to Indicate Received Realm
RFC 8055

Document Type RFC - Proposed Standard (January 2017; No errata)
Was draft-holmberg-dispatch-received-realm (individual in art area)
Last updated 2017-01-31
Stream IETF
Formats plain text pdf html bibtex
Reviews OPSDIR will not review this version
Stream WG state (None)
Document shepherd Adam Roach
Shepherd write-up Show (last changed 2016-10-10)
IESG IESG state RFC 8055 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Ben Campbell
Send notices to (None)
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                       C. Holmberg
Request for Comments: 8055                                      Ericsson
Category: Standards Track                                       Y. Jiang
ISSN: 2070-1721                                             China Mobile
                                                            January 2017

      Session Initiation Protocol (SIP) Via Header Field Parameter
                       to Indicate Received Realm

Abstract

   This specification defines a new Session Initiation Protocol (SIP)
   Via header field parameter, 'received-realm', which allows a SIP
   entity acting as an entry point to a transit network to indicate from
   which adjacent upstream network a SIP request is received by using a
   network realm value associated with the adjacent network.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc8055.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Holmberg & Jiang             Standards Track                    [Page 1]
RFC 8055                     Received Realm                 January 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Use Case: Transit Network Application Services  . . . . .   3
     1.3.  Use Case: Transit Network Routing . . . . . . . . . . . .   4
   2.  Applicability . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Via 'received-realm' Header Field Parameter . . . . . . . . .   5
     5.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .   5
     5.2.  Operator Identifier . . . . . . . . . . . . . . . . . . .   5
     5.3.  JWS Header  . . . . . . . . . . . . . . . . . . . . . . .   6
     5.4.  JWS Payload . . . . . . . . . . . . . . . . . . . . . . .   6
     5.5.  JWS Serialization . . . . . . . . . . . . . . . . . . . .   7
     5.6.  Syntax  . . . . . . . . . . . . . . . . . . . . . . . . .   8
       5.6.1.  General . . . . . . . . . . . . . . . . . . . . . . .   8
       5.6.2.  ABNF  . . . . . . . . . . . . . . . . . . . . . . . .   8
     5.7.  Example: SIP Via Header Field . . . . . . . . . . . . . .   8
   6.  User Agent and Proxy Behavior . . . . . . . . . . . . . . . .   8
     6.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .   8
     6.2.  Behavior of a SIP Entity Acting as a Network Entry Point    8
     6.3.  Behavior of a SIP Entity Consuming the 'received-realm'
           Value . . . . . . . . . . . . . . . . . . . . . . . . . .   9
   7.  Example: SIP INVITE Request and Response  . . . . . . . . . .   9
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
     8.1.  'received-realm' Via Header Field Parameter . . . . . . .  10
     8.2.  JSON Web Token Claims Registration  . . . . . . . . . . .  10
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     10.2.  Informative References . . . . . . . . . . . . . . . . .  12
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

Holmberg & Jiang             Standards Track                    [Page 2]
RFC 8055                     Received Realm                 January 2017
Show full document text