Re: [ipwave] Comments on draft-ietf-ipwave-vehicular-networking-23

Alexandre Petrescu <alexandre.petrescu@gmail.com> Sat, 09 October 2021 10:01 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 A56FF3A0872 for <its@ietfa.amsl.com>; Sat, 9 Oct 2021 03:01:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.668
X-Spam-Level:
X-Spam-Status: No, score=0.668 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 6sSxFFH8a-kg for <its@ietfa.amsl.com>; Sat, 9 Oct 2021 03:01:04 -0700 (PDT)
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 8ECB83A0778 for <its@ietf.org>; Sat, 9 Oct 2021 03:01:02 -0700 (PDT)
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 199A0xqA020745 for <its@ietf.org>; Sat, 9 Oct 2021 12:00:59 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id CAD0F20134F for <its@ietf.org>; Sat, 9 Oct 2021 12:00:59 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id BF4CD200DDA for <its@ietf.org>; Sat, 9 Oct 2021 12:00:59 +0200 (CEST)
Received: from [10.14.0.118] ([10.14.0.118]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 199A0x1m002771 for <its@ietf.org>; Sat, 9 Oct 2021 12:00:59 +0200
To: its@ietf.org
References: <e60add66f857478da782de2a536b9062@boeing.com> <CAPK2DeyXGAhYZpvL-UwOks6L0xdO0Fy-CRugCVzOkKixYwaoeg@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <35e9af7d-54fa-7afa-dd04-e28a2a398038@gmail.com>
Date: Sat, 9 Oct 2021 12:00:59 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: <CAPK2DeyXGAhYZpvL-UwOks6L0xdO0Fy-CRugCVzOkKixYwaoeg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------87CF84DCE880ECC28FAB0D36"
Content-Language: fr
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/LX_T9z1Sn8ooigbyt9hskfka3vY>
Subject: Re: [ipwave] Comments on draft-ietf-ipwave-vehicular-networking-23
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: Sat, 09 Oct 2021 10:01:17 -0000

Thank you for the update.

With respect to authorship: there is a list of Authors, and an Editor.  
But the address on page 50 is titled 'Author's Address' whereas it 
should be titled 'Editor's address'.

Maybe that is a problem with xml2rfc, or something else.

Alex

Le 09/10/2021 à 09:25, Mr. Jaehoon Paul Jeong a écrit :
> Hi Fred,
> I have address all your comments on the revision of IPWAVE PS Draft:
> https://datatracker.ietf.org/doc/html/draft-ietf-ipwave-vehicular-networking-24 
> <https://datatracker.ietf.org/doc/html/draft-ietf-ipwave-vehicular-networking-24>
>
> Thanks for your suggestion.
>
> Best Regards,
> Paul
>
>
> On Fri, Sep 24, 2021 at 11:05 PM Templin (US), Fred L 
> <Fred.L.Templin@boeing.com <mailto:Fred.L.Templin@boeing.com>> wrote:
>
>     Paul, a couple of comments on the -23 draft version:
>
>     1) For AERO, change the title expansion to “Automatic Extended
>     Route Optimization”.
>
>     2) The correct references for AERO and OMNI are:
>
>     https://datatracker.ietf.org/doc/draft-templin-6man-aero/34/
>     <https://datatracker.ietf.org/doc/draft-templin-6man-aero/34/>
>     https://datatracker.ietf.org/doc/draft-templin-6man-omni/47/
>     <https://datatracker.ietf.org/doc/draft-templin-6man-omni/47/>
>
>     3) Appendix B now seems to say a lot about RPL and not much about
>     AERO/OMNI.
>     Please add the following to Appendix B:
>
>     "AERO and OMNI together securely and efficiently address the “6 M’s of
>     Modern Internetworking” for mobile V2V, V2I and V2X Clients,
>     including:
>
>     1. Multilink – a Client's ability to coordinate multiple diverse
>     underlying data links as a
>     single logical unit (i.e., the OMNI interface) to achieve the
>     required communications
>     performance and reliability objectives.
>
>     2. Multinet - the ability to span the OMNI link over a segment
>     routing topology with multiple
>     diverse administrative domain network segments while maintaining
>     seamless end-to-end
>     communications between mobile Clients and correspondents such as
>     air traffic controllers,
>     fleet administrators, etc.
>
>     3. Mobility - a Client's ability to change network points of
>     attachment (e.g., moving between
>     wireless base stations) which may result in an underlying
>     interface address change, but
>     without disruptions to ongoing communication sessions with peers
>     over the OMNI link.
>
>     4. Multicast - the ability to send a single network transmission
>     that reaches multiple
>     Clients belonging to the same interest group, but without
>     disturbing other Clients not
>     subscribed to the interest group.
>
>     5. Multihop - a mobile Client vehicle-to-vehicle relaying
>     capability useful when multiple
>     forwarding hops between vehicles may be necessary to "reach back"
>     to an infrastructure
>     access point connection to the OMNI link.
>
>     6. MTU assurance - the ability to deliver packets of various
>     robust sizes between peers
>     without loss due to a link size restriction, and to dynamically
>     adjust packets sizes to
>     achieve the optimal performance for each independent traffic flow."
>
>     That is all I have for now, but will let you know if I notice
>     anything else.
>
>     Thanks - Fred
>
>
> _______________________________________________
> its mailing list
> its@ietf.org
> https://www.ietf.org/mailman/listinfo/its