Re: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard

"Aissaoui, Mustapha (Mustapha)" <mustapha.aissaoui@alcatel-lucent.com> Wed, 07 March 2012 17:55 UTC

Return-Path: <mustapha.aissaoui@alcatel-lucent.com>
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 5661621F850B; Wed, 7 Mar 2012 09:55:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.233
X-Spam-Level:
X-Spam-Status: No, score=-9.233 tagged_above=-999 required=5 tests=[AWL=1.365, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 QIarkYKasEXh; Wed, 7 Mar 2012 09:55:44 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 54CF821F8499; Wed, 7 Mar 2012 09:55:44 -0800 (PST)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id q27HtfTV014460 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 7 Mar 2012 11:55:41 -0600 (CST)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q27Htfff016717 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 7 Mar 2012 11:55:41 -0600
Received: from USNAVSXCHMBSC2.ndc.alcatel-lucent.com ([135.3.39.147]) by USNAVSXCHHUB01.ndc.alcatel-lucent.com ([135.3.39.110]) with mapi; Wed, 7 Mar 2012 11:55:41 -0600
From: "Aissaoui, Mustapha (Mustapha)" <mustapha.aissaoui@alcatel-lucent.com>
To: "Andrew G. Malis" <amalis@gmail.com>
Date: Wed, 07 Mar 2012 11:55:40 -0600
Thread-Topic: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard
Thread-Index: Acz8izeZXI9/dkIbSZqtuo9E9fuJLwAADwaw
Message-ID: <5DF53972F7E9134782DCE51624466FE50AD5811DB2@USNAVSXCHMBSC2.ndc.alcatel-lucent.com>
References: <20120307170032.20594.20281.idtracker@ietfa.amsl.com> <4F579F33.7050508@cisco.com> <5DF53972F7E9134782DCE51624466FE50AD5811DAC@USNAVSXCHMBSC2.ndc.alcatel-lucent.com> <CAK+d4xsS9GVrM1u2QPhsfXXK6xhzmQzGDDaVNhqay8VM_eQbaQ@mail.gmail.com>
In-Reply-To: <CAK+d4xsS9GVrM1u2QPhsfXXK6xhzmQzGDDaVNhqay8VM_eQbaQ@mail.gmail.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_5DF53972F7E9134782DCE51624466FE50AD5811DB2USNAVSXCHMBSC_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Cc: "draft-ietf-pwe3-redundancy-bit@tools.ietf.org" <draft-ietf-pwe3-redundancy-bit@tools.ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "stbryant@cisco.com" <stbryant@cisco.com>
Subject: Re: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 17:55:45 -0000

makes sense Andy.

Thanks,
Mustapha.

________________________________
From: Andrew G. Malis [mailto:amalis@gmail.com]
Sent: Wednesday, March 07, 2012 12:53 PM
To: Aissaoui, Mustapha (Mustapha)
Cc: stbryant@cisco.com; draft-ietf-pwe3-redundancy-bit@tools.ietf.org; pwe3@ietf.org; ietf@ietf.org
Subject: Re: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard

Mustapha,

You might want to wait for any other LC comments before updating.

Thanks,
Andy

On Wed, Mar 7, 2012 at 9:49 AM, Aissaoui, Mustapha (Mustapha) <mustapha.aissaoui@alcatel-lucent.com<mailto:mustapha.aissaoui@alcatel-lucent.com>> wrote:
Ooops. Thank you for pointing this out Stewart. I will make the update and publish a new revision.

Mustapha.

-----Original Message-----
From: Stewart Bryant [mailto:stbryant@cisco.com<mailto:stbryant@cisco.com>]
Sent: Wednesday, March 07, 2012 12:48 PM
To: draft-ietf-pwe3-redundancy-bit@tools.ietf.org<mailto:draft-ietf-pwe3-redundancy-bit@tools.ietf.org>
Cc: ietf@ietf.org<mailto:ietf@ietf.org>; pwe3@ietf.org<mailto:pwe3@ietf.org>
Subject: Re: Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard


Authors

There was on point that I notice that you did not address from the AD review and so I am picking it up as a LC comment:

In section 10 you say:

   "This document makes the following update to the PwOperStatusTC
   textual convention in RFC5542 [8]: "

This update should be recorded in the metadata (top left front page) and it is usual to put a one line note in the abstract.

Stewart



On 07/03/2012 17:00, The IESG wrote:
> The IESG has received a request from the Pseudowire Emulation Edge to
> Edge WG (pwe3) to consider the following document:
> - 'Pseudowire Preferential Forwarding Status Bit'
>    <draft-ietf-pwe3-redundancy-bit-06.txt>  as a Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org<mailto:ietf@ietf.org> mailing lists by 2012-03-21. Exceptionally, comments may
> be sent to iesg@ietf.org<mailto:iesg@ietf.org> instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     This document describes a mechanism for standby status signaling of
>     redundant pseudowires (PWs) between their termination points. A set
>     of redundant PWs is configured between provider edge (PE) nodes in
>     single-segment pseudowire (SS-PW) applications, or between
>     terminating provider edge (T-PE) nodes in multi-segment pseudowire
>     (MS-PW) applications.
>
>     In order for the PE/T-PE nodes to indicate the preferred PW to use
>     for forwarding PW packets to one another, a new status bit is needed
>     to indicate a preferential forwarding status of Active or Standby for
>     each PW in a redundant set.
>
>     In addition, a second status bit is defined to allow peer PE nodes to
>     coordinate a switchover operation of the PW.
>
>
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundancy-bit/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundancy-bit/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org<mailto:IETF-Announce@ietf.org>
> https://www.ietf.org/mailman/listinfo/ietf-announce
>


--
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


_______________________________________________
pwe3 mailing list
pwe3@ietf.org<mailto:pwe3@ietf.org>
https://www.ietf.org/mailman/listinfo/pwe3