AS4bytes old and new
"Tom Petch" <nwnetworks@dial.pipex.com> Fri, 11 January 2002 15:56 UTC
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id KAA11012 for <idr-archive@nic.merit.edu>; Fri, 11 Jan 2002 10:56:07 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix) id 2636F91288; Fri, 11 Jan 2002 10:54:45 -0500 (EST)
Delivered-To: idr-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56) id 2CD839128F; Fri, 11 Jan 2002 10:54:43 -0500 (EST)
Delivered-To: idr@trapdoor.merit.edu
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by trapdoor.merit.edu (Postfix) with ESMTP id 7F36A9128B for <idr@trapdoor.merit.edu>; Fri, 11 Jan 2002 10:54:37 -0500 (EST)
Received: by segue.merit.edu (Postfix) id AFF325DF4F; Fri, 11 Jan 2002 10:54:37 -0500 (EST)
Delivered-To: idr@merit.edu
Received: from hose.mail.pipex.net (hose.mail.pipex.net [158.43.128.58]) by segue.merit.edu (Postfix) with SMTP id E855C5DF4B for <idr@merit.edu>; Fri, 11 Jan 2002 10:54:36 -0500 (EST)
Received: (qmail 8341 invoked from network); 11 Jan 2002 15:54:27 -0000
Received: from useraq84.uk.uudial.com (HELO tom3) (62.188.136.144) by smtp-4.dial.pipex.com with SMTP; 11 Jan 2002 15:54:27 -0000
Message-ID: <007a01c2b989$a4753cc0$c490bc3e@tom3>
Reply-To: Tom Petch <nwnetworks@dial.pipex.com>
From: Tom Petch <nwnetworks@dial.pipex.com>
To: idr@merit.edu
Subject: AS4bytes old and new
Date: Sat, 11 Jan 2003 14:10:35 -0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Sender: owner-idr@merit.edu
Precedence: bulk
Near me is a town called Newtown; reasonable as it is only 700 years old :-) but it does confuse people even after all these years. I think the use of Old and New in the 4byte AS draft will cause similar confusion in the not too distant future and we should come up with an absolute term to differentiate them rather than a relative term that may soon be obsolete. If you want to see an example of how not to do it, look at SCSI terminology; narrow, wide, ultra-wide, ultra2, really wide, ultra160, ... Tom Petch, Network Consultant nwnetworks@dial.pipex.com
- AS4bytes old and new Tom Petch