IETF Logo Mail Archive

Re: [quicwg/base-drafts] Can Initial/0-RTT CIDs safely be used for routing? (#2026)

ianswett <notifications@github.com> Tue, 20 November 2018 20:30 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 9DDD1130DCF for <quic-issues@ietfa.amsl.com>; Tue, 20 Nov 2018 12:30:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.47
X-Spam-Level:
X-Spam-Status: No, score=-8.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 9rT1lxyJKUfs for <quic-issues@ietfa.amsl.com>; Tue, 20 Nov 2018 12:30:44 -0800 (PST)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DCC6130DD0 for <quic-issues@ietf.org>; Tue, 20 Nov 2018 12:30:44 -0800 (PST)
Date: Tue, 20 Nov 2018 12:30:43 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1542745843; bh=BTNH5Ftj0xZrYCBw5L2nNaFkARMhpDbEtuFXQVQDIbU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pN8AVT0nJTkiuIUl9ohhA2VVEnLhMFm4umqyAE+hmNJe9ybpOdw93fxc9KoigMfIE sYOIwMc113laM7/XcQx6JJ73nC+MfJxZxgZZRTbs9S53EMMrG5miRBcmT8XR5QHAx9 sh1pT1PE37bLKXLNkxqwjDIj+9upOa88p6opbmMc=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab772cc5cb13b74be3c7a91608d484d51d12f7972392cf00000001180c30f392a169ce16d12586@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2026/440419026@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2026@github.com>
References: <quicwg/base-drafts/issues/2026@github.com>
Subject: Re: [quicwg/base-drafts] Can Initial/0-RTT CIDs safely be used for routing? (#2026)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bf46ef3a097d_2f203fdcd38d45c4432833"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/VRTkt0wx_uho_Y6k1H0oJI03kME>
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, 20 Nov 2018 20:30:45 -0000

I'd say sometimes it's safe and sometimes it's not and there are pros and cons of different approaches.  You mention conflicting text, can you point out the text that conflicts with the sections you quoted above in this issue?

-- 
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/2026#issuecomment-440419026

v2.23.0 | Report a Bug | By Email