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 BDC4A132396
 for <quic-issues@ietfa.amsl.com>; Fri, 13 Oct 2017 12:34:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.616
X-Spam-Level: 
X-Spam-Status: No, score=-5.616 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001,
 RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01,
 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 ZJLEOtt_ZuZt for <quic-issues@ietfa.amsl.com>;
 Fri, 13 Oct 2017 12:34:32 -0700 (PDT)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net
 (github-smtp2-ext8.iad.github.net [192.30.252.199])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 34945126BF0
 for <quic-issues@ietf.org>; Fri, 13 Oct 2017 12:34:32 -0700 (PDT)
Date: Fri, 13 Oct 2017 12:34:31 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
 s=pf2014; t=1507923271;
 bh=Fdp1uV9vRA3vM/vbG0TVgEl+MaPRVGyNeBAG/mqcc20=;
 h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
 List-Archive:List-Post:List-Unsubscribe:From;
 b=Va2h1SZiQt4F6AuCQ/d3pR6IKRXmZwv/zO/74RXhhLJ9Kubmfo9M6/7xy0uCeOhNs
 +AQ6IUvyvyoY0ja8C4IWQkuxRar1Q+18qltJpY0UsqN9XE2N6ifccAxXBEQsCg+3cP
 JC0hImZ+srH6DUc8hqCfU4dDw2HN9lMxPluAQvCk=
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab9545b09a4b764590f7c934f64fc8a99bc8ea7b1992cf0000000115f8d74792a169ce0fa5b4c1@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/821/336547456@github.com>
In-Reply-To: <quicwg/base-drafts/issues/821@github.com>
References: <quicwg/base-drafts/issues/821@github.com>
Subject: Re: [quicwg/base-drafts] stateful routing by intermediaries (#821)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_59e115474d141_ac63ff35be46f2c1699a";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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/GqvhUMvizE3fg4zJygbL7XJ7W50>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 13 Oct 2017 19:34:33 -0000


----==_mimepart_59e115474d141_ac63ff35be46f2c1699a
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Any intermediary has to be working with teh server or the client, since the keys aren't available to an intermediary otherwise. Isn't it adequate to have the end that teh intermediary is in cahoots with not send omit_connection_id? Meaning, if this is a reverse proxy, then the server *knows* to not send omit_connection_id, and itself always sends the connection ID. Why is that not enough?

-- 
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/821#issuecomment-336547456
----==_mimepart_59e115474d141_ac63ff35be46f2c1699a
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>Any intermediary has to be working with teh server or the client, sinc=
e the keys aren't available to an intermediary otherwise. Isn't it adequa=
te to have the end that teh intermediary is in cahoots with not send omit=
_connection_id? Meaning, if this is a reverse proxy, then the server <em>=
knows</em> to not send omit_connection_id, and itself always sends the co=
nnection ID. Why is that not enough?</p>

<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&m=
dash;<br />You are receiving this because you are subscribed to this thre=
ad.<br />Reply to this email directly, <a href=3D"https://github.com/quic=
wg/base-drafts/issues/821#issuecomment-336547456">view it on GitHub</a>, =
or <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkq8O9B=
IH27JufCytCpZtIbNgWhYTYks5sr7tHgaJpZM4PsfuY">mute the thread</a>.<img alt=
=3D"" height=3D"1" src=3D"https://github.com/notifications/beacon/AWbkqxv=
PlyA6M-bgtRITGjGrcPcpbVFpks5sr7tHgaJpZM4PsfuY.gif" width=3D"1" /></p>
<div itemscope itemtype=3D"http://schema.org/EmailMessage">
<div itemprop=3D"action" itemscope itemtype=3D"http://schema.org/ViewActi=
on">
  <link itemprop=3D"url" href=3D"https://github.com/quicwg/base-drafts/is=
sues/821#issuecomment-336547456"></link>
  <meta itemprop=3D"name" content=3D"View Issue"></meta>
</div>
<meta itemprop=3D"description" content=3D"View this Issue on GitHub"></me=
ta>
</div>

<script type=3D"application/json" data-scope=3D"inboxmarkup">{"api_versio=
n":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name"=
:"GitHub"},"entity":{"external_key":"github/quicwg/base-drafts","title":"=
quicwg/base-drafts","subtitle":"GitHub repository","main_image_url":"http=
s://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6=
-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubuserconte=
nt.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","=
action":{"name":"Open in GitHub","url":"https://github.com/quicwg/base-dr=
afts"}},"updates":{"snippets":[{"icon":"PERSON","message":"@janaiyengar i=
n #821: Any intermediary has to be working with teh server or the client,=
 since the keys aren't available to an intermediary otherwise. Isn't it a=
dequate to have the end that teh intermediary is in cahoots with not send=
 omit_connection_id? Meaning, if this is a reverse proxy, then the server=
 *knows* to not send omit_connection_id, and itself always sends the conn=
ection ID. Why is that not enough?"}],"action":{"name":"View Issue","url"=
:"https://github.com/quicwg/base-drafts/issues/821#issuecomment-336547456=
"}}}</script>=

----==_mimepart_59e115474d141_ac63ff35be46f2c1699a--

