RE: [newtrk] IESG comments on ISD proposal

"Hallam-Baker, Phillip" <pbaker@verisign.com> Tue, 10 May 2005 20:52 UTC

Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19514 for <newtrk-archive@lists.ietf.org>; Tue, 10 May 2005 16:52:07 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1]) by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j4AKoIIq009751; Tue, 10 May 2005 13:50:18 -0700 (PDT)
Received: (from majordom@localhost) by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j4AKoI9O009750; Tue, 10 May 2005 13:50:18 -0700 (PDT)
Received: from colibri.verisign.com (colibri.verisign.com [65.205.251.74]) by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j4AKoHsg009731 for <newtrk@lists.uoregon.edu>; Tue, 10 May 2005 13:50:17 -0700 (PDT)
Received: from mou1wnexcn01.vcorp.ad.vrsn.com (mailer1.verisign.com [65.205.251.34]) by colibri.verisign.com (8.12.11/8.12.11) with ESMTP id j4AKoH5d018088; Tue, 10 May 2005 13:50:17 -0700 (PDT)
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by mou1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 10 May 2005 13:50:17 -0700
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Subject: RE: [newtrk] IESG comments on ISD proposal
Date: Tue, 10 May 2005 13:50:16 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37250255@MOU1WNEXMB04.vcorp.ad.vrsn.com>
Thread-Topic: [newtrk] IESG comments on ISD proposal
Thread-Index: AcVVn/nceVrZMi4bRqe1ur7J5IMdOwAATanQ
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "Spencer Dawkins" <spencer@mcsr-labs.org>, "NEWTRK" <newtrk@lists.uoregon.edu>
X-OriginalArrivalTime: 10 May 2005 20:50:17.0372 (UTC) FILETIME=[DF42CDC0:01C555A1]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by darkwing.uoregon.edu id j4AKoHsg009742
Sender: owner-newtrk@lists.uoregon.edu
Precedence: bulk
Reply-To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
Content-Transfer-Encoding: 8bit

Appols for top-posting but Spencer is saying something important here:

The STD series is worse than useless. If people considered the STD
series to be the canonical definition for the protocols they would be
creating implementations that actually harm the Internet.

If we have two versions of a protocol and one is known to cause actual
harm it is neither logical nor acceptable for the harmful version of the
protocol to have a higher standards status.


I propose that whenever an RFC is issued that has 'obsoletes RFC xxx' in
the header that this automatically cause RFC xxx to be moved to the
obsolete standards list.



> -----Original Message-----
> From: owner-newtrk@lists.uoregon.edu 
> [mailto:owner-newtrk@lists.uoregon.edu] On Behalf Of Spencer Dawkins
> Sent: Tuesday, May 10, 2005 4:36 PM
> To: NEWTRK
> Subject: Re: [newtrk] IESG comments on ISD proposal
> 
> 
> > More to the point, the original claim, viz. "the Internet runs
> > mainly on
> > Proposed Standards", still hasn't been substantiated.  Even if you 
> > ignore
> > the same *type* of process, there is no way that IP is a mere 
> > "Proposed
> > Standard".
> 
> I did not originate this assertion, but I believe it and have 
> repeated 
> it in public, so...
> 
> When I have repeated this assertion, it's often been in the 
> context of 
> TCP.
> 
> You might think that TCP is a full standard, since RFC 793 TCP is a 
> full standard, but if you watch any modern TCP with tcpdump or some 
> equivalent, you will discover that the TCP is implementing a larger 
> initial congestion window, fast start/congestion avoidance, fast 
> retransmit, fast reecovery, SACK, window scaling, maybe Eifel, and 
> probably some other items that I never heard of or forgot. All of 
> these are proposed standards.
> 
> RFC 793 TCP was prone to persistent oscillating congestion in network 
> conditions encountered during the late 1980s. One can only imagine 
> what the Internet would be like today, if it was running on THIS full 
> standard. Happily, the Internet is running on proposed standards.
> 
> Your mileage may vary, if you're thinking of different protocols, of 
> course.
> 
> Spencer 
> 
> 
> .
> newtrk resources:_____________________________________________________
> web user interface: http://darkwing.uoregon.edu/~llynch/newtrk.html
> mhonarc archive: http://darkwing.uoregon.edu/~llynch/newtrk/index.html
> 
> 

.
newtrk resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/newtrk.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/newtrk/index.html