<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.4.12) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-taylor-dtn-imc-scheme-01" category="std" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="imc URI Scheme">The 'imc' URI Scheme for Bundle Protocol Multicast</title>
    <seriesInfo name="Internet-Draft" value="draft-taylor-dtn-imc-scheme-01"/>
    <author fullname="Rick Taylor">
      <organization>Aalyria Technologies</organization>
      <address>
        <email>rtaylor@aalyria.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="16"/>
    <area>Internet</area>
    <workgroup>Delay/Disruption Tolerant Networking</workgroup>
    <keyword>DTN</keyword>
    <keyword>Bundle Protocol</keyword>
    <keyword>BPv7</keyword>
    <keyword>multicast</keyword>
    <keyword>URI scheme</keyword>
    <abstract>
      <?line 54?>

<t>This document defines the 'imc' URI scheme, a concise integer-based scheme
for identifying Bundle Protocol Version 7 (BPv7) endpoints that are not
singleton endpoints, termed multicast endpoints. The structure of 'imc' URIs
mirrors that of the 'ipn' URI scheme: each 'imc' URI comprises an Allocator
Identifier, a Group Number, and a Service Number. In the same way that the
Allocator Identifier and Node Number of an 'ipn' URI identify the node at
which a service exists, the Allocator Identifier and Group Number of an 'imc'
URI identify a group of nodes at which a service exists, and the Service
Number identifies that service. This document specifies the
textual syntax of 'imc' URIs, their interpretation when used as BPv7 Endpoint
Identifiers, their CBOR encoding, and the corresponding EID Pattern, and
requests the associated IANA registrations.</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        The latest revision of this draft can be found at <eref target="https://ricktaylor.github.io/imc-scheme/draft-taylor-dtn-imc-scheme.html"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-taylor-dtn-imc-scheme/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        Delay/Disruption Tolerant Networking Working Group mailing list (<eref target="mailto:dtn@ietf.org"/>),
        which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/dtn/"/>.
        Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/dtn/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/ricktaylor/imc-scheme"/>.</t>
    </note>
  </front>
  <middle>
    <?line 70?>

<section anchor="intro">
      <name>Introduction</name>
      <t>The Bundle Protocol Version 7 (BPv7) <xref target="RFC9171"/> identifies the destination
of every bundle by an Endpoint Identifier (EID), which is a URI. A bundle
endpoint is a set of zero or more bundle nodes, the members of which are
determined by their registrations in it. Although BPv7 permits endpoints with any
number of members, the 'ipn' URI scheme <xref target="RFC9758"/>, the scheme most commonly
used in deployed BPv7 networks, only identifies singleton endpoints. There is
no equivalently concise scheme for identifying endpoints that may have many
members.</t>
      <t>This document defines the 'imc' URI scheme for this purpose. An 'imc' URI
identifies an endpoint that is not a singleton endpoint; such an endpoint is
termed a "multicast endpoint". The name 'imc' is derived from
"InterPlanetary MultiCast", in the same way that 'ipn' was derived from
"InterPlanetary Network", but like 'ipn' the term is now used as a
non-acronymous name.</t>
      <t>The structure of an imc URI mirrors that of an 'ipn' URI, with a Group Number
in place of the 'ipn' Node Number. An 'ipn' URI identifies a service at a
node: its Fully Qualified Node Number identifies the node, and its Service
Number identifies the service at that node. In the same way, an imc URI
identifies a service at a group of nodes: its Fully Qualified Group Number
identifies the group, and its Service Number identifies the service at the
nodes of that group. As throughout BPv7, it is endpoints that are the
destinations of bundles, and nodes are members of endpoints by
registration: each imc URI identifies a single multicast endpoint, whose
members are the nodes of the group that are registered in it.</t>
      <t>The 'imc' scheme was first proposed in <xref target="I-D.burleigh-dtnrg-imc"/> for use
with Compressed Bundle Header Encoding and the experimental Bundle Protocol
version 6, and was subsequently specified for BPv7 as part of the Bundle
Multicast protocol <xref target="I-D.burleigh-dtn-multicast"/>. This document separates the
definition of the 'imc' scheme from that protocol, so that the scheme can be
standardized independently of any particular multicast forwarding mechanism,
and aligns its structure, terminology, and encodings with the 'ipn' URI scheme
as updated by <xref target="RFC9758"/>.</t>
      <t>Like the 'ipn' URI scheme, the 'imc' URI scheme defines identifiers only. An
'imc' URI does not carry any topological information describing how to route
bundles to the members of the identified multicast endpoint. As with the
Fully Qualified Node Number, the structure of an imc URI allows forwarding
mechanisms to base their decisions on the group it identifies, but the
procedures by which bundles destined for multicast endpoints are forwarded,
and by which information about membership is distributed, are out of scope
for this document; one such set of procedures is defined in
<xref target="I-D.burleigh-dtn-multicast"/>.</t>
    </section>
    <section anchor="conventions-and-definitions">
      <name>Conventions and Definitions</name>
      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
      <?line -18?>

<t>For the remainder of this document, the term "imc URI" is used to refer to a
URI that uses the 'imc' URI scheme, and the term "imc EID" is used to refer to
an imc URI that is used as a BPv7 EID.</t>
      <t>The term "multicast endpoint" refers to the BPv7 endpoint identified by an imc
EID. The members of a multicast endpoint are the bundle nodes that have a
registration (<xref section="3.1" sectionFormat="of" target="RFC9171"/>) in that endpoint (<xref target="membership"/>);
a multicast endpoint is therefore not a singleton endpoint
(<xref section="3.1" sectionFormat="of" target="RFC9171"/>).</t>
      <t>The term "Fully Qualified Group Number" (FQGN) refers to the combination of
the Allocator Identifier and the Group Number of an imc URI, by analogy with
the Fully Qualified Node Number (FQNN) of an 'ipn' URI
(<xref section="3.3.1" sectionFormat="of" target="RFC9758"/>).</t>
      <t>The term "group" refers to the set of bundle nodes identified by an FQGN:
the nodes that are members of at least one multicast endpoint whose imc EID
has that FQGN (<xref target="group-numbers"/>). The multicast endpoints whose imc EIDs
share an FQGN are termed the multicast endpoints "of" that group. A group is
not identified by an EID, so it is not itself a BPv7 endpoint and cannot be
the destination of a bundle.</t>
      <t>The terms "Allocator", "Allocator Identifier", "Default Allocator", "Node
Number", and "Service Number" are used as defined in <xref target="RFC9758"/>.</t>
    </section>
    <section anchor="core">
      <name>Core Concepts</name>
      <t>Every imc URI, no matter whether it is expressed with a textual
representation or a binary encoding, <bcp14>MUST</bcp14> be considered as a tuple of the
following three components:</t>
      <ul spacing="normal">
        <li>
          <t>The Allocator Identifier</t>
        </li>
        <li>
          <t>The Group Number</t>
        </li>
        <li>
          <t>The Service Number</t>
        </li>
      </ul>
      <t>The Allocator Identifier indicates the entity responsible for assigning Group
Numbers, maintaining uniqueness whilst avoiding the need for a single registry
for all assigned Group Numbers. See <xref target="allocators"/>.</t>
      <t>The Group Number is a shared identifier assigned to all imc URIs for
services at the nodes of a single group. See <xref target="group-numbers"/>.</t>
      <t>The Service Number is an identifier to distinguish between services at the
nodes of a group. See <xref target="service-numbers"/>.</t>
      <t>The combination of these three components identifies a single multicast
endpoint. Additionally, the combination of the Allocator Identifier and the
Group Number, the FQGN, uniquely identifies the group of nodes at which the
services identified by those imc URIs exist, in the same way that the FQNN of
an 'ipn' URI identifies the node on which a particular resource is expected
to exist. See <xref target="group-numbers"/>.</t>
      <t>Membership of each multicast endpoint is determined by registration
(<xref target="membership"/>), so the multicast endpoints of a group can have different
members, and the nodes of a group are those that are members of any of its
multicast endpoints.</t>
      <section anchor="allocators">
        <name>Allocator Identifiers</name>
        <t>The Allocator Identifier of an imc URI has the same structure, purpose, and
range as the Allocator Identifier of an 'ipn' URI defined in
<xref section="3.2" sectionFormat="of" target="RFC9758"/>, and is drawn from the same "'ipn' Scheme URI
Allocator Identifiers" registry. An Allocator Identifier is an unsigned
integer in the range 0 to 2^32-1.</t>
        <t>An Allocator that has been assigned an Allocator Identifier is authorized to
assign Group Numbers for use with the 'imc' URI scheme, in addition to Node
Numbers for use with the 'ipn' URI scheme. Each Allocator assigns Group
Numbers according to its own policies. Other than ensuring that any Group
Numbers it assigns are unique amongst all Group Numbers it assigns, an
Allocator does not need to coordinate its assignments with other Allocators.</t>
        <t>Group Numbers and Node Numbers are distinct namespaces. An Allocator may
assign the same numeric value as both a Group Number and a Node Number, and
there is no relationship between a group and a node that happen to share the
same Allocator Identifier and number.</t>
        <t>Where the textual representation of an imc URI omits the Allocator
Identifier (<xref target="text"/>), the Group Number has been assigned by the Default
Allocator (<xref section="3.2.2" sectionFormat="of" target="RFC9758"/>). The CBOR representation always
includes the Allocator Identifier (<xref target="cbor-encoding"/>).</t>
        <t>A new IANA registry, "'imc' Scheme URI Default Allocator Group Numbers", is
defined to control the assignment of Group Number values by the Default
Allocator; see <xref target="iana-groups"/>. This registry reserves some values as defined
in <xref target="special-groups"/> below.</t>
        <t>If a system does not require interoperable deployment of 'imc' scheme URIs,
then the Private Use Group Numbers (<xref target="private-groups"/>), reserved by the
Default Allocator for this purpose, are to be used.</t>
      </section>
      <section anchor="group-numbers">
        <name>Group Numbers</name>
        <t>A Group Number identifies a group in the context of an Allocator. A Group
Number is an unsigned integer. A single Group Number assigned by a single
Allocator <bcp14>MUST</bcp14> refer to a single group.</t>
        <t>A group is the set of nodes at which the services identified by imc URIs with
the group's FQGN exist, distinguished by their Service Numbers, in the same
way that an 'ipn' FQNN identifies the node at which the services identified by
its Service Numbers exist. Unlike a node, a group has no fixed membership: its
nodes are those that are members of at least one of its multicast endpoints
(<xref target="membership"/>), and so may change at any time. Assigning a Group Number
does not make any node a member of any multicast endpoint. An Allocator might
assign a Group Number to a community of interest, a mission, or a function,
with the multicast endpoints of the group identifying the services of that
community.</t>
        <t>A group is not an endpoint, and cannot be the destination of a bundle. The
administrative multicast endpoint of a group (<xref target="admin"/>), whose members are
the nodes of that group, can be.</t>
        <t>Because the services of a group exist at a common set of nodes, services
intended for different sets of nodes benefit from being assigned to different
groups, rather than to different Service Numbers of the same group
(<xref target="sec-unauthorized"/>).</t>
        <t>All Group Number assignments, by all Allocators, <bcp14>MUST</bcp14> be in the range 0 to
2^32-1.</t>
        <t>It is <bcp14>RECOMMENDED</bcp14> that Group Number zero (0) not be assigned by an Allocator,
to avoid confusion with the Null imc URI (<xref target="null-imc"/>).</t>
      </section>
      <section anchor="special-groups">
        <name>Special Group Numbers</name>
        <t>Some special-case Group Numbers are defined by the Default Allocator; see
<xref target="iana-groups"/>.</t>
        <section anchor="zero-group">
          <name>The Zero Group Number</name>
          <t>The Default Allocator assigns the use of Group Number zero (0) solely for
identifying the Null imc URI (<xref target="null-imc"/>).</t>
          <t>Any imc URI with a zero (0) Allocator Identifier and a zero (0) Group Number,
but a non-zero Service Number component, is invalid. Such imc URIs <bcp14>MUST NOT</bcp14> be
composed, and processors of such imc URIs <bcp14>MUST</bcp14> consider them as the Null imc
URI.</t>
        </section>
        <section anchor="max-group">
          <name>The Maximum Group Number</name>
          <t>The Default Allocator reserves Group Number 2^32-1 (0xFFFFFFFF) as invalid,
solely to guard against confusion with LocalNode ipn URIs
(<xref section="3.4.2" sectionFormat="of" target="RFC9758"/>), which use the same Node Number: the mistyped
URI imc:4294967295.7, intended as ipn:4294967295.7, then identifies no
multicast endpoint rather than a real one. Any imc URI with a zero (0)
Allocator Identifier and a Group Number of 2^32-1 is invalid, <bcp14>MUST NOT</bcp14> be
composed, and identifies a multicast endpoint that never has any members.
Other Allocators may assign Group Number 2^32-1.</t>
          <t>The 'imc' URI scheme has no equivalent of LocalNode ipn URIs: services
receive the application data units of bundles delivered to them by their
local bundle protocol agent (<xref section="5.7" sectionFormat="of" target="RFC9171"/>), not bundles, so an
imc URI identifying "the local services" would not identify anything to
which a bundle could meaningfully be sent.</t>
        </section>
        <section anchor="private-groups">
          <name>Private Use Group Numbers</name>
          <t>The Default Allocator reserves several ranges of Group Numbers for Private
Use, as defined in <xref target="RFC8126"/>. These ranges are interleaved with ranges of
registered Group Numbers, so that Private Use Group Numbers are available at
each length of CBOR encoding; see <xref target="iana-groups"/>.</t>
          <t>Any imc URI with a zero (0) Allocator Identifier and a Group Number reserved
for Private Use is not guaranteed to be unique beyond a single administrative
domain, defined as the set of nodes that share a unique allocation of Private
Use Group Numbers. The resulting requirements are specified in
<xref target="private-eids"/>.</t>
        </section>
      </section>
      <section anchor="service-numbers">
        <name>Service Numbers</name>
        <t>A Service Number is an unsigned integer that identifies a particular service
operating on a node, as defined in <xref section="3.5" sectionFormat="of" target="RFC9758"/>. In an imc URI,
the Service Number identifies a particular service operating on each node of
a group, and so distinguishes the multicast endpoints of that group.</t>
      </section>
      <section anchor="null-imc">
        <name>The Null imc URI</name>
        <t>There is value in defining a unique imc URI that identifies a multicast
endpoint that can never have any members. This imc URI is termed the "Null
imc URI" and has all three components (the Allocator Identifier, Group
Number, and Service Number) set to the value zero (0). The multicast endpoint
identified by the Null imc URI is termed the "null multicast endpoint". No
node is ever a member of the null multicast endpoint, and any destination
identified by the Null imc URI is therefore by definition unreachable.</t>
        <t>In particular, the Null imc URI <bcp14>MUST NOT</bcp14> be interpreted as identifying a
multicast endpoint of which all nodes, or all nodes supporting the 'imc'
scheme, are implicitly members. See <xref target="sec-implicit"/>.</t>
      </section>
    </section>
    <section anchor="text">
      <name>Textual Representation of imc URIs</name>
      <t>All 'imc' scheme URIs comply with <xref target="RFC3986"/> and are therefore represented
by a scheme identifier and a scheme-specific part. The scheme identifier is
imc, and the scheme-specific parts are represented as a sequence of numeric
components separated with the '.' character. A formal definition is provided
below (see <xref target="text-syntax"/>) and can be informally considered as:</t>
      <artwork><![CDATA[
imc:[<allocator-identifier>.]<group-number>.<service-number>
]]></artwork>
      <t>To keep the text representation concise, the following rules apply:</t>
      <ul spacing="normal">
        <li>
          <t>All leading '0' characters <bcp14>MUST</bcp14> be omitted. A single '0' is valid.</t>
        </li>
        <li>
          <t>If the Allocator Identifier is zero (0), then the
&lt;allocator-identifier&gt; and '.' <bcp14>MAY</bcp14> be omitted.</t>
        </li>
      </ul>
      <t>Examples of the textual representation of imc URIs can be found in
<xref target="text-examples"/>.</t>
      <section anchor="text-syntax">
        <name>'imc' URI Scheme Text Syntax</name>
        <t>The text syntax of an imc URI <bcp14>MUST</bcp14> comply with the following ABNF syntax from
<xref target="RFC5234"/> and repeats the core ABNF syntax rule for DIGIT defined by that
specification:</t>
        <sourcecode type="abnf"><![CDATA[
imc-uri = "imc:" imc-hier-part

imc-hier-part = group-part "." service-number

group-part = [allocator-identifier "."] group-number

allocator-identifier = number

group-number = number

service-number = number

number = "0" / non-zero-number

non-zero-number = (%x31-39 *DIGIT)

DIGIT = %x30-39
]]></sourcecode>
        <t>None of the reserved characters defined in the generic URI syntax are used as
delimiters within URIs of the 'imc' scheme, other than '.'.</t>
        <t>Unlike the 'ipn' URI scheme, the 'imc' URI scheme has no '!' form, because
it has no equivalent of LocalNode ipn URIs; see <xref target="max-group"/>.</t>
      </section>
    </section>
    <section anchor="bpv7">
      <name>Usage of imc URIs with BPv7</name>
      <t>This section identifies the behavior and interpretation of 'imc' scheme URIs
that <bcp14>MUST</bcp14> be followed when using this URI scheme to represent EIDs in BPv7.</t>
      <t>This document does not define the use of imc URIs with the experimental
Bundle Protocol version 6.</t>
      <section anchor="membership">
        <name>Multicast Endpoint Membership</name>
        <t>The members of a multicast endpoint are those bundle nodes that have a
registration (<xref section="3.1" sectionFormat="of" target="RFC9171"/>) in that endpoint. A single bundle
node may be a member of any number of multicast endpoints.</t>
        <t>This document does not define any mechanism by which a node joins or leaves
a multicast endpoint. As for any BPv7 endpoint, the means by which a
registration is created or removed is an implementation matter
(<xref section="3.3" sectionFormat="of" target="RFC9171"/>), and may for example be a local application
interface, configuration, or a separately specified protocol.</t>
        <t>The membership of each multicast endpoint is determined by registration in
that endpoint alone. For example, the members of imc:977000.17.1 and of
imc:977000.17.2 are determined by the registrations in each of those
endpoints, and either may have no members. The nodes of a group are the
members of any of its multicast endpoints, and every node of a group is a
member of the group's administrative multicast endpoint (<xref target="admin"/>).</t>
        <t>As noted in <xref section="3.1" sectionFormat="of" target="RFC9171"/>, registrations are local, and BPv7 does
not include a mechanism for distributing information about registrations.
Mechanisms by which information about the membership of multicast endpoints
is distributed are out of scope for this document.</t>
      </section>
      <section anchor="null-group">
        <name>The Null Multicast Endpoint</name>
        <t>When the Null imc URI (<xref target="null-imc"/>) is used as a BPv7 EID, it is termed the
"Null imc EID", and the endpoint it identifies is the null multicast endpoint.</t>
        <t>The null multicast endpoint never has any members: a bundle node <bcp14>MUST NOT</bcp14>
have a registration in the null multicast endpoint, by whatever means
registrations are created. A bundle destined for the Null imc EID therefore
cannot be delivered.</t>
        <t>The null multicast endpoint is a different endpoint from the BPv7 null
endpoint ("dtn:none", <xref section="4.2.5.1.1" sectionFormat="of" target="RFC9171"/>), although neither ever
has any members. Where <xref target="RFC9171"/> gives the null endpoint ID a particular
meaning, such as an anonymous bundle source, it is the null endpoint ID
"dtn:none" that has that meaning, not the Null imc EID.</t>
      </section>
      <section anchor="node-ids">
        <name>Node IDs and Bundle Sources</name>
        <t><xref section="4.2.5.2" sectionFormat="of" target="RFC9171"/> requires that a Node ID be the EID of a
singleton endpoint. Because a multicast endpoint is not a singleton endpoint,
an imc EID cannot be used as a Node ID, and so cannot be the source node ID
of a bundle (<xref section="5.2" sectionFormat="of" target="RFC9171"/>), the node ID carried in a Previous
Node Block (<xref section="4.4.1" sectionFormat="of" target="RFC9171"/>), or the security source of a Bundle
Protocol Security (BPSec) <xref target="RFC9172"/> security block.</t>
      </section>
      <section anchor="private-eids">
        <name>Private Use imc EIDs</name>
        <t>imc EIDs with a zero (0) Allocator Identifier and a Group Number within the
Private Use ranges of the Default Allocator (<xref target="private-groups"/>) are not
universally unique, and are therefore only valid within the scope of the
current administrative domain. Any bundle using a Private Use imc EID as a
bundle destination <bcp14>MUST NOT</bcp14> be allowed to cross administrative domains. All
implementations that could be deployed as a gateway between administrative
domains <bcp14>MUST</bcp14> be sufficiently configurable to ensure that this is enforced,
and operators <bcp14>MUST</bcp14> ensure correct configuration.</t>
        <t>Private Use imc EIDs <bcp14>MUST NOT</bcp14> be present in any other part of a bundle that is
destined for another administrative domain when the lack of uniqueness
prevents correct operation.</t>
      </section>
      <section anchor="admin">
        <name>Administrative Multicast Endpoints</name>
        <t>Consistent with the meaning of Service Number zero (0) in 'ipn' EIDs
(<xref section="5.7" sectionFormat="of" target="RFC9758"/>), the multicast endpoint of a group with Service
Number zero (0), for example imc:977000.17.0, is the "administrative
multicast endpoint" of that group: administrative records
(<xref section="6.1" sectionFormat="of" target="RFC9171"/>) destined for it are delivered at each member to
the administrative element of its application agent
(<xref section="3.1" sectionFormat="of" target="RFC9171"/>).</t>
        <t>Every node of a group is a member of the administrative multicast endpoint of
that group, in the same way that every node is a member of its own
administrative endpoint (<xref section="3.2" sectionFormat="of" target="RFC9171"/>). Because a node is a
node of a group only if it is a member of at least one multicast endpoint of
that group, no node is implicitly a member of the administrative multicast
endpoint of any other group.</t>
        <t>An administrative multicast endpoint is not the administrative endpoint of
any node, which is a singleton endpoint (<xref section="3.2" sectionFormat="of" target="RFC9171"/>). An
administrative record delivered from an administrative multicast endpoint
may therefore have been delivered at many nodes.</t>
      </section>
      <section anchor="well-known">
        <name>Well-Known Service Numbers</name>
        <t>The Service Number of an imc EID is interpreted in the same way as the
Service Number of an 'ipn' EID. In particular, the well-known Service Numbers
registered in the "'ipn' Scheme URI Well-Known Service Numbers for BPv7"
registry (<xref section="5.6" sectionFormat="of" target="RFC9758"/>) identify the same services when they
appear in imc EIDs. Service Number zero (0), registered there as the
Administrative Endpoint, identifies the administrative multicast endpoint of
a group (<xref target="admin"/>).</t>
        <t><cref anchor="svc-reg"><xref target="I-D.cavallini-dtn-iac"/> requests that the registries shared by
'ipn' and 'iac' be renamed. The WG needs to coordinate how these shared
registries are named and referenced across 'ipn', 'imc', and 'iac'.</cref></t>
      </section>
    </section>
    <section anchor="cbor">
      <name>CBOR Representation of imc URIs with BPv7</name>
      <t><xref section="4.2.5.1" sectionFormat="of" target="RFC9171"/> requires that any URI scheme used to represent
BPv7 EIDs <bcp14>MUST</bcp14> define how the scheme-specific part of the URI scheme is
encoded with Concise Binary Object Representation (CBOR) <xref target="RFC8949"/>. To meet
this requirement, this section describes the CBOR encoding of imc EIDs. The
formal definition of the CBOR representation is specified in
<xref target="cbor-syntax"/>.</t>
      <t>The examples in this section use the value 3 as the BPv7 URI scheme type of
the 'imc' scheme. This value is a placeholder pending assignment by IANA; see
<xref target="iana-bp"/>.</t>
      <section anchor="cbor-encoding">
        <name>imc EID CBOR Encoding</name>
        <t>When encoding imc EIDs for use with BPv7, the scheme-specific part of an imc
URI <bcp14>MUST</bcp14> be represented as a CBOR array of exactly three (3) elements,
regardless of the Allocator Identifier. Each element of the array <bcp14>MUST</bcp14> be
encoded as a single CBOR unsigned integer, and:</t>
        <ul spacing="normal">
          <li>
            <t>the first element of the array is the Allocator Identifier,</t>
          </li>
          <li>
            <t>the second element of the array is the Group Number, and</t>
          </li>
          <li>
            <t>the third element of the array is the Service Number.</t>
          </li>
        </ul>
        <t>This encoding corresponds to the three-element scheme-specific encoding of
'ipn' EIDs (<xref section="6.1.2" sectionFormat="of" target="RFC9758"/>). There is no equivalent of the
two-element scheme-specific encoding of 'ipn' EIDs
(<xref section="6.1.1" sectionFormat="of" target="RFC9758"/>): the Allocator Identifier is always encoded,
including when it is zero (0), and no element packs the Allocator Identifier
and Group Number into a single integer.</t>
        <t>For example, the imc EID of imc:977000.17.1 would result in the three-element
array of [977000,17,1], which would be encoded in CBOR as the following
10-octet sequence:</t>
        <sourcecode type="cbor-pretty"><![CDATA[
82                # 2-Element Endpoint Encoding
   03             # uri-code: 3 ('imc' URI scheme)
   83             # 3-Element imc EID encoding
      1A 000EE868 # Allocator Identifier
      11          # Group Number
      01          # Service Number
]]></sourcecode>
        <t>Further examples are provided in <xref target="cbor-examples"/>.</t>
        <t>An imc EID whose scheme-specific part is not a CBOR array of exactly three
(3) unsigned integers, or whose Allocator Identifier or Group Number is not
less than 2^32, is malformed. In particular, a two-element array is
malformed. A bundle containing a malformed imc EID in its primary block <bcp14>MUST</bcp14>
be treated as malformed.</t>
        <t><cref anchor="no-2el">The 'ipn' two-element encoding was retained in RFC 9758 only for
backwards compatibility with existing implementations, and CCSDS is
already deprecating it, so this document does not carry it into the new
scheme, in either a packed form or an unpacked form for the Default
Allocator. The cost is one additional octet for imc EIDs using the
Default Allocator, in exchange for each imc EID having a single
encoding.</cref></t>
      </section>
      <section anchor="cbor-syntax">
        <name>'imc' URI Scheme CBOR Syntax</name>
        <t>When encoded in CBOR <xref target="RFC8949"/>, a BPv7 endpoint identified by an imc URI
<bcp14>MUST</bcp14> comply with the following Concise Data Definition Language (CDDL)
<xref target="RFC8610"/> specification:</t>
        <sourcecode type="cddl"><![CDATA[
eid = $eid .within eid-structure

eid-structure = [
  uri-code: uint,
  SSP: any
]

; ... Syntax for other uri-code values defined in RFC 9171 ...

$eid /= [
  uri-code: 3,  ; placeholder pending IANA assignment (TBD1)
  SSP: imc-ssp
]
imc-ssp = [
  allocator-identifier: uint .lt 4294967296,
  group-number: uint .lt 4294967296,
  service-number: uint
]
]]></sourcecode>
      </section>
      <section anchor="matching">
        <name>imc EID Matching</name>
        <t>imc EID matching <bcp14>MUST</bcp14> be performed on the decoded EID information itself:
two imc EIDs are equal if and only if their Allocator Identifiers, Group
Numbers, and Service Numbers are equal.</t>
        <t>Because there is a single scheme-specific encoding, and <xref section="4.1" sectionFormat="of" target="RFC9171"/> requires the core deterministic encoding of <xref target="RFC8949"/> for bundle
blocks, each imc EID has exactly one CBOR representation. Unlike 'ipn' EIDs
(<xref section="6.4" sectionFormat="of" target="RFC9758"/>), no imc EID can be represented by different
encodings that need to be treated as equivalent.</t>
      </section>
    </section>
    <section anchor="special">
      <name>Special Considerations</name>
      <section anchor="other-schemes">
        <name>Relationship to Other URI Schemes</name>
        <t>imc URIs share their Allocator Identifiers and Service Numbers with 'ipn'
URIs (<xref target="allocators"/>, <xref target="well-known"/>). Group Numbers and Node Numbers are
distinct namespaces.</t>
        <t><cref anchor="iac"><xref target="I-D.cavallini-dtn-iac"/> proposes that Group Numbers have the same
meaning in the 'iac' anycast scheme and in multi-destination schemes such
as 'imc', so that one Group Number can be used with either scheme.
The WG needs to decide whether to adopt that alignment.</cref></t>
      </section>
      <section anchor="late-binding">
        <name>Late Binding</name>
        <t><xref target="RFC9171"/> mandates the concept of the "late binding" of an EID, whereby the
address of the destination of a bundle is resolved from its identifier
hop-by-hop as it transits a BPv7 network. The concept of late binding is
preserved in the 'imc' URI scheme. Elements of an imc URI <bcp14>MUST NOT</bcp14> be
regarded as carrying information relating to the location or reachability of
the members of a multicast endpoint, or other addressing or routing concerns.</t>
        <t>In particular, although a forwarding mechanism may base its decisions on the
FQGN, in the same way that 'ipn' forwarding may be based on the FQNN, an FQGN
carries no such information: the nodes of a group may be located anywhere,
and may change at any time.</t>
      </section>
    </section>
    <section anchor="patterns">
      <name>imc EID Patterns</name>
      <t><xref target="I-D.ietf-dtn-eid-pattern"/> defines EID Patterns, a means of matching sets
of BPv7 EIDs, and requires that each URI scheme supporting patterns define a
scheme-specific pattern item, comprising a logical information model, EID
matching logic, pattern set logic, and both text and CBOR forms
(<xref section="1.1" sectionFormat="of" target="I-D.ietf-dtn-eid-pattern"/>). This section defines the
scheme-specific pattern item for the 'imc' URI scheme, termed the "imc
pattern".</t>
      <t>Because the information model of an imc URI is identical to that of an 'ipn'
URI, being three unsigned integer elements with the same domains, the imc
pattern is defined by reference to the IPN Scheme Pattern Item defined in
<xref section="2.4" sectionFormat="of" target="I-D.ietf-dtn-eid-pattern"/>, termed the "IPN pattern". Except
as specified in this section, every requirement of that section and its
subsections applies to the imc pattern, with "imc" substituted for "IPN" or
"ipn".</t>
      <section anchor="pattern-model">
        <name>Information Model</name>
        <t>An imc pattern <bcp14>SHALL</bcp14> logically contain exactly three elements corresponding
to the elements of an imc EID:</t>
        <ul spacing="normal">
          <li>
            <t>Allocator Identifier, with domain 0 to 2^32-1 inclusive</t>
          </li>
          <li>
            <t>Group Number, with domain 0 to 2^32-1 inclusive</t>
          </li>
          <li>
            <t>Service Number, with domain 0 to 2^64-1 inclusive</t>
          </li>
        </ul>
        <t>Each element is matched as a specific value, a range, or a wildcard, and is
subject to the same constraints on ranges, normalization, decoding failure,
and minimum supported number of intervals as the corresponding element of an
IPN pattern (<xref section="2.4" sectionFormat="of" target="I-D.ietf-dtn-eid-pattern"/>), with the Group
Number taking the place of the Node Number.</t>
      </section>
      <section anchor="pattern-matching">
        <name>EID Matching and Pattern Set Logic</name>
        <t>An imc pattern matches an imc EID according to the rules of
<xref section="2.4.1" sectionFormat="of" target="I-D.ietf-dtn-eid-pattern"/>, applied to the decoded
Allocator Identifier, Group Number, and Service Number of the EID. An imc
pattern never matches an EID of any other scheme.</t>
        <t>Set logic between imc patterns is as defined for IPN patterns in
<xref section="2.4.2" sectionFormat="of" target="I-D.ietf-dtn-eid-pattern"/>.</t>
      </section>
      <section anchor="pattern-text">
        <name>Text Form</name>
        <t>The text form of the imc pattern is identical to the text form of the IPN
pattern defined in <xref section="2.4.3" sectionFormat="of" target="I-D.ietf-dtn-eid-pattern"/>, except that
the scheme name is "imc" rather than "ipn". In the same way that the IPN
pattern accepts a single 'ipn' EID written in its two-element text form, the
imc pattern accepts a single imc URI written in its two-element text form
(<xref target="text"/>), without the '!' character, since the 'imc' scheme has no
LocalNode equivalent (<xref target="max-group"/>). It conforms to the following ABNF,
which reuses the rules ipn-part-pat, ipn-decimal, and nbr-delim (and the
rules on which they depend) from Figure 1 of <xref target="I-D.ietf-dtn-eid-pattern"/>:</t>
        <sourcecode type="abnf"><![CDATA[
eid-pattern-item =/ imc-pat-item
imc-pat-item = "imc:" (imc-pat-ssp3 / imc-pat-ssp2)

; Full pattern for three elements
imc-pat-ssp3 = ipn-part-pat
               nbr-delim ipn-part-pat
               nbr-delim ipn-part-pat

; Accept a single EID in two-element text form
imc-pat-ssp2 = ipn-decimal nbr-delim ipn-decimal
]]></sourcecode>
        <t>The two-element text form is not a pattern form in its own right: it
contains only a single imc URI, and cannot contain a range or wildcard. When
decoding it, the first element <bcp14>SHALL</bcp14> be treated as a Group Number assigned by
the Default Allocator, and the pattern <bcp14>SHALL</bcp14> be treated as the three-element
pattern whose elements are the specific values zero (0), that Group Number,
and the Service Number, consistent with the two-element text form of an imc
URI (<xref target="text"/>).</t>
        <t>As for the IPN pattern, the canonical text form of an imc pattern <bcp14>SHALL</bcp14> use
three elements, and every imc URI is itself a valid imc pattern that matches
only that imc URI, satisfying <xref section="2.1.1" sectionFormat="of" target="I-D.ietf-dtn-eid-pattern"/>.</t>
        <t>For example, the following imc pattern matches every Service Number of the
group with Group Number 17 assigned by Allocator 977000:</t>
        <artwork><![CDATA[
imc:977000.17.*
]]></artwork>
        <t>The following imc pattern matches Service Number 1 of every group
assigned by the Default Allocator from the first Private Use range
(<xref target="iana-groups"/>):</t>
        <artwork><![CDATA[
imc:0.[1-127].1
]]></artwork>
      </section>
      <section anchor="pattern-cbor">
        <name>CBOR Form</name>
        <t>The CBOR form of the imc pattern is identical to the CBOR form of the IPN
pattern defined in <xref section="2.4.4" sectionFormat="of" target="I-D.ietf-dtn-eid-pattern"/>, including
the encoding of specific values, ranges, and wildcards, except that the scheme
number is the 'imc' URI scheme type (<xref target="iana-bp"/>) rather than 2. It conforms
to the following CDDL, which reuses the rule ipn-part-pat (and the rules on
which it depends) from Figure 2 of <xref target="I-D.ietf-dtn-eid-pattern"/>:</t>
        <sourcecode type="cddl"><![CDATA[
$eid-pat-item /= [
  scheme-num: 3,  ; placeholder pending IANA assignment (TBD1)
  SSP: imc-pat-ssp
]
imc-pat-ssp = [
  ; This CDDL representation does not restrict to the
  ; true domain of each element.
  3*3 ipn-part-pat,
]
]]></sourcecode>
        <t>As for the IPN pattern, the CBOR form always has three elements.</t>
        <t>For example, the imc pattern imc:977000.17.* would be encoded in CBOR as the
following 11-octet sequence, using the placeholder value 3 for the 'imc' URI
scheme type:</t>
        <sourcecode type="cbor-pretty"><![CDATA[
81                   # EID Pattern with one item
   82                # imc pattern item
      03             # scheme-num: 3 ('imc' URI scheme)
      83             # 3-Element imc pattern SSP
         1A 000EE868 # Allocator Identifier
         11          # Group Number
         F5          # Service Number: wildcard (true)
]]></sourcecode>
        <t><cref anchor="pattern-dep">This section depends normatively on
<xref target="I-D.ietf-dtn-eid-pattern"/>. If the WG prefers not to create that
dependency, this section could instead be moved to that document, or
to a separate document.</cref></t>
      </section>
    </section>
    <section anchor="security">
      <name>Security Considerations</name>
      <t>This section follows the structure of <xref section="8" sectionFormat="of" target="RFC9758"/>.</t>
      <section anchor="reliability-and-consistency">
        <name>Reliability and Consistency</name>
        <t>None of the BPv7 endpoints identified by imc EIDs are guaranteed to be
reachable at any time, and the identity of the processing entities operating
on those endpoints is never guaranteed by the Bundle Protocol itself.
Verification of the signature provided by the Block Integrity Block (BIB)
targeting the bundle's primary block, as defined by BPSec <xref target="RFC9172"/>, is
required for this purpose.</t>
      </section>
      <section anchor="malicious-construction">
        <name>Malicious Construction</name>
        <t>Malicious construction of a conformant imc URI is limited to the malicious
selection of Allocator Identifiers, Group Numbers, and Service Numbers. That
is, a maliciously constructed imc EID could be used to direct a bundle to a
multicast endpoint whose members might be damaged by the arrival of that bundle.
A bundle that asserts an imc EID as its source node ID is not valid
(<xref target="node-ids"/>). In all cases (and indeed in all bundle processing), the node
that receives a bundle should verify its authenticity and validity before
operating on it in any way.</t>
      </section>
      <section anchor="sec-unauthorized">
        <name>Unauthorized Membership</name>
        <t>Membership of a multicast endpoint is characterized by local registrations
(<xref target="membership"/>), and the 'imc' URI scheme itself provides no means of
restricting which nodes may become members of a multicast endpoint. Bundles
destined for a multicast endpoint may therefore be delivered at nodes that
are not intended recipients. Where this is a concern, the confidentiality of
bundle contents should be protected using BPSec <xref target="RFC9172"/>, and multicast
protocols should authenticate membership information before acting on it.</t>
        <t>Because the services of a group exist at a common set of nodes, a
forwarding mechanism that bases its decisions on the FQGN may convey a bundle
destined for one multicast endpoint of a group to any node of that group,
including nodes that are not members of its destination endpoint. Although
such a node does not deliver the bundle, its bundle protocol agent has access
to the bundle's blocks. Allocators and operators should therefore assign
services intended for different sets of nodes to different groups, and
should not rely on the Service Number to confine bundles to the members of a
single multicast endpoint.</t>
      </section>
      <section anchor="sec-implicit">
        <name>Implicit Membership</name>
        <t>This document does not define any multicast endpoint of which all nodes, or
all nodes supporting the 'imc' scheme, are implicitly members. In particular,
the Null imc URI (<xref target="null-imc"/>) identifies the null multicast endpoint, which
never has any members (<xref target="null-group"/>).</t>
        <t>Such an endpoint would allow any node able to inject a single bundle into a
BPv7 network to cause that bundle to be replicated to, and delivered at, every
node in the network. This is an amplification mechanism that could be used
to exhaust transmission opportunities, storage, and power across the whole
network, which is a particularly severe threat in networks with scarce or
scheduled connectivity. Because membership would be implicit rather than
determined by local registrations, no node could decline to receive such
bundles, and the scope of the endpoint could not be confined to a single
administrative domain. Mechanisms that require communication with many nodes,
such as the distribution of membership information, should instead use
multicast endpoints of explicitly assigned groups, whose membership and
origination can be controlled by the deployment.</t>
        <t>The membership of every node of a group in that group's administrative
multicast endpoint (<xref target="admin"/>) does not create such an endpoint. It is
confined to the nodes of that group, each of which is a member of at least
one of its multicast endpoints by registration, and a node that does not wish
administrative records sent to a group to be delivered at it can avoid this
by having no registration in any multicast endpoint of that group.</t>
      </section>
      <section anchor="sec-reports">
        <name>Status Report Implosion</name>
        <t><xref section="6.1.1" sectionFormat="of" target="RFC9171"/> notes that requesting status reports for a
single unicast bundle can result in (1 + (2 * (N-1))) status report bundles,
where N is the number of nodes on the path to its destination, and for that
reason requires that the generation of status reports be disabled by default
and enabled only when the risk of excessive network traffic is deemed
acceptable. <xref section="8" sectionFormat="of" target="RFC9171"/> further notes that malicious initiation
of status reporting could be used to effect a denial-of-service attack.</t>
        <t>These risks are multiplied for bundles destined for multicast endpoints. A
single bundle destined for an imc EID may be replicated along many paths and
delivered at every member of the multicast endpoint, and each node that
receives, forwards, delivers, or deletes a copy may generate a status report.
The number of status reports generated by a single bundle can therefore grow
with the number of members of the multicast endpoint as well as with the
length of each path, and all of those reports converge on the single
report-to endpoint, which may be overwhelmed. A bundle destined for a
multicast endpoint that requests status reports is also an amplification
mechanism, since a single bundle sent by an attacker can cause a much larger
number of bundles to be sent to a victim named as its report-to endpoint.</t>
        <t>Implementations of the 'imc' scheme <bcp14>MUST</bcp14> retain the default of
<xref section="6.1.1" sectionFormat="of" target="RFC9171"/> that status report generation is disabled, and
<bcp14>SHOULD NOT</bcp14> generate status reports in response to bundles destined for imc
EIDs unless explicitly configured to do so for the multicast endpoints
concerned. Where status reporting for bundles destined for multicast
endpoints is enabled, operators should take into account the number of
members and the capacity of the report-to endpoint. Naming an administrative
multicast endpoint (<xref target="admin"/>) as the report-to endpoint distributes the
reports to a set of monitoring nodes, but does not reduce their number, and
further multiplies the resulting traffic. Because every node of a group is a
member of its administrative multicast endpoint, such reports are delivered at
every node of that group, and not only at nodes intended to monitor them, so
a group used for this purpose would normally be assigned to the monitoring
function alone.</t>
        <t>Integrity protection of the primary block using BPSec <xref target="RFC9172"/> allows a
node to verify that status reports were genuinely requested by the source of
a bundle.</t>
      </section>
      <section anchor="sec-private">
        <name>Private Use imc EIDs</name>
        <t>Private Use (<xref target="private-groups"/>) imc URIs present a risk to the stability of
deployed BPv7 networks. If such imc URIs are allowed to propagate beyond the
domain in which they are valid, then the required uniqueness of imc URIs no
longer holds, and bundles may be delivered at members of unintended multicast
endpoints in other administrative domains.</t>
        <t>See <xref target="private-eids"/> for required behaviors to mitigate against this form of
abuse.</t>
      </section>
      <section anchor="back-end-transcoding">
        <name>Back-End Transcoding</name>
        <t>The limited expressiveness of URIs of the 'imc' scheme effectively eliminates
the possibility of threats due to errors in back-end transcoding.</t>
      </section>
      <section anchor="rare-ip-address-formats">
        <name>Rare IP Address Formats</name>
        <t>Not relevant, as IP addresses do not appear anywhere in conformant imc URIs.</t>
      </section>
      <section anchor="sensitive-information">
        <name>Sensitive Information</name>
        <t>Because imc URIs are used only to represent the numeric identities of
multicast endpoints, the risk of disclosure of sensitive information due to
interception of these URIs is minimal. Examination of imc URIs could be used
to support traffic analysis; where traffic analysis is a plausible danger,
bundles should be conveyed by bundle-in-bundle encapsulation
<xref target="I-D.ietf-dtn-bibe"/> or by secure convergence-layer protocols that do not
expose endpoint IDs, such as TCPCLv4 <xref target="RFC9174"/>.</t>
      </section>
      <section anchor="semantic-attacks">
        <name>Semantic Attacks</name>
        <t>The simplicity of the 'imc' URI scheme syntax minimizes the possibility of
misinterpretation of a URI by a human user.</t>
      </section>
      <section anchor="eid-patterns">
        <name>EID Patterns</name>
        <t>The security considerations of <xref section="5" sectionFormat="of" target="I-D.ietf-dtn-eid-pattern"/>
apply to imc patterns (<xref target="patterns"/>). Because the text forms of imc and IPN
patterns differ only in their scheme name, care is needed that a pattern
intended to match 'ipn' EIDs is not written with the 'imc' scheme name, or
vice versa, as the two match disjoint sets of EIDs.</t>
      </section>
    </section>
    <section anchor="iana">
      <name>IANA Considerations</name>
      <section anchor="iana-uri">
        <name>'imc' URI Scheme</name>
        <t>IANA is requested to register the following URI scheme in the "Uniform
Resource Identifier (URI) Schemes" registry, using the template in
<xref section="7.4" sectionFormat="of" target="RFC7595"/>:</t>
        <dl>
          <dt>Scheme name:</dt>
          <dd>
            <t>imc</t>
          </dd>
          <dt>Status:</dt>
          <dd>
            <t>Permanent</t>
          </dd>
          <dt>Applications/protocols that use this scheme name:</dt>
          <dd>
            <t>The Delay-Tolerant Networking (DTN) Bundle Protocol Version 7 (BPv7)
<xref target="RFC9171"/>.</t>
          </dd>
          <dt>Contact:</dt>
          <dd>
            <t>IESG &lt;iesg@ietf.org&gt;</t>
          </dd>
          <dt>Change controller:</dt>
          <dd>
            <t>IETF</t>
          </dd>
          <dt>References:</dt>
          <dd>
            <t>This document.</t>
          </dd>
        </dl>
      </section>
      <section anchor="iana-bp">
        <name>Bundle Protocol URI Scheme Types</name>
        <t>IANA is requested to assign the following value in the "Bundle Protocol URI
Scheme Types" registry within the "Bundle Protocol" registry group, including
the "EID Pattern Reference" column added by
<xref section="6.1" sectionFormat="of" target="I-D.ietf-dtn-eid-pattern"/>:</t>
        <table>
          <name>New Value in the Bundle Protocol URI Scheme Types Registry</name>
          <thead>
            <tr>
              <th align="left">Value</th>
              <th align="left">Description</th>
              <th align="left">BP Utilization Reference</th>
              <th align="left">URI Definition Reference</th>
              <th align="left">EID Pattern Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">TBD1</td>
              <td align="left">imc</td>
              <td align="left">This document</td>
              <td align="left">This document</td>
              <td align="left">This document, <xref target="patterns"/></td>
            </tr>
          </tbody>
        </table>
        <t><cref anchor="tbd1">ION already uses the value 3 for 'imc', although no value has
been assigned by IANA, and <xref target="I-D.cavallini-dtn-iac"/> requests the value 3
for 'iac'. Because 'imc' and 'iac' EIDs share the same three-element
structure, assigning 3 to 'iac' would cause existing three-element 'imc'
EIDs to be silently interpreted as valid 'iac' EIDs, rather than failing
to decode. The author suggests that 'imc' retain the value 3, as the
longer-established use (the 'imc' scheme dates from
<xref target="I-D.burleigh-dtnrg-imc"/>), and that 'iac' request the next available
value; the 'iac' authors have indicated that this is acceptable. Note that this document is already not wire-compatible with
existing implementations for Default Allocator EIDs (<xref target="cbor-encoding"/>)
or for imc:0.0 (<xref target="null-group"/>), so the WG could instead choose a new
value to separate this specification cleanly from deployed practice. As
the registry requires Standards Action, the value could be secured
following WG adoption by an early allocation <xref target="RFC7120"/>.</cref></t>
      </section>
      <section anchor="iana-allocators">
        <name>'ipn' Scheme URI Allocator Identifiers</name>
        <t>IANA is requested to add this document as a reference to the "'ipn' Scheme
URI Allocator Identifiers" registry, and to add the following note to that
registry:</t>
        <ul empty="true">
          <li>
            <t>Allocator Identifiers in this registry are also used to identify the
Allocators of Group Numbers for the 'imc' URI scheme.</t>
          </li>
        </ul>
      </section>
      <section anchor="iana-groups">
        <name>'imc' Scheme URI Default Allocator Group Numbers Registry</name>
        <t>IANA is requested to create a new registry titled "'imc' Scheme URI Default
Allocator Group Numbers" in the "Uniform Resource Identifier (URI) Schemes"
registry group. Using terms defined in <xref target="RFC8126"/>, the registration
procedures for this registry are:</t>
        <table>
          <name>Registration Procedures for the 'imc' Scheme URI Default Allocator Group Numbers Registry</name>
          <thead>
            <tr>
              <th align="left">Range</th>
              <th align="left">Registration Procedures</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">1..127</td>
              <td align="left">Private Use</td>
            </tr>
            <tr>
              <td align="left">128..255</td>
              <td align="left">Standards Action</td>
            </tr>
            <tr>
              <td align="left">0x0100..0x7FFF</td>
              <td align="left">Private Use</td>
            </tr>
            <tr>
              <td align="left">0x8000..0xFFFF</td>
              <td align="left">Specification Required</td>
            </tr>
            <tr>
              <td align="left">0x10000..0xFFFFFFFE</td>
              <td align="left">Private Use</td>
            </tr>
            <tr>
              <td align="left">&gt;=0x100000000</td>
              <td align="left">Invalid</td>
            </tr>
          </tbody>
        </table>
        <t>These ranges follow the CBOR encoding of unsigned integers
(<xref section="3" sectionFormat="of" target="RFC8949"/>), in which values less than 24 are encoded in one
octet, values less than 256 in two octets, values less than 65536 in three
octets, and values less than 2^32 in five octets. The two-octet and
three-octet encoded lengths are each divided between Private Use and
registered Group Numbers, so that deployments using Private Use Group Numbers
are not forced to use less efficiently encoded values than registered
groups. All one-octet values other than zero (0), and all
five-octet values other than 2^32-1, are reserved for Private Use. This is
the same structure as the "'ipn' Scheme URI Well-Known Service Numbers for
BPv7" registry (<xref section="9.3" sectionFormat="of" target="RFC9758"/>).</t>
        <t>The initial values in the registry are:</t>
        <table>
          <name>Initial Values in the 'imc' Scheme URI Default Allocator Group Numbers Registry</name>
          <thead>
            <tr>
              <th align="left">Value</th>
              <th align="left">Description</th>
              <th align="left">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">0</td>
              <td align="left">Reserved for the Null imc URI</td>
              <td align="left">This document, <xref target="null-imc"/></td>
            </tr>
            <tr>
              <td align="left">4294967295</td>
              <td align="left">Invalid; avoids confusion with LocalNode ipn URIs</td>
              <td align="left">This document, <xref target="max-group"/></td>
            </tr>
          </tbody>
        </table>
        <t>Each entry in this registry associates a single Group Number with a
group of interest to the wider BPv7 community. Within the registry,
the group is identified using the "Description" field, and the
"Reference" field identifies a publicly available specification of the
purpose of the group.</t>
        <t><cref anchor="groups-ranges">The ranges of the "'ipn' Scheme URI Default Allocator Node
Numbers" registry (Section 9.2 of <xref target="RFC9758"/>) are not used as a model,
because that registry retains its pre-existing structure and assignments
rather than following CBOR encoding lengths. How this registry relates to
the "Bundle Protocol Well-Known Group Numbers" registry proposed by
<xref target="I-D.cavallini-dtn-iac"/>, which uses the same CBOR-aligned ranges, is to
be decided.</cref></t>
        <section anchor="iana-groups-experts">
          <name>Guidance for Designated Experts</name>
          <t>Due to the nature of the CBOR encoding of unsigned integers used for Group
Numbers with BPv7, Group Numbers with a low value are encoded more
efficiently than larger numbers. The two-octet registered range (128..255)
is therefore reserved for Standards Action. Designated experts reviewing
requests in the three-octet registered range (0x8000..0xFFFF) are strongly
recommended to familiarize themselves with the CBOR encoding of unsigned
integers in <xref target="RFC8949"/>.</t>
          <t>Group Numbers assigned by the Default Allocator are intended for groups that
are of use to the entire BPv7 community. Each registration outside the
Private Use ranges <bcp14>MUST</bcp14> have a corresponding publicly available specification
describing the purpose of the group. Groups that are specific to a particular
deployment or organization are expected to use Group Numbers assigned by that
organization's own Allocator, or Private Use Group Numbers, and do not
require an entry in this registry.</t>
          <t>Because the services of a group exist at a common set of nodes
(<xref target="group-numbers"/>), designated experts should encourage specifications to
request separate Group Numbers for services intended for different sets of
nodes, rather than separate Service Numbers of a single group (see
<xref target="sec-unauthorized"/>).</t>
          <t>Designated experts <bcp14>MUST NOT</bcp14> approve the registration of any Group Number
whose specification requires bundle nodes to be implicitly nodes of the
identified group, or members of any of its multicast endpoints (see
<xref target="sec-implicit"/>).</t>
        </section>
      </section>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC3986">
          <front>
            <title>Uniform Resource Identifier (URI): Generic Syntax</title>
            <author fullname="T. Berners-Lee" initials="T." surname="Berners-Lee"/>
            <author fullname="R. Fielding" initials="R." surname="Fielding"/>
            <author fullname="L. Masinter" initials="L." surname="Masinter"/>
            <date month="January" year="2005"/>
            <abstract>
              <t>A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="66"/>
          <seriesInfo name="RFC" value="3986"/>
          <seriesInfo name="DOI" value="10.17487/RFC3986"/>
        </reference>
        <reference anchor="RFC5234">
          <front>
            <title>Augmented BNF for Syntax Specifications: ABNF</title>
            <author fullname="D. Crocker" initials="D." role="editor" surname="Crocker"/>
            <author fullname="P. Overell" initials="P." surname="Overell"/>
            <date month="January" year="2008"/>
            <abstract>
              <t>Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="68"/>
          <seriesInfo name="RFC" value="5234"/>
          <seriesInfo name="DOI" value="10.17487/RFC5234"/>
        </reference>
        <reference anchor="RFC7595">
          <front>
            <title>Guidelines and Registration Procedures for URI Schemes</title>
            <author fullname="D. Thaler" initials="D." role="editor" surname="Thaler"/>
            <author fullname="T. Hansen" initials="T." surname="Hansen"/>
            <author fullname="T. Hardie" initials="T." surname="Hardie"/>
            <date month="June" year="2015"/>
            <abstract>
              <t>This document updates the guidelines and recommendations, as well as the IANA registration processes, for the definition of Uniform Resource Identifier (URI) schemes. It obsoletes RFC 4395.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="35"/>
          <seriesInfo name="RFC" value="7595"/>
          <seriesInfo name="DOI" value="10.17487/RFC7595"/>
        </reference>
        <reference anchor="RFC8126">
          <front>
            <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
            <author fullname="M. Cotton" initials="M." surname="Cotton"/>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <author fullname="T. Narten" initials="T." surname="Narten"/>
            <date month="June" year="2017"/>
            <abstract>
              <t>Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).</t>
              <t>To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.</t>
              <t>This is the third edition of this document; it obsoletes RFC 5226.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="26"/>
          <seriesInfo name="RFC" value="8126"/>
          <seriesInfo name="DOI" value="10.17487/RFC8126"/>
        </reference>
        <reference anchor="RFC8610">
          <front>
            <title>Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures</title>
            <author fullname="H. Birkholz" initials="H." surname="Birkholz"/>
            <author fullname="C. Vigano" initials="C." surname="Vigano"/>
            <author fullname="C. Bormann" initials="C." surname="Bormann"/>
            <date month="June" year="2019"/>
            <abstract>
              <t>This document proposes a notational convention to express Concise Binary Object Representation (CBOR) data structures (RFC 7049). Its main goal is to provide an easy and unambiguous way to express structures for protocol messages and data formats that use CBOR or JSON.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8610"/>
          <seriesInfo name="DOI" value="10.17487/RFC8610"/>
        </reference>
        <reference anchor="RFC8949">
          <front>
            <title>Concise Binary Object Representation (CBOR)</title>
            <author fullname="C. Bormann" initials="C." surname="Bormann"/>
            <author fullname="P. Hoffman" initials="P." surname="Hoffman"/>
            <date month="December" year="2020"/>
            <abstract>
              <t>The Concise Binary Object Representation (CBOR) is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation. These design goals make it different from earlier binary serializations such as ASN.1 and MessagePack.</t>
              <t>This document obsoletes RFC 7049, providing editorial improvements, new details, and errata fixes while keeping full compatibility with the interchange format of RFC 7049. It does not create a new version of the format.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="94"/>
          <seriesInfo name="RFC" value="8949"/>
          <seriesInfo name="DOI" value="10.17487/RFC8949"/>
        </reference>
        <reference anchor="RFC9171">
          <front>
            <title>Bundle Protocol Version 7</title>
            <author fullname="S. Burleigh" initials="S." surname="Burleigh"/>
            <author fullname="K. Fall" initials="K." surname="Fall"/>
            <author fullname="E. Birrane, III" initials="E." surname="Birrane, III"/>
            <date month="January" year="2022"/>
            <abstract>
              <t>This document presents a specification for the Bundle Protocol, adapted from the experimental Bundle Protocol specification developed by the Delay-Tolerant Networking Research Group of the Internet Research Task Force and documented in RFC 5050.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9171"/>
          <seriesInfo name="DOI" value="10.17487/RFC9171"/>
        </reference>
        <reference anchor="RFC9758">
          <front>
            <title>Updates to the 'ipn' URI Scheme</title>
            <author fullname="R. Taylor" initials="R." surname="Taylor"/>
            <author fullname="E. Birrane III" initials="E." surname="Birrane III"/>
            <date month="May" year="2025"/>
            <abstract>
              <t>This document updates the specification of the 'ipn' URI scheme previously defined in RFC 6260 and the IANA registries established in RFC 7116. It also updates the rules for the encoding and decoding of these URIs when used as an Endpoint Identifier (EID) in the Bundle Protocol version 7 (BPv7) as defined in RFC 9171. These updates clarify the structure and behavior of the 'ipn' URI scheme, define new encodings of 'ipn' scheme URIs, and establish the registries necessary to manage this scheme.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9758"/>
          <seriesInfo name="DOI" value="10.17487/RFC9758"/>
        </reference>
        <reference anchor="I-D.ietf-dtn-eid-pattern">
          <front>
            <title>Bundle Protocol Endpoint ID Patterns</title>
            <author fullname="Brian Sipos" initials="B." surname="Sipos">
              <organization>The Johns Hopkins University Applied Physics Laboratory</organization>
            </author>
            <date day="23" month="September" year="2026"/>
            <abstract>
              <t>   This document extends the Bundle Protocol Endpoint ID (EID) concept
   into an EID Pattern, which is used to categorize any EID as matching
   a specific pattern or not.  EID Patterns are suitable for expressing
   configuration, for being used on-the-wire by protocols, and for being
   easily understandable by a layperson.  EID Patterns include scheme-
   specific optimizations for expressing set membership and each scheme
   pattern includes text and binary encoding forms; the pattern for the
   "ipn" EID scheme being designed to be highly compressible in its
   binary form.

   This document also defines a Public Key Infrastructure Using X.509
   (PKIX) Other Name form to contain an EID Pattern and a handling rule
   to use a pattern to match an EID.  The Other Name form is used to
   update the PKIX profiles of RFC 9174 and [I-D.ietf-dtn-bpsec-cose].

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-dtn-eid-pattern-11"/>
        </reference>
        <reference anchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="RFC7120">
          <front>
            <title>Early IANA Allocation of Standards Track Code Points</title>
            <author fullname="M. Cotton" initials="M." surname="Cotton"/>
            <date month="January" year="2014"/>
            <abstract>
              <t>This memo describes the process for early allocation of code points by IANA from registries for which "Specification Required", "RFC Required", "IETF Review", or "Standards Action" policies apply. This process can be used to alleviate the problem where code point allocation is needed to facilitate desired or required implementation and deployment experience prior to publication of an RFC, which would normally trigger code point allocation. The procedures in this document are intended to apply only to IETF Stream documents.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="100"/>
          <seriesInfo name="RFC" value="7120"/>
          <seriesInfo name="DOI" value="10.17487/RFC7120"/>
        </reference>
        <reference anchor="RFC9172">
          <front>
            <title>Bundle Protocol Security (BPSec)</title>
            <author fullname="E. Birrane, III" initials="E." surname="Birrane, III"/>
            <author fullname="K. McKeever" initials="K." surname="McKeever"/>
            <date month="January" year="2022"/>
            <abstract>
              <t>This document defines a security protocol providing data integrity and confidentiality services for the Bundle Protocol (BP).</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9172"/>
          <seriesInfo name="DOI" value="10.17487/RFC9172"/>
        </reference>
        <reference anchor="RFC9174">
          <front>
            <title>Delay-Tolerant Networking TCP Convergence-Layer Protocol Version 4</title>
            <author fullname="B. Sipos" initials="B." surname="Sipos"/>
            <author fullname="M. Demmer" initials="M." surname="Demmer"/>
            <author fullname="J. Ott" initials="J." surname="Ott"/>
            <author fullname="S. Perreault" initials="S." surname="Perreault"/>
            <date month="January" year="2022"/>
            <abstract>
              <t>This document describes a TCP convergence layer (TCPCL) for Delay-Tolerant Networking (DTN). This version of the TCPCL protocol resolves implementation issues in the earlier TCPCL version 3 as defined in RFC 7242 and provides updates to the Bundle Protocol (BP) contents, encodings, and convergence-layer requirements in BP version 7 (BPv7). Specifically, TCPCLv4 uses BPv7 bundles encoded by the Concise Binary Object Representation (CBOR) as its service data unit being transported and provides a reliable transport of such bundles. This TCPCL version also includes security and extensibility mechanisms.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9174"/>
          <seriesInfo name="DOI" value="10.17487/RFC9174"/>
        </reference>
        <reference anchor="I-D.burleigh-dtn-multicast">
          <front>
            <title>Bundle Multicast</title>
            <author fullname="Scott Burleigh" initials="S." surname="Burleigh">
              <organization>IPNSIG Inc.</organization>
            </author>
            <date day="10" month="October" year="2026"/>
            <abstract>
              <t>   This document describes Bundle Multicast, a protocol that reduces
   network resource consumption in the forwarding of copies of a given
   Bundle Protocol (BP) data unit - a "bundle" - to all BP nodes that
   are members of a BP endpoint whose ID is formed in the "imc" URI
   scheme, here termed a BP "multicast group".

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-burleigh-dtn-multicast-00"/>
        </reference>
        <reference anchor="I-D.burleigh-dtnrg-imc">
          <front>
            <title>CBHE-Compatible Bundle Multicast</title>
            <author fullname="Scott Burleigh" initials="S." surname="Burleigh">
              <organization>Jet Propulsion Laboratory</organization>
            </author>
            <date day="7" month="November" year="2012"/>
            <abstract>
              <t>   This document describes a mechanism for Delay-Tolerant Networking
   (DTN) multicast that is compatible with Compressed Bundle Header
   Encoding (CBHE).  The mechanism, named "Interplanetary Multicast"
   (IMC), comprises (a) a single network-wide multicast spanning tree
   overlaid on any single Bundle Protocol (BP)-based network, (b)
   multicast groups that take the form of ordinary BP non-singleton
   endpoints, (c) a new CBHE-compatible URI scheme, "imc", for
   expressing the identities of these endpoints, (d) a new type of BP
   administrative record that propagates multicast "petitions"
   (announcements regarding nodes' membership in IMC endpoints) through
   the multicast tree, and (e) a new bundle forwarding procedure by
   which bundles whose destinations are multicast groups are forwarded
   through the multicast tree in accord with previously received
   petitions.

   IMC is designed to provide simple and efficient multi-source,
   generally reliable, delay-tolerant multi-point data delivery in a
   network of arbitrary size.  Anycast, content-centric networking,
   persistent messages, and similar research challenges are not
   explicitly supported.

   For research purposes and small-scale deployment, it is anticipated
   that multicast tree construction and maintenance can be manual.  For
   larger networks an automated protocol for IMC tree management would
   be required; the design of such a protocol is beyond the scope of
   this specification.


              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-burleigh-dtnrg-imc-00"/>
        </reference>
        <reference anchor="I-D.cavallini-dtn-iac">
          <front>
            <title>DTN Interplanetary Anycast Scheme</title>
            <author fullname="Danilo Cavallini" initials="D." surname="Cavallini">
              <organization>European Space Operations Centre (ESOC)</organization>
            </author>
            <author fullname="Felix Flentge" initials="F." surname="Flentge">
              <organization>European Space Operations Centre (ESOC)</organization>
            </author>
            <date day="17" month="September" year="2025"/>
            <abstract>
              <t>   This document describe a new anycast addressing scheme for Delay-
   Tolerant Networking (DTN), named Interplanetary Anycast Communication
   (iac).  Designed for use within the DTN Bundle Protocol Version 7
   (BPv7), iac enables IP Anycast-like funcionality in the Context of
   Delayed Tolerant Network, so this mechanism enables the routing and
   delivery of bundles to a single member of a specified iac anycast
   group based on a structured Endpoint Identifier (EID) URI scheme.

   The document formally defines the "iac" URI scheme, made of three
   main components, an Allocator Identifier, a Group Number, and a
   Service Number, details registration requirements with IANA
   addressing formats, and service numbering conventions while
   maintaining compatibility with existing IPN/IMC-based identifiers.


              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-cavallini-dtn-iac-00"/>
        </reference>
        <reference anchor="I-D.ietf-dtn-bibe">
          <front>
            <title>Bundle-in-Bundle Encapsulation</title>
            <author fullname="Rick Taylor" initials="R." surname="Taylor">
              <organization>Aalyria Technologies</organization>
            </author>
            <author fullname="Alberto Montilla" initials="A." surname="Montilla">
              <organization>Spatiam Corporation</organization>
            </author>
            <date day="15" month="November" year="2026"/>
            <abstract>
              <t>   This document describes Bundle-in-Bundle Encapsulation (BIBE), a
   Delay-Tolerant Networking (DTN) Bundle Protocol (BP) tunneling
   mechanism by which a bundle is carried as the payload of one or more
   encapsulating bundles, allowing security measures and routing policy
   to be applied to the encapsulating bundle without modification of the
   encapsulated bundle.  The protocol includes an optional segmentation
   mechanism, allowing a large encapsulated bundle to be carried in
   multiple encapsulating bundles.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-dtn-bibe-02"/>
        </reference>
      </references>
    </references>
    <?line 1120?>

<section anchor="text-examples">
      <name>'imc' URI Scheme Text Representation Examples</name>
      <t>This section provides some example imc URIs in their textual representation.</t>
      <section anchor="using-the-default-allocator">
        <name>Using the Default Allocator</name>
        <t>Consider the imc URI identifying the multicast endpoint with Service Number 1
of the group with Group Number 5 assigned by the Default Allocator (0).</t>
        <t>The recommended seven-character representation of this URI would be as
follows:</t>
        <artwork><![CDATA[
imc:5.1
]]></artwork>
        <t>The nine-character representation of this URI, with the explicit Allocator
Identifier, would be as follows:</t>
        <artwork><![CDATA[
imc:0.5.1
]]></artwork>
      </section>
      <section anchor="using-a-non-default-allocator">
        <name>Using a Non-Default Allocator</name>
        <t>Consider the imc URI identifying the multicast endpoint with Service Number 1
of the group with Group Number 17 assigned by Allocator 977000.</t>
        <t>The 15-character representation of this URI would be as follows:</t>
        <artwork><![CDATA[
imc:977000.17.1
]]></artwork>
      </section>
      <section anchor="the-null-imc-uri">
        <name>The Null imc URI</name>
        <t>The Null imc URI (<xref target="null-imc"/>) is represented as:</t>
        <artwork><![CDATA[
imc:0.0
]]></artwork>
      </section>
    </section>
    <section anchor="cbor-examples">
      <name>'imc' URI Scheme CBOR Encoding Examples</name>
      <t>This section provides some example CBOR encodings of imc EIDs. As in
<xref target="cbor"/>, these examples use the placeholder value 3 for the 'imc' URI scheme
type.</t>
      <section anchor="using-the-default-allocator-1">
        <name>Using the Default Allocator</name>
        <t>Consider the imc EID imc:5.1. This textual representation of an imc EID
identifies the multicast endpoint with Service Number 1 of the group with Group
Number 5 assigned by the Default Allocator (0).</t>
        <t>The six-octet encoding of this EID would be as follows:</t>
        <sourcecode type="cbor-pretty"><![CDATA[
82       # 2-Element Endpoint Encoding
   03    # uri-code: 3 ('imc' URI scheme)
   83    # 3-Element imc EID encoding
      00 # Default Allocator
      05 # Group Number
      01 # Service Number
]]></sourcecode>
      </section>
      <section anchor="using-a-non-default-allocator-1">
        <name>Using a Non-Default Allocator</name>
        <t>Consider the imc EID imc:977000.17.1. This textual representation of an imc
EID identifies the multicast endpoint with Service Number 1 of the group with
Group Number 17 assigned by Allocator 977000.</t>
        <t>The 10-octet encoding of this EID would be as follows:</t>
        <sourcecode type="cbor-pretty"><![CDATA[
82                # 2-Element Endpoint Encoding
   03             # uri-code: 3 ('imc' URI scheme)
   83             # 3-Element imc EID encoding
      1A 000EE868 # Allocator Identifier
      11          # Group Number
      01          # Service Number
]]></sourcecode>
      </section>
      <section anchor="the-null-imc-eid">
        <name>The Null imc EID</name>
        <t>The six-octet encoding of the Null imc EID (<xref target="null-group"/>) of imc:0.0 would
be as follows:</t>
        <sourcecode type="cbor-pretty"><![CDATA[
82       # 2-Element Endpoint Encoding
   03    # uri-code: 3 ('imc' URI scheme)
   83    # 3-Element imc EID encoding
      00 # Default Allocator
      00 # Group Number
      00 # Service Number
]]></sourcecode>
      </section>
    </section>
    <section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>The 'imc' URI scheme was designed by Scott Burleigh, and much of the text of
this document is derived from <xref target="I-D.burleigh-dtn-multicast"/> and
<xref target="I-D.burleigh-dtnrg-imc"/>. The structure of this document follows
<xref target="RFC9758"/>.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA+V9aXPjRpbg9/wVGNbsWPKSLEl1y23PqC63Ym25uqRqR6/H
HQGSkIQ2CXABUCp1uea37G/ZX7bvzHyZACXZPRsbG1sR3RZJII+X775yMpm4
ruyWxWE2Orsssi/K1fyL7MP74+x0flmsiuy8brKXm2qxLLJ3Td3V83qZfb9Z
duU8b7uRy2ezpriCl+E989rIzfOuuKibm8Os7RbOLep5la9glkWTn3eTLr9Z
1s1k0VUTeHHS0kuTvX3Xbmarsm3Luupu1vD48Zuzt1n2IMuXbY2zVItiXcD/
Vd1onI2KRdnVTZkv8cPx0Uv4Dyx3dPz+7O3IVZvVrGgO3QJWcujmddUWVbtp
D7Ou2RQO1vzI5U2Rw6jHVVc0VQHbua6bXy6aerOGb18Xy/zm4euybTbrDhaU
ndXLosmrLjspOnywrC5G7pfiBv5eHLpskr0+O8H/JOCir95dPcP/rhRy+AHB
xTt3V0W1gUVm2W+bPMsYSqMf+ZvsW3wdv1/l5RK+BwD/W1l059O6ocfzZn4J
X1923bo9fPgQn8Kvyqtiqo89xC8ezpr6ui0ewvsP8b2LsrvczODNppz/wof3
MBwcPrEEKLedGTs8OeW3p2Vt3nl4CyJML7vVcuRcvuku6wZBCxNk2flmuWQk
eg9jZ2f0Kv0Cy86r8u85QuowO8qXN4AU2Vkxv6zqZX1RFi09VjBUGp7033J+
bjqvV85VdbOC96/oFN6/ffXoxfOn8ueTg0eP5c9nT148kT+f7x/oA8+f7u/p
ny8ev5A/X+w/29c/nz15jn8eT14TnGm/RbmYrPMOUe/QubI6T1bwbP9gLwx1
EP58rEPNNs2yKC8uaTiPWkO/NhcIXv1lnl/ly2VZlQz3fN5b26ycwTLcZDLJ
8lnbNfm8c+7ssmwzIOTNCsgvWxTnZVW0WRdxDT7AcZZnQHDzsi2yEojromgm
s7wtForvyFVKpOLy/AbxNuUwfy4a5AHZs2wHSWc3A5pf1zAUzpd3gMdFVtWd
a+HlZdHBk/6BcQYQXcFUHiDht2mGPA72s5l3GxiiPg9Lb92qbJq6kRngJ97Z
urI7O8yKfH5pNgzIs25gn22WV9nRclkD4wOsPObNlUWDsCCyzE6IIcHnagHf
nRbNVTkv5NtpdlzRhC0geHad3/Aq4BvnB83CoDTGSb3Q13G5MH9YrQKXxqzw
wbxz15clrD3PWpm6+Fi2BDB4Zussdu1+Gti9i6bJmXPhAzgbQKPLtk2Ho+KU
AgEnY5c6r5yAvIZnZvGuXRdzfapwXfGx2+TLrL2puvxjfKC0sbIhDGzWTdER
f4BlFVW2QWTMW2LM2RvBD3Nq/uVXL394Dwg0rxeAamHt87ppinZdV/h19ub4
dfaOSZkecU3xPzbADpk68rat5yXwx0V2fHRylDXFRYk0hatpp47JbFUugAKc
ewCI0DX1AjAUF/vpQYkfPyP1FXeTyadPwng+f47hWQC9tl1Z0aQOwFRcFc1N
NuMBZzd4rAoGiwE7sLXdsRwlHEOOkJ1mR/KmU9Li39qCCOfvRVOjIF7VQGMy
BWEFo9qqwPNu8UlBkaZwiwLJFjjKAlfDsI8ABceYlR1MvQShsLm45KNb40sA
58AfrkHYwG5uRP7jLDLheJCiBWbAoT9/5ifk+1UNrAPIe1VXyxtHCANLAP1j
Wd/A3zR9xcIYhsaHLMgHOBNxH4BI2YK0yQBDSmDD8AK8qMyyDUqXZY8J91sB
e7jMr2CJuE/Z3fS3MGiaocPH15tmXbdAZUdVeMqZjeRhBzw7vASsF0+7t8Wv
snaD52legc0KP86zUZ8lj5glo1iX6XELRQNicJGdNyCZWTt7t8wB1jmgLCmf
r1D5HON59HkmH/B1fsc4okfBKLNNly3LXxQ1cERcMm/02rOKHE6tmuTzpq5u
VvWmpUVPmTAjkQLbV204FSmWR48FVSMOC3pAtl7m8yIWQIbVy0kljJ5OynNa
lJAOKe4wQ+J4C4rTTfYn4JP4YCw4Ei6BLzGXwxdv49CFnY32h+/25NjYgMNt
XWwiPYaXHcMpXgu931v4lk1GCy8cCyyCN3xDIwGQ8dEGGU0N6IHEDuhGyD+g
iuAohr/SYMz3RNyJTGwi5hcGmt04y+tEyVAkiqFGRDeg3CCTBkJWdqDryszu
BExh3Twp8KSFcFfGZiZE4RRISOdlAzOtmxpZBT376dOwiglyB1kL0Iwj7H6F
6lHR4lsivP5Y5ECXIGxYpHqJWnwEXl4i5wJxnppQVyLonjI4cU1gKbYoZYl/
qlKwYHsVWTM8ss4br8jxiM6brrgbFqL9rQRd+vPnnvpRwKho68ihA48tSVJ7
ejWwQ8bD0NbZxllbe9VOH5sDicwK13awt7xZlH8nGHtLF/ZHrOOGNlTON2Cz
GQSAHV/jWwDLFVg8YAi1q7EjJXNZXqDgBAzzDIrV45LsohuGpmo3IjuHhKQD
aG7WC9JhQDwbkQko8x3yzqG3xsOyRwVTGbQtEp/I2Vx4elEXLGnmedPc0P47
QEC05+aAIt5gqlEot/OmnCEILoFjd3UGeN4VTmgQv0gUD/zo5x+yFYgDKDzc
LRxUdIYtAgDsLDCkzRk5f0a0LLSKRNtZAAq3zD0qQ6zIdDwDYGGFKwKEmhcL
mBC5h+hRul1mRUIMA2YQ0b4sqVgwrvhBLFzzGTI/AdtluSbhjGyqhGXAmzQQ
PgKbbuf1mg27zhLMV7CbgtUC0Q7NyknWn9NSy8rdQYgOleNXdXWFwEAw4bJf
ewJsmXf9UsBG6mbRZqPvP5yeoWMI/5ud/EB/v3/zpw/H79+8xr9P/3j03Xf+
DydPnP7xhw/fvQ5/hTdf/fD9929OXvPL8G0WfeVG3x/9ZcQUNfrh3dnxDydH
341YRbEMhPgyHHwR7BLSL5wgMfPXl6/e/a//uf8YKO2fgNQO9vdfAGflD8/3
nz2GD2jG8GykevJHwIwbl6/XRY5mD2IfUM+6BJaKggjYAJBHlaEWCuD88ieE
zM+H2R9m8/X+42/kC9xw9KXCLPqSYNb/pvcyA3Hgq4FpPDSj7xNIx+s9+kv0
WeFuvvzDvy4BwbLJ/vN//QZQ6C0hKIq+VY48tmFuYE5oHDRA9WqOEFNJD0TW
UpzDW/BHTiYwMfNNu90TIvItDAgm1eCAzvAN1bS98imW6vFrkdE83IBCzcN5
nkevBW08sDy2+WA+h4OSFm74Yz7AN7xKYU06XilZI3mkxGQ7nz6dFmzFPpru
46DeNt1lssjN2PB04DPwxFducAklgRm2WLMHaNAMcbdNHcHvNhVzlO28/dO3
J7sJQMEinImeBwO7W30n+OOA/0QOecxnkKMkJlFDg92mrMOCTmBBiSERb9ds
mAR0vGGSKSmOCGOOjrWHKQiLQxc0Sq9EWqwBQ6rA80KeP3B6pKFmQgPuMpdR
cGhEAFrchO32FlfOWDkgwKKBWtde4kJkkYymbHN2W94f1eejWN1XaYu2+QCd
wDSkupXe/gWtqlieK2EGGoFjB30OnwCVLnG8MGUxnM2xwHo8CqFsGcIn/B6E
XQ6byaKHET/EQFPpE1s/IwKIMpIgbxMtjoQrPAgSdl6sAUafHszh82fn3pCr
yCNtVWcr8nWhzEFiVLvoo2r6YteKbw64Av6Aij3DoEEYAERg0OBYI8kzQ/Kq
WoB+o2yv26yXagyDdoHqFKp5YJsVRItrQDU40UMQZ4QtQ7DT3yIDUr6LYcVn
MkjPICzKuSr+GX7d3WTsA2zL2ZJdKnnbgsrtIzFyLiB7Udh08D/8aVOVaLcA
rFDlWgJi5ld1ueBtAXkVorl5Y0/Y6g1pVyjTeZqEX7VT2Ay6s3JdfksHm+5c
XHVIMgujg4dBUbTBJHLgpLw6MZlbsZmDVekXKYTES0goWVaRWuXkXDIrgIlR
u4TxNmUL6mzRXRdFlSVzOzN3NKk815s25tg4BOncMQLdbmU7YxYsFqRvAohu
xgMS4XZvOq4/jgYQzwe2NRa8iN2IwQ7oe9ZxLA+bmGN1nj/SCZLnfYu7jOc/
OUFhNhRCsJ6hjNzn7NU3tihQQb1p5oVwARBFxcLBYdK021Hi+2BXoDcEXR7D
Ej/2DVslw6Vqg9jXw1w/oAyZ3KS0LMpzEIWwU+e9xCq5UzwT/acm7BkQfhXZ
6SAX3FDoCTnsg0HEQFZraPYWHhTbliw/5TyNgS8uXYlE5NUFhiC2o2UaOoos
sqBXHERahbjaWozng0Uhjg5Zy4gHkwwC1FAGtz3yjI18msNcl3jEpmLW5CSY
qJjMm9tDxnHw10cHk32AcjSSKKdgIyMj8Rwuv2U2ijmTCwY1cnojZrPq4LLe
klTpR9tL+AQuzsjowddjt8k0e4O0EFbIq2hjmZLlc5DPLDVq8vGgabeul+Uc
SHaa/UCiGQCAenG7aVi8INoCnsYjgfzWKUhVID6U5au6ukDhBLIgBkB4HtHA
HK532ZAMg2XNa1oiiE1aIb+1KnycpqZF+gGQSuKpkjgnL5CFxLwjD3y7zue4
3+jcV/mNnp3HSmA9RVPOs6t8uSGKmNU997vEZiP3DlJRJ4EbVH6aYsleXmRc
KqM8i6D3iVcK7oExTjjAOirxbFzNVgnBHBIA8SPNyaYjBzlTRSriBjXFwSIq
N/FMVK9xGGKRPbOkTyEcg8tE4zRHHNkaBwlXEI2dYqbJYvMlSJwWCHi+3CyK
W9gRTDCf1c1EVUO2YI4Apa6j8CkI3xETXuAzWU9DjjEXQ0atUwZH+InR1aWG
aQU5cU8RfAhl2q1A+QpUFBRxJRhzE8KD1juOdbUoJEFWY2SwhsXKiEEhd6SQ
kx87X/pB4FRA4YX9H5OmddN2xSpQGUaZy0YcSfW6aHLUQzlCqfuI/NEUFUdk
ZrJ415RXSJof2iKhcDiENf/olwJ4I1tQ7HB9aKdhxbFxd6EFIlIwnuzTg1g3
wNOOFVarmomdVonqVSFWCyn4daA9Z1lcIkY0JwUfE00vZgKGClQXNCRApkrw
AsUKMC5eTUlrXPd1t2yL7ua1Nu8SoPG+aNm6FV3OKMo2ZB6r2G2k8zmv83l5
T4rfkKJ3j4W6fqCtVZXvQ0UB1VzjiQIS5DPAQc/Lj+hz93obhftciJHdomNZ
BwMrW0Oa3oBaiKy1rSl0jv73C447YkyhRIl75A23JB7riW2V44bgBYaPrEoV
v8EAQiSRyovLTmVSInQIizDTACRvx0okUnSB5wwTcT7kmA3n801F3HfsvP6w
RdU1IQSTShCdp8Q8nZ87Rl/yr1Umwhg5N9Ksksi5gXLA5QtQ2kVXvxp0CBnl
Go6MnqfTYv+OCWUax1MUqB1L8AwW/rKY5xuOpkQ71AkINTnazFkdEWmO/Tuk
ZFYLMcK9fYBPt4GSZ2DAn4MiRJrvrCDMMQZ0MCuYfwLzzINCZh/okZAcHWkJ
9DJic1vMJ5sqKKciFRPVzCpY7F2EB4J2FbwsPf3Zef35mEwu43BnaEfTUILP
zt5uJpgQMUyD9WO0Asm5gZz6fEMxXI+3J5vgZcDjr+Azx5B3RU6csjjsyYtE
TDp3ijJVv53nPXlGWqOI/ViKZ7EUd6kUp4U8ILXmv+OuIzh8eoCQ4IfFbuvL
RFWtcVLEz1S58MBs6yVa/+huSSn2dlAdVV5qqO/ND7pVzzTPRA4JhxFGZNzV
hB5InDbeY4KqFOARKDLlAmz8TUhYaDMNI6ELlF5oKVgIs1Lwr21rxvO2/5b6
/3DbK7VbdfsYcLEn8n3+sVxtVumhrPKPd5yJV8aiN5kGACQf38q/XVyBbHLs
5IAApy82eQMgvMjLipLEItz+DiZZkgkBMpZTSyOt+XGqNWt+nedeSPrGBjlk
Ng/s62YNmiI5Z1bzw8cHLx6/ePrs4MWTKSanKNfCFa+r5FfS+Yygr+oBJ0XE
o3IAEpAenDVKsq0Itj09Ne+FPgS+AW/Gt2BKpPQNrJVTjjCNkdQKEsKaCfdD
YlaS2B+w5YPXIKS9mEQFUVdCph5uon+6h0F0NMW8QFFH9sR6vUSPMSUo5F2O
dnVnU4OAIy3h4YYlBuG76nEOV77UiIxPVckvCg6VKTLB2cbRrTGzZM09Ao0H
DPQkkYi4ygiXyLPo6kfZdb1ZLjITAKG0C1Doycng84dlWXN6elXkqDedU9hq
hqK36pRGtxsYnx4k9sWdlNriUaMRjDKrTbkou1VkPveBLI9+sANz9tkyQxew
jJSrBQWa5ZVGL/wszuRIRROGTJ7tu6So1BUWWaBhBooWOTkBky7Q93EeJxcP
W5G/m7tHeK6WmzNQovWKlof8LAcYMCrOvA9oVtzUNJrYOLFGB8oxxjXGHs75
gMnDudwcoPOuJV62KI3m1NKAxhlF6lukfkBBsXfZf4QDhrQvclYqShXlwovu
nnoF2kMSJ0CddzA0kdqLEpW3jMl4wWVYR4Y4rRfdHmoBJcgYpMGTSBZQ/qQJ
EZPeuz2bcWgBWbQAwjj23Z+73OZJtlG0RYy/rbaED5UyVM9SpeTTA6+TECmz
u4x9bZQ2fV6KeSU4EGc6DDJ7FzN71PSV4V8VEcdnX4vnc62N/45wncoDR7R1
EhjLZT8ItLPNLTWO/AkMwPhYdgntJaLO+1Yy3RbHdmnQJoFpsg8E8MAooyno
CmQ9U/wF4WOtUzKcht+UUhSAoy0OuMeifAbG7CYzKZCbqkF0Q2aHhkRlkHPc
H8iI/iQVKhJU+ZCiEkoHYECx3yQ2ylyn3azXddOp/swVKz4lB5FzhdK5xORK
j0QaRpxP9FeNjJ+JB/Z9zwPrtddPD8i/ykZZz+tGSLbkNA+WRVhg9vkznwD7
eQWm3nEK7JodUDxMmXJ4qZoUJjgnaEuFU++NskUKCLGtoXdbyQn203MEnrNs
OSNdfOjOkIwmxC5MQGP6BTpZsGqMnWyUUbi0qIIuwqa+ghXCJtHHme2w9EMg
TriaB/OExOPAOMLDcLlESBI4dO4//uM/cHuHP/3Bx9EmYfPfTH/+g/UwfjP9
QywCvqEB3Fmd/VIUa+9yT13YUqTBqBxSEZoN6nKo7d1QFgKeP6gSFJn5Ys9A
ovXmN/rqAWLG/4gPMr8s0Un6ZXZ8SyAZHlTWIpo9emOz7F+W3VdDAPiXi+4r
giQezPdHf7FLcO7NxxxQM+SIb482eFyXEzmvN5WIXjq2QkbysrdXTYx0lJ1y
rRYTjJ61ZsPA76GWy4Q3xDgMRBQfwtHLk7f6IpV7EI1h5abQGOymyCVAgnkt
0Rt4hKRAvj7+9vgs9hSA1qZUwsn5hG5ZPqvOEecmm6bMvqbEvsMRrnZyCRCf
ID05F32EpxgL6cNoOspiLHTO/Px19tPQSeJrP2cWmZ0bfO7rLB5UiqHC1/Hc
5gf/xWhvlD30fgA/XfIFPLjzXz4+2p88epF9SeDbdY7B+HUGP+zBD0xeJ+Kz
7Vin40iCIQ6jH5HrsqgoXEf2GB+TyWNyaDsBCuOLiA4lm2JDWfhjiTKSVQsU
ALgp7umh4OuWnHUxBb/4py+ImY0B/cnb6Mruvmai6vfBOyHC5UMLdl1EX4Tg
lFf26cFsffXss9R2taI1Jh77WQEKUVmzXEiqHYdCQI7UKWVGTETIv7kwkmUm
zGa2T1mqwg4o5Y5ylGGB/aoz9ZfzcVqvV7w9yqIyNR8uLW70NR/CTELphi9U
NBkknx4Yhz8zk/uls6Kj+f9AQqvh7VIqSRoaOiJm/fCBqVUcTB25HcasCUtZ
Qcjklzj032CQFrUjsm/bwbxaqnag7DIYKkpo1JLNvDKFBglgYG1z0PxQByCL
fVUjaUt6F0qElZcinDmYZKymLgxEYwQULkhkCgON/RXGsUK++uY8nwPdoheu
vNjwmiRaospJVCKk7pRphCb/SBoSysA4nTlfkuPsbdhBr/YVJcaLZ8/29vam
+88AnyiVn2SK+fpAXNdJcWy/NJbWTdwPi8BMNTxV+JTEAX3dKKZwFsbE3pLp
FIrJovSmIRyVeShTVKzNEKvF2snYINGI5t0RIhMWQl8I4X3fiI6pcZyAB3dD
qMOrJPxGGuJUX85IIJJUEuLAj9S5ID/sF8UkRdzfh6qeWyppuh66DQUv4yKb
Xo1N1quxSW3yAU4p5rl6xX/UFIBbAgvD5QdaBRkMUzfyg2BlQ7AxAu1EBr7E
xbfYpEKUW34ddvgeBp8k4Z5alo65eEqqt5vEdHzAMnAeYnuuj0zC7UIdfFxy
FQEWewN4486F6Kl3/t6xY8rWDdFC/71PueNCdPRxBKLBxi+HoKkVcByBTh5P
D6ZPpvup7IIT05r6SjgF7t6lbvWMM5Jsj4GL8qowx+kXAHu2riknTuKx1IeT
ZMgrLaQWGHISqUewgUFd2FdI7eOSeJ0AoZvCX+iDtDHUXYgJ8JynNCda74g5
E3QcOpdC7CCCl7ohtQRCx9WQOB44cr+B5iTTTIPU24pbtpW0jLU4CEcPSBTo
UxbhXXtxmF7ycyt+yJlIfRxNOEgxwyeE0LRNw75WePtdU4DKuWkdTfwS2Osv
dqjH08d9NBPSAC0WjKbuRldFq5H6XK/9nepDOy/fwd+htcUBnIAfYYbzyvFG
bm2pDDFxhoLP1v/ye13pYm0g47MzhrDEYHB5MKPKt7HZVMgKWvJtsHt0POAY
ojo/8hCYRYhMkAIJAAtxiUSusp+e43hy7Kzn50NQ42YHEWNj1mk9drkYDZhE
19RtT5TzlJiXSc5XqwQK4XD4aKYJa4rIF7Caa9KSJbNyKOQQXCnt5vwcM161
jQargBhuwQR0THyVTCKSmFS+D8Cca9kr+8pr9c3IC9TdZd7FKiWg2SCKWaio
iYQkgvoSMVMtQ/ckJ8V9LhIawA7p6UE4sm1GIbscCA0GC0UkDia9IlecLlsC
ALRkSjqPh+yrB5SBTlqWc6/Qt9Z2uIuQYcTcFedNYhGefEpNKaOCrOEQpUa7
hwMNVmWkmZPuE8HlZe2CWF3eG6voGCV4M1QpGQU2DlPIAyixjtju5WnP7IuO
sOxEW9ewLloEZE8UkudF4ZxknoJJQ5VrGzameO9d1YxvtirdSRTgPulYzqZW
DdaLGB0/mUNy0NO0L6vKD5QTyD6MZPRju3RT3GTnXDSEyIi+o/Iw2RkYQDqL
CQTcF2AuQllP5z4BNGVat8j6IXwwa9Z8w6gDU187uAO0R70zYdw2mEraZH6P
hbsVIYLKJNKwKXU8wvqVLlzrXn4swK74bxWWKPQDstf44y/44+fBQrHgCUbp
ROkjIVyUIinHoN3gEJ5DUZg1jU6FZaRrdHGjFOIvaY3LbVvUpiQj59PBIw75
NOaQcfc2Lu/RhEYVBLbMX0XRdBt3VoOYc01IixcwJaLhjTeDEhfjvXjHQCon
HP9Pf22v5hNYwM/270Ppu9LrRSgKtnRPkwI1ARs11uLCxdkNtXTkU6DYBrz7
BcpgUIAAYgv2bPz4LdWitEkxCnUJoSQQHo7GMpOQYpZT1yqKHZDxNcePrOzQ
tGP2rI7D9FJGi1kdt0QKrXcXSx0GLI6Yy6cWB9CW8c2GNgIyo1NbXXQT8RLK
ngdDf8rxzLCgn1Bmigb2XkmLspdcufvD7G+oaiTb3MG9i66OrTAp2QadTUXn
Oi6H8CkcY1bJ1Ket7S8Y36LMGIUe4/gZFQKnAUXZwFDpCU4SJ4pQgYkGGcX+
1uCV79ihC9OsPI7pP9IkFwKydZHfkBru0vCD5CZIJgSlbGB/r8t6iVmO2OIn
5A6THjC7oTqXKB11tvYxNWWDtFPfRYkxKRTNiIvHQ9Brq1H1Gbe1ug0ppEWE
j8DNBgLEtBKwDXNyEAIc5yhMObdi59GuKjjtGLlf3mBmmjeUhqwuqX8zehFx
IJpAFuFRMzfVurSONGeHqJPishQwpEZWgyOX22uSxvo6oASmQ932fq/Vp74L
ONXc/mrSEVS8/v4IQ8tJ37iBYDzRMdMzNOTjgm6exfrsYAWXr3WLY1ooMLrr
+j4TbjEGnlrvE094eGucm8vGMjnusdSP4RwkCFkRDGKOe615KK/BWNp+rK7X
3hRwxhT0aJUQN42J3PhKhANufM6h5KQ1VRaic3KeVP79J35xvP9svP/vP6uS
d62GsSI5jMI01sZRb7e/N6nnXdH5HA0JThMvQP2ou3HPD7Lk34PsYPJGIOQd
xMpJUBLuPUqe3zTlZE7tBB9lO2lsdBdfeZ6+8shPobAqzAzwb/8og62/efP8
6fNsuC5aH9y340bFOfzlXvRA0tCBQs9vNw27NZXHo3zX/BOOJTD7tAkMR0Hl
5HKUQR7pfXa3cEGHXDBlTJyxxCMP12U3CXLSTI64J8WyMXmZ7F0QhSgQUedJ
1No8s/Sq3MaZF45CNq9vUJGHEYPWXZF9t27KFYp/crwRN3boYpToX27Xgtpe
VU8OiuXP5s9DUsuk06ZZm+cd2NsPo9eaCwCcIkNWwcbfuXT8ngFlY/syTqwC
OT8rl+gQJLFGlT4s9SK/E/OHV69OX58iFHCcfAlLX2AWG5DLnLMmy05yewdj
rtyNDhlPJVy4Kq5pLFP8LW70nDgQewdWFJHEJDn7nYYLtKYUxzFljGeUrdIS
mqFlm/vmExkTPrkdVLZr7L6gYXo+SF7ZRyl/IyeKtpnEE8YcAjp8KXikjuly
KtvyeQjpfT6PVausAmJYmNEMx73eOUPdqah9wB3JP6qavsYs+9ARLvsONrrB
3IqdV69ff7fLOUHYrB1dyAM5PfPFYumKcpF9nf0z/mcqblbs1O77KzgXfcRM
HQBV4JAb8tZn2enpu0PqQwzY/1U2nU4VTgh4dhjoS1oNbDJgCOtB+ccXnaPV
PExnejTOsq8GtUmqkzYq5c7Zy9f7u7ooarTfrmFh8pfsYSiRiPeTTQGPfEHJ
07FeVCA5QFsfipOM+DGYlniy1WW/z7v5JauxK/kzuOoz/cproOuiEe4knRIX
BWMZM6oQdeUeTYeotAQqQd4P4hJbSJ6H/nklqTdlM8iL2zj9tx3K/zUDx8WI
TWHdNluVJh7TGoKoKLlBI1BS2DQtALldrH0ZMiN8kxQU4tqw+oTuWy+ukMcM
mFC+oHebVvc4dfFWtY1WpWYDpg37AsnQflRKenwRghErQRFlG1srA19JJqgE
Fnxp4GfCr/e2VQOMyXVBgX/hC0SKcvGEBojITPcNG7YhxSASEHsiMDkaZSfu
x4ThWOPuQn377oYXbqjhBcrUMp//rP+9zaEinXsFwvGE5MFTPxMxffX2i/LK
jhXgZOTvEWuXM83YDzSxMSIBJAV6WcK26ibRehlEskizEQzZ+N5hIj7FgKZh
UmcOdksFKGkLMtTbF/VaKgWo8a3JjPgOfT4vy0pMZbyrZDLjj+R8CUS2wha8
nScyaoWmxtoI38vkvZFYx5QScY1ULk0RQEQ3xsDdUiCdkS+krZfan5y0q8B3
3WW9nsxuJvAfSoiHjTU5oHrnczGk9bzqCH6ldpGo5ax9rqU/z1h/B3NbDPSh
lFupzWPLnWmRNKA0K4a7onAzmk5Ky7Tdm1QFsIYmLpI7kvNIOdaAGAGUOFtD
jX3ZGoYdN3R/QqrzajJDPtgamVPwsEQYgZk23XXciuuWxvJ2TE7m45tNRBRh
R4WxtiJ0HDInU5prXQPEDn1sPcq8kjEJfOR+vCHk4mjllu4FxBGV3co9FBT6
lj8Jx7fdPQNIrw2Z7evUeYCy/jBLSSUw1sBj9oD3MI7FQWr9kyRdjGfM1GLo
inzmousbVfQEHE6xGuvtKqyXDnV+XgH8lmNqJ+kXSc+N/UhYliNfUaNj7PpD
eeZkDKCww+EigSZOiu0g2xWvXnBe+rsWbt2R1/f7LaNspQ+63OS1UdLZoLf5
hGhL5SIIqU45boh+OG48WoQmir0qN/XXBVWb6EAi794B4vzGWpsx753lygmO
352ouSDIlR1TG5uhPmMHrEpsh3wMKBzbAyp78xGZIPYqt/7eyJs7lvil8UP7
MLAeplwi4KjD/FyyvjAqGzqJI7TXeuELgQnPbERN6buyo7y9c7qK7N0JSIrG
jQD2I5FGx+YIv6cj9KQ6oSP97J0PCmLurSwEwIkOaCEnzlZ/cNHtNE7WXPS5
PJCNlqwMVLzRviT/wPRY44zJFoPq8Grs77zXK7HKNPjS08fxS5FDmDweQOve
/auURmYUMi5KxpEU4OtyuQA2rFXldKwUutDmt4jbWFAEApbLHStJ5kEtFsMM
crHYmM0MJJzzvFxuPFMGXQubEAibKxYmm5sClbCsVn138b1BxhucV84gs3XS
3kkSu+NAqVHXoy7/RQvgojtF7G0ijJKREYabUko9Beb5HaKdxdFgoiVoysfS
2mht1KWOQnkbrjWKif4uhjsWCtRSeTX5BtsPjAcu3OrHgyVXj/r0WHbGKaZm
K5rQ5wP9qpe6UxUtPlvJQIOyjUzdL/IDc8Rtj/GxK347DDTNF2XXW3QehSOR
0sMzLaFif9N5yqsGpMPAC7BID4zBomVc66O7zqsgZkyc1YUIE9/0A8tgfmkb
TjCL3HoPWrQswCrqUeytam+YZtcNFrZV6rC0Pka/U5JhzgKmN6CvuL/HcM42
10NS1FxvLBfyFU5jHHpeGPEf1Ra5UDFkoi47Ub0QqB3HnJWGGoseYFwFN5Y2
DU3hm9IzyQGEqLYMD2lMn1D5XWlWfDVrJlRUle1oo1oh1Sq0AiNHKejou2yz
vMXkuCLbZ5fDdmywNXPmhwmpRF8/JI8UfEefnf0QKut29Ou2XT/Kwivw8WAX
PWzYN90fJ6tZVia66P2vI2i4JEASQPE7noKlHBEyBVwS//kw7tiNyLrkXJIZ
5FupVUXCHRovBCQMLFaKvpic0mAnMmy55kSL4NtXeqgftftShUNkK4UuRLBS
XnjlvHAspWYojrWyBhM7ddLem6GLlDM+cevA1tKCWC+KR+0H3PRpDrZ4PUiv
M4j1h7i2NnGXsMTvB2vHXJKcpE0OH1AcVQ+sg8tb1EAwkkK6TGO+PPPt/lAJ
QLAwMUZ/W59jTQVtYs9pxXYkuWmOpKAjBOG0VUWOFpSilkv0rWS403QaCqcG
DjakTfCqBwW4M+miES7tP4uakgUtgSOupmY8xG6/DKR1+4KSpdCGeZHcr21L
F1XbJ1OLN5hIeonkKFGiPjC7ZsV705/2J/sHz36e7gdXOhmyiVYgyUVnmhfz
W7SC3gv30gruNN58/J4o3LqsEyoceyWcLvwSXtNGeoXJXNGy5XLLfYeUnbNj
sml2I93jIBKsridYMX6k4flEsEbc38tOVXMrkcZlJ5KzjUXnwT1FJ4Wm/ll+
YdEo8SBxN8D+/7GIkMggiQrJJ4kMfcXeDoRCmlxlmtFi7py3q+gtvGlbLTut
rRSOhF7dR18+irUSjQ3dxgcDYkpuCNcAWWa3LWPD43tE9v/+5V0ZF+beif39
JONiHKKuEeA1W6zn8HEGI4fSNfaz/r8H1jUnnbOrgjxKlHwxkOIR7VeeywZS
OyL02ZLckd2Z3+HFz+m7oCbdO8Mju0eSB/x7+8Q+EzPhQ88ish3Eul1GpJ/+
qrwQqO/n9PNh6sQjAs38VeAUEKP5b6PQqfbq+PFbrP+gi3UotbuWOkG2gXAY
vdJvfpMkP3ItDDYTLHJCRC6hVv9duJpK0h84TUmKm+M60FA51Y+NyS9pOwFG
b+ndZS+yC8z9eRTgE0v0Peim6tYnZ6rqQPObuN1DFOYf6nfsA7NpIzLnOwpZ
j3dQBHkobppLJMj9JfnSXPgBfXa+H5YjHz3pgGEtrRj8ZmYR22lDAlaWpu7P
ReMzB3ReZKw5gc2nFekolCmDl89e0KlIqdzL45e7rsubi8I3KeLI0BdJkk3U
O2yG1flwJrYajnqaiz9T60/Nxb7SPCHHIgcstnxFri6+Xtq58P3cfM8BCRGH
edVZlZHbbng/zEoHcACcwr99WxQ9uy2Kjo51oJaSAxA6uPT8ofWZpCRfQqY5
0IuSCqBCpVU93D8q7i9MvZmpEi1f5Rfh6DB4c5UvvYNYL246igq5QKoW1DzJ
OL3k0s2o6lItM1K1UcHzFadk1+ttfahb7HB4dVFIteXStoIU/DbFmVzaIr0n
27D79pLgc4X4esPFRRt4BxU9JVlaDFVScn1y1Duu9IVsIGgFkT6YJsRx/41e
i+L0hpdtNa/eQ0JjAuy5zUNUdr2lo/egridGjRBiy90OOJLlVEvhDNJSeuO1
EnabYxvhOyKTU+ELafne0ObiWplZUhoW2o04KQQNTVzhMMt1ScpMphdBcP1i
rqFPvXyoOmcmmGt41ST0cYeuSyUT7HxBt/OI0jLAS8ij7QudtFWGH8QjEMod
ezGoiWkwKmX5PODRf0J77twNRnOZMIlqhuK53DOf4qZ4c+iNJ4749LZWjfnl
ISepQpmdKSYzOcnJzXjUNt40/OjaKB3ANF+RkLXj8niexXR5IaQxMmJMYw13
h6Wq/TkyCTVjvFzh9J+pbYwb18DKIQeUZYvB3DJ1n9boUXdzbX+OmfAyPFsL
pFwNuFLkWg4KD2+/v1er64c7SFCUTer6+kzKN/e7V1+d+zYfdLc3Hwz3gW5p
PhhnMZB5fGtzjuTShm3tLGilbrBthh/Se5edoz7epue/mEZU7W1uP5D66rL6
G4vbqNORpNE7m6ZCpyr07yWppHmBRUkVryTCmQNZPikhW+lwKd07QvKLcEWQ
UwhUr5clHCLSFPhusktYjqTVyBULQAl4btinme5aboEo8gvRNtf1Nfoouf4L
1wA6BHZ14pVEBZrhHLHvEK6ePZI5yVN5Q8LrLdgsGJlryC5cbJYF9cqvUJW6
whsZfGGs4bbeXlVEss4MF3cLGhCmof6VwQJMk+7IpSIybmBN6VvRFfbsawm9
BgKKzD1Vzwol3YW9GiWtPtV2BKZpjmgwfJ+NXEchJ0lgCgWlY6c9RCgM6Lv0
sN45LJLGytnUwkIH6ZZWt8XHUA+sfjxlYpHaiHMgVwNt50JZumSyybVCy6BK
hkt5hrtODddwV0bO9LolDem1pvLSZKyzFdompE0uLzAd7IlFKUm2YFrbSxks
7xdfu9tvZUm7ZkmPC3Nbll/yddleDtcst9RgnLHLS+ZUsyq5WTDfPIGKEzZS
lfx2usEr7ge0nc/3+h6fdmDltVj2CIyCZExNnIMlS0Nfxy1knvYa7lALK4Py
BRcrtDy0jMFKpUo5oobW803cXKgw2tnP/mu2c5B9me2cTPZ3d3fjoXw3eEeZ
ZNlJ6K6jByhHXmls5VKvlDPqCp/WuVyqh3Z5S2l/NvMLX6e+jd42TjY1I4pF
8bGQ3sFU9UCxiYq/9reZsxu1bH9hqiSz56oIAqXJsfMHZx+BZF04juFS9+Eh
zwXD/lxKgcwZeCszo8IBbiyXrp1zDhNzswAth+QfCGO8eaQ+n2gT7rzrcmpN
c8a95mEf7OEgRONUhpCZrZCWL4eaAGZHLpaySfcQb3xKBqGRqtiM7oJZKB4u
aX0u7lJB/CfufrCtX3ToKC6IwGbnWDMj27ESI5c4wYeiK9hwWd/Q8gRHsNlD
BOSpdMLSZSTYo69FF3NZmgiKK9DsdbghybRXDCrk8B5RsGCCNv1X3nehYz9t
HoEozGsp3gGUC7pMsjSai0IJSoQg/zyhtjSRdqYnVsNbgPjL1fbOYoPODMtI
2hRmVENJ10DECpLzCpLmJaQAbaUYGd8kZJZM7dDACu8yQA9W4wKAjcoul0Ew
r75Co3ulRfVsrPUhgtm8Sa+gut/RVW9go4g0S1cOsEVZRQOMl9P8IuZo2BX3
3SMuxPbK6R9/+PDda0qB9hibgrfSO6BZmx2iZgz1cn1WRcV7RsPQBkPivaox
R14jBkOtAcX0LxbqFejxqLt5ioucn8J2xwNWIF54xqr8HDhf1cWk5HtDqnI4
z9f53LhiB043O8lXnGH2G3UZ0fb6Q5pOiRyq0YMRDzlJ8VUNfL1uvIU+zvCO
IxO5WmzmWulRmcptlRWeZesq9EIKkUFBR79XA0xyxN3VT0Na5el20r5CLp7J
qmpcA91JUoe6mbzlDoAReOBmkPpr37iD5FrqQfa3wkjzdXvflxrmHsBO76eT
DqiYna+eb/E+Ga95XE26xSfFxqdvBwRTikOzT83IuhtSQTaA98sb5YpBD/ct
55y/qu7W7nGo1Unfts9x/6/Bhm6+eEgbgeWswWiuaWeqIHzbM2sntxRNiu/F
oqtTQrs1LObJL6jKg29nQbSXIGsZ5Wrhi3LPUucVKg0UmFvobXOSqnaoLaC3
oF4uxPZThiKCKm71EyQqDKlYNshtquyWFmct5VNie8n4GhfCR79qbXVNBL4C
bY0AoRdxEdpK0oLLZxsf/ngJ4mvyBnZyhua+1KGTsqHhDGDKDWuYCpJt/cRF
6+P4IHUhx5YyLXlsgF7a0h+xGP3AiDfcjq5pcOUAByxfnhR4dmE9GlTDUzt+
h/fMUx3RWzJiWwyokdusuMpJE2vxIamNQV5fc9oXNwXSshGcqx/G0aZMpwVW
FOERmJT04KmNEHDTqm4e9QIXkUCd2iUWV3J672CTYKvSA+eeg/UkocbWr8W6
khlw3OUZlfvAO1q5VwOTwTEBO19i/n++MrVW4bqC1PkjDjpvQ+RVvrxpy/Yr
ruTqfe/7tgCLoit2MTWFrspjuggedvYyM7/hXydlNRGNqqhARoLsYDgnMeVZ
OSsA21F833CDy8JrkiD0J8v8BvM5vENeDGbqCQDIa6OaGRXmqJvk7NW7V99d
PfYs9bG5GgmxAvZ5RPpdyxTRqlPpJsZ+W9HDlcwE+PLvIhZj3HcrLNtJW9Hn
NApp75ebVU7NdWwOulYfyUo0kj2PI9lRZPrJ7SlHji7mIHvWpmYj99bqKNt9
LkqI9pwReaDJf2rFvy2Vw5WoDibDGa8llSYqRUFSl1vFygAuksaYVWYqazVO
qJnHyTXz0Sx148japO6hY5/9eK2jAo39jTBCPfTUQonSBCgjqJcigPlRn4dr
/flHvO8CHqC3pZ8TC9hO/SoSqQg5MzY0J83TPlQlJb++L0Qg2wvA4fldLdAd
meu+Q6JNVwCK0qXyNoX+mS9DfvbkxRNKnToNwDp0lOcE35HGgB/fFcgWMUPU
HYWui+3DhMgYLzBfIh7tjFL7gC4nZ/WywOSB7ISlOK5z5/XZyW4vh+DPcqnB
M+xre/UM02tM+emU2m8CLXY4/vGb02/pThfgqBf/hug9rZsLvMwFHuMqQO9o
bPiFs7cOYCoFWC0vst8oPF2UvaDlZl0oHmCe3JaTlrsU43P2l33REQ9M4uwk
4WRtN9v0NfOUb0ppMwhHNjHK73wEgFluVmhlcCaG6/XwvDXj7tfsz7SXX+F8
sSsZC55fQVPLPnSlFgSF+eAnuX1eW0/YnwaXmP3qfp3wP/3v0Kd/9CeYJcNU
vwzWgZxM//0aI4bN7br/T1jMHrgo7OjTYQYKwLL4enRSXAsM5WDvxLn3cs6j
z5im1c0W+z/7PwC1fzjxvVp8+qXNsdNWfL6TeS0/X+bc6YWaVNrMXERsbbpw
j06EfjoajafEln9edDDDDK0IiZf7JgJc0BLnpeNAPt9qLItDSnqENMajsPEl
1qX2tYn7fvHlZjgYTSmel3LJPZGTq9U40TusML6YGgvbtEUTF9mDycUl5pzY
AVrFxUXozch7Np4YgZGKIhqI7YlJgdbPku+rx93s9GQaV97T9U0h6W62aZZF
eXGJp9JcSPhTQ1K0hJyWQAclwUEs7tVrN2koWtZXIkWpnQHtRrofYLG8xB9t
p2jrTwbl2/aR9sRB7jVGS45bNMVEOxItucseN9LZ0pKIb53q5Ydro7a4qd9n
zsbE/HF2Kx3uTfd6UVxptED5iHFe4fyyrrnDrnQs4tNChVhTCVnO2d442XxZ
5NR6CdOWvdG6xpQdUD3w5hhGl8si8GofFgBhWy2oT9OR1N8GLPFqOWu7CyEs
FSewfGrpQCkl5IYsKKBqLg8l0fls/2DP3DiWdGUd7twhAs505tgm6BaL5MSp
bqVX5By1g3VbJ7bqDGGwzmDlaEW4Vqt7nZ8HqfTNls1oibOHPjsMAAs0TmH7
ydphtlyjO6TzRx2gDHz7uBuPp2xdQe6v+x0Et4QqCUPDfkimLBDGw5O7LZOP
Un0zu1vfdLG+Mc0+sNZZoDkwfJ/w2OI+23aUprfYIAV4d5o9HtIx3pMKl/z7
VSHGGP4uDBQUhnurBSj996fT/YNnvVmsKyv6BV85eD6dHjx5kryS0rJ9Ze/j
3v7e3nS69/HZ27dv7zXL3sfne/zKW/vKacR83qvjR16BScI78O/NXbN887W8
hP/CXo75AvIU+pEOs+0gYhL5HbQw+uzDgnxrBNN+5ssbbF1Mr29g1A9eDB5u
9bQ7Dg5AqWUz3QIfc4OqUOFQV4WjYobxwNNPnkrJIjeaaweeefrkySN+ipoc
6nOSVpqM99dHB/joOXp4+ElWK7BGjisq0OPOig1/1pVy8E3aa+Vk1EqCtdRc
2+PHQe6+sTtkY2jTvK13ePvUTL41ApkUKi8cyDFXT+hqZee06bAQrlPj1DuE
u2xRHjb3E8atTEE+OYTY1se5vcJYLm6VPj/JHd8+Scp5NTQk+YvH4Ld2M6fc
LmObGZR8Ee5zk46y7Mzh2PpSN1FWscagTJGNBqFSa33d79+vxsIa+jnmobcY
VL/Z0jIsdy9ejzmWXlbf8B56VlbI/GOu5tvsPQm87CvOd6H48/mm9alT/Zso
h2YwVeYREzyWY/tzdGz/EOvjZh4VnnpfdWnbel7mnC8g8eje9TtZLnWf2mGD
NH9WxK7RncUhFUkjwxy6H4OHwStgRA4+QGdqUoKfaWQQcAS8q1gufDKcGxl3
A/2UXMy+AWNnjvqqWiKJXi0VrBplq83NeNTcjVnGhEXEz/1v2AEV3zvUp+P+
wSAqkKrttaRAxoGID3wbQb2UQBlhuHOKmy+JdW2yO40ZwPXl3DkWLFa1ggwD
Qjbn6xLZlIgs0lCDGUlGkQrT7I8kOC0OUSsySkHwhknPG2XYW6Iy+mGkaZ6/
amCrl0DTOLxfgngsLndCjegwnV9qWUu/KgqjYQu7BWvWD7JvN+UiR77FJiFX
FGFTS7wktWtjBXpS8LdATq833gqREqT6/J6qRAj4Ru0tbXP4mIzl0ixUVtiG
syrFCgtIrEykA+QMEYmr94S+kdXcWGBHlc9dV9qb5iPplmqiUwsvgUyGF5QV
1Cbbe3GidtzbFhDrpYz3gBA18KIbzHYCruJ99+f5qlyWOVauUDS9LZZYgeNd
9luPwPkj8LYEX5fgXNIP8s5acgo02Lx8xpDMF5bgtK3HEWRRTdHjkMSUo8TI
etNhbICY1MBNZ5SDIxcsxl2N7uJ8Tq568GWzQxyQEc8UU/j6cMrsMHcLBmWO
egY2F3mlDlrCTkCHeRc0t9vACwCz73/BDTNM/4lYsxoqZ5OInKYyU77tkKT7
hyti0AywTXhb0v8XfTqQ4CRi4QbT2ePDIIak3jPvBur7BO5ZAuIkwcaycD9q
qkjSXkXIy80xfOdFr5SMtMgBGvctKvM1lnsVPUtcGzdFFcXSzj2Sxt5jFd8F
Xdss++WNTY4unNEZJDiBeVb3vTLXbtaXpNBGHeiRlCKAcbpeHI76PyX3rrzR
xvafHmD0MjSyTyp9fU1ci5Vu5g41CaZrKBMH2VDZQNQGWEoAvX7UY0ZyfdxC
YoC+bFT8T/reUEWmufHNN9ZwliUMdPl4cg/2CMaUWCCWd2NVRjXxlYdpVwOa
V65A98UWeSuNAFrTjOOJNuGgzNUSTLv7DGo6tmk2oAFi1IQvzJ71Z9+bPrFN
QD5Ip8yTupr83z6bOzqwyJnsP/nNhzAABnP/RgDGWWJr8YR3XHgcX24TQXpP
h97SBt/fxWOIMb5V4l7EGKkMPgOBrz46asP9ReJ3bM3NRSpM7tWHQhunYB+K
30XY1NWKKUBcDMNcI+436ZLCtfuiW7YF3dzvYgVt+dF6mUQ5I2yjHnLbsG34
ZpV7Xqhy/3tU7nF9yt4ePNU/JvnxydabUoYvSPk9zEPP3xDfPfHA0av/WXjg
fg/b2ftPPH7/7/+/i3V6fBYp/FYKS25GT4OXwu8osEnH4P4fpsK9LWDd2wpN
sGfxYoBlsbhgd8inQ9bui8XXo/N82RYSO+jn5F1Tm5CA+afzuuuylxI918J+
ruLzWW7UjD2JZwONl74rfT8GP/GUiqnZ1cJtD9OzsR91lIlnk1N1xs80df8b
DHngwJPGAAA=

-->

</rfc>
