I wonder if the direction of Section 1.2 can be revised to make it more of an engineering document. It currently says: In recent years, the urgency for moving from traditional transport technologies, such as SONET/SDH, TDM, and ATM, to new packet technologies has been rising. This is largely due to the fast growing demand for bandwidth, which has been fueled by the following factors: ... Please consider an approach that describes the the reasons behind the transition from the network operator and network user perspectives: Traditional transport technologies include SONET/SDH, TDM, and ATM. There is a transition away from these transport technologies to new packet technologies. In addition to the ever increasing demand for bandwidth, the packet technologies offer these advantages: ... The fact that IP networks are being used for new applications and that the legacy devices are getting old does not motivate the transition to packet technologies. The advantages that packet technologies offer for these new applications is the thing that needs to be highlighted here, even if it is just a list of bullets. It seems like the only sentence that addresses this point in Section 1.2 is: "It streamlines the operation, reduces the overall complexity, and improves end-to-end convergence." Thanks, Russ On Jan 28, 2013, at 3:01 PM, The IESG wrote: > The IESG has received a request from the Multiprotocol Label Switching WG > (mpls) to consider the following document: > - 'MPLS-TP Applicability; Use Cases and Design' > <draft-ietf-mpls-tp-use-cases-and-design-06.txt> as Informational RFC > > The IESG plans to make a decision in the next few weeks, and solicits > final comments on this action. Please send substantive comments to the > ietf@xxxxxxxx mailing lists by 2013-02-11. Exceptionally, comments may be > sent to iesg@xxxxxxxx instead. In either case, please retain the > beginning of the Subject line to allow automated sorting. > > Abstract > > This document provides applicability, use case studies and network > design considerations for the Multiprotocol Label Switching Transport > Profile (MPLS-TP). The use cases include Metro Ethernet access and > aggregation transport, Mobile backhaul, and packet optical transport. > > The file can be obtained via > http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-use-cases-and-design/ > > IESG discussion can be tracked via > http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-use-cases-and-design/ballot/ > > > No IPR declarations have been submitted directly on this I-D.