Re: [Secdispatch] Requesting agenda time for draft-rsalz-use-san

Carrick Bartle <cbartle891@icloud.com> Wed, 03 March 2021 05:29 UTC

Return-Path: <cbartle891@icloud.com>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 733603A1961 for <secdispatch@ietfa.amsl.com>; Tue, 2 Mar 2021 21:29:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level:
X-Spam-Status: No, score=-1.848 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, 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=icloud.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 AHZ-PQifPA-S for <secdispatch@ietfa.amsl.com>; Tue, 2 Mar 2021 21:29:00 -0800 (PST)
Received: from mr85p00im-ztdg06011901.me.com (mr85p00im-ztdg06011901.me.com [17.58.23.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 352DF3A1960 for <secdispatch@ietf.org>; Tue, 2 Mar 2021 21:29:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=1a1hai; t=1614749339; bh=uGWtgdViE1Hdu9skjac0TB0oIBbKFXzM1h+d6XSSlxM=; h=Content-Type:Mime-Version:Subject:From:Date:Message-Id:To; b=j/g+EB3bqs7YlM82LolyJ30JIYYXwh051nqXsdnDnQ0ercVN8rLFpjz/7deljc+l3 P2yvkwCk3tJa7n1eFZ77r+fYRXoH1WBniz6edau7MWbqztxIhq6vkmpF8fUSRtnuA8 58stHKvxp/qUgTQeCD4XiYisV5GKCqhSdUNMUSrOTGiT0aHDUj1tRPID/6AAaBmxBR mFqasGN7ca6BOZSi5Heg9mJq3ygBBCZW+WdXvSMZKjdEtMGZmmfwqA99Qz2a2aFdzn lf/7/SZA0Iwzq5SraUaahP2zsqAuVnqy8dDK5znwOOGuYhJQ/WoL/cdbEiTBtGhB3i 2Lzo3xDGvWDBQ==
Received: from [17.234.26.21] (unknown [17.234.26.21]) by mr85p00im-ztdg06011901.me.com (Postfix) with ESMTPSA id A45DAA6080A; Wed, 3 Mar 2021 05:28:59 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
From: Carrick Bartle <cbartle891@icloud.com>
In-Reply-To: <b8378d08-5ee9-43e1-8260-29803b0ac243@www.fastmail.com>
Date: Tue, 02 Mar 2021 21:28:58 -0800
Cc: secdispatch@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <5FE56DB9-3126-4DFD-9CB1-300C14C8F626@icloud.com>
References: <619EB16E-48E6-459A-A63A-18A805F75D34@akamai.com> <b8378d08-5ee9-43e1-8260-29803b0ac243@www.fastmail.com>
To: Martin Thomson <mt@lowentropy.net>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.761 definitions=2021-03-02_08:2021-03-01, 2021-03-02 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 mlxscore=0 mlxlogscore=730 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-2006250000 definitions=main-2103030041
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/MBJ-XqgLVZkIic-MTJq-gplY2FA>
Subject: Re: [Secdispatch] Requesting agenda time for draft-rsalz-use-san
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Mar 2021 05:29:01 -0000

> SAN is dead 

Wait, what? Do you mean CN?


> On Mar 2, 2021, at 8:56 PM, Martin Thomson <mt@lowentropy.net> wrote:
> 
> What Rich is doing here is good.  SAN is dead and we should ensure that our documentation reflects that.  (Even at the time of 6125 it was a holdover from a previous era.)
> 
> Is now the time that we get to talk about other updates to RFC 6125?  Because there is no IP-ID reference identity in RFC 6125 and HTTP had to define one just to document what happens in practice: https://httpwg.org/http-core/draft-ietf-httpbis-semantics-latest.html#https.ip-id
> 
> I don't want to get in the way of making actual progress here, but knowing the difficulties with getting 6125 done, it might be safer to do this work in a working group.  I have no opinion regarding whether it is a new one or UTA.
> 
> On Fri, Feb 5, 2021, at 02:43, Salz, Rich wrote:
>> I would like to present https://datatracker.ietf.org/doc/draft-rsalz-use-san/
>> 
>> This updates RFC 6125 to remove commonName as a way to identify the 
>> server; just use subjectAltName.  It also limits where the "*" can go 
>> in wildcard certificates. This is a simplification of widely 
>> implemented existing practice. It may even be de facto what's mostly 
>> done. Perhaps the wildcard limitation is controversial and I'd be 
>> willing to remove it.
>> 
>> 6125 was AD-sponsored. I think this could also be, or perhaps it could 
>> go to UTA. I would not present any slides, and think 10-15 minutes 
>> would be enough time.
>> 
>> 
>> _______________________________________________
>> Secdispatch mailing list
>> Secdispatch@ietf.org
>> https://www.ietf.org/mailman/listinfo/secdispatch
>> 
> 
> _______________________________________________
> Secdispatch mailing list
> Secdispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/secdispatch