1 / 4

MPLS-TP Process draft-ietf-mpls-tp-process-03

This document outlines the MPLS-TP process draft, highlighting the need for familiarizing MPLS-TP stakeholders with IETF processes. It emphasizes cooperation between IETF and ITU-T as stipulated in the JWT report, ensuring mutual review of work. Key points include adapting the IETF processes to involve ITU-T participants, defining liaison points, and clarifying the relationship between IETF and ITU-T documentation. The draft aims to maintain an updated document, facilitate referencing of Informational RFCs, and ultimately publish it as a Historic RFC.

webb
Télécharger la présentation

MPLS-TP Process draft-ietf-mpls-tp-process-03

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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>

  2. 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

  3. 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

  4. 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

More Related