Re: [re-ECN] Viability issue #1

> -----Original Message-----
> From: re-ecn-bounces@ietf.org [mailto:re-ecn-bounces@ietf.org] On
> Behalf Of Leslie Daigle
> Sent: 05 November 2009 06:06
> To: re-ecn@ietf.org
> Subject: [re-ECN] Viability issue #1
> 
> 
> [This attempts to outline an issue that could be perceived as
> challenging the viability of congestion exposure work.  The goal is to
> capture the issue, as well as itemize reasonable supporting arguments
> (for viability) and remaining questions to be addressed.  Please
> respond
> with suggestions as needed for each section.  ]
> 
> 
> Viability Issue #1
> 
> What are the points in favour of/against congestion exposure as an
> architecturally sound technique to specify for the Internet?  (NB --
> this is about congestion exposure, as constrained in the agreed
> principles, not any particular proposal)?
> 
> Suggested:
> 
> 1/ This is about network flows, not applications or services, so it
> will
> serve future network uses (application types).

I would go further and say this is even about single packets in
isolation. Allowing each packet to inform the network of the cost (in
resources, not money) of conveying it to the destination

> 
> 2/ Congestion exposure provides mechanisms to declare awareness of
> whole-path congestion WITHOUT prescribing behaviours.

Yes, and more to the point almost any behaviour you wanted could be
built on top of congestion exposure...

> 
> 3/ This is also network agnostic in the sense that no pre-existing
> agreements or interpretations need be in place to make the congestion
> exposure work.  (*Accounting* for it is a separate matter, but that's
> okay).

As long as this is specified in such a manner that middleboxes are able
to transparently forward the correct information then this is true

> 
> 
> Questions:
> 
> 4/ To what extent is this dependent on an assumed network architecture
> where the major sources of content (and congestion) traverse transit
> networks, as opposed to being CDNs connected directly to access
> networks
> (for business purposes)?

Even if they are CDNs they are still going to potentially cause
congestion that someone may need to account for. Indeed many people
suggest most congestion is in the access... Congestion exposure is NOT
just about inter-network agreements. It also works intra-network
(imagine a company being able to relax their rules on network access
during working hours as long as their employees ensured they never
caused excessive congestion that might impact business-needs use of the
network).

> 
> 
> 
> --
> 
> -------------------------------------------------------------------
> "Reality:
>       Yours to discover."
>                                  -- ThinkingCat
> Leslie Daigle
> leslie@thinkingcat.com
> -------------------------------------------------------------------
> _______________________________________________
> re-ECN mailing list
> re-ECN@ietf.org
> https://www.ietf.org/mailman/listinfo/re-ecn