Re: New Version Notification for draft-huitema-quic-mpath-req-00.txt

[Martin Thomson <[e-mail]>]

Thanks for doing this Christian.

The think that I'm most interested in here is how this relates to the
invariants we have established.  I don't think that it has any impact and
you seem to agree.  So I think we're good.

I don't think that the section on flow control makes any sense, since flow
control operates at your stream layer.

I'm going to have to think on it some more, but your suggestion in 4.7
might be a good idea.  We don't have to do that now, though we might choose
to do so if we can work through the design and implications.

On Thu, Dec 28, 2017 at 8:11 AM, Christian Huitema <[e-mail]>
wrote:

> Yes, I know full well that multipath is not in scope for V1. But since we
> are dabbling in connection migration anyhow, I thought we could just as
> well have a document listing multipath requirements and issues...
>
> -- Christian Huitema
>
>
> -------- Forwarded Message --------
> Subject: New Version Notification for draft-huitema-quic-mpath-req-00.txt
> Date: Wed, 27 Dec 2017 13:07:17 -0800
> From: [e-mail]
> To: Christian Huitema <[e-mail]> <[e-mail]>
>
> A new version of I-D, draft-huitema-quic-mpath-req-00.txt
> has been successfully submitted by Christian Huitema and posted to the
> IETF repository.
>
> Name:		draft-huitema-quic-mpath-req
> Revision:	00
> Title:		QUIC Multipath Requirements
> Document date:	2017-12-27
> Group:		Individual Submission
> Pages:		11
> URL:            https://www.ietf.org/internet-drafts/draft-huitema-quic-mpath-req-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-huitema-quic-mpath-req/
> Htmlized:       https://tools.ietf.org/html/draft-huitema-quic-mpath-req-00
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-huitema-quic-mpath-req-00
>
>
> Abstract:
>    This document describes the requirement and plausible architecture of
>    QUIC multipath extensions.  While the first version of QUIC is not
>    scheduled to include multipath extensions, there are risks that
>    decisions made in this first version might preclude some options that
>    we may later find attractive.  An early review of multipath extension
>    requirements and issues should minimize that risk.
>
>
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>
>