Return-Path: X-Original-To: pwe3@ietfa.amsl.com Delivered-To: pwe3@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47E1021F8617 for ; Tue, 8 May 2012 07:45:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.46 X-Spam-Level: X-Spam-Status: No, score=-6.46 tagged_above=-999 required=5 tests=[AWL=0.138, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uqrPm3ykWy2x for ; Tue, 8 May 2012 07:45:45 -0700 (PDT) Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 9BE3921F8603 for ; Tue, 8 May 2012 07:45:45 -0700 (PDT) Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q48Ejg0F031998; Tue, 8 May 2012 09:45:44 -0500 Received: from EUSAACMS0715.eamcs.ericsson.se ([169.254.1.10]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Tue, 8 May 2012 10:45:40 -0400 From: Gregory Mirsky To: Carlos Pignataro , "Bocci, Matthew (Matthew)" Date: Tue, 8 May 2012 10:45:39 -0400 Thread-Topic: [PWE3] Updates to goals and milestones Thread-Index: Ac0tIW9kVeMg5QsiQYaiirrWvE1QAgAB6/Uw Message-ID: References: <89CB9267-8CBD-479C-B74D-EC201434D893@cisco.com> In-Reply-To: <89CB9267-8CBD-479C-B74D-EC201434D893@cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_FE60A4E52763E84B935532D7D9294FF13552DBBA14EUSAACMS0715e_" MIME-Version: 1.0 Cc: "pwe3@ietf.org" Subject: Re: [PWE3] Updates to goals and milestones X-BeenThere: pwe3@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Pseudo Wires Edge to Edge List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 May 2012 14:45:48 -0000 --_000_FE60A4E52763E84B935532D7D9294FF13552DBBA14EUSAACMS0715e_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Matthew, concur with Carlos, it's the right way. Regards, Greg ________________________________ From: Carlos Pignataro [mailto:cpignata@cisco.com] Sent: Tuesday, May 08, 2012 6:50 AM To: Bocci, Matthew (Matthew) Cc: Gregory Mirsky; pwe3@ietf.org Subject: Re: [PWE3] Updates to goals and milestones Matthew, I agree, sounds like a good approach. Thanks, -- Carlos. On May 8, 2012, at 6:19 AM, Bocci, Matthew (Matthew) wrote: Greg, Carlos, I think this milestone started life as referring to any PW OAM extensions r= equired for MPLS-TP. However, it has become very ambiguous. There are reall= y a number of objectives that we should capture, including at least the fol= lowing: * Additional VCCV Channel Type using the GAL * VCCV capability negotiation for MPLS-TP OAM tools. * Rationalisation of VCCV (RFC5085bis) I think we could replace this milestone with milestones for the above. Regards Matthew On 04/05/2012 20:53, "Gregory Mirsky" > wrote: Dear Matthew, Carlos, et al., I agree with Carlos that updates to VCCV Control Channels resulting from di= scussion of GAL as Type 4 VCCV CC, perhaps as RFC5085bis, can be captured i= n Milestones. But I think that this work not necessarily tied with CV capab= ility extension that, I think, referenced as "Enhanced PW OAM". Regards, Greg ________________________________ From: pwe3-bounces@ietf.org [mailto:pwe3-boun= ces@ietf.org] On Behalf Of Carlos Pignataro (cpignata) Sent: Friday, May 04, 2012 4:38 AM To: Bocci, Matthew (Matthew) Cc: pwe3@ietf.org Subject: Re: [PWE3] Updates to goals and milestones Matthew, In Paris there was discussion (and subsequent followup) about a VCCV-bis do= cument. I am not sure if a formal consensus call was issued on that, but I = wonder if it needs to be captured as a milestone (or how it relates to "Enh= anced PW OAM"). Thumb typed by Carlos Pignataro. Excuze typofraphicak errows On May 4, 2012, at 6:39 AM, "Bocci, Matthew (Matthew)" > wrote: All, Please find below a proposed list of updates to the WG goals and milestones= that was presented in Paris, with one modification pushing the P2MP Requir= ements LC back to Dec 2012. Please post any comments to the list before Friday 11th May. Matthew Done - PWE3 WG started, organize editing teams. Done - Hold interim meeting, including discussion of priority of serv= ice-specific documents and consider pruning some deliverables Done - Accept drafts of service-specific documents as WG items Done - PW Requirements Document Last Call Done - TDM Circuit Documents Last Call Done - ATM Documents Last Call Done - Ethernet Documents Last Call Done - Fragmentation LC Done - TDM Requirements LC Done - SONET Documents Last Call Done - TDM Documents Last Call Done - Frame Relay Documents Last Call Done - FCS retention Last Call Done - Multi-Segment PW Requirements LC Done - VCCV LC Done - PWE3 Services MIBs LC Done - PPP/HDLC PW LC Done - Wildcard FEC LC Done - TDM Signaling LC Done- Multi-Segment Architecture LC Done - Basic Pseudowire MIBs LC Done - PW OAM Mapping LC Done - Multi-Segment PW LC Done - PW Protection and Restoration Requirements LC Done - PW Protection and Restoration Architecture Done - Generic Associated Channel Header LC Done - PW Protection and Restoration LC Done - Fiber Channel Encap LC Done- Multipath PW LC Done - Packet PW Requirements / solution Dec 2012- P2MP Requirements LC Done - PW Status signalling in static/MPLS-TP July 2012 - Dynamic MS PW LC Sept 2012- Enhanced PW OAM Sept 2011 - Signaling extensions for MPLS-TP OAM Dec 2012- Multisegment PW MIB Dec 2012- Security Considerations LC Dec 2012- Congestion Considerations Dec 2012- P2MP PW Signaling (root initiated) Dec 2012- P2MP PW Signaling (leaf initiated) _______________________________________________ pwe3 mailing list pwe3@ietf.org https://www.ietf.org/mailman/listinfo/pwe3 --_000_FE60A4E52763E84B935532D7D9294FF13552DBBA14EUSAACMS0715e_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hi Matthew,
concur with Carlos, it's the right way.
 
    Regards,
      &= nbsp;=20 Greg
From: Carlos Pignataro=20 [mailto:cpignata@cisco.com]
Sent: Tuesday, May 08, 2012 6:50=20 AM
To: Bocci, Matthew (Matthew)
Cc: Gregory Mirsky;=20 pwe3@ietf.org
Subject: Re: [PWE3] Updates to goals and=20 milestones

Matthew,

I agree, sounds like a good approach.

Thanks,

-- Carlos.

On May 8, 2012, at 6:19 AM, Bocci, Matthew (Matthew) wrote:
Greg, Carlos,

I think this milestone started life as referring to any PW OAM exten= sions=20 required for MPLS-TP. However, it has become very ambiguous. There are re= ally=20 a number of objectives that we should capture, including at least the=20 following:

  • Additional VCCV Channel Type using the GAL
  • VCCV capability negotiation for MPLS-TP OAM tools.
  • Rationalisation of VCCV (RFC5085bis)

I think we could replace this milestone with milestones for the=20 above.

Regards

Matthew

On 04/05/2012 20:53, "Gregory Mirsky" <gregory.mirsky@ericsson.com>=20 wrote:

Dear Matthew, Carlos, et al.,
I agree with Carlos that updates to VCCV Contr= ol=20 Channels resulting from discussion of GAL as Type 4 VCCV CC, perhaps as= =20 RFC5085bis, can be captured in Milestones. But I think that this work n= ot=20 necessarily tied with CV capability extension that, I think,= =20 referenced as "Enhanced PW OAM".
 
    Regards,
       =20 Greg
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org]= On=20 Behalf Of Carlos Pignataro (cpignata)
Sent: Friday, May 0= 4,=20 2012 4:38 AM
To: Bocci, Matthew (Matthew)
Cc: pwe3@ietf.org
Subject: Re: = [PWE3]=20 Updates to goals and milestones

Matthew,

In Paris there was discussion (and subsequent followup) about a=20 VCCV-bis document. I am not sure if a formal consensus call was issued = on=20 that, but I wonder if it needs to be captured as a milestone (or how it= =20 relates to "Enhanced= =20 PW OAM"). 

Thumb=20 typed by Carlos Pignataro.
Excuze=20 typofraphicak errows

On May 4, 2012, at 6:39 AM, "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-= lucent.com>=20 wrote:

All,

Please find below a= =20 proposed list of updates to the WG goals and milestones that was pres= ented=20 in Paris, with one modification pushing the P2MP Requirements LC back= to=20 Dec 2012.

Please post any com= ments=20 to the list before Friday 11th May.

Matthew

 Done   &nbs= p; -=20 PWE3 WG started, organize editing teams.

 =20 Done     - Hold interim meeting, including discus= sion=20 of priority of service-specific documents and consider pruning some deliverables  =20 Done     - Accept drafts of service-specific docu= ments=20 as WG items

 =20 Done     - PW Requirements Document Last=20 Call

 =20 Done     - TDM Circuit Documents Last Call=

 =20 Done     - ATM Documents Last Call

 =20 Done     - Ethernet Documents Last Call  =20 Done     - Fragmentation LC

 =20 Done     - TDM Requirements LC

 =20 Done     - SONET Documents Last Call

 =20 Done     - TDM Documents Last Call

 =20 Done     - Frame Relay Documents Last Call=

 =20 Done     - FCS retention Last Call

 =20 Done     - Multi-Segment PW Requirements LC

 =20 Done     - VCCV LC

  Done    = - PWE3=20 Services MIBs LC

 =20 Done     - PPP/HDLC PW LC

 =20 Done     - Wildcard FEC LC

  Done     - TDM Signaling LC

  Done- Multi-Segment Architecture= =20 LC

  Done     - Ba= sic=20 Pseudowire MIBs LC

  Done - PW OAM Mapping LC   Done - Multi-Segment PW LC=

 = =20 Done - PW Protection= and=20 Restoration Requirements LC

  Done - PW Protection and Restorat= ion=20 Architecture

  Done - Generic Associated Channel= Header=20 LC

  Done - PW Protection and Restoration=20 LC

  Done - Fiber=20 Channel Encap LC

  Done- Multipath PW LC

  Done  -=20 Packet PW Requirements / solution

  Dec  2012  Done  –=20 PW Status signalling in static/MPLS-TP

  July 2012=20 - Dynamic MS PW LC   Sept 2012  Sept 2011 – Signaling extensions for MPLS-TP OAM

  Dec 2012Multisegment PW MIB

  Dec 2012  Dec 2012 Dec  2012Signaling (root=20 initiated)

 Dec 2012Signaling (leaf initiated)

=
_______________________________________________
= pwe3=20 mailing list
pwe3@ietf.org
https://www.ietf.= org/mailman/listinfo/pwe3

--_000_FE60A4E52763E84B935532D7D9294FF13552DBBA14EUSAACMS0715e_--