[rfc-dist] RFC 7316 on The Session Initiation Protocol (SIP) P-Private-Network-Indication Private Header (P-Header)

[rfc-editor at rfc-editor.org (rfc-editor at rfc-editor.org)]

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7316

        Title:      The Session Initiation Protocol (SIP) 
                    P-Private-Network-Indication Private Header (P-Header) 
        Author:     J. van Elburg, K. Drage,
                    M. Ohsugi, S. Schubert,
                    K. Arai
        Status:     Informational
        Stream:     IETF
        Date:       July 2014
        Mailbox:    ietf.hanserik at gmail.com, 
                    drage at alcatel-lucent.com, 
                    mayumi.ohsugi at ntt-at.co.jp, 
                    shida at ntt-at.com, 
                    arai.kenjiro at lab.ntt.co.jp
        Pages:      15
        Characters: 33599
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-vanelburg-dispatch-private-network-ind-07.txt

        URL:        https://www.rfc-editor.org/rfc/rfc7316.txt

This document specifies the SIP P-Private-Network-Indication P-header 
used by the 3GPP.  The P-Private-Network-Indication indicates that the 
message is part of the message traffic of a private network and identifies 
that private network.  A private network indication allows nodes to treat 
private network traffic according to a different set of rules than the set 
applicable to public network traffic.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC