Re: [re-ECN] ConEx-IP & ConEx-TCP as separate docs?

[Mirja Kuehlewind <[e-mail]>]

> The main point should be that an implementor of an (incentive)dropper or a
> congestion volume policer should ideally only need to read the ConEx IP
> document to get enough informaton. Application developers would need to
> read both ConEx IP and the transport related ConEx docs.
That's a good point. Inline with that we have to address how to handle 
not-ConEx packets. In a long range from my understanding it would be the goal 
to make very IP packets ConEx-capable. That would mean you need to have an 
IP(-only) spec and also specify requirements for a feedback mechanism (in 
transport layer) regarding e.g. max delay of the ConEx information or 
whatever.

So the question is: Is the goal to make ConEx used by very kind of transport? 
Or does ConEx also work if just some connections use it (e.g. TCP based 
ones)?

I'm not sure if a policer at network ingress makes any sense if one easily can 
avoid to exposure the congestion information by not using TCP...

Mirja