IETF Logo Mail Archive

Re: Did Internet Founders Actually Anticipate Paid, Prioritized Traffic?

Richard Bennett <richard@bennett.com> Mon, 13 September 2010 20:16 UTC

Return-Path: <richard@bennett.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9D0983A6AA9 for <ietf@core3.amsl.com>; Mon, 13 Sep 2010 13:16:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.082
X-Spam-Level:
X-Spam-Status: No, score=-2.082 tagged_above=-999 required=5 tests=[AWL=-0.941, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vE22fuv+VcHe for <ietf@core3.amsl.com>; Mon, 13 Sep 2010 13:16:22 -0700 (PDT)
Received: from biz88.inmotionhosting.com (biz88.inmotionhosting.com [74.124.210.180]) by core3.amsl.com (Postfix) with ESMTP id 610053A6A96 for <ietf@ietf.org>; Mon, 13 Sep 2010 13:16:22 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=bennett.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=OXc/lgliPBkDPZcCqjvQ6U15STkNJBRnhEaKzUIzu2EmdIiTDwbzEKINlLxU4283ngL7VSMxhm7BVI57u6g+WiUjs9Uon4pxF1HjX7BEBXVmE6PiS0Uz5N0Z1ZMkzmAf;
Received: from c-24-5-230-26.hsd1.ca.comcast.net ([24.5.230.26] helo=[192.168.1.109]) by biz88.inmotionhosting.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <richard@bennett.com>) id 1OvFSL-0001lX-36; Mon, 13 Sep 2010 13:16:49 -0700
Message-ID: <4C8E86AB.1050900@bennett.com>
Date: Mon, 13 Sep 2010 13:16:43 -0700
From: Richard Bennett <richard@bennett.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100825 Lightning/1.0b2 Thunderbird/3.1.3
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: Did Internet Founders Actually Anticipate Paid, Prioritized Traffic?
References: <20100913200339.572D16BE5D7@mercury.lcs.mit.edu>
In-Reply-To: <20100913200339.572D16BE5D7@mercury.lcs.mit.edu>
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz88.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bennett.com
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Sep 2010 20:16:23 -0000

The story I've heard from Vint Cerf about the TOS field is that it was put in for AUTODIN-II, a defense network that had multiple service levels to accommodate the requirements of interactive apps vs. bulk data apps. Jon Postel wrote RFC 795 - Service mappings on the mapping of TOS bits to service levels for ARPANET, PRNET, SATNET, and AUTODIN-II. AUTODIN-II never graduated from beta to production status. The Autodin story is told at , http://www.jproc.ca/crypto/autodin.html" rel="nofollow">http://www.jproc.ca/crypto/autodin.html

RB

On 9/13/2010 1:03 PM, Noel Chiappa wrote: 
    > From: todd glassey <tglassey@earthlink.net>

    > Why not simply ask Len Klienrock the answer to this question.

Umm, OK idea, wrong person: Len wasn't around the early Internet development.

I actually vaguely recall discussions about the TOS field (including how many
bits to give to each sub-field), but I can't recall very much of the content
of the discussions. If anyone cares, some of the IENs which document the early
meetings might say more.

Frankly, I doubt we understood the issues that well back then. Remember, this
was the same time period when we put in the 'Source Quench' ICMP message...

	Noel
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf" rel="nofollow">https://www.ietf.org/mailman/listinfo/ietf


-- 
Richard Bennett

v2.23.0 | Report a Bug | By Email