[drinks] RFC 7877 on Session Peering Provisioning Framework (SPPF)
rfc-editor@rfc-editor.org Wed, 17 August 2016 21:37 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: drinks@ietfa.amsl.com
Delivered-To: drinks@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF9F812D09A; Wed, 17 Aug 2016 14:37:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.869
X-Spam-Level:
X-Spam-Status: No, score=-103.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.247, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham 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 Qd9j197ORkZY; Wed, 17 Aug 2016 14:37:14 -0700 (PDT)
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 2AE4D12D768; Wed, 17 Aug 2016 14:37:13 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 22FFFB80BE7; Wed, 17 Aug 2016 14:37:13 -0700 (PDT)
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: <20160817213713.22FFFB80BE7@rfc-editor.org>
Date: Wed, 17 Aug 2016 14:37:13 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/drinks/hRi0n0WvX2AOksolMnj6qDJq0Uk>
Cc: drinks@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
Subject: [drinks] RFC 7877 on Session Peering Provisioning Framework (SPPF)
X-BeenThere: drinks@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF DRINKS WG <drinks.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/drinks>, <mailto:drinks-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/drinks/>
List-Post: <mailto:drinks@ietf.org>
List-Help: <mailto:drinks-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/drinks>, <mailto:drinks-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Aug 2016 21:37:16 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7877
Title: Session Peering Provisioning Framework (SPPF)
Author: K. Cartwright, V. Bhatia,
S. Ali, D. Schwartz
Status: Standards Track
Stream: IETF
Date: August 2016
Mailbox: kcartwright@tnsi.com,
vbhatia@tnsi.com,
syed.ali@neustar.biz,
dschwartz@xconnect.net
Pages: 57
Characters: 121553
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-drinks-spp-framework-12.txt
URL: https://www.rfc-editor.org/info/rfc7877
DOI: http://dx.doi.org/10.17487/RFC7877
This document specifies the data model and the overall structure for
a framework to provision Session Establishment Data (SED) into
Session Data Registries and SIP Service Provider (SSP) data stores.
The framework is called the "Session Peering Provisioning Framework"
(SPPF). The provisioned data is typically used by network elements
for session establishment.
This document is a product of the Data for Reachability of Inter/tra-NetworK SIP Working Group of the IETF.
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