Re: [ipwave] permission

Jérôme Härri <Jerome.Haerri@eurecom.fr> Tue, 27 April 2021 07:00 UTC

Return-Path: <Jerome.Haerri@eurecom.fr>
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 B65C73A0EBA for <its@ietfa.amsl.com>; Tue, 27 Apr 2021 00:00:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 NMEM8LOoLOP5 for <its@ietfa.amsl.com>; Tue, 27 Apr 2021 00:00:37 -0700 (PDT)
Received: from smtp2.eurecom.fr (smtp2.eurecom.fr [193.55.113.211]) by ietfa.amsl.com (Postfix) with ESMTP id 4DEA33A135E for <its@ietf.org>; Tue, 27 Apr 2021 00:00:36 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.82,254,1613430000"; d="scan'208";a="1683581"
Received: from monza.eurecom.fr ([192.168.106.15]) by drago2i.eurecom.fr with ESMTP; 27 Apr 2021 09:00:33 +0200
Received: from portege33 (portege33.eurecom.fr [172.17.31.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by monza.eurecom.fr (Postfix) with ESMTPSA id 322F9655; Tue, 27 Apr 2021 09:00:33 +0200 (CEST)
From: =?UTF-8?B?SsOpcsO0bWUgSMOkcnJp?= <Jerome.Haerri@eurecom.fr>
To: "'Alexandre Petrescu'" <alexandre.petrescu@gmail.com>, "'William Whyte'" <wwhyte@qti.qualcomm.com>, "'Mounira MSAHLI'" <msahli1717@gmail.com>
Cc: <its@ietf.org>
References: <acc0f475-7f7b-bfbe-1099-913f0cef4de6@gmail.com> <01d601d731e3$140e2ed0$3c2a8c70$@eurecom.fr> <0600020f-b6ca-4d6d-2499-817586bc3548@gmail.com> <CAMEeBw9eaPBRT26BqqmXdEpqFzSTGt8w46wmexfg7ax4aRP-pQ@mail.gmail.com> <CAA2OGZCntE+FUtzKwxrsH7i_q70jjZuPoUjRG7cYmEVRHFJU8g@mail.gmail.com> <19dce5f5-8dca-55c2-4d46-bb83046562ab@gmail.com> <1ec103fe-7a50-cb2c-0763-30cc6362bf13@gmail.com> <e822da34-84df-bce0-6497-479ed1016898@gmail.com> <CAA2OGZA5-xr-mo7u7rtJvApu3XwFJLfmZsTz2Q=+RAxG=Rac6Q@mail.gmail.com> <f75e41a0-a86a-fa44-1183-28fcb0f626d9@gmail.com> <CAA2OGZDyBi1y48Smm1eA0Ogn78L_ck0-mTin+hMyzL9RUN1tJw@mail.gmail.com> <fc4cf84a-45ec-bc69-140a-998970a95b1c@gmail.com> <CAA2OGZA7i7dDU+6dv8RobT5TKFTkqxJ-PvbVYcCa=N9Xf2n4rg@mail.gmail.com> <MN2PR02MB6591ADE2799245EEFF7F7D1DF2429@MN2PR02MB6591.namprd02.prod.outlook.com> <c50aa38c-ab00-6ded-71e0-fd45d83c82dd@gmail.com>
In-Reply-To: <c50aa38c-ab00-6ded-71e0-fd45d83c82dd@gmail.com>
Date: Tue, 27 Apr 2021 09:00:33 +0200
Organization: EURECOM
Message-ID: <006401d73b33$044a2d60$0cde8820$@eurecom.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Content-Language: en
Thread-Index: AQGNE4eOrl1DVgZsmuuV5v0KN1fNOAJW1Y3IAudJi94CHB5pXwIot11sAYO0IMoCGrZz7QJ5DJU0Ap+9g7ICysu2/ALhiy8/AkOLmU4CO4rRIgEvXwBrAgiVwUuqX0/1AA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/ONZgi3Vi_qmMEYN6J-LaA5tEe6Q>
Subject: Re: [ipwave] permission
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: Tue, 27 Apr 2021 07:00:42 -0000

Dear Alex, Dear All,

I am not sure to follow here. ETSI provides on its website the ASN1 code (a zip file) for the ETSI security framework version 1.3 (and you can parse it into C or C++ code). We are using it on a network simulator VANETZA. Neither the side nor the content of the .zip file indicate we cannot use it. I am not making any commercial product though...

Of course, there is a difference between accessing the document or the ASN1 code. The ETSI Security standard v1.3 provides a full description of the 'main' message blocks and functional requirements for all DAY 1 ETSI services. Indeed, the ETSI document points to some 1609.2 structures in 1609.2 documents, which I could not access, but I could get the structures details from the ASN1 code. From my understanding and my experience in implementing the 1.3.1 code, I do not need 1609.2 document to make it work, all functional requirements are in the ETSI document.

One point:  I only implemented the security framework stack, not the algorithms to build public/private keys or certificate chains. Maybe for that, there is an issue...not sure,

BR,

Jérôme

-----Original Message-----
From: its <its-bounces@ietf.org> On Behalf Of Alexandre Petrescu
Sent: Monday, 26 April 2021 19:18
To: William Whyte <wwhyte@qti.qualcomm.com>om>; Mounira MSAHLI <msahli1717@gmail.com>
Cc: its@ietf.org
Subject: Re: [ipwave] permission



Le 26/04/2021 à 16:29, William Whyte a écrit :
>>> - the specs of CA must be implementable independently of other 
>>> paying
> sources such as (some) from IEEE or ISO.  For example, the ETSI ITS 
> spec that IMPORTS 1609.2 does not qualify because in the end it is 
> paying.  But the X.509 in RFC 5280 does not rely on other paying 
> documents in order to implement (I think?).
> 
>>> William could answer you this question better than me because it was
> already asked by ETSI.
> 
> Yes, 1609.2 needs to be purchased from IEEE. ETSI has reproduced the
>  ASN.1 (with permission from IEEE)

Is that permission from IEEE only for ETSI or is it for me too?

Because the text says: "This clause provides the relevant ASN.1 modules from IEEE Std 1609.2 [1] (and its amendments), reprinted with permission from IEEE, Copyright © 2016."

To me, that means a permission to print, but not necessarily to put in code.

Alex

  but there are some subtleties of
> implementation and how the crypto operations are carried out that 
> aren’t captured in the ASN.1 alone.
> 
> I’d note that Alex’s preference for standards to be freely available 
> if they are to be referenced by IETF is a reasonable point of view, 
> but it’s not IETF policy; IETF policy allows non-free standards to be  
> referenced.
> 
> Cheers,
> 
> William
> 
> *From:* its <its-bounces@ietf.org> *On Behalf Of * Mounira MSAHLI
> *Sent:* Monday, April 26, 2021 9:54 AM *To:* Alexandre Petrescu 
> <alexandre.petrescu@gmail.com> *Cc:* its@ietf.org *Subject:* [EXT]
> Re: [ipwave] wish list for CAs for vehicular networks
> 
> Can you comment on this wish list?
> 
> Wish list for CAs for vehicular networks
> 
>>> - the CA must be reachable on IPv6, and their website too.
> 
> Could you please mention why not IPv4 ?
> 
> - the specs of CAs for vehicular networks must be available on IPv6 
> (e.g. on an IPv6 website, FTP directory, or GIT shared space).
> 
> You mean certificate policy. I have the same question. You are 
> specifying the IP protocol for the PKI website. I agree that document  
> must be published and available to PKI users but why IPV6 ?
> 
> - the specs of CA must be implementable independently of other paying 
> sources such as (some) from IEEE or ISO.  For example, the ETSI ITS 
> spec that IMPORTS 1609.2 does not qualify because in the end it is 
> paying.  But the X.509 in RFC 5280 does not rely on other paying 
> documents in order to implement (I think?).
> 
> William could answer you this question better than me because it was  
> already asked by ETSI.
> 
> - the CA must offer OCSP reachability on IPv6.
> 
> I find that all recommandations are related to the use of IPv6 not 
> really the
> 
> security or privacy in C-ITS. By analogy with what you are suggesting, 
> I think  that you would prefer to use IPv6 for the upload of log and 
> download of updates and all V2I communications not only V2PKI 
> connexion.
> 
> Mounira
> 

_______________________________________________
its mailing list
its@ietf.org
https://www.ietf.org/mailman/listinfo/its