RFC 7904 on A SIP Usage for REsource LOcation And Discovery (RELOAD)

rfc-editor@rfc-editor.org Sat, 15 October 2016 03:15 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 (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 1D3CF129584; Fri, 14 Oct 2016 20:15:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.598
X-Spam-Status: No, score=-105.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.996, 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 Ax6laj8Az_6a; Fri, 14 Oct 2016 20:15:31 -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 2A3F61293E9; Fri, 14 Oct 2016 20:15:31 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 1755CB8208C; Fri, 14 Oct 2016 20:15:31 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7904 on A SIP Usage for REsource LOcation And Discovery (RELOAD)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20161015031531.1755CB8208C@rfc-editor.org>
Date: Fri, 14 Oct 2016 20:15:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/QAfWQyBnMO427Sga-1koYlxniT4>
Cc: drafts-update-ref@iana.org, p2psip@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Sat, 15 Oct 2016 03:15:33 -0000

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

        RFC 7904

        Title:      A SIP Usage for REsource 
                    LOcation And Discovery (RELOAD) 
        Author:     C. Jennings, 
                    B. Lowekamp,
                    E. Rescorla, 
                    S. Baset,
                    H. Schulzrinne, 
                    T. Schmidt, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2016
        Mailbox:    fluffy@cisco.com, 
        Pages:      20
        Characters: 41978
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-p2psip-sip-21.txt

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

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

This document defines a SIP Usage for REsource LOcation And Discovery
(RELOAD).  The SIP Usage provides the functionality of a SIP proxy or
registrar in a fully distributed system and includes a lookup service
for Address of Records (AORs) stored in the overlay.  It also defines
Globally Routable User Agent URIs (GRUUs) that allow the
registrations to map an AOR to a specific node reachable through the
overlay.  After such initial contact of a Peer, the RELOAD AppAttach
method is used to establish a direct connection between nodes through
which SIP messages are exchanged.

This document is a product of the Peer-to-Peer Session Initiation Protocol 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

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