From: Bruce Barnett <dccp@grymoire.com>
To: dccp@vger.kernel.org
Subject: Discussion of ECN API?
Date: Mon, 19 Dec 2005 21:27:50 +0000 [thread overview]
Message-ID: <200512192127.jBJLRou27403@observ.crd.ge.COM> (raw)
I've been involved with the application perspective of DCCP
programming, or rather - application programming aware of congestion,
and I was wondering if there exists any API for other transport
protocols that make congestion information available to the
application? In particular, is there any existing API to extract the
ECN information that can be used for a model? Or if it is missing, -
how should it be specified?
One approach is to provide an array of ECN values. But how big would
this be? And how would it be packed?
Or one could return a monotonicly increasing count of ECN failures. But
what is a failure, as there are several kinds. Some errors should be
handled by the kernel (Routers that don't support ECN, etc.). Others
should be of interest to the application (there is congestion in the
return path).
One could also provide a error percentage, but how would this be calculated?
Anyone have any ideas or resources I could check?
next reply other threads:[~2005-12-19 21:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-19 21:27 Bruce Barnett [this message]
2005-12-20 14:11 ` Discussion of ECN API? Arnaldo Carvalho de Melo
2005-12-20 17:38 ` Bruce Barnett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200512192127.jBJLRou27403@observ.crd.ge.COM \
--to=dccp@grymoire.com \
--cc=dccp@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox