Re: [ipwave] Éric Vyncke's No Objection on draft-ietf-ipwave-ipv6-over-80211ocb-48: (with COMMENT)

Nabil Benamar <n.benamar@est.umi.ac.ma> Sun, 07 July 2019 20:10 UTC

Return-Path: <n.benamar@est.umi.ac.ma>
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 379BA120176 for <its@ietfa.amsl.com>; Sun, 7 Jul 2019 13:10:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=est-umi-ac-ma.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 GP16hOkfNkSq for <its@ietfa.amsl.com>; Sun, 7 Jul 2019 13:10:54 -0700 (PDT)
Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 62B1F1201D3 for <its@ietf.org>; Sun, 7 Jul 2019 13:10:53 -0700 (PDT)
Received: by mail-io1-xd2b.google.com with SMTP id o9so14753558iom.3 for <its@ietf.org>; Sun, 07 Jul 2019 13:10:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=est-umi-ac-ma.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7MTO/YrOqiM9Xk+Qg07S3CYxa1/ltSSecnPXi6WfEA4=; b=AObKpbu9M6gLYm917HpsUeDxupmJ5LPOkADJgOJYYm/NZLs47ojJ0T+g/5oVaiyW82 wSE+SERRB5XeBxLtpyeZM83VsCJcRpFcp6fyIApoGvt3WAqlgZt8syc4b+gdeTLjfh3u f6WeDy1NafSzrpNQq0i+7V+pA0FGuh5kEjWb7UuOze3HpdiWl4lFJY44QPvWLHunVi4h yeNMQ1x50jhoNpI+V6wPvTprzWc5Mg05mVcoRciGKOJp7PPvZIFs9FlJMk9MN7dQorEm 973RC2LOWddD6asLMsRNgKuGc/04KYm4TlKhF6wQG4ryYkN8e66ZgJQ2lrWruYNowD2v vp+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7MTO/YrOqiM9Xk+Qg07S3CYxa1/ltSSecnPXi6WfEA4=; b=L1TnYp7Yqie8rMCS/qlBiv4V5/p5/A/vmmHdSYE10GtOSFKBdOhyieiRlHOSl/ApRk 3OVu2qoMM2VByYRCrkPaGxXK2NlAK30aYJG4ZmMMchsOhE148jcY5l9K3ccNDtuoMK2/ 4tZgcUDpK95njya02P4fHTtuIGAAb8yFDHaZy+cPsWnrPpktrb2pWznmvo1sCuGKv2lj uHs4ozRBKOBVft2n1rH20crat/Qpd3iEwUZvRLQ7Z6bKOMrje4k4DcN/b44Q+rXnmWz8 F/D+0HQwMshP8f0sT9AICfzCzMkj1vNbErWuVUm1aA6qL9qAaroARGTCRxlc8+dSpFRy 8bTg==
X-Gm-Message-State: APjAAAXLd7qPMBtDXnN7G5d5WFIu2R1aqCuNshS3kdVzcLlc8dLrqj7I 1oQkbsGz/2s19dRb5+BrOuZkbyXzpzraix5KjoSxug==
X-Google-Smtp-Source: APXvYqx1SZsvIt9fFd+axZDC4OrbHaNuL/wHtUY2Gt0riynukMPo3N7TrhH2zYn2/pkBnhWr5Ffre6RKZAgFx1iiRu8=
X-Received: by 2002:a02:a90a:: with SMTP id n10mr16747135jam.61.1562530252547; Sun, 07 Jul 2019 13:10:52 -0700 (PDT)
MIME-Version: 1.0
References: <156251363053.14592.11281412645586709303.idtracker@ietfa.amsl.com>
In-Reply-To: <156251363053.14592.11281412645586709303.idtracker@ietfa.amsl.com>
From: Nabil Benamar <n.benamar@est.umi.ac.ma>
Date: Sun, 07 Jul 2019 21:10:41 +0100
Message-ID: <CAD8vqFdbz+BFRh0aC_0MsDV9RvmozdY-j9U=Y4nU0guRsDW6fg@mail.gmail.com>
To: Éric Vyncke <evyncke@cisco.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-ipwave-ipv6-over-80211ocb@ietf.org, Carlos Bernardos <cjbc@it.uc3m.es>, ipwave-chairs@ietf.org, its@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a77f77058d1cecd1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/KZv5Q-nXK7yyRJHqXOVgWOLLiNY>
Subject: Re: [ipwave] Éric Vyncke's No Objection on draft-ietf-ipwave-ipv6-over-80211ocb-48: (with COMMENT)
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: Sun, 07 Jul 2019 20:11:15 -0000

Dear Éric,

I would like to sincerely thank you for your review. Much appreciated!

Please see my answers in-line below.

On Sun, Jul 7, 2019 at 4:33 PM Éric Vyncke via Datatracker <noreply@ietf.org>
wrote:

> Éric Vyncke has entered the following ballot position for
> draft-ietf-ipwave-ipv6-over-80211ocb-48: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-ipwave-ipv6-over-80211ocb/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Thank you  for the work put into this document. Interesting use case ;-)
>
> Beside the 3 COMMENTs below, I have a question: my understanding is that
> this
> is a P2P link, so, layer-3 multicast packets could easily be sent over
> unicast
> layer-2 IF the other peer is known with its layer-2 address which is
> possibly
> known when forming a OCB "association" (but I am not a WiFi person at all).
> Just curious here ;-)
>

Intersting comment. The thing is that there is no association process in
OCB. Though it belongs to the IEEE 802.11 familly, there are some
differences.
As we said in the text:

OCB (outside the context of a basic service set - BSS): is a mode of
   operation in which a STA is not a member of a BSS and does not
   utilize IEEE Std 802.11 authentication, association, or data

   confidentiality.


> Regards,
>
> -éric
>
> == COMMENTS ==
>
> -- Section 3 --
>
> It is unclear whether a IP-OBU <-> IP-OBU is a use case of this document
> (it is
> mentionned in 4.6 though but it would help the reader to have it mentioned
> in
> section 3).
>

The link model is the following: STA --- 802.11-OCB --- STA.  In

   vehicular networks, STAs can be IP-RSUs and/or IP-OBUs

>
> -- Section 4.4 --
>
> In the discussion of SLAAC, there should be a mention on the presence or
> absence of Router Advertisement and if RA are used: - which entity sends
> this
> RA (probably IP-RSU), - does RA contain PIO ? - what are the
> recommendation for
> router lifetime (and PIO timers) ?
>

I agree. We need to add a mention about who sends RAs

>
> -- Missing --
>
> Duplicate Address Detection is only mentioned in Appendix I and it is
> unclear
> whether optimistic DAD (even for LLA) should/must be used.
>
In section 4.5.1, we say that :

This document is scoped for Address Resolution (AR) and Duplicate

   Address Detection (DAD) per RFC 4861
<https://tools.ietf.org/html/rfc4861>

Thanks again.

-- 

Best Regards

Nabil Benamar
Associate Professor
Department of Computer Sciences
School of Technology
Moulay Ismail University
Meknes. Morocco