Re: I-D Action: draft-ietf-quic-load-balancers-00.txt

[Martin Duke <[e-mail]>]

Hi Magnus,

An email from the chairs made me believe the adoption process was already
complete. I may have misinterpreted it.

Sorry for the misunderstanding. I am happy to proceed however you see fit.

Martin

On Wed, Jan 29, 2020 at 5:17 AM Magnus Westerlund <
[e-mail]> wrote:

> Hi,
> (as AD)
>
> This document should not have been posted as a WG document yet. The
> intention
> was to complete the re-chartering and then adopt documents in a controlled
> fashion. It was submitted but not approved to be posted by any of the
> chairs. We
> think it got posted due to the datatracker server outage recovery work.
>
> Cheers
>
> Magnus
>
>
>
> On Wed, 2020-01-29 at 08:56 +0000, Mirja Kuehlewind wrote:
> > Hi all, hi Martin,
> >
> > This is now a working group document. I thought the plan was to move the
> > protocol part of this proposal to a separate draft. Is that still the
> plan?
> >
> > Mirja
> >
> >
> >
> > On 28.01.20, 20:59, "QUIC on behalf of [e-mail]" <
> > [e-mail] on behalf of [e-mail]> wrote:
> >
> >
> >     A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> >     This draft is a work item of the QUIC WG of the IETF.
> >
> >             Title           : QUIC-LB: Generating Routable QUIC
> Connection IDs
> >             Authors         : Martin Duke
> >                               Nick Banks
> >       Filename        : draft-ietf-quic-load-balancers-00.txt
> >       Pages           : 31
> >       Date            : 2020-01-28
> >
> >     Abstract:
> >        QUIC connection IDs allow continuation of connections across
> address/
> >        port 4-tuple changes, and can store routing information for
> stateless
> >        or low-state load balancers.  They also can prevent linkability of
> >        connections across deliberate address migration through the use of
> >        protected communications between client and server.  This creates
> >        issues for load-balancing intermediaries.  This specification
> >        standardizes methods for encoding routing information and
> proposes an
> >        optional protocol called QUIC-LB to exchange the parameters of
> that
> >        encoding.  This framework also enables offload of other QUIC
> >        functions to trusted intermediaries, given the explicit
> cooperation
> >        of the QUIC server.
> >
> >
> >     The IETF datatracker status page for this draft is:
> >     https://datatracker.ietf.org/doc/draft-ietf-quic-load-balancers/
> >
> >     There are also htmlized versions available at:
> >     https://tools.ietf.org/html/draft-ietf-quic-load-balancers-00
> >
> https://datatracker.ietf.org/doc/html/draft-ietf-quic-load-balancers-00
> >
> >
> >     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.
> >
> >     Internet-Drafts are also available by anonymous FTP at:
> >     ftp://ftp.ietf.org/internet-drafts/
> >
> >
> >
> --
> Cheers
>
> Magnus Westerlund
>
>
> ----------------------------------------------------------------------
> Networks, Ericsson Research
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  [phone]
> Torshamnsgatan 23           | Mobile [phone]
> SE-164 80 Stockholm, Sweden | mailto: [e-mail]
> ----------------------------------------------------------------------
>
>
>