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 259513A00C1
 for <quic-issues@ietfa.amsl.com>; Wed, 17 Jun 2020 13:07:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.555
X-Spam-Level: 
X-Spam-Status: No, score=-1.555 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, DKIM_VALID_EF=-0.1,
 HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1,
 RCVD_IN_MSPIKE_H2=-0.001, 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 i4Q3TwpMKgh8 for <quic-issues@ietfa.amsl.com>;
 Wed, 17 Jun 2020 13:07:53 -0700 (PDT)
Received: from out-19.smtp.github.com (out-19.smtp.github.com [192.30.252.202])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id CF3DA3A0045
 for <quic-issues@ietf.org>; Wed, 17 Jun 2020 13:07:52 -0700 (PDT)
Received: from github-lowworker-0f78100.ash1-iad.github.net
 (github-lowworker-0f78100.ash1-iad.github.net [10.56.25.48])
 by smtp.github.com (Postfix) with ESMTP id 0A3AA52101E
 for <quic-issues@ietf.org>; Wed, 17 Jun 2020 13:07:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
 s=pf2014; t=1592424472;
 bh=3kutVd4w5EXB0AWaOj5gsAbDqCjCQ581rO8455PAuF0=;
 h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
 List-Archive:List-Post:List-Unsubscribe:From;
 b=s4xeAUPcJ/NBXAiKaV8ZU7ZIKXFghWVLHGM+ZxafOdQfAS3WNOuX+NSDNUASgsXB8
 xzWU87Xykmkrg/HFRwun5oClofTZhKjnnmJRMWZZ/ilp4YI8QDzDl0AmpSnIHu+YI0
 gV10wbMPaNHRlF1Pxek8k+BZg6td8rwnSmNZLC/0=
Date: Wed, 17 Jun 2020 13:07:51 -0700
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJK2XH66FIU6RLLAU6RF46ZMRPEVBNHHCMDPNOE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3763/645595855@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3763@github.com>
References: <quicwg/base-drafts/issues/3763@github.com>
Subject: Re: [quicwg/base-drafts] [Editorial] Lots of forward references
 (#3763)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5eea7817ec51b_58cc3fcd1a4cd96c195647";
 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/03UfnjvlXqEM9PCr7Xi2C1-4OsE>
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: Wed, 17 Jun 2020 20:07:58 -0000


----==_mimepart_5eea7817ec51b_58cc3fcd1a4cd96c195647
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

The larger idea is "high-level concepts, then wire encoding" which I think makes sense.  It puts the things that someone needs for a conceptual understanding of the protocol in one place, and the things that someone needs to implement the protocol elsewhere.

Within the high-level concepts, I also find it strange that connections don't come before streams.  However, the "connections" group also includes things that really don't deserve pride-of-place as the first couple things to be discussed, either.

-- 
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/3763#issuecomment-645595855
----==_mimepart_5eea7817ec51b_58cc3fcd1a4cd96c195647
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p></p>
<p>The larger idea is "high-level concepts, then wire encoding" which I think makes sense.  It puts the things that someone needs for a conceptual understanding of the protocol in one place, and the things that someone needs to implement the protocol elsewhere.</p>
<p>Within the high-level concepts, I also find it strange that connections don't come before streams.  However, the "connections" group also includes things that really don't deserve pride-of-place as the first couple things to be discussed, either.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/quicwg/base-drafts/issues/3763#issuecomment-645595855">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK5SRULM7IPP5VLX6VDRXEPBPANCNFSM4N5U5ALQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AFTOJK6JJBJTAYBO76SEDWLRXEPBPA5CNFSM4N5U5AL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEZ5QFTY.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/3763#issuecomment-645595855",
"url": "https://github.com/quicwg/base-drafts/issues/3763#issuecomment-645595855",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5eea7817ec51b_58cc3fcd1a4cd96c195647--

