Re: PROs/CONs of SIP/PIP/TUBA

Tony Whyman <whyman@mwassocs.demon.co.uk> Tue, 18 May 1993 11:06 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00888; 18 May 93 7:06 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id ac00876; 18 May 93 7:06 EDT
Received: from thumper.bellcore.com by CNRI.Reston.VA.US id aa00943; 18 May 93 5:00 EDT
Received: by thumper.bellcore.com (4.1/4.7) id <AA21259> for eric@isci.com; Tue, 18 May 93 03:36:34 EDT
Received: from mwassocs.demon.co.uk by thumper.bellcore.com (4.1/4.7) id <AA21246> for /usr/lib/sendmail -oi -fowner-pip X-pip; Tue, 18 May 93 03:35:55 EDT
Date: Tue, 18 May 93 08:29:45 BST
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Tony Whyman <whyman@mwassocs.demon.co.uk>
Message-Id: <1439.whyman@mwassocs.demon.co.uk>
To: Day@bbn.com
Cc: pip@thumper.bellcore.com, caldera.usc.edu@mwassocs.demon.co.uk, tuba@lanl.gov
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
Reply-To: whyman@mwassocs.demon.co.uk
Subject: Re: PROs/CONs of SIP/PIP/TUBA
X-Mailer: VE3PZR VIEW DIS V1.01.
Lines: 29

John,

In your reply to Eric Fleischman, there's a point which I think should be 
developed further:


> >                                 SIP Con
> >
> >1)  Since hierarchical addresses tend to be deployed in a "sparse" manner,
> >it unclear whether a 64 bit address space will adequately scale to meet
> >every conceivable future addressing scenario.
> 
> It is pretty clear that any fixed length will never be enough.

This is a very significant issue as regards IPng selection and should be taken 
up on the "criteria" list. Built-in obsolescence should no longer be an 
acceptable feature of a communications protocol.




-- 
Tony Whyman             McCallum Whyman Associates Ltd  Tel +44 962 735580
                                                        FAX +44 962 735581
                        Internet: whyman@mwassocs.demon.co.uk
                        Compuserve: 100041,315