From nobody Wed Dec 6 01:14:23 2017 Return-Path: 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 F3F72127419 for ; Wed, 6 Dec 2017 01:14:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.633 X-Spam-Level: X-Spam-Status: No, score=-2.633 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_SOFTFAIL=0.665] 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 Yj6DYs_1j48T for ; Wed, 6 Dec 2017 01:14:20 -0800 (PST) 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 568F5126E01 for ; Wed, 6 Dec 2017 01:14:20 -0800 (PST) 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 vB69EIxR042400 for ; Wed, 6 Dec 2017 10:14:18 +0100 Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id AB1362026CE for ; Wed, 6 Dec 2017 10:14:18 +0100 (CET) Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id A1B8420264A for ; Wed, 6 Dec 2017 10:14:18 +0100 (CET) Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id vB69EIsf030948 for ; Wed, 6 Dec 2017 10:14:18 +0100 To: its@ietf.org References: <149676796476.3863.10419161976482574233.idtracker@ietfa.amsl.com> From: Alexandre Petrescu Message-ID: <6b30e2f4-5b6c-dba8-6e8e-408c555aa03f@gmail.com> Date: Wed, 6 Dec 2017 10:14:18 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <149676796476.3863.10419161976482574233.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [ipwave] New Liaison Statement, "Radio interface standards of vehicle-to-vehicle and vehicle-toinfrastructure communications for Intelligent Transport System applications" X-BeenThere: its@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2017 09:14:23 -0000 HAs there been a reply made? IT says this: >> Please reply by 2017-10-30 Le 06/06/2017 à 18:52, Liaison Statement Management Tool a écrit : > Title: Radio interface standards of vehicle-to-vehicle and vehicle-toinfrastructure communications for Intelligent Transport System applications > Submission Date: 2017-06-06 > URL of the IETF Web page: https://datatracker.ietf.org/liaison/1526/ > Please reply by 2017-10-30 > From: Sergio Buonomo > To: Carlos Bernardos ,Russ Housley > Cc: Terry Manderson ,IP Wireless Access in Vehicular Environments Discussion List ,Russ Housley ,Carlos Bernardos ,Suresh Krishnan ,itu-t-liaison@iab.org > Response Contacts: sergio.buonomo@itu.int > Technical Contacts: > Purpose: For action > > Body: Recommendation ITU-R M.2084-0 – Radio interface standards of vehicle-to-vehicle and > vehicle-to-infrastructure communications for Intelligent Transport System applications was > published in 2015. Currently, WP 5A is working on revising Recommendation ITU-R M.2084-0 > with the updated radio interface information. > > WP 5A invites external organizations to submit updated information if any on the technical > standards characteristics, and will consider the input contribution material during its drafting > process at the meeting in November 2017, upon receiving them prior to 16:00 (UTC) on 30 October > 2017. WP 5A expects to finalize this Revision at its November 2017 meeting. > > Attachment: Annex 33 to Document 5A/469, “Preliminary draft revision of Recommendation ITU-R M.2084-0: “Radio interface standards of vehicle-to-vehicle and vehicle-to-infrastructure communications for Intelligent Transport System applications” > Attachments: > > LS_EOs_5A_141R1 > https://www.ietf.org/lib/dt/documents/LIAISON/liaison-2017-06-06-itu-r-wp5a-ipwave-radio-interface-standards-of-vehicle-to-vehicle-and-vehicle-toinfrastructure-communications-for-intelligent-transpo-attachment-1.pdf > > _______________________________________________ > its mailing list > its@ietf.org > https://www.ietf.org/mailman/listinfo/its > From nobody Wed Dec 6 01:20:41 2017 Return-Path: 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 E9799126D05 for ; Wed, 6 Dec 2017 01:20:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.633 X-Spam-Level: X-Spam-Status: No, score=-2.633 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_SOFTFAIL=0.665] 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 1qu3Czn-CD-i for ; Wed, 6 Dec 2017 01:20:35 -0800 (PST) Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (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 3FF4212711B for ; Wed, 6 Dec 2017 01:20:35 -0800 (PST) Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id vB69KXdF142803 for ; Wed, 6 Dec 2017 10:20:33 +0100 Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 346A02017E3 for ; Wed, 6 Dec 2017 10:20:33 +0100 (CET) Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 1DF04202783 for ; Wed, 6 Dec 2017 10:20:33 +0100 (CET) Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id vB69KW6L006667 for ; Wed, 6 Dec 2017 10:20:32 +0100 References: To: "its@ietf.org" From: Alexandre Petrescu X-Forwarded-Message-Id: Message-ID: <9a54902a-444b-b328-6939-74224900d992@gmail.com> Date: Wed, 6 Dec 2017 10:20:32 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/mixed; boundary="------------B551039E839AA0404BF4432B" Content-Language: fr Archived-At: Subject: [ipwave] Fwd: New Liaison Statement, "Radio interface standards of vehicle-to-vehicle and vehicle-to-infrastructure communications for Intelligent Transport System applications" X-BeenThere: its@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2017 09:20:40 -0000 This is a multi-part message in MIME format. --------------B551039E839AA0404BF4432B Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit fyi -------- Message transféré -------- Sujet : [manet] Fwd: New Liaison Statement, "Radio interface standards of vehicle-to-vehicle and vehicle-to-infrastructure communications for Intelligent Transport System applications" Date : Wed, 29 Nov 2017 10:22:55 -0800 De : Alvaro Retana Pour : manet@ietf.org Just FYI… Somewhat related to the other thread on ipwave.  No action required. Alvaro. On November 29, 2017 at 11:08:37 AM, Liaison Statement Management Tool (lsmt@ietf.org ) wrote: > Title: Radio interface standards of vehicle-to-vehicle and > vehicle-to-infrastructure communications for Intelligent Transport > System applications > Submission Date: 2017-11-29 > URL of the IETF Web page: https://datatracker.ietf.org/liaison/1548/ > Please reply by 2018-03-14 > From: Sergio Buonomo > > To: The IETF Chair > > Cc: The IESG >,The IETF Chair > >,itu-t-liaison@iab.org > > Response Contacts: sergio.buonomo@itu.int > Technical Contacts: > Purpose: For action > > Body: At its November 2017 meeting WP 5A progressed the revision of > Recommendation ITU-R M.2084-0 “Radio interface standards of > vehicle-to-vehicle and vehicle to-infrastructure communications for > Intelligent Transport System applications”. However, the meeting > agreed to extend finalization of this revision until May 2018 in order > to allow some members to submit their standards and technical > specifications. Even though the work will continue, the document is > considered relatively stable as a preliminary draft revision of > Recommendation ITU-R M.2084 (see Annex 30 to Document 5A/650). > > WP 5A invites external organizations to submit updated information, if > any, on technical standards, and will consider any input contributions > at its next meeting in May 2018. The deadline for submission of > contributions is prior to 16:00 (UTC) on 14 May 2018. > Attachments: > > R15-WP5A-171106-TD-0262!R1!MSW-E > https://www.ietf.org/lib/dt/documents/LIAISON/liaison-2017-11-29-itu-r-wp5a-ietf-radio-interface-standards-of-vehicle-to-vehicle-and-vehicle-to-infrastructure-communications-for-intelligent-transp-attachment-1.pdf > > --------------B551039E839AA0404BF4432B Content-Type: text/plain; charset=UTF-8; name="Portion de message joint" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="Portion de message joint" X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCm1hbmV0 IG1haWxpbmcgbGlzdA0KbWFuZXRAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21h aWxtYW4vbGlzdGluZm8vbWFuZXQNCg0K --------------B551039E839AA0404BF4432B-- From nobody Wed Dec 6 03:47:29 2017 Return-Path: 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 0A068124205 for ; Wed, 6 Dec 2017 03:47:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.633 X-Spam-Level: X-Spam-Status: No, score=-2.633 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_SOFTFAIL=0.665] 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 gODcUNLoCRuh for ; Wed, 6 Dec 2017 03:47:26 -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 B285E1241F5 for ; Wed, 6 Dec 2017 03:47:25 -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 vB6BlOlQ029479 for ; Wed, 6 Dec 2017 12:47:24 +0100 Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 104092022AC for ; Wed, 6 Dec 2017 12:47:24 +0100 (CET) Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 06DB8201C31 for ; Wed, 6 Dec 2017 12:47:24 +0100 (CET) Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id vB6BlNoZ005420 for ; Wed, 6 Dec 2017 12:47:23 +0100 References: <7aa86019-20e0-0683-7220-e261bc7a282a@gmail.com> To: "its@ietf.org" From: Alexandre Petrescu X-Forwarded-Message-Id: <7aa86019-20e0-0683-7220-e261bc7a282a@gmail.com> Message-ID: <369645ea-74f7-bc3d-d98f-17b12d841cf0@gmail.com> Date: Wed, 6 Dec 2017 12:47:23 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <7aa86019-20e0-0683-7220-e261bc7a282a@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr Content-Transfer-Encoding: 8bit Archived-At: Subject: [ipwave] Fwd: Re: [Detnet] Netslicing use case clarification - V2X for IPWAVE WG X-BeenThere: its@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2017 11:47:28 -0000 Forwarding to IPWAVE WG a message I posted in reply to detnet WG, in order to avoid cross-posting. -------- Message transféré -------- Sujet : Re: [Detnet] Netslicing use case clarification - V2X for IPWAVE WG Date : Wed, 6 Dec 2017 12:39:46 +0100 De : Alexandre Petrescu Pour : detnet@ietf.org Le 05/12/2017 à 00:37, Greg Mirsky a écrit : > Dear Authors, et. al, > at the meeting in Singapore I've made a comment about mapping between > 3GPP use cases and Detnet. And I took an action to provide text that may > be used in the draft-ietf-detnet-use-cases. Please kindly consider the > following: > > Initial analysis of new services and market enablers by 3GPP listed > more than 70 use cases. These were later grouped into four service > categories identifying service and network requirements: > > * Enhanced Mobile Broadband (eMBB) mainly focuses on facilitating > high data rates. eMBB aims to enable a broadband connectivity > across heterogeneous networks including also fixed mobile > convergence, assure broadband connectivity even under high user > and vehicle mobility and support devices with highly variable > data rates. > Hence, eMBB requires high network capacity, predictable latency > and high network availability. > * Ultra-Reliable Low Latency Communications (URLLC) enables > services requiring ultra reliability and low latency, > facilitating mission critical services, vehicular > communications, industrial automation and control, Augmented > Reality/Virtual Reality (AR/VR), tactile Internet, public > safety, disaster and emergency response, etc. URLLC requires > assuring the desired isolation, prioritization, rapid > communication setup, very low jitter, location precision, etc. > * Vehicle to Everything (V2X) focuses on: > o safety-related services; > o autonomous driving ; > o comfort services. > > Two first areas are considered as special cases of URLLC > category of use cases. For whatever is vehicular you can bring it to the IPWAVE WG ietf.org/mailman/listinfo/its For example, one possible perspective in IPWAVE is that a V2X message CAM of Europe, or BSM of America, is sent on the 3GPP link too, instead of just sent on the 802.11-OCB link. If that message is critical, then a QoS field Traffic Class in 3GPP headers could be mapped into a similar field of 802.11-OCB headers. The autonomous driving and the comfort services parts of V2X can also be of high relevance in IPWAVE WG. For 'netslicing', I heard about first demos of "sliced 5G" for cars. Alex _______________________________________________ detnet mailing list detnet@ietf.org https://www.ietf.org/mailman/listinfo/detnet From nobody Wed Dec 6 09:02:18 2017 Return-Path: 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 844D61276AF for ; Wed, 6 Dec 2017 09:02:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 W-dEiolTDj9M for ; Wed, 6 Dec 2017 09:02:11 -0800 (PST) Received: from smtp2.eurecom.fr (smtp2.eurecom.fr [193.55.113.211]) by ietfa.amsl.com (Postfix) with ESMTP id 4E55D128959 for ; Wed, 6 Dec 2017 09:02:10 -0800 (PST) X-IronPort-AV: E=Sophos;i="5.45,368,1508796000"; d="scan'208";a="7297754" Received: from waha.eurecom.fr (HELO smtps.eurecom.fr) ([10.3.2.236]) by drago2i.eurecom.fr with ESMTP; 06 Dec 2017 18:02:08 +0100 Received: from [10.154.193.197] (unknown [80.12.58.69]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtps.eurecom.fr (Postfix) with ESMTPSA id B877BF0A; Wed, 6 Dec 2017 18:02:07 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) From: Jerome Haerri X-Mailer: iPhone Mail (15C114) In-Reply-To: <369645ea-74f7-bc3d-d98f-17b12d841cf0@gmail.com> Date: Wed, 6 Dec 2017 17:02:06 +0000 Cc: "its@ietf.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <7aa86019-20e0-0683-7220-e261bc7a282a@gmail.com> <369645ea-74f7-bc3d-d98f-17b12d841cf0@gmail.com> To: Alexandre Petrescu Archived-At: Subject: Re: [ipwave] Fwd: Re: [Detnet] Netslicing use case clarification - V2X for IPWAVE WG X-BeenThere: its@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2017 17:02:14 -0000 Hi Alex, this is interesting.. I still would doubt the critical V2X safety to be sent over IP, as even in 3= GPP (rel14), PC5 (sidelink) is requesting connection-less non-IP links...(br= oadcast means one-2-many and no PC5-S signaling.. said it different: it does not make any difference if we use ITS-G5/DSRC or V= 2X..BSM/CAM DO NOT use IP.. BR, J=C3=A9r=C3=B4me Envoy=C3=A9 de mon iPhone > Le 6 d=C3=A9c. 2017 =C3=A0 11:47, Alexandre Petrescu a =C3=A9crit : >=20 > Forwarding to IPWAVE WG a message I posted in reply to detnet WG, in order= to avoid cross-posting. >=20 >=20 > -------- Message transf=C3=A9r=C3=A9 -------- > Sujet : Re: [Detnet] Netslicing use case clarification - V2X for IPWAVE WG= > Date : Wed, 6 Dec 2017 12:39:46 +0100 > De : Alexandre Petrescu > Pour : detnet@ietf.org >=20 >=20 >=20 >> Le 05/12/2017 =C3=A0 00:37, Greg Mirsky a =C3=A9crit : >> Dear Authors, et. al, >> at the meeting in Singapore I've made a comment about mapping between 3GP= P use cases and Detnet. And I took an action to provide text that may be use= d in the draft-ietf-detnet-use-cases. Please kindly consider the following: >> Initial analysis of new services and market enablers by 3GPP listed >> more than 70 use cases. These were later grouped into four service >> categories identifying service and network requirements: >> * Enhanced Mobile Broadband (eMBB) mainly focuses on facilitating >> high data rates. eMBB aims to enable a broadband connectivity >> across heterogeneous networks including also fixed mobile >> convergence, assure broadband connectivity even under high user >> and vehicle mobility and support devices with highly variable >> data rates. >> Hence, eMBB requires high network capacity, predictable latency >> and high network availability. >> * Ultra-Reliable Low Latency Communications (URLLC) enables >> services requiring ultra reliability and low latency, >> facilitating mission critical services, vehicular >> communications, industrial automation and control, Augmented >> Reality/Virtual Reality (AR/VR), tactile Internet, public >> safety, disaster and emergency response, etc. URLLC requires >> assuring the desired isolation, prioritization, rapid >> communication setup, very low jitter, location precision, etc. >> * Vehicle to Everything (V2X) focuses on: >> o safety-related services; >> o autonomous driving ; >> o comfort services. >> Two first areas are considered as special cases of URLLC >> category of use cases. >=20 > For whatever is vehicular you can bring it to the IPWAVE WG ietf.org/mailm= an/listinfo/its >=20 > For example, one possible perspective in IPWAVE is that a V2X message CAM o= f Europe, or BSM of America, is sent on the 3GPP link too, instead of just s= ent on the 802.11-OCB link. If that message is critical, then a QoS field T= raffic Class in 3GPP headers could be mapped into a similar field of 802.11-= OCB headers. >=20 > The autonomous driving and the comfort services parts of V2X can also be o= f high relevance in IPWAVE WG. >=20 > For 'netslicing', I heard about first demos of "sliced 5G" for cars. >=20 > Alex >=20 > _______________________________________________ > detnet mailing list > detnet@ietf.org > https://www.ietf.org/mailman/listinfo/detnet >=20 > _______________________________________________ > its mailing list > its@ietf.org > https://www.ietf.org/mailman/listinfo/its From nobody Wed Dec 6 09:33:17 2017 Return-Path: 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 784051272E1 for ; Wed, 6 Dec 2017 09:33:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 Ln9c4wvjk5f9 for ; Wed, 6 Dec 2017 09:33:14 -0800 (PST) Received: from smtp2.eurecom.fr (smtp2.eurecom.fr [193.55.113.211]) by ietfa.amsl.com (Postfix) with ESMTP id 2A15812717E for ; Wed, 6 Dec 2017 09:33:14 -0800 (PST) X-IronPort-AV: E=Sophos;i="5.45,369,1508796000"; d="scan'208";a="7297924" Received: from waha.eurecom.fr (HELO smtps.eurecom.fr) ([10.3.2.236]) by drago2i.eurecom.fr with ESMTP; 06 Dec 2017 18:33:13 +0100 Received: from [10.132.45.31] (unknown [80.12.42.31]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtps.eurecom.fr (Postfix) with ESMTPSA id 30AE3F1C; Wed, 6 Dec 2017 18:33:12 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) From: Jerome Haerri X-Mailer: iPhone Mail (15C114) In-Reply-To: Date: Wed, 6 Dec 2017 17:33:11 +0000 Cc: "its@ietf.org" Content-Transfer-Encoding: quoted-printable Message-Id: <3B33F073-8A4A-49F8-AF5A-CAB2BB16EE05@eurecom.fr> References: <7aa86019-20e0-0683-7220-e261bc7a282a@gmail.com> <369645ea-74f7-bc3d-d98f-17b12d841cf0@gmail.com> To: Alexandre Petrescu Archived-At: Subject: Re: [ipwave] Fwd: Re: [Detnet] Netslicing use case clarification - V2X for IPWAVE WG X-BeenThere: its@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2017 17:33:16 -0000 Hi Alex, All, I could also add that the 5G Slices for V2X will most likely be on the V2X-U= u interface (the veryical to the eNB), which will be IP..so V2X on Uu could= be part of this group, but I doubt V2X-PC5 should.. BR, J=C3=A9r=C3=B4me Envoy=C3=A9 de mon iPhone > Le 6 d=C3=A9c. 2017 =C3=A0 17:02, Jerome Haerri = a =C3=A9crit : >=20 > Hi Alex, >=20 > this is interesting.. >=20 > I still would doubt the critical V2X safety to be sent over IP, as even in= 3GPP (rel14), PC5 (sidelink) is requesting connection-less non-IP links...(= broadcast means one-2-many and no PC5-S signaling.. >=20 > said it different: it does not make any difference if we use ITS-G5/DSRC o= r V2X..BSM/CAM DO NOT use IP.. >=20 > BR, >=20 > J=C3=A9r=C3=B4me >=20 > Envoy=C3=A9 de mon iPhone >=20 >> Le 6 d=C3=A9c. 2017 =C3=A0 11:47, Alexandre Petrescu a =C3=A9crit : >>=20 >> Forwarding to IPWAVE WG a message I posted in reply to detnet WG, in orde= r to avoid cross-posting. >>=20 >>=20 >> -------- Message transf=C3=A9r=C3=A9 -------- >> Sujet : Re: [Detnet] Netslicing use case clarification - V2X for IPWAVE W= G >> Date : Wed, 6 Dec 2017 12:39:46 +0100 >> De : Alexandre Petrescu >> Pour : detnet@ietf.org >>=20 >>=20 >>=20 >>> Le 05/12/2017 =C3=A0 00:37, Greg Mirsky a =C3=A9crit : >>> Dear Authors, et. al, >>> at the meeting in Singapore I've made a comment about mapping between 3G= PP use cases and Detnet. And I took an action to provide text that may be us= ed in the draft-ietf-detnet-use-cases. Please kindly consider the following:= >>> Initial analysis of new services and market enablers by 3GPP listed >>> more than 70 use cases. These were later grouped into four service >>> categories identifying service and network requirements: >>> * Enhanced Mobile Broadband (eMBB) mainly focuses on facilitating >>> high data rates. eMBB aims to enable a broadband connectivity >>> across heterogeneous networks including also fixed mobile >>> convergence, assure broadband connectivity even under high user >>> and vehicle mobility and support devices with highly variable >>> data rates. >>> Hence, eMBB requires high network capacity, predictable latency >>> and high network availability. >>> * Ultra-Reliable Low Latency Communications (URLLC) enables >>> services requiring ultra reliability and low latency, >>> facilitating mission critical services, vehicular >>> communications, industrial automation and control, Augmented >>> Reality/Virtual Reality (AR/VR), tactile Internet, public >>> safety, disaster and emergency response, etc. URLLC requires >>> assuring the desired isolation, prioritization, rapid >>> communication setup, very low jitter, location precision, etc. >>> * Vehicle to Everything (V2X) focuses on: >>> o safety-related services; >>> o autonomous driving ; >>> o comfort services. >>> Two first areas are considered as special cases of URLLC >>> category of use cases. >>=20 >> For whatever is vehicular you can bring it to the IPWAVE WG ietf.org/mail= man/listinfo/its >>=20 >> For example, one possible perspective in IPWAVE is that a V2X message CAM= of Europe, or BSM of America, is sent on the 3GPP link too, instead of just= sent on the 802.11-OCB link. If that message is critical, then a QoS field= Traffic Class in 3GPP headers could be mapped into a similar field of 802.1= 1-OCB headers. >>=20 >> The autonomous driving and the comfort services parts of V2X can also be o= f high relevance in IPWAVE WG. >>=20 >> For 'netslicing', I heard about first demos of "sliced 5G" for cars. >>=20 >> Alex >>=20 >> _______________________________________________ >> detnet mailing list >> detnet@ietf.org >> https://www.ietf.org/mailman/listinfo/detnet >>=20 >> _______________________________________________ >> its mailing list >> its@ietf.org >> https://www.ietf.org/mailman/listinfo/its >=20 > _______________________________________________ > its mailing list > its@ietf.org > https://www.ietf.org/mailman/listinfo/its From nobody Thu Dec 7 05:56:37 2017 Return-Path: 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 832A9129453 for ; Thu, 7 Dec 2017 05:56:36 -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 9DPplXzGf_Ro for ; Thu, 7 Dec 2017 05:56:34 -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 8524112944F for ; Thu, 7 Dec 2017 05:56:34 -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 vB7DuW6e003574; Thu, 7 Dec 2017 14:56:32 +0100 Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id CC50C202FD5; Thu, 7 Dec 2017 14:56:32 +0100 (CET) Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id B433C202A9F; Thu, 7 Dec 2017 14:56:32 +0100 (CET) Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id vB7DuWuP002735; Thu, 7 Dec 2017 14:56:32 +0100 To: "its@ietf.org" Cc: Thierry Ernst From: Alexandre Petrescu Message-ID: Date: Thu, 7 Dec 2017 14:56:32 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------6F2ADD04C7DB60595C86FDF2" Content-Language: fr Archived-At: Subject: [ipwave] Liaison statement from ISO/TC204 X-BeenThere: its@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Dec 2017 13:56:36 -0000 This is a multi-part message in MIME format. --------------6F2ADD04C7DB60595C86FDF2 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hello IPWAVErs, Please find at this URL a liaison statement from ISO/TC204: https://datatracker.ietf.org/liaison/1549/ Yours, Alexandre PETRESCU, IETF Liaison Manager for SDO ISO/TC204 --------------6F2ADD04C7DB60595C86FDF2 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit

Hello IPWAVErs,

Please find at this URL a liaison statement from ISO/TC204:

https://datatracker.ietf.org/liaison/1549/

Yours,

Alexandre PETRESCU,
IETF Liaison Manager for SDO ISO/TC204

 --------------6F2ADD04C7DB60595C86FDF2-- From nobody Mon Dec 11 12:55:31 2017 Return-Path: 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 EE67F128959 for ; Mon, 11 Dec 2017 12:55:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.521 X-Spam-Level: X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 SwjZHyJ8W2Ob for ; Mon, 11 Dec 2017 12:55:27 -0800 (PST) Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71BD01273B1 for ; Mon, 11 Dec 2017 12:55:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=620; q=dns/txt; s=iport; t=1513025727; x=1514235327; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=g0xDVJCGmGHC8jASj6lIC7ghXP/p/VHrv1kGvI6iVmE=; b=FN79z0s3x0lGhawY4X+Z47Al9riNa6ltCBmNjwhZa8fWbN36Eux4o+wQ TUFp2HmoR7yF9KtjlvGb+FwOj51jNp6cwrLAkUJ26g9jLaCq17heOvhtp wV6zkopGpaU5ozV8GODvZpP9nTjI8+EDVC3UDUiRuBFiwS7nmq1cRWA/W c=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DeAAA08C5a/4oNJK1bGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYM+gVoujhyOf5kJghUKii8/GAEBAQEBAQEBAWsdC4VjUQEaJEI?= =?us-ascii?q?XEASKO6poimMBAQgCASWDaIILgVaQCyAFoxEClR+BfZFmljECERkBgToBHzmBT?= =?us-ascii?q?28VgmSEVIlCgRUBAQE?= X-IronPort-AV: E=Sophos;i="5.45,392,1508803200"; d="scan'208";a="43260252" Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 Dec 2017 20:55:26 +0000 Received: from XCH-ALN-010.cisco.com (xch-aln-010.cisco.com [173.36.7.20]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id vBBKtQ1o025558 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for ; Mon, 11 Dec 2017 20:55:26 GMT Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-ALN-010.cisco.com (173.36.7.20) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 11 Dec 2017 14:55:25 -0600 Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1320.000; Mon, 11 Dec 2017 14:55:25 -0600 From: "Sri Gundavelli (sgundave)" To: "its@ietf.org" Thread-Topic: Documents on ND and Deployment Considerations Thread-Index: AQHTcsJeBB2y8bfzi0qAFYlVDOT9/g== Date: Mon, 11 Dec 2017 20:55:25 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.7.1.161129 x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.20.188.62] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: [ipwave] Documents on ND and Deployment Considerations X-BeenThere: its@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Dec 2017 20:55:30 -0000 Chairs - When we were discussing the IPv6 support over 802.11-OCB draft, we agreed to keep the discussions on ND outside the scope of that document. May be we should discuss on how to support ND in that environment. Alex and I thought will ask for a slot in IETF101 and present few slides.=20 Secondly, I was also wondering if we should focus on the service architecture for vehicular environments. Covering some aspects around on-boarding, mobility, link-aggregator, routing policies ..etc. May be some thing around deployment considerations. Thoughts? Are these items under charter scope? Sri =20 From nobody Mon Dec 11 13:26:52 2017 Return-Path: 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 E17331289C3 for ; Mon, 11 Dec 2017 13:26:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.601 X-Spam-Level: X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=it-uc3m-es.20150623.gappssmtp.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 cOWbmfbam7vd for ; Mon, 11 Dec 2017 13:26:48 -0800 (PST) Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BABD9127137 for ; Mon, 11 Dec 2017 13:26:47 -0800 (PST) Received: by mail-wm0-x230.google.com with SMTP id r78so17161315wme.5 for ; Mon, 11 Dec 2017 13:26:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=it-uc3m-es.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:reply-to:to:date:in-reply-to:references :organization:mime-version:content-transfer-encoding; bh=vIJh0Mvi+5uoMz8E/8vJ2a3J1FNbt4ynVXNcxq3lS/Q=; b=0PE+1CvEtwoHWmXb+R0SHhE/SIj+DtySBt7whNb5GtYpoAE2bXY5lGjUFHePyTP31E r5pFnyuAhY+ty9DNNXmLKgUWpu/3a6qkW3DaOih44nEzvVG+OIf2yClFu2icRd8paJFp L8/wy3NMY2yTzq0DE7nE8JNz315/XjL7/9J738YkRJ8H2P8reFaRndrnPnFVaSShV+vE EMJ7D3uxkcoeFfMK8erT8AjXa3GwvrSSPCxhmQbThpdOfJLKmBaUkbEulGhEF8DUCUJ5 llyk9JSBz8KxMljp2u6XM8SC8jjwv5QpMiEmfJ1z0Isd1hB6vm06nvxVjM9IsOLS+kEn Jhdw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:reply-to:to:date :in-reply-to:references:organization:mime-version :content-transfer-encoding; bh=vIJh0Mvi+5uoMz8E/8vJ2a3J1FNbt4ynVXNcxq3lS/Q=; b=M+v8XTT7UlfmZld/TCZMwR7J3hn1+u/2WMQQXhDBSdA/k6CTfJn+YCM7PHkJ9RioXg SBjxNQD7L1+4EkcVNVzB+3fxikdYSbk2pNCjHLfKRLCW7sFosEtr/JvBY/AKPrgoCYYm +gIvW97t2ZV90z/EVP0ybHjvPcGAM/ahkXNvW7GL9jzkRsBdz0g725RfvwNF52VFvY+J WI3WUMs5TWTmAGaOF5RNSnNRwPeVExbd/q5eDOCvoKKdL+KAB4on8ZVRY8l+lJQO7pNl f/jB5XGfF0EQrg4qA7y1svVCYKQTlvuf3GK5dPKHDS7YYc+8V+V/im6CUkf/91N93DPc 9xrg== X-Gm-Message-State: AKGB3mJ2jWn8ao9fKiWxzv+/iObeyBdnmfvuYVI4V0+wVqrg4sTxOsl1 OxPF+V7FoqhmU0SAQlsXXUNJrw== X-Google-Smtp-Source: ACJfBovq4+w2c3IxuaODSBSfr8nS3oC4LmU57AMmHYaGP7AcaBm28zmuW9i/FZLDbR00fkB2y7gBCQ== X-Received: by 10.28.109.6 with SMTP id i6mr1895113wmc.108.1513027606183; Mon, 11 Dec 2017 13:26:46 -0800 (PST) Received: from cjbc_dell.lan (2.154.161.159.dyn.user.ono.com. [2.154.161.159]) by smtp.gmail.com with ESMTPSA id i65sm11389834wme.20.2017.12.11.13.26.45 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 11 Dec 2017 13:26:45 -0800 (PST) Message-ID: <1513027603.3441.10.camel@it.uc3m.es> From: Carlos =?ISO-8859-1?Q?Jes=FAs?= Bernardos Cano Reply-To: cjbc@it.uc3m.es To: "Sri Gundavelli (sgundave)" , "its@ietf.org" Date: Mon, 11 Dec 2017 22:26:43 +0100 In-Reply-To: References: Organization: Universidad Carlos III de Madrid Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.2-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [ipwave] Documents on ND and Deployment Considerations X-BeenThere: its@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Dec 2017 21:26:51 -0000 Hi Sri, Please see inline below. On Mon, 2017-12-11 at 20:55 +0000, Sri Gundavelli (sgundave) wrote: > Chairs - When we were discussing the IPv6 support over 802.11-OCB > draft, > we agreed to keep the discussions on ND outside the scope of that > document. May be we should discuss on how to support ND in that > environment. Alex and I thought will ask for a slot in IETF101 and > present > few slides. As discussed in Singapore, this is a potential good item for a new charter item. I think it's good if you could prepare that material for IETF 101. > > Secondly, I was also wondering if we should focus on the service > architecture for vehicular environments. Covering some aspects around > on-boarding, mobility, link-aggregator, routing policies ..etc. May > be > some thing around deployment considerations. > > Thoughts? Are these items under charter scope? I think these are good items for discussion. We have to fix our current milestones (at least submit the IPv6-over-802.11-OCB to the IESG and have well advanced the other one) before we are allowed to recharter. If we do our job on those items, we would like to open the floor for rechartering discussions via e-mail before IETF101 and have some F2F airtime in London. As I also highlighted in Singapore, since we have a problem statement document, all items for rechartering should be covered there (and properly justified). This is the perfect placeholder to do the proper analysis of what we need and why we need it (i.e., justification of the problem that need to be addressed, analysis of why there are no solutions already for it, and justification of why the IETF should work on it). Thanks, Carlos > > > Sri > > > _______________________________________________ > its mailing list > its@ietf.org > https://www.ietf.org/mailman/listinfo/its From nobody Mon Dec 11 13:39:21 2017 Return-Path: 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 91917128B38 for ; Mon, 11 Dec 2017 13:39:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.521 X-Spam-Level: X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 MqPfLkLy8azU for ; Mon, 11 Dec 2017 13:39:18 -0800 (PST) Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F125128AA1 for ; Mon, 11 Dec 2017 13:39:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2460; q=dns/txt; s=iport; t=1513028358; x=1514237958; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=UWz84CezYdjK/Ro3NIq1RJyaF6n8ziyyGQDI8WwTAss=; b=HZfF9tuTjWxQn7jCp3LIvywR5IEfUb62O5IYeX/gkJKZvc56dayb4akI Xa/F1D1rdh2lXv88tpo5p4LBVpEAqvkB3ZnGsrglXQWTy4a9r7XdW1FHt swbrkSQBLRNmpDjRLyIHxJkmSpdQ/VmtvO5MaFnMK3vOfiMD2LRHD6nBM 8=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AOAgBK+i5a/4gNJK1bGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYM+ZnQnB50bgX2ZIQoYC4UYAoRyQxQBAQEBAQEBAQFrKIUiAQE?= =?us-ascii?q?BAQIBAQFsEAsCAQgSBi4nCxcOAgQBEhuKBQgQql2KZAEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBARsFg2iCC4FWgWmDK4R8hXsgBZJckDUClR+CFoYSizuWMQIRGQGBOgE2IoF?= =?us-ascii?q?PbxU6gimEVXiJSYEVAQEB?= X-IronPort-AV: E=Sophos;i="5.45,393,1508803200"; d="scan'208";a="331137485" Received: from alln-core-3.cisco.com ([173.36.13.136]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 Dec 2017 21:39:17 +0000 Received: from XCH-RCD-010.cisco.com (xch-rcd-010.cisco.com [173.37.102.20]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id vBBLdHsR011104 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 11 Dec 2017 21:39:17 GMT Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-RCD-010.cisco.com (173.37.102.20) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 11 Dec 2017 15:39:16 -0600 Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1320.000; Mon, 11 Dec 2017 15:39:16 -0600 From: "Sri Gundavelli (sgundave)" To: "cjbc@it.uc3m.es" , "its@ietf.org" Thread-Topic: [ipwave] Documents on ND and Deployment Considerations Thread-Index: AQHTcsh+aprEaB1yk0qpDOSy4iWpiA== Date: Mon, 11 Dec 2017 21:39:16 +0000 Message-ID: References: <1513027603.3441.10.camel@it.uc3m.es> In-Reply-To: <1513027603.3441.10.camel@it.uc3m.es> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.7.1.161129 x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.20.188.62] Content-Type: text/plain; charset="iso-8859-1" Content-ID: <287509AA6A864B4DACE034394E6FEA15@emea.cisco.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: Re: [ipwave] Documents on ND and Deployment Considerations X-BeenThere: its@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Dec 2017 21:39:20 -0000 Hi Carlos, Thanks for sharing the plan. We probably should open some discussions in the mailer. > As I also highlighted in Singapore, since we have a problem statement >document, all items for rechartering should be covered there (and >properly justified). Agree! I need to check this out. I have this problem of ignoring PS documents :-) Will review and make sure these are included. Regards Sri On 12/11/17, 1:26 PM, "Carlos Jes=FAs Bernardos Cano" wrote: >Hi Sri, > >Please see inline below. > >On Mon, 2017-12-11 at 20:55 +0000, Sri Gundavelli (sgundave) wrote: >> Chairs - When we were discussing the IPv6 support over 802.11-OCB >> draft, >> we agreed to keep the discussions on ND outside the scope of that >> document. May be we should discuss on how to support ND in that >> environment. Alex and I thought will ask for a slot in IETF101 and >> present >> few slides.=20 > >As discussed in Singapore, this is a potential good item for a new >charter item. I think it's good if you could prepare that material for >IETF 101. > >>=20 >> Secondly, I was also wondering if we should focus on the service >> architecture for vehicular environments. Covering some aspects around >> on-boarding, mobility, link-aggregator, routing policies ..etc. May >> be >> some thing around deployment considerations. >>=20 >> Thoughts? Are these items under charter scope? > >I think these are good items for discussion. We have to fix our current >milestones (at least submit the IPv6-over-802.11-OCB to the IESG and >have well advanced the other one) before we are allowed to recharter. >If we do our job on those items, we would like to open the floor for >rechartering discussions via e-mail before IETF101 and have some F2F >airtime in London. > >As I also highlighted in Singapore, since we have a problem statement >document, all items for rechartering should be covered there (and >properly justified). This is the perfect placeholder to do the proper >analysis of what we need and why we need it (i.e., justification of the >problem that need to be addressed, analysis of why there are no >solutions already for it, and justification of why the IETF should work >on it). > >Thanks, > >Carlos > >>=20 >>=20 >> Sri >> =20 >>=20 >> _______________________________________________ >> its mailing list >> its@ietf.org >> https://www.ietf.org/mailman/listinfo/its From nobody Mon Dec 11 14:24:42 2017 Return-Path: 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 4DA781200F1 for ; Mon, 11 Dec 2017 14:24:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.601 X-Spam-Level: X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=it-uc3m-es.20150623.gappssmtp.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 l7KlOTknKICj for ; Mon, 11 Dec 2017 14:24:38 -0800 (PST) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66CA3126DD9 for ; Mon, 11 Dec 2017 14:24:38 -0800 (PST) Received: by mail-wm0-x236.google.com with SMTP id t8so17309487wmc.3 for ; Mon, 11 Dec 2017 14:24:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=it-uc3m-es.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:reply-to:to:date:in-reply-to:references :organization:mime-version:content-transfer-encoding; bh=0dgDzICHenT26tLLl0+x+QgBwCqBJrm4Edo8U852qNw=; b=UpLHbH/PpmwDx6AUm/LbXHR6HDPfAoHT6gM0MYgWEBtvlMtJSz6wcxW0fGWt4TDRS7 XuC299+P9k5/TtJMO0qu8JOZbxF606eVrVADO7naE1C3SvM95G2s/kdoJdJJF3V2jhIu lRXmZxk3/uMlLiEx2si+uWEtKsBnTFmk/GKmBmBN63qtiAXU/x66Wv0iaJqyuWlb8qAK J2N0ysAGPq04KK9eVJBNs9yIfGaTkZzbd1omeBNosVGG6H/7k0pXQGrO8eGXypSwlpz/ jdzvC38dGxSgKJBVPharagNfEraUWsscMLrxiRQ4FmMGIHUdlCkxEVt+4Z4NL9rrweSj IvOA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:reply-to:to:date :in-reply-to:references:organization:mime-version :content-transfer-encoding; bh=0dgDzICHenT26tLLl0+x+QgBwCqBJrm4Edo8U852qNw=; b=RIJHHUbEOYdeDzXFoNU0kANBAwaQI4Cs/EZIiIPkBGqDdUnLmDgl6eak8KtdErROHO 4rwx9si8Xr2bg+vgtsFeYRAwhcJnSt42/YBtLliw5mWPET7Er8D40YoSekZf8LzV7n0a dYUCgImCr/6JUnJ+tIozK1zgcnvP4OsLOULcXAlfHlIcptS4MSJaucp3quCI0XXix8QV Tp5POYLNYsIbKY7bG6yuGgQjJpwqTdMGYLb2wj02t+mZhUOgSUYmOdAKDj4g4/H5W0AE XVxq1LB4iHRYTedlY5BBakNFVSHwU/HyudozthDISjB+CfOS8/Z7K0RFDNFKw1PBbeTD zXVw== X-Gm-Message-State: AKGB3mLZmFBJhG/9RlVjEUbzKtWbB6C5HZJH+cHqYMlNS1w5xjFRuQJi q4G92J8UsXUHOWGL1bpcDaxdxIF7 X-Google-Smtp-Source: ACJfBovqIaaDt1q2ac0YDzW4ONPA0gqqJebcizP6qHjjdCyJyYJm0/FUnYr1gJ/P0CtkKc64Q9nCOA== X-Received: by 10.28.69.136 with SMTP id l8mr1935741wmi.19.1513031076651; Mon, 11 Dec 2017 14:24:36 -0800 (PST) Received: from cjbc_dell.lan (2.154.161.159.dyn.user.ono.com. [2.154.161.159]) by smtp.gmail.com with ESMTPSA id m127sm10089471wmm.48.2017.12.11.14.24.35 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 11 Dec 2017 14:24:35 -0800 (PST) Message-ID: <1513031074.3441.37.camel@it.uc3m.es> From: Carlos =?ISO-8859-1?Q?Jes=FAs?= Bernardos Cano Reply-To: cjbc@it.uc3m.es To: "Sri Gundavelli (sgundave)" , "its@ietf.org" Date: Mon, 11 Dec 2017 23:24:34 +0100 In-Reply-To: References: <1513027603.3441.10.camel@it.uc3m.es> Organization: Universidad Carlos III de Madrid Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.2-1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [ipwave] Documents on ND and Deployment Considerations X-BeenThere: its@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Dec 2017 22:24:41 -0000 Hi Sri, On Mon, 2017-12-11 at 21:39 +0000, Sri Gundavelli (sgundave) wrote: > Hi Carlos, > > Thanks for sharing the plan. We probably should open some discussions > in > the mailer. Sure. > > > As I also highlighted in Singapore, since we have a problem > > statement > > document, all items for rechartering should be covered there (and > > properly justified). > > Agree! I need to check this out. I have this problem of ignoring PS > documents :-) Will review and make sure these are included. :D Carlos > > > > Regards > Sri > > > On 12/11/17, 1:26 PM, "Carlos Jesús Bernardos Cano" > wrote: > > > Hi Sri, > > > > Please see inline below. > > > > On Mon, 2017-12-11 at 20:55 +0000, Sri Gundavelli (sgundave) wrote: > > > Chairs - When we were discussing the IPv6 support over 802.11-OCB > > > draft, > > > we agreed to keep the discussions on ND outside the scope of that > > > document. May be we should discuss on how to support ND in that > > > environment. Alex and I thought will ask for a slot in IETF101 > > > and > > > present > > > few slides. > > > > As discussed in Singapore, this is a potential good item for a new > > charter item. I think it's good if you could prepare that material > > for > > IETF 101. > > > > > > > > Secondly, I was also wondering if we should focus on the service > > > architecture for vehicular environments. Covering some aspects > > > around > > > on-boarding, mobility, link-aggregator, routing policies ..etc. > > > May > > > be > > > some thing around deployment considerations. > > > > > > Thoughts? Are these items under charter scope? > > > > I think these are good items for discussion. We have to fix our > > current > > milestones (at least submit the IPv6-over-802.11-OCB to the IESG > > and > > have well advanced the other one) before we are allowed to > > recharter. > > If we do our job on those items, we would like to open the floor > > for > > rechartering discussions via e-mail before IETF101 and have some > > F2F > > airtime in London. > > > > As I also highlighted in Singapore, since we have a problem > > statement > > document, all items for rechartering should be covered there (and > > properly justified). This is the perfect placeholder to do the > > proper > > analysis of what we need and why we need it (i.e., justification of > > the > > problem that need to be addressed, analysis of why there are no > > solutions already for it, and justification of why the IETF should > > work > > on it). > > > > Thanks, > > > > Carlos > > > > > > > > > > > Sri > > > > > > > > > _______________________________________________ > > > its mailing list > > > its@ietf.org > > > https://www.ietf.org/mailman/listinfo/its > > From nobody Tue Dec 19 11:16:18 2017 Return-Path: X-Original-To: its@ietf.org Delivered-To: its@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id ECE921270AC; Tue, 19 Dec 2017 11:16:15 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Meeting Session Request Tool To: Cc: cjbc@it.uc3m.es, suresh@kaloom.com, its@ietf.org, ipwave-chairs@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.68.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <151371097593.7447.2110442855572979073.idtracker@ietfa.amsl.com> Date: Tue, 19 Dec 2017 11:16:15 -0800 Archived-At: Subject: [ipwave] ipwave - New Meeting Session Request for IETF 101 X-BeenThere: its@ietf.org X-Mailman-Version: 2.1.22 List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Dec 2017 19:16:16 -0000 A new meeting session request has just been submitted by Carlos J. Bernardos, a Chair of the ipwave working group. --------------------------------------------------------- Working Group Name: IP Wireless Access in Vehicular Environments Area Name: Internet Area Session Requester: Carlos Bernardos Number of Sessions: 1 Length of Session(s): 2.5 Hours Number of Attendees: 100 Conflicts to Avoid: First Priority: l2sm saag rtgarea manet 6man 6lo intarea stir lamps nfvrg detnet dmm Second Priority: sfc cfrg dhc roll ospf i2nsf isis lime Third Priority: mtgvenue iasa20 People who must be present: Russ Housley Suresh Krishnan Carlos J. Bernardos Resources Requested: Special Requests: --------------------------------------------------------- From nobody Tue Dec 19 15:27:17 2017 Return-Path: X-Original-To: its@ietf.org Delivered-To: its@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 33EEE129C6B; Tue, 19 Dec 2017 15:27:09 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Meeting Session Request Tool To: Cc: cjbc@it.uc3m.es, suresh@kaloom.com, its@ietf.org, ipwave-chairs@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.68.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <151372602916.2727.4961374581324114069.idtracker@ietfa.amsl.com> Date: Tue, 19 Dec 2017 15:27:09 -0800 Archived-At: Subject: [ipwave] ipwave - Update to a Meeting Session Request for IETF 101 X-BeenThere: its@ietf.org X-Mailman-Version: 2.1.22 List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Dec 2017 23:27:09 -0000 An update to a meeting session request has just been submitted by Carlos J. Bernardos, a Chair of the ipwave working group. --------------------------------------------------------- Working Group Name: IP Wireless Access in Vehicular Environments Area Name: Internet Area Session Requester: Carlos Bernardos Number of Sessions: 1 Length of Session(s): 2.5 Hours Number of Attendees: 100 Conflicts to Avoid: First Priority: l2sm saag rtgarea manet 6man 6lo intarea stir lamps nfvrg detnet dmm suit Second Priority: sfc cfrg dhc roll ospf i2nsf isis lime Third Priority: mtgvenue iasa20 People who must be present: Russ Housley Suresh Krishnan Carlos J. Bernardos Resources Requested: Special Requests: --------------------------------------------------------- From nobody Sun Dec 31 07:39:18 2017 Return-Path: X-Original-To: its@ietf.org Delivered-To: its@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A8C121241FC; Sun, 31 Dec 2017 07:39:11 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: its@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.68.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <151473475164.14817.16344430458855849850@ietfa.amsl.com> Date: Sun, 31 Dec 2017 07:39:11 -0800 Archived-At: Subject: [ipwave] I-D Action: draft-ietf-ipwave-ipv6-over-80211ocb-12.txt X-BeenThere: its@ietf.org X-Mailman-Version: 2.1.22 List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Dec 2017 15:39:12 -0000 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 : Transmission of IPv6 Packets over IEEE 802.11 Networks operating in mode Outside the Context of a Basic Service Set (IPv6-over-80211-OCB) Authors : Alexandre Petrescu Nabil Benamar Jerome Haerri Jong-Hyouk Lee Thierry Ernst Filename : draft-ietf-ipwave-ipv6-over-80211ocb-12.txt Pages : 38 Date : 2017-12-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. 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-12 https://datatracker.ietf.org/doc/html/draft-ietf-ipwave-ipv6-over-80211ocb-12 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-ipwave-ipv6-over-80211ocb-12 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/ From nobody Sun Dec 31 07:47:25 2017 Return-Path: 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 8BDD9127978 for ; Sun, 31 Dec 2017 07:47:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.632 X-Spam-Level: X-Spam-Status: No, score=-2.632 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] 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 riKCvzc5kzoF for ; Sun, 31 Dec 2017 07:47:22 -0800 (PST) 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 DEA011241FC for ; Sun, 31 Dec 2017 07:47:21 -0800 (PST) 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 vBVFlJvI045810 for ; Sun, 31 Dec 2017 16:47:19 +0100 Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id C8FB2203258 for ; Sun, 31 Dec 2017 16:47:19 +0100 (CET) Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id BDBD62015CB for ; Sun, 31 Dec 2017 16:47:19 +0100 (CET) Received: from [132.166.84.62] ([132.166.84.62]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id vBVFlIxw019822 for ; Sun, 31 Dec 2017 16:47:19 +0100 References: <151473475181.14817.7342841253974626213.idtracker@ietfa.amsl.com> To: IPWAVE WG list From: Alexandre Petrescu X-Forwarded-Message-Id: <151473475181.14817.7342841253974626213.idtracker@ietfa.amsl.com> Message-ID: <506f1a5b-77ee-944b-448e-914071dfe090@gmail.com> Date: Sun, 31 Dec 2017 16:47:18 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <151473475181.14817.7342841253974626213.idtracker@ietfa.amsl.com> Content-Type: multipart/alternative; boundary="------------12BF0E8E763ABB22F1C9276F" Content-Language: fr Archived-At: Subject: [ipwave] Fwd: New Version Notification for draft-ietf-ipwave-ipv6-over-80211ocb-12.txt X-BeenThere: its@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Dec 2017 15:47:25 -0000 This is a multi-part message in MIME format. --------------12BF0E8E763ABB22F1C9276F Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hi IPWAVErs, I submitted the version -12. This update is about the Singapour comments on the Appendix F.4 "MAC Address Generation": the text now is rephrased more to make it an optional alternative of randomizing the MAC address, that may or may not be implemented. Alex -------- Message transféré -------- Sujet : New Version Notification for draft-ietf-ipwave-ipv6-over-80211ocb-12.txt Date : Sun, 31 Dec 2017 07:39:11 -0800 De : internet-drafts@ietf.org Pour : Jerome Haerri , ipwave-chairs@ietf.org, Jerome Haerri , Alexandre Petrescu , Alexandre Petrescu , Nabil Benamar , Thierry Ernst , Jong-Hyouk Lee A new version of I-D, draft-ietf-ipwave-ipv6-over-80211ocb-12.txt has been successfully submitted by Alexandre Petrescu and posted to the IETF repository. Name: draft-ietf-ipwave-ipv6-over-80211ocb Revision: 12 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: 2017-12-31 Group: ipwave Pages: 38 URL: https://www.ietf.org/internet-drafts/draft-ietf-ipwave-ipv6-over-80211ocb-12.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-12 Htmlized: https://datatracker.ietf.org/doc/html/draft-ietf-ipwave-ipv6-over-80211ocb-12 Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-ipwave-ipv6-over-80211ocb-12 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 --------------12BF0E8E763ABB22F1C9276F Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

Hi IPWAVErs,

I submitted the version -12. 

This update is about the Singapour comments on the Appendix F.4 "MAC Address Generation": the text now is rephrased more to make it an optional alternative of randomizing the MAC address, that may or may not be implemented.

Alex



-------- Message transféré --------
Sujet : New Version Notification for draft-ietf-ipwave-ipv6-over-80211ocb-12.txt
Date : Sun, 31 Dec 2017 07:39:11 -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-12.txt
has been successfully submitted by Alexandre Petrescu and posted to the
IETF repository.

Name:		draft-ietf-ipwave-ipv6-over-80211ocb
Revision:	12
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:	2017-12-31
Group:		ipwave
Pages:		38
URL:            https://www.ietf.org/internet-drafts/draft-ietf-ipwave-ipv6-over-80211ocb-12.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-12
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-ipwave-ipv6-over-80211ocb-12
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-ipwave-ipv6-over-80211ocb-12

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