![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
>As someone from Proteon or cisco already mentioned, their boxes currently >run lots of protocols on the same collections of wires. Each protocol >has its own routing protocol. The protocols all "work together" by being >blissfully unaware of each other. >Again, maybe I don't understand. yes- i agree this is all too vague. a. you have wires carrying multiple (link+net) protocols b. you have routes these protocols allow c. you have multiple routing info exchange protocols which also run over these wires a+b+c => 1. you can reduce to one routing info exchange protocol, 2. you can reduce further to one set of routes common to all (link+net) protocols (3. you could run the same routing exchange protocols but with different addr spaces run different route calculation/algorithms - though that sounds like asking for trouble) 1. may be desirable to reduce the number of copmplex things like routing algorithms etc to worry about 2. may not be desirable, since different (link+net) protocols may have different effects and so on on nets by the way, my belief is we will want explicitly 1 and not 2 for the future uk-US connections. have i got this right? jon
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.