Re: [tcpm] Fwd: New Version Notification for draft-williams-exp-tcp-host-id-opt-03.txt

Hi Brandon, all,

Thanks a lot for this update. Indeed, the update takes into account TCPM feedback, and this is excellent.

However, based on the list discussion so far, it seems to the chairs that this document would be a better fit to an independent stream submission. The TCP option described in this document actually does not modify any TCP logic. Identifying the hosts that are hidden behind a shared address/prefix sharing device or application-layer proxy seems like a new service that current TCP does not offer. TCPM is only chartered for minor TCP extensions.

Also, in its current form, it seems that this document formally does not require TCPM adoption. While TCPM documents probably (hopefully!) have more weight among end-system TCP stack implementers, it is much less clear whether a TCPM document on this specific topic will indeed foster implementation convergence among middleboxes. We have no empirical evidence for that.

TCPM is used to adopt new working group items based on rather strong consensus. According to the list discussion so far, the TCPM chairs currently understand that there is no consensus in the TCPM community to adopt this document at this point in time. 

Obviously, as usual in the IETF, further list discussion is welcome.

Best regards

Michael
on behalf of the TCPM chairs 

> -----Original Message-----
> From: tcpm [mailto:tcpm-bounces@ietf.org] On Behalf Of Brandon Williams
> Sent: Wednesday, April 30, 2014 4:44 PM
> To: tcpm@ietf.org
> Subject: [tcpm] Fwd: New Version Notification for draft-williams-exp-
> tcp-host-id-opt-03.txt
> 
> We have updated the draft based on feedback on the list and in London.
> In particular, we have attempted to provide a clearer explanation of
> the
> use cases we are attempting to address and why solutions at other
> layers
> in the protocol stack do not work for these use cases. Previous updates
> had already attempted to provide stronger limiting guidance for option
> usage.
> 
> As we have indicated previously on the list, we would prefer to see WG
> adoption of this I.D. rather than working toward publishing as an
> individual submission. We think WG adoption has a few benefits, even in
> the absence of clear consensus on the question of whether this is a
> good
> idea. First and foremost, WG adoption would mean that the limiting
> guidance on usage carries more weight. And second, WG adoption would
> more strongly encourage individual implementations that are already in
> use to converge on a single option format.
> 
> We look forward to your feedback.
> 
> Thanks,
> --Brandon
> 
> 
> -------- Original Message --------
> Subject: New Version Notification for
> draft-williams-exp-tcp-host-id-opt-03.txt
> Date: Wed, 30 Apr 2014 10:22:20 -0400
> From: internet-drafts@ietf.org <internet-drafts@ietf.org>
> To: Williams, Brandon <brandon.williams@akamai.com>, Dan Wing
> <dwing@cisco.com>, Mohamed Boucadair <mohamed.boucadair@orange.com>,
> Mohamed Boucadair <mohamed.boucadair@orange.com>, Dan Wing
> <dwing@cisco.com>, Williams, Brandon <brandon.williams@akamai.com>
> 
> 
> A new version of I-D, draft-williams-exp-tcp-host-id-opt-03.txt
> has been successfully submitted by Brandon Williams and posted to the
> IETF repository.
> 
> Name:		draft-williams-exp-tcp-host-id-opt
> Revision:	03
> Title:		Experimental Option for TCP Host Identification
> Document date:	2014-04-29
> Group:		Individual Submission
> Pages:		11
> URL:
> http://www.ietf.org/internet-drafts/draft-williams-exp-tcp-host-id-opt-
> 03.txt
> Status:
> https://datatracker.ietf.org/doc/draft-williams-exp-tcp-host-id-opt/
> Htmlized:
> http://tools.ietf.org/html/draft-williams-exp-tcp-host-id-opt-03
> Diff:
> http://www.ietf.org/rfcdiff?url2=draft-williams-exp-tcp-host-id-opt-03
> 
> Abstract:
>     Recent IETF proposals have identified benefits to more distinctly
>     identifying the hosts that are hidden behind a shared
> address/prefix
>     sharing device or application-layer proxy.  Analysis indicates that
>     the use of a TCP option for this purpose can be successfully
> applied
>     to a broad range of use cases.  This document describes a common
>     experimental TCP option format for host identification.
> 
> 
> 
> 
> 
> 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
> 
> 
> --
> Brandon Williams; Senior Principal Software Engineer
> Emerging Products Engineering; Akamai Technologies Inc.
> 
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm