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: =?utf-8?q?=5Bdtn=5D_Re=3A_Private_use/unassigned_URI_schemes=3F?=
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>

------=_NextPart_000_0219_01DB1BBC.175A7F50
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_021A_01DB1BBC.175A7F50"


------=_NextPart_001_021A_01DB1BBC.175A7F50
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

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


------=_NextPart_001_021A_01DB1BBC.175A7F50
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 15 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle24
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:729429096;
	mso-list-type:hybrid;
	mso-list-template-ids:-1966168714 -1393400574 134807555 134807557 =
134807553 134807555 134807557 134807553 134807555 134807557;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US =
link=3D"#0563C1" vlink=3D"#954F72" style=3D'word-wrap:break-word'><div =
class=3DWordSection1><p class=3DMsoNormal>Rick,<o:p></o:p></p><p =
class=3DMsoNormal>It&#8217;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&#8217;t want to start a draft =
but if there was a repo issue tracker somewhere to take notes =
in...?<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>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 (&#8220;orange book&#8221;) 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.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #E1E1E1 =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b>From:</b> Rick =
Taylor &lt;rick@tropicalstormsoftware.com&gt; <br><b>Sent:</b> Thursday, =
October 10, 2024 9:57 AM<br><b>To:</b> Rick Taylor =
&lt;rick@tropicalstormsoftware.com&gt;; Sipos, Brian J. =
&lt;Brian.Sipos@jhuapl.edu&gt;; Huff, John &lt;jh571912@ohio.edu&gt;; =
dtn@ietf.org<br><b>Subject:</b> [EXT] RE: Private use/unassigned URI =
schemes?<o:p></o:p></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div =
id=3DAPLWarningText><table class=3DMsoNormalTable border=3D0 =
cellspacing=3D0 cellpadding=3D0 align=3Dleft><tr><td width=3D"100%" =
style=3D'width:100.0%;background:#E0E0E0;padding:0in 0in 0in 0in'><p =
class=3DMsoNormal =
style=3D'mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wr=
ap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizo=
ntal:column;mso-height-rule:exactly'><b><span style=3D'color:red'>APL =
external email warning: </span></b><span style=3D'color:black'>Verify =
sender <a =
href=3D"mailto:rick@tropicalstormsoftware.com">rick@tropicalstormsoftware=
.com</a> before clicking links or =
attachments</span><o:p></o:p></p></td></tr></table><p><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><span lang=3DEN-GB style=3D'color:#1F497D'>Sorry for =
the top-post.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-GB style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB style=3D'color:#1F497D'>As a quick =
aside, the relevant text in Section 4.2.5.1 of RFC9171 uses lowercase =
&#8216;must&#8217; and &#8216;may&#8217; which have no special meaning =
as per RFC8174.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-GB style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB style=3D'color:#1F497D'>I read that =
section as: &#8220;Please add new schemes to the IANA registry because =
it&#8217;s really helpful&#8221; (&#8220;imc&#8221; hint =
hint)<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB style=3D'color:#1F497D'>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.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'>Cheers,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'>Rick<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma",sans-serif'>From:</span></=
b><span style=3D'font-size:10.0pt;font-family:"Tahoma",sans-serif'> Rick =
Taylor [<a =
href=3D"mailto:rick@tropicalstormsoftware.com">mailto:rick@tropicalstorms=
oftware.com</a>] <br><b>Sent:</b> 10 October 2024 14:45<br><b>To:</b> =
Sipos, Brian J.; Huff, John; <a =
href=3D"mailto:dtn@ietf.org">dtn@ietf.org</a><br><b>Subject:</b> [dtn] =
Re: Private use/unassigned URI =
schemes?<o:p></o:p></span></p></div></div><p class=3DMsoNormal><span =
lang=3DEN-GB><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-GB style=3D'color:#1F497D'>John, =
Brian,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB style=3D'color:#1F497D'>Not all =
implementations&#8230; ;)<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB style=3D'color:#1F497D'>For what =
it&#8217;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.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-GB style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB style=3D'color:#1F497D'>Given our =
forwarding lookup is based on the eid-pattern&#8217;s draft, it is =
entirely possible to add a default route, or an &#8216;unknown EID =
scheme X&#8217; route, to the FIB, and then processing just =
happens.&nbsp; FIB actions can include &#8216;forward to X&#8217;, drop, =
send status code, store, etc.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB style=3D'color:#1F497D'>This allows =
some quite smart behaviours, including:<o:p></o:p></span></p><ul =
style=3D'margin-top:0in' type=3Ddisc><li class=3DMsoListParagraph =
style=3D'color:#1F497D;margin-left:0in;mso-list:l0 level1 lfo2'><span =
lang=3DEN-GB>Drop the bundle silently if you don&#8217;t recognise the =
EID scheme (black hole).<o:p></o:p></span></li><li =
class=3DMsoListParagraph =
style=3D'color:#1F497D;margin-left:0in;mso-list:l0 level1 lfo2'><span =
lang=3DEN-GB>Forward some unrecognised schemes to a next hop you believe =
might be able to handle them (proxy gateway).<o:p></o:p></span></li><li =
class=3DMsoListParagraph =
style=3D'color:#1F497D;margin-left:0in;mso-list:l0 level1 lfo2'><span =
lang=3DEN-GB>At least try to send a status report if you want.&nbsp; 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).<o:p></o:p></span></li><li class=3DMsoListParagraph =
style=3D'color:#1F497D;margin-bottom:12.0pt;margin-left:0in;mso-list:l0 =
level1 lfo2'><span lang=3DEN-GB>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).<o:p></o:p></span></li></ul><p class=3DMsoNormal><span =
lang=3DEN-GB style=3D'color:#1F497D'>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.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-GB style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB style=3D'color:#1F497D'>Also, it =
would be great if someone could write up &#8220;imc&#8221;, or perhaps =
point to a descriptive document?<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'>Cheers,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'>Rick<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma",sans-serif'>From:</span></=
b><span style=3D'font-size:10.0pt;font-family:"Tahoma",sans-serif'> =
Sipos, Brian J. [<a =
href=3D"mailto:Brian.Sipos@jhuapl.edu">mailto:Brian.Sipos@jhuapl.edu</a>]=
 <br><b>Sent:</b> 10 October 2024 14:13<br><b>To:</b> Huff, John; <a =
href=3D"mailto:dtn@ietf.org">dtn@ietf.org</a><br><b>Subject:</b> [dtn] =
Re: Private use/unassigned URI =
schemes?<o:p></o:p></span></p></div></div><p class=3DMsoNormal><span =
lang=3DEN-GB><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal>John,<o:p></o:p></p><p class=3DMsoNormal>I&#8217;ve =
brought up this same issue in the past related to interoperability [1], =
especially related to secondary EIDs like Report To.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>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&#8217;t understand/support.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>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.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>That said, =
what would be a forcing function to steer a &#8220;well behaving&#8221; =
BPA implementation to at least handle unknown-scheme EIDs as well-formed =
opaque data. This doesn&#8217;t mean that the BPA needs to do anything =
specific (e.g. to forward an unknown-scheme destination =
&#8220;properly&#8221;) but it does need to be able to actually get to =
the dispatching/forwarding procedures.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>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 =
&#8220;default forwarding&#8221; decision for a private use scheme, =
something like &#8220;65536:**&#8221;<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Looking =
forward to finding an interoperable solution for this,<o:p></o:p></p><p =
class=3DMsoNormal>Brian S.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>[1] <a =
href=3D"https://mailarchive.ietf.org/arch/msg/dtn/rLi15ueKQy0ijzDV7DF3tBH=
knJs/">https://mailarchive.ietf.org/arch/msg/dtn/rLi15ueKQy0ijzDV7DF3tBHk=
nJs/</a><o:p></o:p></p><p class=3DMsoNormal>[2] <a =
href=3D"https://www.ietf.org/archive/id/draft-sipos-dtn-eid-pattern-03.ht=
ml#section-2.3">https://www.ietf.org/archive/id/draft-sipos-dtn-eid-patte=
rn-03.html#section-2.3</a><o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #E1E1E1 =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b>From:</b> Huff, =
John &lt;<a href=3D"mailto:jh571912@ohio.edu">jh571912@ohio.edu</a>&gt; =
<br><b>Sent:</b> Wednesday, October 9, 2024 8:07 PM<br><b>To:</b> <a =
href=3D"mailto:dtn@ietf.org">dtn@ietf.org</a><br><b>Subject:</b> [EXT] =
[dtn] Private use/unassigned URI schemes?<o:p></o:p></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div =
id=3DAPLWarningText><table class=3DMsoNormalTable border=3D0 =
cellspacing=3D0 cellpadding=3D0 align=3Dleft><tr><td width=3D"100%" =
style=3D'width:100.0%;background:#E0E0E0;padding:0in 0in 0in 0in'><p =
class=3DMsoNormal =
style=3D'mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wr=
ap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizo=
ntal:column;mso-height-rule:exactly'><b><span style=3D'color:red'>APL =
external email warning: </span></b><span style=3D'color:black'>Verify =
sender <a =
href=3D"mailto:forwardingalgorithm@ietf.org">forwardingalgorithm@ietf.org=
</a> before clicking links or =
attachments</span><o:p></o:p></p></td></tr></table><p>&nbsp;<o:p></o:p></=
p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>In RFC9171 section 4.2.5.1 it says the =
following:<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>```<o:p></o:p></p></div><div><p class=3DMsoNormal>Each =
scheme that may be used to form a BP endpoint ID must be added to the =
&quot;Bundle Protocol URI Schemes Types&quot; =
registry.<o:p></o:p></p></div><div><p =
class=3DMsoNormal>```<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>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 &quot;imc&quot; although it has not yet been added to =
the registry.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>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?<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>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 &quot;Destination endpoint ID =
unavailable&quot;, &quot;Block unintelligible&quot;, and &quot;No known =
route to destination from here&quot;.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>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?<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>-John =
Huff<o:p></o:p></p></div></div></div></div></div></div></body></html>
------=_NextPart_001_021A_01DB1BBC.175A7F50--

------=_NextPart_000_0219_01DB1BBC.175A7F50
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIVijCCA9Iw
ggK6oAMCAQICBFWRbZ4wDQYJKoZIhvcNAQELBQAwgYgxCzAJBgNVBAYTAlVTMTwwOgYDVQQKEzNK
b2hucyBIb3BraW5zIFVuaXZlcnNpdHkgQXBwbGllZCBQaHlzaWNzIExhYm9yYXRvcnkxIjAgBgNV
BAsTGUNlcnRpZmljYXRpb24gQXV0aG9yaXRpZXMxFzAVBgNVBAMTDkpIVUFQTCBSb290IENBMB4X
DTE1MDYyOTE1MzkwMloXDTMxMDIyODE2MDkwMlowgYgxCzAJBgNVBAYTAlVTMTwwOgYDVQQKEzNK
b2hucyBIb3BraW5zIFVuaXZlcnNpdHkgQXBwbGllZCBQaHlzaWNzIExhYm9yYXRvcnkxIjAgBgNV
BAsTGUNlcnRpZmljYXRpb24gQXV0aG9yaXRpZXMxFzAVBgNVBAMTDkpIVUFQTCBSb290IENBMIIB
IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvhKkDoyyRvXrtC0TJxEpR1CyTwLFAF2Gz5NN
isky/tGXPWn9cO8MGxECvZywMzFEBIJOjBmQKeMYmK2/Y/qd/fWTt/9HJTRGpDr902+4nWZJnq21
na6qS6J26reRd8BVV+O8i8TVlsuKG8snyQJUugg6D8BJWM8yPJXC9QByonfK7X1ZYCAI2h1OTTxH
RKAytgaV12PfI2AQzsT6RpVoJQqzNvu0VtAeRQ2v64cXHiPoMyrq0wT9Y+bWwD6Tjb7ZEwY1noxo
k0mhdVRH0Z17VpXuGHtBRNUyvKJx1NyztKkvbvqBqhykNn0ZM77cTLnfA6AMAazO7DgT+H1YXflz
CwIDAQABo0IwQDAOBgNVHQ8BAf8EBAMCAQYwDwYDVR0TAQH/BAUwAwEB/zAdBgNVHQ4EFgQU94yZ
iElQRjdbWqkEBy07V3tOp30wDQYJKoZIhvcNAQELBQADggEBABgRzXW4bO7oTGysnxMZqIMvWUid
YoiPqf2ve6sp2S/n+bR4IHVR2mPys/haOP2kixJfKvKkYX1+kl+I4mwhLauwEUMeJSvApesCn/E+
eoFF5BMLL1euszN1MNBXhPS+e4xqaxgrPA7fCacn+i3ayqPcwSZx2AhggH0aiNqTfjANbLImq2os
AWJINJ/gEQt56b8VBdmC3KxEYtUvhHx5wrhi3ulncJ61dwSGi9olhmQtIwsngNB9FcFg3+vG9NlE
xdmQOhChscKTsYSCrVy6tHrsKvT5P4fG4aX+lDuy/kINFMkVn552eQv2j69AwtH57qkMuD7QMFVi
Wsdie1C8yRwwggXLMIIEs6ADAgECAgRVkW3xMA0GCSqGSIb3DQEBCwUAMIGIMQswCQYDVQQGEwJV
UzE8MDoGA1UEChMzSm9obnMgSG9wa2lucyBVbml2ZXJzaXR5IEFwcGxpZWQgUGh5c2ljcyBMYWJv
cmF0b3J5MSIwIAYDVQQLExlDZXJ0aWZpY2F0aW9uIEF1dGhvcml0aWVzMRcwFQYDVQQDEw5KSFVB
UEwgUm9vdCBDQTAeFw0xNTA2MjkxOTMwNTdaFw0zMTAxMjkyMDAwNTdaMIGLMQswCQYDVQQGEwJV
UzE8MDoGA1UEChMzSm9obnMgSG9wa2lucyBVbml2ZXJzaXR5IEFwcGxpZWQgUGh5c2ljcyBMYWJv
cmF0b3J5MSIwIAYDVQQLExlDZXJ0aWZpY2F0aW9uIEF1dGhvcml0aWVzMRowGAYDVQQDExFKSFVB
UEwgSXNzdWluZyBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMDbSDs+bw1I2DXk
lAdB0aGUz7kZNVfRT+b6P98WZogI+HiQur3cwxWnVtSkEQKDq6CHj6ApCzX+p8U78/22fAba7tYi
WFv1JtPRis0AGLe7D4/yb2dImUtEtqiSlTtK4pAz0u+W/BWBa3AoIv3gNJDXT9+KTOHu2rFKDvyN
K7riASgJd+DU6tgK2eFcD0I3esjMvLvOVs2fMm3nYjP3qox+lPFLPFadRWkJE9bceChGhbjC9QDZ
CQMpkJ8pUcqyqsq0aYQioJf/crhwmGuj+4jUILr681TymK190psiapF7FfN8cEZxQPhytpmgVL8w
6+KCG8kdObvyYyG0jY9wEOECAwEAAaOCAjYwggIyMA4GA1UdDwEB/wQEAwIBBjASBgNVHRMBAf8E
CDAGAQH/AgEAMIGXBggrBgEFBQcBAQSBijCBhzBSBggrBgEFBQcwAoZGaHR0cDovL2podWFwbGNy
bC5tYW5hZ2VkLmVudHJ1c3QuY29tL0FJQS9DZXJ0c0lzc3VlZHRvSkhVQVBMUm9vdENBLnA3YzAx
BggrBgEFBQcwAYYlaHR0cDovL2podWFwbG9jc3AubWFuYWdlZC5lbnRydXN0LmNvbTA8BgNVHSAE
NTAzMA8GDWCGSAGG+muBSAMKHgMwDwYNYIZIAYb6a4FIAwoeAjAPBg1ghkgBhvprgUgDCh4BMIHz
BgNVHR8EgeswgegwQKA+oDyGOmh0dHA6Ly9qaHVhcGxjcmwubWFuYWdlZC5lbnRydXN0LmNvbS9D
UkxzL2podWFwbFJvb3RDQS5jcmwwgaOggaCggZ2kgZowgZcxCzAJBgNVBAYTAlVTMTwwOgYDVQQK
EzNKb2hucyBIb3BraW5zIFVuaXZlcnNpdHkgQXBwbGllZCBQaHlzaWNzIExhYm9yYXRvcnkxIjAg
BgNVBAsTGUNlcnRpZmljYXRpb24gQXV0aG9yaXRpZXMxFzAVBgNVBAMTDkpIVUFQTCBSb290IENB
MQ0wCwYDVQQDEwRDUkwxMB8GA1UdIwQYMBaAFPeMmYhJUEY3W1qpBActO1d7Tqd9MB0GA1UdDgQW
BBQigLc8FIxuLUzRCACoiti7VnV1azANBgkqhkiG9w0BAQsFAAOCAQEAjAyN/rFaFM+8N2viJpCl
yKz2CCo9RcZ1avKSJKYAv0RUFqicPoVM3f5KSfD6f2MIa/4htpQCAndQseY4/K7sZd9SgYXjSZrG
6OD3Ij9wCcwEaIxB67xigEkcJIlBTcUYDcNlEQTe2siACKkpVhd9H6/96EtHMzVFfORuupBRi4wr
S6CjS0X16BKJMl9ZSfWg59Zj+UINtzkokI7JZUJTmMJCVIbnHvJ3wkLtrvCKo2gsTYGQJ/0Rd0UW
psFpAwK+L7o9CVorSwV5UL36NY/6IoG8u3mRVvxwZdtKkBQ7ijGa0+GsiaePo0pstMEZNhX9NImZ
Xd1Cp9ViGoVjA5/RwjCCBd4wggTGoAMCAQICBGXjqcQwDQYJKoZIhvcNAQELBQAwgYsxCzAJBgNV
BAYTAlVTMTwwOgYDVQQKEzNKb2hucyBIb3BraW5zIFVuaXZlcnNpdHkgQXBwbGllZCBQaHlzaWNz
IExhYm9yYXRvcnkxIjAgBgNVBAsTGUNlcnRpZmljYXRpb24gQXV0aG9yaXRpZXMxGjAYBgNVBAMT
EUpIVUFQTCBJc3N1aW5nIENBMB4XDTI0MDUyMzE0MjU0M1oXDTI3MDUyMzE0NTU0M1owdDELMAkG
A1UEBhMCVVMxPDA6BgNVBAoTM0pvaG5zIEhvcGtpbnMgVW5pdmVyc2l0eSBBcHBsaWVkIFBoeXNp
Y3MgTGFib3JhdG9yeTEPMA0GA1UECxMGUGVvcGxlMRYwFAYDVQQDEw1CcmlhbiBKIFNpcG9zMIIB
IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApCeBkIZH9nRnFc9egkvb7u3WVlIfq7riuVrp
CacsDfFkv+2I3ByTlf2AY+ai5n2lfsZwwl7l5ugNtIJAVMmx0Vpo1XcFX14GMAWGKBxLwoP+R112
Ys6mS1a9CWlxaYJbUbSp157ZL+oWSJXVB072I43v4MmOa8IwsxO7VH3YjzmoE+iiqa3Ajuj3n6/u
nece9xAa5o7DRb3Y49HoPNXU2FvZAigF3FP6bEF8Z0cL7GTq33s0J2+aUknIN8HkcA1A08M6sjQr
Kr9hmZeE2Rzay1uHCoUJcNSSAmjlSkasitxVCn5nG/l1EM7CtpdJbVpeKrQJphICMXA8idncoM0V
vQIDAQABo4ICXjCCAlowDgYDVR0PAQH/BAQDAgUgMBMGA1UdJQQMMAoGCCsGAQUFBwMEMIGaBggr
BgEFBQcBAQSBjTCBijBVBggrBgEFBQcwAoZJaHR0cDovL2podWFwbGNybC5tYW5hZ2VkLmVudHJ1
c3QuY29tL0FJQS9DZXJ0c0lzc3VlZHRvSkhVQVBMSXNzdWluZ0NBLnA3YzAxBggrBgEFBQcwAYYl
aHR0cDovL2podWFwbG9jc3AubWFuYWdlZC5lbnRydXN0LmNvbTAaBgNVHSAEEzARMA8GDWCGSAGG
+muBSAMKHgIwIQYDVR0RBBowGIEWQnJpYW4uU2lwb3NAamh1YXBsLmVkdTCB+wYDVR0fBIHzMIHw
MEOgQaA/hj1odHRwOi8vamh1YXBsY3JsLm1hbmFnZWQuZW50cnVzdC5jb20vQ1JMcy9KSFVBUExJ
c3N1aW5nQ0EuY3JsMIGooIGloIGipIGfMIGcMQswCQYDVQQGEwJVUzE8MDoGA1UEChMzSm9obnMg
SG9wa2lucyBVbml2ZXJzaXR5IEFwcGxpZWQgUGh5c2ljcyBMYWJvcmF0b3J5MSIwIAYDVQQLExlD
ZXJ0aWZpY2F0aW9uIEF1dGhvcml0aWVzMRowGAYDVQQDExFKSFVBUEwgSXNzdWluZyBDQTEPMA0G
A1UEAxMGQ1JMMTI0MB8GA1UdIwQYMBaAFCKAtzwUjG4tTNEIAKiK2LtWdXVrMB0GA1UdDgQWBBR0
/+uVYbzqy/npA4Z2/u8DIiHNLTAZBgkqhkiG9n0HQQAEDDAKGwRWOC4zAwIEsDANBgkqhkiG9w0B
AQsFAAOCAQEAB4wscC/j9NTARuV2dkR7Aa6/yN/TyEuSXgZPvC9Nk9Cfa/Yb5o/aZlD1yaen0HUk
X4iEEA4BJonX/DgTdyhnaMMFtcucMp5qDguIber9V0iCGZXvFJECQsfgmJ2C4kGjbhYxjeg49zs+
tahhq0Pg5gyHQxgAy8VQlQz1187TpmbEhFJ7x4AifREJ/9WX6aMpnmHpPksOJaJQzqghxE4f1dZO
NMDgQQMYOH7dqfEbqcw+vPB5VfFlOrddzwyco3/0+JH87Sm5Z73K8xOtH7w8Q/pTazNIHg+/JMt6
NMe4EfBX51P6EgMP41/2DW4+D4oEZMvnaiRC4b2f8+G+33bfcTCCBf8wggTnoAMCAQICBFWVtj4w
DQYJKoZIhvcNAQELBQAwgYsxCzAJBgNVBAYTAlVTMTwwOgYDVQQKEzNKb2hucyBIb3BraW5zIFVu
aXZlcnNpdHkgQXBwbGllZCBQaHlzaWNzIExhYm9yYXRvcnkxIjAgBgNVBAsTGUNlcnRpZmljYXRp
b24gQXV0aG9yaXRpZXMxGjAYBgNVBAMTEUpIVUFQTCBJc3N1aW5nIENBMB4XDTIzMDYyOTE4NTEx
NFoXDTI2MDYyOTE5MjExNFowdDELMAkGA1UEBhMCVVMxPDA6BgNVBAoTM0pvaG5zIEhvcGtpbnMg
VW5pdmVyc2l0eSBBcHBsaWVkIFBoeXNpY3MgTGFib3JhdG9yeTEPMA0GA1UECxMGUGVvcGxlMRYw
FAYDVQQDEw1CcmlhbiBKIFNpcG9zMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArA4K
rgGPxXaHeoAgzXcrjbfRca9NMtpzO8uKOiKeQFL+7VHuICkX1Xf+P7s4QE4v3HGL5RQPHZ4lo+G3
f2Ji0/GsS0GHyMjS+CaXkJ2pV/55FyZHOnTfcsniHR13DSPDD8IDQilrRwGeg2fj2K+XfR+rsUdG
RI41rkI8aXzh9fTv1D1ivV95Rf+/HqKnOPyji0yb09md8VIxzaf9BDLXZCrafTQyVWTo0PH8y8K4
XHlp45HtHt+fQ9frjlp47hE8xptmF5QlWwNEKmsgkaG+BLkJ0n4jIox2IK/SOBBpXHCcgGu6LdQo
M/Px6GWgkkcNEE1TTpEweyp131x248BeXwIDAQABo4ICfzCCAnswDgYDVR0PAQH/BAQDAgbAMDQG
A1UdJQQtMCsGCCsGAQUFBwMCBggrBgEFBQcDBAYJKoZIhvcvAQEFBgorBgEEAYI3CgMMMIGaBggr
BgEFBQcBAQSBjTCBijBVBggrBgEFBQcwAoZJaHR0cDovL2podWFwbGNybC5tYW5hZ2VkLmVudHJ1
c3QuY29tL0FJQS9DZXJ0c0lzc3VlZHRvSkhVQVBMSXNzdWluZ0NBLnA3YzAxBggrBgEFBQcwAYYl
aHR0cDovL2podWFwbG9jc3AubWFuYWdlZC5lbnRydXN0LmNvbTAaBgNVHSAEEzARMA8GDWCGSAGG
+muBSAMKHgIwIQYDVR0RBBowGIEWQnJpYW4uU2lwb3NAamh1YXBsLmVkdTCB+wYDVR0fBIHzMIHw
MEOgQaA/hj1odHRwOi8vamh1YXBsY3JsLm1hbmFnZWQuZW50cnVzdC5jb20vQ1JMcy9KSFVBUExJ
c3N1aW5nQ0EuY3JsMIGooIGloIGipIGfMIGcMQswCQYDVQQGEwJVUzE8MDoGA1UEChMzSm9obnMg
SG9wa2lucyBVbml2ZXJzaXR5IEFwcGxpZWQgUGh5c2ljcyBMYWJvcmF0b3J5MSIwIAYDVQQLExlD
ZXJ0aWZpY2F0aW9uIEF1dGhvcml0aWVzMRowGAYDVQQDExFKSFVBUEwgSXNzdWluZyBDQTEPMA0G
A1UEAxMGQ1JMMTExMB8GA1UdIwQYMBaAFCKAtzwUjG4tTNEIAKiK2LtWdXVrMB0GA1UdDgQWBBS5
Ljxj9TG0QDP7ErnyuyCWeOyyQzAZBgkqhkiG9n0HQQAEDDAKGwRWOC4zAwIEsDANBgkqhkiG9w0B
AQsFAAOCAQEAfq3J0TeUoaZ5IUDK2fkiK18pM2Hq1cRY4uRqWS3t+MRBnc51tbnwK0fQSsgJiyO6
uA+1NnqLU25+4WRq9vl1EWOh7ihjivqp3pUGKw7Mb+jsSIoGmxOKqZqDcbS2TNXpfgFRxcwHHPR/
Af5vUEIXPYlqk5bAzSBKkAFH9jeyNAKQWujmfEBGf89CG/pjK/AZ7E0FOtqjDpTdDjEmmM/GfaN5
xlHpMhPvLG7ttFnpViHsZ5ZMFCnYWM9o7KpbK0MOiEPmGvKCDln4dztZ2/Nuc7QLaJJJEeLjwMzE
xBk4xb/hGjOFBZ2aOJnTwrnkfX3BOy38PhOXu6ITH9XyuKkVaDGCA8UwggPBAgEBMIGUMIGLMQsw
CQYDVQQGEwJVUzE8MDoGA1UEChMzSm9obnMgSG9wa2lucyBVbml2ZXJzaXR5IEFwcGxpZWQgUGh5
c2ljcyBMYWJvcmF0b3J5MSIwIAYDVQQLExlDZXJ0aWZpY2F0aW9uIEF1dGhvcml0aWVzMRowGAYD
VQQDExFKSFVBUEwgSXNzdWluZyBDQQIEVZW2PjAJBgUrDgMCGgUAoIICBTAYBgkqhkiG9w0BCQMx
CwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0yNDEwMTExMzAwNTlaMCMGCSqGSIb3DQEJBDEW
BBTr7kaLoLhe8ImGSmbxRZcI87/GuDBUBgkqhkiG9w0BCQ8xRzBFMAsGCWCGSAFlAwQBKjAKBggq
hkiG9w0DBzAOBggqhkiG9w0DAgICAIAwCwYJYIZIAWUCAQEEMA0GCCqGSIb3DQMCAgFAMIGlBgkr
BgEEAYI3EAQxgZcwgZQwgYsxCzAJBgNVBAYTAlVTMTwwOgYDVQQKEzNKb2hucyBIb3BraW5zIFVu
aXZlcnNpdHkgQXBwbGllZCBQaHlzaWNzIExhYm9yYXRvcnkxIjAgBgNVBAsTGUNlcnRpZmljYXRp
b24gQXV0aG9yaXRpZXMxGjAYBgNVBAMTEUpIVUFQTCBJc3N1aW5nIENBAgRl46nEMIGnBgsqhkiG
9w0BCRACCzGBl6CBlDCBizELMAkGA1UEBhMCVVMxPDA6BgNVBAoTM0pvaG5zIEhvcGtpbnMgVW5p
dmVyc2l0eSBBcHBsaWVkIFBoeXNpY3MgTGFib3JhdG9yeTEiMCAGA1UECxMZQ2VydGlmaWNhdGlv
biBBdXRob3JpdGllczEaMBgGA1UEAxMRSkhVQVBMIElzc3VpbmcgQ0ECBGXjqcQwDQYJKoZIhvcN
AQEBBQAEggEAqceYb0ZzLfIkzNF5QwRZt7G7I+pKqizPre6EfMDB+o86Jt20ehWXILHrdelRHh4C
t5C4JPzSLQUTBdgYdAzEHqw1UcckvOicXKKDR9wvP0kMxpL7zLREgxyUifxBhd7meTmAfK4qjShU
1K3Asx1sG8gLa7u8woMc+8Ovztifxym2sLqDhNE1RTLI6GuQgVPzL8SfSrouV0VmxAjDxzC84i1o
qpP2ppNqmuG2OoHMfQ2kjxy3zeAVIO21TPh8Mz//3WVcU+Wdswtow5xDll3gZERKh6OaNJPd3Zdx
kXQeQtNEWJN4G/eSonA706NsX/+ncS3x1FdjARVe4S7OaqTJuQAAAAAAAA==

------=_NextPart_000_0219_01DB1BBC.175A7F50--

