RFC 6940 on REsource LOcation And Discovery (RELOAD) Base Protocol

rfc-editor@rfc-editor.org Fri, 17 January 2014 06:05 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 583B71ADF78; Thu, 16 Jan 2014 22:05:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 3Mdjg4vtUfr7; Thu, 16 Jan 2014 22:05:07 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id BAEF51ADF76; Thu, 16 Jan 2014 22:05:07 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 913557FC396; Thu, 16 Jan 2014 22:04:54 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6940 on REsource LOcation And Discovery (RELOAD) Base Protocol
From: rfc-editor@rfc-editor.org
Message-Id: <20140117060454.913557FC396@rfc-editor.org>
Date: Thu, 16 Jan 2014 22:04:54 -0800
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.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: Fri, 17 Jan 2014 06:05:11 -0000

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

        RFC 6940

        Title:      REsource LOcation And Discovery (RELOAD) 
                    Base Protocol 
        Author:     C. Jennings,
                    B. Lowekamp, Ed., 
                    E. Rescorla,
                    S. Baset, 
                    H. Schulzrinne
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2014
        Mailbox:    fluffy@cisco.com, 
        Pages:      176
        Characters: 403862
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-p2psip-base-26.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6940.txt

This specification defines REsource LOcation And Discovery (RELOAD),
a peer-to-peer (P2P) signaling protocol for use on the Internet.  A
P2P signaling protocol provides its clients with an abstract storage
and messaging service between a set of cooperating peers that form
the overlay network.  RELOAD is designed to support a P2P Session
Initiation Protocol (P2PSIP) network, but can be utilized by other
applications with similar requirements by defining new usages that
specify the Kinds of data that need to be stored for a particular
application.  RELOAD defines a security model based on a certificate
enrollment service that provides unique identities.  NAT traversal is
a fundamental service of the protocol.  RELOAD also allows access
from "client" nodes that do not need to route traffic or store data
for others.

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 Internet
Official Protocol Standards (STD 1) 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 http://www.rfc-editor.org/search/rfc_search.php
For downloading RFCs, see http://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