Re: [ipwave] [Gen-art] Genart last call review of draft-ietf-ipwave-ipv6-over-80211ocb-46

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 17 June 2019 14:12 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 2C936120127 for <its@ietfa.amsl.com>; Mon, 17 Jun 2019 07:12:00 -0700 (PDT)
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_HELO_NONE=0.001, 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 CUGvCBenz8Oe for <its@ietfa.amsl.com>; Mon, 17 Jun 2019 07:11:57 -0700 (PDT)
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 5CDEF12011C for <its@ietf.org>; Mon, 17 Jun 2019 07:11:57 -0700 (PDT)
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 x5HEBsra125166 for <its@ietf.org>; Mon, 17 Jun 2019 16:11:54 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id CB80E207AB0 for <its@ietf.org>; Mon, 17 Jun 2019 16:11:54 +0200 (CEST)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id C1F3A207AAE for <its@ietf.org>; Mon, 17 Jun 2019 16:11:54 +0200 (CEST)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x5HEBsXB008168 for <its@ietf.org>; Mon, 17 Jun 2019 16:11:54 +0200
To: its@ietf.org
References: <156067514313.12185.6559961431451739070@ietfa.amsl.com> <CAD8vqFcngv75CvQTSY1vnL1TsLWoFVtw8b_q6hvBRRdSMDZZsw@mail.gmail.com> <6E58094ECC8D8344914996DAD28F1CCD18D37579@dggemm526-mbx.china.huawei.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <8cd9eb28-35a6-600f-c3d7-4e61972bacde@gmail.com>
Date: Mon, 17 Jun 2019 16:11:54 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.1
MIME-Version: 1.0
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD18D37579@dggemm526-mbx.china.huawei.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/jIhYBQXwKvlOSIquk24AtJG9SwY>
Subject: Re: [ipwave] [Gen-art] Genart last call review of draft-ietf-ipwave-ipv6-over-80211ocb-46
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF <its.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/its>, <mailto:its-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/its/>
List-Post: <mailto:its@ietf.org>
List-Help: <mailto:its-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/its>, <mailto:its-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jun 2019 14:12:00 -0000

I would like to ask for comparison to implementation too.

I dont want my implementation to become non-standard because it does not 
change its MAC address all the time.

Le 17/06/2019 à 15:25, Roni Even (A) a écrit :
> Thanks,
> 
> The only comment left is:
> 
> 
> 2. In section 5.2 "The policy dictating when the MAC address is changed 
> on the
> 802.11-OCB interface is to-be-determined.". Reading the next sentence it 
> looks
> to me that this is needed as part of the solution and should not be left for
> the unknown future.
> 
> Should we reformulate here?
> 
> I was expecting some recommendation since the changing of MAC address is 
> important to address privacy issues (discussed in section 5). Currently 
> it is left open with no recommendation , only saying that dynamic change 
> of MAC address is needed.
> 
> Maybe the document should have some normative language for example in 
> section 5.1 that will say that IP-OBU MUST dynamic change their MAC 
> addresses
> 
> Did the document go through security area review?
> 
> Roni
> 
> *From:*Gen-art [mailto:gen-art-bounces@ietf.org] *On Behalf Of *NABIL 
> BENAMAR
> *Sent:* Monday, June 17, 2019 12:48 PM
> *To:* Roni Even
> *Cc:* gen-art@ietf.org; IETF Discussion; its@ietf.org; 
> draft-ietf-ipwave-ipv6-over-80211ocb.all@ietf.org
> *Subject:* Re: [Gen-art] Genart last call review of 
> draft-ietf-ipwave-ipv6-over-80211ocb-46
> 
> Dear Roni,
> 
> Thank you for your review.
> 
> Please, see my answers below.
> 
> On Sun, Jun 16, 2019, 09:52 Roni Even via Datatracker <noreply@ietf.org 
> <mailto:noreply@ietf.org>> wrote:
> 
>     Reviewer: Roni Even
>     Review result: Almost Ready
> 
>     I am the assigned Gen-ART reviewer for this draft. The General Area
>     Review Team (Gen-ART) reviews all IETF documents being processed
>     by the IESG for the IETF Chair.  Please treat these comments just
>     like any other last call comments.
> 
>     For more information, please see the FAQ at
> 
>     <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
> 
>     Document: draft-ietf-ipwave-ipv6-over-80211ocb-??
>     Reviewer: Roni Even
>     Review Date: 2019-06-16
>     IETF LC End Date: 2019-06-26
>     IESG Telechat date: Not scheduled for a telechat
> 
>     Summary:
>     The document is almost ready for publication as a standard track RFC
> 
>     Major issues:
> 
>     Minor issues:
> 
>     1. Section 4.2  says "IP packets MUST be transmitted over 802.11-OCB
>     media as
>     QoS Data" while appendix F say "The STA may send data frames of
>     subtype Data,
>     Null, QoS Data, and
>            QoS Null.
> 
> I will update the appendix to reflect the text in section 4.2.
> 
> 
>     2. In section 5.2 "The policy dictating when the MAC address is
>     changed on the
>     802.11-OCB interface is to-be-determined.". Reading the next
>     sentence it looks
>     to me that this is needed as part of the solution and should not be
>     left for
>     the unknown future.
> 
> Should we reformulate here?
> 
> 
>     3. In Appendix I 4th paragraph " However, this does not apply if TBD
>     TBD TBD. "
>     .. What are the TBDs?
> 
> The whole sentence will be removed.
> 
> 
>     Nits/editorial comments:
>     1. In appendix I last paragraph "Support of RFC 8505 is may be
>     implemented on
>     OCB." should be "Support of RFC 8505 may be implemented on OCB." 2.
>     In Appendix
>     I "OCB nodes that support RFC 8505 would support the 6LN operation
>     in order to
>     act as a host".  I think that instead of "would" it should be
>     "should"  also if
>     this is a recommendation why not have this paragraph not in an
>     appendix with
>     "MAY" and "SHOULD
> 
> Agreed.
> 
> 
> _______________________________________________
> its mailing list
> its@ietf.org
> https://www.ietf.org/mailman/listinfo/its
>