[P2PSIP] RFC 7890 on Concepts and Terminology for Peer-to-Peer SIP (P2PSIP)

rfc-editor@rfc-editor.org Wed, 22 June 2016 22:57 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: p2psip@ietfa.amsl.com
Delivered-To: p2psip@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id A9E0E12DD8E; Wed, 22 Jun 2016 15:57:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.028
X-Spam-Status: No, score=-104.028 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 5F5DZnPzCeN9; Wed, 22 Jun 2016 15:57:18 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB3CD12D615; Wed, 22 Jun 2016 15:57:18 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A1324B80C5D; Wed, 22 Jun 2016 15:57:18 -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: <20160622225718.A1324B80C5D@rfc-editor.org>
Date: Wed, 22 Jun 2016 15:57:18 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/p2psip/rXspbyIbIP-UxMYyAaP3iWs7sgY>
Cc: p2psip@ietf.org, rfc-editor@rfc-editor.org
Subject: [P2PSIP] RFC 7890 on Concepts and Terminology for Peer-to-Peer SIP (P2PSIP)
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/p2psip>, <mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/p2psip/>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jun 2016 22:57:21 -0000

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

        RFC 7890

        Title:      Concepts and Terminology for Peer-to-Peer 
                    SIP (P2PSIP) 
        Author:     D. Bryan, P. Matthews,
                    E. Shim, D. Willis, S. Dawkins
        Status:     Informational
        Stream:     IETF
        Date:       June 2016
        Mailbox:    dbryan@ethernot.org, 
        Pages:      19
        Characters: 45276
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-p2psip-concepts-09.txt

        URL:        https://www.rfc-editor.org/info/rfc7890

        DOI:        http://dx.doi.org/10.17487/RFC7890

This document defines concepts and terminology for using the Session
Initiation Protocol in a peer-to-peer environment where the
traditional proxy-registrar and message-routing functions are
replaced by a distributed mechanism.  These mechanisms may be
implemented using a Distributed Hash Table or other distributed data
mechanism with similar external properties.  This document includes a
high-level view of the functional relationships between the network
elements defined herein, a conceptual model of operations, and an
outline of the related problems addressed by the P2PSIP working
group, the REsource LOcation And Discovery (RELOAD) protocol, and the
SIP usage document defined by the working group.

This document is a product of the Peer-to-Peer Session Initiation Protocol Working Group of the IETF.

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

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