[dtn] Re: I-D Action: draft-ietf-dtn-eid-pattern-10.txt

[Brian Sipos <[e-mail]>]

Erik,
Yes I forgot to mention that because this updates proposed standards it
must also be a proposed standard.

If anyone has strong opinions on the overall allowed character set
(currently UTF-8 less restricted code points) and whether it makes more
sense to define the allowed set (more like URI with 7-bit ASCII) rather
than a restricted set, please chime in on the mailing list. I think that is
the only unsettled issue that doesn't have a clear conclusion yet. It can
be discussed as part of WGLC also.

Brian S.

On Sat, Aug 22, 2026 at 11:25 PM Erik Kline <[e-mail]> wrote:

> Chairs,
>
> Hopefully this can get a WGLC.  I'm glad this version changes the track to
> PS; thanks for that Brian!
>
> -ek
>
> On Fri, Aug 21, 2026 at 8:40 AM Brian Sipos <[e-mail]>
> wrote:
>
>> WG,
>> This update of the EID Patterns draft makes one change to the text form
>> ABNF to address feedback (described below), further restricts allowed
>> pattern item characters, and adds new Operational Considerations
>> subsections to explain pattern usage options.
>>
>> The updated text form now allows the initial character of a pattern to be
>> the separator "|" in order to positively disambiguate that the text is a
>> pattern and not a simple EID. This is a relaxation of earlier ABNF
>> constraints. A new Appendix B subsection explains this with an example
>> "|ipn:0.3.4" to illustrate it. A strict URI processor will fail to process
>> this text, and even a lax one will fail to match the non-scheme text
>> "|ipn". This addresses the security consideration of Section 5.2 in an
>> optional-to-the-encoder way.
>>
>> The more restrictive character set (which constrains future schemes'
>> pattern definitions) disallows non-printing and blank characters, which was
>> recommended during earlier review. It is also formalized by a
>> negative-matching ABNF rule "ssp-nochar". I think the current text should
>> be good but let me know if there needs to be any further restriction.
>>
>> Brian S.
>>
>> On Fri, Aug 21, 2026 at 11:11 AM <[e-mail]> wrote:
>>
>>> Internet-Draft draft-ietf-dtn-eid-pattern-10.txt is now available. It is
>>> a
>>> work item of the Delay/Disruption Tolerant Networking (DTN) WG of the
>>> IETF.
>>>
>>>    Title:   Bundle Protocol Endpoint ID Patterns
>>>    Author:  Brian Sipos
>>>    Name:    draft-ietf-dtn-eid-pattern-10.txt
>>>    Pages:   37
>>>    Dates:   2026-08-19
>>>
>>> Abstract:
>>>
>>>    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 IETF datatracker status page for this Internet-Draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-dtn-eid-pattern/
>>>
>>> There is also an HTML version available at:
>>> https://www.ietf.org/archive/id/draft-ietf-dtn-eid-pattern-10.html
>>>
>>> A diff from the previous version is available at:
>>> https://author-tools.ietf.org/iddiff?url2=draft-ietf-dtn-eid-pattern-10
>>>
>>> Internet-Drafts are also available by rsync at:
>>> rsync.ietf.org::internet-drafts
>>>
>>>
>>> _______________________________________________
>>> dtn mailing list -- [e-mail]
>>> To unsubscribe send an email to [e-mail]
>>>
>> _______________________________________________
>> dtn mailing list -- [e-mail]
>> To unsubscribe send an email to [e-mail]
>>
>