[dtn] Re: WG Adoption Call: BPv7 Echo Service: Through Sep 21, 2026

[Felix Flentge <[e-mail]>]

I support adoption.

Questions/ideas:

1) The draft talks about IPN-scheme service numbers. Could it be useful, dangerous or both to have the echo service registered in multicast or anycast endpoints? IMC has also service numbers and the private IAC draft as well. I believe that service numbers should ultimately be aligned between those schemes (though not all services may be valid in all schemes).

2) What about the DTN naming scheme? Anything to register there?

3) What about having a BIBE Echo Service: the destination BIBES the bundle as received and sends it to the source of the bundle as BIBE destination? This would allow a node to check how a bundle has been altered during transport. But that's maybe a separate RFC (once we have one for BIBE).

Regards,
Felix

-----Original Message-----
From: Ed Birrane <[e-mail]>
Sent: 07 September 2026 19:21
To: [e-mail]
Subject: [dtn] WG Adoption Call: BPv7 Echo Service: Through Sep 21, 2026

DTNWG,

  At IETF 125 Rick Taylor presented a -00 of the BPv7 Echo Service.
Based on comments and discussions at IETF 125 and the mailing list, a
-01 was published and presented at IETF 126.

  Rick has asked for WG adoption of this draft, and this e-mail serves as notice for the adoption call.  Please reply to this thread (or generally on the mailing list) to capture support, concerns, or other comments relating to adoption of this draft.

  This adoption call will stay open until September 21st. Since Rick is the author of this document, I will work directly with our responsible AD to interpret WG consensus and proceed accordingly.

  The draft can be found at:
https://datatracker.ietf.org/doc/draft-taylor-dtn-echo-service/

-Ed

_______________________________________________
dtn mailing list -- [e-mail]
To unsubscribe send an email to [e-mail]
This message is intended only for the recipient(s) named above. It may contain proprietary information and/or protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect personal data, in case of data privacy queries, please contact the ESA Data Protection Officer ([e-mail])