Re: [ipwave] Shepherd review of draft-ietf-ipwave-ipv6-over-80211ocb-12

François Simon <fygsimon@gmail.com> Mon, 05 February 2018 15:10 UTC

Return-Path: <fygsimon@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 4D4EC1242F7 for <its@ietfa.amsl.com>; Mon, 5 Feb 2018 07:10:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 9C37dajm4Em1 for <its@ietfa.amsl.com>; Mon, 5 Feb 2018 07:10:39 -0800 (PST)
Received: from mail-qt0-x234.google.com (mail-qt0-x234.google.com [IPv6:2607:f8b0:400d:c0d::234]) (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 7DDEB12D837 for <its@ietf.org>; Mon, 5 Feb 2018 07:10:39 -0800 (PST)
Received: by mail-qt0-x234.google.com with SMTP id t25so6366554qtg.3 for <its@ietf.org>; Mon, 05 Feb 2018 07:10:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:thread-index:content-language; bh=wi1zJBqq7AV3BlgjKTQYZvCYklBBoh9eGB3sbKIKKmA=; b=Lq6jnX36NqvQ0+cWtT9yLv5VeHS0l/MSTdJ79a+JaErQ3O/Fbd4I/Q4AFdtu5eQ0bb XpfuMgnqXiVa4/d9qgiImRag1Pi8/rrpc7rnnO0rSQQPvpzhK+oDasIOEEWcX0R428Tt 348E3+R41+/E6hKRBQ+QTl7qHA+7GoZmfsiINuKV7TLfK/57JzjOK7a5K67oMHZTO7FY tHQuTBoFJ5gqixXgTrzm42LEBNjELtxiddRhPEUu6Kuaa7itKRmSf0vBar7I2qgBvODf 380HNFAoRYYoDX+RgRKxsiNo+FzP55ZcKcrzkbYJGu2hqVPuuRwkgFkC9VxE+CJxBycE g7JQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=wi1zJBqq7AV3BlgjKTQYZvCYklBBoh9eGB3sbKIKKmA=; b=RhxbFwHb0KLaYrLKghckRB3auLLslNW2S1Lub/F7rpydqMQtqCMaI9K2EZmjI5enMT nm/4jUzWquXHwyFSnmVqtfPNyYovXpk2QoIcuht7pavW6tFWwGDIxakEQeF57jIETg/j HuSaAdj9MTmvHl1ezdW2BoSm+RcLokU8NqlEu7jDGX063iaoaqNlv3NOsRU2m/Kg9Hvc XfNwYwPqGN/3t5HplTD3DplNDTbhV44GsWwzhHLDZqXz6LYWdGiaERHv64dIUxduf9m3 Q0RGtUt6/Bb5784zt8Mq1xeGfc+07z+TnGB/LuekZVqyXryUAkeG+K8GtPUF0sEJIi6f fhXg==
X-Gm-Message-State: AKwxytf7Kyc5v34EgqhS11gun+z5HMCub3NYJgfS6sbOtkTrDbGFsvNE p4Dt/sZI8LQgV4Mj93tvc5o=
X-Google-Smtp-Source: AH8x224IobUA0P1BR4djshWfgIf2r4tPu7Xtkf7zNUd97jFgiBdo6TEuhVoCQsIlyj1napv3DXwwlg==
X-Received: by 10.200.112.1 with SMTP id x1mr69577081qtm.138.1517843438637; Mon, 05 Feb 2018 07:10:38 -0800 (PST)
Received: from FrancoisPC (pool-108-48-182-86.washdc.fios.verizon.net. [108.48.182.86]) by smtp.gmail.com with ESMTPSA id l10sm5691558qta.45.2018.02.05.07.10.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Feb 2018 07:10:37 -0800 (PST)
From: François Simon <fygsimon@gmail.com>
To: 'Alexandre Petrescu' <alexandre.petrescu@gmail.com>
Cc: 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>
In-Reply-To: <87888ef4-ae0e-421c-0e48-43b0276f038a@gmail.com>
Date: Mon, 05 Feb 2018 10:10:37 -0500
Message-ID: <001a01d39e93$7ad4e4b0$707eae10$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_001B_01D39E69.92014DB0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQL7ISfFSBtQJ/i74DjDJlbgILh28gG4su6HASuQMD8BaTCMjwKzySiooQ7ZoBA=
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/pYjVktl5haaxMhWic1wnFlkf4S4>
Subject: Re: [ipwave] 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: Mon, 05 Feb 2018 15:10:42 -0000

"Is DSRCS a typo? (correct DSRC)."
-	No typo. DSRCS stands for “Dedicated Short Range Communication Service”

-----Original Message-----
From: Alexandre Petrescu [mailto:alexandre.petrescu@gmail.com] 
Sent: Sunday, February 04, 2018 11:08 AM
To: François Simon <fygsimon@gmail.com>
Cc: 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] On Behalf Of Alexandre 
> Petrescu
> 
> Sent: Monday, January 29, 2018 10:08 AM
> 
> To: 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
> 
>> already provided that information**and references multiple
> 
>> times.]***
> 
> 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?
> 
> 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.
> 
> Alex
> 
> _______________________________________________
> 
> its mailing list
> 
> its@ietf.org <mailto:its@ietf.org> 
> 
> https://www.ietf.org/mailman/listinfo/its
>