IETF Logo Mail Archive

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

Mike Bishop <notifications@github.com> Mon, 26 November 2018 19:50 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 D1F4A130F4A for <quic-issues@ietfa.amsl.com>; Mon, 26 Nov 2018 11:50:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Level:
X-Spam-Status: No, score=-9.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, 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 KkMtHrMfUD8D for <quic-issues@ietfa.amsl.com>; Mon, 26 Nov 2018 11:50:11 -0800 (PST)
Received: from out-16.smtp.github.com (out-16.smtp.github.com [192.30.254.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 635AC130E2B for <quic-issues@ietf.org>; Mon, 26 Nov 2018 11:50:09 -0800 (PST)
Date: Mon, 26 Nov 2018 11:50:08 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1543261809; bh=wzYIPsg3igGN4LTpzQfMmZJeqvHZZkV8ABTuSAn/8vg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=BkXJxAnc6SAPcFtts4nynbKDTZeA3yFX2lbTAV85YKSEOZQ5VIF/UloJhWpdZQX4v NGUQaE9LriVeRq8wQL+HBaizv81DaKhGVvr6foY9w54/rt1PcfXtlEBMNdH5KnPSsF Oi2PjLHrrZWjslv34e/6+FS1/gYsCe9wfxkKYKS4=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abe566c89419683e0ee609c458ab5007a9d9407e7a92cf000000011814107092a169ce16d12586@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/441774129@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_5bfc4e70c76cc_63d83fde1e4d45b83921e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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/I_H1nYFT2J12-BYrJA8ehqIqKY4>
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: Mon, 26 Nov 2018 19:50:14 -0000

Obviously I think we should.  :-)  If we think there's a place for both, then let's give both some airtime in the spec.

-- 
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-441774129

v2.23.0 | Report a Bug | By Email