IETF Logo Mail Archive

Re: [Iotops] BRSKI and IDevID (non-!)issues with draft-ietf-uta-use-san

Eliot Lear <lear@cisco.com> Fri, 14 May 2021 14:08 UTC

Return-Path: <lear@cisco.com>
X-Original-To: iotops@ietfa.amsl.com
Delivered-To: iotops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E672C3A3418; Fri, 14 May 2021 07:08:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.599
X-Spam-Level:
X-Spam-Status: No, score=-9.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_NONE=0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 1kzoD-LwOXCu; Fri, 14 May 2021 07:08:18 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 771823A3416; Fri, 14 May 2021 07:08:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1583; q=dns/txt; s=iport; t=1621001297; x=1622210897; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=jXcaF4EmQEu69/DHXNzbs0Kg0TIZY7du8rcBpCfYWVk=; b=j3pZB9CuwDK0w0dlc0sjcmcwcaZXTLZreUkGNG+hlHSAfzyUHPRLoY5A A8KfWLjFF5xaelOareW29w7+6wyXo3Q10XLe6bhtZG74eeUy/wGQx6rSc DlnHyLLzZxk9QY/LpSVJEK07b005EQWLWHXS36xStso0yzwcv92tfU2KB w=;
X-Files: signature.asc : 488
X-IPAS-Result: A0AVAAB/gp5g/xbLJq1aGgEBAQEBAQEBAQEDAQEBARIBAQEBAgIBAQEBggYCAQEBAQsBg3cBJxIxhEeJBIkCnQwEBwEBAQoDAQFBBAEBhE8CgXUmNwYOAgQBAQEBAwIDAQEBAQUBAQUBAQECAQYEcROFXYZEAQEBAwEjVgULCwwMKgICPRoGE4JxAYJmIad1eoEygQGEY4UgEIE6AYFSiBmDd0OCDYEVJxyCXz6HWjaCLQSBVYFZdWM/n0GdJIMgg0qBSZgxBSODR6FytSyECgIEBgUCFoFqJIFZMxoIGxVlAYI+PhIZDpxuPwMvOAIGAQkBAQMJikstghgBAQ
IronPort-HdrOrdr: A9a23:t8Hi1aFFSlxva1dtpLqE7ceALOsnbusQ8zAXPo5KOH9om62j+/ xG88576faZslwssTQb+exoRpPsfZqsz/FICOAqVN/IYOClghrMEGgI1+XfKlPbak/DH5ZmpM Ndm2wUMqyXMbC85vyKhzWFLw==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.82,300,1613433600"; d="asc'?scan'208";a="33579439"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 14 May 2021 14:08:13 +0000
Received: from smtpclient.apple ([10.61.144.21]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id 14EE8C4V025837 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 14 May 2021 14:08:12 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <0346569E-B1CB-4CE5-AD26-D2E21798A1D5@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_81E547FA-E704-457C-BE9C-19F61144BC80"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.80.0.2.43\))
Date: Fri, 14 May 2021 16:08:11 +0200
In-Reply-To: <6F770550-8636-4353-BDBD-2C2376447168@akamai.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "uta@ietf.org" <uta@ietf.org>, "iotops@ietf.org" <iotops@ietf.org>, "anima@ietf.org" <anima@ietf.org>
To: "Salz, Rich" <rsalz@akamai.com>
References: <F538FFD7-D172-4AEE-82DD-CF6F93936C3B@akamai.com> <D341C730-EBA1-4BF5-B200-0BE1A4B8A1D0@cisco.com> <413CBCFE-1FDF-458E-9F0E-E3D58F86E5D9@bluepopcorn.net> <A5B94C6E-419D-454E-92E8-FEEB5F8EDE17@cisco.com> <8A41ED29-2448-4633-AC45-33DE98A6BC81@akamai.com> <7B51BB81-1C9D-4B2F-AF83-1E528E620AE7@cisco.com> <CAFewVt4Pm6-T3XC65uEceuzpXjNubEYLWY9h1cmHdNBPcpOVXQ@mail.gmail.com> <42739D1C-004F-4DAD-8023-8E9731B46E05@cisco.com> <15280.1620951766@localhost> <D426B94E-6C3B-44C3-A580-310D2953D0CD@cisco.com> <6F770550-8636-4353-BDBD-2C2376447168@akamai.com>
X-Mailer: Apple Mail (2.3654.80.0.2.43)
X-Outbound-SMTP-Client: 10.61.144.21, [10.61.144.21]
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/iotops/EgcyOjkhg3T07s4146gvvZJQkG8>
Subject: Re: [Iotops] BRSKI and IDevID (non-!)issues with draft-ietf-uta-use-san
X-BeenThere: iotops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IOT Operations <iotops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iotops>, <mailto:iotops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iotops/>
List-Post: <mailto:iotops@ietf.org>
List-Help: <mailto:iotops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iotops>, <mailto:iotops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 May 2021 14:08:23 -0000

Rich,

As I wrote, I think we’re past it, because this is about domain/IP address validation and not client cert validation.  Correct?

Eliot

> On 14 May 2021, at 16:02, Salz, Rich <rsalz@akamai.com> wrote:
> 
>>   There are a VAST number of devices that run off of iDevIDs: they never transition off of them.  I’m not a fan, but that’s what they do.
> 
> Okay, so this draft doesn't apply to them.  There doesn't seem to be a problem with, say, not using TLS 1.3 in cases, or not using ECDH in some cases, so why is this draft different from those situation?
>

v2.23.0 | Report a Bug | By Email