Re: [re-ECN] Pls respond: Do we have a Congestion Exposure community?

[Bob Briscoe <[e-mail]>]

Steve,

Here's what was in the minutes of the Bar Bof
<http://trac.tools.ietf.org/area/tsv/trac/wiki/0907re-ECNBarBoFMinutes>

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
* known implementations
   - 1+ * Linux
   - 0+ * vendor
   - 2 * ns2
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\

1 Linux is Alan Smith's (BT)
1 ns2 is Toby Moncaster's (BT)

Both are intended to be usable by others, but 
still not ready to be official patches to the Linux kernel or the ns2 codebase.
The '+' items are people who don't want to reveal 
their plans until they are closer to knowing they 
will deliver. I guess you understand there's a 
step up between a bit of code to test your own 
ideas in a focused simulation, and fully featured 
code you would be happy to distribute to others.



Bob

At 16:13 06/09/2009, you wrote:
>Speaking of implementations/demos/simulations, is there a summary
>anywhere of what is currently available in terms of code?
>
>Thanks,
>Steve
>
>
>2009/9/6 Bob Briscoe <[e-mail]>uk>:
> > João,
> >
> > Thanks for this.
> >
> > As someone who has already implemented re-ECN (at least sufficiently for
> > your ns2 analysis), your contribution will be particularly valuable.
> >
> >
> > Bob
> >
> > At 18:00 05/09/2009, João Taveira Araújo wrote:
> >>
> >> Hi Bob,
> >>
> >> As you know, I'm very much interested in re-ECN, particularly in using
> >> some of its properties in other areas like TE/routing. I have cycles to
> >> spare so feel free to count on me for 
> reviewing/coding/booing and clapping.
> >>
> >> Cheers,
> >> Joao.
> >>
> >> Bob Briscoe wrote:
> >>>
> >>> Folks,
> >>>
> >>> I'd like to try to arrange a Congestion Exposure (re-ECN) BoF in Nov at
> >>> the Hiroshima IETF. If so, we have to 
> notify the area directors v soon - by
> >>> 24:00 UTC Mon 7 Sep 09. #1 gating function 
> for Area Directors: activity on
> >>> an ietf list.
> >>>
> >>> Therefore, pls respond preferably *on this list* if you're interested in
> >>> being involved, no matter how insignificantly, e.g.
> >>>
> >>> - you want congestion visibility for other stuff you're doing
> >>>  (but don't intend to work on it itself)
> >>> - reviewing docs,
> >>> - alternative way to achieve congestion exposure
> >>> - participate in mailing list discussion,
> >>> - co-authoring docs
> >>> - design ways to do incremental deployment
> >>> - using code for other stuff you're doing
> >>> - thinking up new uses for the protocol
> >>> - breaking it
> >>> - analysing benefits/costs
> >>> - implement protocol
> >>> - implement a demo
> >>> - running or participating in trials
> >>> - standing on the sidelines booing or clapping
> >>> - whatever
> >>>
> >>> Perceived problem:
> >>> Most people want to work on something finite like a new cool
> >>> non-TCP-friendly congestion control. Less people want to go into an
> >>> pseudo-infinite loop fixing IP to allow 
> other cool stuff to happen. If you
> >>> want something like re-ECN to be there, but 
> don't have the bandwidth to work
> >>> on it, that's cool too - please say this - 
> it's still palpable support. And
> >>> you will be likely to have review comments related to how you want to use
> >>> it.
> >>>
> >>> Cheers
> >>>
> >>>
> >>> Bob
> >>>
> >>>
> >>> ________________________________________________________________
> >>> Bob Briscoe,               Networks Research Centre, BT Research
> >>> _______________________________________________
> >>> re-ECN mailing list
> >>> [e-mail]
> >>> https://www.ietf.org/mailman/listinfo/re-ecn
> >>
> >> _______________________________________________
> >> re-ECN mailing list
> >> [e-mail]
> >> https://www.ietf.org/mailman/listinfo/re-ecn
> >
> > ________________________________________________________________
> > Bob Briscoe,               Networks Research Centre, BT Research
> > _______________________________________________
> > re-ECN mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/re-ecn
> >

________________________________________________________________
Bob Briscoe,               Networks Research Centre, BT Research