40 likes | 160 Views
MPLS-TP Process draft-ietf-mpls-tp-process-03. Loa Andersson <loa.andersson@ericsson.com> Dave Ward <dward@cisco.com> Malcolm Betts <malcolm.betts@huawei.com> Adrian Farrel <adrian.farrel@huawei.com>. Why write a Process draft?.
E N D
MPLS-TP Processdraft-ietf-mpls-tp-process-03 Loa Andersson <loa.andersson@ericsson.com> Dave Ward <dward@cisco.com> Malcolm Betts <malcolm.betts@huawei.com> Adrian Farrel <adrian.farrel@huawei.com>
Why write a Process draft? • Many people involved in MPLS-TP are not familiar with IETF processes • This is a cooperation project • As agreed in the JWT report • ITU-T must review IETF work • IETF must review ITU-T work • Need to understand how that works • Need a common understanding of expectations
What does it say? • No change to normal IETF processes • “Adaptation” to show how ITU-T participants are involved • Points in the process where liaisons will be sent • Points at which liaison responses are required • Simple explanation of normal IETF process and mailing lists
What are the plans? • Include boilerplate text • Clarify the cooperative source of documents • Ensure that Informational RFCs can be referenced • Currently visible at http://wiki.tools.ietf.org/misc/mpls-tp/ • Keep document up-to-date • Finally publish as Historic RFC? • How does the IEFT contribute to ITU-T Recommendations? • Separate draft being written (Stewart Bryant and Adrian Farrel) • Based on material from ITU-T • Liaison received in May • Discussions face-to-face in Geneva in October • MPLS-TP Steering Group • Continued monitoring of cooperation process by IETF and ITU-T management