IETF Logo Mail Archive

Re: [TLS] WG adoption + early code point assignment: draft-mavrogiannopoulos-chacha-tls

Martin Thomson <martin.thomson@gmail.com> Wed, 20 May 2015 18:23 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EEE11A8A60 for <tls@ietfa.amsl.com>; Wed, 20 May 2015 11:23:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 wL5WKRQXCjOh for <tls@ietfa.amsl.com>; Wed, 20 May 2015 11:23:28 -0700 (PDT)
Received: from mail-yk0-x232.google.com (mail-yk0-x232.google.com [IPv6:2607:f8b0:4002:c07::232]) (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 2E5311A8A55 for <tls@ietf.org>; Wed, 20 May 2015 11:23:28 -0700 (PDT)
Received: by ykeo186 with SMTP id o186so18696502yke.0 for <tls@ietf.org>; Wed, 20 May 2015 11:23:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=lEHR0fFRse1YTDPHE+3YEFy+2kjTrXUMmFQwMvIYBSA=; b=jIdHFOTVbvsXUhw2TjhfFckqJgpcL4G+QJfvd55bXOWUI0lKU+EyVLxqkm5AERXog+ rZEHFvERARCOyaWl79ufd2ok2MoMBgO6bS5ew6+4WIGozMO/WrvSMkYjIJr2kx4iREBM dK6Z6d6uU9wZbldD+iHJoEnf5CBWNElK1Xj0vnkjDmQXi/EtLmj6Jg5zLhxFlY2S4Nc7 cY0GF05d7GaFg6ZWY+MHh9pD0g0rGZQb5/GQrPRXSybPnnMUbKywSYzmDzsbJx+Ly/Zk HjKE2bKKqYT/Fak3jji6hGVpkk+qLShJFgejnZoKqssMznTrSzg3vBBjEvSsZp0PkXwU /Png==
MIME-Version: 1.0
X-Received: by 10.170.61.141 with SMTP id d135mr36172173ykd.26.1432146207623; Wed, 20 May 2015 11:23:27 -0700 (PDT)
Received: by 10.13.247.71 with HTTP; Wed, 20 May 2015 11:23:27 -0700 (PDT)
In-Reply-To: <0A275078-EE74-483F-8065-B9CD7808E5EB@gmail.com>
References: <FD8B7C3F-C3DD-4367-B84D-26B9907F1B9D@ieca.com> <CABcZeBOqnyXS5kp=ZiN2PpKYt_dOg1+L4_S__h-+YP=n6sHk3A@mail.gmail.com> <1269593170.1072986.1432104184832.JavaMail.zimbra@redhat.com> <CABcZeBNQQKgBzzoia0TWzbG8PycoOLT+ejOM7dwNNfgNoCqRtA@mail.gmail.com> <86AF5010-12A3-410A-AE23-9A0643D536EE@gmail.com> <CAMfhd9XvrhX3MgjMOQ+P=c8oydWT6F6AwUfFerbSWLgra2tbdw@mail.gmail.com> <CABcZeBMB9ieZ2n4maCkJXAWKEto81XDEfFDnjY=X1G3fKNwjcw@mail.gmail.com> <86328675.1427913.1432137385798.JavaMail.zimbra@redhat.com> <CABcZeBO1y+P3pPCVtgSvyK8OFQBpBju0Egm9NfgO9p7+7VmbGw@mail.gmail.com> <0A275078-EE74-483F-8065-B9CD7808E5EB@gmail.com>
Date: Wed, 20 May 2015 11:23:27 -0700
Message-ID: <CABkgnnWRi8APFnt8taq=PDnxB=qjMp7=uUKfX=LzqBm2kJSm1Q@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Yoav Nir <ynir.ietf@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/f5ZfZQVBwC8iKfdG2A_DH6zk6lI>
Cc: Adam Langley <agl@imperialviolet.org>, IETF TLS Working Group <tls@ietf.org>
Subject: Re: [TLS] WG adoption + early code point assignment: draft-mavrogiannopoulos-chacha-tls
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 May 2015 18:23:29 -0000

On 20 May 2015 at 11:01, Yoav Nir <ynir.ietf@gmail.com> wrote:
> That’s your call, but as Stephen said there is always the potential for
> non-interoperable changes to happen during the WG process. I don’t see this
> as blocking, but I was told the same at IPsecME when I made the same
> request.

We're talking about a code point allocation.  That usually requires a
commitment to semantics first.

v2.23.0 | Report a Bug | By Email