The MPLS WG Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] GMPLS features applicable to MPLS
Ping, You make a good point. This discussion is about document organization. Nothing earth shattering. This would not be important except that in some ways the world has changed. No longer do we have only a handful of implementations of a particular protocol - all being done by folks who work in 2 or 3 companies. Protocols are being implemented by an increasing number of companies with development in many parts of the world other than North America. Having well organized content simply makes lives easier for future developers. In this particular case, it also has clear implications on $ and code creep - see my previous email. Ideally, the Hitless Restart content & Unnumbered Links content should have remained separate content applicable to MPLS. Otherwise the next best compromise is an applicability statement draft. Best, Nabil Ping Pan wrote: > > Hmmm... have to bite now. Who is confused here? The carriers? Don't > think so. They know exactly which feature to have in their networks. The > developers? Don't think so either. They know what can and cannot be > implemented. So if we have enough solutions floating around in various > drafts and RFC's. Why write more document? > > - Ping
|
|