IETF Logo Mail Archive

Re: [quicwg/base-drafts] Add retry integrity tag (#3120)

ekr <notifications@github.com> Sat, 16 November 2019 01:31 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 1C4001200F1 for <quic-issues@ietfa.amsl.com>; Fri, 15 Nov 2019 17:31:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Level:
X-Spam-Status: No, score=-7.999 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_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 isRzGmcpSAoK for <quic-issues@ietfa.amsl.com>; Fri, 15 Nov 2019 17:31:16 -0800 (PST)
Received: from out-18.smtp.github.com (out-18.smtp.github.com [192.30.252.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 673DF120044 for <quic-issues@ietf.org>; Fri, 15 Nov 2019 17:31:16 -0800 (PST)
Received: from github-lowworker-5fb2734.va3-iad.github.net (github-lowworker-5fb2734.va3-iad.github.net [10.48.19.27]) by smtp.github.com (Postfix) with ESMTP id ACF696E0477 for <quic-issues@ietf.org>; Fri, 15 Nov 2019 17:31:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1573867875; bh=KXvYyMCC+2nQkGLpEqHuQEktCkfCghCr6slZOaMnJ6o=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=GOVA8ShSkaGmDLTqoHsllQFO9Pfu5pJ5hc5nPfqRvTTDAjmRmUtkvYovIISKCd6tH I9Y9a6ZX1G9QF9ouSZu150eDMey25sRam6muImaVANAUtCjayUg0W0w3WDOApcg+Zo 9MPQjuOzcWNAA+bPHWygre9SPEEG6EQRZo/UEVzs=
Date: Fri, 15 Nov 2019 17:31:15 -0800
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKY4PIDPSUODXTA6OUF33SB6HEVBNHHB4UZE54@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3120/c554589952@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3120@github.com>
References: <quicwg/base-drafts/pull/3120@github.com>
Subject: Re: [quicwg/base-drafts] Add retry integrity tag (#3120)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dcf51639b73c_5eec3fee054cd960445451f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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/22tRt_6s476P7LxmDzQ0rgr2ntg>
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: Sat, 16 Nov 2019 01:31:18 -0000

Ossification. Same reason we encrypt Initial


On Fri, Nov 15, 2019 at 4:19 PM Christian Huitema <notifications@github.com>
wrote:

> Can you elaborate why? Is this about security, or ossification?
>
> -- Christian Huitema
>
> > On Nov 15, 2019, at 6:32 PM, ekr <notifications@github.com> wrote:
> >
> > 
> > The discussion on this PR and related issue #3014 indicates that there
> is interest in the Retry Integrity Tag. On top of that, the PR as-is is
> currently covered by the chairs' latest consensus call.
> >
> > Yes, and I'm responding to that saying we ought to encrypt.
> >
> > —
> > You are receiving this because you commented.
> > Reply to this email directly, view it on GitHub, or unsubscribe.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/pull/3120?email_source=notifications&email_token=AAIPLIKXYMQMDUA52WE6GMDQT4373A5CNFSM4JCAOODKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEHDPLQ#issuecomment-554579886>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAIPLIJPCTOVFIYEGVOBUB3QT4373ANCNFSM4JCAOODA>
> .
>


-- 
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/pull/3120#issuecomment-554589952

v2.23.0 | Report a Bug | By Email