Date: Fri, 18 Jan 2019 00:03:15 -0800
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4abac54bf02e02da05a13d53b23facb48898f951c7c92cf0000000118594a4392a169ce17e0dd5b@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2348@github.com>
Subject: [quicwg/base-drafts] Specify IPv6 flow label for QUIC (#2348)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5c418843d961a_14113fb24f4d45b8284060";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/EMhFHRBKw6SYJXT1_KdH-ADVRy4>


----==_mimepart_5c418843d961a_14113fb24f4d45b8284060
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

There is an ongoing push in the IPv6 working group for conformance to [RFC 6437](https://tools.ietf.org/html/rfc6437). The pseudo random flow label enables routers to perform flow-preserving load balancing without having to parse the transport header, which in IPv6 is sometimes hidden behind a chain of extension headers.

For QUIC, that would probably mean setting the IPv6 flow label to a pseudorandom value function of the source and destination addresses and ports and the Destination Connection ID (if present). Should we mention that in the transport 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/2348
----==_mimepart_5c418843d961a_14113fb24f4d45b8284060
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>There is an ongoing push in the IPv6 working group for conformance to <a href="https://tools.ietf.org/html/rfc6437" rel="nofollow">RFC 6437</a>. The pseudo random flow label enables routers to perform flow-preserving load balancing without having to parse the transport header, which in IPv6 is sometimes hidden behind a chain of extension headers.</p>
<p>For QUIC, that would probably mean setting the IPv6 flow label to a pseudorandom value function of the source and destination addresses and ports and the Destination Connection ID (if present). Should we mention that in the transport spec?</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/2348">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AWbkq-h4SRlE7x16MiRpZSQDZz2xghq9ks5vEX_DgaJpZM4aHaIS">mute the thread</a>.<img src="https://github.com/notifications/beacon/AWbkq2D6pfuJ0Ha4OEp6B7p8FkM0l6ycks5vEX_DgaJpZM4aHaIS.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"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":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/quicwg/base-drafts"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"Specify IPv6 flow label for QUIC (#2348)"}],"action":{"name":"View Issue","url":"https://github.com/quicwg/base-drafts/issues/2348"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/2348",
"url": "https://github.com/quicwg/base-drafts/issues/2348",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5c418843d961a_14113fb24f4d45b8284060--