RE: Interested in wireless ?

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Tue, 07 July 2020 14:03 UTC

Return-Path: <Fred.L.Templin@boeing.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 589923A0CE9; Tue, 7 Jul 2020 07:03:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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_MSPIKE_H2=-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=boeing.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 52K83gjM9u0H; Tue, 7 Jul 2020 07:03:35 -0700 (PDT)
Received: from clt-mbsout-01.mbs.boeing.net (clt-mbsout-01.mbs.boeing.net [130.76.144.162]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3401E3A0CEA; Tue, 7 Jul 2020 07:03:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 067E3UH0026969; Tue, 7 Jul 2020 10:03:32 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1594130612; bh=xPiQaC2IIise1ahgLW85cwqoPvDZbBA+iM6azSCAPcA=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=EEz/RetU/ACCkrV9QtSgiMPMnMJd7iKmTulu3U1nw+kKz8dOk/LwysJ/rD8dL0jWe jPSPUUcaPLg7qfTwAqFd650QugaHF5rAteCS5zkUSui9uI++nA7HZt4zVRReE1iKF+ L1YV63+rqc6DlyyCauXQzCEZVXPX6Uy4gwQd6gxebGWUsn4G/cax4a3d94km+WNkfm N6aHZca5hb5NUmLObgNXLze/v7M6i9JmQ/cu/tckGD+4znJeITcn7ViBzy7vmg0g4S sjZq3Wx3bSYChPnvmoEpilQ240IsXyi4Uo/8vWu+xgGZk2ooK4rt1NZDxtFTbTdVhb 0REpMv1SUAWrQ==
Received: from XCH16-07-10.nos.boeing.com (xch16-07-10.nos.boeing.com [144.115.66.112]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 067E3IDm025496 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Tue, 7 Jul 2020 10:03:19 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-10.nos.boeing.com (144.115.66.112) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1979.3; Tue, 7 Jul 2020 07:03:17 -0700
Received: from XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8]) by XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8%2]) with mapi id 15.01.1979.003; Tue, 7 Jul 2020 07:03:17 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "Pascal Thubert (pthubert)" <pthubert=40cisco.com@dmarc.ietf.org>, 6man Chairs <6man-chairs@ietf.org>
CC: 6man WG <ipv6@ietf.org>
Subject: RE: Interested in wireless ?
Thread-Topic: Interested in wireless ?
Thread-Index: AQHWNnfqX/nhVMuy1Ea+e7RI89I6LqjBGiqAgAFNXKuAAG+3AIA5J0LwgABiESA=
Date: Tue, 07 Jul 2020 14:03:17 +0000
Message-ID: <92a335aa8afc44ddbea3d9d82a75beeb@boeing.com>
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>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: C49CBE5B02E078D24723DD9F66C3CADC6CF8FEB7F6435ACB89DEC95E192024472000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/urSMJbKrF7jXObpqG3gbLf4u9wg>
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 14:03:37 -0000

Pascal, when using the OMNI interface for wireless there is no need for changes
to ND and no need for multilink subnets:

https://datatracker.ietf.org/doc/draft-templin-6man-omni-interface/

There is an adoption call in the queue for OMNI.

Thanks - Fred

> 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
> --------------------------------------------------------------------