Re: Interested in wireless ?

Behcet Sarikaya <sarikaya2012@gmail.com> Mon, 01 June 2020 19:11 UTC

Return-Path: <sarikaya2012@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 BB2C83A14D1 for <ipv6@ietfa.amsl.com>; Mon, 1 Jun 2020 12:11:09 -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=unavailable 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 8vKgO4f5I24f for <ipv6@ietfa.amsl.com>; Mon, 1 Jun 2020 12:11:07 -0700 (PDT)
Received: from mail-yb1-xb35.google.com (mail-yb1-xb35.google.com [IPv6:2607:f8b0:4864:20::b35]) (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 8E8C73A14D3 for <ipv6@ietf.org>; Mon, 1 Jun 2020 12:11:07 -0700 (PDT)
Received: by mail-yb1-xb35.google.com with SMTP id n123so5705329ybf.11 for <ipv6@ietf.org>; Mon, 01 Jun 2020 12:11:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=cHxy8tt0seIJOde20I52UkjXZ46v0b/u9DQLq0R6o+c=; b=T0/rs3l31DdTlcoYssY6Uvun/YcOcr3Ntjp1XbCUqKUHM5WSNxIlkn0MZm7dBLMG3r xYBQMuTneFfKObyMbNvrGu18suDvxneUfKMlnQNKm77I7xK9c+T4FagJNb3Da0KRaLr3 6AReuWWXW1BK2sWUXpXiOKIQpZDz1A1wS06Os7SWaNGlFmZ3IhFg49ij9214N8lUi/r6 Uq0R3VOiqqG7a2+gpyMhxmUeEVwvBhPlLxlnezojh8hhdbR5W0VKZGQ7s8g1o44v9N1T q/twzeqMqJkXkXzz30gjajkMIeBhuaYKdrsabc9IknlkyRj3ulYmy1kg1AQiGpYoshds kXxA==
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:reply-to :from:date:message-id:subject:to:cc; bh=cHxy8tt0seIJOde20I52UkjXZ46v0b/u9DQLq0R6o+c=; b=BzK3Ig79HBGERSKuIOu4BvvaWr3QN7jxTv18qj2RHFh7hCOarviU9HDzbnUpjdHw+B 9fzKwpTEgduYinfUd+62DMc5XvwwBhRVxoknA3uzTAF5U88kp95OXOsPNubWa0P9MV/2 JwLD2QNYHXj7pWOq+zVKIsbahFRhDGS8oDWRiyamo5E1npfYGR2JSUQ1FJA7ZmZHKFDm MIwYHr0AVzzxTa7UTGOC20fTGFTm6NbJu2yu6nTmxK62SqxQdCwC3gABj9wDof49A3rV 8gPIvtifL5wDiSrd2gCRnPfY7s2DfSMiUKnn1chhAzz2ZrvlB89tc+MN1vxEWK6BmOsu RJeQ==
X-Gm-Message-State: AOAM532qMDLyt/q8JVdD/3m4i01tYYZoW49F6GJ9u13tey3H0qw8sRXq lYJeJkFdEFyHkYR66XQ2VJ1dXp4eGQrCvFq6bLc=
X-Google-Smtp-Source: ABdhPJxJUhPJlvfsNZD5YzXokvM+Y72ZjlYasNNzEZyCcWIXHLdWjunuVFIUKpz/T1S4He3j4yf+8AjfqkjDPiZM5Oo=
X-Received: by 2002:a5b:390:: with SMTP id k16mr37373596ybp.175.1591038666609; Mon, 01 Jun 2020 12:11:06 -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> <MN2PR11MB3565BC3BF415667EB2D75870D88A0@MN2PR11MB3565.namprd11.prod.outlook.com> <4594894861b54c3ab6a3644829440a5f@att.com>
In-Reply-To: <4594894861b54c3ab6a3644829440a5f@att.com>
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Mon, 1 Jun 2020 14:10:55 -0500
Message-ID: <CAC8QAceZXg3SMhkSXfyEOQHWSv_p_WWX0qhe44BVQqEL=0pE2Q@mail.gmail.com>
Subject: Re: Interested in wireless ?
To: "STARK, BARBARA H" <bs7652@att.com>
Cc: "Pascal Thubert (pthubert)" <pthubert=40cisco.com@dmarc.ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>, 6man WG <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008c18df05a70a8e3b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/GL94GJkwdUUX0c8LVFkuIeZdqtc>
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: Mon, 01 Jun 2020 19:11:10 -0000

On Mon, Jun 1, 2020 at 10:17 AM STARK, BARBARA H <bs7652@att.com> wrote:

> > Neat!
> >
> > Many thanks Brian.
> >
> > Pascal
>
> Oh, good. I'd just like to say that Brian very eloquently expressed some
> of the thoughts I had when reading through the draft. This is an important
> topic. I'd like to see it presented in a way that drives deployment, if it
> really will help to solve the problem.
>
> I suspect that to really get high rates of good, interoperable
> implementations in deployed Wi-Fi products, it might need to get picked up
> by Wi-Fi Alliance. An applicability statement that helps them understand
> the use case would be useful. I wonder, though, if that would be more v6ops
> than 6man? That is, it seems more about using (and implementing/deploying)
> existing protocols to improve operation of a network.
>



I think this is a good point. Thanks for pointing it out Barbara.

Regards,
Behcet

> Barbara
>
> > > From: Brian E Carpenter <brian.e.carpenter@gmail.com>
> > >
> > > Pascal,
> > >
> > > There is a category of standards track documents foreseen in RFC2026
> > > called "applicability statements", described at
> > > https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_ht
> > > ml_rfc2026-23section-2D3.2&d=DwIGaQ&c=LFYZ-
> > o9_HUMeMTSQicvjIg&r=LoGzhC-
> > >
> > 8sc8SY8Tq4vrfog&m=_i8eV1zjwa6e9U_4dG_Ehj8deR5jGNQadCAX4NyOVRg
> > &s=S88z1M
> > > klplQDukKNZjL75ub8LZnYm9ZJBYq_cafJfzY&e=
> > >
> > > 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://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.or
> > > >>> g_html_draft-2Dthubert-2D6man-2Dipv6-2Dover-2Dwireless-
> > 2D05&d=DwIG
> > > >>> aQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=LoGzhC-
> > 8sc8SY8Tq4vrfog&m=_i8eV1zjwa6
> > > >>>
> > e9U_4dG_Ehj8deR5jGNQadCAX4NyOVRg&s=zhmY1Y4gPkDO08iqReP1D3y6I
> > UQ2eCR
> > > >>> cItaE6PV0kzU&e=
> > > >>> ?
> > > >>>
> > > >>> 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://urldefense.proofpoint.com/v2/url?u=https-
> > 3A__www.ietf.org_
> > > >>> mailman_listinfo_ipv6&d=DwIGaQ&c=LFYZ-
> > o9_HUMeMTSQicvjIg&r=LoGzhC-8
> > > >>>
> > sc8SY8Tq4vrfog&m=_i8eV1zjwa6e9U_4dG_Ehj8deR5jGNQadCAX4NyOVRg&
> > s=d4r
> > > >>> J3C_jWlTRhy2Hr3SeRSeCEeyC8wNfKBtnuG7VCeU&e=
> > > >>> ------------------------------------------------------------------
> > > >>> --
> > > >>>
> > > >>
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests:
> > https://urldefense.proofpoint.com/v2/url?u=https-
> > 3A__www.ietf.org_mailman_listinfo_ipv6&d=DwIGaQ&c=LFYZ-
> > o9_HUMeMTSQicvjIg&r=LoGzhC-
> > 8sc8SY8Tq4vrfog&m=_i8eV1zjwa6e9U_4dG_Ehj8deR5jGNQadCAX4NyOVRg
> > &s=d4rJ3C_jWlTRhy2Hr3SeRSeCEeyC8wNfKBtnuG7VCeU&e=
> > --------------------------------------------------------------------
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>