[manet] Re: [IPv6]Re: Adoption call for <draft-templ in-6man-mla>
"Templin \(US\), Fred L" <[email protected]> Fri, 20 Sep 2024 19:04:31 +0000
| Newsgroups | gmane.ietf.manet,gmane.ietf.ipv6 |
|---|---|
| Message-ID | <BN0P110MB1420B82DD5AF5EF38FFE85C8A36CA@BN0P110MB1420.NAMP110.PROD.OUTLOOK.COM> |
Nick, thank you for these well intended comments. You are quite right that the document would benefit from illustrations and I will work those into the next document version. A few words about what got us to this point: over a decade ago the IETF AUTOCONF working group published RFC5889 and had intentions of carrying the work further. But, the effort seems to have run out of steam and the working group closed while declaring success based on RFC5889. But, that left the whole subject of how to do address autoconfiguration for Ad Hoc networks an unsolved mystery. RFC5889 says: "For IPv6, these addresses may be global [RFC3587], Unique-Local [RFC4193] or Link-Local [RFC4291]", but for GUAs and ULAs it does not say how to obtain those for address autoconfiguration purposes. What the MLA draft does is define a new address type that Ad Hoc network nodes can autoconfigure first and then use to later obtain GUAs/ULAs when an Internetworking infrastructure point of attachment becomes available. It solves the chicken-and-egg dilemma of what address can be autoconfigured when there is no other means for obtaining GUAs/ULAs such as DHCPv6 or RAs with PIOs. In particular, when there is no other means to configure an address an Ad Hoc network node can always count on being able to autoconfigure and use an MLA. The MLA can then be used both for ongoing local network communications and to bootstrap the autoconfiguration of GUAs/ULAs if and when the opportunity presents itself. This is why we need this draft. Thank you - Fred > -----Original Message----- > From: Nick Buraglio <[email protected]> > Sent: Friday, September 20, 2024 11:01 AM > To: Templin (US), Fred L <[email protected]> > Cc: Bob Hinden <[email protected]>; IPv6 List <[email protected]>; [email protected] > Subject: Re: [IPv6]Re: Adoption call for <draft-templin-6man-mla> > > I'll toss my brain to keyboard notes in to hopefully get the > conversation started: > > https://datatracker.ietf.org/doc/draft-templin-6man-mla/ > > I can't claim to really know much about MLA, but I do know enough > about sensor networks to be dangerous, and this feels like a > reasonable idea for building and addressing sensor networks where > there may be different, adjacent groups of sensors that need to > communicate both to their peers and upstream to a collection system, > when available. I like the idea of a self-organizing addressing schema > to aid in that and running as IPv6-only fits the requirements I have > for such things. > > I did find the document a bit hard to digest. I think it needs more > clear examples or, more likely, some illustrative diagrams to > accompany what is there. > I am curious to know what similar technologies exist in this space (I > have admittedly not read all of the linked documents), so I can say at > this point I am neutral on adoption since I don't feel like I am well > informed enough to do so yet. - I am not against adoption, just not > well enough informed. > > Section 2. > A diagram may aid in making this easier to digest. It's not > complicated, but the manner in which that section is constructed, I > was looking for a diagram to illustrate Router A, B, and R. I'm a bit > of a visual thinker, so it's possible it's a limitation of my brain. > > Section 3 and 4. > After reading, I definitely think that the document would benefit from > some example illustration. Conceptually, it's fairly straightforward, > but I did need to draw it out myself. Again, maybe just me. > > On Thu, Sep 19, 2024 at 10:02 AM Templin (US), Fred L > <[email protected]> wrote: > > > > Please remember to respond to this adoption call - it is important for the future of IPv6 internetworking > > for Ad Hoc Networks. > > > > Thank you - Fred > > > > > -----Original Message----- > > > From: Bob Hinden <[email protected]> > > > Sent: Friday, September 06, 2024 8:26 AM > > > To: IPv6 List <[email protected]> > > > Cc: Bob Hinden <[email protected]> > > > Subject: [IPv6]Adoption call for <draft-templin-6man-mla> > > > > > > This email starts a 6MAN adoption call for the following document: > > > > > > Title: IPv6 Addresses for Ad Hoc Networks > > > Authors: F. L. Templin > > > Name: draft-templin-6man-mla-24 > > > Pages: 12 > > > Dates: 20-August-2024 > > > > > > https://datatracker.ietf.org/doc/html/draft-templin-6man-mla-24 > > > > > > Substantive comments, statements of support for adopting this > > > document, or objections to adoption should be sent to the mailing > > > list. Editorial suggestions can be sent to the author. > > > > > > Please include in statements of support: > > > > > > - The use cases this will be used for > > > - If you are willing to review the current and future versions of this document. > > > > > > The adoption call ends on 20 September 2024, 23:59 UTC. > > > > > > Bob, Jen > > > 6MAN Chairs > > > > > > > > > > > > > > > > -------------------------------------------------------------------- > > IETF IPv6 working group mailing list > > [email protected] > > List Info: https://mailman3.ietf.org/mailman3/lists/[email protected]/ > > -------------------------------------------------------------------- _______________________________________________ manet mailing list -- [email protected] To unsubscribe send an email to [email protected]