Browse Prior Art Database

An Extension to the REsource LOcation And Discovery (RELOAD) Protocol to Support Relay Peer Routing (RFC7264)

IP.com Disclosure Number: IPCOM000237455D
Publication Date: 2014-Jun-18
Document File: 30 page(s) / 32K

Publishing Venue

The IP.com Prior Art Database

Related People

N. Zong: AUTHOR [+4]

Abstract

The REsource LOcation And Discovery (RELOAD) protocol [RFC6940] recommends symmetric recursive routing (SRR) for routing messages and describes the extensions that would be required to support additional routing algorithms. In addition to SRR, two other routing options -- direct response routing (DRR) and relay peer routing (RPR) -- are also discussed in Appendix A of [RFC6940]. As we show in Section 3, RPR is advantageous over SRR in some scenarios in that RPR can reduce load (CPU and link bandwidth) on intermediate peers. RPR works better in a network where relay peers are provisioned in advance so

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 9% of the total text.

Internet Engineering Task Force (IETF)                           N. Zong Request for Comments: 7264                                      X. Jiang Category: Standards Track                                        R. Even ISSN: 2070-1721                                      Huawei Technologies                                                                 Y. Zhang                                                   CoolPad / China Mobile                                                                June 2014

  An Extension to the REsource LOcation And Discovery (RELOAD) Protocol                      to Support Relay Peer Routing

Abstract

   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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7264.

 Zong, et al.                 Standards Track                    [Page 1]
 RFC 7264                       P2PSIP RPR                      June 2014

 Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

Zo...