Re: [dtn] I-D Action: draft-ietf-dtn-bpbis-15.txt

"Burleigh, Scott C (US 312B)" <> Mon, 21 October 2019 22:03 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8AFF0120A34 for <>; Mon, 21 Oct 2019 15:03:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id pBZQ4D1hg5Hl for <>; Mon, 21 Oct 2019 15:03:43 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id F0C681209F9 for <>; Mon, 21 Oct 2019 15:03:41 -0700 (PDT)
Received: from pps.filterd ( []) by ( with SMTP id x9LM0IoE006546; Mon, 21 Oct 2019 15:03:41 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; h=from : to : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=InSight1906; bh=tv72isM+/O712X5dvC9Lf0Ce6TSiu5+5kfORRugBUy0=; b=5gVm6dMjKvBicRwLD3gDezRoiY5JmEwpNDIyIl55Yry8Gco7vWTjvUgejcOJOu9Ht0Xv hgik75AVjuyRdp/X9s/JfQmKmezKTSSVZ4ODSeuiykA40anq91culhzHxuCDhRiw2b1i Nsl1dYUba4n0DatGkNO4ZVg5NioI6pBFJlm3wLcboIxgPaAIz9ziHIit6q21lovYjMQM dSRAdGf/6O+wdgeSbiKwfVVve9ovZn6I0tQt0y3NGf9c13lvRfWyAFkLGslt1GaDr3tn k3XFyWu7P7krUvwsASggqTdDlSEvTyr4kXxluQUde6kKvwPZ73lzQjoGSKsfXCqrVj72 rw==
Received: from ( []) by with ESMTP id 2vr1nuxjq6-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 21 Oct 2019 15:03:41 -0700
Received: from ap-embx16-sp40.RES.AD.JPL ( []) by (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id x9LM3ePb028749 (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128 bits) verified FAIL); Mon, 21 Oct 2019 15:03:40 -0700
Received: from ap-embx16-sp10.RES.AD.JPL (2002:8095:8953::8095:8953) by ap-embx16-sp40.RES.AD.JPL (2002:8095:8956::8095:8956) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Mon, 21 Oct 2019 15:03:40 -0700
Received: from ap-embx16-sp10.RES.AD.JPL ([fe80::4:f430:47b5:767b]) by ap-embx16-sp10.RES.AD.JPL ([fe80::4:f430:47b5:767b%17]) with mapi id 15.01.1591.008; Mon, 21 Oct 2019 15:03:40 -0700
From: "Burleigh, Scott C (US 312B)" <>
To: Brian Sipos <>, "" <>
Thread-Topic: [dtn] I-D Action: draft-ietf-dtn-bpbis-15.txt
Thread-Index: AQHViFhqq70QTsmxuEGH+XOGl+Bb8Kdlo1Tg
Date: Mon, 21 Oct 2019 22:03:40 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_e6b2f6aba5d147f8a5b887181e17b3c6jplnasagov_"
MIME-Version: 1.0
X-Source-IP: []
X-AUTH: Authorized
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-10-21_05:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1908290000 definitions=main-1910210207
Archived-At: <>
Subject: Re: [dtn] I-D Action: draft-ietf-dtn-bpbis-15.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Delay Tolerant Networking \(DTN\) discussion list at the IETF." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 21 Oct 2019 22:03:46 -0000

Thanks, Brian.  How about byte strings?  Could we say that the CRC SHALL be represented as a CBOR byte string of length either 2 or 4, and that the content of each such byte string is to be processed as an integer in network byte order?


From: Brian Sipos <>
Sent: Monday, October 21, 2019 2:42 PM
To:; Burleigh, Scott C (US 312B) <>
Subject: [EXTERNAL] Re: [dtn] I-D Action: draft-ietf-dtn-bpbis-15.txt

The new text leaves me confused about the correct encoding and interpretation of the CRC values themselves. The earlier text said that the values are a "sequence of bytes" representing an integer. The new -15 text says that the values are CBOR integer type but still talks about sequences of bytes.

For some background on my desire for specific requirements here: there are many COTS CBOR encoders today (mostly for higher-level languages, e.g. Python and ECMAScript) which do not allow a fine-grained level of control about how numbers are CBOR-encoded. These COTS encoders don't have an API to tell the encoder to make a non-shortest-length output; so it's not possible to implement the BPv7-CRC-required behavior of:

   ...including the CRC field itself, which for this purpose SHALL be

   temporarily populated with the value zero.
When these encoders see a native integer/number value of zero the output is always the encoded bytestring 0x00. My opinion is that unnecessarily limits environments which BPv7 can be used in (at least when CRC handling is intended). I understand that these may not be expected use environments for BP, so take all of this with a grain of salt.
Brian S.

From: dtn <<>> on behalf of<> <<>>
Sent: Friday, October 18, 2019 17:02
To:<> <<>>
Cc:<> <<>>
Subject: [dtn] I-D Action: draft-ietf-dtn-bpbis-15.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Delay/Disruption Tolerant Networking WG of the IETF.

        Title           : Bundle Protocol Version 7
        Authors         : Scott Burleigh
                          Kevin Fall
                          Edward J. Birrane
        Filename        : draft-ietf-dtn-bpbis-15.txt
        Pages           : 61
        Date            : 2019-10-18

   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.

The IETF datatracker status page for this draft is:

There are also htmlized versions available at:

A diff from the previous version is available at:

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at

Internet-Drafts are also available by anonymous FTP at:

dtn mailing list<>