RE: I-D Action: draft-thubert-6man-ipv6-over-wireless-09.txt

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Tue, 18 May 2021 20:54 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 D69FB3A0CB7 for <ipv6@ietfa.amsl.com>; Tue, 18 May 2021 13:54:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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 XhgqWgrJSwhg for <ipv6@ietfa.amsl.com>; Tue, 18 May 2021 13:54:29 -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 1AC463A0CB1 for <ipv6@ietf.org>; Tue, 18 May 2021 13:54:28 -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 14IKsPTP010303; Tue, 18 May 2021 16:54:26 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1621371266; bh=9gzMErqslqKCF1f78bgV3ILSVq6ulJtUBhDjTx5yJLo=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=dCYBgiL8bi2ZGZzTYGssrpMsvjepIPnpMdBiZXvvjd1+M+vO/dAqePZWAlLxHMbe5 aJGWEhLIFLE8FKkz+ubSnm29BWOa4CHIkWy7DJ+tHoThAlPZuKOLokdPp708gGVNun gYmaVD+XqdOQbUJ4d/2Zi6hoIw20cHfMvCIRQHD6mgcKwEMOE0c41jLRAHugIyhkbF 2LM+5t27yuF43JBALKi0STmOi3EjngKgWE4RVOjBlvSQXPWdVgN68+0O4AAvEASHT3 bEFs4mQvbifK2/8Zh66j1og1sOzxVtNkos53DIhFlNQJWTJxwn9eCqLCnHPhEugDLq tcS1dY9Hky8VA==
Received: from XCH16-07-09.nos.boeing.com (xch16-07-09.nos.boeing.com [144.115.66.111]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 14IKsCIv010162 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Tue, 18 May 2021 16:54:13 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-09.nos.boeing.com (144.115.66.111) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2242.4; Tue, 18 May 2021 13:54:11 -0700
Received: from XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5]) by XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5%2]) with mapi id 15.01.2242.008; Tue, 18 May 2021 13:54:11 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
CC: Vasilenko Eduard <vasilenko.eduard@huawei.com>, 6man <ipv6@ietf.org>
Subject: RE: I-D Action: draft-thubert-6man-ipv6-over-wireless-09.txt
Thread-Topic: I-D Action: draft-thubert-6man-ipv6-over-wireless-09.txt
Thread-Index: AQHXS2dZ7ChRBIoAkka6t/WVw/6Ig6rona2AgADOHRCAAAMiYIAAgV2A//+xt9CAAIdfAP//jWxg
Date: Tue, 18 May 2021 20:54:11 +0000
Message-ID: <38e009ecde2447d58ba95409f2035747@boeing.com>
References: <162126274647.25711.8162789738375511264@ietfa.amsl.com> <32c96d37-a743-f0fa-c858-36333b102d2b@gmail.com> <CO1PR11MB4881C8C2B221BA018BE0FF4CD82C9@CO1PR11MB4881.namprd11.prod.outlook.com> <db22fe3d2ccd4f0fa92e373949078bdb@huawei.com>, <22b24c0b429b48fcb2f48190012b9ee1@boeing.com> <A3D88057-CBF1-4E8C-B905-B79EBE24E1BB@cisco.com>, <762dad577e5e48d18f8bfe1ce23e936b@boeing.com> <5142B0F5-70B8-4447-AB3F-839085812F94@cisco.com>
In-Reply-To: <5142B0F5-70B8-4447-AB3F-839085812F94@cisco.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: EBBB0A25C81E150CC4E4C5FD5CD2564E0EB69A76B762C6BA5027C223421BCFEB2000: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/sAS1tt11-hzYfGB34_l202-PfYY>
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, 18 May 2021 20:54:34 -0000

Pascal,

Sorry to be disruptive, but you think you have a generalized solution for
wireless and I think I have a generalized solution for wireless. Mine includes
a familiar link model that builds on mature standards and BCPs and as near
as I can tell does so in an optimal fashion. OMNI is no longer research or a
pre-prototype toy; OMNI is engineering-ready for IETF progression.

Fred

> -----Original Message-----
> From: Pascal Thubert (pthubert) [mailto:pthubert@cisco.com]
> Sent: Tuesday, May 18, 2021 1:36 PM
> To: Templin (US), Fred L <Fred.L.Templin@boeing.com>
> Cc: Vasilenko Eduard <vasilenko.eduard@huawei.com>; 6man <ipv6@ietf.org>
> Subject: [EXTERNAL] Re: I-D Action: draft-thubert-6man-ipv6-over-wireless-09.txt
> 
> EXT email: be mindful of links/attachments.
> 
> 
> 
> Fred,
> 
> This does not tell me why you bring this work in this discussion. I do not see that disrupting this thread can help your work to progress.
> 
> I agree with Eduard that it is a good time to poll and see whether 6MAN wishes to adopt this work.
> 
> Maybe this is not the place for creating educational material such as this.
> 
> Whether this doc gets published here or not, it is my hope that we can debate and possibly reach a consensus on our basic concepts.
> 
> Regards,
> 
> Pascal
> 
> > Le 18 mai 2021 à 21:38, Templin (US), Fred L <Fred.L.Templin@boeing.com> a écrit :
> >
> > Pascal,
> >
> > Apologies, I should have presented the URL's in the reverse order and
> > recommended looking first at OMNI which specifies details of the OMNI
> > interface and link model. AERO is a companion document that specifies
> > internetworking considerations for nodes that employ OMNI interfaces,
> > but please start first with OMNI:
> >
> > https://datatracker.ietf.org/doc/draft-templin-6man-omni/
> > https://datatracker.ietf.org/doc/draft-templin-6man-aero/
> >
> > Thanks - Fred
> >
> >> -----Original Message-----
> >> From: Pascal Thubert (pthubert) [mailto:pthubert@cisco.com]
> >> Sent: Tuesday, May 18, 2021 10:12 AM
> >> To: Templin (US), Fred L <Fred.L.Templin@boeing.com>
> >> Cc: Vasilenko Eduard <vasilenko.eduard@huawei.com>; 6man <ipv6@ietf.org>
> >> Subject: Re: I-D Action: draft-thubert-6man-ipv6-over-wireless-09.txt
> >>
> >> Hello Fred
> >>
> >> I fail to understand why you present Aero as an alternative.
> >>
> >> This draft discusses links and subnet models and how existing RFCs can be applied to those models. It is a BCP type of work looking at
> >> existing stuff and trying to make sense of it.
> >>
> >> Seems that aero is defining new mechanisms and falls in the std track category. Where exactly do they compete?
> >>
> >>
> >> Regards,
> >>
> >> Pascal
> >>
> >>>> Le 18 mai 2021 à 18:32, Templin (US), Fred L <Fred.L.Templin@boeing.com> a écrit :
> >>>
> >>> It is premature to propose adoption without first considering the alternative:
> >>>
> >>> https://datatracker.ietf.org/doc/draft-templin-6man-aero/
> >>> https://datatracker.ietf.org/doc/draft-templin-6man-omni/
> >>>
> >>> Fred
> >>>
> >>>> -----Original Message-----
> >>>> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Vasilenko Eduard
> >>>> Sent: Tuesday, May 18, 2021 9:20 AM
> >>>> To: 6man <ipv6@ietf.org>
> >>>> Subject: RE: I-D Action: draft-thubert-6man-ipv6-over-wireless-09.txt
> >>>>
> >>>>
> >>>>
> >>>> Hi all,
> >>>> Current ND is not compatible with any Wireless, especially for low power or roaming scenarios. Hence, the proper discussion would
> be
> >>>> helpful.
> >>>> Hence, I propose to adopt draft-thubert-6man-ipv6-over-wireless in 6man.
> >>>> Eduard
> >>>> -----Original Message-----
> >>>> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Pascal Thubert (pthubert)
> >>>> Sent: Tuesday, May 18, 2021 10:00 AM
> >>>> To: Brian E Carpenter <brian.e.carpenter@gmail.com>; 6man <ipv6@ietf.org>
> >>>> Subject: RE: I-D Action: draft-thubert-6man-ipv6-over-wireless-09.txt
> >>>>
> >>>> Many thanks Brian;
> >>>>
> >>>> Though writing code and deploying networks is core to many of us, we also end up teaching, writing papers and publishing
> >> informational
> >>>> documents in other bodies such as ETSI. It was during a discussion for an ETSI doc that we realized we were missing those definitions.
> >>>>
> >>>> But above there's a need to regain a degree of freedom in how we use links and subnets. The lack of definitions leads to overloading
> >> and
> >>>> confusion, which in turn leads to confine us within the commonly understood model that is ethernet.
> >>>>
> >>>> As we separate the definition of the IP link from that of the lower layer, and separate the definition of subnet from that of IPv4, we
> >> regain
> >>>> a degree of freedom that enables us to build IPv6 abstractions over any new medium and build subnets of any size and shape.
> >>>>
> >>>> Happy to discuss the exact terms of the definitions.
> >>>>
> >>>> Keep safe,
> >>>>
> >>>>
> >>>> Pascal
> >>>>
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Brian E Carpenter
> >>>>> Sent: lundi 17 mai 2021 23:55
> >>>>> To: 6man <ipv6@ietf.org>
> >>>>> Subject: Re: I-D Action: draft-thubert-6man-ipv6-over-wireless-09.txt
> >>>>>
> >>>>> Hi,
> >>>>>
> >>>>> IMHO this draft now includes some important new material, namely
> >>>>> definitions of two terms "IP Link" and "IP Subnet" (at
> >>>>> https://www.ietf.org/archive/id/draft-thubert-6man-ipv6-over-wireless-
> >>>>> 09.html#name-terminology ). While I'm not sure yet that I completely
> >>>>> agree with the text, I think the topic is very important, since the
> >>>>> previous doctrine has effectively been that all "links" behave like
> >>>>> Ethernet. And, by the way, the socket API incorporates that doctrine.
> >>>>>
> >>>>> (This is something that gave us quite a lot of angst in ANIMA,
> >>>>> especially in clarifying the "link" model in the Autonomic Control
> >>>>> Plane, since we depend on link-local multicast.)
> >>>>>
> >>>>> Regards
> >>>>>  Brian
> >>>>>
> >>>>> On 18-May-21 02:45, internet-drafts@ietf.org wrote:
> >>>>>>
> >>>>>> A New Internet-Draft is available from the on-line Internet-Drafts
> >>>>> directories.
> >>>>>>
> >>>>>>
> >>>>>>       Title           : IPv6 Neighbor Discovery on Wireless Networks
> >>>>>>       Author          : Pascal Thubert
> >>>>>>   Filename        : draft-thubert-6man-ipv6-over-wireless-09.txt
> >>>>>>   Pages           : 25
> >>>>>>   Date            : 2021-05-17
> >>>>>>
> >>>>>> Abstract:
> >>>>>>  This document describes how the original IPv6 Neighbor Discovery
> >>>>> and
> >>>>>>  Wireless ND (WiND) can be applied on various abstractions of
> >>>>> wireless
> >>>>>>  media.
> >>>>>>
> >>>>>>
> >>>>>> The IETF datatracker status page for this draft is:
> >>>>>> https://datatracker.ietf.org/doc/draft-thubert-6man-ipv6-over-wirele
> >>>>>> ss
> >>>>>> /
> >>>>>>
> >>>>>> There is also an HTML version available at:
> >>>>>> https://www.ietf.org/archive/id/draft-thubert-6man-ipv6-over-wireles
> >>>>>> s-
> >>>>>> 09.html
> >>>>>>
> >>>>>> A diff from the previous version is available at:
> >>>>>> https://www.ietf.org/rfcdiff?url2=draft-thubert-6man-ipv6-over-wirel
> >>>>>> es
> >>>>>> s-09
> >>>>>>
> >>>>>>
> >>>>>> Please note that it may take a couple of minutes from the time of
> >>>>>> submission until the htmlized version and diff are available at
> >>>>> tools.ietf.org.
> >>>>>>
> >>>>>> Internet-Drafts are also available by anonymous FTP at:
> >>>>>> ftp://ftp.ietf.org/internet-drafts/
> >>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> I-D-Announce mailing list
> >>>>>> I-D-Announce@ietf.org
> >>>>>> https://www.ietf.org/mailman/listinfo/i-d-announce
> >>>>>> Internet-Draft directories: http://www.ietf.org/shadow.html or
> >>>>>> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >>>>>>
> >>>>>
> >>>>> --------------------------------------------------------------------
> >>>>> 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
> >>>> --------------------------------------------------------------------
> >>>>
> >>>> --------------------------------------------------------------------
> >>>> 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
> >>> --------------------------------------------------------------------