![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Steve, being multi-protocol doesn't imply dual IS-IS. NSN carries both IP and DECNET now without having a single routing protocol doing the work. We find this approach to work well. I'm working on a fairly long message that describes why I think dual IS-IS is in general a bad idea, though that doesn't mean it wouldn't be a good fit for the NSFNET backbone. There are lots of ways of skinning the multi-protocol cat. You could run one IS-IS for IP and another IS-IS for 8473. This avoids any coupling between the 2 protocols metrics, areas, etc... Thanks, Milo
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.