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

The information below is for an old version of the document
Document Type Active Internet-Draft (p2psip WG)
Last updated 2012-05-29
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
P2PSIP                                                      N. Zong, Ed.
Internet-Draft                                                  X. Jiang
Intended status: Standards Track                                 R. Even
Expires: November 30, 2012                           Huawei Technologies
                                                                Y. Zhang
                                                            China Mobile
                                                            May 29, 2012

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

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 intermediary
   peers and describes the potential 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 November 30, 2012.

Copyright Notice

   Copyright (c) 2012 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 November 30, 2012               [Page 1]
Internet-Draft                P2PSIP relay                      May 2012

   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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Zong, et al.            Expires November 30, 2012               [Page 2]
Internet-Draft                P2PSIP relay                      May 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  Backgrounds  . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Problem Statement  . . . . . . . . . . . . . . . . . . . . . .  5
     3.1.  Overview . . . . . . . . . . . . . . . . . . . . . . . . .  5
       3.1.1.  Relay Peer Routing (RPR) . . . . . . . . . . . . . . .  6
     3.2.  Scenarios Where RPR Benefits . . . . . . . . . . . . . . .  6
       3.2.1.  Managed or Closed P2P System . . . . . . . . . . . . .  6
       3.2.2.  Using Bootstrap Peers as Relay Peers . . . . . . . . .  7
       3.2.3.  Wireless Scenarios . . . . . . . . . . . . . . . . . .  7
   4.  Relationship Between SRR and RPR . . . . . . . . . . . . . . .  7
     4.1.  How RPR Works  . . . . . . . . . . . . . . . . . . . . . .  7
     4.2.  How SRR and RPR Work Together  . . . . . . . . . . . . . .  8
   5.  Comparison on cost of SRR and RPR  . . . . . . . . . . . . . .  8
     5.1.  Closed or managed networks . . . . . . . . . . . . . . . .  8
     5.2.  Open networks  . . . . . . . . . . . . . . . . . . . . . .  9
   6.  Extensions to RELOAD . . . . . . . . . . . . . . . . . . . . .  9
     6.1.  Basic Requirements . . . . . . . . . . . . . . . . . . . .  9
     6.2.  Modification To RELOAD Message Structure . . . . . . . . . 10
       6.2.1.  State-keeping Flag . . . . . . . . . . . . . . . . . . 10
       6.2.2.  Extensive Routing Mode . . . . . . . . . . . . . . . . 10
Show full document text