![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
From: Stephen Wolff <steve at cise.nsf.gov> Date: Tue, 13 Feb 90 11:10:32 -0500 Subject: Re: Intra-AS Routing Standards The NSFNET Backbone needs a dual IS-IS because we are committed to being a dual protocol network. Our demo at Interop '89 was a signal. -s Steve, let's be sure we're using the same terms. You want to be able to route both IP and ISO packets. The approach Ross Callon has proposed, the so-called dual IS-IS, is to use (with restrictions) one routing protocol to support two protocol families, but it isn't necessary to do this to get your desired result. Saying you want to carry both types of traffic doesn't mean you have to fit support for doing so into one universal routing protocol. The way most implementors do this -- and they have been doing so for quite a while, with lots of different protocol families -- is to have a separate routing protocol module for each family, which satisfies your requirement just fine. Scott
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.