![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Stev: The NSFNET backbone has extensive experience with the ANSI IS-IS protocol. I heard a statement from IBM before that they would conform to the IS-IS document that the IETF IS-IS Working Group is working on. Given that we would also like to support CLNP sooner or later I assume that Steve Wolff meant that we can expand the existing almost two years of IS-IS experience in the NSFNET backbone towards some experience in an environment where we could use IS-IS for multiple datagram-style protocols. It is true that the NSFNET backbone IS-IS implementation is only a subset of the full ANSI IS-IS spec. However, please note that the reason for that was that there was no need for the NSFNET backbone support itself to implement more than this subset. Steve (Wolff), please correct me if I misrepresented what you had in mind. -- Hans-Werner
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.