IETF Logo Mail Archive

Re: [quicwg/base-drafts] Are transport parameters mandatory? (#2528)

Martin Thomson <notifications@github.com> Tue, 19 March 2019 23:16 UTC

Return-Path: <noreply@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 1ED90124B91 for <quic-issues@ietfa.amsl.com>; Tue, 19 Mar 2019 16:16:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.383
X-Spam-Level:
X-Spam-Status: No, score=-6.383 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 TqF_19zOxQ_U for <quic-issues@ietfa.amsl.com>; Tue, 19 Mar 2019 16:16:14 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 531E712008F for <quic-issues@ietf.org>; Tue, 19 Mar 2019 16:16:14 -0700 (PDT)
Date: Tue, 19 Mar 2019 16:16:13 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1553037373; bh=OlB92UAdhVd0aa9oPbyTM/Hn93JRWJVsYZAi4h7G/04=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=L7TqyfswNUveZhcqrmTq56Ja9BkOVsa011rlRmQdUc25+zsvepLePWhMZGaJhayAW qieq4NQ3lh3QRtO32N05YgjbPhNHpdI6+cZ2kQ294uvNEyI9GZNQRlIXbfr4VLfe65 LmrB57ADdVh81MJdNQArhXzhC1utrqSmNJ5i7dtk=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abf19cdf060eaaff53c6c59e43834fbff59997d7a692cf0000000118a93a3d92a169ce192ea180@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2528/474620917@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2528@github.com>
References: <quicwg/base-drafts/issues/2528@github.com>
Subject: Re: [quicwg/base-drafts] Are transport parameters mandatory? (#2528)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c91783d697e3_16173fd4508d45b42783c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/UoEtMrtCwKP3zFh5nY44mMkmKjo>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 19 Mar 2019 23:16:16 -0000

Our defense for cross-protocol attacks is ALPN.  Then key separation, and probably other things.  While layers of defense is generally a good idea, that isn't a necessary layer.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/2528#issuecomment-474620917

v2.15.0 | Report a Bug | By Email