MPLS Forwarding Compliance and Performance Requirements
draft-ietf-mpls-forwarding-09

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: RFC Editor <rfc-editor@rfc-editor.org>,
    mpls mailing list <mpls@ietf.org>,
    mpls chair <mpls-chairs@tools.ietf.org>
Subject: Document Action: 'MPLS Forwarding Compliance and Performance Requirements' to Informational RFC (draft-ietf-mpls-forwarding-09.txt)

The IESG has approved the following document:
- 'MPLS Forwarding Compliance and Performance Requirements'
  (draft-ietf-mpls-forwarding-09.txt) as Informational RFC

This document is the product of the Multiprotocol Label Switching Working
Group.

The IESG contact persons are Adrian Farrel and Stewart Bryant.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-mpls-forwarding/


Technical Summary

      This document provides guidelines for implementers regarding MPLS
      forwarding and a basis for evaluations of forwarding implementations.
      Guidelines cover many aspects of MPLS forwarding.  Topics are
      highlighted where implementers might otherwise overlook practical
      requirements which are unstated or under emphasized or are optional
      for conformance to RFCs but are often considered mandatory by
      providers.

Working Group Summary

      This document has been discussed by the working group both on the
      mailing list and at a long slot at the working meeting in Vancouver.

      The working group is behind this document, there has been no mayor
      controversies and very good discussions.

Document Quality

      The question about implementations is a bit tricky - there are no
      implementations based on the document, as there were existing 
      implementations when the document was started up. Instead it is the 
      other  way around, the document discusses implementation and 
      deployment experiences. All the scenarios discussed in the document
      have been implemented and/or deployed.

      The document is Informational and no MIB Doctor, Media type or other
      other types of expert reviews have been necessary.
       
Personnel

      Loa Andersson, is the document Shepherd.
      Adrian Farrel is the Responsible AD