Re: [Mpls-interop] moving mpls-tp documents - you are supposed torespond

["BUSI ITALO" <[e-mail]>]

By when are you expecting us to reply to the "accept as a MEAD team doc"
question?

Thanks and have a nice week-end

Italo 

> -----Original Message-----
> From: [e-mail] 
> [mailto:[e-mail]] On Behalf Of Loa Andersson
> Sent: Friday, January 23, 2009 4:57 PM
> To: MEAD team
> Subject: [Mpls-interop] moving mpls-tp documents - you are 
> supposed torespond
> 
> 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:  [phone]
> 
>                                        email:  
> [e-mail]
>                                                
> [e-mail]
>                                                [e-mail]
> 
> 
> _______________________________________________
> Mpls-interop mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/mpls-interop
> 
_______________________________________________
Mpls-interop mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/mpls-interop