[manet] Re: [IPv6]IPv6 Address for Ad Hoc Networks
"Templin \(US\), Fred L" <[email protected]>
| Newsgroups | gmane.ietf.manet,gmane.ietf.ipv6 |
|---|---|
| Message-ID | <BN0P110MB1420846B00B7227FD63FE985A3B3A@BN0P110MB1420.NAMP110.PROD.OUTLOOK.COM> |
OK, thank you. Fred > -----Original Message----- > From: Bob Hinden <[email protected]> > Sent: Friday, August 02, 2024 12:04 PM > To: Templin (US), Fred L <[email protected]> > Cc: Bob Hinden <[email protected]>; IPv6 List <[email protected]>; [email protected] > Subject: Re: [IPv6]IPv6 Address for Ad Hoc Networks > > Fred, > > > On Aug 2, 2024, at 8:50 AM, Templin (US), Fred L <[email protected]> wrote: > > > > Bob, thank you for your comment. I would like to propose a "meet halfway" solution in which > > the specific prefixes are removed from the main body of the document but may be mentioned > > in a non-normative appendix - would that work? > > No, I think it's still a distraction. > > Bob > > > > > > Fred > > > >> -----Original Message----- > >> From: Bob Hinden <[email protected]> > >> Sent: Friday, August 02, 2024 11:35 AM > >> To: Templin (US), Fred L <[email protected]> > >> Cc: Bob Hinden <[email protected]>; IPv6 List <[email protected]>; [email protected] > >> Subject: Re: [IPv6]IPv6 Address for Ad Hoc Networks > >> > >> Fred, > >> > >>> On Aug 1, 2024, at 11:40 AM, Templin (US), Fred L <[email protected]> wrote: > >>> > >>> Hi, this draft has been updated based on feedback from the IETF120 6MAN and MANET working > >>> group sessions where the work was presented. The updates include: > >>> > >>> - Drop support for fec0::/10 - reason: RFC3879 deprecation has rendered this prefix inoperable > >>> - Use prefix 2001:20::/28 [RFC7343][RFC7401] as "Type-1" Multilink-Local Address (MLA) prefix > >>> - Use prefix 2001:30::/28 [RFC9374] as "Type-2" MLA prefix > >>> - Allow future documents to define new MLA types, if necessary > >> > >> IMHO, this draft should not specify any specific prefixes. It should all be “To be assigned”. Including it now is a distraction to the more > >> important question. > >> > >> I think the question that needs to be answered is: Is there a real need for Ad Hoc IPv6 addresses? Focusing now on the details or which > or > >> how many prefixes it might use doesn’t address that. > >> > >> Bob (w/ no hats) > >> > >> > >>> While MANETs represent a natural basic use case, the IPv6 Ad Hoc network addressing > >>> scheme applies to all manners of IPv6 networks and not just those that fall within the auspices > >>> of the MANET working group. The work is therefore in scope for the larger Internet area in > >>> general the same as RFC5889, but is more specifically targeted for 6MAN due to its exclusive > >>> focus on IPv6. For full context, please view the IETF120 MANET session presentation beginning > >>> at the 22minute mark here: > >>> > >>> https://play.conf.meetecho.com/Playout/?session=IETF120-MANET-20240726-1630 > >>> > >>> Please review and comment so that this essential work can move forward. > >>> > >>> Thank you - Fred Templin > >>> > >>> -----Original Message----- > >>> From: [email protected] <[email protected]> > >>> Sent: Thursday, August 01, 2024 12:49 PM > >>> To: [email protected] > >>> Subject: I-D Action: draft-templin-6man-mla-19.txt > >>> > >>> Internet-Draft draft-templin-6man-mla-19.txt is now available. > >>> > >>> Title: IPv6 Addresses for Ad Hoc Networks > >>> Author: Fred L. Templin > >>> Name: draft-templin-6man-mla-19.txt > >>> Pages: 13 > >>> Dates: 2024-08-01 > >>> > >>> Abstract: > >>> > >>> Ad Hoc networks often present a challenging environment for IPv6 > >>> addressing due to the indeterminant neighborhood properties of their > >>> interfaces. IPv6 nodes must assign IPv6 addresses to their interface > >>> connections to Ad Hoc networks that are locally unique but must not > >>> be propagated to other networks. IPv6 nodes must therefore be able > >>> to assign self-generated addresses to their interfaces when there are > >>> no IPv6 Internetworking routers present that can coordinate topology- > >>> relative IPv6 addresses or prefixes. This document specifies IPv6 > >>> address types that can be assigned to Ad Hoc network interfaces. > >>> > >>> The IETF datatracker status page for this Internet-Draft is: > >>> https://datatracker.ietf.org/doc/draft-templin-6man-mla/ > >>> > >>> There is also an HTMLized version available at: > >>> https://datatracker.ietf.org/doc/html/draft-templin-6man-mla-19 > >>> > >>> A diff from the previous version is available at: > >>> https://author-tools.ietf.org/iddiff?url2=draft-templin-6man-mla-19 > >>> > >>> Internet-Drafts are also available by rsync at: > >>> rsync.ietf.org::internet-drafts > >>> > >>> > >>> _______________________________________________ > >>> I-D-Announce mailing list -- [email protected] > >>> To unsubscribe send an email to [email protected] > >>> -------------------------------------------------------------------- > >>> IETF IPv6 working group mailing list > >>> [email protected] > >>> Administrative Requests: > >>> -------------------------------------------------------------------- > > _______________________________________________ manet mailing list -- [email protected] To unsubscribe send an email to [email protected]