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

"Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com> Sat, 09 October 2021 07:25 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 2D5D23A00D6 for <its@ietfa.amsl.com>; Sat, 9 Oct 2021 00:25:44 -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 6g2Dv5eL4uZI for <its@ietfa.amsl.com>; Sat, 9 Oct 2021 00:25:39 -0700 (PDT)
Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) (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 53B953A00C3 for <its@ietf.org>; Sat, 9 Oct 2021 00:25:39 -0700 (PDT)
Received: by mail-lf1-x133.google.com with SMTP id z11so39953898lfj.4 for <its@ietf.org>; Sat, 09 Oct 2021 00:25:39 -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=+iWeO9/9bDvwaapJKESvBssuLTkpYiD/JzlrCzPgOJw=; b=PRxiI09g7E14aGQIAFk1SKivhf9Ge6drWZBbia3qGlBszE1QDQ7PS/gB7ejNKNFTwE Uqj/xKmJxEpXop8SAnVsYDFLMSkPx6cNINwfJ0G8Sj+CmGmlc4/M3wX1euSwrhLu1Cgr 1LIPJ2RKKH4aKNhlsihap5ec3YMWg1hJPH1fOWw0emShCA+SpKEwo6KGEXASlaGJ2zPN ijhhy6ht7+AGhb3I6OR1Iv/ecZoU/dpBdVp2eckd03t8KbWtwZ/fbYR9voDpmOffdMbS KeLVOxYOUE/7R9YyATL7gTaJiuWzIOiiYWW4doGMQ/sOZOiftDY9iYmft3yi/4isruJG OxcQ==
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=+iWeO9/9bDvwaapJKESvBssuLTkpYiD/JzlrCzPgOJw=; b=oYiQi6FX1Le6rbDRdQSNAsHkXwBtqfAjGFPPdD3OFYyeFToeQVOUtgHPrZ5MiIGWxw ebcR3kbvHDdmSKTUS027WdG3CKNWg5JqlkS68oRmx9LK2vA+GMCuqZK9ljHIfDqJvlCB CF7hOXqBmMZeFrTepL7OrEy9kDpgYblUveo3MJ/1VzG2QP3l1CuJlU3920K5V5mXnfEr IPjad2mSKjwSHGraSq9foJ9Jz1TRO7YBmVtYLav+FXelAF6GuJJ0of6ACr3o9lcQxv6k eRmYRcv1TEIijDcsvhJgEsw+RYhFuV2RV7xZCg1BInJkQJ0ud+0RnrBXgSYxySQRYi3l LmTA==
X-Gm-Message-State: AOAM530iiUGZFFWLo83aGWv4gqHEce0YBUqyZcVm4ecRkUyqoEztelAW KE5r415DVlSyL39z/0hF1qamCb/agdFJFgoHIMM=
X-Google-Smtp-Source: ABdhPJz1zknWkUls8g7kXqkzE0gSaPwcWCE6wWvdzhhbb5g54NdQKbpC6rUZQo0xJxgNczpd0YTWTTs5g3eALZkI6dM=
X-Received: by 2002:a05:6512:39d3:: with SMTP id k19mr12739264lfu.258.1633764337229; Sat, 09 Oct 2021 00:25:37 -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: Sat, 9 Oct 2021 16:25:00 +0900
Message-ID: <CAPK2DeyXGAhYZpvL-UwOks6L0xdO0Fy-CRugCVzOkKixYwaoeg@mail.gmail.com>
To: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
Cc: its <its@ietf.org>, Chris Shen <shenyiwen7@gmail.com>, "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000f7a32c05cde666a8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/bVR2nKCulXu0HIVpHv6NqTYIH5o>
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 07:25:44 -0000

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

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> 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
>
>