Hello All , THe URL specified for this document does not
exist as of this morning . Does anyone have another ?
Tia , JimL
On Tue, 6 Feb 2001 [EMAIL PROTECTED] wrote:
A New Internet-Draft is available from the on-line Internet-Drafts
directories. This draft
One of the history lessons on this list about 6 months back referred to Dag
Belsnes' original research proving that you cannot move a data item and end
up with both parties knowing that the data has arrived safely in less than
5 packets. Other people have the referentsit's not obvious to
1. There are two annoying incompetence of TCP. One is that
TCP does not distinguish packet loss caused by network
transmission error from that caused by network congestion.
The congestion control and avoidance mechanism makes TCP
drop its transmit window upon detecting a packet loss,
ATP Header Format
The IPv6 packet whose payload contains an ATP packet must conform to latest IPv6
specification, currently RFC 2460. ATP suggest that the traffic class field should
renamed to 'flags'. The leftmost bit could be RTP(real time payload), the rightmost be
ECN(Explicit Congestion
Is that a bit of chauvinism, Harald? :-)
D. Belsnes, "Single-Message Communication," IEEE Transactions on
Communication, Vol. TCOM -24, No. 2, pp. 190--194, February 1976.
You're right, the TCP peak was 1.48Gbps from the show floor in Dallas to a
storage cluster at Berkeley Laboratory. Single applications using multiple
stream. Bottleneck link was 1.5Gbps provisioned circuit on Qwest link from
convention center to DARPA's HSCC pop node.
This beat last years
Jun'an Gao wrote:
The host *is* the edge of the network.
I'm sorry to have not mentioned that I consider the host nodes, or the end nodes,
are not edges but instead something attaching on network edges. I consider the very
last hub, or the access router which the end nodes connected to as
General question:
if you are proposing that the IETF should investigate ATP, have you
submitted the proposal as an internet-draft?
If not, why not?
--
Harald Tveit Alvestrand, [EMAIL PROTECTED]
+47 41 44 29 94
Personal email: [EMAIL PROTECTED]
* From [EMAIL PROTECTED] Tue Feb 6 20:18:29 2001
* X-URI: http://www.cs.utk.edu/~moore/
* From: Keith Moore [EMAIL PROTECTED]
* To: "Jun'an Gao" [EMAIL PROTECTED]
* cc: [EMAIL PROTECTED]
* Subject: Re: An alternative to TCP (part 1)
* Date: Tue, 06 Feb 2001 22:46:02 -0500
*
Hi folks (esp. IETFers in Latin America):
The advance program and registration information for SIGCOMM's Workshop on
Data Communication in Latin American and the Caribbean is now up. We've got a
great keynote speaker (Jose Maria Figueres, head of the UN technology program
and thus spearheading
Bob,
I think I attended that BOF, but if I recall correctly I came away from
it thinking that the group had based its conclusions on a fairly narrow
set of assumptions about the nature and use of that protocol; change
those assumptions slightly and it gets much more feasible.
At any rate I
I have a question:
If the traffic class field in the IPv6 header was changed, as suggested, to
a set of flags, then how would a full gammit of differentiated services be
indicated? In other words, if there is only one flag indicating type of
service, then different levels of, for example,
I am interested in a comprehensive definition of Quality of Service (QoS) in the
Internet context. If anyone can point out some resources, my thanks in advance.
Nara Kamath
Start with RFC 2990. It has good references.
Brian
[EMAIL PROTECTED] wrote:
I am interested in a comprehensive definition of Quality of Service (QoS) in the
Internet context. If anyone can point out some resources, my thanks in advance.
Nara Kamath
The host *is* the edge of the network.
I'm sorry to have not mentioned that I consider the host nodes, or
the end nodes, are not edges but instead something attaching on
network edges. I consider the very last hub, or the access router
which the end nodes connected to as the 'network
Richard Carlson wrote:
You're right, the TCP peak was 1.48Gbps from the show floor in Dallas to a
storage cluster at Berkeley Laboratory. Single applications using multiple
stream. Bottleneck link was 1.5Gbps provisioned circuit on Qwest link from
convention center to DARPA's HSCC pop
The host *is* the edge of the network.
I'm sorry to have not mentioned that I consider the host nodes,
or the end nodes, are not edges but instead something attaching
on network edges. I consider the very last hub, or the access router
which the end nodes connected to as the 'network
if you are proposing that the IETF should investigate ATP, have you
submitted the proposal as an internet-draft?
No.
If not, why not?
I myself have some unsureness on ATP.
1. There're too many contraints in the tranditional TCP/IPv4 internet environment. So
ATP is going to be optimized for
It is very hard to read your valuable contributions because you aren't
sending pre-formatted text, rather one line per paragraph.
I'm very sorry! I'll resend part 2 after I pre-format it.
I have a question:
If the traffic class field in the IPv6 header was changed, as suggested, to
a set of flags, then how would a full gammit of differentiated services be
indicated? In other words, if there is only one flag indicating type of
service, then different levels of, for example,
Richard Carlson wrote:
You're right, the TCP peak was 1.48Gbps from the show floor in Dallas to
a
storage cluster at Berkeley Laboratory. Single applications using
multiple
stream. Bottleneck link was 1.5Gbps provisioned circuit on Qwest link
from
convention center to DARPA's HSCC pop
21 matches
Mail list logo
