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

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 10 December 2018 18:23 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 66AB4131145 for <its@ietfa.amsl.com>; Mon, 10 Dec 2018 10:23:29 -0800 (PST)
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, HTML_MESSAGE=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, 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 g366wiYf_ehc for <its@ietfa.amsl.com>; Mon, 10 Dec 2018 10:23:27 -0800 (PST)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 A4F0D13114D for <its@ietf.org>; Mon, 10 Dec 2018 10:23:26 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id wBAINOxP032112 for <its@ietf.org>; Mon, 10 Dec 2018 19:23:24 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id B83BC2054ED for <its@ietf.org>; Mon, 10 Dec 2018 19:23:24 +0100 (CET)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id AC649201288 for <its@ietf.org>; Mon, 10 Dec 2018 19:23:24 +0100 (CET)
Received: from [10.8.68.91] ([10.8.68.91]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id wBAINOI0025869 for <its@ietf.org>; Mon, 10 Dec 2018 19:23:24 +0100
References: <154446587964.3005.11723773497142081483.idtracker@ietfa.amsl.com>
To: "its@ietf.org" <its@ietf.org>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
X-Forwarded-Message-Id: <154446587964.3005.11723773497142081483.idtracker@ietfa.amsl.com>
Message-ID: <b910471e-9502-19db-50f2-d262ad2f2062@gmail.com>
Date: Mon, 10 Dec 2018 19:23:23 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.3
MIME-Version: 1.0
In-Reply-To: <154446587964.3005.11723773497142081483.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------35B5DAC0564E439235348F4E"
Content-Language: fr
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/PDT2FzmTLQiYvMI25b6-05f_aR8>
Subject: [ipwave] Fwd: New Version Notification for draft-ietf-ipwave-ipv6-over-80211ocb-32.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: Mon, 10 Dec 2018 18:23:33 -0000

Hi IPWAVErs,

I submitted version -32 of IPv6/OCB.

The only change is shortening the IPv6/ND running statement.  It's just 
tells ND works over OCB.

This is in agreement with recent text adjustments suggested by 6MAN WG 
participants and further tweaked by IEEE participants.

I think it is the last changes.

Please progress the draft.

Why should it be progressed?

- we are at a point where comments lead to changes and back to initial.  
It's converged.

- I would like to move on and work on the new technologies that make use 
of this draft.

- deployments already do much of what this draft says, albeit at times a 
little bit differently (QoS).  (yet that is not a problem because QoS or 
no QoS implementations do interoperate).

Yours,

Alex



-------- Message transféré --------
Sujet : 	New Version Notification for 
draft-ietf-ipwave-ipv6-over-80211ocb-32.txt
Date : 	Mon, 10 Dec 2018 10:17:59 -0800
De : 	internet-drafts@ietf.org
Pour : 	Jerome Haerri <Jerome.Haerri@eurecom.fr>, 
ipwave-chairs@ietf.org, Jerome Haerri <jerome.haerri@eurecom.fr>, 
Alexandre Petrescu <Alexandre.Petrescu@cea.fr>, Alexandre Petrescu 
<alexandre.petrescu@cea.fr>, Nabil Benamar <n.benamar@est.umi.ac.ma>, 
Thierry Ernst <thierry.ernst@yogoko.fr>, Jong-Hyouk Lee 
<jonghyouk@smu.ac.kr>




A new version of I-D, draft-ietf-ipwave-ipv6-over-80211ocb-32.txt
has been successfully submitted by Alexandre Petrescu and posted to the
IETF repository.

Name: draft-ietf-ipwave-ipv6-over-80211ocb
Revision: 32
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-12-10
Group: ipwave
Pages: 41
URL: 
https://www.ietf.org/internet-drafts/draft-ietf-ipwave-ipv6-over-80211ocb-32.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-32
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-32

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.

The IETF Secretariat