Re: Interested in wireless ?

Nabil Benamar <benamar73@gmail.com> Tue, 07 July 2020 09:10 UTC

Return-Path: <benamar73@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 448803A0812; Tue, 7 Jul 2020 02:10:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level:
X-Spam-Status: No, score=-1.847 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, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RLdMA6vDwUSb; Tue, 7 Jul 2020 02:10:04 -0700 (PDT)
Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EBA173A07A1; Tue, 7 Jul 2020 02:10:03 -0700 (PDT)
Received: by mail-lf1-x12a.google.com with SMTP id g2so24322792lfb.0; Tue, 07 Jul 2020 02:10:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qzy32ogZm77zZtPlAYZpFAnfNLGZYrLH3AHukX+mQI0=; b=F9ls7wHkFdXMcuJ+ctTWC64gyRuJDE3onIJeZQZzH0MDYBc2uepTpfaeploNik72Hi RrORmOPt0QzHjY0f1ytLVVfHvS7jCxzXc8CjUeYKjvdBuOjXoG6qlEYDqgftPT+3/MRh +qeSNDmaZEpD+K+dM82b6ZVduHElXc7jHZqRBGr3PNN3rDljJki/Z3q1HITI8/4V1Gyd XPm+VT9eYK/ayS8Ri2IP0Sa1TKmdtfNSUt4mWizYQ8QhFw0jDbPKjeLxYftZiIyVH99n zlOZwSxfPZSiq/IXaC+P6SZsELnd7D9erdSL9QoHlpCHkMb6XW4LkFzcPobisjHLVDV2 Wcag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qzy32ogZm77zZtPlAYZpFAnfNLGZYrLH3AHukX+mQI0=; b=baFP408KUi2mOldEtnYT1Nvo9KcFSGRD8Q24eQGH6bQLywjmico2rBlGHhR+ebfATv 2JZadStgL6H75pGsDwZSyaVJUyBQa9jiBbw/a/3raUOfijiDmFB6blNV6JvfZ2HHdrhs hcXj3NBkg+CH6/JMdV88XNdj7gL8goPcclDZKddwa+BhRepDApzWSNiG8aFu6rvkZYfu sjv7XKifIPcd8vZkFIHCuiKS6V0NLS/6pokCpxQtG1DCoJyZIbjHwhK19jjJTaSZvR7Q pg3cCB6CUJ9Wwj9yBcAj3yeaom7OIPXeGTOj9HgNBz6RvTOLJj2sdCgPh4QNgunDhiUl 8APg==
X-Gm-Message-State: AOAM5337Ld4sI7j86WSYUBguhW6vg7lGmFs0TR999Z7wdOSi10AKEVz8 dOEtw9i2AiHSTIU8N5EUy7Qtc8iQHrvPxJIN3eo=
X-Google-Smtp-Source: ABdhPJxAkpUBhGkB0VS6ZPwaYMZlcK3dmCTjwxcDRIdC+Dz0nJm/HnWjpGiuVZpU6zgyY5d2lXolLNCttz63Fmy5LcU=
X-Received: by 2002:a05:6512:3150:: with SMTP id s16mr21473996lfi.47.1594113001811; Tue, 07 Jul 2020 02:10:01 -0700 (PDT)
MIME-Version: 1.0
References: <A26FA9F8-72B8-4728-B978-6DDD271EC64D@cisco.com> <d157e481-f5d0-7f54-2f62-7400e0394688@gmail.com> <49E329AB-5060-46A3-BEC9-66EC80056565@cisco.com> <2c94c310-28ba-01e5-a874-029509e9b653@gmail.com> <MN2PR11MB35650796E6B764F8EECCC2FDD8660@MN2PR11MB3565.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB35650796E6B764F8EECCC2FDD8660@MN2PR11MB3565.namprd11.prod.outlook.com>
From: Nabil Benamar <benamar73@gmail.com>
Date: Tue, 07 Jul 2020 10:10:50 +0100
Message-ID: <CAMugd_UXeJXsnn7=M6SA7thC4JbLN0e+h=Fv-WH11Uch9t-9TA@mail.gmail.com>
Subject: Re: Interested in wireless ?
To: "Pascal Thubert (pthubert)" <pthubert=40cisco.com@dmarc.ietf.org>
Cc: 6man Chairs <6man-chairs@ietf.org>, 6man WG <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000034727505a9d65ba6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/bpaNNL5KaIw7-nVWTGLfPoT4QIc>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jul 2020 09:10:06 -0000

I definitely support the adoption of this draft.

The content is needed and add more detailed information on ND and wireless.

On Tue, Jul 7, 2020, 09:13 Pascal Thubert (pthubert) <pthubert=
40cisco.com@dmarc.ietf.org> wrote:

> Dear chairs;
>
> We have had a long thread on the adoption of
> https://tools.ietf.org/html/draft-thubert-6man-ipv6-over-wireless.
> I have seen only supporting comments, and even a path for a proper RFC
> type indicated by Brian below.
> But I have not seen the action on your part.
>
> It would be nice to make the call for adoption now so we could discuss the
> result at one of the IETF virtual meetings.
> What do you think?
>
> Pascal
>
> > -----Original Message-----
> > From: Brian E Carpenter <brian.e.carpenter@gmail.com>
> > Sent: lundi 1 juin 2020 01:21
> > To: Pascal Thubert (pthubert) <pthubert@cisco.com>
> > Cc: 6man WG <ipv6@ietf.org>
> > Subject: Re: Interested in wireless ?
> >
> > Pascal,
> >
> > There is a category of standards track documents foreseen in RFC2026
> called
> > "applicability statements", described at
> > https://tools.ietf.org/html/rfc2026#section-3.2
> >
> > I think that is perhaps where your draft could fit. A little bit
> stronger than
> > Informational and little bit different than Best *Current* Practice.
> >
> > Regards
> >    Brian
> >
> > On 01-Jun-20 04:40, Pascal Thubert (pthubert) wrote:
> > > Hello Brian
> > >
> > > We may have to split the doc but for the most part I agree it is an
> > informational.
> > >
> > > For now I suggest to just change the intended status accordingly and
> aim at
> > BCP or something.
> > >
> > > Let’s discuss in parallel the coexistence and if there’s a need for an
> std track
> > somewhere. There’s at least the use of a 6LBR for address looking up in
> > unicast.
> > >
> > > Take care,
> > > Pascal
> > >
> > >> Le 30 mai 2020 à 22:47, Brian E Carpenter <
> brian.e.carpenter@gmail.com>
> > a écrit :
> > >>
> > >> Hi,
> > >>
> > >> I believe that this is an important topic that 6MAN should take up.
> The draft
> > is a good basis.
> > >>
> > >> At the moment I find the draft a bit confusing in one way. It's aimed
> at
> > standards track, but it mainly doesn't read like a standard. There's a
> lot of
> > discussion but not much specification. If I was a coder, I wouldn't
> really know
> > where to start. For example, the end of the Introduction says:
> > >>
> > >> "This document discusses the applicability of IPv6 ND over wireless
> > >> links, as compared with routing-based alternatives such as prefix-per
> > >> node and multi-link subnets (MLSN), and with Wireless ND (WiND), that
> > >> is similar to the Wi-Fi association and reduces the need for
> > >> Network-Layer multicast."
> > >>
> > >> If it's a standard, IMHO it shouldn't do that. It should specify what
> WiND is,
> > with normative references as needed. Section 5 is the important part.
> It's fine
> > to have a descriptive section about why WiND is needed, but that is
> almost
> > better as an appendix. The main text should be essentially the
> instructions for a
> > kernel programmer.
> > >>
> > >> Regards
> > >>   Brian Carpenter
> > >>
> > >>> On 30-May-20 23:46, Pascal Thubert (pthubert) wrote:
> > >>> Dear all
> > >>>
> > >>> Since there’s so much energy on the list these days, could we
> > >>> consider the adoption of
> > >>> https://tools.ietf.org/html/draft-thubert-6man-ipv6-over-wireless-05
> > >>> ?
> > >>>
> > >>> I got only positive feedback, there’s no politics, there no label,
> it’s all about
> > IPv6 models for wireless. This may appear useful in a world where the
> vast
> > majority of devices are connected that way.
> > >>>
> > >>> Keep safe,
> > >>>
> > >>> Pascal
> > >>>
> > >>> --------------------------------------------------------------------
> > >>> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> > >>> Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > >>> --------------------------------------------------------------------
> > >>>
> > >>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>