[manet] Re: [IPv6]Re: Adoption call for <draft-templin-6man-mla>

Nick Buraglio <buraglio@forwardingplane.net> Fri, 20 September 2024 18:00 UTC

Return-Path: <buraglio@forwardingplane.net>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39143C14F6A9 for <manet@ietfa.amsl.com>; Fri, 20 Sep 2024 11:00:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=forwardingplane.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HrFitXd-bDcj for <manet@ietfa.amsl.com>; Fri, 20 Sep 2024 11:00:46 -0700 (PDT)
Received: from mail-qt1-x836.google.com (mail-qt1-x836.google.com [IPv6:2607:f8b0:4864:20::836]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 244CCC14F68D for <manet@ietf.org>; Fri, 20 Sep 2024 11:00:46 -0700 (PDT)
Received: by mail-qt1-x836.google.com with SMTP id d75a77b69052e-457ce5fda1aso17511341cf.1 for <manet@ietf.org>; Fri, 20 Sep 2024 11:00:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=forwardingplane.net; s=google; t=1726855245; x=1727460045; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=duCZU2XE7txoF4PPw9gbUsH/og3p4Tnxy8O9KrEYZco=; b=eP5wPPaR2ZKslb6yfiJ/KvN8jA0QPct8UQ1KTEdo1SUfKrkeqoHLQE02C/UzZT726j 4EDmeGe/JPOK95u6sZUfZZw7OOuW3byOq4t/AeyYA9YJRk1f+udQTqlU2Tn7AGUHD48s DgyBRjWsfGUpHbLVnMQ2BO0oKLFIHE+fR43Gc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726855245; x=1727460045; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=duCZU2XE7txoF4PPw9gbUsH/og3p4Tnxy8O9KrEYZco=; b=rnW7GhQxch+WKCskxUHdupJd9wluEccU3U8V+2ykVGUoRzdQcrCqpO/1cMipyxu0DW ScEj/tUTPT14PbOci5KOeGwg6ES+kNYioXqti8egr2WFgNhQ8P71ixxlCPWyBo+mOOdU 94eRyO3lvTkpFZvLUEMzg2ivT4wSYLjVewAqrqJD2AjJ7r+2LnbHfHhQY8Bb/yXJe2Sl px/gXEE9pbJZhtVqnrnEjP4JkFziNRgZ/9R5S+DXwLGGFn3tT2L0jk5J8FQDuTNGCCMc WvC8Nv76ATv9oJMWyXvx77ILzOXRzVxSE6CHwUISzb/bmcXkZQTExjPBWAdPoRH49voh IF3w==
X-Forwarded-Encrypted: i=1; AJvYcCXeZzGfqep1gcnv/mST89Pabt3Gx0vpLZRLGeRR0w76Z8vqm46b8jR1wpvnRwoekYgdBWKo4g==@ietf.org
X-Gm-Message-State: AOJu0Ywf9/QZl7+phOGNsciAwGzMAG/ZKHtR+cLVNref5G9aN1Y052tr UZIBI8P5DgL2Bcm78BFofS3J1Stm+0gEwy1Z3lKOkUrcIgGh9K9o9syv8SRJON0nvMj3MrXJfgV JIDgGfExujiJJAoOMRpByPDhkk2+3CbrcTqXY
X-Google-Smtp-Source: AGHT+IEG4fbNZ+zVswLka3bEucc/UbX14UegHmu/gvH7zpOBFNKoX9losx4T8SmB7cPZ9COHOd6mttcpIjLKsd/RN7I=
X-Received: by 2002:a05:622a:2996:b0:458:3850:c7aa with SMTP id d75a77b69052e-45b226c76edmr51193091cf.15.1726855245176; Fri, 20 Sep 2024 11:00:45 -0700 (PDT)
MIME-Version: 1.0
References: <17947F47-8891-43C7-991C-AA93629C4EEC@gmail.com> <BN0P110MB1420FE0F6540D36A628AC286A363A@BN0P110MB1420.NAMP110.PROD.OUTLOOK.COM>
In-Reply-To: <BN0P110MB1420FE0F6540D36A628AC286A363A@BN0P110MB1420.NAMP110.PROD.OUTLOOK.COM>
From: Nick Buraglio <buraglio@forwardingplane.net>
Date: Fri, 20 Sep 2024 13:00:34 -0500
Message-ID: <CACMsEX_ESV5s56_+hE7QVA-qH-uBmTf=DPn4MDrXojvCbG8r5g@mail.gmail.com>
To: "Templin (US), Fred L" <Fred.L.Templin=40boeing.com@dmarc.ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: D5GBT3HCKYQDIGCS533P5LD4JYJZQ3YB
X-Message-ID-Hash: D5GBT3HCKYQDIGCS533P5LD4JYJZQ3YB
X-MailFrom: buraglio@forwardingplane.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-manet.ietf.org-0; header-match-manet.ietf.org-1; header-match-manet.ietf.org-2; header-match-manet.ietf.org-3; header-match-manet.ietf.org-4; header-match-manet.ietf.org-5; header-match-manet.ietf.org-6; header-match-manet.ietf.org-7; header-match-manet.ietf.org-8; header-match-manet.ietf.org-9; header-match-manet.ietf.org-10; header-match-manet.ietf.org-11; header-match-manet.ietf.org-12; header-match-manet.ietf.org-13; header-match-manet.ietf.org-14; header-match-manet.ietf.org-15; header-match-manet.ietf.org-16; header-match-manet.ietf.org-17; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>, "manet@ietf.org" <manet@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [manet] Re: [IPv6]Re: Adoption call for <draft-templin-6man-mla>
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/aAPV7Kjmuhba8xLhf9-QEu72fac>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Owner: <mailto:manet-owner@ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Subscribe: <mailto:manet-join@ietf.org>
List-Unsubscribe: <mailto:manet-leave@ietf.org>

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
<Fred.L.Templin=40boeing.com@dmarc.ietf.org> 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 <bob.hinden@gmail.com>
> > Sent: Friday, September 06, 2024 8:26 AM
> > To: IPv6 List <ipv6@ietf.org>
> > Cc: Bob Hinden <bob.hinden@gmail.com>
> > 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
> ipv6@ietf.org
> List Info: https://mailman3.ietf.org/mailman3/lists/ipv6@ietf.org/
> --------------------------------------------------------------------