[e2e] Types Of Service
ssurya at ieee.org
Thu Jul 31 14:15:40 PDT 2003
----- Original Message -----
From: "Fernando Gont" <fernando at gont.com.ar>
To: "Bob Braden" <braden at isi.edu>; <end2end-interest at postel.org>
Sent: Thursday, July 31, 2003 4:22 PM
Subject: Re: [e2e] Types Of Service
> At 16:34 28/07/2003 -0700, you wrote:
> > *> However, only TCP, UDP, and RTP (which is built over UDP) come to
> > mind,
> > *> they don't guarantee any specific type of service (for example,
> > *> delay", "high throughput", etc.) by themselves.
> > *>
> >But in principle, they could. The original IP specification DID
> >include a TOS byte with delay and throughput bits.
> Yes, but it didn't *guarantee* the service.
> > *> Besides that, for example, TCP provides a "realiable" byte stream.
> > However,
> > *> there are some errors that TCP won't catch, so if reliability is a
> > *> issue, then another layer of error control must be built up on top
> > of TCP.
> > *>
> >Presumably you are referring to local system errors between TCP and the
> >applications. This would ultimately have to be dealt with at the
> >application layer, of course (see the classic E2E argument paper.)
> What's the author/title of that paper? Is it available online?
title: "End-to-End arguments in system design".
> >Or are you referring to the weakness of the TCP checksum?
> Yes, that's what I was referring to.
> Fernando Gont
> e-mail: fernando at gont.com.ar || fgont at acm.org
More information about the end2end-interest