Re: making Noel happy......
Paul Tsuchiya <tsuchiya@thumper.bellcore.com> Tue, 02 March 1993 21:36 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08854;
2 Mar 93 16:36 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa08850;
2 Mar 93 16:36 EST
Received: from thumper.bellcore.com by CNRI.Reston.VA.US id aa22964;
2 Mar 93 16:36 EST
Received: by thumper.bellcore.com (4.1/4.7)
id <AA06055> for ietf-archive@nri.reston.va.us; Tue, 2 Mar 93 16:34:04 EST
Received: from chiya.bellcore.com by thumper.bellcore.com (4.1/4.7)
id <AA06043> for /usr/lib/sendmail -oi -fowner-pip X-pip;
Tue, 2 Mar 93 16:34:01 EST
Received: by chiya.bellcore.com (4.1/4.7)
id <AA01247> for tsuchiya@thumper.bellcore.com; Tue, 2 Mar 93 16:10:57 EST
Date: Tue, 2 Mar 93 16:10:57 EST
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Paul Tsuchiya <tsuchiya@thumper.bellcore.com>
Message-Id: <9303022110.AA01247@chiya.bellcore.com>
To: jnc@ginger.lcs.mit.edu, pip@thumper.bellcore.com,
tsuchiya@thumper.bellcore.com
Subject: Re: making Noel happy......
> > Now, (I hope), Noel won't say anymore "Pip is > a protocol without an architecture....." :-) > > What Noel said (to be precise) is that X,Y,Z and PIP didn't have *routing > architectures*. (For my definition of this term, please refer to the Big-I > archives.) There's a big difference. Sorry, I meant routing architecture when I said architecture.... :-) > > Noel > > PS: As near as I can tell from a quick scan of sections 4 and 10, PIP now > has rudiments of an RA, but not one I am enthused about. > I'm not surprised. Except for adding provider selection, the initial (near-term) Pip routing architecture is plain old vanilla hierarchical addresses...... PX
- making Noel happy...... Paul Tsuchiya
- Re: making Noel happy...... Noel Chiappa
- Re: making Noel happy...... Paul Tsuchiya
- Re: making Noel happy...... Noel Chiappa