[dtn] Re: Private use/unassigned URI schemes?
sburleig.sb@gmail.com Fri, 11 October 2024 10:34 UTC
Return-Path: <sburleig.sb@gmail.com>
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 497C8C14F6A2 for <dtn@ietfa.amsl.com>; Fri, 11 Oct 2024 03:34:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 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, FREEMAIL_FROM=0.001, 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=gmail.com
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 YMfXM75eXkOa for <dtn@ietfa.amsl.com>; Fri, 11 Oct 2024 03:34:29 -0700 (PDT)
Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39102C14F681 for <dtn@ietf.org>; Fri, 11 Oct 2024 03:34:29 -0700 (PDT)
Received: by mail-qt1-x82b.google.com with SMTP id d75a77b69052e-4603f47b2c8so20335701cf.1 for <dtn@ietf.org>; Fri, 11 Oct 2024 03:34:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1728642868; x=1729247668; darn=ietf.org; h=content-language:thread-index:mime-version:message-id:date:subject :in-reply-to:references:to:from:from:to:cc:subject:date:message-id :reply-to; bh=+NEnJBmox5/ukSvrL+VRj7gglFtcRepzJS4ptm/McXs=; b=aW6ZkNgR89OGByOcY6Q+pZ2iw4XlIWOjySX97Qzy54oyda0qaSGrVH1rJcImm3ciXk QbS22CG7U5EUlJgeiL3xqO8yhSIOlsu0+g5W09W48LA7EgiHLMYdbgDlmYN8aeY1fSQG Uv6/BnGU9YYpksyB9qfBGSE11cTzj+lJRZcty2n8k/1DbIBtnA++VpYlyYciTl6G16UT G2Ndm35cq7tHor5GRLMhAjZxE0mymR0LAoPzwDM2uPVmC1KEM/j2Y9JqQtGcPRugVyeY wnzobEKpGCqVZh5fcG7W5DdHCCURge3CWznPBIV7K+6+Il4EyPj1cQIezVOQqk+QA9ZJ coJA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728642868; x=1729247668; h=content-language:thread-index:mime-version:message-id:date:subject :in-reply-to:references:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=+NEnJBmox5/ukSvrL+VRj7gglFtcRepzJS4ptm/McXs=; b=S8HesrJaVVyUI+NYDe1R+ekRdFHpqUMbJ9AUyUG6iZzXCyMTPp8I/nvlHkWs3aROGm JUxM+6ruKec4yBRe4GAC8AlN0Uwu0QBu7AuRzPphM4RQAr5QiddK6sCTs2tMIE2Z0u3R U6wuWtjk/xGw7GcuCalfxl1GzwmgLXppb1YPBSTfNbPzPenibC8UHlATYZMaih10yRVo 6XQGIxd1Mn4pdhb2xq/3CtdiE4TN+/rMx0M1OxlZfHYzoCA4dra6WaGeCpbXz4+VYog0 DnbT7Bhi9nsx9OogWdC8aAGDIG83nRj5JVG+sZkmk+GmyF67URefPKmDOnuSI/cKcLL0 0nzw==
X-Forwarded-Encrypted: i=1; AJvYcCV4si2D05OkxN/YJ8cvm5+zyWbiMlmDEGG5YryWls+VodOAtbozimM3oH+56drwlkVGVwg=@ietf.org
X-Gm-Message-State: AOJu0Yy5Irdx+3K5UKlM1YZF9tOjiL7c/SvDKWOeHq/lI5RuJNg+v1yD ljuMp64qMUinnNGTQz+Rep9KsGI0C/4sFWClXcXa1HedMAQkkEx4
X-Google-Smtp-Source: AGHT+IEGzkskNA8Kxc3Lvtkhjvn12C3g53tg96zrOlNJIFiBl7OU0Mhh3ehH7ZpqCniwJuWQJrvJrw==
X-Received: by 2002:a05:622a:15c4:b0:458:4bf3:7c5e with SMTP id d75a77b69052e-4604bc82905mr26925961cf.49.1728642867735; Fri, 11 Oct 2024 03:34:27 -0700 (PDT)
Received: from Dorothy ([2603:7080:d3f:b300:a089:4056:6dcf:846d]) by smtp.gmail.com with ESMTPSA id 6a1803df08f44-6cbe85a5d54sm14129956d6.22.2024.10.11.03.34.26 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 11 Oct 2024 03:34:27 -0700 (PDT)
From: sburleig.sb@gmail.com
To: 'Rick Taylor' <rick@tropicalstormsoftware.com>, "'Sipos, Brian J.'" <Brian.Sipos@jhuapl.edu>, "'Huff, John'" <jh571912@ohio.edu>, dtn@ietf.org
References: <MN0PR01MB76824D0A8F35D230073605F0AA7F2@MN0PR01MB7682.prod.exchangelabs.com> <049145456b764007b3b1297e538f2be4@jhuapl.edu> <38A5475DE83986499AEACD2CFAFC3F9802ADDD4A66@tss-server1.home.tropicalstormsoftware.com>
In-Reply-To: <38A5475DE83986499AEACD2CFAFC3F9802ADDD4A66@tss-server1.home.tropicalstormsoftware.com>
Date: Fri, 11 Oct 2024 06:34:23 -0400
Message-ID: <078301db1bc9$2417fd50$6c47f7f0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0784_01DB1BA7.9D08A740"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQKevVUnw0WfOGjI4YuFIxh5oinUgAJflWUdARo2L/6w3kW7kA==
Content-Language: en-us
Message-ID-Hash: ZMTL2QKI6XRCZDNASODDY7AJ2OC3LTWZ
X-Message-ID-Hash: ZMTL2QKI6XRCZDNASODDY7AJ2OC3LTWZ
X-MailFrom: sburleig.sb@gmail.com
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/pMHhzCxrRrKlI9_JCdw9Ll1p5do>
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>
Hi, Rick. The original writeup for "imc" was in https://datatracker.ietf.org/doc/draft-burleigh-dtnrg-imc/, but the multicast procedures described in that draft are no long the state of the art. Bundle multicast in ION has since then been improved along the lines of https://ieeexplore.ieee.org/document/8863857. Scott From: Rick Taylor <rick@tropicalstormsoftware.com> Sent: Thursday, October 10, 2024 9:45 AM To: Sipos, Brian J. <Brian.Sipos@jhuapl.edu>; Huff, John <jh571912@ohio.edu>; 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