1 / 5

A process to change protocol specification in the (G)MPLS area draft-rtg-area-gmpls-change-00.txt

A process to change protocol specification in the (G)MPLS area draft-rtg-area-gmpls-change-00.txt. Loa Andersson ( loa@pi.se ) Adrian Farrel ( adrian@olddog.co.uk ). Status of the document. Old draft that were discussed on the mpls-list, from ADs and co-chairs at that time

cecil
Download Presentation

A process to change protocol specification in the (G)MPLS area draft-rtg-area-gmpls-change-00.txt

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. A process to change protocol specification in the (G)MPLS areadraft-rtg-area-gmpls-change-00.txt Loa Andersson (loa@pi.se) Adrian Farrel (adrian@olddog.co.uk) 61st IETF Washington DC November 2004

  2. Status of the document • Old draft that were discussed on the mpls-list, from ADs and co-chairs at that time • The current draft is available at:http://www.tla-group.com/~mpls/draft-andersson-rtg-(g)mpls-change-00-1.txt • However, did not make the cut-off • Outstanding comments, and will be updated shortly :) • (g)mpls ? 61st IETF Washington DC November 2004

  3. Issues to be Addressed • Defined process for changing (g)mpls protocols • interoperability • make the process known to other parties • Basic idea • Use the existing IETF process • requirements • wg charter • solution • standard • the draft describes how we will treat incoming proposals and the roles played by different parties in getting a working group chartered to work on requirements and solutions • Applicability • Protocols developed by (nn) working groups 61st IETF Washington DC November 2004

  4. Questions and Next Steps • Questions • Do we need this? • Should this be (g)mpls only? • Next Steps • Fill in details • Comments and contributions welcome 61st IETF Washington DC November 2004

  5. +-------+ +---------+ +---------+ | prob |discussion |review by| ACK | IESG | ACK | statem|---------->|wg chairs|------------->| IAB |-------+ | id |on mailing |and ad's | request to |decision | | +-------+ list +---------+ IESG/IAB to +---------+ | | appoint rewg | | | NAK and charter |NAK rewg | | req eval | chartered| | | to work| V | on prob| | statement| |response| | | |to the | | | |prob | <---------------+ | +->|statment| <-------------------+ | | +--------+ | | | ^ | | |NAK | NAK | | | +-----------------+ | V | | | NAK +-------+ +--------+ +-------+ +------| rewg | | IESG | ACK | AD | ACK | req | +-----------| IAB |<-------------- |review |<----------| eval | | wg |decision| request to | | | | |chartered +--------+ IESG/IAB to +-------+ +-------+ |to work approve wg |solution charter changes | +---------+ | | IETF | +--------->| WG |-----/ /----> RFC | process | +---------+ ^ | solutions ID 61st IETF Washington DC November 2004

More Related