Re: [ipwave] FW: Shepherd review of draft-ietf-ipwave-ipv6-over-80211ocb-12
Alexandre Petrescu <alexandre.petrescu@gmail.com> Tue, 06 February 2018 18:06 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 84E571270AB for <its@ietfa.amsl.com>; Tue, 6 Feb 2018 10:06:11 -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, 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 CgwdzHBFbbMY for <its@ietfa.amsl.com>; Tue, 6 Feb 2018 10:06:09 -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 C25F7124239 for <its@ietf.org>; Tue, 6 Feb 2018 10:06:08 -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 w16I66lj008352; Tue, 6 Feb 2018 19:06:06 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id DBE27204A43; Tue, 6 Feb 2018 19:06:06 +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 CACA02047BB; Tue, 6 Feb 2018 19:06:06 +0100 (CET)
Received: from [132.166.84.139] ([132.166.84.139]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id w16I66Xq027074; Tue, 6 Feb 2018 19:06:06 +0100
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Cc: François Simon <fygsimon@gmail.com>, its <its@ietf.org>
References: <1517217856.4315.32.camel@it.uc3m.es> <006601d39910$bdcf1cf0$396d56d0$@gmail.com> <d539c9e9-f9e4-b6c3-e8fc-c6273a7067ce@gmail.com> <000101d39c0f$e3b32f90$ab198eb0$@gmail.com> <87888ef4-ae0e-421c-0e48-43b0276f038a@gmail.com> <001a01d39e93$7ad4e4b0$707eae10$@gmail.com> <e6681433-e294-a41d-371f-866c5ffe50db@gmail.com> <000e01d39ef1$b5d553c0$217ffb40$@gmail.com> <38aab103-1a78-b0ba-c7af-2c3bf5ec5c75@gmail.com> <005c01d39f69$2d04ad20$870e0760$@gmail.com> <589c15a1-5ab4-3e16-5b92-c98c7043dcb7@gmail.com> <CADnDZ8_YuG0oFFOVoo_OD3v7eWq9n_M--kAsJpXC16h25y-UdQ@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <ec1e70f9-8807-adb4-a6e1-a8b47b03e928@gmail.com>
Date: Tue, 06 Feb 2018 19:06:05 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CADnDZ8_YuG0oFFOVoo_OD3v7eWq9n_M--kAsJpXC16h25y-UdQ@mail.gmail.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/j9Lkt4AW_QgyscpwoWZjovpAF-E>
Subject: Re: [ipwave] FW: Shepherd review of draft-ietf-ipwave-ipv6-over-80211ocb-12
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 <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: Tue, 06 Feb 2018 18:06:11 -0000
Le 06/02/2018 à 18:40, Abdussalam Baryun a écrit : > Hi Alex and Francois, > > I don't mind putting any clear definition in terms but should be used in > the body consistently within the draft. IP-OBU and IP-RSU are used in the text. We are not using DSRC, DSRCS, OBU nor RSU in the text. > Also we need to try to make the > definition short and to the point. I am not very interested in this > IP-xxx, however, I like the terminology used in RFC8200. so we should > mention that our IP-units are nodes or routers, Noted. > in terminology the > definition word 'computer' used is not consistent with other ietf RFCs. 'computer' is generic enough to not need a definition. I used 'computer' to solve the problem of saying 'Host' vs saying 'Router'. That debate is not solved and we wont solve it here. Alex > > AB > > On Tue, Feb 6, 2018 at 6:47 PM, Alexandre Petrescu > <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>> wrote: > > > > Le 06/02/2018 à 17:40, François Simon a écrit : > > Mr. Petrescu, > > /“//There are two very relevant terms: IP-OBU and IP-RSU.//”/// > > -// IftheWorkingGroupthinksthese terms are relevant, thenso > bid.Irespectfully disagree.Furthermore,I have nothing more to > add to this discussion;I have provided allUS relevant definitions. > > > I thank you for the definitions. > > I propose we go this way: > > Copy the definitions from your emails for DSRCS, and then DSRC and > then OBU and RSU in terms of DSRCS and of DSRC. > > But have these definitions (DSRCS, DSRC, OBU and RSU) in an > Appendix, not in the Terminology section. > > The Terminology section would list IP-OBU and IP-RSU and refer to > the Appendix. > > Alex > > > Sincerely, > > Francois Simon > > Lojik Technologies > > -----Original Message----- > From: Alexandre Petrescu [mailto:alexandre.petrescu@gmail.com > <mailto:alexandre.petrescu@gmail.com>] > Sent: Tuesday, February 06, 2018 10:41 AM > To: François Simon <fygsimon@gmail.com <mailto:fygsimon@gmail.com>> > Cc: its@ietf.org <mailto:its@ietf.org> > Subject: Re: FW: [ipwave] Shepherd review of > draft-ietf-ipwave-ipv6-over-80211ocb-12 > > If I add DSRCS, and DSRC, and OBU - it makes for 3 terms only > tangentially relevant. > > I find it too much. > > There are two very relevant terms: IP-OBU and IP-RSU. > > We need to have more relevant terms than tangentially relevant > terms. > > Le 06/02/2018 à 03:25, François Simon a écrit : > > /"//So, in order to define OBU in terms of DSRCS one has to > define > > > first DSRCS, all while caring to avoid loops. I think it > can become > > > too lengthy.//"/// > > > > > -///Dedicated Short-Range Communications////Services > (DSRCS)/.-The use > > > of radio techniquesto transfer data over short distancesbetween > > > roadside and mobile > > > > > units, between mobile units, and betweenportable > and mobile > > > units to performoperations related to the > improvementof traffic > > > flow, traffic safety, > > > > > and other intelligent transportationservice > applications in a > > > varietyof environments. DSRCS systems mayalso > transmit status > > > and instructional > > > > > messages related to the units involved.[ Ref. 47 > CFR90.7 – > > > Definitions] > > > > > -----Original Message----- > > > From: Alexandre Petrescu > [mailto:alexandre.petrescu@gmail.com > <mailto:alexandre.petrescu@gmail.com>] > > > Sent: Monday, February 05, 2018 10:41 AM > > > To: François Simon <fygsimon@gmail.com > <mailto:fygsimon@gmail.com><mailto:fygsimon@gmail.com > <mailto:fygsimon@gmail.com>>> > > > Cc:its@ietf.org > <mailto:Cc%3Aits@ietf.org><mailto:its@ietf.org > <mailto:its@ietf.org>> > > > Subject: Re: [ipwave] Shepherd review of > > > draft-ietf-ipwave-ipv6-over-80211ocb-12 > > > > > Le 05/02/2018 à 16:10, François Simon a écrit : > > > > > /"//Is DSRCS a typo? (correct DSRC).//"/// > > > > > > > > > -// No typo. DSRCS stands for “Dedicated Short Range > Communication Service” > > > > > So, in order to define OBU in terms of DSRCS one has to > define first > > > DSRCS, all while caring to avoid loops. I think it can > become too lengthy. > > > > > Alex > > > > > > > > > -----Original Message----- > > > > > From: Alexandre Petrescu > [mailto:alexandre.petrescu@gmail.com > <mailto:alexandre.petrescu@gmail.com>] > > > > > Sent: Sunday, February 04, 2018 11:08 AM > > > > > To: François Simon <fygsimon@gmail.com > <mailto:fygsimon@gmail.com><mailto:fygsimon@gmail.com > <mailto:fygsimon@gmail.com><mailto:fygsimon@gmail.com > <mailto:fygsimon@gmail.com><mailto:fygsimon@gmail.com > <mailto:fygsimon@gmail.com>>>> > > > > > Cc:its@ietf.org > <mailto:Cc%3Aits@ietf.org><mailto:its@ietf.org > <mailto:its@ietf.org>> > > > > > Subject: Re: [ipwave] Shepherd review of > > > > > draft-ietf-ipwave-ipv6-over-80211ocb-12 > > > > > > > > > I am adding this OBU ref for reference but I have a > question: > > > > > > > > > Le 02/02/2018 à 11:23, François Simon a écrit : > > > > > > > > > [...] > > > > > > > > > /On-Board unit (OBU). An On-Board Unit is a DSRCS > transceiver that > > > is > > > > > > > > > Is DSRCS a typo? (correct DSRC). > > > > > > > > > Alex > > > > > > > > > normally mounted in or on a vehicle, or which in > some instances may > > > > > be > > > > > > > > > a portable unit. An OBU can be operational while a > vehicle or person > > > > > > > > > is either mobile or stationary. The OBUs receive and > contend for > > > time > > > > > > > > > to transmit on one or more radio frequency (RF) > channels. Except > > > > > where > > > > > > > > > specifically excluded, OBU operation is permitted > wherever vehicle > > > > > > > > > operation or human passage is permitted. The OBUs > mounted in > > > vehicles > > > > > > > > > are licensed by rule under part 95 of this chapter > and communicate > > > > > > > > > with Roadside Units (RSUs) and other OBUs. Portable > OBUs are also > > > > > > > > > licensed by rule under part 95 of this chapter. OBU > operations in > > > the > > > > > > > > > Unlicensed National Information Infrastructure > (UNII) Bands follow > > > > > the > > > > > > > > > rules in those bands./- [CFR 90.7 - Definitions] - > October 2010 > > > > > > > > > > > > > > > > > *IPWAVE Issue*** > > > > > > > > > > > > > > > > > ** > > > > > > > > > > > > > > > > > /“The problem with the FCC definition of OBU is that > it has no > > > > > > > > > relationship to IP. Worse, that FCC definition has > no indication > > > > > that > > > > > > > > > it MAY use IP somehow. And here we say that all > OBUs must use IP. > > > > > Do > > > > > > > > > you see what I mean?”/// > > > > > > > > > > > > > > > > > // > > > > > > > > > > > > > > > > > Correct; the OBU has no relationship with IP and is > not intended to. > > > > > > > > > IP is a network protocol. If an On-Board Unit (OBU) > device is > > > > > > > > > required to exchange IP, it needs to be dealt in > protocol(s) and/or > > > > > > > > > Management in higher layers similar to WAVE within > the On-Board Equipment (OBE) . > > > > > > > > > > > > > > > > > /“Do you think FCC will mind if we use the term OBU > in this draft to > > > > > > > > > mean something else? I, and a colleague, think that > FCC would not > > > > > > > > > mind.”/// > > > > > > > > > > > > > > > > > // > > > > > > > > > > > > > > > > > Depending of the reader. If one is familiar with > DSRC, OBU and RSU > > > as > > > > > > > > > defined by FCC will come in mind. As far as I know, > “OBU” and “RSU” > > > > > > > > > are not registered and could be used for other > definitions > > > (something > > > > > > > > > like > > > > > > > > > “ATM”: Asynchronous Transfer Mode and Automatic > Teller Machine😊). > > > My > > > > > > > > > suggestion to the IPWAVE team is to use “OBE and RSE”. > > > > > > > > > > > > > > > > > This is my personal view as I donot represent any > involved interest. > > > > > > > > > If any one has questions, let me know. > > > > > > > > > > > > > > > > > Francois Simon > > > > > > > > > > > > > > > > > Lojik Technologies > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > > > > > > > > > > From: its [mailto:its-bounces@ietf.org > <mailto:its-bounces@ietf.org>] On Behalf Of Alexandre > > > > > > > > > Petrescu > > > > > > > > > > > > > > > > > Sent: Monday, January 29, 2018 10:08 AM > > > > > > > > > > > > > > > > > To:its@ietf.org > <mailto:To%3Aits@ietf.org><mailto:its@ietf.org > <mailto:its@ietf.org>> > > > > > > > > > > > > > > > > > Subject: Re: [ipwave] Shepherd review of > > > > > > > > > draft-ietf-ipwave-ipv6-over-80211ocb-12 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Le 29/01/2018 à 15:52, François Simon a écrit : > > > > > > > > > > > > > > > > > My comments arewithin the text*[Fygs.......]*. > > > > > > > > > > > > > > > > > [...] > > > > > > > > > > > > > > > > > In the terminology section, the OBU term is > mentioned to be defined > > > > > > > > > > > > > > > > > outside the IETF. This is fine, but we have to > provide a reference. > > > > > > > > > > > > > > > > > And even with that, it would not harm to include > some short > > > > > > > > > definition > > > > > > > > > > > > > > > > > to provide context. The RSU term is also defined > outside the IETF > > > > > and > > > > > > > > > > > > > > > > > there is quite a lot of text provided (I think > the relevant part is > > > > > > > > > > > > > > > > > the last sentence, the one starting with "The > difference between..."). > > > > > > > > > > > > > > > > > Both terms should be handled in the same way. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > *[Fygs: The**definitions**was issued by the FCC > 20 years ago. I > > > > > have > > > > > > > > > > > > > > >
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Scott Weeks
- [ipwave] Shepherd review of draft-ietf-ipwave-ipv… Carlos Jesús Bernardos Cano
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… François Simon
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Alexandre Petrescu
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… François Simon
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Alexandre Petrescu
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Tony Li
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… John Kenney
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Alexandre Petrescu
- [ipwave] FW: Shepherd review of draft-ietf-ipwave… François Simon
- [ipwave] FW: Shepherd review of draft-ietf-ipwave… François Simon
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Russ Housley
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… François Simon
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Alexandre Petrescu
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… François Simon
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Alexandre Petrescu
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… François Simon
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Dirk.von-Hugo
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Alexandre Petrescu
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Alexandre Petrescu
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… François Simon
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Alexandre Petrescu
- [ipwave] FW: Shepherd review of draft-ietf-ipwave… François Simon
- Re: [ipwave] FW: Shepherd review of draft-ietf-ip… Alexandre Petrescu
- Re: [ipwave] FW: Shepherd review of draft-ietf-ip… François Simon
- Re: [ipwave] FW: Shepherd review of draft-ietf-ip… Alexandre Petrescu
- Re: [ipwave] FW: Shepherd review of draft-ietf-ip… Abdussalam Baryun
- Re: [ipwave] FW: Shepherd review of draft-ietf-ip… Alexandre Petrescu
- Re: [ipwave] FW: Shepherd review of draft-ietf-ip… Alexandre Petrescu
- Re: [ipwave] FW: Shepherd review of draft-ietf-ip… Abdussalam Baryun
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Carlos Jesús Bernardos Cano
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Alexandre Petrescu
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Alexandre Petrescu
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… François Simon
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Tony Li
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… tony.li
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… tony.li
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Abdussalam Baryun
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Abdussalam Baryun
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Alexandre Petrescu
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Alexandre Petrescu
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Carlos Jesús Bernardos Cano
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Alexandre Petrescu
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Carlos Jesús Bernardos Cano
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Alexandre Petrescu
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Tony Li
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Carlos Jesús Bernardos Cano
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… tony.li
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Alexandre Petrescu
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Abdussalam Baryun
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Alexandre Petrescu
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… tony.li
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Alexandre Petrescu
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Carlos Jesús Bernardos Cano
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Alexandre Petrescu
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Carlos Jesús Bernardos Cano
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Alexandre Petrescu
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Tony Li
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Carlos Jesús Bernardos Cano
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Alexandre Petrescu
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… tony.li
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Alexandre Petrescu
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Alexandre Petrescu
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Tony Li
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Nabil Benamar
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Alexandre Petrescu
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… François Simon
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Alexandre Petrescu
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Alexandre Petrescu
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… tony.li
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Abdussalam Baryun
- Re: [ipwave] Shepherd review of draft-ietf-ipwave… Tony Li
- Re: [ipwave] addresses Alexandre Petrescu
- Re: [ipwave] addresses Abdussalam Baryun