RFC 7316 on The Session Initiation Protocol (SIP) P-Private-Network-Indication Private Header (P-Header)
rfc-editor@rfc-editor.org Tue, 29 July 2014 22:21 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5394E1B29AB for <ietf-announce@ietfa.amsl.com>; Tue, 29 Jul 2014 15:21:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.903
X-Spam-Level:
X-Spam-Status: No, score=-106.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CwnfieJ-P25Q for <ietf-announce@ietfa.amsl.com>; Tue, 29 Jul 2014 15:21:12 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 6872F1B29AF for <ietf-announce@ietf.org>; Tue, 29 Jul 2014 15:21:12 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 61D7D188012; Tue, 29 Jul 2014 15:20:08 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7316 on The Session Initiation Protocol (SIP) P-Private-Network-Indication Private Header (P-Header)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140729222008.61D7D188012@rfc-editor.org>
Date: Tue, 29 Jul 2014 15:20:08 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/92cdvHS-3KXdR1FIuPi2ohBtVdo
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2014 22:21:20 -0000
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@gmail.com,
drage@alcatel-lucent.com,
mayumi.ohsugi@ntt-at.co.jp,
shida@ntt-at.com,
arai.kenjiro@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@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