Return-Path: X-Original-To: tls@ietfa.amsl.com Delivered-To: tls@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A6761296FB for ; Fri, 10 Mar 2017 11:29:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 DX5YiBTavloB for ; Fri, 10 Mar 2017 11:29:33 -0800 (PST) Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E93161296F5 for ; Fri, 10 Mar 2017 11:29:32 -0800 (PST) Received: by mail-yw0-x236.google.com with SMTP id v198so29934936ywc.2 for ; Fri, 10 Mar 2017 11:29:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NWEpb3ljc/q/3ACxYSgPwRAaehTHO2TfPtnMdZsuRs4=; b=deypajJl4w17eV91tZkFu6rozmFyUdJFjudoaY8EhxNnyScXX74GEjHXGi6YRnjP95 EK8HbZWOxTAydEkzAIt6vwymxxXJR7cM4vw/RE64FfD0BAPlxApx39AvFwmZiz1Y+4Zt s5dokvHvW0cgHO1hLeYGvu19FAtd1OxHZItRMxStxdV37nLPckwaZfIqN7d5RfpYNGl+ h920UhJvAfHf4Yit31ad1GTg/2al0CbBwxDfbSBW3M8k269e+8SRFHkixy9mdk8/Erag 2qWyjlB3uCwlba+hee9iqnQHfKA2GnUbDiofaQSU2JdyT9w11r1RFExTClIpz6NLxgDY AJTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=NWEpb3ljc/q/3ACxYSgPwRAaehTHO2TfPtnMdZsuRs4=; b=HX4ivE7rnMn/YpcWmsH00xlrzSREPLcChp/Z9VU0KHTz/2XSA6btLOToXIhp5oh634 IVoZF/ga+4hbL0YoMWW6WZEqzm9Tf5m0+ZxaunPCYyRe9MOOqlKGdvJ5DsPFNTI+NQWG m6U8J/TQ6n/MuY1t82xicDIulnQnQhCay9knZP/NZp9WtQiiv7PHWVWuQ6o5wAU08UNY N/tUDWK2iHq5lMgkzZE4PNVYQXmugApi3pkxbtupK2tFzId0gUCbh4QiQyxuQz3zJolZ f0fMNxepOx9CYHB50xSr/LTvvGJQM5cbzoEuPnHB3E4YnZjbo7vgTJfUKoZj6HS6utVk g5zg== X-Gm-Message-State: AMke39nbtmQmdD4pLpIqTDtv0qD6PnUTEOwY3hIvHrSqNzvbHNISWR8cgiELAJW+VNe2tN7yKKymgNwWIU5ehQ== X-Received: by 10.37.97.210 with SMTP id v201mr8785809ybb.65.1489174171982; Fri, 10 Mar 2017 11:29:31 -0800 (PST) MIME-Version: 1.0 Received: by 10.129.154.210 with HTTP; Fri, 10 Mar 2017 11:28:51 -0800 (PST) In-Reply-To: References: <20170310124013.GA1197@LK-Perkele-V2.elisa-laajakaista.fi> <20170310163738.GA1636@LK-Perkele-V2.elisa-laajakaista.fi> From: Eric Rescorla Date: Fri, 10 Mar 2017 11:28:51 -0800 Message-ID: To: Andrei Popov Content-Type: multipart/alternative; boundary=001a1142ed0488258a054a6561a9 Archived-At: Cc: "tls@ietf.org" Subject: Re: [TLS] Updating for non-X.509 certificate types X-BeenThere: tls@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Mar 2017 19:29:34 -0000 --001a1142ed0488258a054a6561a9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thanks On Fri, Mar 10, 2017 at 11:26 AM, Andrei Popov wrote: > It will be inelegant to have two code points for what is conceptually the > same thing, but I think this is the best option, under the circumstances. > > > > Cheers, > > > > Andrei > > > > *From:* Eric Rescorla [mailto:ekr@rtfm.com] > *Sent:* Friday, March 10, 2017 10:53 AM > *To:* Andrei Popov > *Cc:* Ilari Liusvaara ; tls@ietf.org > *Subject:* Re: [TLS] Updating for non-X.509 certificate types > > > > > > > > On Fri, Mar 10, 2017 at 10:04 AM, Andrei Popov > wrote: > > =C3=98 Does anyone use this? > > =C3=98 I don't think anyone uses it. > > > > Au contraire: Windows TLS stack supports user_mapping and this mechanism > appears to be somewhat in use. However, I agree that this falls into the > category of extensions that need to be either deprecated or redefined for > TLS 1.3. > > > > Are you OK with deprecated followed by redefined with a new code point? > > > > -Ekr > > > > > > Cheers, > > > > Andrei > > > --001a1142ed0488258a054a6561a9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks

On Fri, Mar 10, 2017 at 11:26 AM, Andrei Popov <Andre= i.Popov@microsoft.com> wrote:

It will be inelegant to have two code points for wh= at is conceptually the same thing, but I think this is the best option, und= er the circumstances.

=C2=A0

Cheers,

=C2=A0

Andrei

=C2=A0

From: Eric Rescorla [mailto:ekr@rtfm.com]
Sent: Friday, March 10, 2017 10:53 AM
To: Andrei Popov <Andrei.Popov@microsoft.com>
Cc: Ilari Liusvaara <ilariliusvaara@welho.com>; tls@ietf.org
Subject: Re: [TLS] Updating for non-X.509 certificate types

=C2=A0

=C2=A0

=C2=A0

On Fri, Mar 10, 2017 at 10:04 AM, Andrei Popov <<= a href=3D"mailto:Andrei.Popov@microsoft.com" target=3D"_blank">Andrei.Popov= @microsoft.com> wrote:

=C3=98=C2=A0 Does anyone use this?

=C3=98=C2=A0 I don't think anyone uses it.

=C2=A0

Au contraire: Windows TLS stack supports user_mappi= ng and this mechanism appears to be somewhat in use. However, I agree that this falls into the category of extensions that need to be ei= ther deprecated or redefined for TLS 1.3.

=C2=A0

Are you OK with deprecated followed by redefined wit= h a new code point?

=C2=A0

-Ekr

=C2=A0

=C2=A0

Cheers,

=C2=A0

Andrei

=C2=A0


--001a1142ed0488258a054a6561a9--