RE: [PWE3] PW Redundancy to WG drafts?

"AISSAOUI Mustapha" <Mustapha.Aissaoui@alcatel-lucent.com> Mon, 17 December 2007 16:27 UTC

Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4IoG-0001d8-Q1; Mon, 17 Dec 2007 11:27:16 -0500
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43) id 1J4IoF-0001cv-Om for pwe3-confirm+ok@megatron.ietf.org; Mon, 17 Dec 2007 11:27:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4IoF-0001ch-1e for pwe3@ietf.org; Mon, 17 Dec 2007 11:27:15 -0500
Received: from audl751.usa.alcatel.com ([143.209.238.164]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J4IoC-0007Ei-QC for pwe3@ietf.org; Mon, 17 Dec 2007 11:27:15 -0500
Received: from usdalsbhs02.ad3.ad.alcatel.com (usdalsbhs02.usa.alcatel.com [172.22.216.13]) by audl751.usa.alcatel.com (ALCANET) with ESMTP id lBHGRBVB019824; Mon, 17 Dec 2007 10:27:11 -0600
Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.7]) by usdalsbhs02.ad3.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Mon, 17 Dec 2007 10:26:44 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] PW Redundancy to WG drafts?
Date: Mon, 17 Dec 2007 10:26:43 -0600
Message-ID: <4A5028372622294A99B8FFF6BD06EB7B03C7CBAC@USDALSMBS03.ad3.ad.alcatel.com>
In-Reply-To: <007b01c840c7$87f32e70$c1922799@mcilink.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [PWE3] PW Redundancy to WG drafts?
Thread-Index: AchApGVoiwC8XswAQUay+u+h/sThVQAGvPUwAAG4s+AAAJ2sAA==
References: <0JSY00A19TTYIL@ntt.com> <476664B4.40703@cisco.com> <4A5028372622294A99B8FFF6BD06EB7B03C7CB94@USDALSMBS03.ad3.ad.alcatel.com> <007b01c840c7$87f32e70$c1922799@mcilink.com>
From: AISSAOUI Mustapha <Mustapha.Aissaoui@alcatel-lucent.com>
To: Dave McDysan <dave.mcdysan@verizon.com>, stbryant@cisco.com, pwe3@ietf.org
X-OriginalArrivalTime: 17 Dec 2007 16:26:44.0395 (UTC) FILETIME=[9CD63FB0:01C840C9]
X-Scanned-By: MIMEDefang 2.51 on 143.209.238.34
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Cc:
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

Dave,
sure, let us incorporate your scenarios into the framework document. We
can then evaluate if these can be addressed by capabilities currently
defined the solution draft or not.

Mustapha.

> -----Original Message-----
> From: Dave McDysan [mailto:dave.mcdysan@verizon.com] 
> Sent: Monday, December 17, 2007 11:12 AM
> To: AISSAOUI Mustapha; stbryant@cisco.com; pwe3@ietf.org
> Subject: RE: [PWE3] PW Redundancy to WG drafts?
> 
> The charter states the following:
> 
> "Define requirements for and mechanisms to provide protection 
> and restoration of PWs."
> 
> I view draft-muley-pwe3-redundancy-02.txt that describes 
> scenarios as a good starting point to document requirements, 
> which can be combined with a framework (if the wg wants to 
> undertake that increased charter scope). 
> 
> I support these documents becoming WG drafts so that they can 
> be open to inputs from the working group. 
> 
> As I mentioned in the meeting, I have additional requirements 
> and scenarios that I would like for the wg to consider.
> 
> Thanks,
> 
> Dsve
> > -----Original Message-----
> > From: AISSAOUI Mustapha 
> [mailto:Mustapha.Aissaoui@alcatel-lucent.com]
> > Sent: Monday, December 17, 2007 10:56 AM
> > To: stbryant@cisco.com; pwe3@ietf.org
> > Subject: RE: [PWE3] PW Redundancy to WG drafts?
> > 
> > Stewart,
> > I believe all of the requirements we received from service 
> providers 
> > and vendors were incorporated into the scenarios described in the 
> > framework draft and addressed by the solution draft. In my opinion, 
> > this reflects the level of support for moving these two 
> documents to 
> > WG status.
> > 
> > Having said that, if the WG requires a separate 
> requirements document, 
> > we can work on separating them from the framework draft but this 
> > should not delay these drafts from progressing as WG documents.
> > 
> > Regards,
> > Mustapha.
> > 
> > > -----Original Message-----
> > > From: Stewart Bryant [mailto:stbryant@cisco.com]
> > > Sent: Monday, December 17, 2007 7:00 AM
> > > To: pwe3@ietf.org
> > > Subject: Re: [PWE3] PW Redundancy to WG drafts?
> > > 
> > > A considerable number of people have said that they support
> > adoption
> > > of these drafts, but the minutes of the PWE3 meetings say:
> > > 
> > > 
> > >  >Authors requesting to move to WG status  >Dave McDyson: 
> Proposes 
> > > requirements be settled first.
> > >  >Also requests cross-referencing other drafts, and  >explaining 
> > > terminology.
> > >  >
> > >  >Stewart: asks what alignment is required  >  >Dave 
> McDyson: IEEE 
> > > protection, and possibly ITU  >
> > >  >Matthew: That is part of requirements draft  >  >Dave
> > McDyson: The
> > > solution seems to rely on correct configuration.
> > >  >
> > >  >Automatic identification of master and slave would be nice.
> > >  >
> > >  >Danny: Are you volunteering to help ?
> > >  >
> > >  >Dave McDyson: yes
> > >  >
> > >  >Dave says he is happy that Luca is now working on this
> > draft as well
> > > >  >Luca Martini (via Jabber): Hey ! , this is a very different
> > > document  >since the time I made that statement !
> > >  >
> > >  >Danny: will ask on the list.
> > > 
> > > I therefore have two questions?
> > > 
> > > 1) Do we need a requirements draft?
> > > 
> > > 2) If we need a requirements draft,
> > > 2a) Do we proceed with these proposals and sync up the 
> requirements 
> > > and solutions drafts on the fly?
> > > 
> > > or
> > > 
> > > 2b) Do we get traction on the requirements draft and then
> > verify that
> > > these drafts are suitable solutions?
> > > 
> > > Stewart
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > pwe3 mailing list
> > > pwe3@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/pwe3
> > > 
> > 
> > 
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pwe3
> > 
> 
> 
> 


_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www1.ietf.org/mailman/listinfo/pwe3