[rfc-dist] RFC 8055 on Session Initiation Protocol (SIP) Via Header Field Parameter to Indicate Received Realm
rfc-editor@rfc-editor.org Wed, 01 February 2017 01:46 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15D251296F5 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 31 Jan 2017 17:46:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.4
X-Spam-Level:
X-Spam-Status: No, score=-7.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 FXfbLzbFKMsl for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 31 Jan 2017 17:46:00 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C000912970A for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 31 Jan 2017 17:45:23 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 4E56BB81C48; Tue, 31 Jan 2017 17:45:20 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 1C5D1B81C45; Tue, 31 Jan 2017 17:45:19 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170201014519.1C5D1B81C45@rfc-editor.org>
Date: Tue, 31 Jan 2017 17:45:19 -0800
Subject: [rfc-dist] RFC 8055 on Session Initiation Protocol (SIP) Via Header Field Parameter to Indicate Received Realm
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
A new Request for Comments is now available in online RFC libraries.
RFC 8055
Title: Session Initiation Protocol (SIP) Via
Header Field Parameter to Indicate Received
Realm
Author: C. Holmberg, Y. Jiang
Status: Standards Track
Stream: IETF
Date: January 2017
Mailbox: christer.holmberg@ericsson.com,
jiangyi@chinamobile.com
Pages: 13
Characters: 25117
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-holmberg-dispatch-received-realm-12.txt
URL: https://www.rfc-editor.org/info/rfc8055
DOI: 10.17487/RFC8055
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.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. 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/retrieve/bulk
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
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org