Re: [secdir] [ipwave] Secdir telechat review of draft-ietf-ipwave-vehicular-networking-27

"Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com> Wed, 30 March 2022 16:53 UTC

Return-Path: <jaehoon.paul@gmail.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AF753A153B; Wed, 30 Mar 2022 09:53:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level:
X-Spam-Status: No, score=-2.087 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_FREEMAIL_DOC_PDF=0.01, T_HK_NAME_FM_MR_MRS=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham 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 HB1VW754b7_j; Wed, 30 Mar 2022 09:53:21 -0700 (PDT)
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (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 C2B3C3A1804; Wed, 30 Mar 2022 09:52:33 -0700 (PDT)
Received: by mail-lf1-x136.google.com with SMTP id p10so30982411lfa.12; Wed, 30 Mar 2022 09:52:33 -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=5nTYs9kZWWzbHkx50OPu44lK/0PtIXmtCR4kQd7d/3E=; b=Te+W6tzgoE5Hs37gs0eqXcQZ2IUG1BuKLE5t19SogJXdj/fLogDXehkWdlrq2Y7ATj 9XoDU0z/09N2+5dL9y0f+Cm9D0jScO6iBDDU41raGvGfhjWkSjMCD7B4snHzk69rZh7g XdU8AEbLu65vYA/swISBLvfp66RhP3V/5issQ+GZB8N3kU7JcLeb+Ink9BOplbrQ+yuS v+JvN9IGZRTAKiPTc2B47O5XjQ9mM+REhmTaBqVSRR1Zx62X5wWKjL9A7xec0fGl25DO 5RiFfbjy1FceJxGhben0iHVuqZyrvW5m7A18dlv0xevTBsCZIW0mdte9BOQNRxOEGEfi teww==
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=5nTYs9kZWWzbHkx50OPu44lK/0PtIXmtCR4kQd7d/3E=; b=Y9n1S3xMhhOjjmFxtucAFCmj26Ouy6pS8l+BfuErfl5QW4Wh0NECwl8kmVK12ClZg+ 0/6v0j6bDfibhlCbWdGnEUtlrGOmbKSmmj+MJKubJWSyTAMJmxsD1PQMhVlskutuZWDA 7OCPDsjbDhfFK8Fvt+uZdqf55HHFBqeyJanjOQ5fobmLfy3BL2nvTb3w+msopAdFSToJ /QONtNF1W+oqqea+eCuN5anlgkkJFO4Gc6bEOrzEsveyhzTUzni0FljCUSFYq5zfAKx9 fpAOH9WH78CHxox0n8fYcCBZDB2zhHmxsBAJrTEJaqNlzzaPFeHqEaVW6Nvk+0j2u39z 5C3w==
X-Gm-Message-State: AOAM531qVhyMqIkgcHMLvNE1+w6cKgqWNe3CBb7JanVOnslnmsNnqTZc L00krQbQ0+oV0cnJG7t43DCGZDL0kPS7YdSH7iB4ioYxK+I=
X-Google-Smtp-Source: ABdhPJx07cRE6FEfTQEFLH9ylYB7arrv3ZEtZjD5aWplMHSF8XEneIC3PRvwuQXv5ai1UWMRqzUfHddMn11beVl/JhQ=
X-Received: by 2002:a19:650d:0:b0:448:6bf1:ab65 with SMTP id z13-20020a19650d000000b004486bf1ab65mr7647784lfb.668.1648659150783; Wed, 30 Mar 2022 09:52:30 -0700 (PDT)
MIME-Version: 1.0
References: <164624978894.17953.13607898323269640268@ietfa.amsl.com> <DM6PR15MB368990AB8B44D06252BAA3F9E3039@DM6PR15MB3689.namprd15.prod.outlook.com>
In-Reply-To: <DM6PR15MB368990AB8B44D06252BAA3F9E3039@DM6PR15MB3689.namprd15.prod.outlook.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Thu, 31 Mar 2022 01:51:53 +0900
Message-ID: <CAPK2DexkP2L-7L7M0rV4U=LOuqkmn6HQeycM7ZNs=pgt_-wZUw@mail.gmail.com>
To: Daniel Migault <daniel.migault=40ericsson.com@dmarc.ietf.org>
Cc: "secdir@ietf.org" <secdir@ietf.org>, Daniel Migault <daniel.migault@ericsson.com>, "last-call@ietf.org" <last-call@ietf.org>, "its@ietf.org" <its@ietf.org>, Chris Shen <shenyiwen7@gmail.com>, skku-iotlab-members <skku-iotlab-members@googlegroups.com>, "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Content-Type: multipart/mixed; boundary="00000000000009f6ed05db725f74"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/Vmbln3dBbFpX65J82vKe6ZB7IrE>
Subject: Re: [secdir] [ipwave] Secdir telechat review of draft-ietf-ipwave-vehicular-networking-27
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2022 16:53:25 -0000

Hi Daniel,
Here is the revision of IPWAVE PS Draft:

https://datatracker.ietf.org/doc/html/draft-ietf-ipwave-vehicular-networking-28

I attach a revision letter to explain how Chris and I have addressed your
comments
on the revision.

Thanks.

Best Regards,
Paul


On Thu, Mar 3, 2022 at 4:40 AM Daniel Migault <daniel.migault=
40ericsson.com@dmarc.ietf.org> wrote:

> -- clicking too fast
>
> Reviewer: Daniel Migault
> Review result: Has Issues
>
> Hi,
>
> I have reviewed this document as part of the security directorate's
> ongoing effort to review all IETF documents being processed by the
> IESG.  These comments were written primarily for the benefit of the
> security area directors.  Document editors and WG chairs should treat
> these comments just like any other last call comments.
>
> Please find my comments below:
>
> 1.  Introduction
>
>    Vehicular networking studies have mainly focused on improving safety
>    and efficiency, and also enabling entertainment in vehicular
>    networks.  The Federal Communications Commission (FCC) in the US
>    allocated wireless channels for Dedicated Short-Range Communications
>    (DSRC) [DSRC] in the Intelligent Transportation Systems (ITS) with
>    the frequency band of 5.850 - 5.925 GHz (i.e., 5.9 GHz band).  DSRC-
>    based wireless communications can support vehicle-to-vehicle (V2V),
>    vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X)
>    networking.  The European Union (EU) allocated radio spectrum for
>    safety-related and non-safety-related applications of ITS with the
>    frequency band of 5.875 - 5.905 GHz, as part of the Commission
>    Decision 2008/671/EC [EU-2008-671-EC].
>
> <mglt>
> I am wondering US/EU covers all spectrum allocation worldwide ?
> </mglt>
>
> 3.2.  V2I
>
>    The emergency communication between accident vehicles (or emergency
>    vehicles) and a TCC can be performed via either IP-RSU or 4G-LTE
>    networks.  The First Responder Network Authority (FirstNet)
>    [FirstNet] is provided by the US government to establish, operate,
>    and maintain an interoperable public safety broadband network for
>    safety and security network services, e.g., emergency calls.  The
>    construction of the nationwide FirstNet network requires each state
>    in the US to have a Radio Access Network (RAN) that will connect to
>    the FirstNet's network core.  The current RAN is mainly constructed
>    using 4G-LTE for the communication between a vehicle and an
>    infrastructure node (i.e., V2I) [FirstNet-Report], but it is expected
>    that DSRC-based vehicular networks [DSRC] will be available for V2I
>    and V2V in the near future.
>
> <mglt>
> Is this use case restricted to the US or do we have any equivalent in EU
> for
> example ? <mglt>
>
> 3.3.  V2X
>
>    The use case of V2X networking discussed in this section is for a
>    pedestrian protection service.
>
> <mglt>
> I do have an issue with such use case - of course if my understanding is
> correct. My understanding from the description is that the use case
> explains
> how pedestrian can advertise its presence to a vehicle so avoid the
> vehicle to
> hit that pedestrian. Such assumption does not seem to me acceptable as not
> everyone has a phone, and their security - from a vehicle perspective -
> MUST
> NOT be provided by such a mechanism as it would given a false sense of
> security. If a vehicle is not able to detect a pedestrian unless this
> pedestrian has a working smartphone with a specific application, the
> problem is
> bigger and out of scope of the IETF. I can also see that in some
> countries, it
> will become the pedestrian's fault if it is hit without its application.
> As I
> understand it, I find this use case extremely dangerous, so my request
> would be
> to remove it or if I misunderstood it to clarify its scope. <mglt>
>
>
> ________________________________________
> From: secdir <secdir-bounces@ietf.org> on behalf of Daniel Migault via
> Datatracker <noreply@ietf.org>
> Sent: Wednesday, March 2, 2022 2:36 PM
> To: secdir@ietf.org
> Cc: last-call@ietf.org;
> draft-ietf-ipwave-vehicular-networking.all@ietf.org; its@ietf.org
> Subject: [secdir] Secdir telechat review of
> draft-ietf-ipwave-vehicular-networking-27
>
> Reviewer: Daniel Migault
> Review result: Has Issues
>
> 1.  Introduction
>
>    Vehicular networking studies have mainly focused on improving safety
>    and efficiency, and also enabling entertainment in vehicular
>    networks.  The Federal Communications Commission (FCC) in the US
>    allocated wireless channels for Dedicated Short-Range Communications
>    (DSRC) [DSRC] in the Intelligent Transportation Systems (ITS) with
>    the frequency band of 5.850 - 5.925 GHz (i.e., 5.9 GHz band).  DSRC-
>    based wireless communications can support vehicle-to-vehicle (V2V),
>    vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X)
>    networking.  The European Union (EU) allocated radio spectrum for
>    safety-related and non-safety-related applications of ITS with the
>    frequency band of 5.875 - 5.905 GHz, as part of the Commission
>    Decision 2008/671/EC [EU-2008-671-EC].
>
> <mglt>
> I am wondering US/EU covers all spectrum allocation worldwide ?
> </mglt>
>
> 3.2.  V2I
>
>    The emergency communication between accident vehicles (or emergency
>    vehicles) and a TCC can be performed via either IP-RSU or 4G-LTE
>    networks.  The First Responder Network Authority (FirstNet)
>    [FirstNet] is provided by the US government to establish, operate,
>    and maintain an interoperable public safety broadband network for
>    safety and security network services, e.g., emergency calls.  The
>    construction of the nationwide FirstNet network requires each state
>    in the US to have a Radio Access Network (RAN) that will connect to
>    the FirstNet's network core.  The current RAN is mainly constructed
>    using 4G-LTE for the communication between a vehicle and an
>    infrastructure node (i.e., V2I) [FirstNet-Report], but it is expected
>    that DSRC-based vehicular networks [DSRC] will be available for V2I
>    and V2V in the near future.
>
> <mglt>
> Is this use case restricted to the US or do we have any equivalent in EU
> for
> example ? <mglt>
>
> 3.3.  V2X
>
>    The use case of V2X networking discussed in this section is for a
>    pedestrian protection service.
>
> <mglt>
> I do have an issue with such use case - of course if my understanding is
> correct. My understanding from the description is that the use case
> explains
> how pedestrian can advertise its presence to a vehicle so avoid the
> vehicle to
> hit that pedestrian. Such assumption does not seem to me acceptable as not
> everyone has a phone, and their security - from a vehicle perspective -
> MUST
> NOT be provided by such a mechanism as it would given a false sense of
> security. If a vehicle is not able to detect a pedestrian unless this
> pedestrian has a working smartphone with a specific application, the
> problem is
> bigger and out of scope of the IETF. I can also see that in some
> countries, it
> will become the pedestrian's fault if it is hit without its application.
> As I
> understand it, I find this use case extremely dangerous, so my request
> would be
> to remove it or if I misunderstood it to clarify its scope. <mglt>
>
>
>
> _______________________________________________
> secdir mailing list
> secdir@ietf.org
> https://www.ietf.org/mailman/listinfo/secdir
> wiki: https://trac.ietf.org/trac/sec/wiki/SecDirReview
>
> _______________________________________________
> its mailing list
> its@ietf.org
> https://www.ietf.org/mailman/listinfo/its
>