Re: [ipwave] comments on the TLS certs draft

William Whyte <wwhyte@onboardsecurity.com> Fri, 29 March 2019 17:37 UTC

Return-Path: <wwhyte@onboardsecurity.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 56463120270 for <its@ietfa.amsl.com>; Fri, 29 Mar 2019 10:37:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=onboardsecurity-com.20150623.gappssmtp.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 NDxAuObKZh-Z for <its@ietfa.amsl.com>; Fri, 29 Mar 2019 10:37:21 -0700 (PDT)
Received: from mail-pl1-x633.google.com (mail-pl1-x633.google.com [IPv6:2607:f8b0:4864:20::633]) (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 C439E12008A for <its@ietf.org>; Fri, 29 Mar 2019 10:37:21 -0700 (PDT)
Received: by mail-pl1-x633.google.com with SMTP id bf11so1340218plb.12 for <its@ietf.org>; Fri, 29 Mar 2019 10:37:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=onboardsecurity-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ACIOYVuAO5+gd2XFYzeMATNaSBAMHyAAi+u6tuHrB9A=; b=o4zduiKj+q5qQxNlIIz5KkYOCSVVDDL2zjlUCM4ZmHTn3EJLKReTdhQYJAUBu0qerK lg0Ti91FQrvobSZN2OX3Qilm4goVfRhGxcduH5lF5STBLK3pvKoCBeAw1pvC8NUmwNdr iEDa8jwbQLEKBUA56FHTPQ96OCOWBqyEoBDNeIjLmZMvKhQmg+7cFnZhnvzvogzjfQrC YkM++XbcU2ynvXJ6pqPifd6sPzttfdRntK7f+UcN2+TjRnDivXq1nqheOBjEslDMOmyC lE5jauRH9Vg+6zUcwTBovzCXTqDq9KMSreCDHKrOC9Bo69mHh4gRLaTeR5q7wllTAfrs ydkg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ACIOYVuAO5+gd2XFYzeMATNaSBAMHyAAi+u6tuHrB9A=; b=TB/K+69rUHbolGUQ0cM6ZfPO+SLP2uzdX1O7VG8RNz3clMesu+NwCUJ8lm0fQCnXdx bPN06vmhmjnei/GYfL1dteVkOKn8cuYTApkesfF+UdHADxTfb6FoY7/o3BtqBrxLes/H LK3SJuboBTPBQKCbHx74/IDYrfltz+GzKhh0H9Cj4MsBTp7KE3hrXtrbHun0l2V/Xi0E EjQuVtVGJ0YbofFeXoY2YQblL/Jhuz6vw4UEoqcw7Y5H1Gy05p3dr1GEVZcdlrOPrREk TY9GTl4snbsM/EET0tI43qbFG63BvTJ4eTnW4593cWuW3BD24uM3MXbY5iPGHl85Ui0H Cdaw==
X-Gm-Message-State: APjAAAUhTVpLTuu6Pm9zI7490EvGshjd3zZduoVyaVOwp9SwiDjJ8RX5 7bWZbPEx1QKhUx0GtkFu7P+O6vVnBXYb+HLDE0VtIA==
X-Google-Smtp-Source: APXvYqzy51ztYMV+p6D5zoDes0yah5QYc4+OK/sbIHW6Po0GbArNdZ6AFf+BITD830goOSkyyCctrS6fwbwew6kXTd8=
X-Received: by 2002:a17:902:3183:: with SMTP id x3mr49745305plb.170.1553881041240; Fri, 29 Mar 2019 10:37:21 -0700 (PDT)
MIME-Version: 1.0
References: <e4f79bf5-4b61-73f3-3fef-6080a95d2209@gmail.com> <CAND9ES1n9obVvSi7TrDjPeBYkPLj=K7djQFBhN2+WuoQvNkRZQ@mail.gmail.com> <483e04fa-8629-dab7-66f6-8eb0bc7a5180@gmail.com>
In-Reply-To: <483e04fa-8629-dab7-66f6-8eb0bc7a5180@gmail.com>
From: William Whyte <wwhyte@onboardsecurity.com>
Date: Fri, 29 Mar 2019 13:37:09 -0400
Message-ID: <CAND9ES0Hu=W6zXf66NYdMHRDzLMyj95MSObzmTQztfskqVR9ng@mail.gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: "its@ietf.org" <its@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007c98ac05853f1fc2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/GXI9V1PZMEd0yseslLrLXOmeN-M>
Subject: Re: [ipwave] comments on the TLS certs draft
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: Fri, 29 Mar 2019 17:37:24 -0000

Hi Alex -- you can get certificates from
https://www.ghsiss.com/v2x-certificates/, if you have a 1609.2/103 097
implementation. There's a java implementation of 1609.2/103 097 here:
https://github.com/pvendil/c2c-common. I can't vouch for its quality. A
number of companies (including mine) will license a C/C++ implementation to
you.

Note that C-ITS certificates aren't X.509 certificates with ITS extensions,
they're a completely different and incompatible format. Your X.509
libraries won't be any use for this.

Cheers,

William

On Fri, Mar 29, 2019 at 11:17 AM Alexandre Petrescu <
alexandre.petrescu@gmail.com> wrote:

> I agree with the statements about deployment expectation and available
> commercial support, and with the existing sdos and sites asking for this
> draft.
>
> On my side, I work for a few small deployments as well.
>
> I need certificates now.
>
> Allow me to be specific about my case.
>
> I am in France: in order to obtain ITS-specific certificates I got
> redirected to a French enterprise named IDnomic.  It is a great company
> (presumably part of what you refer to as 'commercial support'). That has
> a website with ITS described as Object-ID
> https://www.idnomic.com/object-id/
>
> However, on that web page, there is no button to press to ask a
> certificate.  IDnomic is not like, let's say, I asked a certificate to
> Let's Encrypt.   Let's Encrypt can offer me certificates in an automated
> manner; and not least important - for free.
>
> On the downside, Let's Encrypt certificates are not specific for
> Vehicular networks.  (I suppose Let's Encrypt never heard about ITS
> extensions to certificates).
>
> In this situation, what I do in my deployments, is to generate our own
> certificates, and sign them by our own CAs created locally.  The cars
> and traffic lights connect to our own openvpn server; they understand
> each other, because under same authority.
>
> Yet, this situation is not something that can scale: I dont want more
> and more vehicles to connect to my server.  It risks becoming a single
> point of failure.
>
> As a side note, I take advantage of this discussion to ask whether there
> is software implementation, or howto, that allows me to generate easily
> certificates with ITS extensions described in this draft.
>
> I need these now (well, during the following months).
>
> Alex
>
> Le 29/03/2019 à 13:38, William Whyte a écrit :
> > Alex, these certs are going to be widely deployed, and there is good
> > commercial support for them. We have standards organizations and
> > deployment sites asking for this draft.
> >
> > Cheers,
> >
> > William
> >
> >
> > On Fri, Mar 29, 2019 at 8:37 AM Alexandre Petrescu
> > <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>>
> wrote:
> >
> >     draft-tls-certieee1609-02
> >
> >     draft-msahli-ipwave-ieee1609-00.txt
> >
> >
> >     The certificates are highly necessary for securing IP based
> >     communications in vehicle networks.
> >
> >     But the conditions of their use may prevent deployment.
> >
> >     - can I use an open source package to generate now a certificate
> >     with features of these drafts?
> >
> >     - is there a Certificate Authority that I can ask now to sign them?
> >
> >     - can I do these two things for free now?
> >
> >     Because in absence of these conditions, I am highly tempted to use
> >     openvpn and its associated free tools to generate my own CA and my
> >     own certificates to put in the cars I deal with.
> >
> >     I think in practice several people do just that.
> >
> >     I think it is a situation that needs to be prevented, because it
> >     means the drafts are not used.
> >
> >     Alex
> >
> >     _______________________________________________
> >     its mailing list
> >     its@ietf.org <mailto:its@ietf.org>
> >     https://www.ietf.org/mailman/listinfo/its
> >
> >
> >
> > --
> >
> > ---
> >
> > I may have sent this email out of office hours. I never expect a
> > response outside yours.
>


-- 

---

I may have sent this email out of office hours. I never expect a response
outside yours.