Bundle Protocol
draft-ietf-dtn-bpbis-02

The information below is for an old version of the document
Document Type Active Internet-Draft (dtn WG)
Last updated 2016-01-11
Replaces draft-dtnwg-bp
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Additional URLs
- Mailing list discussion
Stream WG state WG Document (wg milestone: Dec 2016 - RFC5050bis... )
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Delay-Tolerant Networking Working Group                     S. Burleigh
Internet Draft                          JPL, Calif. Inst. Of Technology
Intended status: Standards Track                                K. Fall
Expires: December 2015                 Carnegie Mellon University / SEI
                                                             E. Birrane
                                          APL, Johns Hopkins University
                                                       January 11, 2016

                              Bundle Protocol
                        draft-ietf-dtn-bpbis-02.txt

Status of this Memo

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

   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.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on July 14, 2016.

Burleigh                  Expires July 2016                    [Page 1]
Internet-Draft     Proposed Revised Bundle Protocol       January 20166

Copyright Notice

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

Abstract

   This Internet Draft presents a specification for Bundle Protocol,
   adapted from the experimental Bundle Protocol specification
   developed by the Delay-Tolerant Networking Research group of the
   Internet Research Task Force and documented in RFC 5050.

Table of Contents

   1. Introduction...................................................3
   2. Conventions used in this document..............................5
   3. Service Description............................................6
      3.1. Definitions...............................................6
      3.2. Discussion of BP concepts.................................9
      3.3. Services Offered by Bundle Protocol Agents...............14
   4. Bundle Format.................................................14
      4.1. Bundle Processing Control Flags..........................14
      4.2. Block Processing Control Flags...........................16
      4.3. Identifiers..............................................16
         4.3.1. Endpoint ID.........................................16
         4.3.2. Node ID.............................................17
      4.4. Contents of Bundle Blocks................................17
         4.4.1. Primary Bundle Block................................17
         4.4.2. Canonical Bundle Block Format.......................19
      4.5. Extension Blocks.........................................20
         4.5.1. Current Custodian...................................20
         4.5.2. Flow Label..........................................20
         4.5.3. Previous Node ID....................................21
         4.5.4. Bundle Age..........................................21
         4.5.5. Hop Count...........................................21
   5. Bundle Processing.............................................21

Burleigh                  Expires July 2016                    [Page 2]
Internet-Draft     Proposed Revised Bundle Protocol       January 20166
Show full document text