[dtn] BPbis consensus status

"Burleigh, Scott C (US 312B)" <scott.c.burleigh@jpl.nasa.gov> Wed, 16 September 2020 19:43 UTC

Return-Path: <scott.c.burleigh@jpl.nasa.gov>
X-Original-To: dtn@ietfa.amsl.com
Delivered-To: dtn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D8693A0BE2 for <dtn@ietfa.amsl.com>; Wed, 16 Sep 2020 12:43:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.162
X-Spam-Level:
X-Spam-Status: No, score=-4.162 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.695, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FROM_GOV_DKIM_AU=-0.448, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=jpl.nasa.gov
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s5Xh57UbJ9jZ for <dtn@ietfa.amsl.com>; Wed, 16 Sep 2020 12:43:36 -0700 (PDT)
Received: from ppa02.jpl.nasa.gov (ppa02.jpl.nasa.gov [128.149.137.113]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0768D3A0BD3 for <dtn@ietf.org>; Wed, 16 Sep 2020 12:43:35 -0700 (PDT)
Received: from pps.filterd (ppa02.jpl.nasa.gov [127.0.0.1]) by ppa02.jpl.nasa.gov (8.16.0.27/8.16.0.27) with SMTP id 08GJeojH070510 for <dtn@ietf.org>; Wed, 16 Sep 2020 12:43:35 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jpl.nasa.gov; h=from : to : subject : date : message-id : content-type : content-transfer-encoding : mime-version; s=InSight1906; bh=HamVeiXrEUSIJ9ZLnA2nWHLFNsP07FtxhGFCu2t4hwk=; b=lOvzgzet7mHNFaxKW3RKf1dS+KFceDigKAa7C9EYzqqAji+RxuhobF+RxF/VQUl3AyNk gwMDjaCXW0k97rCx0b/qbNceW8ZfUvDUEYxXq1EXv8focb+E9i6fqleRgEKWetzSgNzE M+IaaBqtpYsYQwTEK5SDN0mMDXgABoOBsDqaaJn0Y9+OYCE9sENvvnNFKY8LC/rw0pcW nX6BVPxZDppSNJ1kfAFfj+Vtevom8VF51n0NICtspGi+QkzMJtbQAFWkIJtiudrUuNCi APK9XUwXTGPJZC5ZAo8IEocdFREHAGgU0sdoDxVD7zDKRUhQmxWVdh4Vm47kcCHZp2Yg kg==
Received: from mail.jpl.nasa.gov (altphysenclup01.jpl.nasa.gov [128.149.137.52]) by ppa02.jpl.nasa.gov with ESMTP id 33k5nyguc5-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <dtn@ietf.org>; Wed, 16 Sep 2020 12:43:34 -0700
Received: from ap-embx16-sp30.RES.AD.JPL (ap-embx16-sp30.jpl.nasa.gov [128.149.137.85]) by smtp.jpl.nasa.gov (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id 08GJhYBm007545 (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128 bits) verified FAIL) for <dtn@ietf.org>; Wed, 16 Sep 2020 12:43:34 -0700
Received: from ap-embx16-sp10.RES.AD.JPL (2002:8095:8953::8095:8953) by ap-embx16-sp30.RES.AD.JPL (2002:8095:8955::8095:8955) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1979.3; Wed, 16 Sep 2020 12:43:33 -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.1979.003; Wed, 16 Sep 2020 12:43:33 -0700
From: "Burleigh, Scott C (US 312B)" <scott.c.burleigh@jpl.nasa.gov>
To: "dtn@ietf.org" <dtn@ietf.org>
Thread-Topic: BPbis consensus status
Thread-Index: AdaMYT/t9udv/yXoSOqh+8IsTyeHog==
Date: Wed, 16 Sep 2020 19:43:33 +0000
Message-ID: <34a7886b09d946faa816acbd26700d65@jpl.nasa.gov>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [207.151.104.72]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Source-IP: ap-embx16-sp30.jpl.nasa.gov [128.149.137.85]
X-Source-Sender: scott.c.burleigh@jpl.nasa.gov
X-AUTH: Authorized
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-09-16_12:2020-09-16, 2020-09-16 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=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-2006250000 definitions=main-2009160140
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/A-kdmYHPteLFucXOA3hNGkCJOWI>
Subject: [dtn] BPbis consensus status
X-BeenThere: dtn@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Delay Tolerant Networking \(DTN\) discussion list at the IETF." <dtn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtn>, <mailto:dtn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtn/>
List-Post: <mailto:dtn@ietf.org>
List-Help: <mailto:dtn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtn>, <mailto:dtn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Sep 2020 19:43:38 -0000

Hi.  As best I can work out from the last eight weeks of emails, here is the status of the remaining open questions on the BPbis draft.

1.	Should the BPbis specification mandate implementation of the BPSec security extensions?
	a.	On July 27, Marc Blanchet strongly opposes this mandate.
	b.	On July 28, Brian Sipos supports the mandate in a limited way: when bundle-level security is needed, that security must be provided by BPSec rather than by some other mechanism.  [This language now appears in section 9 of version 26 of the BPbis Internet Draft.]
	c.	On July 28, Ronny Bull agrees with Brian.
	d.	On July 28, Mehmet Adalier agrees with Brian.
	e.	On July 28, Ed Birrane agrees with Brian.
	f.	On July 29, Ran Atkinson supports the mandate in a more expansive way: implementation of BPSec is mandatory for any Bundle Protocol Agent that sources, verifies, and/or accepts a bundle.  A BPA that only forwards bundles (without verifying them) need not implement BPSec.
	g.	On July 29, Rick Taylor agrees with Ran.
	h.	On July 29, Ed Birrane agrees with Ran.
	i.	On July 29, Ronny Bull agrees with Ran.
	j.	On August 3, Adam Wiethuechter agrees with Brian.
	k.	On September 2, Magnus Westerlund supports the mandate without limitation.

2.	Is the registration policy for Bundle and Block Processing Control flags in sections 10.3 and 10.4 of BPbis version 26 satisfactory?
	a.	To date, no comments from the Working Group.

3.	Does the language in section 5.4 Step 2 of BPbis version 26 satisfactorily address the question of mandating implementation of TCPCL in the BPbis specification?
	a.	To date, no comments from the Working Group.

4.	Does the language in section 4.2.2 and 5.5 of BPbis version 26 satisfactorily address the question of authorizing Bundle Protocol Agents to override the bundle lifetimes asserted by BP applications?
	a.	To date, no comments from the Working Group.

5.	Does the language in section 4.1.5.1.1 of BPbis version 26 satisfactorily address the question of discerning whether or not a given dtn-scheme endpoint ID identifies a singleton endpoint?
	a.	To date, no comments from the Working Group.

6.	Does the language in section 10.6 of BPbis version 26 satisfactorily address the question of limiting the permitted number of different BP URI scheme type codes?
	a.	To date, no comments from the Working Group.

7.	In version 26 of the BPbis specification, all BP time values (e.g., bundle creation time, lifetime, bundle age) are denominated in milliseconds rather than in seconds or microseconds.  Is this satisfactory?
	a.	On July 28, Carsten Bormann notes that the CBOR representation of time values could utilize tags to reduce transmission bandwidth consumption.
	b.	On July 29, Jeremy Mayer endorses Carsten's idea: times may be denominated in seconds (tag 1) or at other granularity (tag 1001).
	c.	On July 29, Ed Birrane warns that this concept introduces the possibility of time values changing in transit, violating the immutability of primary blocks.
	d.	On July 29, Rick Taylor, Scott Burleigh, Ed Birrane, and Ran Atkinson discuss the question of what is really meant by the immutability of the primary block: semantic immutability or syntactic immutability?
	e.	On August 3, Adam Wiethuechter agrees with Ran that both semantic immutability and syntactic immutability are required.  He believes that denominating all DTN times in milliseconds is a good resolution.
	f.	On August 4, Lloyd Wood explains immutability.

8.	Does the language in section 4.3 of BPbis version 26 satisfactorily address the question of whether implementation of all extension blocks defined in the BPbis specification is mandatory or conditional?
	a.	To date, no comments from the Working Group.

Scott