[dtn] draft-ietf-dtn-bpbis-25: ABNF "dtn" URI scheme

Alvar Penning <post@0x21.biz> Fri, 29 May 2020 12:58 UTC

Return-Path: <post@0x21.biz>
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 A95133A0820 for <dtn@ietfa.amsl.com>; Fri, 29 May 2020 05:58:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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 (1024-bit key) header.d=0x21.biz
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 Ealhe8j69HCx for <dtn@ietfa.amsl.com>; Fri, 29 May 2020 05:58:35 -0700 (PDT)
Received: from sadachbia.lurk.space (sadachbia.lurk.space [IPv6:2a03:4000:6:d293::2]) (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 5B4A33A081F for <dtn@ietf.org>; Fri, 29 May 2020 05:58:35 -0700 (PDT)
Date: Fri, 29 May 2020 14:58:26 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=0x21.biz; s=mail; t=1590757112; bh=jzu7ObCd1jPiEBuf2sNbfRhDSUBOfP6SCe9mexPNAT4=; h=Date:From:To:Subject; b=QnDxQQg+j9DgEs8zbxSUFbOFXg1ppcQUFAWFne5G5JpICJRf+R3+UfWVlSNBIdQ+N 0FPiKDSPnHKjl4wQLsJr60WaWeYz3CfUdEWBRAw3PEn9TJ5pfeTxEfztrdiM2M8Ilo rwayUoQ3GVJwqg6ieW68Sbc6C5fZwg8+DXJM0wZI=
From: Alvar Penning <post@0x21.biz>
To: dtn@ietf.org
Message-ID: <20200529145826.74fa3a09.post@0x21.biz>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/12-NZl8tF3Xu_QUruWGzWMZM2LI>
Subject: [dtn] draft-ietf-dtn-bpbis-25: ABNF "dtn" URI scheme
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: Fri, 29 May 2020 12:58:37 -0000

Dear all,

thanks for releasing the 25th draft of the Bundle Protocol. As I read
the changes, I found the Augmented Backus-Naur Form of the URI schemas
quite useful. However, I have a question about this.

In section 4.1.5.1.1[0] a straight forward ABNF is defined for the
"dtn" URI scheme:

> dtn-uri = "dtn:" dtn-hier-part
> dtn-hier-part = "//" node-name name-delim demux ; a path-rootless
> node-name = 1*VCHAR
> name-delim = "/"
> demux = *VCHAR

Some `dtn-uri` is defined as the concatenation[1] of "dtn:" and a
`dtn-hier-part`. A `dtn-hier-part` starts with two leading slashes
("//") and one slash ("/", `name-delim`) follows a nonempty
`node-name`. Various characters might follow. The line ends with a
comment[2].

Thus, some "dtn" URI has at least the following form: "dtn://NODE-NAME/"

The following paragraph within this section defines the null endpoint as
"dtn:none". However, as far as I understand this does not fit the ABNF
defined above.

If I am not wrong on this, I would like to suggest a new rule for the
"none" `dtn-hier-part`. This could look like the following:

> dtn-hier-part =  "none" 
> dtn-hier-part =/ "//" node-name name-delim demux

Otherwise, the null endpoint could be renamed to "dtn://none/" to match
the current ABNF. Note, a node named "none" and the null endpoint may
get mixed up.

I would be pleased about comments in this regard.

Best regards,
Alvar


[0]:https://tools.ietf.org/html/draft-ietf-dtn-bpbis-25#section-4.1.5.1.1
[1]:https://tools.ietf.org/html/rfc5234#section-3.1
[2]:https://tools.ietf.org/html/rfc5234#section-3.9