Re: [ipwave] Fwd: New Version Notification for draft-ietf-ipwave-ipv6-over-80211ocb-31.txt

Jérôme Härri <jerome.haerri@eurecom.fr> Wed, 05 December 2018 02:10 UTC

Return-Path: <jerome.haerri@eurecom.fr>
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 5A424130E70 for <its@ietfa.amsl.com>; Tue, 4 Dec 2018 18:10:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.921
X-Spam-Level:
X-Spam-Status: No, score=-0.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FROM_EXCESS_BASE64=0.979, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 X_HhfFG81ftC for <its@ietfa.amsl.com>; Tue, 4 Dec 2018 18:10:06 -0800 (PST)
Received: from smtp2.eurecom.fr (smtp2.eurecom.fr [193.55.113.211]) by ietfa.amsl.com (Postfix) with ESMTP id 92ACF130DD1 for <its@ietf.org>; Tue, 4 Dec 2018 18:10:04 -0800 (PST)
X-IronPort-AV: E=Sophos; i="5.56,316,1539640800"; d="scan'208,217"; a="10028554"
Received: from monza.eurecom.fr ([192.168.106.15]) by drago2i.eurecom.fr with ESMTP; 05 Dec 2018 03:10:02 +0100
Received: from xerus29 (unknown [192.168.200.3]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by monza.eurecom.fr (Postfix) with ESMTPSA id E49A433C7; Wed, 5 Dec 2018 03:09:58 +0100 (CET)
From: Jérôme Härri <jerome.haerri@eurecom.fr>
To: 'John Kenney' <jkenney@us.toyota-itc.com>, 'Alexandre Petrescu' <alexandre.petrescu@gmail.com>
Cc: 'its' <its@ietf.org>, 'Dorothy Stanley' <dstanley1389@gmail.com>
References: <154265051210.5320.13285322581737635986.idtracker@ietfa.amsl.com> <22d298c1-cae2-4d11-e2a6-1aa515276fba@gmail.com> <CAGRfTMkHLD3sPtGgEgRjfG98Z6bB38ArzxRAn8wExV_mEOpr=A@mail.gmail.com> <c73941c7-ec34-6c84-89eb-ac1460e32508@gmail.com> <CAP6QOWQs6tt1uaehJEw79h9J79asmJC8oadecj3nDEY00FKspA@mail.gmail.com>
In-Reply-To: <CAP6QOWQs6tt1uaehJEw79h9J79asmJC8oadecj3nDEY00FKspA@mail.gmail.com>
Date: Wed, 05 Dec 2018 03:09:54 +0100
Organization: EURECOM
Message-ID: <016001d48c3f$a0d37d30$e27a7790$@eurecom.fr>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0161_01D48C48.029F1120"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQI6HfC8h5gSKO1DJoF/+Szc0vfWrwGdqRQqAkSntxQB2lH/OAEt3vZdpGzuBiA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/U9NPpJ-yALZLljSrWfMmaxYFG9M>
Subject: Re: [ipwave] Fwd: New Version Notification for draft-ietf-ipwave-ipv6-over-80211ocb-31.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: Wed, 05 Dec 2018 02:10:09 -0000

Hi All,

 

I support John’s comment. ITS-G5/DSRC/OCB can fully do unicast with acks. It is the application that chose not to use this but rather broadcast. And even considering broadcast, I do not think we have higher packet losses. Just that we do not retransmit, as it is broadcast. Maybe we should mention reduced ‘application-layer reliability’ so something in that direction..


BR,

 

Jérôme 

 

From: its [mailto:its-bounces@ietf.org] On Behalf Of John Kenney
Sent: Tuesday 04 December 2018 16:38
To: Alexandre Petrescu
Cc: its; Dorothy Stanley
Subject: Re: [ipwave] Fwd: New Version Notification for draft-ietf-ipwave-ipv6-over-80211ocb-31.txt

 

Hi,

 

Caveat: I know nothing about Neighbor Discovery protocol.

 

I see this in the proposed new text: 

 

Due to lack of link-layer acknowledgements in 802.11-OCB, we can expect higher packet loss than for 802.11 BSS. 

 

I don't understand why it is expected that OCB has a lack of link-layer acknowledgments.  OCB uses link layer acks the same way as 802.11 BSS uses them.   If I send a unicast 802.11 packet outside the context of a BSS, I expect an 802.11 ACK. If I don't get the 802.11 ACK, I go through exponential backoff and retransmit.  Just like normal 802.11.  Maybe I'm missing something.

 

Best Regards,

John

 

 

On Tue, Dec 4, 2018 at 7:11 AM Alexandre Petrescu <alexandre.petrescu@gmail.com> wrote:



Le 04/12/2018 à 16:04, Dorothy Stanley a écrit :
> Hello Alexandre, all,
> 
> I am sharing the following information from John Kenny ( 
> jkenney@us.toyota-itc.com <mailto:jkenney@us.toyota-itc.com>), who is
> actively involved in 802.11p implementation and deployments: "OCB can
> use unicast in the same way as other flavors of 802.11 ( individually
> addressed 802.11 MAC PDU that is ACKed using 802.11 procedures ). I
> find this is a common misunderstanding (indeed, I am in a meeting
> right now where this very point came up about 20 minutes ago).
> Probably the confusion is partly due to the fact that a great deal of
> DSRC attention is focused on the broadcast Basic Safety Message. Some
> people think that DSRC is only BSMs, or only broadcast messages. But,
> there are some important unicast applications as well."
> 
> Thus a change is needed in 4.7, either delete the second sentence or
>  modify to reflect that unicast is acknowledged.

I propose

NEW:
> The Neighbor Discovery protocol (ND) [RFC4861] is used over 
> 802.11-OCB links.  Due to lack of link-layer acknowledgements in 
> 802.11-OCB, we can expect higher packet loss than for 802.11 BSS. The
> ND retransmissions are supposed to handle loss of IP unicast and/or 
> IP multicast just as it does for other link types.

(remark disappeared 'unicast' and 'multicast' from 2nd phrase, and added 
'IP' in front of unicast and multicast in 3rd phrase).

OLD:
> The Neighbor Discovery protocol (ND) [RFC4861] is used over 
> 802.11-OCB links.  Due to lack of link-layer acknowledgements in 
> 802.11-OCB for both unicast and multicast, we can expect higher 
> unicast loss than for 802.11 BSS.  The ND retransmissions are 
> supposed to handle loss of unicast and/or multicast just as it does 
> for other link types.

Would this be agreed by John Kenney.

Alex

> 
> Thanks,
> 
> Dorothy
> 
> ---------------------- Dorothy Stanley IEEE 802.11 WG Chair, 
> dstanley@ieee.org <mailto:dstanley@ieee.org> Hewlett Packard 
> Enterprise dorothy.stanley@hpe.com 
> <mailto:dstanley@arubanetworks.com> dstanley1389@gmail.com 
> <mailto:dstanley1389@gmail.com> +1 630-363-1389 <tel:630-363-1389>
> 
> 
> 
> On Mon, Nov 19, 2018 at 10:07 AM Alexandre Petrescu 
> <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>>
>  wrote:
> 
> Hi IPWAVErs,
> 
> Following the discussion during presentation of the IPv6/OCB slides 
> by Nabil during IPWAVE WG meeting, I have updated the IPv6/OCB 
> draft.
> 
> This is the ChangeLog:
> 
> - filled in the section titled "Pseudonym Handling"; - removed a 'MAY
> NOT' phrase about possibility of having other prefix than the LL on
> the link between cars; - shortened and improved the paragraph about
> Mobile IPv6, now with DNAv6; - improved the ND text about ND 
> retransmissions with relationship to packet loss; - changed the title
> of an appendix from 'EPD' to 'Protocol Layering'; - improved the
> 'Aspects introduced by OCB' appendix with a few phrases about the
> channel use and references.
> 
> This fixes all issues about ND and pseudonym handling.
> 
> Alex
> 
> -------- Message transféré -------- Sujet : New Version Notification
>  for draft-ietf-ipwave-ipv6-over-80211ocb-31.txt Date : Mon, 19 Nov 
> 2018 10:01:52 -0800 De : internet-drafts@ietf.org 
> <mailto:internet-drafts@ietf.org> Pour : Jerome Haerri 
> <Jerome.Haerri@eurecom.fr <mailto:Jerome.Haerri@eurecom.fr <mailto:Jerome.Haerri@eurecom..fr> >>, 
> ipwave-chairs@ietf.org <mailto:ipwave-chairs@ietf.org>, Jerome Haerri
> <jerome.haerri@eurecom.fr <mailto:jerome.haerri@eurecom.fr <mailto:jerome.haerri@eurecom..fr> >>, 
> Alexandre Petrescu <Alexandre.Petrescu@cea.fr 
> <mailto:Alexandre.Petrescu@cea.fr>>, Alexandre Petrescu 
> <alexandre.petrescu@cea.fr <mailto:alexandre.petrescu@cea.fr>>, Nabil
> Benamar <n.benamar@est.umi.ac.ma <mailto:n.benamar@est.umi.ac.ma>>,
> Thierry Ernst <thierry.ernst@yogoko.fr
> <mailto:thierry.ernst@yogoko.fr>>, Jong-Hyouk Lee
> <jonghyouk@smu.ac.kr <mailto:jonghyouk@smu.ac.kr>>
> 
> 
> A new version of I-D, draft-ietf-ipwave-ipv6-over-80211ocb-31.txt has
> been successfully submitted by Alexandre Petrescu and posted to the
> IETF repository.
> 
> Name:           draft-ietf-ipwave-ipv6-over-80211ocb Revision: 31 
> Title:          Transmission of IPv6 Packets over IEEE 802.11 
> Networks operating in mode Outside the Context of a Basic Service Set
> (IPv6-over-80211-OCB) Document date:  2018-11-19 Group: ipwave Pages:
> 41 URL: 
> https://www.ietf.org/internet-drafts/draft-ietf-ipwave-ipv6-over-80211ocb-31.txt
>
>
>
> 
Status:
> https://datatracker.ietf.org/doc/draft-ietf-ipwave-ipv6-over-80211ocb/
>
>
>
> 
Htmlized:
> https://tools.ietf.org/html/draft-ietf-ipwave-ipv6-over-80211ocb-31 
> Htmlized: 
> https://datatracker.ietf.org/doc/html/draft-ietf-ipwave-ipv6-over-80211ocb
>
>
>
> 
Diff:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-ipwave-ipv6-over-80211ocb-31
>
>
>
> 
Abstract: In order to transmit IPv6 packets on IEEE 802.11 networks
> running outside the context of a basic service set (OCB, earlier 
> "802.11p") there is a need to define a few parameters such as the 
> supported Maximum Transmission Unit size on the 802.11-OCB link, the
>  header format preceding the IPv6 header, the Type value within it, 
> and others.  This document describes these parameters for IPv6 and 
> IEEE 802.11-OCB networks; it portrays the layering of IPv6 on 
> 802.11-OCB similarly to other known 802.11 and Ethernet layers - by 
> using an Ethernet Adaptation Layer.
> 
> 
> 
> 
> 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 <http://tools.ietf.org>.
> 
> The IETF Secretariat
> 
> _______________________________________________ its mailing list 
> its@ietf.org <mailto:its@ietf.org> 
> https://www.ietf.org/mailman/listinfo/its
> 

_______________________________________________
its mailing list
its@ietf.org
https://www.ietf.org/mailman/listinfo/its




 

-- 

John Kenney

Director and Principal Researcher

Toyota InfoTechnology Center, USA

465 Bernardo Avenue

Mountain View, CA 94043

Tel: 650-694-4160. Mobile: 650-224-6644