[secdir] Secdir telechat review of draft-ietf-ipwave-vehicular-networking-28

Daniel Migault via Datatracker <noreply@ietf.org> Mon, 09 May 2022 13:24 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: secdir@ietf.org
Delivered-To: secdir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 540B1C15E6DA; Mon, 9 May 2022 06:24:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Daniel Migault via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Cc: draft-ietf-ipwave-vehicular-networking.all@ietf.org, its@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 8.1.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <165210265233.19575.17646910253336534079@ietfa.amsl.com>
Reply-To: Daniel Migault <daniel.migault@ericsson.com>
Date: Mon, 09 May 2022 06:24:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/SN6j6t1X5ZBopgXV_eZzcFY74tI>
Subject: [secdir] Secdir telechat review of draft-ietf-ipwave-vehicular-networking-28
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.34
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: Mon, 09 May 2022 13:24:12 -0000

Reviewer: Daniel Migault
Review result: Has Nits

Hi,

I am still a bit uncomfortable with the message of the use case 3.3 where
pedestrians or cyclists need to carry a mobile phone to avoid being knocked
down by a car - at least that is how I read it.

The reason is that, in many places, drivers are not paying enough attention to
pedestrians and cyclists - even considering their presence on the road as an
aggression. As a rebound effect your application that aims at providing more
security for the vulnerable pedestrian or cyclist, is likely to result in
walking/cycling being more dangerous. Drivers may rely on that application to
detect the presence of pedestrians and cyclists and defer the responsibility of
being knocked down to the pedestrian or cyclist wearing this application. This
is problematic as drivers will likely be even less careful toward pedestrians
and cyclists which increases the most vulnerable persons (here I am thinking of
kids) as they do not have such mobile phones.

For this reason, I do not think the use case is neither appropriate, nor
convincing. The use case sounded to me a bit like the "IPv6 fridge". I would
rather consider such use case more appropriate for specific environments such
as construction sites where everyone may be required to carry such
applications. My recommendation would be to reformulate the use case for these
environments. This probably requires very minor changes in the text.

That said, I let you decide what to do with it, as it might also reflect a
personal view, and I do not want to slow the publication of document. Feel free
to let me know, if you need more information.

Yours,
Daniel

   """
   For Vehicle-to-Pedestrian (V2P), a vehicle can directly communicate
   with a pedestrian's smartphone by V2X without IP-RSU relaying.
   Light-weight mobile nodes such as bicycles may also communicate
   directly with a vehicle for collision avoidance using V2V.  Note that
   it is true that a pedestrian or a cyclist may have a higher risk of
   being hit by a vehicle if they are not with a smartphone in the
   current setting. """