Re: [PWE3] Questions on draft-martini-pwe3-static-pw-status-02.txt

Luca Martini <lmartini@cisco.com> Thu, 03 December 2009 16:10 UTC

Return-Path: <lmartini@cisco.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 204433A69E7 for <pwe3@core3.amsl.com>; Thu, 3 Dec 2009 08:10:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level:
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 SpLxRdSrSrYF for <pwe3@core3.amsl.com>; Thu, 3 Dec 2009 08:10:29 -0800 (PST)
Received: from napoleon.monoski.com (napoleon.monoski.com [67.41.208.110]) by core3.amsl.com (Postfix) with ESMTP id AF2733A6876 for <pwe3@ietf.org>; Thu, 3 Dec 2009 08:10:28 -0800 (PST)
Received: from confusion.monoski.com (confusion.monoski.com [209.245.27.2]) (authenticated bits=0) by napoleon.monoski.com (8.13.8/8.13.8) with ESMTP id nB3G4hb3021749 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 3 Dec 2009 09:04:44 -0700 (MST)
Message-ID: <4B17E19B.1090604@cisco.com>
Date: Thu, 03 Dec 2009 09:04:43 -0700
From: Luca Martini <lmartini@cisco.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20081209)
MIME-Version: 1.0
To: Linda Dunbar <ldunbar@huawei.com>
References: <4AEF1C90.5060909@cisco.com> <4B06F925.8090908@cisco.com> <005801ca7370$ee36ca60$440c7c0a@china.huawei.com> <4B169F7C.3000801@cisco.com> <009e01ca739a$d490aed0$440c7c0a@china.huawei.com>
In-Reply-To: <009e01ca739a$d490aed0$440c7c0a@china.huawei.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.63 on 209.245.27.1
Cc: 'pwe3' <pwe3@ietf.org>, stbryant@cisco.com
Subject: Re: [PWE3] Questions on draft-martini-pwe3-static-pw-status-02.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 03 Dec 2009 16:10:29 -0000

Linda Dunbar wrote:
> With PW OAM message defined for static PW, can PW established by LDP also
> use this OAM message instead of the LDP notification message? 
>
>   
No.
This has been the case for the past 10 years, as defined in rfc4447.
The control plane is in control of the PW. So you cannot use a special 
channel to bypass the control plane.
Even the bypass message that is defined in this draft today does not 
work as mentioned. I believe we will be dropping that feature as it 
cannot be made to work without changing the basic design.
( we are missing the information about the origin on the message ).

I hope this helps.
Luca

> Linda 
>
> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com] 
> Sent: Wednesday, December 02, 2009 11:10 AM
> To: Linda Dunbar
> Cc: 'pwe3'
> Subject: Re: [PWE3] Questions on draft-martini-pwe3-static-pw-status-02.txt
>
> Linda:
>
> It is explained in the introduction:
>
> The default control plane for Pseudowire (PW) technology, as defined in 
> [RFC4447], is based on LDP. However that document also describes a 
> static provisioning mode without control plane. When a static PW is used 
> , there is no method to transmit the status of the PW, or attachment 
> circuit (AC) between the two PEs at each end of the PW.
>
> I.e. when there is no LDP there is no current method of exchanging 
> status, so a new method is needed, and that is described in this document.
> .
> - Stewart
>
> Linda Dunbar wrote:
>   
>> The "draft-martini-pwe3-static-pw-status-02.txt" stated using ACH for
>> exchange PW OAM status. Is PW's ACH same as PW's VCCV? 
>>
>> The RFC 4447 described PW Status to be exchanged via LDP notification
>>     
> which
>   
>> is over TCP. I am just curious why the static PW can't use the PW Status
>>     
> via
>   
>> notification defined by RFC 4447?  
>>
>> Thank you very much. 
>>
>> Linda Dunbar
>>
>> -----Original Message-----
>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
>> Stewart Bryant
>> Sent: Friday, November 20, 2009 2:17 PM
>> To: stbryant@cisco.com
>> Cc: pwe3
>> Subject: Re: [PWE3] draft-martini-pwe3-static-pw-status-02.txt now WG
>>     
> draft
>   
>> I have seen a large number of accepts and no objections.
>>
>> Please will the authors resubmit this as a WG document.
>>
>> As discussed at the WG, will the authors please remove the reference to 
>> MPLS-TP. This work is useful in it's own right, and any applicability to 
>> MPLS-TP should be decided by the MPLS-TP project.
>>
>> - Stewart
>>
>>
>>
>> Stewart Bryant wrote:
>>   
>>     
>>> This is a poll to see if
>>>
>>> http://tools.ietf.org/id/draft-martini-pwe3-static-pw-status-02.txt
>>>
>>> should be accepted as a PWE3 WG draft.
>>>
>>> Please reply "accept" or "do not accept" to this thread.
>>>
>>> Please start a new thread on for technical discussions on the draft.
>>>
>>> In view of the timing of IETF, I will close the poll Sunday 22nd 
>>> November.
>>>
>>> - Stewart
>>> _______________________________________________
>>> pwe3 mailing list
>>> pwe3@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pwe3
>>>
>>>     
>>>       
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3
>>
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3
>>
>>   
>>     
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>