[dtn] Re: Private use/unassigned URI schemes?
"Sipos, Brian J." <Brian.Sipos@jhuapl.edu> Fri, 11 October 2024 13:01 UTC
Return-Path: <Brian.Sipos@jhuapl.edu>
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 42BA2C1D5307 for <dtn@ietfa.amsl.com>; Fri, 11 Oct 2024 06:01:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=jhuapl.edu
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0QJU0mWcYn7V for <dtn@ietfa.amsl.com>; Fri, 11 Oct 2024 06:01:03 -0700 (PDT)
Received: from aplegw02.jhuapl.edu (aplegw02.jhuapl.edu [128.244.251.169]) by ietfa.amsl.com (Postfix) with ESMTP id 560A3C1D61F1 for <dtn@ietf.org>; Fri, 11 Oct 2024 06:01:03 -0700 (PDT)
Received: from pps.filterd (aplegw02.jhuapl.edu [127.0.0.1]) by aplegw02.jhuapl.edu (8.18.1.2/8.18.1.2) with ESMTP id 49BChWLt003913; Fri, 11 Oct 2024 09:01:02 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jhuapl.edu; h=content-type : date : from : in-reply-to : message-id : mime-version : references : subject : to; s=JHUAPLDec2018; bh=/J1a4NhezMc1q2wNEjMB9/efQiYHw9PRZVhvCr1AvVY=; b=AMt9Ck/63U8HpMQbsmkqBIOaAx6f6rt8SuWLRbGEI5lwr+mS1DCPGgeE0X6jpybUUV7j jzMJhl9wwlWv9GCrHwaW+gmOVeklBBXW1A8k7wbrDwMqTT09eHe7WroHUbhad5fFD8a7 l1oe12kV+gKew+zdwMTVIhYQUbRMk2bqIGK8YQv0hUb4m174hjgWit2krX8TSInMQ7MV YvJSIChCzI+UHa8Tn2IyUI94ceQy2SvBWnfuX9BhgRzV7UGTEMkSWCrMJHDNiUzzYIlM Kq6zmCRNfhDk/dOGu4Z4eNicu1qsv641hWjfp4F+3+ScuzWiwRMNUjWoG27ElOJM8tZs dQ==
Received: from aplex29.dom1.jhuapl.edu (aplex29.dom1.jhuapl.edu [10.114.162.14]) by aplegw02.jhuapl.edu (PPS) with ESMTPS id 4231nypr01-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 11 Oct 2024 09:01:02 -0400
Received: from APLEX21.dom1.jhuapl.edu (10.114.162.6) by APLEX29.dom1.jhuapl.edu (10.114.162.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Fri, 11 Oct 2024 09:01:01 -0400
Received: from APLEX21.dom1.jhuapl.edu ([fe80::20d7:9545:f01e:9b2]) by APLEX21.dom1.jhuapl.edu ([fe80::20d7:9545:f01e:9b2%5]) with mapi id 15.02.1544.011; Fri, 11 Oct 2024 09:01:01 -0400
From: "Sipos, Brian J." <Brian.Sipos@jhuapl.edu>
To: Rick Taylor <rick@tropicalstormsoftware.com>, "Huff, John" <jh571912@ohio.edu>, "dtn@ietf.org" <dtn@ietf.org>
Thread-Topic: Private use/unassigned URI schemes?
Thread-Index: AQHbGprlEju/mWyiYkKhTizHbrsk2bJ/8YcwgAAIXNCAAAcaEIABgoIw
Date: Fri, 11 Oct 2024 13:01:01 +0000
Message-ID: <4d02d86b6f60409d924f2eb97e30712a@jhuapl.edu>
References: <MN0PR01MB76824D0A8F35D230073605F0AA7F2@MN0PR01MB7682.prod.exchangelabs.com> <049145456b764007b3b1297e538f2be4@jhuapl.edu> <38A5475DE83986499AEACD2CFAFC3F9802ADDD4A66@tss-server1.home.tropicalstormsoftware.com> <38A5475DE83986499AEACD2CFAFC3F9802ADDD4A81@tss-server1.home.tropicalstormsoftware.com>
In-Reply-To: <38A5475DE83986499AEACD2CFAFC3F9802ADDD4A81@tss-server1.home.tropicalstormsoftware.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.162.18]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="SHA1"; boundary="----=_NextPart_000_0219_01DB1BBC.175A7F50"
MIME-Version: 1.0
X-CrossPremisesHeadersFilteredBySendConnector: APLEX29.dom1.jhuapl.edu
X-OrganizationHeadersPreserved: APLEX29.dom1.jhuapl.edu
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1051,Hydra:6.0.680,FMLib:17.12.62.30 definitions=2024-10-11_10,2024-10-11_01,2024-09-30_01
Message-ID-Hash: 7SJNGXE42ZBQQHMOHUMS4UGFWZJNW6XA
X-Message-ID-Hash: 7SJNGXE42ZBQQHMOHUMS4UGFWZJNW6XA
X-MailFrom: Brian.Sipos@jhuapl.edu
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dtn.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc5
Precedence: list
Subject: [dtn] Re: Private use/unassigned URI schemes?
List-Id: "Delay Tolerant Networking (DTN) discussion list at the IETF." <dtn.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/Oy4gTrwVLFaYX-eQMHMf6JPa2Ow>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtn>
List-Help: <mailto:dtn-request@ietf.org?subject=help>
List-Owner: <mailto:dtn-owner@ietf.org>
List-Post: <mailto:dtn@ietf.org>
List-Subscribe: <mailto:dtn-join@ietf.org>
List-Unsubscribe: <mailto:dtn-leave@ietf.org>
Rick,
It's really great to hear about robustness in your BPA, which to me is part
of interoperability and well-behaved-ness in a heterogeneous network. This
seems like more of a BPA-behavior BCP wishlist than an errata on RFC 9171.
Is there any place that is used to keep track of these kinds of things? I
don't want to start a draft but if there was a repo issue tracker somewhere
to take notes in...?
Regarding the IMC scheme I had started writing something up as a companion
to the BP SAND (advertisement/discovery) draft but think that this might be
superseded by an upcoming CCSDS experimental ("orange book") publication
about existing IMC implementations. Unfortunately I think there may be some
gap between what has been experimented with and what makes sense in a
universal deployment similarly to the IPN scheme updates to create an IPN
allocator identifier registry. I would hate to have the same amount of churn
with an IMC scheme as there was/is with IPN scheme. That is a separate
discussion though.
From: Rick Taylor <rick@tropicalstormsoftware.com>
Sent: Thursday, October 10, 2024 9:57 AM
To: Rick Taylor <rick@tropicalstormsoftware.com>; Sipos, Brian J.
<Brian.Sipos@jhuapl.edu>; Huff, John <jh571912@ohio.edu>; dtn@ietf.org
Subject: [EXT] RE: Private use/unassigned URI schemes?
APL external email warning: Verify sender rick@tropicalstormsoftware.com
<mailto:rick@tropicalstormsoftware.com> before clicking links or
attachments
Sorry for the top-post.
As a quick aside, the relevant text in Section 4.2.5.1 of RFC9171 uses
lowercase 'must' and 'may' which have no special meaning as per RFC8174.
I read that section as: "Please add new schemes to the IANA registry because
it's really helpful" ("imc" hint hint)
I can find no normative text about not processing bundles with unrecognised
EIDs, and so I understand the requirement is to process them as best one
can, and I think this is the correct behaviour.
Cheers,
Rick
From: Rick Taylor [mailto:rick@tropicalstormsoftware.com]
Sent: 10 October 2024 14:45
To: Sipos, Brian J.; Huff, John; dtn@ietf.org <mailto:dtn@ietf.org>
Subject: [dtn] Re: Private use/unassigned URI schemes?
John, Brian,
Not all implementations. ;)
For what it's worth our implementation will attempt to parse unrecognised
EIDs, and given some sensible validity checks (such as less than 16 levels
of nested CBOR in the scheme-specific part), will then attempt to forward
the bundle.
Given our forwarding lookup is based on the eid-pattern's draft, it is
entirely possible to add a default route, or an 'unknown EID scheme X'
route, to the FIB, and then processing just happens. FIB actions can
include 'forward to X', drop, send status code, store, etc.
This allows some quite smart behaviours, including:
* Drop the bundle silently if you don't recognise the EID scheme
(black hole).
* Forward some unrecognised schemes to a next hop you believe might be
able to handle them (proxy gateway).
* At least try to send a status report if you want. Of course in this
case if the report-to is also an unspecified EID, the same rules are applied
to the status report bundle destination (filter reject).
* Store it for some extended period, for when you roll out the next
version of the BPA that understand the scheme, which it will then pick up
and forward correctly (in-band upgrade).
This is one of the reasons I am a huge fan of the eid-pattern draft, and why
both Erik Kline and I keep muttering about having a formal definition of a
BPA FIB and its responsibilities.
Also, it would be great if someone could write up "imc", or perhaps point to
a descriptive document?
Cheers,
Rick
From: Sipos, Brian J. [mailto:Brian.Sipos@jhuapl.edu]
Sent: 10 October 2024 14:13
To: Huff, John; dtn@ietf.org <mailto:dtn@ietf.org>
Subject: [dtn] Re: Private use/unassigned URI schemes?
John,
I've brought up this same issue in the past related to interoperability [1],
especially related to secondary EIDs like Report To.
In some hypothetical situation where I put a private-use scheme (or even a
scheme that simply is not directly supported by a BPA) EID as the private
block Report To field. To make the case more simple, none of the bundle or
block flags indicate that we want status reporting so no node will need to
generate reports. Now in this situation, a well-behaving network should
forward this bundle all the way to its proper destination and never care
that a particular EID within the bundle has a scheme that it doesn't
understand/support.
Now for the bad news in my opinion: all of the current major BPAs will
either fail to decode this bundle or will treat the EID as malformed and
intentionally stop processing it (as you have seen). While this may be in a
requirement and conformance gray area, I think this is a terribly important
for actual, realistic interoperability.
That said, what would be a forcing function to steer a "well behaving" BPA
implementation to at least handle unknown-scheme EIDs as well-formed opaque
data. This doesn't mean that the BPA needs to do anything specific (e.g. to
forward an unknown-scheme destination "properly") but it does need to be
able to actually get to the dispatching/forwarding procedures.
As a starting point, at least the current EID Pattern draft [3] recognizes
and allows input and handling of arbitrary unknown-scheme EIDs. This would
in the future allow a BPA to be configured to have a "default forwarding"
decision for a private use scheme, something like "65536:**"
Looking forward to finding an interoperable solution for this,
Brian S.
[1] https://mailarchive.ietf.org/arch/msg/dtn/rLi15ueKQy0ijzDV7DF3tBHknJs/
[2]
https://www.ietf.org/archive/id/draft-sipos-dtn-eid-pattern-03.html#section-
2.3
From: Huff, John <jh571912@ohio.edu <mailto:jh571912@ohio.edu> >
Sent: Wednesday, October 9, 2024 8:07 PM
To: dtn@ietf.org <mailto:dtn@ietf.org>
Subject: [EXT] [dtn] Private use/unassigned URI schemes?
APL external email warning: Verify sender forwardingalgorithm@ietf.org
<mailto:forwardingalgorithm@ietf.org> before clicking links or attachments
In RFC9171 section 4.2.5.1 it says the following:
```
Each scheme that may be used to form a BP endpoint ID must be added to the
"Bundle Protocol URI Schemes Types" registry.
```
Does this mean that an endpoint using a scheme that's not in the registry is
malformed? In practice, the scheme code 3 is commonly used for "imc"
although it has not yet been added to the registry.
How should a node treat bundles containing EIDs that use schemes that it
doesn't implement? Should it do something different if the EID is using a
URI scheme code in the unassigned space vs private use space?
If it is indeed valid to encode a bundle containing an EID with a private
scheme code, what Bundle Status Report Reason Code is used by a forwarding
node that doesn't implement the URI scheme of the destination node? Possible
options are "Destination endpoint ID unavailable", "Block unintelligible",
and "No known route to destination from here".
In ION, if the any of the EIDs in primary block use a scheme code other than
dtn (1), ipn (2), or imc (3), the bundle is considered malformed. Is this
the correct behavior?
-John Huff
- [dtn] Private use/unassigned URI schemes? Huff, John
- [dtn] Re: Private use/unassigned URI schemes? Sipos, Brian J.
- [dtn] Re: Private use/unassigned URI schemes? Rick Taylor
- [dtn] Re: Private use/unassigned URI schemes? Rick Taylor
- [dtn] Re: [External] RE: Private use/unassigned U… Huff, John
- [dtn] Re: Private use/unassigned URI schemes? Sipos, Brian J.
- [dtn] Re: Private use/unassigned URI schemes? Rick Taylor
- [dtn] Re: Private use/unassigned URI schemes? Ran Atkinson
- [dtn] Re: Private use/unassigned URI schemes? Sipos, Brian J.
- [dtn] Re: Private use/unassigned URI schemes? Sipos, Brian J.
- [dtn] Re: Private use/unassigned URI schemes? Rick Taylor
- [dtn] Re: Private use/unassigned URI schemes? Sipos, Brian J.
- [dtn] Re: Private use/unassigned URI schemes? Rick Taylor
- [dtn] Re: Private use/unassigned URI schemes? Sipos, Brian J.
- [dtn] Re: Private use/unassigned URI schemes? Ran Atkinson
- [dtn] Re: Private use/unassigned URI schemes? Carsten Bormann
- [dtn] Re: Private use/unassigned URI schemes? Rick Taylor
- [dtn] Re: Private use/unassigned URI schemes? sburleig.sb