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

"Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com> Thu, 30 September 2021 10:18 UTC

Return-Path: <jaehoon.paul@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 C35BD3A0A8E for <its@ietfa.amsl.com>; Thu, 30 Sep 2021 03:18:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.555
X-Spam-Level:
X-Spam-Status: No, score=-1.555 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HK_NAME_FM_MR_MRS=0.542, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 nXp3zy7P4x6R for <its@ietfa.amsl.com>; Thu, 30 Sep 2021 03:18:32 -0700 (PDT)
Received: from mail-lf1-x12d.google.com (mail-lf1-x12d.google.com [IPv6:2a00:1450:4864:20::12d]) (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 158A73A0778 for <its@ietf.org>; Thu, 30 Sep 2021 03:18:32 -0700 (PDT)
Received: by mail-lf1-x12d.google.com with SMTP id b15so22970785lfe.7 for <its@ietf.org>; Thu, 30 Sep 2021 03:18:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=9DCydKeQ+GOs5b4Bmk9St2JjzFU3gKrCjidgi7TeCyE=; b=mZqKaebfYh4kMmkHf9MmkryHxZY6nVB5bHPdcRNdSaL0z84Dq0Ov3gc9FSMTqK5o2U iqFkQ7HDxHvExeDy8trg/BNhN1+OvF5i+tHGnX9ynllBigbXF8veI+rXrauCKO7P8urK TBrb4yTc28TomCuAeS9zfHRjcU5Ve3bAMW0bD3vo16L/lgkK/FgHnKSREYWomLVcfELf qYUHWoG0l4KZt/VWcJAqFNsXdAjCd2k8JInYqo1QL/2e3z2hB2TDsfYpubsDvMCsB1Kb ur++nfeVr+8vQYvE/AJyEKhthKcJeRDAAv6rMhCsSM74o25bL1b8wc2CCu0igaHyHFps w8mw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9DCydKeQ+GOs5b4Bmk9St2JjzFU3gKrCjidgi7TeCyE=; b=wSoFlcg6LT1ig88pP6/3EI6tGPP20PRDBi+LSg18IwCwByZQgU9RbGLOetToQurBc3 aZNCf05vucjwwcOSs/BklVZ6G8xkWRaPYOeffSQVFGCyUtEqSnVzKVAR6kKVA1ippk2Q j+ftQaJpsq62xYMzloZJad2T6bLxGIGrPcqNusnhJtmnx9Iimwo3Ax0NobXapHq7T9ra Bz2WgqlQOVVnuDIZ1WMvDwAqgexs9JG+eM98rz3/roBOWy4wFGBALlFowpHQ/i2fxV3z VVOuxILm8lC0lWP0VTLUYVQ11TIBTEaQWYVMh34MqnYUe86qVLXoNg+ZZRelhjc2SQnK 1xUg==
X-Gm-Message-State: AOAM530mh+8o1vjpVtrQ6UeV5Wnvi8OYMKBIP8nCSgHw8dRUpB7KYdMF W/ffvMUvh6/24DKMp0CtzQa9Wc4eDjimOx6rdG8=
X-Google-Smtp-Source: ABdhPJyMdhg34t5hLnr9RV99P3GKMzy1fgTnTbIHwXml9VZVf0ANJ7+RB1dp5vlvvDZwniMAUAsxCEhF/2ShV1ZNMzM=
X-Received: by 2002:a2e:a5c5:: with SMTP id n5mr5198558ljp.497.1632997109629; Thu, 30 Sep 2021 03:18:29 -0700 (PDT)
MIME-Version: 1.0
References: <e60add66f857478da782de2a536b9062@boeing.com>
In-Reply-To: <e60add66f857478da782de2a536b9062@boeing.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Thu, 30 Sep 2021 19:17:53 +0900
Message-ID: <CAPK2DezT63rrF3rccN_J3bRAT2Hxv9uZ9V=8HWQpf4ezeNpv=w@mail.gmail.com>
To: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
Cc: its <its@ietf.org>, "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000a3872b05cd33c42c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/s3uogj4Cl5VH95mEMVj-QIcjmpo>
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: Thu, 30 Sep 2021 10:18:37 -0000

Hi Fred,
Sure, I will add your suggested text for AERO and OMNI to the Appendix B of
our IPWAVE PS draft
along with your suggested updates.

Thanks.

Best Regards,
Paul

On Fri, Sep 24, 2021 at 11:05 PM Templin (US), Fred L <
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-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
>
>