Dear all: Sadly, we can see the diff only after pushing the publish button. There was an awful typo, so I republished the draft to remove it.
all the best Pascal ---------- Forwarded message --------- De : <[email protected]> Date: ven. 4 juil. 2025 à 10:42 Subject: New Version Notification for draft-ietf-6lo-prefix-registration-15.txt To: Pascal Thubert <[email protected]> A new version of Internet-Draft draft-ietf-6lo-prefix-registration-15.txt has been successfully submitted by Pascal Thubert and posted to the IETF repository. Name: draft-ietf-6lo-prefix-registration Revision: 15 Title: IPv6 Neighbor Discovery Prefix Registration Date: 2025-07-04 Group: 6lo Pages: 27 URL: https://www.ietf.org/archive/id/draft-ietf-6lo-prefix-registration-15.txt Status: https://datatracker.ietf.org/doc/draft-ietf-6lo-prefix-registration/ HTML: https://www.ietf.org/archive/id/draft-ietf-6lo-prefix-registration-15.html HTMLized: https://datatracker.ietf.org/doc/html/draft-ietf-6lo-prefix-registration Diff: https://author-tools.ietf.org/iddiff?url2=draft-ietf-6lo-prefix-registration-15 Abstract: This document updates IPv6 Neighbor Discovery (RFC 4861) and IPv6 Subnet Neighbor Discovery (RFC 8505, RFC 8928) to enable a node that owns or is directly connected to a prefix to register that prefix to neighbor routers. The registration indicates that the registered prefix can be reached via the advertising node without a loop. The unicast prefix registration allows the node to request neighbor router(s) to redistribute the prefix in another routing domain regardless of the routing protocol used in that domain. This document updates Routing Protocol for Low-Power and Lossy Networks (RPL) (RFC 6550, RFC 9010) to enable a 6LoWPAN Router (6LR) to inject the registered prefix in RPL. The IETF Secretariat -- Pascal
_______________________________________________ 6lo mailing list -- [email protected] To unsubscribe send an email to [email protected]
