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 9B52612D1D2 for ; Thu, 1 Sep 2016 09:08:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.45 X-Spam-Level: X-Spam-Status: No, score=-7.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 RQ6pQAfm_4hB for ; Thu, 1 Sep 2016 09:07:57 -0700 (PDT) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87B8A12D0FC for ; Thu, 1 Sep 2016 09:07:57 -0700 (PDT) Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 4DD0D4E4E5 for ; Thu, 1 Sep 2016 16:07:57 +0000 (UTC) Received: from pintsize.usersys.redhat.com (dhcp-0-191.brq.redhat.com [10.34.0.191]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u81G7uKF020638 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 1 Sep 2016 12:07:57 -0400 From: Hubert Kario To: "tls@ietf.org" Date: Thu, 01 Sep 2016 18:07:50 +0200 Message-ID: <4152939.QfPvxGhp5y@pintsize.usersys.redhat.com> User-Agent: KMail/5.2.3 (Linux/4.6.7-300.fc24.x86_64; KDE/5.25.0; x86_64; ; ) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4664947.PDm2GODNzS"; micalg="pgp-sha512"; protocol="application/pgp-signature" X-Scanned-By: MIMEDefang 2.68 on 10.5.11.27 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Thu, 01 Sep 2016 16:07:57 +0000 (UTC) Archived-At: Subject: [TLS] TLSv1.2 connection renegotiation to TLSv1.3 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: Thu, 01 Sep 2016 16:08:04 -0000 --nextPart4664947.PDm2GODNzS Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" I didn't notice in the -15 draft anything explicitly prohibiting sending a= =20 TLSv1.3 Client Hello inside established TLSv1.x connection (where x < 3). Is this something that the protocol should allow? If yes, renegotiation_inf= o=20 extension status would probably need to be updated. If not, then I think th= e=20 document should be a bit more explicit about it. =2D-=20 Regards, Hubert Kario Senior Quality Engineer, QE BaseOS Security team Web: www.cz.redhat.com Red Hat Czech s.r.o., Purky=C5=88ova 99/71, 612 45, Brno, Czech Republic --nextPart4664947.PDm2GODNzS Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCgAGBQJXyFJWAAoJEJKo0bgB0vX1X+AP/jHhTJnIhyYV/upOjh/cyXsE 8eLLFdgKrY6StO7TAfQYns8K0NImfwirTZjGz09Um10QxfBuOPw9aJmNIfJRsiTr FmNf6c92tI1lZAZhQ53a+KfaIToMzmLOlgFvoY9TTb0lXrFSwAJbghZQ1f95RiFg pPp3Z9ED2ZlOBB++az0saUcukW8iZP8frZNZL+0bf9jWi5gEclI4vviZxqg6lW0p zFYWMYGJWsMU5nmUP+LnobfIeroRPc0x3EG71TqPAMn8LYm9Ucz4x1eQlKMjXxQx WJXRMze7Tuu7zbSb+382zOv6tryCJ0q7U4gmOXPdfrvnMW/gLWaB30y69e3rohQD 96Dle7aZzyVV06/OCFnqOboEhbcigOwJVGmHFIMVN8heIKPnm19USnLVy1d91UQc o8lNzYkL7+Dw8at9oQZUDZ4ReatmkqWqS4JhtKia97xJX5jMigOin8wXG1XfBRIT eR8rljRTE/xvqTVZ14G04zizqZL84+Sp79jW5a5jEvvHk10hj5gpBke2kW5VxcN4 L1N/7BEKaAaqW/Wt/nXJy03c/T6iGJ7IzcJVUrKo4S4y/5ZKDo2NkE3/gAUG74be bD6izUv9w93rQE8myrFubx40GDK6AKRCzbtlbUsqdaNtD6tWVm8/cYZOYNjt28Un QFTQ8oIF+Sr5yL27JOTo =k2zp -----END PGP SIGNATURE----- --nextPart4664947.PDm2GODNzS--