datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

An Extension to REsource LOcation And Discovery (RELOAD) Protocol to Support Relay Peer Routing
draft-ietf-p2psip-rpr-11

Document type: Active Internet-Draft (p2psip WG)
Document stream: IETF
Last updated: 2014-03-11 (latest revision 2013-10-20)
Intended RFC status: Proposed Standard
Other versions: plain text, pdf, html

IETF State: WG Document
Consensus: Yes
Document shepherd: Carlos Bernardos
Shepherd Write-Up: Last changed 2013-06-10

IESG State: RFC Ed Queue
IANA Review State: IANA OK - Actions Needed
IANA Action State: RFC-Ed-Ack
RFC Editor State: EDIT
Responsible AD: Gonzalo Camarillo
Send notices to: p2psip-chairs@tools.ietf.org, draft-ietf-p2psip-rpr@tools.ietf.org

P2PSIP                                                      N. Zong, Ed.
Internet-Draft                                                  X. Jiang
Intended status: Standards Track                                 R. Even
Expires: April 24, 2014                              Huawei Technologies
                                                                Y. Zhang
                                                                 CoolPad
                                                        October 21, 2013

  An Extension to REsource LOcation And Discovery (RELOAD) Protocol to
                       Support Relay Peer Routing
                        draft-ietf-p2psip-rpr-11

Abstract

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

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 24, 2014.

Copyright Notice

   Copyright (c) 2013 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

Zong, et al.             Expires April 24, 2014                 [Page 1]
Internet-Draft                P2PSIP relay                  October 2013

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  RPR . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Scenarios where RPR can be used . . . . . . . . . . . . .   5
       3.2.1.  Managed or closed P2P systems . . . . . . . . . . . .   5
       3.2.2.  Using bootstrap nodes as relay peers  . . . . . . . .   5
       3.2.3.  Wireless scenarios  . . . . . . . . . . . . . . . . .   6
   4.  Relationship between SRR and RPR  . . . . . . . . . . . . . .   6
     4.1.  How RPR works . . . . . . . . . . . . . . . . . . . . . .   6
     4.2.  How SRR and RPR work together . . . . . . . . . . . . . .   6
   5.  Comparison on cost of SRR and RPR . . . . . . . . . . . . . .   7
     5.1.  Closed or managed networks  . . . . . . . . . . . . . . .   7
     5.2.  Open networks . . . . . . . . . . . . . . . . . . . . . .   7
   6.  RPR extensions to RELOAD  . . . . . . . . . . . . . . . . . .   8
     6.1.  Basic requirements  . . . . . . . . . . . . . . . . . . .   8
     6.2.  Modification to RELOAD message structure  . . . . . . . .   8
       6.2.1.  State-keeping flag  . . . . . . . . . . . . . . . . .   8
       6.2.2.  Extensive routing mode  . . . . . . . . . . . . . . .   9
     6.3.  Creating a request  . . . . . . . . . . . . . . . . . . .   9
       6.3.1.  Creating a request for RPR  . . . . . . . . . . . . .   9
     6.4.  Request and response processing . . . . . . . . . . . . .  10
       6.4.1.  Destination peer: receiving a request and sending a
               response  . . . . . . . . . . . . . . . . . . . . . .  10
       6.4.2.  Sending peer: receiving a response  . . . . . . . . .  11
       6.4.3.  Relay peer processing . . . . . . . . . . . . . . . .  11
   7.  Overlay configuration extension . . . . . . . . . . . . . . .  11
   8.  Discovery of relay peers  . . . . . . . . . . . . . . . . . .  11
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12

[include full document text]