From nobody Thu Jun 23 19:16:52 2022 Return-Path: X-Original-To: spasm@ietfa.amsl.com Delivered-To: spasm@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B32CEC159489 for ; Thu, 23 Jun 2022 19:16:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.104 X-Spam-Level: X-Spam-Status: No, score=-2.104 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cPOixrygKjKO for ; Thu, 23 Jun 2022 19:16:51 -0700 (PDT) Received: from mail-pj1-x102d.google.com (mail-pj1-x102d.google.com [IPv6:2607:f8b0:4864:20::102d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3800DC14F72E for ; Thu, 23 Jun 2022 19:16:51 -0700 (PDT) Received: by mail-pj1-x102d.google.com with SMTP id cv13so1374793pjb.4 for ; Thu, 23 Jun 2022 19:16:51 -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=6kCMkyf+Xg2gFm0kwTSKQxzgrF//mlnhtjV9Vz6LEGQ=; b=GnmXBeBL8y1lKHFMMMj57DgywpPDVaaXrIj3KtXmbsgLiXIAhxlj+UrY6KInIXv6kS 99ZI+gedjztsX+WyTBc1qTMaHwgfnWS6ZUyjU27HoopI4LpfK9FGCs5sF3byMvVo0TO2 9F+hCnaUYZZF1KJxyAbzFMMBc4ANcgUJj+zjUPJD8l/GUue2HCedBUQmNUcBejP9LpeY ZIgUCgHKjVdrX24XRLTHxuDhNoyw0OSeU54KFq1QhbHPr6XnVAobrvijCNxP8+UnrH2b uIYaq/OICPeWVn00A7ql2nR6FKpUaG4kLO4bQMusR5svElUS/zApmRNoJ4L7Toa2PiGW 1wIA== 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=6kCMkyf+Xg2gFm0kwTSKQxzgrF//mlnhtjV9Vz6LEGQ=; b=gGyGFj/RGh5HGs0cXolCjJus8ZnCtSI7syedXjooBH66Igo0xIBm6UfiW8RkRdPcUm 1eup/vNqxMTeqPULHQt3o1H05TDARZVjhb/2lxAhGqIV0jWnPN+EUCZERq90LcUnAo7+ hbOWjD4qD3N9Wwzv34OyluMego7xpeOgTv/hDHzoN/FFhFSkmxHfsZ5sIOODEU9GVy4j zcjxGizGeuEjUjz9gBk4afa9I/Lc4wXKrhlQU7KhFQunsfTHObmvud0FChE/WTJSm8rE EPWNfSwmE57DC33/GWuHeOj67NQ+0HpZn4m6p75SYJCSiqgCuQtEjhJesP8aA3kL7K41 wIng== X-Gm-Message-State: AJIora83kQq3Wq4FdUawjJ3vNowDbThRDa+O03vhNtref+7L9JCSnbVf pHtLCSVgdlWAJHlCQack2egj5UOJ10oD9gZA6QPYrrThSco= X-Google-Smtp-Source: AGRyM1sp2NIoYlAJp2yWuky29uppFRgGRkIFWwq7CyR0IPI9BdKdGHGzy8EW8pOpBrnjBq+8Xn9lJo0RHIKk8vkoY1g= X-Received: by 2002:a17:902:8f97:b0:169:5e8:d75b with SMTP id z23-20020a1709028f9700b0016905e8d75bmr40293632plo.28.1656037010428; Thu, 23 Jun 2022 19:16:50 -0700 (PDT) MIME-Version: 1.0 References: <77B15D02-EBA9-405D-88ED-411AD7BB82E4@vigilsec.com> <6148FBA0-7A1D-432B-823F-3694B305DF7C@akamai.com> In-Reply-To: <6148FBA0-7A1D-432B-823F-3694B305DF7C@akamai.com> From: Daniel Migault Date: Thu, 23 Jun 2022 22:16:39 -0400 Message-ID: To: "Salz, Rich" Cc: Russ Housley , LAMPS Content-Type: multipart/alternative; boundary="000000000000bdd77005e2282944" Archived-At: Subject: Re: [lamps] Including 3GPP NF Type in HTTPS certificates X-BeenThere: spasm@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jun 2022 02:16:51 -0000 --000000000000bdd77005e2282944 Content-Type: text/plain; charset="UTF-8" I obviously support adoption and also have a question fo the WG. As the nf type is used for role access base, I am wondering if the issuer of the certificate should proceed to some specific verification. If so, I am also wondering if you have any thoughts on how such verification could be automated, to later use something like ACME for example. Yours, Daniel On Thu, Jun 23, 2022 at 12:52 PM Salz, Rich wrote: > > > - https://datatracker.ietf.org/doc/draft-housley-lamps-3g-nftypes/ > > > > - It is very straightforward. > > > > You left out short :) > > > > I support adoption. > _______________________________________________ > Spasm mailing list > Spasm@ietf.org > https://www.ietf.org/mailman/listinfo/spasm > -- Daniel Migault Ericsson --000000000000bdd77005e2282944 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I obviously support adoption and also have a question= fo the=C2=A0WG.=C2=A0

As the nf type is used for role = access base, I am wondering if the issuer of the certificate should proceed= to some specific verification. If so, I am also wondering if you have any = thoughts on how such verification could be automated, to later use somethin= g=C2=A0like ACME for example.=C2=A0 =C2=A0=C2=A0

Yours,= =C2=A0
Daniel

On Thu, Jun 23, 2022 at 12:52 PM Salz, Rich &= lt;rsalz=3D40akamai.com@dmar= c.ietf.org> wrote:

=C2=A0

=C2=A0

  • It is very straightforward.

=C2=A0

You left out short :)

=C2=A0

I support adoption.

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


--
Daniel Migault
Ericsson
--000000000000bdd77005e2282944--