[Mpls-interop] moving mpls-tp documents - you are supposed to respond

Loa Andersson <loa@pi.nu> Fri, 23 January 2009 15:57 UTC

Return-Path: <mpls-interop-bounces@ietf.org>
X-Original-To: mpls-interop-archive@ietf.org
Delivered-To: ietfarch-mpls-interop-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 59D543A67F2; Fri, 23 Jan 2009 07:57:46 -0800 (PST)
X-Original-To: mpls-interop@core3.amsl.com
Delivered-To: mpls-interop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4B6A83A6ABF for <mpls-interop@core3.amsl.com>; Fri, 23 Jan 2009 07:57:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level:
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[AWL=-0.052, BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6q5xiP9k5yEP for <mpls-interop@core3.amsl.com>; Fri, 23 Jan 2009 07:57:40 -0800 (PST)
Received: from ns.elverljung.se (ns.elverljung.se [194.68.48.116]) by core3.amsl.com (Postfix) with ESMTP id BE0DC3A67F2 for <mpls-interop@ietf.org>; Fri, 23 Jan 2009 07:57:39 -0800 (PST)
Received: from [172.31.253.82] (dmz-emmb.redback.com [155.53.1.254]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa) by ns.elverljung.se (Postfix) with ESMTPSA id B0CCB2D840B for <mpls-interop@ietf.org>; Fri, 23 Jan 2009 16:57:19 +0100 (CET)
Message-ID: <4979E8D9.8060904@pi.nu>
Date: Fri, 23 Jan 2009 16:57:13 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: MEAD team <mpls-interop@ietf.org>
Subject: [Mpls-interop] moving mpls-tp documents - you are supposed to respond
X-BeenThere: mpls-interop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF MPLS Interoperability Design Team <mpls-interop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-interop>, <mailto:mpls-interop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls-interop>
List-Post: <mailto:mpls-interop@ietf.org>
List-Help: <mailto:mpls-interop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-interop>, <mailto:mpls-interop-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mpls-interop-bounces@ietf.org
Errors-To: mpls-interop-bounces@ietf.org All,

I'll to try push the next round of documents to wg last call,
or have them accepted as wg documents asap. The discussions in
Ipswich gave a of input that should be captured in several
documents.

This also means that we need to to have a couple of documents
become wg documents. Here are the steps we need to take:

draft-andersson-mpls-tp-oam-def       (accept as a MEAD team doc?)  	
draft-beller-mpls-tp-gach-dcn 	      (accept as a MEAD team doc?)
draft-boutros-mpls-tp-cv              (accept as a MEAD team doc?)
  	
draft-boutros-mpls-tp-fault           (accept as a MEAD team doc?) 	
draft-boutros-mpls-tp-loopback 	      (comments and review need!) 	
draft-boutros-mpls-tp-performance     (accept as a MEAD team doc?)
  	
draft-bryant-mpls-tp-ach-tlv          (accept as a MEAD team doc?) 	
draft-busi-mpls-tp-oam-framework      (update based on Ipswich
                                        discussion!) 	
draft-gray-mpls-tp-nm-req             (accept as a wg doc!)

draft-ietf-mpls-tp-framework          (prepare for a wg last call, after
                                        the tp-requirements are wg last
                                        called)
draft-ietf-mpls-tp-oam-requirements   (we need to get existing comments
                                        written down, we will allow until
                                        Friday Jan 30 to do this, after
                                        that we'll prepare the doc for wg
                                        last call)
draft-ietf-mpls-tp-requirements       (prepare for wg last call)

draft-martinotti-mpls-tp-interworking (accept as a MEAD team doc?) 	
draft-sprecher-mpls-tp-oam-analysis   (update as soon as the
                                        oam-requirements are stable)
draft-sprecher-mpls-tp-survive-fwk    (document has expired and should
                                        be republished)

draft-yang-mpls-tp-ring-protection
-analysis                             (accept as a MEAD team doc?)

As a member of the MEAD team you are expected to respond to the
"accept as a MEAD team doc"?

As a a MEAD team member you are expected to supply your comments on
draft-ietf-mpls-tp-oam-requirements on Fri Jan 30, the latest.

As an editor you are supposed to take the action (when the time is
right) for the other document.

A reminder:

Becoming a MEAD team document means that there a strong element
in that draft that the MEAD needs to coordinate, it won't stop
us from splitting or merge documents, just that we will do so
in a coordinated way.

Becoming wg documents means positive response to three questions.

- does this document address a problem that the wg needs to
   solve
- is this document a good enough start to solve this problem
- is it within wg charter

/Loa


-- 


Loa Andersson

Sr Strategy and Standards Manager
Ericsson ///                          phone:  +46 8 632 77 14

                                       email:  loa.andersson@ericsson.com
                                               loa.andersson@redback.com
                                               loa@pi.nu


_______________________________________________
Mpls-interop mailing list
Mpls-interop@ietf.org
https://www.ietf.org/mailman/listinfo/mpls-interop