IETF Logo Mail Archive

Future IGPs

yakov@watson.ibm.com Thu, 14 April 1994 13:37 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03826; 14 Apr 94 9:37 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa03822; 14 Apr 94 9:37 EDT
Received: from murtoa.cs.mu.OZ.AU by CNRI.Reston.VA.US id aa07303; 14 Apr 94 9:37 EDT
Received: from mailing-list by murtoa.cs.mu.OZ.AU (8.5/1.0) id XAA22904; Thu, 14 Apr 1994 23:31:19 +1000
Received: from munnari.oz.au by murtoa.cs.mu.OZ.AU (8.5/1.0) with SMTP id XAA22855; Thu, 14 Apr 1994 23:06:17 +1000
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: yakov@watson.ibm.com
Received: from watson.ibm.com by munnari.oz.au with SMTP (5.83--+1.3.1+0.50) id AA12544; Thu, 14 Apr 1994 22:01:22 +1000 (from yakov@watson.ibm.com)
Message-Id: <9404141201.12544@munnari.oz.au>
Received: from YKTVMV by watson.ibm.com (IBM VM SMTP V2R3) with BSMTP id 1107; Thu, 14 Apr 94 08:01:20 EDT
Date: Thu, 14 Apr 1994 08:00:12 -0400
To: tli@cisco.com
Cc: bound@zk3.dec.com, big-internet@munnari.oz.au
Subject: Future IGPs

Ref:  Your note of Wed, 13 Apr 1994 21:07:56 -0700


Tony,

>Thus, for IDRP, we can carry around a GOSIP format NSAP and a SIPP
>address with impunity..

That is correct. Folks who doubt this, should consider reading
IDRP for IP Internet Draft (draft-hares-idrp-05.txt) and IDRP
for SIP Internet Draft (draft-ietf-ipidrp-sip-01.txt).

>So, for example, adding IPng support to IDRP consists of defining
>one new attribute and saying "well, addresses of type 57 will be
>IPng addresses". That's IT. Done.

Actually for IDRP you DON'T need to define ANY NEW attributes.
You just need to specify the protocol type of the the Network Layer
Reachability Information you carry (e.g. IPv4 has protocol type X,
SIPP has protocol type Y, etc...). So, it is even simpler than you described.

Yakov.

v2.23.0 | Report a Bug | By Email