[rfc-dist] RFC 7264 on An Extension to the REsource LOcation And Discovery (RELOAD) Protocol to Support Relay Peer Routing

rfc-editor at rfc-editor.org (rfc-editor at rfc-editor.org) Tue, 17 June 2014 23:26 UTC

From: "rfc-editor at rfc-editor.org"
Date: Tue, 17 Jun 2014 16:26:30 -0700
Subject: [rfc-dist] RFC 7264 on An Extension to the REsource LOcation And Discovery (RELOAD) Protocol to Support Relay Peer Routing
Message-ID: <20140617232630.1D7911801C2@rfc-editor.org>

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

        
        RFC 7264

        Title:      An Extension to the REsource 
                    LOcation And Discovery (RELOAD) Protocol to 
                    Support Relay Peer Routing 
        Author:     N. Zong, X. Jiang,
                    R. Even, Y. Zhang
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2014
        Mailbox:    zongning at huawei.com, 
                    jiang.x.f at huawei.com, 
                    roni.even at mail01.huawei.com,
                    hishigh at gmail.com
        Pages:      15
        Characters: 31995
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-p2psip-rpr-11.txt

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

This document defines an optional extension to the REsource LOcation
And Discovery (RELOAD) protocol to support the relay peer routing
mode.  RELOAD recommends symmetric recursive routing for routing
messages.  The new optional extension provides a shorter route for
responses, thereby reducing overhead on intermediate peers.  This
document also describes potential cases where this extension can be
used.

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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search
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 at 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