Re: [Uta] WGLC for draft-ietf-uta-rfc6125bis-06

Valery Smyslov <valery@smyslov.net> Wed, 06 July 2022 14:14 UTC

Return-Path: <valery@smyslov.net>
X-Original-To: uta@ietfa.amsl.com
Delivered-To: uta@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF093C15A731; Wed, 6 Jul 2022 07:14:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.797
X-Spam-Level:
X-Spam-Status: No, score=-5.797 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_VALIDITY_RPBL=1.31, 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_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=smyslov.net
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 Sc4pExS9n0Do; Wed, 6 Jul 2022 07:14:50 -0700 (PDT)
Received: from direct.host-care.com (direct.host-care.com [198.136.54.115]) (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 3FD4DC157B4A; Wed, 6 Jul 2022 07:14:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smyslov.net ; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID :Date:Subject:In-Reply-To:References:Cc:To:From:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=eUW0KzqpW/7BlTVTJ+Qlt7mFW9qvkH24AxYCGavrBeg=; b=cM1oOLXdIkhM16pOLczjVO3Vbp r+/SXUUxt+CQYGugaaRj2XjWiQZF9x9fkzb92CMtvjyzO4ILtns0yU92cSDjKGlAlKX+GEQXyBu8D 1ST1ettjIITWM6ohCZzLfbzDuwk5UOOCe2lIJV5sS2fk2I+8w4xxODOKYwStBWOb4IzXp3D10M99P hIR22rYX/Kl8akoBC9pShl80SSHqaEWAApy/mY3554Exad5/whfaBTIq1xHaVvk0dhP8w1Pk6Dg4Z P+188dRV7qMRWEBxyXLmNHsWmkQRnKGy++aZhriKSik42r5WHy/f9itC5kar4IM53aPbgbbl0ahRs 6efUo9hQ==;
Received: from [93.188.44.204] (port=51114 helo=buildpc) by direct.host-care.com with esmtpsa (TLS1.2) tls TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <valery@smyslov.net>) id 1o95ni-0007nL-VK; Wed, 06 Jul 2022 10:14:47 -0400
From: Valery Smyslov <valery@smyslov.net>
To: 'Peter Saint-Andre' <stpeter@stpeter.im>, 'Martin Thomson' <mt@lowentropy.net>, uta@ietf.org
Cc: uta-chairs@ietf.org
References: <002e01d87e9c$78a002e0$69e008a0$@smyslov.net> <152a5c9d-3142-419e-81dd-aa19bc2c8a02@beta.fastmail.com> <A8121C94-7881-4BA1-8A3D-C70291020FA6@akamai.com> <53fb3bb0-6414-3e1b-5ef5-2204522528f8@stpeter.im> <ED51AE33-23D2-4D40-91CD-155877E0ABAC@akamai.com> <03e601d88d54$65876150$309623f0$@gmail.com> <617eb543-e898-4716-8bda-77000e6d55b7@beta.fastmail.com> <05ce01d89103$6718fd50$354af7f0$@smyslov.net> <6afa428d-271d-43be-3652-9c9729ce110c@stpeter.im>
In-Reply-To: <6afa428d-271d-43be-3652-9c9729ce110c@stpeter.im>
Date: Wed, 06 Jul 2022 17:14:46 +0300
Message-ID: <064701d89142$c0751fc0$415f5f40$@smyslov.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQE4vpxHxcvf4kNYSTziui8SK76GFwEDFSMRAsPAPQUClCqpnQKwzk49AZHRBWICC6hFQQH4p8TFAm2n4EauKIlNoA==
Content-Language: ru
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - direct.host-care.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - smyslov.net
X-Get-Message-Sender-Via: direct.host-care.com: authenticated_id: valery@smyslov.net
X-Authenticated-Sender: direct.host-care.com: valery@smyslov.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/uta/K2CSDya2f_SU5k8oiedthGS0-Q4>
Subject: Re: [Uta] WGLC for draft-ietf-uta-rfc6125bis-06
X-BeenThere: uta@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: UTA working group mailing list <uta.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uta>, <mailto:uta-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uta/>
List-Post: <mailto:uta@ietf.org>
List-Help: <mailto:uta-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uta>, <mailto:uta-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2022 14:14:54 -0000

Hi Peter,

> On 7/6/22 12:41 AM, Valery Smyslov wrote:
> > Hi Martin,
> >
> >>> The chairs think that the rough consensus is to limit the scope of the
> >>> draft to domain names
> >>> (with the pointer to the HTTP RFC as advise for protocols that support
> >>> IP addresses).
> >>
> >> Is this the consensus of the chairs, or was there some discussion that I missed?
> >
> > We discussed this with Leif going back to the history of RFC 6125.
> > The text explicitly limiting the scope of the document to domain names
> > first appeared in draft-saintandre-tls-server-id-check-05 back in 2010
> > and was kept in RFC 6125. At the time the 6125bis draft was adopted
> > there was no intention to widen the scope of RFC 6125.
> >
> >> I agree that there is no consensus to include changes, but I don't see any input other than from Rich
> (and
> >> I guess now yourself).
> >
> > Peter also participated in the discussion and from our point of view he supported Rich's position.
> > We also waited a bit for others to chime in.
> 
> I'm actually not opposed to adding support for IP addresses - my only
> concern was performing major surgery on the document, so I wanted to
> think about what changes we would need to make. At the time that Jeff
> and I worked on RFC 6125, we were not aware of widespread use of IP
> addresses in PKIX certificates. If the deployment situation has changed
> (as indicated by RFC 9110), then I am open to adding IP-IDs to 6125bis.

OK, sorry for misinterpreting your response.

> > Just to reiterate the chairs' position. We think that describing the handling of non-domain based names
> > (like IP-ID) is a good idea, but at the same time we think that it would require quite a lot
> > of changes to the current document,
> 
> Martin sketched that out here:
> 
> https://github.com/richsalz/draft-ietf-uta-rfc6125bis/pull/54/files
> 
> I don't think it's *too* bad.
> 
> > that would slow down its progress.
> 
> What's the hurry? It's been 10+ years since we published RFC 6125, I
> don't think a few more weeks will make a big difference.

Then, we'd like to hear from WG members:
whether the scope of rfc6125bis draft should be broaden
to include non-domain names, like IP addresses
(at the cost of delaying its publication) or this issue
should be addressed in a separate document.

Regards,
Valery.

> Peter