An extension to RELOAD to support Relay Peer Routing
draft-ietf-p2psip-rpr-07

The information below is for an old version of the document
Document Type Active Internet-Draft (p2psip WG)
Last updated 2013-06-17 (latest revision 2013-06-09)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd None
Shepherd write-up Show (last changed 2013-06-10)
IESG IESG state Publication Requested::External Party
Consensus Boilerplate Unknown
Telechat date
Responsible AD Gonzalo Camarillo
IESG note Carlos J. Bernardos (cjbc@it.uc3m.es) is the document shepherd.
Send notices to p2psip-chairs@tools.ietf.org, draft-ietf-p2psip-rpr@tools.ietf.org
P2PSIP                                                           N. Zong
Internet-Draft                                                  X. Jiang
Intended status: Standards Track                                 R. Even
Expires: December 11, 2013                           Huawei Technologies
                                                                Y. Zhang

                                                           June 09, 2013

          An extension to RELOAD to support Relay Peer Routing
                        draft-ietf-p2psip-rpr-07

Abstract

   This document proposes an optional extension to RELOAD 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 December 11, 2013.

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
   carefully, as they describe your rights and restrictions with respect

Zong, et al.            Expires December 11, 2013               [Page 1]
Internet-Draft                P2PSIP relay                     June 2013

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  RPR . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
       3.1.1.  Relay Peer Routing (RPR)  . . . . . . . . . . . . . .   4
     3.2.  Scenarios where RPR can be beneficial . . . . . . . . . .   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 . . . . . . . . . . . . . .   6
     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.  Discovery of relay peers  . . . . . . . . . . . . . . . . . .  11
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
     9.1.  A new RELOAD Forwarding Option  . . . . . . . . . . . . .  12
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  12
     11.2.  Informative References . . . . . . . . . . . . . . . . .  12
Show full document text