Re: [quicwg/base-drafts] Connection ID DT output (#1742)

Martin Thomson <notifications@github.com> Tue, 25 September 2018 01:09 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 6FD49131166 for <quic-issues@ietfa.amsl.com>; Mon, 24 Sep 2018 18:09:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Level:
X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 Nc8JVPvReflF for <quic-issues@ietfa.amsl.com>; Mon, 24 Sep 2018 18:09:49 -0700 (PDT)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9734E13115B for <quic-issues@ietf.org>; Mon, 24 Sep 2018 18:09:49 -0700 (PDT)
Date: Mon, 24 Sep 2018 18:09:48 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1537837788; bh=GD5TFsd0WXwH0Wd3wnQaHW8LgNsEMBvUsrk1thKwYuU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=iLoTEbMb45o0Yk4JiU7IhJw+2PNWx1StGeT8YjlXLMWRsQ19BoZaOyKo/ebcLVWtJ vgYkAqo8c1c+4CrEAueDDbycQ62mXx/ou0Y1LWqurVR9umDfrWPQI7Zn4GA3nU07uY EoHdEIdoASbt1yFivcOtw+OoYOMui4EdPyQzerPg=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab6702315bfa9ef4867148ac7d8aa4bbf8e10a04f392cf0000000117c14cdc92a169ce156fd3c0@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1742/review/158348635@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1742@github.com>
References: <quicwg/base-drafts/pull/1742@github.com>
Subject: Re: [quicwg/base-drafts] Connection ID DT output (#1742)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ba98adce3917_30c33ff60e4d45c419089a"; 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/Z-72g80VHnmo-o3sNiMyvNsiy5g>
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, 25 Sep 2018 01:09:51 -0000

martinthomson commented on this pull request.



>  
 
 ### Issuing Connection IDs
 
-An endpoint issues connection IDs to its peer for the peer to use when sending
-packets. This allows the endpoint control over the strategy used to interpret
-connection IDs of packets that it receives.  These connection IDs are
-communicated to the peer using NEW_CONNECTION_ID frames
-({{frame-new-connection-id}}).
+The initial connection ID issued by an endpoint is the Source Connection ID
+during the handshake.  Subsequent connection IDs are communicated to the peer
+using NEW_CONNECTION_ID frames ({{frame-new-connection-id}}).  While each
+endpoint independently chooses how many connection IDs to issue, a recommended
+number of outstanding connection IDs is eight.

endpoints SHOULD provide and maintain at least 8 connection IDs......

-- 
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/1742#pullrequestreview-158348635