draft-ietf-dtn-bibect-00.txt   draft-ietf-dtn-bibect-01.txt 
Delay-Tolerant Networking Working Group S. Burleigh Delay-Tolerant Networking Working Group S. Burleigh
Internet Draft JPL, Calif. Inst. Of Technology Internet Draft JPL, Calif. Inst. Of Technology
Intended status: Standards Track July 30, 2018 Intended status: Standards Track January 31, 2019
Expires: January 2019 Expires: August 2019
Bundle-in-Bundle Encapsulation Bundle-in-Bundle Encapsulation
draft-ietf-dtn-bibect-00.txt draft-ietf-dtn-bibect-01.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 31 skipping to change at page 1, line 31
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on January 31, 2019. This Internet-Draft will expire on August 4, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License. warranty as described in the Simplified BSD License.
Internet-Draft Bundle-in-Bundle Encapsulation January 20199
Abstract Abstract
This document describes Bundle-in-Bundle Encapsulation (BIBE), a This document describes Bundle-in-Bundle Encapsulation (BIBE), a
Delay-Tolerant Networking (DTN) Bundle Protocol (BP) "convergence Delay-Tolerant Networking (DTN) Bundle Protocol (BP) "convergence
layer" protocol that tunnels BP "bundles" through encapsulating layer" protocol that tunnels BP "bundles" through encapsulating
bundles. The services provided by the BIBE convergence-layer bundles. The services provided by the BIBE convergence-layer
protocol adapter encapsulate an outbound BP "bundle" in a BIBE protocol adapter encapsulate an outbound BP "bundle" in a BIBE
convergence-layer protocol data unit for transmission as the payload convergence-layer protocol data unit for transmission as the payload
of a bundle. Security measures applied to the encapsulating bundle of a bundle. Security measures applied to the encapsulating bundle
may augment those applied to the encapsulated bundle. The protocol may augment those applied to the encapsulated bundle. The protocol
skipping to change at page 3, line 5 skipping to change at page 3, line 5
Appendix A. For More Information.................................13 Appendix A. For More Information.................................13
Appendix B. CDDL expression......................................14 Appendix B. CDDL expression......................................14
1. Introduction 1. Introduction
This document describes Bundle-in-Bundle Encapsulation (BIBE), a This document describes Bundle-in-Bundle Encapsulation (BIBE), a
Delay-Tolerant Networking (DTN) Bundle Protocol (BP) [RFC5050] Delay-Tolerant Networking (DTN) Bundle Protocol (BP) [RFC5050]
"convergence layer" protocol that tunnels BP "bundles" through "convergence layer" protocol that tunnels BP "bundles" through
encapsulating bundles. encapsulating bundles.
Internet-Draft Bundle-in-Bundle Encapsulation January 20199
Conformance to the bundle-in-bundle encapsulation (BIBE) Conformance to the bundle-in-bundle encapsulation (BIBE)
specification is OPTIONAL for BP nodes. Each BP node that conforms specification is OPTIONAL for BP nodes. Each BP node that conforms
to the BIBE specification provides a BIBE convergence-layer adapter to the BIBE specification provides a BIBE convergence-layer adapter
(CLA) that is implemented within the administrative element of the (CLA) that is implemented within the administrative element of the
BP node's application agent. Like any convergence-layer adapter, BP node's application agent. Like any convergence-layer adapter,
the BIBE CLA provides: the BIBE CLA provides:
. A transmission service that sends an outbound bundle (from the . A transmission service that sends an outbound bundle (from the
bundle protocol agent) to a peer CLA. In the case of BIBE, the bundle protocol agent) to a peer CLA. In the case of BIBE, the
sending CLA and receiving peer CLA are both BP nodes. sending CLA and receiving peer CLA are both BP nodes.
skipping to change at page 4, line 4 skipping to change at page 4, line 4
destination"). destination").
Note that: Note that:
. If the payload of the encapsulating bundle is protected by a . If the payload of the encapsulating bundle is protected by a
Bundle Confidentiality Block (BCB), then the source and Bundle Confidentiality Block (BCB), then the source and
destination of the encapsulated bundle are encrypted, providing destination of the encapsulated bundle are encrypted, providing
defense against traffic analysis that BPSEC alone cannot offer. defense against traffic analysis that BPSEC alone cannot offer.
. Bundles whose payloads are BIBE protocol data units may . Bundles whose payloads are BIBE protocol data units may
themselves be forwarded via a BIBE convergence-layer adapter, themselves be forwarded via a BIBE convergence-layer adapter,
Internet-Draft Bundle-in-Bundle Encapsulation January 20199
enabling nested bundle encapsulation to arbitrary depth as enabling nested bundle encapsulation to arbitrary depth as
required by security policy. required by security policy.
. Moreover, in the event that no single point of egress from an . Moreover, in the event that no single point of egress from an
insecure region of network topology can be determined at the insecure region of network topology can be determined at the
moment a bundle is to be encapsulated, multiple copies of the moment a bundle is to be encapsulated, multiple copies of the
bundle may be encapsulated individually and forwarded to all bundle may be encapsulated individually and forwarded to all
candidate points of egress. candidate points of egress.
The protocol includes a mechanism for recovery from loss of an The protocol includes a mechanism for recovery from loss of an
encapsulating bundle, called "custody transfer". This mechanism is encapsulating bundle, called "custody transfer". This mechanism is
skipping to change at page 4, line 45 skipping to change at page 4, line 48
BIBE convergence-layer protocol endpoints, also known as BIBE BIBE convergence-layer protocol endpoints, also known as BIBE
convergence-layer adapters (BCLAs), are the Administrative Elements convergence-layer adapters (BCLAs), are the Administrative Elements
of Bundle Protocol nodes that conform to the BIBE protocol of Bundle Protocol nodes that conform to the BIBE protocol
specification. The node of which a given BCLA is one component is specification. The node of which a given BCLA is one component is
termed the BCLA's "local node". termed the BCLA's "local node".
3.2. BIBE Protocol Data Units 3.2. BIBE Protocol Data Units
Notionally, a BCLA is assumed to implement in some way, for each Notionally, a BCLA is assumed to implement in some way, for each
neighboring node to which the local node issues Bundle Protocol Data neighboring node to which the local node issues BIBE Protocol Data
Units (BPDUs), the following two data resources: Units (BPDUs), the following two data resources:
1. A "custodial transmission count" (CTC). A CTC is a 1. A "custodial transmission count" (CTC). A CTC is a
monotonically increasing integer indicating the number of monotonically increasing integer indicating the number of
"custodial" BPDUs - that is, BPDUs for which custody transfer "custodial" BPDUs - that is, BPDUs for which custody transfer
Internet-Draft Bundle-in-Bundle Encapsulation January 20199
was requested - that have been issued to the neighboring node was requested - that have been issued to the neighboring node
by the local node since instantiation of the local node. by the local node since instantiation of the local node.
2. A "custodial transmission database" (CTDB), a notional array of 2. A "custodial transmission database" (CTDB), a notional array of
"custodial transmission items" (CTIs). The CTDB contains one "custodial transmission items" (CTIs). The CTDB contains one
CTI for each custodial BPDU issued to the neighboring node, by CTI for each custodial BPDU issued to the neighboring node, by
the local node, for which (a) no custody disposition has yet the local node, for which (a) no custody disposition has yet
been received in any custody signal (as discussed later) and been received in any custody signal (as discussed later) and
(b) the bundle encapsulated in that BPDU has not yet been (b) the bundle encapsulated in that BPDU has not yet been
destroyed due to, e.g., time-to-live expiration. Each CTI destroyed due to, e.g., time-to-live expiration. Each CTI
notionally contains: notionally contains:
skipping to change at page 5, line 48 skipping to change at page 5, line 51
expected), represented as a CBOR unsigned integer. Retransmission expected), represented as a CBOR unsigned integer. Retransmission
time for a BPDU for which custody transfer is NOT requested SHALL be time for a BPDU for which custody transfer is NOT requested SHALL be
zero. Retransmission time for a BPDU for which custody transfer IS zero. Retransmission time for a BPDU for which custody transfer IS
requested SHALL take the form of a "DTN Time" as defined in the requested SHALL take the form of a "DTN Time" as defined in the
Bundle Protocol specification; determination of the value of Bundle Protocol specification; determination of the value of
retransmission time is an implementation matter that is beyond the retransmission time is an implementation matter that is beyond the
scope of this specification and may be dynamically responsive to scope of this specification and may be dynamically responsive to
changes in connectivity. changes in connectivity.
The third item of the BPDU array SHALL be a single BP bundle, termed The third item of the BPDU array SHALL be a single BP bundle, termed
the "encapsulated bundle", represented as a CBOR byte string. the "encapsulated bundle", represented as a CBOR byte string of
definite length.
Internet-Draft Bundle-in-Bundle Encapsulation January 20199
3.3. Custody Signals 3.3. Custody Signals
A "custody signal" is defined as a Bundle Protocol administrative A "custody signal" is a Bundle Protocol administrative record whose
record whose record type code is 4 (i.e., bit pattern 0100) and record type code is 4 (i.e., bit pattern 0100) and whose content is
whose content is constructed as follows. constructed as follows.
The content of each custody signal SHALL be represented as a CBOR The content of each custody signal SHALL be represented as a CBOR
array. The number of elements in the array SHALL be 2. array. The number of elements in the array SHALL be 2.
The first item of the custody signal content array SHALL be a The first item of the custody signal content array SHALL be a
disposition code represented as a CBOR unsigned integer. Valid disposition code represented as a CBOR unsigned integer. Valid
disposition codes are defined as follows: disposition codes are defined as follows:
+---------+--------------------------------------------+ +---------+--------------------------------------------+
skipping to change at page 7, line 4 skipping to change at page 7, line 4
| 4 | Depleted storage. | | 4 | Depleted storage. |
+---------+--------------------------------------------+ +---------+--------------------------------------------+
| 5 | Destination endpoint ID unintelligible. | | 5 | Destination endpoint ID unintelligible. |
+---------+--------------------------------------------+ +---------+--------------------------------------------+
| 6 | No known route destination from here. | | 6 | No known route destination from here. |
Internet-Draft Bundle-in-Bundle Encapsulation January 20199
+---------+--------------------------------------------+ +---------+--------------------------------------------+
| 7 | No timely contact with next node on route. | | 7 | No timely contact with next node on route. |
+---------+--------------------------------------------+ +---------+--------------------------------------------+
| 8 | Block unintelligible. | | 8 | Block unintelligible. |
+---------+--------------------------------------------+ +---------+--------------------------------------------+
skipping to change at page 8, line 5 skipping to change at page 8, line 5
of all bundles that were encapsulated in the indicated BPDUs. of all bundles that were encapsulated in the indicated BPDUs.
Otherwise the source of the custody signal has refused custody of Otherwise the source of the custody signal has refused custody of
all bundles that were encapsulated in the indicated BPDUs, for the all bundles that were encapsulated in the indicated BPDUs, for the
indicated reason. indicated reason.
3.4. Custody Transfer Status Reports 3.4. Custody Transfer Status Reports
A "custody transfer status report" is a bundle status report with A "custody transfer status report" is a bundle status report with
the "reporting node attempted custody transfer" flag set to 1. the "reporting node attempted custody transfer" flag set to 1.
Internet-Draft Bundle-in-Bundle Encapsulation January 20199
4. BIBE Procedures 4. BIBE Procedures
4.1. BPDU Transmission 4.1. BPDU Transmission
When a BCLA is requested by the bundle protocol agent to send a When a BCLA is requested by the bundle protocol agent to send a
bundle to the peer BCLA(s) included in the BP endpoint identified by bundle to the peer BCLA(s) included in the BP endpoint identified by
a specified BP endpoint ID: a specified BP endpoint ID:
. The BCLA SHALL generate, as defined in Section 6.2 of the . The BCLA SHALL generate, as defined in Section 6.2 of the
Bundle Protocol specification (a work in progress), a BPDU for Bundle Protocol specification (a work in progress), a BPDU for
skipping to change at page 9, line 5 skipping to change at page 9, line 5
Note that the custody transfer retransmission timer mechanism Note that the custody transfer retransmission timer mechanism
provides a means of recovering from loss of an encapsulating bundle provides a means of recovering from loss of an encapsulating bundle
as indicated by non-arrival of a responding custody signal. as indicated by non-arrival of a responding custody signal.
4.2. BPDU Reception 4.2. BPDU Reception
When a BCLA receives a BPDU from the bundle protocol agent (that is, When a BCLA receives a BPDU from the bundle protocol agent (that is,
upon delivery of the payload of an encapsulating bundle): upon delivery of the payload of an encapsulating bundle):
Internet-Draft Bundle-in-Bundle Encapsulation January 20199
. If Custody Transfer was requested for this BPDU (as indicated . If Custody Transfer was requested for this BPDU (as indicated
by a non-zero value of transmission ID): by a non-zero value of transmission ID):
o If the encapsulated bundle has the same source node ID, o If the encapsulated bundle has the same source node ID,
creation timestamp, and (if that bundle is a fragment) creation timestamp, and (if that bundle is a fragment)
fragment offset and payload length as another bundle that fragment offset and payload length as another bundle that
is currently retained at the BCLA's local node, then is currently retained at the BCLA's local node, then
custody transfer redundancy MUST be handled as follows: custody transfer redundancy MUST be handled as follows:
. The BCLA SHALL add the BPDU's transmission ID to the . The BCLA SHALL add the BPDU's transmission ID to the
disposition scope report of a pending outbound disposition scope report of a pending outbound
custody signal, destined for the node that was the custody signal, destined for the node that was the
source of the encapsulating bundle, whose disposition source of the encapsulating bundle, whose disposition
is the reason code from Figure 1 for "Redundant is the reason code from Figure 1 for "Redundant
reception"., reception".
o Otherwise, if the BCLA determines that its local node can o Otherwise, if the BCLA determines that its local node can
neither deliver nor forward the encapsulated bundle for neither deliver nor forward the encapsulated bundle for
any of the reasons listed in Figure 1, then custody any of the reasons listed in Figure 1, then custody
transfer has failed. Custody transfer failure SHALL be transfer has failed. Custody transfer failure SHALL be
handled as follows: handled as follows:
. The BCLA SHALL add the BPDU's transmission ID to the . The BCLA SHALL add the BPDU's transmission ID to the
disposition scope report of a pending outbound disposition scope report of a pending outbound
custody signal, destined for the node that was the custody signal, destined for the node that was the
source of the encapsulating bundle, whose disposition source of the encapsulating bundle, whose disposition
is the reason code from Figure 2 that indicates the is the reason code from Figure 2 that indicates the
skipping to change at page 10, line 4 skipping to change at page 10, line 4
attempted" flag in the encapsulating bundle's status attempted" flag in the encapsulating bundle's status
report request field is set to 1, and status report request field is set to 1, and status
reporting is enabled, a custody transfer status reporting is enabled, a custody transfer status
report whose reason code is the same as the pending report whose reason code is the same as the pending
outbound custody signal's disposition SHOULD be outbound custody signal's disposition SHOULD be
generated, destined for the report-to endpoint of the generated, destined for the report-to endpoint of the
encapsulating bundle. encapsulating bundle.
. If Custody Transfer was NOT requested for this BPDU, or if . If Custody Transfer was NOT requested for this BPDU, or if
Custody Transfer was requested for this BPDU and custody Custody Transfer was requested for this BPDU and custody
transfer succeeded, then the encapsulated bundle SHALL be transfer succeeded, then the encapsulated bundle SHALL be
Internet-Draft Bundle-in-Bundle Encapsulation January 20199
delivered from the convergence layer adapter to the bundle delivered from the convergence layer adapter to the bundle
protocol agent, whereupon bundle reception SHALL be performed protocol agent, whereupon bundle reception SHALL be performed
as defined in section 5.6 of the Bundle Protocol specification as defined in section 5.6 of the Bundle Protocol specification
(a work in progress) as usual: the encapsulated bundle may be (a work in progress) as usual: the encapsulated bundle may be
forwarded, delivered, etc. forwarded, delivered, etc.
Note that the manner in which pending outbound custody signals are Note that the manner in which pending outbound custody signals are
managed, disposition scope reports are aggregated, and custody managed, disposition scope reports are aggregated, and custody
signal transmission is initiated is an implementation matter that signal transmission is initiated is an implementation matter that
is beyond the scope of this specification. Note, however, that is beyond the scope of this specification. Note, however, that
skipping to change at page 11, line 4 skipping to change at page 11, line 4
(destroying the associated retransmission timer, if any). (destroying the associated retransmission timer, if any).
. Otherwise (custody refusal), for each transmission ID in the . Otherwise (custody refusal), for each transmission ID in the
custody signal's disposition scope report: custody signal's disposition scope report:
o The corresponding CTI MUST be removed from the CTDB o The corresponding CTI MUST be removed from the CTDB
(destroying the associated retransmission timer, if any). (destroying the associated retransmission timer, if any).
o Any further action taken by the BCLA is implementation- o Any further action taken by the BCLA is implementation-
specific and may depend on the reason code cited for the specific and may depend on the reason code cited for the
refusal. For example, if the custody signal's reason code refusal. For example, if the custody signal's reason code
was "Depleted storage", the BCLA might choose to notify was "Depleted storage", the BCLA might choose to notify
the bundle protocol agent that custodial transmission of the bundle protocol agent that custodial transmission of
Internet-Draft Bundle-in-Bundle Encapsulation January 20199
the indicated bundle failed. If the reason code was the indicated bundle failed. If the reason code was
"Redundant reception", on the other hand, this might cause "Redundant reception", on the other hand, this might cause
the BCLA simply to instruct the bundle protocol agent to the BCLA simply to instruct the bundle protocol agent to
remove the retention constraint "Custody accepted" on the remove the retention constraint "Custody accepted" on the
bundle referenced by the corresponding CTI and to revise bundle referenced by the corresponding CTI and to revise
its algorithm for computing retransmission time. its algorithm for computing retransmission time.
5. Security Considerations 5. Security Considerations
An adversary on a DTN-based network that can delete bundles could An adversary on a DTN-based network that can delete bundles could
skipping to change at page 11, line 41 skipping to change at page 11, line 44
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
7.2. Informative References 7.2. Informative References
[RFC5050] Scott, M. and S. Burleigh, "Bundle Protocol [RFC5050] Scott, K. and S. Burleigh, "Bundle Protocol
Specification", RFC 5050, November 2007. Specification", RFC 5050, November 2007.
8. Acknowledgments 8. Acknowledgments
This work is freely adapted from [RFC5050], which was an effort of This work is freely adapted from [RFC5050], which was an effort of
the Delay Tolerant Networking Research Group. The following DTNRG the Delay Tolerant Networking Research Group. The following DTNRG
participants contributed significant technical material and/or participants contributed significant technical material and/or
inputs to that document: Dr. Vinton Cerf of Google, Scott Burleigh, inputs to that document: Dr. Vinton Cerf of Google, Scott Burleigh,
Adrian Hooke, and Leigh Torgerson of the Jet Propulsion Laboratory, Adrian Hooke, and Leigh Torgerson of the Jet Propulsion Laboratory,
Internet-Draft Bundle-in-Bundle Encapsulation January 20199
Michael Demmer of the University of California at Berkeley, Robert Michael Demmer of the University of California at Berkeley, Robert
Durst, Keith Scott, and Susan Symington of The MITRE Corporation, Durst, Keith Scott, and Susan Symington of The MITRE Corporation,
Kevin Fall of Carnegie Mellon University, Stephen Farrell of Trinity Kevin Fall of Carnegie Mellon University, Stephen Farrell of Trinity
College Dublin, Peter Lovell of SPARTA, Inc., Manikantan Ramadas of College Dublin, Peter Lovell and Howard Weiss of SPARTA, Inc., and
Ohio University, and Howard Weiss of SPARTA, Inc. Manikantan Ramadas of Ohio University.
The custody transfer procedures defined in this specification are The custody transfer procedures defined in this specification are
adapted from the Aggregate Custody Signals draft specification adapted from the Aggregate Custody Signals draft specification
authored in 2010-2012 by Sebastian Kuzminsky and Andrew Jenkins, authored in 2010-2012 by Sebastian Kuzminsky and Andrew Jenkins,
then of the University of Colorado at Boulder. then of the University of Colorado at Boulder.
Although the BIBE specification diverges in some ways from the Although the BIBE specification diverges in some ways from the
original Bundle-in-Bundle Encapsulation Internet Draft authored by original Bundle-in-Bundle Encapsulation Internet Draft authored by
Susan Symington, Bob Durst, and Keith Scott of The MITRE Corporation Susan Symington, Bob Durst, and Keith Scott of The MITRE Corporation
(draft-irtf-dtnrg-bundle-encapsulation-06, 2009), the influence of (draft-irtf-dtnrg-bundle-encapsulation-06, 2009), the influence of
that earlier document is gratefully acknowledged. that earlier document is gratefully acknowledged.
This document was prepared using 2-Word-v2.0.template.dot. This document was prepared using 2-Word-v2.0.template.dot.
Internet-Draft Bundle-in-Bundle Encapsulation January 20199
Appendix A. For More Information Appendix A. For More Information
Please refer comments to dtn@ietf.org. The Delay Tolerant Networking Please refer comments to dtn@ietf.org. The Delay Tolerant Networking
Research Group (DTNRG) Web site is located at http://www.dtnrg.org. Research Group (DTNRG) Web site is located at http://www.dtnrg.org.
Copyright (c) 2018 IETF Trust and the persons identified as authors Copyright (c) 2019 IETF Trust and the persons identified as authors
of the code. All rights reserved. of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without Redistribution and use in source and binary forms, with or without
modification, is permitted pursuant to, and subject to the license modification, is permitted pursuant to, and subject to the license
terms contained in, the Simplified BSD License set forth in Section terms contained in, the Simplified BSD License set forth in Section
4.c of the IETF Trust's Legal Provisions Relating to IETF Documents 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
Internet-Draft Bundle-in-Bundle Encapsulation January 20199
Appendix B. CDDL expression Appendix B. CDDL expression
For informational purposes, Carsten Bormann has kindly provided an For informational purposes, Carsten Bormann has kindly provided an
expression of the Bundle Protocol specification in the CBOR Data expression of the Bundle Protocol specification in the CBOR Data
Definition Language (CDDL). Portions of CDDL expression that bear Definition Language (CDDL). Portions of CDDL expression that bear
on the custody transfer extension are presented below, somewhat on the custody transfer extension are presented below, somewhat
edited by the authors. Note that wherever the CDDL expression is in edited by the authors. Note that wherever the CDDL expression is in
disagreement with the textual representation of the BP specification disagreement with the textual representation of the BP specification
presented in the earlier sections of this document, the textual presented in the earlier sections of this document, the textual
representation rules. representation rules.
 End of changes. 23 change blocks. 
15 lines changed or deleted 48 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/