[re-ECN] FW: New draft Conex charter - for rapid comments please

[<[e-mail]>]

Cc list, which got dropped by mistake
phil

-----Original Message-----
From: Eardley,PL,Philip,DEE1 R 
Sent: 31 March 2010 17:45
To: 'Alissa Cooper'
Subject: RE: [re-ECN] New draft Conex charter - for rapid comments
please


> >
> > In establishing this working group, much interest was expressed in 
> > pursuing an IPv4 specification. A new work item proposed for TSVWG
> > would define how 'bit 48' of the IPv4 header can be used for  
> > Experiments.
> >
> [AC] It's unclear what this means -- has the work item already been
> proposed? Will it definitely be proposed? Or does the CONEX 
> group just  
> really hope it gets proposed so we can get on with standardizing  
> something in the IPv4 header?
> 
At the moment, the last is nearest

How about this -
The WG hopes that other IETF work (to be proposed for TSVWG) will define
how 'bit 48' of the IPv4 header can be used for Experiments.

Thanks
phil 

----


-----Original Message-----
From: Alissa Cooper [mailto:[e-mail]] 
Sent: 31 March 2010 17:36
To: Eardley,PL,Philip,DEE1 R
Subject: Re: [re-ECN] New draft Conex charter - for rapid comments
please


Two comments inline...

On Mar 30, 2010, at 6:40 AM, <[e-mail]>
<[e-mail] 
 > wrote:
>
> ---
> Congestion Exposure (CONEX) WG
>
>
> The purpose of the CONEX working group is to develop a mechanism by
> which senders inform the network about the congestion their packets  
> encounter. Today, the network signals congestion by ECN marking or  
> dropping packets, the receiver passes this information back to the  
> sender in transport layer acknowledgements, where the sender makes  
> an adjustment to its window size or data rate as appropriate.
>
[AC] s/the receiver passes/and the receiver passes/
> The mechanism to be developed under CONEX will enable the sender to
> also relay the congestion information back into the IP layer such  
> that the total level of congestion is visible to all IP devices  
> along the path.
>
> The primary goal of the CONEX WG is to develop experimental
> specifications to achieve the above. To help explore how to squeeze  
> the necessary information into a very limited numbers of header  
> bits, the WG will also develop an abstract specification for the  
> congestion exposure mechanism, independent of transport and protocol  
> version.
>
> Primary work items are:
>
> *       An Informational document with an abstract specification for  
> the congestion exposure mechanism
> *       Experimental Specification of IPv6 packet structure that  
> encapsulates CONEX information (header bits, interpretation).
>
> *       Experimental Specification for modification to TCP, for the  
> timely transport of congestion information from the destination to
> the sender
>
> It is believed that the CONEX mechanism will be useful as a
> generative technology which can be applied as a key element of  
> congestion management solutions in a wide variety of use cases.  
> However, the WG will initially focus solely on one use case, where  
> the end hosts and the network of the destination end host are CONEX- 
> enabled but the other networks are not. CONEX information can assist  
> the network operator's traffic management and incentivise LEDBAT- 
> like applications. Experiments on the use case are encouraged and  
> the WG will solicit input about their process and findings. The  
> output of the WG includes Informational document(s) for the use case  
> covering:
>
> *       Assumptions it makes
> *       Deployment considerations
> *       Security Threats
> *       Advice on mitigating threats (detailed work on a mechanism  
> to mitigate the threats is out of the initial scope)
> *       Description of results from experiments on the use case
>
> In establishing this working group, much interest was expressed in
> pursuing an IPv4 specification. A new work item proposed for TSVWG  
> would define how 'bit 48' of the IPv4 header can be used for  
> Experiments.
>
[AC] It's unclear what this means -- has the work item already been  
proposed? Will it definitely be proposed? Or does the CONEX group just  
really hope it gets proposed so we can get on with standardizing  
something in the IPv4 header?

> At the appropriate time, the CONEX WG will consider rechartering to
> include a work item to specify the IPv4 packet structure to  
> encapsulate CONEX information.
>
> Milestones
>
> Jul 2010 Internet-draft Informational document with an abstract
> specification for the congestion exposure mechanism
>
> Jul 2010 Internet-draft use case
>
> Sep 2010 Internet-draft specification of IPv6 packet structure.
>
> Sep 2010 Internet-draft specification for modification to TCP
>
> Mar 2011 Informational RFC abstract specification of the congestion
> exposure mechanism
>
> Mar 2011 Informational RFC use case
>
> Sep 2011 Experimental RFC specification of IPv6 packet structure
>
> Sep 2011 Experimental RFC specification for modification to TCP
>
> _______________________________________________
> re-ECN mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/re-ecn