Re: WGLC: draft-ietf-appsawg-http-forwarded-02.txt

I wonder if the forwarded information should also include TCP header
options ( http://www.networksorcery.com/enp/protocol/tcp.htm#Option<http://www.networksorcery.com/enp/protocol/tcp.htm#Options>s)
based on the TCP connection carrying the original GET request.

Peter

On Tue, May 1, 2012 at 7:33 PM, Mark Nottingham <mnot@mnot.net> wrote:

> HTTP folk,
>
> Please have a look at this document and send along comments, especially if
> you're an intermediary or firewall person, or consume the existing
> X-Forwarded-For header.
>
> <http://tools.ietf.org/html/draft-ietf-appsawg-http-forwarded-02>
>
> Cheers,
>
>
> Begin forwarded message:
>
> > From: Alexey Melnikov <alexey.melnikov@isode.com>
> > Subject: [apps-discuss] WGLC: draft-ietf-appsawg-http-forwarded-02.txt
> > Date: 2 May 2012 4:26:50 AM AEST
> > To: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
> >
> > Dear WG participants,
> > I would like to initiate WG Last Call on
> draft-ietf-appsawg-http-forwarded-02.txt ("Forwarded HTTP Extension").
> Please send your reviews, as well as expressions of support regarding
> document readiness for IESG (or not) either to the mailing list, or
> directly to WG chairs (Murray Kucherawy <msk@cloudmark.com> and myself).
> Comments like "I've read the document and it is Ok to publish" or "I've
> read the document and it has the following issues" are useful and would be
> gratefully accepted by chairs.
> >
> > The WGLC will end on Friday, May 18th.
> >
> > Thank you,
> > Alexey as an APPSAWG co-chair.
> >
> > _______________________________________________
> > apps-discuss mailing list
> > apps-discuss@ietf.org
> > https://www.ietf.org/mailman/listinfo/apps-discuss
>
> --
> Mark Nottingham
> http://www.mnot.net/
>
>
>
>
>
>