Hi Hannu, Thanks for the comments.
> 1. Section 3.1 Improved routing scalability > > You talk about "the control plane", but it is unclear what is the > Internets control plane? RFC 1958 that was referred in section 2 doesn't > mention anything about the control plane. Is FIB in your definition on > control plane? So, do you think that the solution should support the > scalability of FIBs? RIB is in my opinion on the routing control plane? > But what about the DNS? Is flow control on the control plane that the > document addresses? Ok, thanks. I'll expand on this a bit. > 2. Section 3.4 Scalable support for mobility > > Is this document only about the global routing, and not applicable to > intra domain nor MANET type of routing? Maybe the context should be > defined somewhere, preferably in the introduction. Sure, we can expand on that. > I do not think that there is a consensus whether mobility is part of the > global routing system. Why should it be? Actually, it should not be. However, it is a function of the routing and addressing architecture. This is exactly the bug that we're trying to fix. > 3. Maybe section 3.10 Deployment > > I am wondering why the interdomain policy aspects have been left out. In > order to be incrementally deployable the current policy/business > relationships should be supported: customer, peering and transit > relationships. At least on the architecture level. Sure, worth mentioning. Tony _______________________________________________ rrg mailing list [email protected] http://www.irtf.org/mailman/listinfo/rrg
