Re: [ipwave] I-D Action: draft-ietf-ipwave-ipv6-over-80211ocb-51.txt
Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 25 July 2019 14:36 UTC
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: its@ietfa.amsl.com
Delivered-To: its@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D90631202D2 for <its@ietfa.amsl.com>; Thu, 25 Jul 2019 07:36:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.631
X-Spam-Level:
X-Spam-Status: No, score=-2.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Q02icuCE1ODU for <its@ietfa.amsl.com>; Thu, 25 Jul 2019 07:36:53 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 BF272120294 for <its@ietf.org>; Thu, 25 Jul 2019 07:36:52 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x6PEapRp036200 for <its@ietf.org>; Thu, 25 Jul 2019 16:36:51 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 0F4772017F6 for <its@ietf.org>; Thu, 25 Jul 2019 16:36:51 +0200 (CEST)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 04DC3201393 for <its@ietf.org>; Thu, 25 Jul 2019 16:36:51 +0200 (CEST)
Received: from [10.8.68.110] ([10.8.68.110]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x6PEamWB022228 for <its@ietf.org>; Thu, 25 Jul 2019 16:36:50 +0200
To: "its@ietf.org" <its@ietf.org>
References: <156406237987.12613.6896522812916332682@ietfa.amsl.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <c4724d92-707d-8456-9873-14a700d19ee5@gmail.com>
Date: Thu, 25 Jul 2019 16:36:48 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <156406237987.12613.6896522812916332682@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/NahJqKEp_B6z-on0FeJxXSOr2Sc>
Subject: Re: [ipwave] I-D Action: draft-ietf-ipwave-ipv6-over-80211ocb-51.txt
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF <its.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/its>, <mailto:its-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/its/>
List-Post: <mailto:its@ietf.org>
List-Help: <mailto:its-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/its>, <mailto:its-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jul 2019 14:37:00 -0000
Thanks for the new version! I have some comments from the earlier versions, so I think it is time I put them now on the list. I wonder whether you think addressing these comments are necessary now, or I can send them later, maybe after some more thought? Anyways, here are the comments: > but operates over 802.11-OCB to provide at least P2P (Point to Point) > connectivity using IPv6 ND and link-local addresses. 802.11-OCB is not a point-to-point link and nobody used it as such. I think the writer of this text has a completely different understanding than me, about what is a point-to-point link. For me, a point-to-point link is typically a cellular link, not an 802.11 link. A more tangible differentiator is the absence of MAC addresses most of the time. > The link model is the following: STA --- 802.11-OCB --- STA. In > vehicular networks, STAs can be IP-RSUs and/or IP-OBUs. All links > are assumed to be P2P and multiple links can be on one radio > interface. Nobody assumes the 802.11-OCB to be P2P (point-to-point) links; for my part, I never linked multiple links on one radio interface. I do not understand what the writer of this text meant. > IPv6 Neighbor Discovery protocol (ND) requires reflexive properties > (bidirectional connectivity) which is generally, though not always, > the case for P2P OCB links. I do not understand what is meant by P2P OCB links? > [Abstract:] Support for these methods and settings require minimal > changes to existing stacks. > [Section 4.2 Frame Format:] The mapping to the 802.11 data service > SHOULD use a 'priority' value of 1 (QoS with a 'Background' user > priority), These two paragraphs seem contradictory. Because making QoS 'Background' priority requires the use of 802.11 QoS Data headers which are not available in existing stacks. For my part I did not see stacks that do QoS Data headers. SO adding QoS Data headers requires much changes to existing stacks. (note: I do like and agree with the way in which 'minimal changes' is formulated and added for the draft). (note: I did see QoS Data headers but never seen the stacks that send them). Alex Le 25/07/2019 à 15:46, internet-drafts@ietf.org a écrit : > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. This draft is a work item of the IP Wireless Access in > Vehicular Environments WG of the IETF. > > Title : Basic Support for IPv6 over IEEE Std 802.11 > Networks Operating Outside the Context of a Basic Service Set > Authors : Nabil Benamar Jerome Haerri Jong-Hyouk Lee Thierry Ernst > Filename : draft-ietf-ipwave-ipv6-over-80211ocb-51.txt Pages : 31 > Date : 2019-07-25 > > Abstract: This document provides methods and settings, for using > IPv6 to communicate among nodes within range of one another over a > single IEEE 802.11-OCB link. Support for these methods and settings > require minimal changes to existing stacks. This document also > describes limitations associated with using these methods. > Optimizations and usage of IPv6 over more complex scenarios is not > covered in this specification and is subject of future work. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-ipwave-ipv6-over-80211ocb/ > > > > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-ipwave-ipv6-over-80211ocb-51 > https://datatracker.ietf.org/doc/html/draft-ietf-ipwave-ipv6-over-80211ocb-51 > > > > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-ipwave-ipv6-over-80211ocb-51 > > > > > > > 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 >
- [ipwave] I-D Action: draft-ietf-ipwave-ipv6-over-… internet-drafts
- Re: [ipwave] I-D Action: draft-ietf-ipwave-ipv6-o… Alexandre Petrescu