![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
There is a very important point that there wasn't time for me to make at the open IESG meeting. We should not be comparing OSPF and dual IS-IS. Rather, IS-IS for IP for be examined in it's own right. Remember, nobody has asked for a routing protocol which handles IP *and* DECnet; yet, there are routers which handle both. As I (and I mean me personally) see it, the natural progression is for OSPF to become the standard routing protocol for IP (always assuming that it doesn't barf in the field tests) because it will be available first. Vendors will be implementating IS-IS anyway because they'll need it for their ISO stacks. After some period of time, the user community may decide that one protocol is sufficiently superior another to warrent pressuring vendors to supply that protocol for both stacks; and eventually, possibly, as a dual protocol. Make sense? Gary
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.