From: Peter Gutmann <pgut001@cs.auckland.ac.nz>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, "noloader@gmail.com"
 <noloader@gmail.com>, Tony Arcieri <bascule@gmail.com>
Thread-Topic: [TLS] TLS Provfiles (Was: Call for consensus to remove
 anonymous DH)
Thread-Index: AQHQ8FFq13KcVZ89fEGkcyYs2GLTPZ4+0CRR//8+EACAAPO8Y///cIqAgADNSLw=
Date: Wed, 16 Sep 2015 14:59:32 +0000
Message-ID: <9A043F3CF02CD34C8E74AC1594475C73F4B08823@uxcn10-tdc05.UoA.auckland.ac.nz>
References: <CAH8yC8=eHzQPL6cROVK4Pm0V2FSYTL7C7csLG7p49W5LEmfo=Q@mail.gmail.com>
 <9A043F3CF02CD34C8E74AC1594475C73F4B070E6@uxcn10-tdc05.UoA.auckland.ac.nz>
 <55F92C1A.9060703@cs.tcd.ie>
 <9A043F3CF02CD34C8E74AC1594475C73F4B0723C@uxcn10-tdc05.UoA.auckland.ac.nz>,
 <55F98037.6050103@cs.tcd.ie>
In-Reply-To: <55F98037.6050103@cs.tcd.ie>
Accept-Language: en-NZ, en-GB, en-US
Content-Language: en-NZ
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/u6LUNa-3-MnlnVRKcDBkzK5EE_k>
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] TLS Provfiles (Was: Call for consensus to remove
 anonymous DH)
Precedence: list

Stephen Farrell <stephen.farrell@cs.tcd.ie> writes:=0A=
=0A=
>I'm not sure how to process that comment. You ask for X, I ask is Y=3D=3DX=
 and=0A=
>your answer is that Y doesn't exist? Seems odd. ;-)=0A=
=0A=
There's a difference between "X/Y exists" (but no-one knows about it) and "=
X/Y=0A=
exists and is actively used".  As I said, I've never seen the BCP quoted,=
=0A=
cited, or referenced in any third-party standard that deals with TLS (and b=
y=0A=
third-party standard I don't mean other RFCs but industry standards like IE=
C=0A=
61850 or IEC 62351).=0A=
=0A=
>Feel free to collect a bunch of your own emails (hand-wringing or not:-) a=
nd=0A=
>shoot those out as an I-D.=0A=
=0A=
That makes it worse, not better, because it's just creating one more I-D or=
=0A=
RFC or BCP or whatever to languish in obscurity.  The profiles need to be p=
art=0A=
of the TLS spec where they'll be noticed and used by other standards=0A=
referencing it.=0A=
=0A=
Peter.=0A=