[quicwg/base-drafts] fce754: Stronger protocol negotiation requirement

Martin Thomson <mt@lowentropy.net> Wed, 02 January 2019 23:35 UTC

Return-Path: <bounce+565321.40f-quic-issues=ietf.org@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D606E129A87 for <quic-issues@ietfa.amsl.com>; Wed, 2 Jan 2019 15:35:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.965
X-Spam-Level:
X-Spam-Status: No, score=-1.965 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 Yh7YKzDKci3E for <quic-issues@ietfa.amsl.com>; Wed, 2 Jan 2019 15:35:37 -0800 (PST)
Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 047C9124BE5 for <quic-issues@ietf.org>; Wed, 2 Jan 2019 15:35:36 -0800 (PST)
DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1546472136; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=cN+aUkbVKHicQz74C/2gGAmLpk4DpRTm8iB1mlqJR+I=; b=rnUypV8m40awwSM+/3ik0/vzCnuLn5ytvIcS4YzT99fBQECnACg474tgHzTmUKj4FHkSevq+ t548+Dl7sJ38SgmLsljSuF7ApEmEBg7NVd4uUKWmKjR8Ln0bKoARvnlmnxeFwix1Hgbqe9qj Kkqm9qaFAi2yho6ImRWP+CdixKk=
X-Mailgun-Sending-Ip: 166.78.71.131
X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ==
Sender: mt=lowentropy.net@github.com
Received: from github.com (Unknown [192.30.253.29]) by mxa.mailgun.org with ESMTP id 5c2d4ac7.7f8680823330-smtp-out-n02; Wed, 02 Jan 2019 23:35:35 -0000 (UTC)
Date: Wed, 02 Jan 2019 15:35:35 -0800
From: Martin Thomson <mt@lowentropy.net>
Reply-To: Martin Thomson <mt@lowentropy.net>
To: quic-issues@ietf.org
Message-ID: <5c2d4ac79abdd_66b72b1ce12ba58814539b@hookshot-fe-b0febf1.cp1-iad.github.net.mail>
Subject: [quicwg/base-drafts] fce754: Stronger protocol negotiation requirement
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="--==_mimepart_5c2d4ac79a632_66b72b1ce12ba5881452e1"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/LkmUzRd1gPJOSJGkH3hZR0svI4M>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2019 23:35:39 -0000

  Branch: refs/heads/proto-nego
  Home:   https://github.com/quicwg/base-drafts
  Commit: fce75453e774abba3b9db9d01bb2257dcb6dcf62
      https://github.com/quicwg/base-drafts/commit/fce75453e774abba3b9db9d01bb2257dcb6dcf62
  Author: Martin Thomson <mt@lowentropy.net>
  Date:   2019-01-03 (Thu, 03 Jan 2019)

  Changed paths:
    M draft-ietf-quic-tls.md

  Log Message:
  -----------
  Stronger protocol negotiation requirement

The transport already requires that the cryptographic handshake provide
authenticated negotiation of application protocol.  However, the TLS doc
was a little weak on whether ALPN should be used.  This clears that up.

Closes #2263.



      **NOTE:** This service has been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/

      Functionality will be removed from GitHub.com on January 31st, 2019.