
From wwwrun@core3.amsl.com  Wed Feb  2 07:28:19 2011
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: mpls-tp@ietf.org
Delivered-To: mpls-tp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id E2B403A6D2C; Wed,  2 Feb 2011 07:28:19 -0800 (PST)
From: Loa Andersson(IETF MPLS WG) <loa@pi.nu>
To: greg.jones@itu.int
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110202152819.E2B403A6D2C@core3.amsl.com>
Date: Wed,  2 Feb 2011 07:28:19 -0800 (PST)
Cc: mpls@ietf.org, greg.jones@itu.int, mpls-tp@ietf.org, loa.andersson@ericsson.com, swallow@cisco.con, yoichi.maeda@ttc.or.jp, kam.lam@alcatel-lucent.com, ahmpls-tp@lists.itu.int, paf@cisco.com, adrian.farrel@huawei.com, tsbsg15@itu.int, hhelvoort@huawei.com, ghani.abbas@ericsson.com
Subject: [mpls-tp] New Liaison Statement, "The IETF MPLS working group request early review of two MPLS working group documents (ref #048.01)"
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: loa.andersson@ericsson.com
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 15:28:20 -0000

Title: The IETF MPLS working group request early review of two MPLS working group documents (ref #048.01)
Submission Date: 2011-02-02
URL of the IETF Web page: https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=1001 
Please reply by 2011-02-28

From: Loa Andersson(IETF MPLS WG) <loa@pi.nu>
To: SG15, Q9, Q10, Q12 and Q14(greg.jones@itu.int)
Cc: yoichi.maeda@ttc.or.jp
greg.jones@itu.int
ghani.abbas@ericsson.com
hhelvoort@huawei.com
malcolm.betts@zte.com.cn
kam.lam@alcatel-lucent.com
tsbsg15@itu.int
ahmpls-tp@lists.itu.int
adrian.farrel@huawei.com
rcallon@juniper.net
paf@cisco.com
stbryant@cisco.com
mpls@ietf.org
mpls-tp@ietf.org
swallow@cisco.com
Reponse Contact: loa.andersson@ericsson.com
Technical Contact: loa.andersson@ericsson.com
swallow@cisco.con
rcallon@juniper.net
Purpose: For action 
Body: 

The MPLS working group would like to like to rerquest that the ITU-T SG15
undertakes an early rview on:


"Multiprotocol Label Switching Transport Profile (MPLS-TP)
 MIB-based Management Overview"

draft-ietf-mpls-tp-mib-management-overview-02.txt

and 

"A Thesaurus for the Terminology used in Multiprotocol Label
 Switching Transport Profile (MPLS-TP) drafts/RFCs and ITU-T's
 Transport Network Recommendations."

draft-ietf-mpls-tp-rosetta-stone-03



Since we intend to work the comments receive through this early review
into the documents that will be discussed at the IETF meeting in Prague
We would like to receive comments from the ITU-T by February 28, 2011.


Loa Andersson
George Swallow
Ross Callon


MPLS Working Group co-chairs
Attachment(s):
No document has been attached



From loa@pi.nu  Wed Feb  2 08:09:50 2011
Return-Path: <loa@pi.nu>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 29ECA3A6D5C; Wed,  2 Feb 2011 08:09:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.15
X-Spam-Level: 
X-Spam-Status: No, score=-102.15 tagged_above=-999 required=5 tests=[AWL=-0.169, BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619, USER_IN_WHITELIST=-100]
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 ISElDGukAY6q; Wed,  2 Feb 2011 08:09:49 -0800 (PST)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id 2F7613A6D5B; Wed,  2 Feb 2011 08:09:47 -0800 (PST)
Received: from [10.154.12.191] (unknown [192.165.126.74]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id A6E282A8002; Wed,  2 Feb 2011 17:13:06 +0100 (CET)
Message-ID: <4D498294.7050703@pi.nu>
Date: Wed, 02 Feb 2011 17:13:08 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: mpls@ietf.org, mpls-tp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ahmpls-tp@lists.itu.int
Subject: [mpls-tp] Early review of two mpls working group documents
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 16:09:50 -0000

Working group,

this is to start a four week "early review" of

"Multiprotocol Label Switching Transport Profile (MPLS-TP)
  MIB-based Management Overview"

draft-ietf-mpls-tp-mib-management-overview-02.txt

and

"A Thesaurus for the Terminology used in Multiprotocol Label
  Switching Transport Profile (MPLS-TP) drafts/RFCs and ITU-T's
  Transport Network Recommendations."

draft-ietf-mpls-tp-rosetta-stone-03.txt


An "early review" is issued at a point when the document has matured
to a point where a consolidated review will help us moving the documents
into working group last call.

In order to address your comments in the document versions discussed at
the Prague meeting the comments should be sent to the mpls-tp list
February 28, 2011 the latest.

Loa, George and Ross

MPLS WG co-chairs

From loa@pi.nu  Wed Feb  2 09:40:55 2011
Return-Path: <loa@pi.nu>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CA81D3A6D89; Wed,  2 Feb 2011 09:40:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.128
X-Spam-Level: 
X-Spam-Status: No, score=-102.128 tagged_above=-999 required=5 tests=[AWL=-0.148, BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619, USER_IN_WHITELIST=-100]
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 4oLeRDATfaXr; Wed,  2 Feb 2011 09:40:55 -0800 (PST)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id 0E92D3A6D7C; Wed,  2 Feb 2011 09:40:54 -0800 (PST)
Received: from [10.154.12.191] (unknown [192.165.126.74]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id C2ED12A8001; Wed,  2 Feb 2011 18:44:13 +0100 (CET)
Message-ID: <4D4997EE.5020400@pi.nu>
Date: Wed, 02 Feb 2011 18:44:14 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: mpls-tp@ietf.org, mpls@ietf.org, draft-he-mpls-tp-csf@tools.ietf.org,  George Swallow <swallow@cisco.com>, Ross Callon <rcallon@juniper.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [mpls-tp] New working group document - draftt-he-mpls-tp-csf
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 17:40:55 -0000

Working Group,

the poll to accept draft-he-mpls-tp-csf-03.txt ("Indication of Client
Failure in MPLS-TP") concluded some time ago.

The poll gave a very clear indication of support for accepting the
the document as a MPLS Working Group document.

After the poll had concluded a discussion started where several
opinions were voiced, including that the document is not really needed.

However after discussing the topic the wg chairs has decided to accept 
the draft as a working group draft, since the case where an LSP coming
in over an UNI and goes directly into the MPLS based Transport Network
without the PW adaptation is still valid and needs to be covered.

Could the authors please re-spin the draft as:

draft-ietf-mpls-tp-csf-00.txt

After that the draft needs to be re-worked to clearly focus on the
case described


   - the current document needs to be published as wg doc version -00
   - immediately after that a new version should be re-spun focusing
     on the UNI case mentioned above and a new version (-01) has
     to be timely published

Loa, George, Ross
mpls wg co-chairs

From loa@pi.nu  Thu Feb  3 03:20:48 2011
Return-Path: <loa@pi.nu>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 426C43A68FA; Thu,  3 Feb 2011 03:20:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.099
X-Spam-Level: 
X-Spam-Status: No, score=-102.099 tagged_above=-999 required=5 tests=[AWL=-0.119, BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619, USER_IN_WHITELIST=-100]
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 sj2qpXVf-rQa; Thu,  3 Feb 2011 03:20:47 -0800 (PST)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id 3E6793A68F8; Thu,  3 Feb 2011 03:20:47 -0800 (PST)
Received: from [10.154.12.191] (unknown [192.165.126.74]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id A395D2A8001; Thu,  3 Feb 2011 12:24:07 +0100 (CET)
Message-ID: <4D4A9059.9050701@pi.nu>
Date: Thu, 03 Feb 2011 12:24:09 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: mpls-tp@ietf.org, mpls@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ahmpls-tp@lists.itu.int
Subject: [mpls-tp] Upcoming reviews and working group last calls
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 11:20:48 -0000

Working Group,

we are now in a situation there a number of documents from the
mpls-tp project are ready to be working group last called,
early reviewed or reviewed by external parties.

Since there are strong interdependencies between these
document we have come to the conclusion that rather than do
a number of two week consecutive last call or review we
want to allocate a four week period (ending approx February 28)
to review and last call a number of documents. Still a bit
unclear how many.

You have seen the call for early review of the Rosetta Stone
and the Management Overview documents.

You will later today see working group last calls for the Linear
Protection  and the Fault Signaling documents. We have good hope
that we also will be able to include the Proactive CC and CV
document in this.

It is possible that we will include further documents.

The reviews and last call are important, and even though we do
this to able progress documents smoothly please note that we
still need to take care to get good reviews.

Loa, George and Ross

MPLS wg co-chairs

From loa@pi.nu  Thu Feb  3 03:33:25 2011
Return-Path: <loa@pi.nu>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 24B163A6901; Thu,  3 Feb 2011 03:33:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.088
X-Spam-Level: 
X-Spam-Status: No, score=-102.088 tagged_above=-999 required=5 tests=[AWL=-0.108, BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619, USER_IN_WHITELIST=-100]
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 7XfVTu+G7Vqj; Thu,  3 Feb 2011 03:33:24 -0800 (PST)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id 4698C3A68FD; Thu,  3 Feb 2011 03:33:24 -0800 (PST)
Received: from [10.154.12.191] (unknown [192.165.126.74]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id 64BFD2A8001; Thu,  3 Feb 2011 12:36:45 +0100 (CET)
Message-ID: <4D4A934F.5020206@pi.nu>
Date: Thu, 03 Feb 2011 12:36:47 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: mpls-tp@ietf.org, mpls@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ahmpls-tp@lists.itu.int
Subject: [mpls-tp] wg last call on draft-ietf-mpls-tp-fault-03
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 11:33:25 -0000

Working Group,

this is to start a four week working group last call
on "MPLS Fault Management OAM" (draft-ietf-mpls-tp-fault-03).

Please send comments to the mpls-tp@ietf.org mailing list.

This working group last call ends on February 28, 2011.



Loa, George and Ross

MPLS wg co-chairs

--

Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13




From loa@pi.nu  Thu Feb  3 03:38:22 2011
Return-Path: <loa@pi.nu>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 03C3C3A68FE; Thu,  3 Feb 2011 03:38:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.079
X-Spam-Level: 
X-Spam-Status: No, score=-102.079 tagged_above=-999 required=5 tests=[AWL=-0.099, BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619, USER_IN_WHITELIST=-100]
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 Mfo63-sRe7iw; Thu,  3 Feb 2011 03:38:21 -0800 (PST)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id 3D4253A68D7; Thu,  3 Feb 2011 03:38:21 -0800 (PST)
Received: from [10.154.12.191] (unknown [192.165.126.74]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id 8E78D2A8001; Thu,  3 Feb 2011 12:41:42 +0100 (CET)
Message-ID: <4D4A9478.7050704@pi.nu>
Date: Thu, 03 Feb 2011 12:41:44 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: mpls-tp@ietf.org, mpls@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ahmpls-tp@lists.itu.int
Subject: [mpls-tp] mpls wg last call on draft-ietf-mpls-tp-linear-protection-04
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 11:38:22 -0000

Working Group,

this is to start a four week working group last call on
"MPLS-TP Linear Protection" (draft-ietf-mpls-tp-linear-protection-04).

Please send comments to the mpls-tp@ietf.org mailing list.

This working group last call ends on February 28, 2011.



Loa, George and Ross

MPLS wg co-chairs



-- 


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13

From wwwrun@core3.amsl.com  Thu Feb  3 04:02:09 2011
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: mpls-tp@ietf.org
Delivered-To: mpls-tp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 0DFC43A6936; Thu,  3 Feb 2011 04:02:08 -0800 (PST)
From: Loa Andersson(IETF MPLS WG) <loa@pi.nu>
To: greg.jones@itu.int
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110203120209.0DFC43A6936@core3.amsl.com>
Date: Thu,  3 Feb 2011 04:02:09 -0800 (PST)
Cc: mpls@ietf.org, greg.jones@itu.int, mpls-tp@ietf.org, loa.andersson@ericsson.com, yoichi.maeda@ttc.or.jp, kam.lam@alcatel-lucent.com, ahmpls-tp@lists.itu.int, paf@cisco.com, adrian.farrel@huawei.com, tsbsg15@itu.int, hhelvoort@huawei.com, ghani.abbas@ericsson.com
Subject: [mpls-tp] New Liaison Statement, "The IETF MPLS working group last call on "MPLS Fault Management OAM" (ref #047.01)"
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: loa.andersson@ericsson.com
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 12:02:09 -0000

Title: The IETF MPLS working group last call on "MPLS Fault Management OAM" (ref #047.01)
Submission Date: 2011-02-03
URL of the IETF Web page: https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=1003 
Please reply by 2011-02-28

From: Loa Andersson(IETF MPLS WG) <loa@pi.nu>
To: SG15, Q9, Q10, Q12 and Q14(greg.jones@itu.int)
Cc: yoichi.maeda@ttc.or.jp
greg.jones@itu.int
ghani.abbas@ericsson.com
hhelvoort@huawei.com
malcolm.betts@zte.com.cn
kam.lam@alcatel-lucent.com
tsbsg15@itu.int
ahmpls-tp@lists.itu.int
adrian.farrel@huawei.com
rcallon@juniper.net
paf@cisco.com
stbryant@cisco.com
mpls@ietf.org
mpls-tp@ietf.org
swallow@cisco.com
Reponse Contact:  rcallon@juniper.net
 swallow@cisco.com
loa.andersson@ericsson.com
Technical Contact: loa.andersson@ericsson.com
Purpose: For action 
Body: 


The MPLS working group would like to inform you that we have started
a working group last call on "MPLS Fault Management OAM" 
(draft-ietf-mpls-tp-fault-03).

Since we intend to work the comments received through this working 
group last call into the documents that will be discussed at the 
IETF meeting in Prague we would like to receive comments from the 
ITU-T by February 28, 2011.


Loa Andersson
George Swallow
Ross Callon
Attachment(s):
No document has been attached



From wwwrun@core3.amsl.com  Thu Feb  3 04:37:51 2011
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: mpls-tp@ietf.org
Delivered-To: mpls-tp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id CCE7D3A695B; Thu,  3 Feb 2011 04:37:51 -0800 (PST)
From: Loa Andersson(IETF MPLS WG) <loa@pi.nu>
To: greg.jones@itu.int
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110203123751.CCE7D3A695B@core3.amsl.com>
Date: Thu,  3 Feb 2011 04:37:51 -0800 (PST)
Cc: mpls@ietf.org, greg.jones@itu.int, mpls-tp@ietf.org, loa.andersson@ericsson.com, yoichi.maeda@ttc.or.jp, kam.lam@alcatel-lucent.com, ahmpls-tp@lists.itu.int, paf@cisco.com, adrian.farrel@huawei.com, tsbsg15@itu.int, hhelvoort@huawei.com, ghani.abbas@ericsson.com
Subject: [mpls-tp] New Liaison Statement, "The IETF MPLS working group last call on "MPLS-TP Linear Protection" (ref #049.01)"
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: loa.andersson@ericsson.com
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 12:37:51 -0000

Title: The IETF MPLS working group last call on "MPLS-TP Linear Protection" (ref #049.01)
Submission Date: 2011-02-03
URL of the IETF Web page: https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=1004 
Please reply by 2011-02-28

From: Loa Andersson(IETF MPLS WG) <loa@pi.nu>
To: SG15, Q9, Q10, Q12 and Q14(greg.jones@itu.int)
Cc: yoichi.maeda@ttc.or.jp
greg.jones@itu.int
ghani.abbas@ericsson.com
hhelvoort@huawei.com
malcolm.betts@zte.com.cn
kam.lam@alcatel-lucent.com
tsbsg15@itu.int
ahmpls-tp@lists.itu.int
adrian.farrel@huawei.com
rcallon@juniper.net
paf@cisco.com
stbryant@cisco.com
mpls@ietf.org
mpls-tp@ietf.org
swallow@cisco.com
Reponse Contact: loa.andersson@ericsson.com
Technical Contact: loa.andersson@ericsson.com
swallow@cisco.com
rcallon@juniper.net
Purpose: For action 
Body: 


The MPLS working group would like to inform you that we have started
a working group last call on "MPLS-TP Linear Protection" 
(draft-ietf-mpls-tp-linear-protection-04).

Since we intend to work the comments received through this working 
group last call into the documents that will be discussed at the 
IETF meeting in Prague we would like to receive comments from the 
ITU-T by February 28, 2011.




Loa Andersson
George Swallow
Ross Callon


MPLS Working Group co-chairs
Attachment(s):
No document has been attached



From loa@pi.nu  Thu Feb  3 06:10:27 2011
Return-Path: <loa@pi.nu>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4AE843A6944; Thu,  3 Feb 2011 06:10:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.071
X-Spam-Level: 
X-Spam-Status: No, score=-102.071 tagged_above=-999 required=5 tests=[AWL=-0.091, BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619, USER_IN_WHITELIST=-100]
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 0N0oEPegPM8V; Thu,  3 Feb 2011 06:10:26 -0800 (PST)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id 6F1B43A6943; Thu,  3 Feb 2011 06:10:26 -0800 (PST)
Received: from [10.154.12.191] (unknown [192.165.126.74]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id A5FCE2A8001; Thu,  3 Feb 2011 15:13:47 +0100 (CET)
Message-ID: <4D4AB81D.3080907@pi.nu>
Date: Thu, 03 Feb 2011 15:13:49 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: mpls-tp@ietf.org, mpls@ietf.org, ahmpls-tp@lists.itu.int
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [mpls-tp] mpls wg last call on draft-ietf-mpls-tp-cc-cv-rdi-03
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 14:10:27 -0000

Working Group,

this is to start a four week working group last call on
"Proactive Connectivity Verification, Continuity Check and
Remote Defect indication for MPLS Transport Profile"
(draft-ietf-mpls-tp-cc-cv-rdi-03.txt).

Please send comments to the mpls-tp@ietf.org mailing list.

This working group last call ends on February 28, 2011.


Loa, George and Ross

MPLS wg co-chairs
-- 


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13

From wwwrun@core3.amsl.com  Thu Feb  3 06:25:33 2011
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: mpls-tp@ietf.org
Delivered-To: mpls-tp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id BA00F3A698D; Thu,  3 Feb 2011 06:25:33 -0800 (PST)
From: Loa Andersson(IETF MPLS WG) <loa@pi.nu>
To: greg.jones@itu.int
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110203142533.BA00F3A698D@core3.amsl.com>
Date: Thu,  3 Feb 2011 06:25:33 -0800 (PST)
Cc: mpls@ietf.org, greg.jones@itu.int, mpls-tp@ietf.org, loa.andersson@ericsson.com, yoichi.maeda@ttc.or.jp, kam.lam@alcatel-lucent.com, ahmpls-tp@lists.itu.int, paf@cisco.com, adrian.farrel@huawei.com, tsbsg15@itu.int, hhelvoort@huawei.com, ghani.abbas@ericsson.com
Subject: [mpls-tp] New Liaison Statement, "The IETF MPLS working group last call on "Proactive Connectivity Verification, Continuity Check and Remote Defect indication for MPLS Transport Profile" (ref #050.01)"
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: loa.andersson@ericsson.com
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 14:25:33 -0000

Title: The IETF MPLS working group last call on "Proactive Connectivity Verification, Continuity Check and Remote Defect indication for MPLS Transport Profile" (ref #050.01)
Submission Date: 2011-02-03
URL of the IETF Web page: https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=1005 
Please reply by 2011-02-28

From: Loa Andersson(IETF MPLS WG) <loa@pi.nu>
To: SG15, Q9, Q10, Q12 and Q14(greg.jones@itu.int)
Cc: yoichi.maeda@ttc.or.jp
greg.jones@itu.int
ghani.abbas@ericsson.com
hhelvoort@huawei.com
malcolm.betts@zte.com.cn
kam.lam@alcatel-lucent.com
tsbsg15@itu.int
ahmpls-tp@lists.itu.int
adrian.farrel@huawei.com
rcallon@juniper.net
paf@cisco.com
stbryant@cisco.com
mpls@ietf.org
mpls-tp@ietf.org
swallow@cisco.com
Reponse Contact: loa.andersson@ericsson.com
Technical Contact: swallow@cisco.com
rcallon@juniper.net
loa.andersson@ericsson.com
Purpose: For action 
Body: 


The MPLS working group would like to inform you that we have started
a working group last call on "Proactive Connectivity Verification,
Continuity Check and Remote Defect indication for MPLS Transport Profile" 
(draft-ietf-mpls-tp-cc-cv-rdi-03.txt).

Since we intend to work the comments received through this working 
group last call into the documents that will be discussed at the 
IETF meeting in Prague we would like to receive comments from the 
ITU-T by February 28, 2011.




Loa Andersson
George Swallow
Ross Callon


MPLS Working Group co-chairs
Attachment(s):
No document has been attached



From rcallon@juniper.net  Sun Feb  6 19:36:34 2011
Return-Path: <rcallon@juniper.net>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A97963A6C9B; Sun,  6 Feb 2011 19:36:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 cpnDpjhVRzvZ; Sun,  6 Feb 2011 19:36:34 -0800 (PST)
Received: from exprod7og126.obsmtp.com (exprod7og126.obsmtp.com [64.18.2.206]) by core3.amsl.com (Postfix) with ESMTP id 9168E3A6C95; Sun,  6 Feb 2011 19:36:33 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob126.postini.com ([64.18.6.12]) with SMTP ID DSNKTU9ovDiy6IectHZ/jwgBbqgeCvlSRbyC@postini.com; Sun, 06 Feb 2011 19:36:37 PST
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.2.254.0; Sun, 6 Feb 2011 19:33:02 -0800
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Sun, 6 Feb 2011 22:33:07 -0500
From: Ross Callon <rcallon@juniper.net>
To: "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>, "ahmpls-tp@lists.itu.int" <ahmpls-tp@lists.itu.int>
Date: Sun, 6 Feb 2011 22:33:06 -0500
Thread-Topic: MPLS WG last call on draft-ietf-mpls-tp-loss-delay-profile-02
Thread-Index: AcvDrJhCOwxbl7gbTh6wLaZt8CCDPACx1e2w
Message-ID: <DF7F294AF4153D498141CBEFADB177049BA717FF88@EMBX01-WF.jnpr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [mpls-tp] MPLS WG last call on draft-ietf-mpls-tp-loss-delay-profile-02
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Feb 2011 03:36:34 -0000

Working Group,

This is to start a four week working group last call on
"A Packet Loss and Delay Measurement Profile for MPLS-based=20
Transport Networks"
(draft-ietf-mpls-tp-loss-delay-profile-02.txt).

Please send comments to the mpls-tp@ietf.org mailing list.

Also, please note that the related document=20
"draft-ietf-mpls-loss-delay-01" is being last called in=20
parallel on the MPLS WG email list.=20

This working group last call ends on Monday March 7, 2011.

Ross, Loa, and George

MPLS WG co-chairs


From wwwrun@core3.amsl.com  Mon Feb  7 00:58:41 2011
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: mpls-tp@ietf.org
Delivered-To: mpls-tp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 639BF3A6CFA; Mon,  7 Feb 2011 00:58:41 -0800 (PST)
From: Loa Andersson(IETF MPLS WG) <loa@pi.nu>
To: greg.jones@itu.int
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110207085841.639BF3A6CFA@core3.amsl.com>
Date: Mon,  7 Feb 2011 00:58:41 -0800 (PST)
Cc: mpls@ietf.org, greg.jones@itu.int, mpls-tp@ietf.org, loa.andersson@ericsson.com, yoichi.maeda@ttc.or.jp, kam.lam@alcatel-lucent.com, ahmpls-tp@lists.itu.int, paf@cisco.com, adrian.farrel@huawei.com, tsbsg15@itu.int, hhelvoort@huawei.com, ghani.abbas@ericsson.com
Subject: [mpls-tp] New Liaison Statement, "The IETF MPLS working group last call on "A Packet Loss and Delay Measurement Profile for MPLS-based Transport Networks" (ref #051.01)"
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: loa.andersson@ericsson.com
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Feb 2011 08:58:41 -0000

Title: The IETF MPLS working group last call on "A Packet Loss and Delay Measurement Profile for MPLS-based Transport Networks" (ref #051.01)
Submission Date: 2011-02-07
URL of the IETF Web page: https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=1009 
Please reply by 2011-03-07

From: Loa Andersson(IETF MPLS WG) <loa@pi.nu>
To: ITU-T SG15 Q9, Q10, Q12 and Q14(greg.jones@itu.int)
Cc: yoichi.maeda@ttc.or.jp
greg.jones@itu.int
ghani.abbas@ericsson.com
hhelvoort@huawei.com
malcolm.betts@zte.com.cn
kam.lam@alcatel-lucent.com
tsbsg15@itu.int
ahmpls-tp@lists.itu.int
adrian.farrel@huawei.com
rcallon@juniper.net
paf@cisco.com
stbryant@cisco.com
mpls@ietf.org
mpls-tp@ietf.org
swallow@cisco.com
elisa.bellagamba@ericsson.com
Reponse Contact: loa.andersson@ericsson.com
Technical Contact: loa.andersson@ericsson.com
swallow@cisco.com
rcallon@juniper.net
Purpose: For action 
Body: 


The MPLS working group would like to inform you that we have started
a working group last call on "A Packet Loss and Delay Measurement 
Profile for MPLS-based Transport Networks" 
(draft-ietf-mpls-tp-loss-delay-profile-02.txt).

Please note that the related document "draft-ietf-mpls-loss-delay-01"
is being last called in parallel on the MPLS WG email list. 

Since we intend to work the comments received through this working 
group last call into the documents that will be discussed at the 
IETF meeting in Prague we would like to receive comments from the 
ITU-T by March 7, 2011.




Loa Andersson
George Swallow
Ross Callon


MPLS Working Group co-chairs
Attachment(s):
No document has been attached



From velantechie@gmail.com  Mon Feb  7 18:12:40 2011
Return-Path: <velantechie@gmail.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0FADF3A6A32; Mon,  7 Feb 2011 18:12:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 NCuccIp7jjsn; Mon,  7 Feb 2011 18:12:39 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id D374F3A7006; Mon,  7 Feb 2011 18:12:38 -0800 (PST)
Received: by wwa36 with SMTP id 36so5780898wwa.13 for <multiple recipients>; Mon, 07 Feb 2011 18:12:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=WaBpb1O6Lql0+HhAdNftqBP/taPBLpqEawJUHj2k3ug=; b=waKB+bvgy9fMXZCYz+q1lW1SLEHq/PDDSO7+xbt5mIfsXcAId+YqLuU0mDWJymsOjc ec2Y9KfxCm0BHLuLf+veTjhU6ggxjU8m/45JIa1okgtbiiBccr98dFMKJfUpRCApQQBi d9E2c8tBoOxnenmsTZJnO6eY8v6D48CpIXkV0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=b+Hl6OTxr+1FypdbdUTJe+VgbHLue4zWD8OkgDJMgMAR72k3EqctAGNz9yOaazwp9Z +Kt3x1LsSMyN6WXMxMdUoTKxNFsINJKi8awD9Avt2KvWXilAzhJ8+VRserv6N0FlVgVw enJLi6iPOlIGGv27QVRNgtdOpgx0RKo0BmmWQ=
MIME-Version: 1.0
Received: by 10.227.128.141 with SMTP id k13mr16821638wbs.11.1297131132355; Mon, 07 Feb 2011 18:12:12 -0800 (PST)
Received: by 10.227.145.14 with HTTP; Mon, 7 Feb 2011 18:12:12 -0800 (PST)
Date: Mon, 7 Feb 2011 18:12:12 -0800
Message-ID: <AANLkTi=9bTAukbm12HR34Nm3p20yjd0b4hS5dH3uFFAK@mail.gmail.com>
From: Velan S <velantechie@gmail.com>
To: mpls-tp@ietf.org, mpls@ietf.org
Content-Type: multipart/alternative; boundary=001636831e765f05bd049bbbe0b0
Subject: [mpls-tp] Questions of MPLS-TP LSP labeling
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Feb 2011 02:12:40 -0000

--001636831e765f05bd049bbbe0b0
Content-Type: text/plain; charset=ISO-8859-1

Hi Experts,

I have few questions and clarifications on MPLS-TP LSP labeling before I
speed up into MPLS-TP world.

1. Is MPLS-TP LSP uses special label value allocated static/dynamically. ?

2. why MPLS-TP LSP needs to be bidirectional and does each LSR/LER need to
bind the bi-directional LSP's association.?

3. My assumption is that MPLS-TP lsp is nothing but normal LSP created
statically/dynamically used to carry data and in-band channel information
over it.?

4. My assumption is that each Pseudowire data circuit will have 1:1
MPLS-TP Pseudowire for in-band channel communication to operate OAM function
on Pseudowire.?

5. Is bi-directional LSP symmeric  or not?

6. If it is Asymmetric, if one direction of the MPLS-TP lsp goes down, do we
need to make other direction of the paired LSP to  make it down.?

Please clarify my question.

Many thanks in advance.

Regards
Velan.S

--001636831e765f05bd049bbbe0b0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Hi Experts,</div>
<div>=A0</div>
<div>I have few questions and clarifications=A0on MPLS-TP LSP labeling befo=
re I speed up=A0into MPLS-TP world.</div>
<div>=A0</div>
<div>1. Is MPLS-TP LSP uses special label=A0value allocated static/dynamica=
lly. ?</div>
<div>=A0</div>
<div>2. why MPLS-TP LSP needs to be bidirectional and does=A0each LSR/LER n=
eed to bind the bi-directional LSP&#39;s association.?</div>
<div>=A0</div>
<div>3. My assumption is=A0that MPLS-TP lsp is nothing but normal LSP creat=
ed statically/dynamically used to carry data and in-band channel informatio=
n over it.?</div>
<div>=A0</div>
<div>4. My assumption is that each=A0Pseudowire=A0data circuit will have 1:=
1 MPLS-TP=A0Pseudowire for in-band channel communication to operate OAM fun=
ction on Pseudowire.?</div>
<div>=A0</div>
<div>5. Is bi-directional LSP symmeric=A0 or not?</div>
<div>=A0</div>
<div>6. If it is Asymmetric, if one direction of the MPLS-TP lsp goes down,=
 do we need to make other direction of the paired LSP to =A0make it down.?<=
/div>
<div>=A0</div>
<div>Please clarify my question.</div>
<div>=A0</div>
<div>Many thanks in advance.</div>
<div>=A0</div>
<div>Regards</div>
<div>Velan.S</div>

--001636831e765f05bd049bbbe0b0--

From loa@pi.nu  Tue Feb  8 15:40:33 2011
Return-Path: <loa@pi.nu>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DCBF73A68D1; Tue,  8 Feb 2011 15:40:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 z9IyiHEbZes6; Tue,  8 Feb 2011 15:40:33 -0800 (PST)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id F212D3A6866; Tue,  8 Feb 2011 15:40:32 -0800 (PST)
Received: from [10.104.72.179] (62-50-197-30.client.stsn.net [62.50.197.30]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id 3075B2A8001; Wed,  9 Feb 2011 00:40:38 +0100 (CET)
Message-ID: <4D51D472.5070607@pi.nu>
Date: Wed, 09 Feb 2011 00:40:34 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: "mpls-tp@ietf.org" <mpls-tp@ietf.org>
References: <4D3B30A3.1030607@pi.nu>
In-Reply-To: <4D3B30A3.1030607@pi.nu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mpls@ietf.org" <mpls@ietf.org>, MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>, draft-fang-mpls-tp-security-framework@tools.ietf.org
Subject: [mpls-tp] Poll has ended - Re: [mpls] poll on making draft-fang-mpls-tp-security-framework-04 a working group document
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Feb 2011 23:40:34 -0000

All,

this poll has ended.

We have accepted a new working group document.

Could the authors please publish the document as:

draft-ietf-mpls-tp-security-framework-00

without any other changes than date, file name and version number.


Loa, George and Ross
mpls wg co-chairs



On 2011-01-22 20:31, Loa Andersson wrote:
> Working Group,
>
> this is to start a two week poll on making
>
> draft-fang-mpls-tp-security-framework-04
>
> an MPLS working group document!
>
> Please send your responses to the mpls-tp@ietf.org mailing list.
>
> The poll ends Feb 6, 2011.
>
> Loa, George and Ross
> mpls wg co-chairs
>
>

-- 


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13

From mukund.mani@gmail.com  Tue Feb  8 22:27:08 2011
Return-Path: <mukund.mani@gmail.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1D8703A6900; Tue,  8 Feb 2011 22:27:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 ph8KFKdDfkvv; Tue,  8 Feb 2011 22:27:05 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id B74753A685D; Tue,  8 Feb 2011 22:27:03 -0800 (PST)
Received: by wwa36 with SMTP id 36so7110508wwa.13 for <multiple recipients>; Tue, 08 Feb 2011 22:27:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=K1koCvAC6pCcs7HkSamR/cYuXphtLhm5H2emc8S+4mg=; b=m0OFBCo+US7iJw+tHDFOKsHTmKgetK4LTxtp5+TtigtsIkavvCvooJAGP9TR2FLasI mFwTKlGgI+GrGYlmrKa/yszq0hSMsRb0y+0cS8weG08bdexZF1ear07PeCnJwYXfhPy6 op7DSxdW6G744xUfpqPYT+LXRqc8ChTVk2jiw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=YYFmWRTS6f8GJ9yKy1e2oyfo4DwViEDn7HOQYHGkWOkogF8DEo/0jczSvBEE+nYmdo vMbG203pHuRKoVpRFL4qAG0bpwshYE4YKuJy8mDWdmxLSwN3tuEi/G+VGn1rouf+Bbn1 JnhAsxkpqJ9tGbCNDRT1LK46qqrA5eYcAZOQM=
MIME-Version: 1.0
Received: by 10.227.144.194 with SMTP id a2mr1044014wbv.94.1297232832263; Tue, 08 Feb 2011 22:27:12 -0800 (PST)
Received: by 10.227.146.76 with HTTP; Tue, 8 Feb 2011 22:27:12 -0800 (PST)
Date: Wed, 9 Feb 2011 11:57:12 +0530
Message-ID: <AANLkTi=zeJTVn8gx_ZFefaS6adnFb20kWAnpDnDo2fP1@mail.gmail.com>
From: Mukund Mani <mukund.mani@gmail.com>
To: mpls-tp@ietf.org, rtg-bfd@ietf.org
Content-Type: multipart/alternative; boundary=0016368331982877f5049bd38e76
Subject: [mpls-tp] MPLS-ACH-IP and MPLS-IP encapsulations for BFD in MPLS-TP
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Feb 2011 06:27:08 -0000

--0016368331982877f5049bd38e76
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hello all


Had some questions on the usage of MPLS-ACH-IP and MPLS-IP encapsulations
for BFD in MPLS-TP

1.

MPLS-IP encapsulation is valid for MPLS-TP when IP addressing is being used=
.

(i.e in this case ACH will not be used).  If we follow the procedures
defined in BFD-base
drafts or BFD-MPLS, how exactly is it expected to achieve CV (connectivity
verification)
when ACH is not used in MPLS-TP? Is it acheived using Source IP comparison?

**

*Reference: *
**=93*draft-ietf-mpls-tp-lsp-ping-bfd-procedures-01=94 mentions the followi=
ng in
Section 3*

**

   [RFC5884] describes how BFD can be used for Continuity Check of MPLS

   LSPs.  The procedures described in [RFC5884] MUST be used when IP

   encapsulation is in use.  This section clarifies the usage of BFD in

   the context of MPLS-TP LSPs when it is not desirable to use IP

   encapsulation.  When using BFD over MPLS-TP LSPs, the BFD

   discriminator MUST either be signaled via LSP-Ping or be statically

   configured.  The BFD packets MUST be sent over ACH when IP

   encapsulation is not used.

2.
Is the usage of ACH TLV=92s allowed when MPLS-ACH-IP encapsulation is used =
in
MPLS-TP?
Question arises from the fact that to do CV in MPLS-TP, MEP identification
(carrying MEP TLV)
is required and thus ACH needs to be included even if IP addressing is
available.
Else there should be a mechanism to do CV with IP (Ref: Question 1)

With Regards
Mukund

--0016368331982877f5049bd38e76
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div>Hello all</div>
<div>=A0</div>
<div>=A0</div>
<div>Had some questions on the usage of MPLS-ACH-IP and MPLS-IP=A0encapsula=
tions for BFD in MPLS-TP</div>
<div>=A0</div>
<div>1. </div>
<div><span style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"></spa=
n>=A0</div>
<div><span style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">MPLS-=
IP encapsulation is valid for MPLS-TP when IP addressing is being used. </s=
pan></div>
<div><span style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">(i.e =
in this case ACH will not be used).=A0=A0</span><span style=3D"FONT-SIZE: 1=
0pt; COLOR: blue; FONT-FAMILY: Arial">If we follow the procedures defined i=
n BFD-base </span></div>

<div><span style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">draft=
s or BFD-MPLS, how exactly is it expected to achieve CV (connectivity verif=
ication) </span></div>
<div><span style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">when =
ACH is not used in MPLS-TP? Is it acheived using Source IP comparison?</spa=
n></div><pre style=3D"MARGIN-LEFT: 0.25in"><b><font face=3D"Courier New" si=
ze=3D"2"><span lang=3D"EN" style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt"></s=
pan></font></b></pre>

<div style=3D"MARGIN-LEFT: 0.25in"><b><font face=3D"Courier New" size=3D"2"=
><span lang=3D"EN" style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt">Reference: =
</span></font></b></div>
<div style=3D"MARGIN-LEFT: 0.25in"><b><font face=3D"Courier New" size=3D"2"=
><span lang=3D"EN" style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt"></span></fo=
nt></b><font face=3D"Arial" color=3D"navy" size=3D"2"><span style=3D"FONT-S=
IZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">=93</span></font><span class=3D=
"h11"><b><font face=3D"Courier New" size=3D"2"><span lang=3D"EN" style=3D"F=
ONT-SIZE: 10pt">draft-ietf-mpls-tp-lsp-ping-bfd-procedures-01=94 mentions t=
he following in Section 3</span></font></b></span></div>
<pre style=3D"MARGIN-LEFT: 0.25in"><span class=3D"h11"><b><font face=3D"Cou=
rier New" size=3D"2"><span lang=3D"EN" style=3D"FONT-SIZE: 10pt"></span></f=
ont></b></span></pre>
<p class=3D"MsoNormal"><font face=3D"Courier New" size=3D"2"><span style=3D=
"FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">=A0=A0 [RFC5884] desc=
ribes how BFD can be used for Continuity Check of MPLS</span></font></p>
<p class=3D"MsoNormal"><font face=3D"Courier New" size=3D"2"><span style=3D=
"FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">=A0=A0 LSPs.=A0 The p=
rocedures described in [RFC5884] MUST be used when IP</span></font></p>
<p class=3D"MsoNormal"><font face=3D"Courier New" size=3D"2"><span style=3D=
"FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">=A0=A0 encapsulation =
is in use.=A0 This section clarifies the usage of BFD in</span></font></p>
<p class=3D"MsoNormal"><font face=3D"Courier New" size=3D"2"><span style=3D=
"FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">=A0=A0 the context of=
 MPLS-TP LSPs when it is not desirable to use IP</span></font></p>
<p class=3D"MsoNormal"><font face=3D"Courier New" size=3D"2"><span style=3D=
"FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">=A0=A0 encapsulation.=
=A0 When using BFD over MPLS-TP LSPs, the BFD</span></font></p>
<p class=3D"MsoNormal"><font face=3D"Courier New" size=3D"2"><span style=3D=
"FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">=A0=A0 discriminator =
MUST either be signaled via LSP-Ping or be statically</span></font></p>
<p class=3D"MsoNormal"><font face=3D"Courier New" size=3D"2"><span style=3D=
"FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">=A0=A0 configured.=A0=
 The BFD packets MUST be sent over ACH when IP</span></font></p>
<p class=3D"MsoNormal"><font face=3D"Courier New" size=3D"2"><span style=3D=
"FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">=A0=A0 encapsulation =
is not used.</span></font></p>
<div style=3D"MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in; mso-list: l13 level=
1 lfo33"><font color=3D"blue" size=3D"2"><span lang=3D"EN" style=3D"FONT-SI=
ZE: 10pt; COLOR: blue"></span></font>=A0</div>
<div style=3D"MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in; mso-list: l13 level=
1 lfo33"><font color=3D"blue" size=3D"2"><span lang=3D"EN" style=3D"FONT-SI=
ZE: 10pt; COLOR: blue">2. </span></font></div>
<div style=3D"MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in; mso-list: l13 level=
1 lfo33"><font color=3D"blue" size=3D"2"><span lang=3D"EN" style=3D"FONT-SI=
ZE: 10pt; COLOR: blue">Is the usage of ACH TLV=92s allowed when MPLS-ACH-IP=
 encapsulation is used in MPLS-TP? </span></font></div>

<div style=3D"MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in; mso-list: l13 level=
1 lfo33"><font color=3D"blue" size=3D"2"><span lang=3D"EN" style=3D"FONT-SI=
ZE: 10pt; COLOR: blue">Question arises from the fact that to do CV in MPLS-=
TP, MEP identification (carrying MEP TLV) </span></font></div>

<div style=3D"MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in; mso-list: l13 level=
1 lfo33"><font color=3D"blue" size=3D"2"><span lang=3D"EN" style=3D"FONT-SI=
ZE: 10pt; COLOR: blue">is required and thus ACH needs to be included even i=
f IP addressing is available. </span></font></div>

<div style=3D"MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in; mso-list: l13 level=
1 lfo33"><font color=3D"blue" size=3D"2"><span lang=3D"EN" style=3D"FONT-SI=
ZE: 10pt; COLOR: blue">Else there should be a mechanism to do CV with IP (R=
ef: Question 1)</span></font><font color=3D"blue"><span style=3D"COLOR: blu=
e"></span></font></div>

<div>=A0</div>
<div>With Regards</div>
<div>Mukund</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>

--0016368331982877f5049bd38e76--

From david.i.allan@ericsson.com  Tue Feb  8 23:55:51 2011
Return-Path: <david.i.allan@ericsson.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CCD373A6924; Tue,  8 Feb 2011 23:55:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 B9+dX0VrZM1f; Tue,  8 Feb 2011 23:55:47 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id 9ECBA3A6922; Tue,  8 Feb 2011 23:55:47 -0800 (PST)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p198dkG6001006; Wed, 9 Feb 2011 02:39:47 -0600
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.66]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Wed, 9 Feb 2011 02:55:48 -0500
From: David Allan I <david.i.allan@ericsson.com>
To: Mukund Mani <mukund.mani@gmail.com>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Date: Wed, 9 Feb 2011 02:55:46 -0500
Thread-Topic: [mpls-tp] MPLS-ACH-IP and MPLS-IP encapsulations for BFD in MPLS-TP
Thread-Index: AcvIImzJvOwb4h2vSOm347RPHWUuNQAC5U5w
Message-ID: <60C093A41B5E45409A19D42CF7786DFD51CDEF1D53@EUSAACMS0703.eamcs.ericsson.se>
References: <AANLkTi=zeJTVn8gx_ZFefaS6adnFb20kWAnpDnDo2fP1@mail.gmail.com>
In-Reply-To: <AANLkTi=zeJTVn8gx_ZFefaS6adnFb20kWAnpDnDo2fP1@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_60C093A41B5E45409A19D42CF7786DFD51CDEF1D53EUSAACMS0703e_"
MIME-Version: 1.0
Subject: Re: [mpls-tp] MPLS-ACH-IP and MPLS-IP encapsulations for BFD in MPLS-TP
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Feb 2011 07:55:51 -0000

--_000_60C093A41B5E45409A19D42CF7786DFD51CDEF1D53EUSAACMS0703e_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

HI Mikund:

    You asked

          MPLS-IP encapsulation is valid for MPLS-TP when IP addressing is =
being used.
          (i.e in this case ACH will not be used).  If we follow the proced=
ures defined in BFD-base
          drafts or BFD-MPLS, how exactly is it expected to achieve CV (con=
nectivity verification)
          when ACH is not used in MPLS-TP? Is it acheived using Source IP c=
omparison?

    Yes,.see cc-cv-rdi draft 03 version section 3
A further artifact of IP encapsulation is that CV mis-connectivity defect d=
etection can be performed by inferring MEP_ID on the basis of the combinati=
on of the source IP address and "my discriminator" fields.

2.
Is the usage of ACH TLV's allowed when MPLS-ACH-IP encapsulation is used in=
 MPLS-TP?
Question arises from the fact that to do CV in MPLS-TP, MEP identification =
(carrying MEP TLV)
is required and thus ACH needs to be included even if IP addressing is avai=
lable.
Else there should be a mechanism to do CV with IP (Ref: Question 1)

The CC-CV-RDI draft deprecated the use of the ACH TLV in favor of a trailin=
g TLV for MEP ID, and we do not mandate the use of the trailing TLV when MP=
LS-ACH-IP encapsulation would be used (different code points).

I hope this helps
Dave

















--_000_60C093A41B5E45409A19D42CF7786DFD51CDEF1D53EUSAACMS0703e_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6001.18542" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D818235007-09022011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2><STRONG>HI Mikund:</STRONG></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D818235007-09022011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2><STRONG></STRONG></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SPAN=
=20
class=3D818235007-09022011><STRONG>&nbsp;&nbsp;&nbsp; You=20
asked</STRONG></SPAN></SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SPAN=
=20
class=3D818235007-09022011><FONT face=3D"Times New Roman" color=3D#000000=20
size=3D3>&nbsp;&nbsp;&nbsp; </FONT></SPAN></SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SPAN=
=20
class=3D818235007-09022011>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;</SPAN>MPLS-IP=20
encapsulation is valid for MPLS-TP when IP addressing is being used.=20
</SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SPAN=
=20
class=3D818235007-09022011>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;</SPAN>(i.e=20
in this case ACH will not be used).&nbsp;&nbsp;</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">If we follow the=
=20
procedures defined in BFD-base </SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SPAN=
=20
class=3D818235007-09022011>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;</SPAN>drafts=20
or BFD-MPLS, how exactly is it expected to achieve CV (connectivity=20
verification) </SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SPAN=
=20
class=3D818235007-09022011>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;</SPAN>when=20
ACH is not used in MPLS-TP? Is it acheived using Source IP comparison?<SPAN=
=20
class=3D818235007-09022011>&nbsp;</SPAN></SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SPAN=
=20
class=3D818235007-09022011></SPAN></SPAN>&nbsp;</DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SPAN=
=20
class=3D818235007-09022011><STRONG>&nbsp;&nbsp;&nbsp; Yes,.see cc-cv-rdi dr=
aft 03=20
version section 3&nbsp;</STRONG></SPAN></SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SPAN=
=20
class=3D818235007-09022011>
<P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 12pt 21.6pt"><FONT size=3D3><=
FONT=20
color=3D#000000><FONT face=3D"Courier New"><SPAN lang=3DEN=20
style=3D"mso-ansi-language: EN">A further artifact of IP encapsulation is t=
hat CV=20
mis-connectivity defect detection can be performed by inferring MEP_ID on t=
he=20
basis of the combination of the source IP address and </SPAN>"<SPAN lang=3D=
EN=20
style=3D"mso-ansi-language: EN">my discriminator</SPAN>" fields.<SPAN lang=
=3DEN=20
style=3D"mso-ansi-language: EN"><?xml:namespace prefix =3D o ns =3D=20
"urn:schemas-microsoft-com:office:office"=20
/><o:p></o:p></SPAN></FONT></FONT></FONT></P></SPAN></SPAN></DIV><PRE style=
=3D"MARGIN-LEFT: 0.25in"><B><FONT face=3D"Courier New" size=3D2><SPAN lang=
=3DEN style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt"></SPAN></FONT></B></PRE>
<DIV=20
style=3D"MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in; mso-list: l13 level1 lfo=
33"><FONT=20
color=3Dblue size=3D2><SPAN lang=3DEN style=3D"FONT-SIZE: 10pt; COLOR: blue=
">2.=20
</SPAN></FONT></DIV>
<DIV=20
style=3D"MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in; mso-list: l13 level1 lfo=
33"><FONT=20
color=3Dblue size=3D2><SPAN lang=3DEN style=3D"FONT-SIZE: 10pt; COLOR: blue=
">Is the=20
usage of ACH TLV&#8217;s allowed when MPLS-ACH-IP encapsulation is used in =
MPLS-TP?=20
</SPAN></FONT></DIV>
<DIV=20
style=3D"MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in; mso-list: l13 level1 lfo=
33"><FONT=20
color=3Dblue size=3D2><SPAN lang=3DEN style=3D"FONT-SIZE: 10pt; COLOR: blue=
">Question=20
arises from the fact that to do CV in MPLS-TP, MEP identification (carrying=
 MEP=20
TLV) </SPAN></FONT></DIV>
<DIV=20
style=3D"MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in; mso-list: l13 level1 lfo=
33"><FONT=20
color=3Dblue size=3D2><SPAN lang=3DEN style=3D"FONT-SIZE: 10pt; COLOR: blue=
">is required=20
and thus ACH needs to be included even if IP addressing is available.=20
</SPAN></FONT></DIV>
<DIV=20
style=3D"MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in; mso-list: l13 level1 lfo=
33"><SPAN=20
lang=3DEN style=3D"FONT-SIZE: 10pt; COLOR: blue">Else there should be a mec=
hanism to=20
do CV with IP (Ref: Question 1)<SPAN class=3D818235007-09022011><FONT=20
face=3DArial>&nbsp;</FONT></SPAN></SPAN></DIV>
<DIV=20
style=3D"MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in; mso-list: l13 level1 lfo=
33"><SPAN=20
lang=3DEN style=3D"FONT-SIZE: 10pt; COLOR: blue"><SPAN=20
class=3D818235007-09022011><FONT=20
face=3DArial><STRONG></STRONG></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV=20
style=3D"MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in; mso-list: l13 level1 lfo=
33"><SPAN=20
lang=3DEN style=3D"FONT-SIZE: 10pt; COLOR: blue"><SPAN=20
class=3D818235007-09022011><FONT face=3DArial><STRONG>The CC-CV-RDI draft d=
eprecated=20
the use of the ACH TLV in favor of a trailing TLV for MEP ID, and we do not=
=20
mandate the use of the trailing TLV when MPLS-ACH-IP encapsulation&nbsp;wou=
ld be=20
used (different code points).</STRONG></FONT></SPAN></SPAN></DIV>
<DIV=20
style=3D"MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in; mso-list: l13 level1 lfo=
33"><SPAN=20
lang=3DEN style=3D"FONT-SIZE: 10pt; COLOR: blue"><SPAN=20
class=3D818235007-09022011><STRONG></STRONG></SPAN></SPAN>&nbsp;</DIV>
<DIV=20
style=3D"MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in; mso-list: l13 level1 lfo=
33"><SPAN=20
lang=3DEN style=3D"FONT-SIZE: 10pt; COLOR: blue"><SPAN=20
class=3D818235007-09022011><FONT face=3DArial><STRONG>I hope this=20
helps</STRONG></FONT></SPAN></SPAN></DIV>
<DIV=20
style=3D"MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in; mso-list: l13 level1 lfo=
33"><STRONG><SPAN=20
lang=3DEN style=3D"FONT-SIZE: 10pt; COLOR: blue"><SPAN=20
class=3D818235007-09022011><FONT face=3DArial>Dave</FONT>&nbsp;</SPAN></SPA=
N><SPAN=20
style=3D"COLOR: blue"></SPAN></STRONG></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

--_000_60C093A41B5E45409A19D42CF7786DFD51CDEF1D53EUSAACMS0703e_--

From takeda.tomonori@lab.ntt.co.jp  Wed Feb  9 07:02:41 2011
Return-Path: <takeda.tomonori@lab.ntt.co.jp>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 70A483A69A8; Wed,  9 Feb 2011 07:02:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.89
X-Spam-Level: 
X-Spam-Status: No, score=-98.89 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_13=0.6, J_CHICKENPOX_21=0.6, USER_IN_WHITELIST=-100]
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 oNDqTJqwJklB; Wed,  9 Feb 2011 07:02:40 -0800 (PST)
Received: from tama50.ecl.ntt.co.jp (tama50.ecl.ntt.co.jp [129.60.39.147]) by core3.amsl.com (Postfix) with ESMTP id 1425E3A6767; Wed,  9 Feb 2011 07:02:39 -0800 (PST)
Received: from mfs5.rdh.ecl.ntt.co.jp (mfs5.rdh.ecl.ntt.co.jp [129.60.39.144]) by tama50.ecl.ntt.co.jp (8.14.4/8.14.4) with ESMTP id p19F2m2H028639; Thu, 10 Feb 2011 00:02:48 +0900 (JST)
Received: from mfs5.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by mfs5.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 70A486D3D; Thu, 10 Feb 2011 00:02:48 +0900 (JST)
Received: from imail2.m.ecl.ntt.co.jp (imail2-mgr.m.ecl.ntt.co.jp [129.60.144.42]) by mfs5.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 4AD2E6D39; Thu, 10 Feb 2011 00:02:48 +0900 (JST)
Received: from imf.m.ecl.ntt.co.jp (webmail.ecl.ntt.co.jp [129.60.39.130]) by imail2.m.ecl.ntt.co.jp (8.13.8/8.13.8) with SMTP id p19F2mPp015543;  Thu, 10 Feb 2011 00:02:48 +0900
Message-Id: <201102091502.p19F2mPp015543@imail2.m.ecl.ntt.co.jp>
To: ccamp@ietf.org, pce@ietf.org, mpls@ietf.org, mpls-tp@ietf.org
From: Tomonori TAKEDA <takeda.tomonori@lab.ntt.co.jp>
Date: Thu, 10 Feb 2011 00:02:48 +0900
X-Mailer: WebMail V3.7 PL3
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-2022-JP
Cc: iPOP2011-tpc-sec@pilab.jp
Subject: [mpls-tp] iPOP2011 Call for Presentation
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Feb 2011 15:02:41 -0000

(Apologies if you received multiple copies of this message.)

Dear CCAMP, PCE, MPLS and MPLS-TP subscribers,

iPOP2011 Call for Presentation is now open as follows.
The deadline for submitting presentation proposal is February 25th.

Best Regards,
Tomonori Takeda

------------------------------------------------------------------------
                     Call for Presentation

7th  International Conference on IP + Optical Network (iPOP 2011)
                         June 2-3, 2010
               NEC Tamagawa Plant, Kanagawa, Japan
                  http://www.pilab.jp/ipop2011/

The conference is intended to share among the industry and the academia,
the knowledge, new findings, and experience on the state-of-the art of
IP and optical networking technologies. It features technical sessions
and planned exhibitions. The opportunity to participate is open to all.

Important Dates:
Submission deadline of one-page abstract: February 25, 2010 
Notification of acceptance: April 4, 2010
Submission deadline of final presentation slides: April 22, 2010

The Technical Program Committee for iPOP 2010 is soliciting presentation 
proposals for this conference. Protocol design, experiment, theory, 
implementation, and operational experiences are solicited.
The topics of the conference will include but not limited to the following:

* GMPLS/ASON technologies
* GMPLS Network management, OA&M
* Multi-layer network (MLN) / Multi-region network (MRN)
* Path Computation Element (PCE), Traffic engineering
* Inter-area/Inter-AS network
* L1VPN, Bandwidth on Demand, and Photonic Grid
* Wavelength Switched Optical Networks  (WSON), Routing wavelength
  assignment, Impairment management
* GMPLS-controlled Ethernet Label Switching  (GELS) and related Ethernet
  transport technologies
* Carrier Ethernet and MPLS-TP
* Photonic Network for NxGN and NwGN
* Application with high-bandwidth demand
* Testbed, field trial

If you wish to submit a topic for consideration, please send an Extended 
Abstracts of a 400 words and a maximum of 1 page, including figures and 
diagrams, speaker$B!G(Bs name, affiliation, and contact information 
to the Technical Program Committee at ipop2011-CFP@pilab.jp.
Please see http://www.pilab.jp/ipop2011/ for more details.
----------------------------------------------------------------------


From gregimirsky@gmail.com  Wed Feb  9 16:51:13 2011
Return-Path: <gregimirsky@gmail.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A356E3A672F; Wed,  9 Feb 2011 16:51:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 RRL-0kS24T0i; Wed,  9 Feb 2011 16:51:12 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id 9358D3A67FA; Wed,  9 Feb 2011 16:51:12 -0800 (PST)
Received: by vxi40 with SMTP id 40so418649vxi.31 for <multiple recipients>; Wed, 09 Feb 2011 16:51:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=tUqJXPz2GD7xvMYG+mU49GaszlbMbASjF6rh0h6kV6o=; b=ptoBztQnUajvfmGh6JfO5z3zYF3JumxabTr2Urn2EAOoPmsknVTDPuicguyD66Vvli xSfZjx7EWcCOqWGk04tYPIpsKrk0VF9l3chnk8wYG9zTLDN3sBuOp/NAexYL6DutnNyi O3QvdcqFXuErq5Uh0mDnFMcXqnQBHXliCXbNw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=DFDGJxPPhf2lzeAQpBZh2iGPYPResOgVniZj4p8qe0yoTKiUiMGRQ1Z5H+fCtmHVO4 3HUsy86WPF0o23z6Fpexz2z/ALOSRuJvWGRFz6LyQfWV3joDcHWKsXhNxAyhmAf5vQ19 GrcrpoEQp7fP9i5E8GnDXGS6pw10rabU5aoxk=
MIME-Version: 1.0
Received: by 10.220.181.9 with SMTP id bw9mr177252vcb.13.1297299083130; Wed, 09 Feb 2011 16:51:23 -0800 (PST)
Received: by 10.220.103.4 with HTTP; Wed, 9 Feb 2011 16:51:23 -0800 (PST)
Date: Wed, 9 Feb 2011 16:51:23 -0800
Message-ID: <AANLkTinbh8j1RqeSjTpOnnkFTa75neSxiee9QPRvwCf-@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: swallow@cisco.com, martin.vigoureux@alcatel-lucent.com,  Sami Boutros <sboutros@cisco.com>, David Ward <dward@juniper.net>, mpls@ietf.org, mpls-tp@ietf.org
Content-Type: multipart/alternative; boundary=90e6ba53a90c0478c9049be2fb97
Subject: [mpls-tp] Question to draft-ietf-mpls-tp-fault-03
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Feb 2011 00:51:13 -0000

--90e6ba53a90c0478c9049be2fb97
Content-Type: text/plain; charset=ISO-8859-1

Dear Authors,
section 6 lists mandatory and optional implementation requirements. In
bullet 1 setting of R-flag to non-zero value (clearing of previously
reported FM condition) listed as optional - "... setting the R bit to value
other than zero need not be supported."
But setting the R-flag is not listed as optional functionality. Only
"support of receiving the R flag" is listed as optional item #2. Adding
"sending" and " or "setting R-flag to non-zero value" to this  "Support of
receiving the R flag" might clear the issue.

Regards,
Greg

--90e6ba53a90c0478c9049be2fb97
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear Authors,<br>section 6 lists mandatory and optional implementation requ=
irements. In bullet 1 setting of R-flag to non-zero value (clearing of prev=
iously reported FM condition) listed as optional - &quot;... setting the R =
bit to value other than zero need not be supported.&quot;<br>
But setting the R-flag is not listed as optional functionality. Only &quot;=
support of receiving the R flag&quot; is listed as optional item #2. Adding=
 &quot;sending&quot; and &quot; or &quot;setting R-flag to non-zero value&q=
uot; to this=A0 &quot;Support of receiving the R flag&quot; might clear the=
 issue.<br>
<br>Regards,<br>Greg<br>

--90e6ba53a90c0478c9049be2fb97--

From mach@huawei.com  Wed Feb  9 19:46:05 2011
Return-Path: <mach@huawei.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 76C343A684D; Wed,  9 Feb 2011 19:46:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
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 1ZCLo3qFLs7M; Wed,  9 Feb 2011 19:46:04 -0800 (PST)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 280F73A684B; Wed,  9 Feb 2011 19:46:04 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LGD00FYNUEH60@szxga05-in.huawei.com>; Thu, 10 Feb 2011 11:44:41 +0800 (CST)
Received: from C55527A ([10.110.98.33]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LGD00MPYUEBW4@szxga05-in.huawei.com>; Thu, 10 Feb 2011 11:44:41 +0800 (CST)
Date: Thu, 10 Feb 2011 11:44:35 +0800
From: Mach Chen <mach@huawei.com>
In-reply-to: <4D4AB81D.3080907@pi.nu>
To: 'Loa Andersson' <loa@pi.nu>, mpls-tp@ietf.org, mpls@ietf.org, ahmpls-tp@lists.itu.int
Message-id: <06c901cbc8d4$d682a820$8387f860$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: zh-cn
Content-transfer-encoding: 7BIT
Thread-index: AcvDrJpCvXJpavHRRhKBBXlDzw1/zAFFYIGQ
References: <4D4AB81D.3080907@pi.nu>
Subject: Re: [mpls-tp] mpls wg last call on draft-ietf-mpls-tp-cc-cv-rdi-03
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Feb 2011 03:46:05 -0000

Dear authors,

I read the draft, here are some comments, please consider:

1.Section 3.5, last sentence of first paragraph

"Poll/final discipline can only used for VCCV and UDP/IP encapsulated BFD."
There is a "be" lost between "can" and "only".

2.Section 3.5.2
"1. BFD control packets are received with an unexpected encapsulation
(mis-connectivity defect), these include: 
          - a PW receiving a packet with a GAL", Since GAL can be used for
PW(http://tools.ietf.org/html/draft-ietf-pwe3-mpls-tp-gal-in-pw-00), this
should not be a defect. Suggest to remove it.

3 Section 3.5.2
" 4. Receipt of an expected session discriminator with an unexpected label
(mis-connectivity defect).", For a receiver, how does it know that the
session discriminator is valid but the label is invalid? IMHO, this defect
is just another description of defect 3 . Suggest to remove it.

4.Section 3.5.4.2
" Exit from a misconfiguration defect occurs when two consecutive CC or CV
frames have been received with the expected M bit setting." IMHO, this
sentence is little bit vague, and since this draft only defines for P2P LSP,
why not just say "...with M bit clear."

5. Section 3.5.4.3
"Exit from a mis-connectivity defect state occurs when no CV messages have
been received with an incorrect source MEP-ID for a period of 3.5 seconds.",
since there are several defects listed in Section 3.5.2 and this is only one
condition for exiting from a mis-connectivity defect state. How about "Exit
from a mis-connectivity defect state occurs when no CV messages with
mis-connectivity defects have been received for a period of 3.5 seconds "

6. Section 3.5.5

In Figure 5, seems that it is lack of "AIS-LDI, LKR" inputs for DOWN state.



Best regards,
Mach


> -----Original Message-----
> From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf
> Of Loa Andersson
> Sent: Thursday, February 03, 2011 10:14 PM
> To: mpls-tp@ietf.org; mpls@ietf.org; ahmpls-tp@lists.itu.int
> Subject: [mpls-tp] mpls wg last call on draft-ietf-mpls-tp-cc-cv-rdi-03
> 
> Working Group,
> 
> this is to start a four week working group last call on
> "Proactive Connectivity Verification, Continuity Check and
> Remote Defect indication for MPLS Transport Profile"
> (draft-ietf-mpls-tp-cc-cv-rdi-03.txt).
> 
> Please send comments to the mpls-tp@ietf.org mailing list.
> 
> This working group last call ends on February 28, 2011.
> 
> 
> Loa, George and Ross
> 
> MPLS wg co-chairs
> --
> 
> 
> Loa Andersson                         email:
> loa.andersson@ericsson.com
> Sr Strategy and Standards Manager            loa@pi.nu
> Ericsson Inc                          phone: +46 10 717 52 13
>                                               +46 767 72 92 13
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp



From guoxinchun@huawei.com  Thu Feb 10 01:51:45 2011
Return-Path: <guoxinchun@huawei.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F00B3A693C; Thu, 10 Feb 2011 01:51:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.495
X-Spam-Level: 
X-Spam-Status: No, score=-4.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
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 XJPSMaK0xY3p; Thu, 10 Feb 2011 01:51:44 -0800 (PST)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id D6C173A6929; Thu, 10 Feb 2011 01:51:43 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LGE004EUBE985@szxga04-in.huawei.com>; Thu, 10 Feb 2011 17:51:45 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LGE009XEBE930@szxga04-in.huawei.com>; Thu, 10 Feb 2011 17:51:45 +0800 (CST)
Received: from g67564e ([10.110.98.42]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LGE003E3BE4B5@szxml04-in.huawei.com>; Thu, 10 Feb 2011 17:51:45 +0800 (CST)
Date: Thu, 10 Feb 2011 17:51:40 +0800
From: g67564 <guoxinchun@huawei.com>
In-reply-to: <4D4A934F.5020206@pi.nu>
To: 'Loa Andersson' <loa@pi.nu>, mpls-tp@ietf.org, mpls@ietf.org
Message-id: <01b501cbc908$1dbba830$5932f890$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: TEXT/PLAIN
Content-language: zh-cn
Content-transfer-encoding: 7BIT
Thread-index: AcvDlrY6pzaQPGLDTRSwwtw9z+OhdgFcUP8g
References: <4D4A934F.5020206@pi.nu>
Cc: ahmpls-tp@lists.itu.int
Subject: Re: [mpls-tp] [mpls] wg last call on draft-ietf-mpls-tp-fault-03
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Feb 2011 09:51:45 -0000

Dear authors

After read the document, I have a question about the FM massage procedure.

In the section 5.1, the third paragraph, it said "The message is then sent.
The message MUST be refreshed two more times at an interval of one second.
Further refreshes are sent according to the value of the refresh timer."  I
don't know why the refreshing massage must be first sent two more times in
one second and then sent as the refresh timer interval.  Is it ok if the
refreshing massage is sent only according to the value of the refresh timer?
If it is not, what problem may be introduced? Hope authors could explain it
for me.

In addition, figure 2 is about the fault management massage format, so I
think naming the figure" MPLS-TP fault Management Message Format " other
than" MPLS-TP OAM Message Format " is more suitable.

Best Regards
Xinchun

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Loa
Andersson
Sent: Thursday, February 03, 2011 7:37 PM
To: mpls-tp@ietf.org; mpls@ietf.org
Cc: Ross Callon; ahmpls-tp@lists.itu.int
Subject: [mpls] wg last call on draft-ietf-mpls-tp-fault-03

Working Group,

this is to start a four week working group last call
on "MPLS Fault Management OAM" (draft-ietf-mpls-tp-fault-03).

Please send comments to the mpls-tp@ietf.org mailing list.

This working group last call ends on February 28, 2011.



Loa, George and Ross

MPLS wg co-chairs

--

Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13



_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls




From david.i.allan@ericsson.com  Thu Feb 10 03:08:36 2011
Return-Path: <david.i.allan@ericsson.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8389E3A6955; Thu, 10 Feb 2011 03:08:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599]
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 RHrhnwiGs62l; Thu, 10 Feb 2011 03:08:35 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id 36EAD3A6970; Thu, 10 Feb 2011 03:08:34 -0800 (PST)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p1ABqmBC012803; Thu, 10 Feb 2011 05:52:49 -0600
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.66]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Thu, 10 Feb 2011 06:08:35 -0500
From: David Allan I <david.i.allan@ericsson.com>
To: Mach Chen <mach@huawei.com>, "'Loa Andersson'" <loa@pi.nu>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>,  "ahmpls-tp@lists.itu.int" <ahmpls-tp@lists.itu.int>
Date: Thu, 10 Feb 2011 06:08:35 -0500
Thread-Topic: [mpls] [mpls-tp] mpls wg last call on draft-ietf-mpls-tp-cc-cv-rdi-03
Thread-Index: AcvDrJpCvXJpavHRRhKBBXlDzw1/zAFFYIGQABGDQCAAAKcQEA==
Message-ID: <60C093A41B5E45409A19D42CF7786DFD51CDF3F790@EUSAACMS0703.eamcs.ericsson.se>
References: <4D4AB81D.3080907@pi.nu> <06c901cbc8d4$d682a820$8387f860$@com> 
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [mpls-tp] [mpls] mpls wg last call on	draft-ietf-mpls-tp-cc-cv-rdi-03
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Feb 2011 11:08:36 -0000

=20

Hi Mach:=20

Thanks for the review

>I read the draft, here are some comments, please consider:

>1.Section 3.5, last sentence of first paragraph

>"Poll/final discipline can only used for VCCV and UDP/IP encapsulated BFD.=
"
>There is a "be" lost between "can" and "only".

Good catch, will fix.

>2.Section 3.5.2
>"1. BFD control packets are received with an unexpected encapsulation (mis=
-connectivity defect), these include:=20
>          - a PW receiving a packet with a GAL", Since GAL can be used=20
>for PW(http://tools.ietf.org/html/draft-ietf-pwe3-mpls-tp-gal-in-pw-00), t=
his should not be a defect. Suggest to remove it.

We'll review and edit accordingly.

>3 Section 3.5.2
>" 4. Receipt of an expected session discriminator with an unexpected label=
 (mis-connectivity defect).", For a receiver, how does it know that the ses=
sion >discriminator is valid but the label is invalid? IMHO, this defect is=
 just another description of defect 3 . Suggest to remove it.

If the session discriminator exists in the BFD database, it is superficiall=
y a valid descriminator but the label of arrival can be incorrect. This may=
 indicate an implementation problem at the source MEP. What we were referri=
ng to in '3' was a session discriminator that did not exist in the local da=
tabase, BFD had never handed it out hence it could not be found.

>4.Section 3.5.4.2
>" Exit from a misconfiguration defect occurs when two consecutive CC or=20
>CV frames have been received with the expected M bit setting." IMHO, this =
sentence is little bit vague, and since this draft only defines for P2P LSP=
, why not just say "...with M bit clear."

OK

>5. Section 3.5.4.3
>"Exit from a mis-connectivity defect state occurs when no CV messages=20
>have been received with an incorrect source MEP-ID for a period of 3.5 sec=
onds.", since there are several defects listed in Section 3.5.2 and this is=
 only one condition for exiting from a mis-connectivity defect state. How a=
bout "Exit >from a mis-connectivity defect state occurs when no CV messages=
 with mis-connectivity defects have been received for a period of 3.5 secon=
ds "

That seems to be more accurate, I'd replace "with...." with "indicating an =
on-going mis-connectivity defect has been....". Simply wordsmithing.

>6. Section 3.5.5

>In Figure 5, seems that it is lack of "AIS-LDI, LKR" inputs for DOWN state=
.

Good catch. Will fix

Cheers
Dave



> -----Original Message-----
> From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On=20
> Behalf Of Loa Andersson
> Sent: Thursday, February 03, 2011 10:14 PM
> To: mpls-tp@ietf.org; mpls@ietf.org; ahmpls-tp@lists.itu.int
> Subject: [mpls-tp] mpls wg last call on
> draft-ietf-mpls-tp-cc-cv-rdi-03
>=20
> Working Group,
>=20
> this is to start a four week working group last call on "Proactive=20
> Connectivity Verification, Continuity Check and Remote Defect=20
> indication for MPLS Transport Profile"
> (draft-ietf-mpls-tp-cc-cv-rdi-03.txt).
>=20
> Please send comments to the mpls-tp@ietf.org mailing list.
>=20
> This working group last call ends on February 28, 2011.
>=20
>=20
> Loa, George and Ross
>=20
> MPLS wg co-chairs
> --
>=20
>=20
> Loa Andersson                         email:
> loa.andersson@ericsson.com
> Sr Strategy and Standards Manager            loa@pi.nu
> Ericsson Inc                          phone: +46 10 717 52 13
>                                               +46 767 72 92 13=20
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From Alexander.Vainshtein@ecitele.com  Thu Feb 10 03:36:26 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F9A63A698F; Thu, 10 Feb 2011 03:36:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 NjzuCnORzw0m; Thu, 10 Feb 2011 03:36:25 -0800 (PST)
Received: from ilptbmg01.ecitele.com (ilptbmg01-out.ecitele.com [147.234.242.234]) by core3.amsl.com (Postfix) with ESMTP id 6B1EC3A697B; Thu, 10 Feb 2011 03:36:24 -0800 (PST)
X-AuditID: 93eaf2e7-b7b47ae000005f02-3d-4d53cdc5b6dc
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id AD.C1.24322.5CDC35D4; Thu, 10 Feb 2011 13:36:38 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Thu, 10 Feb 2011 13:36:35 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: David Allan I <david.i.allan@ericsson.com>
Date: Thu, 10 Feb 2011 13:36:25 +0200
Thread-Topic: [mpls] [mpls-tp] mpls wg last call	on draft-ietf-mpls-tp-cc-cv-rdi-03
Thread-Index: AcvDrJpCvXJpavHRRhKBBXlDzw1/zAFFYIGQABGDQCAAAKcQEAACic4A
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D6FB9C9FA3@ILPTMAIL02.ecitele.com>
References: <4D4AB81D.3080907@pi.nu> <06c901cbc8d4$d682a820$8387f860$@com> <60C093A41B5E45409A19D42CF7786DFD51CDF3F790@EUSAACMS0703.eamcs.ericsson.se>
In-Reply-To: <60C093A41B5E45409A19D42CF7786DFD51CDF3F790@EUSAACMS0703.eamcs.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, Robert Rennison <Robert.Rennison@ecitele.com>
Subject: Re: [mpls-tp] [mpls] mpls wg last call	on	draft-ietf-mpls-tp-cc-cv-rdi-03
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Feb 2011 11:36:26 -0000

Dave and all,
I'd like to remind you that Rob and I have already questioned the decision =
to change the BFD state machine by disabling in some case the Poll/Final se=
quence.

The situation as presented in the draft seems to introduce even more proble=
ms.=20
E.g., RFC 5885 allows to run BFD in VCCV without UDP/IP encapsulation but f=
ollows the procedures specified in RFC 5880 and 5881 which, to the best of =
my understanding, include usage of Poll/Final sequence.

It is my understanding that BFD for an MPLS-TP LSP would look exactly as BF=
D in VCCV (including the same code point).
If this is correct, how should the implementation distinguish between "PWE3=
 mode" (where poll/final are used) and "MPLS-TP mode where they seem to be =
prohibited?

Regards,
     Sasha

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Dav=
id Allan I
Sent: Thursday, February 10, 2011 1:09 PM
To: Mach Chen; 'Loa Andersson'; mpls-tp@ietf.org; mpls@ietf.org; ahmpls-tp@=
lists.itu.int
Subject: Re: [mpls] [mpls-tp] mpls wg last call on draft-ietf-mpls-tp-cc-cv=
-rdi-03

=20

Hi Mach:=20

Thanks for the review

>I read the draft, here are some comments, please consider:

>1.Section 3.5, last sentence of first paragraph

>"Poll/final discipline can only used for VCCV and UDP/IP encapsulated BFD.=
"
>There is a "be" lost between "can" and "only".

Good catch, will fix.

>2.Section 3.5.2
>"1. BFD control packets are received with an unexpected encapsulation (mis=
-connectivity defect), these include:=20
>          - a PW receiving a packet with a GAL", Since GAL can be used=20
>for PW(http://tools.ietf.org/html/draft-ietf-pwe3-mpls-tp-gal-in-pw-00), t=
his should not be a defect. Suggest to remove it.

We'll review and edit accordingly.

>3 Section 3.5.2
>" 4. Receipt of an expected session discriminator with an unexpected label=
 (mis-connectivity defect).", For a receiver, how does it know that the ses=
sion >discriminator is valid but the label is invalid? IMHO, this defect is=
 just another description of defect 3 . Suggest to remove it.

If the session discriminator exists in the BFD database, it is superficiall=
y a valid descriminator but the label of arrival can be incorrect. This may=
 indicate an implementation problem at the source MEP. What we were referri=
ng to in '3' was a session discriminator that did not exist in the local da=
tabase, BFD had never handed it out hence it could not be found.

>4.Section 3.5.4.2
>" Exit from a misconfiguration defect occurs when two consecutive CC or=20
>CV frames have been received with the expected M bit setting." IMHO, this =
sentence is little bit vague, and since this draft only defines for P2P LSP=
, why not just say "...with M bit clear."

OK

>5. Section 3.5.4.3
>"Exit from a mis-connectivity defect state occurs when no CV messages=20
>have been received with an incorrect source MEP-ID for a period of 3.5 sec=
onds.", since there are several defects listed in Section 3.5.2 and this is=
 only one condition for exiting from a mis-connectivity defect state. How a=
bout "Exit >from a mis-connectivity defect state occurs when no CV messages=
 with mis-connectivity defects have been received for a period of 3.5 secon=
ds "

That seems to be more accurate, I'd replace "with...." with "indicating an =
on-going mis-connectivity defect has been....". Simply wordsmithing.

>6. Section 3.5.5

>In Figure 5, seems that it is lack of "AIS-LDI, LKR" inputs for DOWN state=
.

Good catch. Will fix

Cheers
Dave



> -----Original Message-----
> From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On=20
> Behalf Of Loa Andersson
> Sent: Thursday, February 03, 2011 10:14 PM
> To: mpls-tp@ietf.org; mpls@ietf.org; ahmpls-tp@lists.itu.int
> Subject: [mpls-tp] mpls wg last call on
> draft-ietf-mpls-tp-cc-cv-rdi-03
>=20
> Working Group,
>=20
> this is to start a four week working group last call on "Proactive=20
> Connectivity Verification, Continuity Check and Remote Defect=20
> indication for MPLS Transport Profile"
> (draft-ietf-mpls-tp-cc-cv-rdi-03.txt).
>=20
> Please send comments to the mpls-tp@ietf.org mailing list.
>=20
> This working group last call ends on February 28, 2011.
>=20
>=20
> Loa, George and Ross
>=20
> MPLS wg co-chairs
> --
>=20
>=20
> Loa Andersson                         email:
> loa.andersson@ericsson.com
> Sr Strategy and Standards Manager            loa@pi.nu
> Ericsson Inc                          phone: +46 10 717 52 13
>                                               +46 767 72 92 13=20
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From mukund.mani@gmail.com  Thu Feb 10 05:09:26 2011
Return-Path: <mukund.mani@gmail.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F041D3A6A02; Thu, 10 Feb 2011 05:09:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 uhk6gJNxny8P; Thu, 10 Feb 2011 05:09:25 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 4E85F3A69A6; Thu, 10 Feb 2011 05:09:25 -0800 (PST)
Received: by wyf23 with SMTP id 23so1386897wyf.31 for <multiple recipients>; Thu, 10 Feb 2011 05:09:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=exk/kyRUbAVvPC7tS3gs3h0lSp6/r0hB4ewZxw6H2Ig=; b=Q2EpwYWLCmJZpVOoAz604yGD5Pyvw2s68eGpsAEnrBRO/3DWQRBfu+uJEIOArkUyOu 9MWV3c9mqGCZrONHZSzSHpjAFVAiwhJCDT6o+/+Vzfs+OYxBL0xi4GSkDfrnjuK+IXJn DOlrF/vRBnui+pIb/GrKxOC0kmB3IgeDlKadU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=VAFT54wZwFdgN1k+0v8FzuCJj+3fSo1RlFSD8hQSS1VAiXk/NZEqr+CGCef4vT77cd hqxosLp3N61dBa5zIf1YJ9sA22ZaI81VHVTFwREWq4370PeJkaZktVc/75ajiiEQw2sy tek7eQQnc/Z+STQlxkP7/8tQarYJH/gvPDTyk=
MIME-Version: 1.0
Received: by 10.227.145.17 with SMTP id b17mr6664532wbv.152.1297343376675; Thu, 10 Feb 2011 05:09:36 -0800 (PST)
Received: by 10.227.146.76 with HTTP; Thu, 10 Feb 2011 05:09:36 -0800 (PST)
In-Reply-To: <60C093A41B5E45409A19D42CF7786DFD51CDEF1D53@EUSAACMS0703.eamcs.ericsson.se>
References: <AANLkTi=zeJTVn8gx_ZFefaS6adnFb20kWAnpDnDo2fP1@mail.gmail.com> <60C093A41B5E45409A19D42CF7786DFD51CDEF1D53@EUSAACMS0703.eamcs.ericsson.se>
Date: Thu, 10 Feb 2011 18:39:36 +0530
Message-ID: <AANLkTim_tQ46Ox=vYLm2fuzV=FP5zkOhM=b7m6qou2We@mail.gmail.com>
From: Mukund Mani <mukund.mani@gmail.com>
To: David Allan I <david.i.allan@ericsson.com>
Content-Type: multipart/alternative; boundary=0016367faf831e59c9049bed4b5c
Cc: rtg-bfd@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls-tp] MPLS-ACH-IP and MPLS-IP encapsulations for BFD in MPLS-TP
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Feb 2011 13:09:27 -0000

--0016367faf831e59c9049bed4b5c
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Dave

Not really clear on the first one.. Here we are not including trailing MEP
TLV. How do we do CV for the first BFD packet with MPLS-IP encap ?

With Regards
Mukund
On Wed, Feb 9, 2011 at 1:25 PM, David Allan I <david.i.allan@ericsson.com>w=
rote:

>  *HI Mikund:*
> **
> *    You asked*
>
>           MPLS-IP encapsulation is valid for MPLS-TP when IP addressing i=
s
> being used.
>           (i.e in this case ACH will not be used).  If we follow the
> procedures defined in BFD-base
>           drafts or BFD-MPLS, how exactly is it expected to achieve CV
> (connectivity verification)
>           when ACH is not used in MPLS-TP? Is it acheived using Source IP
> comparison?
>
> *    Yes,.see cc-cv-rdi draft 03 version section 3 *
>
> A further artifact of IP encapsulation is that CV mis-connectivity defect
> detection can be performed by inferring MEP_ID on the basis of the
> combination of the source IP address and "my discriminator" fields.
>
> **
>
> 2.
> Is the usage of ACH TLV=92s allowed when MPLS-ACH-IP encapsulation is use=
d in
> MPLS-TP?
> Question arises from the fact that to do CV in MPLS-TP, MEP identificatio=
n
> (carrying MEP TLV)
> is required and thus ACH needs to be included even if IP addressing is
> available.
> Else there should be a mechanism to do CV with IP (Ref: Question 1)
> **
> *The CC-CV-RDI draft deprecated the use of the ACH TLV in favor of a
> trailing TLV for MEP ID, and we do not mandate the use of the trailing TL=
V
> when MPLS-ACH-IP encapsulation would be used (different code points).*
> **
> *I hope this helps*
> *Dave *
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

--0016367faf831e59c9049bed4b5c
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div>Hi Dave</div>
<div>=A0</div>
<div>Not really clear on the first one.. Here we are not including trailing=
 MEP TLV.=A0How do we do=A0CV for the first BFD packet with MPLS-IP encap ?=
 </div>
<div>=A0</div>
<div>With Regards</div>
<div>Mukund<br></div>
<div class=3D"gmail_quote">On Wed, Feb 9, 2011 at 1:25 PM, David Allan I <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:david.i.allan@ericsson.com">david.i.a=
llan@ericsson.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div dir=3D"ltr" align=3D"left"><span><font face=3D"Arial" color=3D"#0000ff=
" size=3D"2"><strong>HI Mikund:</strong></font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font face=3D"Arial" color=3D"#0000ff=
" size=3D"2"><strong></strong></font></span>=A0</div>
<div><span style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><span=
><strong>=A0=A0=A0 You asked</strong></span></span></div>
<div class=3D"im">
<div><span style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><span=
><font face=3D"Times New Roman" color=3D"#000000" size=3D"3">=A0=A0=A0 </fo=
nt></span></span></div>
<div><span style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><span=
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0</span>MPLS-IP encapsulation is valid for MP=
LS-TP when IP addressing is being used. </span></div>
<div><span style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><span=
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0</span>(i.e in this case ACH will not be use=
d).=A0=A0</span><span style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: A=
rial">If we follow the procedures defined in BFD-base </span></div>

<div><span style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><span=
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0</span>drafts or BFD-MPLS, how exactly is it=
 expected to achieve CV (connectivity verification) </span></div>
<div><span style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><span=
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0</span>when ACH is not used in MPLS-TP? Is i=
t acheived using Source IP comparison?<span>=A0</span></span></div>
<div><span style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><span=
></span></span>=A0</div></div>
<div><span style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><span=
><strong>=A0=A0=A0 Yes,.see cc-cv-rdi draft 03 version section 3=A0</strong=
></span></span></div>
<div><span style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><span=
>
<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 12pt 21.6pt"><font size=3D"=
3"><font color=3D"#000000"><font face=3D"Courier New"><span lang=3D"EN">A f=
urther artifact of IP encapsulation is that CV mis-connectivity defect dete=
ction can be performed by inferring MEP_ID on the basis of the combination =
of the source IP address and </span>&quot;<span lang=3D"EN">my discriminato=
r</span>&quot; fields.<span lang=3D"EN"></span></font></font></font></p>
</span></span></div>
<div class=3D"im"><pre style=3D"MARGIN-LEFT: 0.25in"><b><font face=3D"Couri=
er New" size=3D"2"><span lang=3D"EN" style=3D"FONT-WEIGHT: bold; FONT-SIZE:=
 10pt"></span></font></b></pre>
<div style=3D"MARGIN-LEFT: 0.5in"><font color=3D"blue" size=3D"2"><span lan=
g=3D"EN" style=3D"FONT-SIZE: 10pt; COLOR: blue">2. </span></font></div>
<div style=3D"MARGIN-LEFT: 0.5in"><font color=3D"blue" size=3D"2"><span lan=
g=3D"EN" style=3D"FONT-SIZE: 10pt; COLOR: blue">Is the usage of ACH TLV=92s=
 allowed when MPLS-ACH-IP encapsulation is used in MPLS-TP? </span></font><=
/div>
<div style=3D"MARGIN-LEFT: 0.5in"><font color=3D"blue" size=3D"2"><span lan=
g=3D"EN" style=3D"FONT-SIZE: 10pt; COLOR: blue">Question arises from the fa=
ct that to do CV in MPLS-TP, MEP identification (carrying MEP TLV) </span><=
/font></div>

<div style=3D"MARGIN-LEFT: 0.5in"><font color=3D"blue" size=3D"2"><span lan=
g=3D"EN" style=3D"FONT-SIZE: 10pt; COLOR: blue">is required and thus ACH ne=
eds to be included even if IP addressing is available. </span></font></div>
<div style=3D"MARGIN-LEFT: 0.5in"><span lang=3D"EN" style=3D"FONT-SIZE: 10p=
t; COLOR: blue">Else there should be a mechanism to do CV with IP (Ref: Que=
stion 1)<span><font face=3D"Arial">=A0</font></span></span></div>
<div style=3D"MARGIN-LEFT: 0.5in"><span lang=3D"EN" style=3D"FONT-SIZE: 10p=
t; COLOR: blue"><span><font face=3D"Arial"><strong></strong></font></span><=
/span>=A0</div></div>
<div style=3D"MARGIN-LEFT: 0.5in"><span lang=3D"EN" style=3D"FONT-SIZE: 10p=
t; COLOR: blue"><span><font face=3D"Arial"><strong>The CC-CV-RDI draft depr=
ecated the use of the ACH TLV in favor of a trailing TLV for MEP ID, and we=
 do not mandate the use of the trailing TLV when MPLS-ACH-IP encapsulation=
=A0would be used (different code points).</strong></font></span></span></di=
v>

<div style=3D"MARGIN-LEFT: 0.5in"><span lang=3D"EN" style=3D"FONT-SIZE: 10p=
t; COLOR: blue"><span><strong></strong></span></span>=A0</div>
<div style=3D"MARGIN-LEFT: 0.5in"><span lang=3D"EN" style=3D"FONT-SIZE: 10p=
t; COLOR: blue"><span><font face=3D"Arial"><strong>I hope this helps</stron=
g></font></span></span></div>
<div style=3D"MARGIN-LEFT: 0.5in"><strong><span lang=3D"EN" style=3D"FONT-S=
IZE: 10pt; COLOR: blue"><span><font face=3D"Arial">Dave</font>=A0</span></s=
pan><span style=3D"COLOR: blue"></span></strong></div>
<div><font face=3D"Arial" color=3D"#0000ff" size=3D"2"></font>=A0</div>
<div><font face=3D"Arial" color=3D"#0000ff" size=3D"2"></font>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div></div></blockquote></div><br>

--0016367faf831e59c9049bed4b5c--

From Alexander.Vainshtein@ecitele.com  Thu Feb 10 06:38:14 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1CA8C3A69C9; Thu, 10 Feb 2011 06:38:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 Z0qSXzqbMoJG; Thu, 10 Feb 2011 06:38:13 -0800 (PST)
Received: from ilptbmg01.ecitele.com (ilptbmg01-out.ecitele.com [147.234.242.234]) by core3.amsl.com (Postfix) with ESMTP id 275E23A69C6; Thu, 10 Feb 2011 06:38:11 -0800 (PST)
X-AuditID: 93eaf2e7-b7b47ae000005f02-46-4d53f86198c5
Received: from ilptexch01.ecitele.com ( [172.31.244.40]) by ilptbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id 31.69.24322.168F35D4; Thu, 10 Feb 2011 16:38:26 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ilptexch01.ecitele.com ([172.31.244.40]) with mapi; Thu, 10 Feb 2011 16:38:21 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: David Allan I <david.i.allan@ericsson.com>
Date: Thu, 10 Feb 2011 16:38:20 +0200
Thread-Topic: [mpls] [mpls-tp] mpls wg last call	on draft-ietf-mpls-tp-cc-cv-rdi-03
Thread-Index: AcvDrJpCvXJpavHRRhKBBXlDzw1/zAFFYIGQABGDQCAAAKcQEAACic4AAAbIaBA=
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D6FB9CA07E@ILPTMAIL02.ecitele.com>
References: <4D4AB81D.3080907@pi.nu> <06c901cbc8d4$d682a820$8387f860$@com> <60C093A41B5E45409A19D42CF7786DFD51CDF3F790@EUSAACMS0703.eamcs.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, Robert Rennison <Robert.Rennison@ecitele.com>
Subject: Re: [mpls-tp] [mpls] mpls wg last call	on	draft-ietf-mpls-tp-cc-cv-rdi-03
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Feb 2011 14:38:14 -0000

Dave, and all,
To avoid any misinterpretation, please consider the original email as my LC=
 comment.

Regards,
     Sasha


-----Original Message-----
From: Alexander Vainshtein=20
Sent: Thursday, February 10, 2011 1:36 PM
To: 'David Allan I'
Cc: Mach Chen; 'Loa Andersson'; mpls-tp@ietf.org; mpls@ietf.org; Robert Ren=
nison
Subject: RE: [mpls] [mpls-tp] mpls wg last call on draft-ietf-mpls-tp-cc-cv=
-rdi-03

Dave and all,
I'd like to remind you that Rob and I have already questioned the decision =
to change the BFD state machine by disabling in some case the Poll/Final se=
quence.

The situation as presented in the draft seems to introduce even more proble=
ms.=20
E.g., RFC 5885 allows to run BFD in VCCV without UDP/IP encapsulation but f=
ollows the procedures specified in RFC 5880 and 5881 which, to the best of =
my understanding, include usage of Poll/Final sequence.

It is my understanding that BFD for an MPLS-TP LSP would look exactly as BF=
D in VCCV (including the same code point).
If this is correct, how should the implementation distinguish between "PWE3=
 mode" (where poll/final are used) and "MPLS-TP mode where they seem to be =
prohibited?

Regards,
     Sasha

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Dav=
id Allan I
Sent: Thursday, February 10, 2011 1:09 PM
To: Mach Chen; 'Loa Andersson'; mpls-tp@ietf.org; mpls@ietf.org; ahmpls-tp@=
lists.itu.int
Subject: Re: [mpls] [mpls-tp] mpls wg last call on draft-ietf-mpls-tp-cc-cv=
-rdi-03

=20

Hi Mach:=20

Thanks for the review

>I read the draft, here are some comments, please consider:

>1.Section 3.5, last sentence of first paragraph

>"Poll/final discipline can only used for VCCV and UDP/IP encapsulated BFD.=
"
>There is a "be" lost between "can" and "only".

Good catch, will fix.

>2.Section 3.5.2
>"1. BFD control packets are received with an unexpected encapsulation (mis=
-connectivity defect), these include:=20
>          - a PW receiving a packet with a GAL", Since GAL can be used=20
>for PW(http://tools.ietf.org/html/draft-ietf-pwe3-mpls-tp-gal-in-pw-00), t=
his should not be a defect. Suggest to remove it.

We'll review and edit accordingly.

>3 Section 3.5.2
>" 4. Receipt of an expected session discriminator with an unexpected label=
 (mis-connectivity defect).", For a receiver, how does it know that the ses=
sion >discriminator is valid but the label is invalid? IMHO, this defect is=
 just another description of defect 3 . Suggest to remove it.

If the session discriminator exists in the BFD database, it is superficiall=
y a valid descriminator but the label of arrival can be incorrect. This may=
 indicate an implementation problem at the source MEP. What we were referri=
ng to in '3' was a session discriminator that did not exist in the local da=
tabase, BFD had never handed it out hence it could not be found.

>4.Section 3.5.4.2
>" Exit from a misconfiguration defect occurs when two consecutive CC or=20
>CV frames have been received with the expected M bit setting." IMHO, this =
sentence is little bit vague, and since this draft only defines for P2P LSP=
, why not just say "...with M bit clear."

OK

>5. Section 3.5.4.3
>"Exit from a mis-connectivity defect state occurs when no CV messages=20
>have been received with an incorrect source MEP-ID for a period of 3.5 sec=
onds.", since there are several defects listed in Section 3.5.2 and this is=
 only one condition for exiting from a mis-connectivity defect state. How a=
bout "Exit >from a mis-connectivity defect state occurs when no CV messages=
 with mis-connectivity defects have been received for a period of 3.5 secon=
ds "

That seems to be more accurate, I'd replace "with...." with "indicating an =
on-going mis-connectivity defect has been....". Simply wordsmithing.

>6. Section 3.5.5

>In Figure 5, seems that it is lack of "AIS-LDI, LKR" inputs for DOWN state=
.

Good catch. Will fix

Cheers
Dave



> -----Original Message-----
> From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On=20
> Behalf Of Loa Andersson
> Sent: Thursday, February 03, 2011 10:14 PM
> To: mpls-tp@ietf.org; mpls@ietf.org; ahmpls-tp@lists.itu.int
> Subject: [mpls-tp] mpls wg last call on
> draft-ietf-mpls-tp-cc-cv-rdi-03
>=20
> Working Group,
>=20
> this is to start a four week working group last call on "Proactive=20
> Connectivity Verification, Continuity Check and Remote Defect=20
> indication for MPLS Transport Profile"
> (draft-ietf-mpls-tp-cc-cv-rdi-03.txt).
>=20
> Please send comments to the mpls-tp@ietf.org mailing list.
>=20
> This working group last call ends on February 28, 2011.
>=20
>=20
> Loa, George and Ross
>=20
> MPLS wg co-chairs
> --
>=20
>=20
> Loa Andersson                         email:
> loa.andersson@ericsson.com
> Sr Strategy and Standards Manager            loa@pi.nu
> Ericsson Inc                          phone: +46 10 717 52 13
>                                               +46 767 72 92 13=20
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From david.i.allan@ericsson.com  Thu Feb 10 07:36:24 2011
Return-Path: <david.i.allan@ericsson.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A4FBB3A69D1; Thu, 10 Feb 2011 07:36:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 NTgt6PHUcSaK; Thu, 10 Feb 2011 07:36:19 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id 619FB3A67EC; Thu, 10 Feb 2011 07:36:19 -0800 (PST)
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 p1AGKaZB008099; Thu, 10 Feb 2011 10:20:40 -0600
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.66]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Thu, 10 Feb 2011 10:36:29 -0500
From: David Allan I <david.i.allan@ericsson.com>
To: Mukund Mani <mukund.mani@gmail.com>
Date: Thu, 10 Feb 2011 10:36:28 -0500
Thread-Topic: [mpls-tp] MPLS-ACH-IP and MPLS-IP encapsulations for BFD in MPLS-TP
Thread-Index: AcvJI8X6htI7HsitSCKDSKGMWTnO6gAFDQdQ
Message-ID: <60C093A41B5E45409A19D42CF7786DFD51CDF3F8EE@EUSAACMS0703.eamcs.ericsson.se>
References: <AANLkTi=zeJTVn8gx_ZFefaS6adnFb20kWAnpDnDo2fP1@mail.gmail.com> <60C093A41B5E45409A19D42CF7786DFD51CDEF1D53@EUSAACMS0703.eamcs.ericsson.se> <AANLkTim_tQ46Ox=vYLm2fuzV=FP5zkOhM=b7m6qou2We@mail.gmail.com>
In-Reply-To: <AANLkTim_tQ46Ox=vYLm2fuzV=FP5zkOhM=b7m6qou2We@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_60C093A41B5E45409A19D42CF7786DFD51CDF3F8EEEUSAACMS0703e_"
MIME-Version: 1.0
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls-tp] MPLS-ACH-IP and MPLS-IP encapsulations for BFD in MPLS-TP
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Feb 2011 15:36:24 -0000

--_000_60C093A41B5E45409A19D42CF7786DFD51CDF3F8EEEUSAACMS0703e_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Mikund:

If I understand your question correctly, you would need knowledge of the IP=
 address of the source of the BFD packets.

cheers
Dave

________________________________
From: Mukund Mani [mailto:mukund.mani@gmail.com]
Sent: Thursday, February 10, 2011 5:10 AM
To: David Allan I
Cc: rtg-bfd@ietf.org; mpls-tp@ietf.org
Subject: Re: [mpls-tp] MPLS-ACH-IP and MPLS-IP encapsulations for BFD in MP=
LS-TP

Hi Dave

Not really clear on the first one.. Here we are not including trailing MEP =
TLV. How do we do CV for the first BFD packet with MPLS-IP encap ?

With Regards
Mukund
On Wed, Feb 9, 2011 at 1:25 PM, David Allan I <david.i.allan@ericsson.com<m=
ailto:david.i.allan@ericsson.com>> wrote:
HI Mikund:

    You asked

          MPLS-IP encapsulation is valid for MPLS-TP when IP addressing is =
being used.
          (i.e in this case ACH will not be used).  If we follow the proced=
ures defined in BFD-base
          drafts or BFD-MPLS, how exactly is it expected to achieve CV (con=
nectivity verification)
          when ACH is not used in MPLS-TP? Is it acheived using Source IP c=
omparison?

    Yes,.see cc-cv-rdi draft 03 version section 3
A further artifact of IP encapsulation is that CV mis-connectivity defect d=
etection can be performed by inferring MEP_ID on the basis of the combinati=
on of the source IP address and "my discriminator" fields.

2.
Is the usage of ACH TLV's allowed when MPLS-ACH-IP encapsulation is used in=
 MPLS-TP?
Question arises from the fact that to do CV in MPLS-TP, MEP identification =
(carrying MEP TLV)
is required and thus ACH needs to be included even if IP addressing is avai=
lable.
Else there should be a mechanism to do CV with IP (Ref: Question 1)

The CC-CV-RDI draft deprecated the use of the ACH TLV in favor of a trailin=
g TLV for MEP ID, and we do not mandate the use of the trailing TLV when MP=
LS-ACH-IP encapsulation would be used (different code points).

I hope this helps
Dave


















--_000_60C093A41B5E45409A19D42CF7786DFD51CDF3F8EEEUSAACMS0703e_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6001.18542" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D671163415-10022011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Hi Mikund:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D671163415-10022011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D671163415-10022011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>If I understand your question correctly, you would=
 need=20
knowledge of the IP address of the source of the BFD packets.=20
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D671163415-10022011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D671163415-10022011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>cheers</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D671163415-10022011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Dave</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Mukund Mani [mailto:mukund.mani@g=
mail.com]=20
<BR><B>Sent:</B> Thursday, February 10, 2011 5:10 AM<BR><B>To:</B> David Al=
lan=20
I<BR><B>Cc:</B> rtg-bfd@ietf.org; mpls-tp@ietf.org<BR><B>Subject:</B> Re:=20
[mpls-tp] MPLS-ACH-IP and MPLS-IP encapsulations for BFD in=20
MPLS-TP<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>Hi Dave</DIV>
<DIV>&nbsp;</DIV>
<DIV>Not really clear on the first one.. Here we are not including trailing=
 MEP=20
TLV.&nbsp;How do we do&nbsp;CV for the first BFD packet with MPLS-IP encap =
?=20
</DIV>
<DIV>&nbsp;</DIV>
<DIV>With Regards</DIV>
<DIV>Mukund<BR></DIV>
<DIV class=3Dgmail_quote>On Wed, Feb 9, 2011 at 1:25 PM, David Allan I <SPA=
N=20
dir=3Dltr>&lt;<A=20
href=3D"mailto:david.i.allan@ericsson.com">david.i.allan@ericsson.com</A>&g=
t;</SPAN>=20
wrote:<BR>
<BLOCKQUOTE class=3Dgmail_quote=20
style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1p=
x solid">
  <DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0000ff size=
=3D2><STRONG>HI=20
  Mikund:</STRONG></FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN><FONT face=3DArial color=3D#0000ff=20
  size=3D2><STRONG></STRONG></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SPAN><STRONG>=
&nbsp;&nbsp;&nbsp;=20
  You asked</STRONG></SPAN></SPAN></DIV>
  <DIV class=3Dim>
  <DIV><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SPAN><FONT=20
  face=3D"Times New Roman" color=3D#000000 size=3D3>&nbsp;&nbsp;&nbsp;=20
  </FONT></SPAN></SPAN></DIV>
  <DIV><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SPAN>&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN>MPLS-IP=20
  encapsulation is valid for MPLS-TP when IP addressing is being used.=20
  </SPAN></DIV>
  <DIV><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SPAN>&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN>(i.e=20
  in this case ACH will not be used).&nbsp;&nbsp;</SPAN><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">If we follow t=
he=20
  procedures defined in BFD-base </SPAN></DIV>
  <DIV><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SPAN>&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN>drafts=20
  or BFD-MPLS, how exactly is it expected to achieve CV (connectivity=20
  verification) </SPAN></DIV>
  <DIV><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SPAN>&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN>when=20
  ACH is not used in MPLS-TP? Is it acheived using Source IP=20
  comparison?<SPAN>&nbsp;</SPAN></SPAN></DIV>
  <DIV><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SPAN></SPAN><=
/SPAN>&nbsp;</DIV></DIV>
  <DIV><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SPAN><STRONG>=
&nbsp;&nbsp;&nbsp;=20
  Yes,.see cc-cv-rdi draft 03 version section=20
  3&nbsp;</STRONG></SPAN></SPAN></DIV>
  <DIV><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SP=
AN>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 12pt 21.6pt"><FONT size=3D3=
><FONT=20
  color=3D#000000><FONT face=3D"Courier New"><SPAN lang=3DEN>A further arti=
fact of IP=20
  encapsulation is that CV mis-connectivity defect detection can be perform=
ed by=20
  inferring MEP_ID on the basis of the combination of the source IP address=
 and=20
  </SPAN>"<SPAN lang=3DEN>my discriminator</SPAN>" fields.<SPAN=20
  lang=3DEN></SPAN></FONT></FONT></FONT></P></SPAN></SPAN></DIV>
  <DIV class=3Dim><PRE style=3D"MARGIN-LEFT: 0.25in"><B><FONT face=3D"Couri=
er New" size=3D2><SPAN lang=3DEN style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10p=
t"></SPAN></FONT></B></PRE>
  <DIV style=3D"MARGIN-LEFT: 0.5in"><FONT color=3Dblue size=3D2><SPAN lang=
=3DEN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue">2. </SPAN></FONT></DIV>
  <DIV style=3D"MARGIN-LEFT: 0.5in"><FONT color=3Dblue size=3D2><SPAN lang=
=3DEN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue">Is the usage of ACH TLV&#8217;s al=
lowed when=20
  MPLS-ACH-IP encapsulation is used in MPLS-TP? </SPAN></FONT></DIV>
  <DIV style=3D"MARGIN-LEFT: 0.5in"><FONT color=3Dblue size=3D2><SPAN lang=
=3DEN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue">Question arises from the fact that=
 to do=20
  CV in MPLS-TP, MEP identification (carrying MEP TLV) </SPAN></FONT></DIV>
  <DIV style=3D"MARGIN-LEFT: 0.5in"><FONT color=3Dblue size=3D2><SPAN lang=
=3DEN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue">is required and thus ACH needs to =
be=20
  included even if IP addressing is available. </SPAN></FONT></DIV>
  <DIV style=3D"MARGIN-LEFT: 0.5in"><SPAN lang=3DEN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue">Else there should be a mechanism t=
o do CV=20
  with IP (Ref: Question 1)<SPAN><FONT=20
  face=3DArial>&nbsp;</FONT></SPAN></SPAN></DIV>
  <DIV style=3D"MARGIN-LEFT: 0.5in"><SPAN lang=3DEN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue"><SPAN><FONT=20
  face=3DArial><STRONG></STRONG></FONT></SPAN></SPAN>&nbsp;</DIV></DIV>
  <DIV style=3D"MARGIN-LEFT: 0.5in"><SPAN lang=3DEN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue"><SPAN><FONT face=3DArial><STRONG>T=
he=20
  CC-CV-RDI draft deprecated the use of the ACH TLV in favor of a trailing =
TLV=20
  for MEP ID, and we do not mandate the use of the trailing TLV when MPLS-A=
CH-IP=20
  encapsulation&nbsp;would be used (different code=20
  points).</STRONG></FONT></SPAN></SPAN></DIV>
  <DIV style=3D"MARGIN-LEFT: 0.5in"><SPAN lang=3DEN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue"><SPAN><STRONG></STRONG></SPAN></SP=
AN>&nbsp;</DIV>
  <DIV style=3D"MARGIN-LEFT: 0.5in"><SPAN lang=3DEN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue"><SPAN><FONT face=3DArial><STRONG>I=
 hope=20
  this helps</STRONG></FONT></SPAN></SPAN></DIV>
  <DIV style=3D"MARGIN-LEFT: 0.5in"><STRONG><SPAN lang=3DEN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue"><SPAN><FONT=20
  face=3DArial>Dave</FONT>&nbsp;</SPAN></SPAN><SPAN=20
  style=3D"COLOR: blue"></SPAN></STRONG></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV></DIV></BLOCKQUOTE></DIV><BR></BODY></HTML>

--_000_60C093A41B5E45409A19D42CF7786DFD51CDF3F8EEEUSAACMS0703e_--

From linda.dunbar@huawei.com  Thu Feb 10 08:36:27 2011
Return-Path: <linda.dunbar@huawei.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ADB953A67A2 for <mpls-tp@core3.amsl.com>; Thu, 10 Feb 2011 08:36:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.5
X-Spam-Level: 
X-Spam-Status: No, score=-3.5 tagged_above=-999 required=5 tests=[AWL=-1.989,  BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001,  MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4]
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 f9+qify2i61g for <mpls-tp@core3.amsl.com>; Thu, 10 Feb 2011 08:36:26 -0800 (PST)
Received: from usaga04-in.huawei.com (usaga04-in.huawei.com [206.16.17.180]) by core3.amsl.com (Postfix) with ESMTP id 632FF3A659A for <mpls-tp@ietf.org>; Thu, 10 Feb 2011 08:36:26 -0800 (PST)
Received: from huawei.com (usaga04-in [172.18.4.101]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LGE00ESQU51KS@usaga04-in.huawei.com> for mpls-tp@ietf.org; Thu, 10 Feb 2011 10:36:38 -0600 (CST)
Received: from dfweml201-edg.china.huawei.com ([172.18.9.107]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPS id <0LGE00MZRU4X3Q@usaga04-in.huawei.com> for mpls-tp@ietf.org; Thu, 10 Feb 2011 10:36:37 -0600 (CST)
Received: from DFWEML402-HUB.china.huawei.com (10.193.5.102) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.270.1; Thu, 10 Feb 2011 08:36:34 -0800
Received: from DFWEML501-MBX.china.huawei.com ([fe80::c52a:9e19:87eb:4531]) by DFWEML402-HUB.china.huawei.com ([::1]) with mapi id 14.01.0270.001; Thu, 10 Feb 2011 08:36:34 -0800
Date: Thu, 10 Feb 2011 16:36:34 +0000
From: Linda Dunbar <linda.dunbar@huawei.com>
X-Originating-IP: [10.124.12.77]
To: "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Message-id: <4A95BA014132FF49AE685FAB4B9F17F6A82496@DFWEML501-MBX.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_AcmXHOciVfIEMHQUpz5elA)"
Content-language: en-US
Accept-Language: en-US
Thread-topic: MPLS WG Last call on draft-ietf-mpls-loss-delay-01
Thread-index: AcvDrJhC7YZ5M3jNY0iGGGg2vMPKUACx1e2wAFC2+fAAYmjdQA==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Subject: [mpls-tp] FW: MPLS WG Last call on draft-ietf-mpls-loss-delay-01
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Feb 2011 16:36:28 -0000

--Boundary_(ID_AcmXHOciVfIEMHQUpz5elA)
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: base64

TXkgYXBvbG9neSBpZiB5b3Whr3ZlIHNlZW4gdGhpcyBlbWFpbC4gTXBscy10cCByZWplY3RlZCB0
aGlzIG9uZSBkdWUgdG8gbXkgZW1haWwgYWRkcmVzcyBjaGFuZ2UsIHNvIEkgYW0ganVzdCByZS1z
ZW5kIGl0LiCoQ0xpbmRhIER1bmJhcg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18NCkZyb206IExpbmRhIER1bmJhcg0KU2VudDogMjAxMcTqMtTCOMjVIDE1
OjU4DQpUbzogJ1Jvc3MgQ2FsbG9uJzsgbXBscy10cEBpZXRmLm9yZzsgbXBsc0BpZXRmLm9yZzsg
YWhtcGxzLXRwQGxpc3RzLml0dS5pbnQNClN1YmplY3Q6IFJFOiBNUExTIFdHIExhc3QgY2FsbCBv
biBkcmFmdC1pZXRmLW1wbHMtbG9zcy1kZWxheS0wMQ0KDQoNCkkgaGF2ZSBzb21lIGlzc3VlcyB3
aXRoIHRoaXMgZHJhZnQ6DQpUaGVyZSBoYWQgYmVlbiBhIGxvdCBvZiBkaXNjdXNzaW9ucyBvbiBl
bWFpbCBsaXN0IG9uIHdoYXQgc2hvdWxkIEluaXRpYXRvciAocXVlcmllcikgZG8gd2hlbiBub3Qg
cmVjZWl2aW5nIGEgcmVzcG9uc2UgZnJvbSBmYXIgZW5kLg0KDQpCZW4gSmVua2lucyBzdWdnZXN0
ZWQgdGhlIGZvbGxvd2luZyB0ZXh0IChodHRwOi8vd3d3LmlldGYub3JnL21haWwtYXJjaGl2ZS93
ZWIvbXBscy9jdXJyZW50L21zZzA1Njk2Lmh0bWwpIHdoaWNoIGlzIG5vdCBpbmNvcnBvcmF0ZWQg
dG8gdGhpcyBuZXcgZHJhZnQgeWV0Lg0KDQogICAgICBXaGVuIGluaXRpYXRpbmcgYW4gTE0gb3Bl
cmF0aW9uLCB0aGUgZmFyIGVuZCBtYXkgcmVxdWlyZSBhIHBlcmlvZCBvZiB0aW1lIHRvIGJlY29t
ZSByZWFkeSBmb3IgdGhlIHJlcXVlc3RlZCBtZWFzdXJlbWVudCBvcGVyYXRpb24gb3IgdGhlIGZh
ciBlbmQgbWF5IG5vdCBiZSBhYmxlIHRvIHN1cHBvcnQgdGhlIHJlcXVlc3RlZCBtZWFzdXJlbWVu
dC4gVW5kZXIgdGhvc2UgY2lyY3Vtc3RhbmNlcywgTE0gcXVlcmllcyBNQVkgc2ltcGx5IGJlIGRp
c2NhcmRlZCwgYW5kIHRoZSBxdWVyaWVyIGV4cGVjdGluZyBhIHJlc3BvbnNlIFNIT1VMRCBiZSBw
cmVwYXJlZCBmb3IgdGhpcyBzaXR1YXRpb24uIEFsdGVybmF0aXZlbHksIHRoZSByZWNlaXZlciBN
QVkgcmVzcG9uZCwgcG9zc2libHkgaW4gYSByYXRlLWxpbWl0ZWQgbWFubmVyLCB0byBxdWVyaWVz
IHJlY2VpdmVkIGR1cmluZyB0aGlzIHBlcmlvZCB3aXRoIGFuIGFwcHJvcHJpYXRlIG5vdGlmaWNh
dGlvbiBjb2RlLiAgVGhlIHF1ZXJpZXIgc2hvdWxkIGFib3J0IHRoZSBtZWFzdXJlbWVudCBhZnRl
ciBub3QgcmVjZWl2aW5nIGFueSBwb3NpdGl2ZSBmZWVkYmFjayB3aGVuIGEgc3BlY2lmaWVkIHRp
bWVyIGV4cGlyZXMuDQoNCg0KDQpTZWN0aW9uIDMuNS4zOiBJdCBzdGF0ZWQ6DQogICAgICAgV2hl
biBhIHF1ZXJ5IGlzIHJlY2VpdmVkIHdpdGggYSBTZXNzaW9uIFF1ZXJ5IEludGVydmFsIHRoYXQg
aXMgdG9vIGxvdyBmb3IgdGhlIHJlY2VpdmVyIHRvIHN1cHBvcnQsIHRoZSByZWNlaXZlciBTSE9V
TEQgaW5jbHVkZSB0aGlzIG9iamVjdCB3aGVuIGl0IGdlbmVyYXRlcyBhbiBlcnJvciByZXNwb25z
ZS4NCg0KUXVlc3Rpb246DQogICAgICBXaGljaCBlcnJvciBjb2RlIHNob3VsZCBiZSB1c2VkPyBJ
cyBpdCAweDE4OkVycm9yIC0gVW5zdXBwb3J0ZWQgUXVlcnkgSW50ZXJ2YWw/IElmIFllcywgc2hv
dWxkIGFkZCB0aGlzIHRvIHRoZSBzZW50ZW5jZS4NCg0KICAgICAgV2hhdCBpZiB0aGUgUXVlcmll
ciBpbmRpY2F0ZXMgIjB4MjogTm8gUmVzcG9uc2UgUmVxdWVzdGVkIj8NCg0KU2VjdGlvbiA0LjEu
NToNCiogICAgICAgU2hvdWxkIGFsbG93IHRoZSBMb3NzIG1lYXN1cmVtZW50IHRvIGJlIGNhbGN1
bGF0ZWQgc29tZXdoZXJlIGVsc2UsIGluIGNhc2UgdGhlIGluaXRpYXRvciAocXVlcmllcikgZG9l
c24ndCBoYXZlIHRoZSBjYXBhY2l0eSB0byBkbyB0aGUgY2FsY3VsYXRpb24uDQoqICAgICAgIFNo
b3VsZCBhZGQgYSBkZXNjcmlwdGlvbiB0aGF0IG1lYXN1cmVtZW50IGlzIHRvIGJlIHN0b3BwZWQg
d2hlbiBmYXIgZW5kIG5vdCByZXNwb25kIGFueW1vcmUuDQoNCg0KDQpMaW5kYSBEdW5iYXINCg0K
DQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogbXBscy1ib3VuY2VzQGlldGYub3Jn
IFttYWlsdG86bXBscy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgUm9zcyBDYWxsb24N
ClNlbnQ6IFN1bmRheSwgRmVicnVhcnkgMDYsIDIwMTEgOTozMyBQTQ0KVG86IG1wbHMtdHBAaWV0
Zi5vcmc7IG1wbHNAaWV0Zi5vcmc7IGFobXBscy10cEBsaXN0cy5pdHUuaW50DQpTdWJqZWN0OiBb
bXBsc10gTVBMUyBXRyBsYXN0IGNhbGwgb24gZHJhZnQtaWV0Zi1tcGxzLWxvc3MtZGVsYXktMDEN
Cg0KV29ya2luZyBHcm91cCwNCg0KVGhpcyBpcyB0byBzdGFydCBhIGZvdXIgd2VlayB3b3JraW5n
IGdyb3VwIGxhc3QgY2FsbCBvbg0KIiBQYWNrZXQgTG9zcyBhbmQgRGVsYXkgTWVhc3VyZW1lbnQg
Zm9yIE1QTFMgTmV0d29ya3MiDQooZHJhZnQtaWV0Zi1tcGxzLWxvc3MtZGVsYXktMDEpLg0KDQpQ
bGVhc2Ugc2VuZCBjb21tZW50cyB0byB0aGUgbXBscyBhdCBpZXRmLm9yZyBtYWlsaW5nIGxpc3Qu
DQoNCkFsc28sIHBsZWFzZSBub3RlIHRoYXQgdGhlIHJlbGF0ZWQgZG9jdW1lbnQNCiIgZHJhZnQt
aWV0Zi1tcGxzLXRwLWxvc3MtZGVsYXktcHJvZmlsZS0wMi50eHQiIGlzIGJlaW5nIGxhc3QgY2Fs
bGVkIGluDQpwYXJhbGxlbCBvbiB0aGUgbXBscy10cCBlbWFpbCBsaXN0IChtcGxzLXRwIGF0IGll
dGYub3JnKS4NCg0KVGhpcyB3b3JraW5nIGdyb3VwIGxhc3QgY2FsbCBlbmRzIG9uIE1vbmRheSBN
YXJjaCA3LCAyMDExLg0KDQpSb3NzLCBMb2EsIGFuZCBHZW9yZ2UNCg0KTVBMUyBXRyBjby1jaGFp
cnMNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQptcGxz
IG1haWxpbmcgbGlzdA0KbXBsc0BpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9tcGxzDQoNCg==

--Boundary_(ID_AcmXHOciVfIEMHQUpz5elA)
Content-type: text/html; charset=gb2312
Content-transfer-encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dgb2312">
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Calibri" size=3D"2"><span style=3D"font-size:11pt;">
<div><font color=3D"#1F497D">My apology if you=A1=AFve seen this email. Mpl=
s-tp rejected this one due to my email address change, so I am just re-send=
 it. =A8CLinda Dunbar</font></div>
<div><font face=3D"Times New Roman" color=3D"#1F497D">&nbsp;</font></div>
<div><font face=3D"Tahoma" size=3D"2"><span style=3D"font-size:10pt;">_____=
________________________________________<br>

<b>From:</b> Linda Dunbar <br>

<b>Sent:</b> 2011<font face=3D"=CB=CE=CC=E5">=C4=EA</font>2<font face=3D"=
=CB=CE=CC=E5">=D4=C2</font>8<font face=3D"=CB=CE=CC=E5">=C8=D5</font> 15:58=
<br>

<b>To:</b> 'Ross Callon'; mpls-tp@ietf.org; mpls@ietf.org; ahmpls-tp@lists.=
itu.int<br>

<b>Subject:</b> RE: MPLS WG Last call on draft-ietf-mpls-loss-delay-01 </sp=
an></font></div>
<div><font face=3D"Times New Roman">&nbsp;</font></div>
<div><font face=3D"Times New Roman">&nbsp;</font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">I=
 have some issues with this draft: </span></font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">T=
here had been a lot of discussions on email list on what should Initiator (=
querier) do when not receiving a response from far end. </span></font></div=
>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">&=
nbsp;</span></font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">B=
en Jenkins suggested the following text (<a href=3D"http://www.ietf.org/mai=
l-archive/web/mpls/current/msg05696.html"><font color=3D"blue"><u>http://ww=
w.ietf.org/mail-archive/web/mpls/current/msg05696.html</u></font></a>)
which is not incorporated to this new draft yet.&nbsp; </span></font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">&=
nbsp;</span></font></div>
<div style=3D"padding-left:36pt;"><font face=3D"Consolas" size=3D"2"><span =
style=3D"font-size:10.5pt;"><i>When initiating an LM operation, the far end=
 may require a period of time to become ready for the requested measurement=
 operation or the far end may not be able
to support the requested measurement. Under those circumstances, LM queries=
 MAY simply be discarded, and the querier expecting a response SHOULD be pr=
epared for this situation. Alternatively, the receiver MAY respond, possibl=
y in a rate-limited manner, to queries
received during this period with an appropriate notification code.&nbsp; Th=
e querier should abort the measurement after not receiving any positive fee=
dback when a specified timer expires.&nbsp; </i></span></font></div>
<div><font face=3D"Times New Roman" size=3D"2"><span style=3D"font-size:10.=
5pt;">&nbsp;</span></font></div>
<div><font face=3D"Times New Roman" size=3D"2"><span style=3D"font-size:10.=
5pt;">&nbsp;</span></font></div>
<div><font face=3D"Times New Roman" size=3D"2"><span style=3D"font-size:10.=
5pt;">&nbsp;</span></font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">S=
ection 3.5.3: It stated: </span></font></div>
<div style=3D"padding-left:36pt;"> <font face=3D"Courier" size=3D"2"><span =
style=3D"font-size:10pt;"><i>When a query is received with a Session Query =
Interval that is too low for the receiver to support, the receiver SHOULD i=
nclude this object when it generates an
error response. </i></span></font></div>
<div style=3D"padding-left:36pt;"><font face=3D"Times New Roman">&nbsp;</fo=
nt></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">Q=
uestion: </span></font></div>
<div style=3D"padding-left:36pt;"><font face=3D"Consolas" size=3D"2"><span =
style=3D"font-size:10.5pt;">Which error code should be used? Is it <font fa=
ce=3D"Courier" size=3D"2"><span style=3D"font-size:10pt;"><i>0x18:Error - U=
nsupported Query Interval</i></span></font><font face=3D"Courier" size=3D"2=
"><span style=3D"font-size:10pt;">?
</span></font>If Yes, should add this to the sentence.</span></font></div>
<div><font face=3D"Times New Roman" size=3D"2"><span style=3D"font-size:10.=
5pt;">&nbsp;</span></font></div>
<div style=3D"padding-left:36pt;"><font face=3D"Consolas" size=3D"2"><span =
style=3D"font-size:10.5pt;">What if the Querier<font face=3D"Courier" size=
=3D"2"><span style=3D"font-size:10pt;"> </span></font>indicates<font face=
=3D"Courier" size=3D"2"><span style=3D"font-size:10pt;">
&quot;0x2: No Response Requested&quot;? </span></font></span></font></div>
<div><font face=3D"Times New Roman">&nbsp;</font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">S=
ection 4.1.5:</span></font></div>
<ul style=3D"margin:0;padding-left:36pt;">
<font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">
<li>Should allow the Loss measurement to be calculated somewhere else, in c=
ase the initiator (querier) doesn't have the capacity to do the calculation=
.<font face=3D"Courier" size=3D"2"><span style=3D"font-size:10pt;"> </span>=
</font></li><li>Should add a description that measurement is to be stopped =
when far end not respond anymore. </li></span></font>
</ul>
<div style=3D"padding-left:36pt;"><font face=3D"Times New Roman">&nbsp;</fo=
nt></div>
<div style=3D"padding-left:36pt;"><font face=3D"Times New Roman">&nbsp;</fo=
nt></div>
<div style=3D"padding-left:36pt;"><font face=3D"Times New Roman">&nbsp;</fo=
nt></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">L=
inda Dunbar</span></font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">&=
nbsp;</span></font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">&=
nbsp;</span></font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">-=
----Original Message-----<br>

From: mpls-bounces@ietf.org [<a href=3D"mailto:mpls-bounces@ietf.org">mailt=
o:mpls-bounces@ietf.org</a>] On Behalf Of Ross Callon<br>

Sent: Sunday, February 06, 2011 9:33 PM<br>

To: mpls-tp@ietf.org; mpls@ietf.org; ahmpls-tp@lists.itu.int<br>

Subject: [mpls] MPLS WG last call on draft-ietf-mpls-loss-delay-01</span></=
font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">&=
nbsp;</span></font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">W=
orking Group,</span></font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">&=
nbsp;</span></font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">T=
his is to start a four week working group last call on</span></font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">&=
quot; Packet Loss and Delay Measurement for MPLS Networks&quot;</span></fon=
t></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">(=
draft-ietf-mpls-loss-delay-01).</span></font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">&=
nbsp;</span></font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">P=
lease send comments to the mpls at ietf.org mailing list.</span></font></di=
v>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">&=
nbsp;</span></font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">A=
lso, please note that the related document </span></font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">&=
quot; draft-ietf-mpls-tp-loss-delay-profile-02.txt&quot; is being last call=
ed in </span></font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">p=
arallel on the mpls-tp email list (mpls-tp at ietf.org). </span></font></di=
v>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">&=
nbsp;</span></font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">T=
his working group last call ends on Monday March 7, 2011.</span></font></di=
v>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">&=
nbsp;</span></font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">R=
oss, Loa, and George</span></font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">&=
nbsp;</span></font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">M=
PLS WG co-chairs</span></font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">_=
______________________________________________</span></font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">m=
pls mailing list</span></font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;">m=
pls@ietf.org</span></font></div>
<div><font face=3D"Consolas" size=3D"2"><span style=3D"font-size:10.5pt;"><=
a href=3D"https://www.ietf.org/mailman/listinfo/mpls">https://www.ietf.org/=
mailman/listinfo/mpls</a></span></font></div>
<div><font face=3D"Times New Roman" size=3D"2"><span style=3D"font-size:10.=
5pt;">&nbsp;</span></font></div>
</span></font>
</body>
</html>

--Boundary_(ID_AcmXHOciVfIEMHQUpz5elA)--

From lberger@labn.net  Thu Feb 10 10:40:09 2011
Return-Path: <lberger@labn.net>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 448473A69C3 for <mpls-tp@core3.amsl.com>; Thu, 10 Feb 2011 10:40:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
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 hRwWxN5ryKkA for <mpls-tp@core3.amsl.com>; Thu, 10 Feb 2011 10:40:09 -0800 (PST)
Received: from oproxy2-pub.bluehost.com (oproxy2-pub.bluehost.com [67.222.39.60]) by core3.amsl.com (Postfix) with SMTP id 170923A6824 for <mpls-tp@ietf.org>; Thu, 10 Feb 2011 10:40:09 -0800 (PST)
Received: (qmail 5403 invoked by uid 0); 10 Feb 2011 18:33:42 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy2.bluehost.com with SMTP; 10 Feb 2011 18:33:42 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=labn.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=NgKhyUWP4jG8OspW4zGvhcimu8oplkNUPgHOzpnjLOY5Kx9XuaX0ViCq/4cKZQIEzjejlZdqTEHdxJc8H6IeF8dM4EVBGRVWPOPe0iuUoWLIrEBL/We7glV4kkpMiWaE;
Received: from box313.bluehost.com ([69.89.31.113] helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.69) (envelope-from <lberger@labn.net>) id 1PnbKo-0006op-Cd; Thu, 10 Feb 2011 11:33:42 -0700
Message-ID: <4D542F85.6050607@labn.net>
Date: Thu, 10 Feb 2011 13:33:41 -0500
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: ccamp@ietf.org, "mpls-tp@ietf.org" <mpls-tp@ietf.org>,  "pwe3@ietf.org" <pwe3@ietf.org>, IESG <iesg@ietf.org>
References: <20110210141501.4357.50359.idtracker@localhost>
In-Reply-To: <20110210141501.4357.50359.idtracker@localhost>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Subject: Re: [mpls-tp] [CCAMP] I-D Action:draft-ietf-ccamp-mpls-tp-cp-framework-06.txt
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Feb 2011 18:40:09 -0000

FYI - this update was made to address IESG comments.

Changes include:

1) Update references
2) Minor editorial changes, including:
    - acronym expansion,
    - wordsmithing,
    - clarification of terms
3) Removal (and consequential reordering) of requirement 38 (was 
"Requirement removed.")
4) Added additional references
5) Added (PW) section 5.1.1. to parallel (LSP) section 4.2.1
6) Removed some out-of-scope text

Lou

On 2/10/2011 9:15 AM, Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Common Control and Measurement Plane Working Group of the IETF.
>
>
> 	Title           : MPLS-TP Control Plane Framework
> 	Author(s)       : L. Andersson, et al.
> 	Filename        : draft-ietf-ccamp-mpls-tp-cp-framework-06.txt
> 	Pages           : 55
> 	Date            : 2011-02-10
>
> The MPLS Transport Profile (MPLS-TP) supports static provisioning
> of transport paths via a Network Management System (NMS), and
> dynamic provisioning of transport paths via a control plane. This
> document provides the framework for MPLS-TP dynamic provisioning,
> and covers control plane addressing, routing, path computation,
> signaling, traffic engineering, and path recovery.  MPLS-TP uses
> GMPLS as the control plane for MPLS-TP Label Switched Paths
> (LSPs).  MPLS-TP also uses the Pseudowire (PW) control plane for
> Pseudowires (PWs).  Management plane functions are out of scope of
> this document.
>
> This document is a product of a joint Internet Engineering Task Force
> (IETF) / International Telecommunication Union Telecommunication
> Standardization Sector (ITU-T) effort to include an MPLS Transport
> Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge
> (PWE3) architectures to support the capabilities and functionalities
> of a packet transport network as defined by the ITU-T.
>
> This Informational Internet-Draft is aimed at achieving IETF
> Consensus before publication as an RFC and will be subject to an IETF
> Last Call.
>
> [RFC Editor, please remove this note before publication as an RFC and
> insert the correct Streams Boilerplate to indicate that the published
> RFC has IETF consensus.]
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-ccamp-mpls-tp-cp-framework-06.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>
>
>
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp

From guoxinchun@huawei.com  Thu Feb 10 17:39:30 2011
Return-Path: <guoxinchun@huawei.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1F3F13A6971; Thu, 10 Feb 2011 17:39:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.495
X-Spam-Level: 
X-Spam-Status: No, score=-4.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
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 3sgTbNIW8I1m; Thu, 10 Feb 2011 17:39:29 -0800 (PST)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 237123A67D2; Thu, 10 Feb 2011 17:39:29 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LGF005H2J9RIJ@szxga04-in.huawei.com>; Fri, 11 Feb 2011 09:39:27 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LGF00GM4J9R7J@szxga04-in.huawei.com>; Fri, 11 Feb 2011 09:39:27 +0800 (CST)
Received: from g67564e ([10.110.98.42]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LGF00AESJ9MX5@szxml04-in.huawei.com>; Fri, 11 Feb 2011 09:39:27 +0800 (CST)
Date: Fri, 11 Feb 2011 09:39:22 +0800
From: Xinchun Guo <guoxinchun@huawei.com>
In-reply-to: <4D4A934F.5020206@pi.nu>
To: 'Loa Andersson' <loa@pi.nu>, mpls-tp@ietf.org, mpls@ietf.org
Message-id: <020201cbc98c$8269d750$873d85f0$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: TEXT/PLAIN
Content-language: zh-cn
Content-transfer-encoding: 7BIT
Thread-index: AcvDlq57z2Yieu+sT1qv11A4xrFRrgF9U4SA
References: <4D4A934F.5020206@pi.nu>
Cc: ahmpls-tp@lists.itu.int
Subject: Re: [mpls-tp] wg last call on draft-ietf-mpls-tp-fault-03
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Feb 2011 01:39:30 -0000

Dear authors

After read the document, I have a question about the FM massage procedure.

In the section 5.1, the third paragraph, it said "The message is then sent.
The message MUST be refreshed two more times at an interval of one second.
Further refreshes are sent according to the value of the refresh timer."  I
don't know why the refreshing massage must be first sent two more times in
one second and then sent as the refresh timer interval.  Is it ok if the
refreshing massage is sent only according to the value of the refresh timer?
If it is not, what problem may be introduced? Hope authors could explain it
for me.

In addition, figure 2 is about the fault management massage format, so I
think naming the figure" MPLS-TP fault Management Message Format " other
than" MPLS-TP OAM Message Format " is more suitable.

Best Regards
Xinchun

-----Original Message-----
From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf
Of Loa Andersson
Sent: Thursday, February 03, 2011 7:37 PM
To: mpls-tp@ietf.org; mpls@ietf.org
Cc: ahmpls-tp@lists.itu.int
Subject: [mpls-tp] wg last call on draft-ietf-mpls-tp-fault-03

Working Group,

this is to start a four week working group last call
on "MPLS Fault Management OAM" (draft-ietf-mpls-tp-fault-03).

Please send comments to the mpls-tp@ietf.org mailing list.

This working group last call ends on February 28, 2011.



Loa, George and Ross

MPLS wg co-chairs

--

Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13



_______________________________________________
mpls-tp mailing list
mpls-tp@ietf.org
https://www.ietf.org/mailman/listinfo/mpls-tp




From wwwrun@core3.amsl.com  Thu Feb 10 23:39:51 2011
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: mpls-tp@ietf.org
Delivered-To: mpls-tp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 55BE63A6B11; Thu, 10 Feb 2011 23:39:51 -0800 (PST)
From: Loa Andersson(IETF MPLS WG) <loa@pi.nu>
To: greg.jones@itu.int
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110211073951.55BE63A6B11@core3.amsl.com>
Date: Thu, 10 Feb 2011 23:39:51 -0800 (PST)
Cc: mpls@ietf.org, greg.jones@itu.int, mpls-tp@ietf.org, Matthew.Bocci@alcatel-lucent.com, loa.andersson@ericsson.com, yoichi.maeda@ttc.or.jp, kam.lam@alcatel-lucent.com, ahmpls-tp@lists.itu.int, paf@cisco.com, adrian.farrel@huawei.com, tsbsg15@itu.int, andrew.g.malis@verizon.com, hhelvoort@huawei.com, ghani.abbas@ericsson.com
Subject: [mpls-tp] New Liaison Statement, "Status of the IETF MPLS-TP project documents 2011-02-11 (ref #052.01)"
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: loa.andersson@ericsson.com
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Feb 2011 07:39:51 -0000

Title: Status of the IETF MPLS-TP project documents 2011-02-11 (ref #052.01)
Submission Date: 2011-02-10
URL of the IETF Web page: https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=1013 

From: Loa Andersson(IETF MPLS WG) <loa@pi.nu>
To: SG15, Q9, Q10, Q12 and Q14(greg.jones@itu.int)
Cc: yoichi.maeda@ttc.or.jp
greg.jones@itu.int
ghani.abbas@ericsson.com
hhelvoort@huawei.com
malcolm.betts@zte.com.cn
kam.lam@alcatel-lucent.com
tsbsg15@itu.int
ahmpls-tp@lists.itu.int
adrian.farrel@huawei.com
rcallon@juniper.net
paf@cisco.com
stbryant@cisco.com
mpls@ietf.org
mpls-tp@ietf.org
swallow@cisco.com
elisa.bellagamba@ericsson.com
Reponse Contact: loa.andersson@ericsson.com
Technical Contact: loa.andersson@ericsson.com
swallow@cisco.com
rcallon@juniper.net
db3546@att.com
lberger@labn.net
andrew.g.malis@verizon.com
Matthew.Bocci@alcatel-lucent.com
Purpose: For information 
Body: 


The chairs of the MPLS, PWE3, and CCAMP working group would like to inform
you of the status of the MPLS-TP project within the IETF.

The attached document shows the many MPLS-TP documents that have been
worked on within the IETF, and shows what formal input has been provided 
by SG15 of the ITU-T.

We would like to take this opportunity to thank the many experts from SG15
who have contributed to this work by participating through the normal 
IETF process.

Loa Andersson (MPLS WG Co-chair)
Lou Berger (CCAMP WG Co-chair)
Matthew Bocci (PWE3 WG Co-chair)
Deborah Brungard (CCAMP WG Co-chair)
Ross Callon (MPLS  WG Co-chair)
Andrew Malis (PWE3 WG Co-chair)
George Swallow (MPLS WG Co-chair)
Attachment(s):
     Status of MPLS-TP Documents Under Development in the IETF � February 10, 2011 (https://datatracker.ietf.org/documents/LIAISON/file1186.doc)




From mach@huawei.com  Fri Feb 11 00:14:14 2011
Return-Path: <mach@huawei.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 751883A68BB; Fri, 11 Feb 2011 00:14:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
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 VzN7SgovTT80; Fri, 11 Feb 2011 00:14:13 -0800 (PST)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id DA38C3A681D; Fri, 11 Feb 2011 00:14:12 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LGG001OM1G1V1@szxga05-in.huawei.com>; Fri, 11 Feb 2011 16:12:01 +0800 (CST)
Received: from C55527A ([10.110.98.33]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LGG00MMG1FWCS@szxga05-in.huawei.com>; Fri, 11 Feb 2011 16:12:01 +0800 (CST)
Date: Fri, 11 Feb 2011 16:11:56 +0800
From: Mach Chen <mach@huawei.com>
In-reply-to: <60C093A41B5E45409A19D42CF7786DFD51CDF3F790@EUSAACMS0703.eamcs.ericsson.se>
To: 'David Allan I' <david.i.allan@ericsson.com>, 'Loa Andersson' <loa@pi.nu>,  mpls-tp@ietf.org, mpls@ietf.org, ahmpls-tp@lists.itu.int
Message-id: <075b01cbc9c3$5a4ca810$0ee5f830$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: zh-cn
Content-transfer-encoding: 7BIT
Thread-index: AcvDrJpCvXJpavHRRhKBBXlDzw1/zAFFYIGQABGDQCAAAKcQEAAlE/oA
References: <4D4AB81D.3080907@pi.nu> <06c901cbc8d4$d682a820$8387f860$@com> <60C093A41B5E45409A19D42CF7786DFD51CDF3F790@EUSAACMS0703.eamcs.ericsson.se>
Subject: Re: [mpls-tp] [mpls] mpls wg last call on	draft-ietf-mpls-tp-cc-cv-rdi-03
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Feb 2011 08:14:14 -0000

Hi Dave,

Thanks for your prompt response!

> >3 Section 3.5.2
> >" 4. Receipt of an expected session discriminator with an unexpected
label
> (mis-connectivity defect).", For a receiver, how does it know that the
> session >discriminator is valid but the label is invalid? IMHO, this
defect is just
> another description of defect 3 . Suggest to remove it.
> 
> If the session discriminator exists in the BFD database, it is
superficially a valid
> descriminator but the label of arrival can be incorrect. This may indicate
an
> implementation problem at the source MEP. What we were referring to in '3'
> was a session discriminator that did not exist in the local database, BFD
had
> never handed it out hence it could not be found.
> 

OK, but more clarification text would be helpful.

Best regards,
Mach



From dongjie_dj@huawei.com  Fri Feb 11 00:44:10 2011
Return-Path: <dongjie_dj@huawei.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A469A3A6A43; Fri, 11 Feb 2011 00:44:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.495
X-Spam-Level: 
X-Spam-Status: No, score=-4.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
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 FuvzyIzK9DyT; Fri, 11 Feb 2011 00:44:09 -0800 (PST)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 970973A69DD; Fri, 11 Feb 2011 00:44:09 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LGG00GC62XNVI@szxga04-in.huawei.com>; Fri, 11 Feb 2011 16:44:11 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LGG00KIK2XNJT@szxga04-in.huawei.com>; Fri, 11 Feb 2011 16:44:11 +0800 (CST)
Received: from D65110A ([10.110.98.31]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LGG004V72XITN@szxml04-in.huawei.com>; Fri, 11 Feb 2011 16:44:11 +0800 (CST)
Date: Fri, 11 Feb 2011 16:44:06 +0800
From: Jie Dong <dongjie_dj@huawei.com>
In-reply-to: <4D4A9478.7050704@pi.nu>
To: mpls-tp@ietf.org, mpls@ietf.org
Message-id: <021101cbc9c7$d7c8b140$875a13c0$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: TEXT/PLAIN
Content-language: zh-cn
Content-transfer-encoding: 7BIT
Thread-index: AcvDl10fqyGU6Z/HTcaxkW43UzP3eAFXdT1g
References: <4D4A9478.7050704@pi.nu>
Subject: Re: [mpls-tp] mpls wg last call on	draft-ietf-mpls-tp-linear-protection-04
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Feb 2011 08:44:10 -0000

Dear authors,

Here are some comments on linear protection draft.

1. In section 1.2, it says:
" The basic protocol is designed for use in conjunction with the 1:1
protection architecture (for both unidirectional and bidirectional
protection) and for 1+1 protection of a bidirectional path (for both
unidirectional and bidirectional protection switching). "

Would you please explain why coordination is needed for unidirectional
protection switching in 1+1 protection of a bidirectional path? Because
section 4.7.2 of tp-survive-fwk says:
"In 1+1 unidirectional protection switching there is no need to coordinate
the protection state between the protection controllers at both ends of the
protection domain."

I guess you mean 1+1 protection may need coordination to keep traffic on
co-routed paths, but that would be bidirectional protection switching.
Hope this could be made clearer in this draft.

2. Section 2.1, Acronyms
The full name of "LER" should be "Label Edge Router"
"PST" is an old term replaced by SPME (Sub-Path Maintenance Entity), but
neither is used in the following sections, so it may be removed from
acronyms.

3. In Section 3, there is only one level-2 subsection (3.1), so what about
promote the level-3 subtitles (3.1.1, 3.1.2, ...) to level-2, and level-4
(3.1.6.1) to level-3?

4. Section 4, 3rd paragraph, s/single-phase/single-phased, to be consistent
with 2nd paragraph.

5. Section 4.1, 4th paragraph,
" In the event a signal fail condition is detected on the protection path,
the received PSC specific information should be evaluated."
The statement is vague. What would be the state and action when a signal
fail is detected on the protection path? Would you please elaborate on this
point?

6. Section 4.2.2, 4th paragraph,
" The Fpath field SHALL identify the path that is reporting the failure
condition (i.e. if protection path then Fpath is set to 0...".
Since PSC message are only transmitted on protection path, if protection
path has signal fail, the PSC message may not be able to be sent out to
far-end.

7. Section 4.3.2, there is signal degrade on working path as input, but no
signal degrade on protection path.

8. Section 4.3.3, I go through this part fast, a general question is: are
the PSC operations for 4 different protection types identical ? In this
section there is no description about operation of each specific protection
type, but to my understanding, there may be different operations, e.g., for
bidirectional 1:1 protection, the end point may need to switch the sink
selector and transmitting bridge simultaneously according to some input, but
for unidirectional 1:1 the end point may only need to switch the
transmitting bridge OR the sink selector. And the PSC message sent may also
be different for different protection types. (Please correct me if there is
anything wrong with this thought).


Best Regards,
Jie

> -----Original Message-----
> From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On
> Behalf Of Loa Andersson
> Sent: Thursday, February 03, 2011 7:42 PM
> To: mpls-tp@ietf.org; mpls@ietf.org
> Cc: ahmpls-tp@lists.itu.int
> Subject: [mpls-tp] mpls wg last call on
draft-ietf-mpls-tp-linear-protection-04
>
> Working Group,
>
> this is to start a four week working group last call on
> "MPLS-TP Linear Protection" (draft-ietf-mpls-tp-linear-protection-04).
>
> Please send comments to the mpls-tp@ietf.org mailing list.
>
> This working group last call ends on February 28, 2011.
>
>
>
> Loa, George and Ross
>
> MPLS wg co-chairs
>
>
>
> --
>
>
> Loa Andersson                         email:
> loa.andersson@ericsson.com
> Sr Strategy and Standards Manager            loa@pi.nu
> Ericsson Inc                          phone: +46 10 717 52 13
>                                               +46 767 72 92 13
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp




From guoxinchun@huawei.com  Fri Feb 11 01:53:32 2011
Return-Path: <guoxinchun@huawei.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 24A933A688F; Fri, 11 Feb 2011 01:53:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.495
X-Spam-Level: 
X-Spam-Status: No, score=-2.495 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
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 u35drlYcj7MU; Fri, 11 Feb 2011 01:53:31 -0800 (PST)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 27ADF3A685A; Fri, 11 Feb 2011 01:53:31 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LGG002P563246@szxga05-in.huawei.com>; Fri, 11 Feb 2011 17:52:14 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LGG00ELT631LS@szxga05-in.huawei.com>; Fri, 11 Feb 2011 17:52:13 +0800 (CST)
Received: from g67564e ([10.110.98.42]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LGG00B0Z62WFI@szxml04-in.huawei.com>; Fri, 11 Feb 2011 17:52:13 +0800 (CST)
Date: Fri, 11 Feb 2011 17:52:08 +0800
From: Xinchun Guo <guoxinchun@huawei.com>
In-reply-to: <020201cbc98c$8269d750$873d85f0$@com>
To: 'Loa Andersson' <loa@pi.nu>, mpls-tp@ietf.org, mpls@ietf.org
Message-id: <020701cbc9d1$594011b0$0bc03510$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: TEXT/PLAIN
Content-language: zh-cn
Content-transfer-encoding: 7BIT
Thread-index: AcvDlq57z2Yieu+sT1qv11A4xrFRrgF9U4SAAAVBXrA=
References: <4D4A934F.5020206@pi.nu> <020201cbc98c$8269d750$873d85f0$@com>
Cc: ahmpls-tp@lists.itu.int
Subject: Re: [mpls-tp] wg last call on draft-ietf-mpls-tp-fault-03
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Feb 2011 09:53:32 -0000

Other 3 edit comments, see below.

1.section 2.2, there is overlapping between the last sentence of the first
paragraph and the first sentence of the second paragraph about " The purpose
of the LKR message is to suppress alarms in the MPLS-TP layer network above
the level at which the defect occurs" . Simplify it will be more smart.

2.section 4.1.2, the first sentence" This TLV carries the Interface
Identifier as defined ......", "the Interface Identifier" should be "the
Global Identifier". right?

3. section 5.3, there are two "that" in the first sentence, one is
redundancy.

Regards
Xinchun

-----Original Message-----
From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf
Of Xinchun Guo
Sent: Friday, February 11, 2011 9:39 AM
To: 'Loa Andersson'; mpls-tp@ietf.org; mpls@ietf.org
Cc: ahmpls-tp@lists.itu.int
Subject: Re: [mpls-tp] wg last call on draft-ietf-mpls-tp-fault-03

Dear authors

After read the document, I have a question about the FM massage procedure.

In the section 5.1, the third paragraph, it said "The message is then sent.
The message MUST be refreshed two more times at an interval of one second.
Further refreshes are sent according to the value of the refresh timer."  I
don't know why the refreshing massage must be first sent two more times in
one second and then sent as the refresh timer interval.  Is it ok if the
refreshing massage is sent only according to the value of the refresh timer?
If it is not, what problem may be introduced? Hope authors could explain it
for me.

In addition, figure 2 is about the fault management massage format, so I
think naming the figure" MPLS-TP fault Management Message Format " other
than" MPLS-TP OAM Message Format " is more suitable.

Best Regards
Xinchun

-----Original Message-----
From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf
Of Loa Andersson
Sent: Thursday, February 03, 2011 7:37 PM
To: mpls-tp@ietf.org; mpls@ietf.org
Cc: ahmpls-tp@lists.itu.int
Subject: [mpls-tp] wg last call on draft-ietf-mpls-tp-fault-03

Working Group,

this is to start a four week working group last call
on "MPLS Fault Management OAM" (draft-ietf-mpls-tp-fault-03).

Please send comments to the mpls-tp@ietf.org mailing list.

This working group last call ends on February 28, 2011.



Loa, George and Ross

MPLS wg co-chairs

--

Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13



_______________________________________________
mpls-tp mailing list
mpls-tp@ietf.org
https://www.ietf.org/mailman/listinfo/mpls-tp



_______________________________________________
mpls-tp mailing list
mpls-tp@ietf.org
https://www.ietf.org/mailman/listinfo/mpls-tp




From david.i.allan@ericsson.com  Fri Feb 11 02:11:40 2011
Return-Path: <david.i.allan@ericsson.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B23F23A6A70; Fri, 11 Feb 2011 02:11:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 oOTNO63niOl7; Fri, 11 Feb 2011 02:11:39 -0800 (PST)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by core3.amsl.com (Postfix) with ESMTP id ACEFF3A6A6D; Fri, 11 Feb 2011 02:11:39 -0800 (PST)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id p1BABp9r018454 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 11 Feb 2011 04:11:51 -0600
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.66]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Fri, 11 Feb 2011 05:11:50 -0500
From: David Allan I <david.i.allan@ericsson.com>
To: Mach Chen <mach@huawei.com>, "'Loa Andersson'" <loa@pi.nu>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>,  "ahmpls-tp@lists.itu.int" <ahmpls-tp@lists.itu.int>
Date: Fri, 11 Feb 2011 05:11:40 -0500
Thread-Topic: [mpls] [mpls-tp] mpls wg last call on draft-ietf-mpls-tp-cc-cv-rdi-03
Thread-Index: AcvDrJpCvXJpavHRRhKBBXlDzw1/zAFFYIGQABGDQCAAAKcQEAAlE/oAAA0+koA=
Message-ID: <60C093A41B5E45409A19D42CF7786DFD51CDF3FEBE@EUSAACMS0703.eamcs.ericsson.se>
References: <4D4AB81D.3080907@pi.nu> <06c901cbc8d4$d682a820$8387f860$@com> <60C093A41B5E45409A19D42CF7786DFD51CDF3F790@EUSAACMS0703.eamcs.ericsson.se> <075b01cbc9c3$5a4ca810$0ee5f830$@com>
In-Reply-To: <075b01cbc9c3$5a4ca810$0ee5f830$@com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [mpls-tp] [mpls] mpls wg last call on	draft-ietf-mpls-tp-cc-cv-rdi-03
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Feb 2011 10:11:40 -0000

OK, will do...

Dave=20

-----Original Message-----
From: Mach Chen [mailto:mach@huawei.com]=20
Sent: Friday, February 11, 2011 12:12 AM
To: David Allan I; 'Loa Andersson'; mpls-tp@ietf.org; mpls@ietf.org; ahmpls=
-tp@lists.itu.int
Subject: RE: [mpls] [mpls-tp] mpls wg last call on draft-ietf-mpls-tp-cc-cv=
-rdi-03

Hi Dave,

Thanks for your prompt response!

> >3 Section 3.5.2
> >" 4. Receipt of an expected session discriminator with an unexpected
label
> (mis-connectivity defect).", For a receiver, how does it know that the=20
> session >discriminator is valid but the label is invalid? IMHO, this
defect is just
> another description of defect 3 . Suggest to remove it.
>=20
> If the session discriminator exists in the BFD database, it is
superficially a valid
> descriminator but the label of arrival can be incorrect. This may=20
> indicate
an
> implementation problem at the source MEP. What we were referring to in '3=
'
> was a session discriminator that did not exist in the local database,=20
> BFD
had
> never handed it out hence it could not be found.
>=20

OK, but more clarification text would be helpful.

Best regards,
Mach



From guoxinchun@huawei.com  Sun Feb 13 19:09:52 2011
Return-Path: <guoxinchun@huawei.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 57D5D3A6A6F; Sun, 13 Feb 2011 19:09:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.828
X-Spam-Level: 
X-Spam-Status: No, score=-1.828 tagged_above=-999 required=5 tests=[AWL=-1.333, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
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 c5Mz+Y0HOmWX; Sun, 13 Feb 2011 19:09:51 -0800 (PST)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 0D6133A6839; Sun, 13 Feb 2011 19:09:51 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LGL00J367GQP3@szxga05-in.huawei.com>; Mon, 14 Feb 2011 11:10:02 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LGL00CFS7GPKM@szxga05-in.huawei.com>; Mon, 14 Feb 2011 11:10:01 +0800 (CST)
Received: from g67564e ([10.110.98.42]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LGL00FUU7GL2F@szxml04-in.huawei.com>; Mon, 14 Feb 2011 11:10:01 +0800 (CST)
Date: Mon, 14 Feb 2011 11:09:56 +0800
From: Xinchun Guo <guoxinchun@huawei.com>
In-reply-to: <020701cbc9d1$594011b0$0bc03510$@com>
To: 'Loa Andersson' <loa@pi.nu>, mpls-tp@ietf.org, mpls@ietf.org
Message-id: <000001cbcbf4$a8cd32b0$fa679810$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: TEXT/PLAIN
Content-language: zh-cn
Content-transfer-encoding: 7BIT
Thread-index: AcvDlq57z2Yieu+sT1qv11A4xrFRrgF9U4SAAAVBXrAAk0N8oA==
References: <4D4A934F.5020206@pi.nu> <020201cbc98c$8269d750$873d85f0$@com> <020701cbc9d1$594011b0$0bc03510$@com>
Cc: ahmpls-tp@lists.itu.int
Subject: Re: [mpls-tp] wg last call on draft-ietf-mpls-tp-fault-03
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Feb 2011 03:09:52 -0000

Hi authors and all

About this document, I have another question expect to be clarification. I
am not very clear about the specific application of Fault management
message.

In section 2 of this document, it said " Fault OAM messages are generated by
intermediate nodes where an LSP is switched".  Does it mean that the fault
message can only be used for alarm suppress of LSP layer?  Could not this
fault management function be used for PW layer, especially for the MS-PW
conditions.  Take the following hiberarchy scenario for example, PW1 and PW2
are two segments of the MS-PW which is client of the LSP layer.  if the
server layer of LSP fails, such as Link1, node2 will initiate AIS message
and sent it to LSP1 end point node3.  As MS-PW is client of LSP1, for this
condition, whether Node3 will further initiate Fault management message to
MS-PW end point Node4 to notify the failure of LSP1 to suppress alarm of the
end to end pw service.  IMO, Fault management function should cover these PW
conditions.

-                        MS-PW                   -
-                           +---------AIS/LKR-------------->>-
-<-----------------PW1-------------------->|-----------------PW2------------
>-
-              +----AIS/LKR---->>                     -
-<-------LSP1---------+-------------------><--------------LSP2--------------
->-
-              |AIS/LKR                            -
-<--- Link1---------->|<---
Link2------><--------Link3--------------------->-
Node1       Node2       Node3                Node4


Hope authors could clarify this point and detail the Fault function process
about PW scenarios in this document.

Best Regards
Xinchun


-----Original Message-----
From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf
Of Xinchun Guo
Sent: Friday, February 11, 2011 5:52 PM
To: 'Loa Andersson'; mpls-tp@ietf.org; mpls@ietf.org
Cc: ahmpls-tp@lists.itu.int
Subject: Re: [mpls-tp] wg last call on draft-ietf-mpls-tp-fault-03

Other 3 edit comments, see below.

1.section 2.2, there is overlapping between the last sentence of the first
paragraph and the first sentence of the second paragraph about " The purpose
of the LKR message is to suppress alarms in the MPLS-TP layer network above
the level at which the defect occurs" . Simplify it will be more smart.

2.section 4.1.2, the first sentence" This TLV carries the Interface
Identifier as defined ......", "the Interface Identifier" should be "the
Global Identifier". right?

3. section 5.3, there are two "that" in the first sentence, one is
redundancy.

Regards
Xinchun

-----Original Message-----
From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf
Of Xinchun Guo
Sent: Friday, February 11, 2011 9:39 AM
To: 'Loa Andersson'; mpls-tp@ietf.org; mpls@ietf.org
Cc: ahmpls-tp@lists.itu.int
Subject: Re: [mpls-tp] wg last call on draft-ietf-mpls-tp-fault-03

Dear authors

After read the document, I have a question about the FM massage procedure.

In the section 5.1, the third paragraph, it said "The message is then sent.
The message MUST be refreshed two more times at an interval of one second.
Further refreshes are sent according to the value of the refresh timer."  I
don't know why the refreshing massage must be first sent two more times in
one second and then sent as the refresh timer interval.  Is it ok if the
refreshing massage is sent only according to the value of the refresh timer?
If it is not, what problem may be introduced? Hope authors could explain it
for me.

In addition, figure 2 is about the fault management massage format, so I
think naming the figure" MPLS-TP fault Management Message Format " other
than" MPLS-TP OAM Message Format " is more suitable.

Best Regards
Xinchun

-----Original Message-----
From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf
Of Loa Andersson
Sent: Thursday, February 03, 2011 7:37 PM
To: mpls-tp@ietf.org; mpls@ietf.org
Cc: ahmpls-tp@lists.itu.int
Subject: [mpls-tp] wg last call on draft-ietf-mpls-tp-fault-03

Working Group,

this is to start a four week working group last call
on "MPLS Fault Management OAM" (draft-ietf-mpls-tp-fault-03).

Please send comments to the mpls-tp@ietf.org mailing list.

This working group last call ends on February 28, 2011.



Loa, George and Ross

MPLS wg co-chairs

--

Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13



_______________________________________________
mpls-tp mailing list
mpls-tp@ietf.org
https://www.ietf.org/mailman/listinfo/mpls-tp



_______________________________________________
mpls-tp mailing list
mpls-tp@ietf.org
https://www.ietf.org/mailman/listinfo/mpls-tp



_______________________________________________
mpls-tp mailing list
mpls-tp@ietf.org
https://www.ietf.org/mailman/listinfo/mpls-tp




From danfrost@cisco.com  Tue Feb 15 06:14:56 2011
Return-Path: <danfrost@cisco.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 560D73A6C94; Tue, 15 Feb 2011 06:14:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 z7Gn5q8nyG37; Tue, 15 Feb 2011 06:14:55 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 442D23A6A6C; Tue, 15 Feb 2011 06:14:55 -0800 (PST)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAPYYWk1AZnwM/2dsb2JhbAClV3OgGptlhV4EjAI
X-IronPort-AV: E=Sophos;i="4.60,474,1291593600"; d="scan'208";a="215825315"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 15 Feb 2011 14:15:20 +0000
Received: from isolaria.cisco.com (isolaria.cisco.com [64.100.19.13]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p1FEFKPx025208; Tue, 15 Feb 2011 14:15:20 GMT
Received: from isolaria.cisco.com (isolaria [127.0.0.1]) by isolaria.cisco.com (8.13.1/8.13.1) with ESMTP id p1FEFKqC022897; Tue, 15 Feb 2011 09:15:20 -0500
Received: (from danfrost@localhost) by isolaria.cisco.com (8.13.1/8.13.1/Submit) id p1FEFJo6022896; Tue, 15 Feb 2011 14:15:19 GMT
X-Authentication-Warning: isolaria.cisco.com: danfrost set sender to danfrost@cisco.com using -f
From: Dan Frost <danfrost@cisco.com>
To: Linda Dunbar <linda.dunbar@huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F6A81B8F@DFWEML501-MBX.china.huawei.com> (Linda Dunbar's message of "Tue, 08 Feb 2011 21:57:32 +0000")
References: <DF7F294AF4153D498141CBEFADB177049BA717FF88@EMBX01-WF.jnpr.net> <4A95BA014132FF49AE685FAB4B9F17F6A81B8F@DFWEML501-MBX.china.huawei.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)
Date: Tue, 15 Feb 2011 14:15:19 +0000
Message-ID: <y1gmzkpxe64o.fsf@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: mpls@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] MPLS WG Last call on draft-ietf-mpls-loss-delay-01
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Feb 2011 14:14:56 -0000

Hi Linda,

Linda Dunbar <linda.dunbar@huawei.com> writes:
> I have some issues with this draft:
> There had been a lot of discussions on email list on what should
> Initiator (querier) do when not receiving a response from far end.
>
> Ben Jenkins suggested the following text
> (http://www.ietf.org/mail-archive/web/mpls/current/msg05696.html)
> which is not incorporated to this new draft yet.
>
>       When initiating an LM operation, the far end may require a
>       period of time to become ready for the requested measurement
>       operation or the far end may not be able to support the
>       requested measurement. Under those circumstances, LM queries MAY
>       simply be discarded, and the querier expecting a response SHOULD
>       be prepared for this situation. Alternatively, the receiver MAY
>       respond, possibly in a rate-limited manner, to queries received
>       during this period with an appropriate notification code.  The
>       querier should abort the measurement after not receiving any
>       positive feedback when a specified timer expires.

With one exception, this text looks substantially the same to me as the
last paragraph of Section 4.1.1.  The exception is your addition of 'or
the far end may not be able to support the requested measurement' to the
first sentence, but that case is not what this text is meant to cover:
if the far end doesn't support the requested measurement, the right
thing to do is to reply with an appropriate error code so the querier
knows what went wrong.

> Section 3.5.3: It stated:
>        When a query is received with a Session Query Interval that is
>        too low for the receiver to support, the receiver SHOULD
>        include this object when it generates an error response.
>
> Question:
>       Which error code should be used? Is it 0x18:Error - Unsupported
>       Query Interval? If Yes, should add this to the sentence.

Yes, that's the purpose of this error code.  We can be explicit here.

>       What if the Querier indicates "0x2: No Response Requested"?

In general, a no-response-requested measurement means that the querier
can't receive any direct feedback; the assumption of this measurement
mode is that control is achieved through some external means, e.g. an
NMS that ensures consistent operation among the nodes involved.

> Section 4.1.5:
> * Should allow the Loss measurement to be calculated somewhere else,
> in case the initiator (querier) doesn't have the capacity to do the
> calculation.

Ben Mack-Crane has made comprehensive comments on this topic, so we'll
address it in that context.

> * Should add a description that measurement is to be stopped when far
> end not respond anymore.

OK.

Thanks for your comments!

-d

> Linda Dunbar

From linda.dunbar@huawei.com  Tue Feb 15 08:06:51 2011
Return-Path: <linda.dunbar@huawei.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0D9173A6C38; Tue, 15 Feb 2011 08:06:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.38
X-Spam-Level: 
X-Spam-Status: No, score=-5.38 tagged_above=-999 required=5 tests=[AWL=1.218,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 po7EqR+xrJzS; Tue, 15 Feb 2011 08:06:49 -0800 (PST)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id BF9903A6B60; Tue, 15 Feb 2011 08:06:49 -0800 (PST)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LGO004T5242U9@usaga02-in.huawei.com>; Tue, 15 Feb 2011 08:07:15 -0800 (PST)
Received: from dfweml201-edg.china.huawei.com ([172.18.9.107]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPS id <0LGO00CIE24275@usaga02-in.huawei.com>; Tue, 15 Feb 2011 08:07:14 -0800 (PST)
Received: from DFWEML402-HUB.china.huawei.com (10.193.5.102) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 15 Feb 2011 08:07:11 -0800
Received: from DFWEML501-MBX.china.huawei.com ([fe80::c52a:9e19:87eb:4531]) by DFWEML402-HUB.china.huawei.com ([::1]) with mapi id 14.01.0270.001; Tue, 15 Feb 2011 08:07:14 -0800
Date: Tue, 15 Feb 2011 16:07:12 +0000
From: Linda Dunbar <linda.dunbar@huawei.com>
In-reply-to: <y1gmzkpxe64o.fsf@cisco.com>
X-Originating-IP: [10.124.12.77]
To: Dan Frost <danfrost@cisco.com>
Message-id: <4A95BA014132FF49AE685FAB4B9F17F6A83645@DFWEML501-MBX.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_NyZlYbtxfvUUJtZRdhAsxw)"
Content-language: en-US
Accept-Language: en-US
Thread-topic: [mpls-tp] [mpls] MPLS WG Last call on draft-ietf-mpls-loss-delay-01
Thread-index: AQHLzRr0ixNfwYWA20Cm8N6c/tU+FpQCtduw
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <DF7F294AF4153D498141CBEFADB177049BA717FF88@EMBX01-WF.jnpr.net> <4A95BA014132FF49AE685FAB4B9F17F6A81B8F@DFWEML501-MBX.china.huawei.com> <y1gmzkpxe64o.fsf@cisco.com>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls-tp] [mpls] MPLS WG Last call on	draft-ietf-mpls-loss-delay-01
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Feb 2011 16:06:51 -0000

--Boundary_(ID_NyZlYbtxfvUUJtZRdhAsxw)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Dan:

 You said:
            "if the far end doesn't support the requested measurement, the right thing to do is to reply with an appropriate error code so the querier knows what went wrong."

What if the reply message got lost? Then you have to add the mechanism to make far-end sending multiple messages with the correct Error Code.

So the simplest thing is for the Querier to stop the measurement either upon receiving a reply with Error Code or not receiving any reply for a while.

Linda Dunbar

-----Original Message-----
From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf Of Dan Frost
Sent: Tuesday, February 15, 2011 8:15 AM
To: Linda Dunbar
Cc: mpls@ietf.org; mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] MPLS WG Last call on draft-ietf-mpls-loss-delay-01

Hi Linda,

Linda Dunbar <linda.dunbar@huawei.com> writes:
> I have some issues with this draft:
> There had been a lot of discussions on email list on what should
> Initiator (querier) do when not receiving a response from far end.
>
> Ben Jenkins suggested the following text
> (http://www.ietf.org/mail-archive/web/mpls/current/msg05696.html)
> which is not incorporated to this new draft yet.
>
>       When initiating an LM operation, the far end may require a
>       period of time to become ready for the requested measurement
>       operation or the far end may not be able to support the
>       requested measurement. Under those circumstances, LM queries MAY
>       simply be discarded, and the querier expecting a response SHOULD
>       be prepared for this situation. Alternatively, the receiver MAY
>       respond, possibly in a rate-limited manner, to queries received
>       during this period with an appropriate notification code.  The
>       querier should abort the measurement after not receiving any
>       positive feedback when a specified timer expires.

With one exception, this text looks substantially the same to me as the
last paragraph of Section 4.1.1.  The exception is your addition of 'or
the far end may not be able to support the requested measurement' to the
first sentence, but that case is not what this text is meant to cover:
if the far end doesn't support the requested measurement, the right
thing to do is to reply with an appropriate error code so the querier
knows what went wrong.

> Section 3.5.3: It stated:
>        When a query is received with a Session Query Interval that is
>        too low for the receiver to support, the receiver SHOULD
>        include this object when it generates an error response.
>
> Question:
>       Which error code should be used? Is it 0x18:Error - Unsupported
>       Query Interval? If Yes, should add this to the sentence.

Yes, that's the purpose of this error code.  We can be explicit here.

>       What if the Querier indicates "0x2: No Response Requested"?

In general, a no-response-requested measurement means that the querier
can't receive any direct feedback; the assumption of this measurement
mode is that control is achieved through some external means, e.g. an
NMS that ensures consistent operation among the nodes involved.

> Section 4.1.5:
> * Should allow the Loss measurement to be calculated somewhere else,
> in case the initiator (querier) doesn't have the capacity to do the
> calculation.

Ben Mack-Crane has made comprehensive comments on this topic, so we'll
address it in that context.

> * Should add a description that measurement is to be stopped when far
> end not respond anymore.

OK.

Thanks for your comments!

-d

> Linda Dunbar
_______________________________________________
mpls-tp mailing list
mpls-tp@ietf.org
https://www.ietf.org/mailman/listinfo/mpls-tp


--Boundary_(ID_NyZlYbtxfvUUJtZRdhAsxw)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Consolas" size="2"><span style="font-size:10.5pt;">
<div>Dan:</div>
<div>&nbsp;</div>
<div> You said: </div>
<div style="padding-left:72pt;"><i>&quot;</i><i>if the far end doesn't support the requested measurement, the right thing to do is to reply with an appropriate error code so the querier knows what went wrong.</i><i>&quot;</i></div>
<div style="padding-left:72pt;"><font face="Times New Roman">&nbsp;</font></div>
<div>What if the reply message got lost? Then you have to add the mechanism to make far-end sending multiple messages with the correct Error Code. </div>
<div>&nbsp;</div>
<div>So the simplest thing is for the Querier to stop the measurement either upon receiving a reply with Error Code or not receiving any reply for a while. </div>
<div>&nbsp;</div>
<div>Linda Dunbar</div>
<div><font face="Times New Roman">&nbsp;</font></div>
<div>-----Original Message-----<br>

From: mpls-tp-bounces@ietf.org [<a href="mailto:mpls-tp-bounces@ietf.org">mailto:mpls-tp-bounces@ietf.org</a>] On Behalf Of Dan Frost<br>

Sent: Tuesday, February 15, 2011 8:15 AM<br>

To: Linda Dunbar<br>

Cc: mpls@ietf.org; mpls-tp@ietf.org<br>

Subject: Re: [mpls-tp] [mpls] MPLS WG Last call on draft-ietf-mpls-loss-delay-01</div>
<div><font face="Times New Roman">&nbsp;</font></div>
<div>Hi Linda,</div>
<div>&nbsp;</div>
<div>Linda Dunbar &lt;linda.dunbar@huawei.com&gt; writes:</div>
<div>&gt; I have some issues with this draft:</div>
<div>&gt; There had been a lot of discussions on email list on what should</div>
<div>&gt; Initiator (querier) do when not receiving a response from far end.</div>
<div>&gt;</div>
<div>&gt; Ben Jenkins suggested the following text</div>
<div>&gt; (<a href="http://www.ietf.org/mail-archive/web/mpls/current/msg05696.html">http://www.ietf.org/mail-archive/web/mpls/current/msg05696.html</a>)</div>
<div>&gt; which is not incorporated to this new draft yet.</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; When initiating an LM operation, the far end may require a</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; period of time to become ready for the requested measurement</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; operation or the far end may not be able to support the</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; requested measurement. Under those circumstances, LM queries MAY</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; simply be discarded, and the querier expecting a response SHOULD</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; be prepared for this situation. Alternatively, the receiver MAY</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; respond, possibly in a rate-limited manner, to queries received</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; during this period with an appropriate notification code.&nbsp; The</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; querier should abort the measurement after not receiving any</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; positive feedback when a specified timer expires.</div>
<div>&nbsp;</div>
<div>With one exception, this text looks substantially the same to me as the</div>
<div>last paragraph of Section 4.1.1.&nbsp; The exception is your addition of 'or</div>
<div>the far end may not be able to support the requested measurement' to the</div>
<div>first sentence, but that case is not what this text is meant to cover:</div>
<div>if the far end doesn't support the requested measurement, the right</div>
<div>thing to do is to reply with an appropriate error code so the querier</div>
<div>knows what went wrong.</div>
<div>&nbsp;</div>
<div>&gt; Section 3.5.3: It stated:</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; When a query is received with a Session Query Interval that is</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; too low for the receiver to support, the receiver SHOULD</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; include this object when it generates an error response.</div>
<div>&gt;</div>
<div>&gt; Question:</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Which error code should be used? Is it 0x18:Error - Unsupported</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Query Interval? If Yes, should add this to the sentence.</div>
<div>&nbsp;</div>
<div>Yes, that's the purpose of this error code.&nbsp; We can be explicit here.</div>
<div>&nbsp;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; What if the Querier indicates &quot;0x2: No Response Requested&quot;?</div>
<div>&nbsp;</div>
<div>In general, a no-response-requested measurement means that the querier</div>
<div>can't receive any direct feedback; the assumption of this measurement</div>
<div>mode is that control is achieved through some external means, e.g. an</div>
<div>NMS that ensures consistent operation among the nodes involved.</div>
<div>&nbsp;</div>
<div>&gt; Section 4.1.5:</div>
<div>&gt; * Should allow the Loss measurement to be calculated somewhere else,</div>
<div>&gt; in case the initiator (querier) doesn't have the capacity to do the</div>
<div>&gt; calculation.</div>
<div>&nbsp;</div>
<div>Ben Mack-Crane has made comprehensive comments on this topic, so we'll</div>
<div>address it in that context.</div>
<div>&nbsp;</div>
<div>&gt; * Should add a description that measurement is to be stopped when far</div>
<div>&gt; end not respond anymore.</div>
<div>&nbsp;</div>
<div>OK.</div>
<div>&nbsp;</div>
<div>Thanks for your comments!</div>
<div>&nbsp;</div>
<div>-d</div>
<div>&nbsp;</div>
<div>&gt; Linda Dunbar</div>
<div>_______________________________________________</div>
<div>mpls-tp mailing list</div>
<div>mpls-tp@ietf.org</div>
<div><a href="https://www.ietf.org/mailman/listinfo/mpls-tp">https://www.ietf.org/mailman/listinfo/mpls-tp</a></div>
<div><font face="Times New Roman">&nbsp;</font></div>
</span></font>
</body>
</html>

--Boundary_(ID_NyZlYbtxfvUUJtZRdhAsxw)--

From danfrost@cisco.com  Wed Feb 16 03:22:20 2011
Return-Path: <danfrost@cisco.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 268513A6D3C; Wed, 16 Feb 2011 03:22:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 C2BvrmTZj8BA; Wed, 16 Feb 2011 03:22:18 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 4A7463A6D3A; Wed, 16 Feb 2011 03:22:18 -0800 (PST)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAGNCW01AZnwN/2dsb2JhbAClXnOgcptOhV4EjAo
X-IronPort-AV: E=Sophos;i="4.60,479,1291593600"; d="scan'208";a="215981752"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 16 Feb 2011 11:22:46 +0000
Received: from isolaria.cisco.com (isolaria.cisco.com [64.100.19.13]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p1GBMk8Z001819; Wed, 16 Feb 2011 11:22:46 GMT
Received: from isolaria.cisco.com (isolaria [127.0.0.1]) by isolaria.cisco.com (8.13.1/8.13.1) with ESMTP id p1GBMjc2004729; Wed, 16 Feb 2011 06:22:45 -0500
Received: (from danfrost@localhost) by isolaria.cisco.com (8.13.1/8.13.1/Submit) id p1GBMj8P004728; Wed, 16 Feb 2011 11:22:45 GMT
Date: Wed, 16 Feb 2011 11:22:45 +0000
From: Dan Frost <danfrost@cisco.com>
To: Linda Dunbar <linda.dunbar@huawei.com>
Message-ID: <20110216112245.GB2602@cisco.com>
References: <DF7F294AF4153D498141CBEFADB177049BA717FF88@EMBX01-WF.jnpr.net> <4A95BA014132FF49AE685FAB4B9F17F6A81B8F@DFWEML501-MBX.china.huawei.com> <y1gmzkpxe64o.fsf@cisco.com> <4A95BA014132FF49AE685FAB4B9F17F6A83645@DFWEML501-MBX.china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F6A83645@DFWEML501-MBX.china.huawei.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls-tp] [mpls] MPLS WG Last call on	draft-ietf-mpls-loss-delay-01
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 11:22:20 -0000

Hi Linda,

On Tue, Feb 15, 2011 at 04:07:12PM +0000, Linda Dunbar wrote:
> You said:
>  "if the far end doesn't support the requested measurement,
>   the right thing to do is to reply with an appropriate
>   error code so the querier knows what went wrong."
> 
> What if the reply message got lost? Then you have to add the mechanism
> to make far-end sending multiple messages with the correct Error Code.

There's no extra mechanism needed; this is the normal operation of the
protocol.  A lost response just means another query/response will
happen.

> So the simplest thing is for the Querier to stop the measurement
> either upon receiving a reply with Error Code or not receiving any
> reply for a while.

Sure.  In essence, upon receiving a query requesting an unsupported
operation, the responder SHOULD respond with an appropriate error code,
and in general, the querier SHOULD time out any measurement attempt
that's been outstanding for too long.  We'll clarify this in the text.

Cheers,

-d

> Linda Dunbar

From yaacov.weingarten@nsn.com  Wed Feb 16 06:08:39 2011
Return-Path: <yaacov.weingarten@nsn.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 633453A6CCD; Wed, 16 Feb 2011 06:08:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 A8gU2ts+MrzR; Wed, 16 Feb 2011 06:08:38 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by core3.amsl.com (Postfix) with ESMTP id 8E56B3A6CA7; Wed, 16 Feb 2011 06:08:33 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id p1GE8sWC006843 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 16 Feb 2011 15:08:54 +0100
Received: from demuexc025.nsn-intra.net (demuexc025.nsn-intra.net [10.159.32.12]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p1GE8rEU011815; Wed, 16 Feb 2011 15:08:54 +0100
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by demuexc025.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 16 Feb 2011 15:08:51 +0100
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
Date: Wed, 16 Feb 2011 15:08:46 +0100
Message-ID: <E4873516F3FC7547BCFE792C7D94039C05F0D5@DEMUEXC013.nsn-intra.net>
In-Reply-To: <021101cbc9c7$d7c8b140$875a13c0$@com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls-tp] mpls wg last callon	draft-ietf-mpls-tp-linear-protection-04
Thread-Index: AcvDl10fqyGU6Z/HTcaxkW43UzP3eAFXdT1gATjyzUA=
References: <4D4A9478.7050704@pi.nu> <021101cbc9c7$d7c8b140$875a13c0$@com>
From: "Weingarten, Yaacov (NSN - IL/Hod HaSharon)" <yaacov.weingarten@nsn.com>
To: "ext Jie Dong" <dongjie_dj@huawei.com>, <mpls-tp@ietf.org>, <mpls@ietf.org>
X-OriginalArrivalTime: 16 Feb 2011 14:08:51.0980 (UTC) FILETIME=[0A08A4C0:01CBCDE3]
Subject: Re: [mpls-tp] mpls wg last callon	draft-ietf-mpls-tp-linear-protection-04
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 14:08:39 -0000

Jie, hi

Thank you for your very detailed comments, see replies in-line

BR,
yaacov

>> -----Original Message-----
>> From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On
>> Behalf Of ext Jie Dong
>> Sent: Friday, February 11, 2011 10:44 AM
>> To: mpls-tp@ietf.org; mpls@ietf.org
>> Subject: Re: [mpls-tp] mpls wg last callon draft-ietf-mpls-tp-linear-
>> protection-04
>>=20
>> Dear authors,
>>=20
>> Here are some comments on linear protection draft.
>>=20
>> 1. In section 1.2, it says:
>> " The basic protocol is designed for use in conjunction with the 1:1
>> protection architecture (for both unidirectional and bidirectional
>> protection) and for 1+1 protection of a bidirectional path (for both
>> unidirectional and bidirectional protection switching). "
>>=20
>> Would you please explain why coordination is needed for
unidirectional
>> protection switching in 1+1 protection of a bidirectional path?
>> Because
>> section 4.7.2 of tp-survive-fwk says:
>> "In 1+1 unidirectional protection switching there is no need to
>> coordinate
>> the protection state between the protection controllers at both ends
>> of the
>> protection domain."

yw> Yes, you are correct that there is no need for coordination for
unidirectional protection however this protocol could be used by the
endpoints to coordinate information regarding the state of the network.=20
>>=20
>> I guess you mean 1+1 protection may need coordination to keep traffic
>> on
>> co-routed paths, but that would be bidirectional protection
switching.
>> Hope this could be made clearer in this draft.

yw> we will try to clarify this better in the next version.
>>=20
>> 2. Section 2.1, Acronyms
>> The full name of "LER" should be "Label Edge Router"
>> "PST" is an old term replaced by SPME (Sub-Path Maintenance Entity),
>> but
>> neither is used in the following sections, so it may be removed from
>> acronyms.

Yw>  You are correct and this will be corrected as suggested.
>>=20
>> 3. In Section 3, there is only one level-2 subsection (3.1), so what
>> about
>> promote the level-3 subtitles (3.1.1, 3.1.2, ...) to level-2, and
>> level-4
>> (3.1.6.1) to level-3?

yw> Thank you for pointing this out!
>>=20
>> 4. Section 4, 3rd paragraph, s/single-phase/single-phased, to be
>> consistent
>> with 2nd paragraph.

yw> Thank you
>>=20
>> 5. Section 4.1, 4th paragraph,
>> " In the event a signal fail condition is detected on the protection
>> path,
>> the received PSC specific information should be evaluated."
>> The statement is vague. What would be the state and action when a
>> signal
>> fail is detected on the protection path? Would you please elaborate
on
>> this
>> point?

yw> will try to clarify in the next version.
>>=20
>> 6. Section 4.2.2, 4th paragraph,
>> " The Fpath field SHALL identify the path that is reporting the
>> failure
>> condition (i.e. if protection path then Fpath is set to 0...".
>> Since PSC message are only transmitted on protection path, if
>> protection
>> path has signal fail, the PSC message may not be able to be sent out
>> to
>> far-end.

yw>  Actually, if there is a signal failure on the protection path,
there is a possibility that the messages may not be received by the
far-end, however, it is advisable that the source end-point continue to
transmit these messages.
>>=20
>> 7. Section 4.3.2, there is signal degrade on working path as input,
>> but no
>> signal degrade on protection path.

yw> Currently, the signal degrade input in this list is a place holder -
the issue of how to deal with SD in general is for further study as
stated in section 4.2.2.  Note - there have been lengthy discussions at
several IETF meetings on how to deal with SD without any conclusions.

>>=20
>> 8. Section 4.3.3, I go through this part fast, a general question is:
>> are
>> the PSC operations for 4 different protection types identical ? In
>> this
>> section there is no description about operation of each specific
>> protection
>> type, but to my understanding, there may be different operations,
>> e.g., for
>> bidirectional 1:1 protection, the end point may need to switch the
>> sink
>> selector and transmitting bridge simultaneously according to some
>> input, but
>> for unidirectional 1:1 the end point may only need to switch the
>> transmitting bridge OR the sink selector. And the PSC message sent
may
>> also
>> be different for different protection types. (Please correct me if
>> there is
>> anything wrong with this thought).

yw> Can you clarify for which scenario you believe that the messages
generated should be different dependent upon the protection type (aside
from the value of the protection type field)?  The exact actions of the
selector and transmitting bridges are not fully described in the
document aside from the note at the end of section 4.3.1.  In addition,
in the introductory text of each state description in section 4.3.3.3.x
describe how the user data is being transmitted.  Is there a feeling
that we need to describe this separately for each scenario?
>>=20
>>=20
>> Best Regards,
>> Jie
>>=20
>> > -----Original Message-----
>> > From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On
>> > Behalf Of Loa Andersson
>> > Sent: Thursday, February 03, 2011 7:42 PM
>> > To: mpls-tp@ietf.org; mpls@ietf.org
>> > Cc: ahmpls-tp@lists.itu.int
>> > Subject: [mpls-tp] mpls wg last call on
>> draft-ietf-mpls-tp-linear-protection-04
>> >
>> > Working Group,
>> >
>> > this is to start a four week working group last call on
>> > "MPLS-TP Linear Protection" (draft-ietf-mpls-tp-linear-protection-
>> 04).
>> >
>> > Please send comments to the mpls-tp@ietf.org mailing list.
>> >
>> > This working group last call ends on February 28, 2011.
>> >
>> >
>> >
>> > Loa, George and Ross
>> >
>> > MPLS wg co-chairs
>> >
>> >
>> >
>> > --
>> >
>> >
>> > Loa Andersson                         email:
>> > loa.andersson@ericsson.com
>> > Sr Strategy and Standards Manager            loa@pi.nu
>> > Ericsson Inc                          phone: +46 10 717 52 13
>> >                                               +46 767 72 92 13
>> > _______________________________________________
>> > mpls-tp mailing list
>> > mpls-tp@ietf.org
>> > https://www.ietf.org/mailman/listinfo/mpls-tp
>>=20
>>=20
>>=20
>> _______________________________________________
>> mpls-tp mailing list
>> mpls-tp@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls-tp

From Feng.f.Huang@alcatel-sbell.com.cn  Wed Feb 16 08:43:01 2011
Return-Path: <Feng.f.Huang@alcatel-sbell.com.cn>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B34D3A6E8B; Wed, 16 Feb 2011 08:43:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.149
X-Spam-Level: 
X-Spam-Status: No, score=-0.149 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_CHARSET_FARAWAY=2.45]
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 Zlylfp7sTrqO; Wed, 16 Feb 2011 08:43:00 -0800 (PST)
Received: from cnshjsmin03.alcatel-sbell.com.cn (cnshjsmin03.alcatel-sbell.com.cn [211.144.215.47]) by core3.amsl.com (Postfix) with ESMTP id C5F243A6E80; Wed, 16 Feb 2011 08:42:59 -0800 (PST)
X-AuditID: ac189297-b7c82ae0000013a2-b2-4d5bfeae8e47
Received: from cnshgsbhs01.ad4.ad.alcatel.com (smtp.cn.alcatel-lucent.com [172.24.146.145]) by cnshjsmin03.alcatel-sbell.com.cn (Symantec Brightmail Gateway) with SMTP id AE.D8.05026.EAEFB5D4; Thu, 17 Feb 2011 00:43:26 +0800 (HKT)
Received: from CNSHGSMBS01.ad4.ad.alcatel.com ([172.24.146.171]) by cnshgsbhs01.ad4.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 17 Feb 2011 00:42:53 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 17 Feb 2011 00:42:50 +0800
Message-ID: <FF8F3C1FD6EDF74CB6DD38B90FDEBADB07559154@CNSHGSMBS01.ad4.ad.alcatel.com>
In-Reply-To: <60C093A41B5E45409A19D42CF7786DFD51CDF3FEBE@EUSAACMS0703.eamcs.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] [mpls-tp] mpls wg last callon	draft-ietf-mpls-tp-cc-cv-rdi-03
Thread-Index: AcvDrJpCvXJpavHRRhKBBXlDzw1/zAFFYIGQABGDQCAAAKcQEAAlE/oAAA0+koABCO/PQA==
References: <4D4AB81D.3080907@pi.nu> <06c901cbc8d4$d682a820$8387f860$@com><60C093A41B5E45409A19D42CF7786DFD51CDF3F790@EUSAACMS0703.eamcs.ericsson.se><075b01cbc9c3$5a4ca810$0ee5f830$@com> <60C093A41B5E45409A19D42CF7786DFD51CDF3FEBE@EUSAACMS0703.eamcs.ericsson.se>
From: "HUANG Feng F" <Feng.f.Huang@alcatel-sbell.com.cn>
To: "David Allan I" <david.i.allan@ericsson.com>, <mpls-tp@ietf.org>, <mpls@ietf.org>, <ahmpls-tp@lists.itu.int>
X-OriginalArrivalTime: 16 Feb 2011 16:42:53.0555 (UTC) FILETIME=[8E711430:01CBCDF8]
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [mpls-tp] [mpls] mpls wg last callon	draft-ietf-mpls-tp-cc-cv-rdi-03
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 16:43:01 -0000

 Dear Dave,
     In 3.3. MPLS BFD proactive CV Message format, LSP/PW MEP ID is =
defined without MEG, how to detect Mismerge?
     And BFD protocol is enabled for period negotiation, when period is =
different, lower one is used, then how to detection Uexpect period?
B.R.
Feng


-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of =
David Allan I
Sent: 2011=C4=EA2=D4=C211=C8=D5 18:12
To: Mach Chen; 'Loa Andersson'; mpls-tp@ietf.org; mpls@ietf.org; =
ahmpls-tp@lists.itu.int
Subject: Re: [mpls] [mpls-tp] mpls wg last callon =
draft-ietf-mpls-tp-cc-cv-rdi-03

OK, will do...

Dave=20

-----Original Message-----
From: Mach Chen [mailto:mach@huawei.com]
Sent: Friday, February 11, 2011 12:12 AM
To: David Allan I; 'Loa Andersson'; mpls-tp@ietf.org; mpls@ietf.org; =
ahmpls-tp@lists.itu.int
Subject: RE: [mpls] [mpls-tp] mpls wg last call on =
draft-ietf-mpls-tp-cc-cv-rdi-03

Hi Dave,

Thanks for your prompt response!

> >3 Section 3.5.2
> >" 4. Receipt of an expected session discriminator with an unexpected
label
> (mis-connectivity defect).", For a receiver, how does it know that the =

> session >discriminator is valid but the label is invalid? IMHO, this
defect is just
> another description of defect 3 . Suggest to remove it.
>=20
> If the session discriminator exists in the BFD database, it is
superficially a valid
> descriminator but the label of arrival can be incorrect. This may=20
> indicate
an
> implementation problem at the source MEP. What we were referring to in =
'3'
> was a session discriminator that did not exist in the local database,=20
> BFD
had
> never handed it out hence it could not be found.
>=20

OK, but more clarification text would be helpful.

Best regards,
Mach


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From david.i.allan@ericsson.com  Wed Feb 16 08:50:18 2011
Return-Path: <david.i.allan@ericsson.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B4FC33A6E84; Wed, 16 Feb 2011 08:50:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.854
X-Spam-Level: 
X-Spam-Status: No, score=-1.854 tagged_above=-999 required=5 tests=[AWL=-0.744, BAYES_05=-1.11]
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 F1JLXrYZ5XIr; Wed, 16 Feb 2011 08:50:15 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id 4F6B63A6B7C; Wed, 16 Feb 2011 08:50:14 -0800 (PST)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p1GHa9Ph003156; Wed, 16 Feb 2011 11:36:12 -0600
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.66]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Wed, 16 Feb 2011 11:50:38 -0500
From: David Allan I <david.i.allan@ericsson.com>
To: HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>, "ahmpls-tp@lists.itu.int" <ahmpls-tp@lists.itu.int>
Date: Wed, 16 Feb 2011 11:50:37 -0500
Thread-Topic: [mpls] [mpls-tp] mpls wg last callon draft-ietf-mpls-tp-cc-cv-rdi-03
Thread-Index: AcvDrJpCvXJpavHRRhKBBXlDzw1/zAFFYIGQABGDQCAAAKcQEAAlE/oAAA0+koABCO/PQAAAVVfQ
Message-ID: <60C093A41B5E45409A19D42CF7786DFD51CDFCE2D0@EUSAACMS0703.eamcs.ericsson.se>
References: <4D4AB81D.3080907@pi.nu> <06c901cbc8d4$d682a820$8387f860$@com><60C093A41B5E45409A19D42CF7786DFD51CDF3F790@EUSAACMS0703.eamcs.ericsson.se><075b01cbc9c3$5a4ca810$0ee5f830$@com> <60C093A41B5E45409A19D42CF7786DFD51CDF3FEBE@EUSAACMS0703.eamcs.ericsson.se> <FF8F3C1FD6EDF74CB6DD38B90FDEBADB07559154@CNSHGSMBS01.ad4.ad.alcatel.com>
In-Reply-To: <FF8F3C1FD6EDF74CB6DD38B90FDEBADB07559154@CNSHGSMBS01.ad4.ad.alcatel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [mpls-tp] [mpls] mpls wg last callon	draft-ietf-mpls-tp-cc-cv-rdi-03
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 16:50:18 -0000

HI Feng:

See section 7.1 of http://tools.ietf.org/html/draft-ietf-mpls-tp-identifier=
s-03 . IMO it is simply a terminology issue as to whether a MEG is encoded =
in the LSP and PW formats or not.

Section 3.5.1 of the CC-CV-BFD draft identifies that period negotiation is =
not used. So unexpected period occurs when one end unpexpectedly changes th=
e period advertised.

I hope this helps
Dave=20

-----Original Message-----
From: HUANG Feng F [mailto:Feng.f.Huang@alcatel-sbell.com.cn]=20
Sent: Wednesday, February 16, 2011 5:43 PM
To: David Allan I; mpls-tp@ietf.org; mpls@ietf.org; ahmpls-tp@lists.itu.int
Cc: Loa Andersson
Subject: RE: [mpls] [mpls-tp] mpls wg last callon draft-ietf-mpls-tp-cc-cv-=
rdi-03


 Dear Dave,
     In 3.3. MPLS BFD proactive CV Message format, LSP/PW MEP ID is defined=
 without MEG, how to detect Mismerge?
     And BFD protocol is enabled for period negotiation, when period is dif=
ferent, lower one is used, then how to detection Uexpect period?
B.R.
Feng


-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Dav=
id Allan I
Sent: 2011=1B$BG/=1B(B2=1B$B7n=1B(B11=1B$BF|=1B(B 18:12
To: Mach Chen; 'Loa Andersson'; mpls-tp@ietf.org; mpls@ietf.org; ahmpls-tp@=
lists.itu.int
Subject: Re: [mpls] [mpls-tp] mpls wg last callon draft-ietf-mpls-tp-cc-cv-=
rdi-03

OK, will do...

Dave=20

-----Original Message-----
From: Mach Chen [mailto:mach@huawei.com]
Sent: Friday, February 11, 2011 12:12 AM
To: David Allan I; 'Loa Andersson'; mpls-tp@ietf.org; mpls@ietf.org; ahmpls=
-tp@lists.itu.int
Subject: RE: [mpls] [mpls-tp] mpls wg last call on draft-ietf-mpls-tp-cc-cv=
-rdi-03

Hi Dave,

Thanks for your prompt response!

> >3 Section 3.5.2
> >" 4. Receipt of an expected session discriminator with an unexpected
label
> (mis-connectivity defect).", For a receiver, how does it know that the=20
> session >discriminator is valid but the label is invalid? IMHO, this
defect is just
> another description of defect 3 . Suggest to remove it.
>=20
> If the session discriminator exists in the BFD database, it is
superficially a valid
> descriminator but the label of arrival can be incorrect. This may=20
> indicate
an
> implementation problem at the source MEP. What we were referring to in '3=
'
> was a session discriminator that did not exist in the local database,=20
> BFD
had
> never handed it out hence it could not be found.
>=20

OK, but more clarification text would be helpful.

Best regards,
Mach


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From eosborne@cisco.com  Wed Feb 16 09:57:43 2011
Return-Path: <eosborne@cisco.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CDA4E3A6EDE; Wed, 16 Feb 2011 09:57:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 q-oIHFdoz14i; Wed, 16 Feb 2011 09:57:43 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id C20053A6D27; Wed, 16 Feb 2011 09:57:42 -0800 (PST)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiABADKfW02tJV2a/2dsb2JhbACXI45Ic6Bqm1UCgnuCYQSFCIVxhE8
X-IronPort-AV: E=Sophos;i="4.60,480,1291593600"; d="scan'208";a="216386923"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rtp-iport-2.cisco.com with ESMTP; 16 Feb 2011 17:58:11 +0000
Received: from xbh-rcd-301.cisco.com (xbh-rcd-301.cisco.com [72.163.63.8]) by rcdn-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p1GHwALI001388;  Wed, 16 Feb 2011 17:58:10 GMT
Received: from xmb-rcd-202.cisco.com ([72.163.62.209]) by xbh-rcd-301.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 16 Feb 2011 11:58:10 -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
Date: Wed, 16 Feb 2011 11:58:09 -0600
Message-ID: <D29E470202D67745B61059870F433B540461B15B@XMB-RCD-202.cisco.com>
In-Reply-To: <021101cbc9c7$d7c8b140$875a13c0$@com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls-tp] mpls wg last callon	draft-ietf-mpls-tp-linear-protection-04
Thread-Index: AcvDl10fqyGU6Z/HTcaxkW43UzP3eAFXdT1gAUNLvlA=
References: <4D4A9478.7050704@pi.nu> <021101cbc9c7$d7c8b140$875a13c0$@com>
From: "Eric Osborne (eosborne)" <eosborne@cisco.com>
To: "Jie Dong" <dongjie_dj@huawei.com>, <mpls-tp@ietf.org>, <mpls@ietf.org>
X-OriginalArrivalTime: 16 Feb 2011 17:58:10.0887 (UTC) FILETIME=[12FB3D70:01CBCE03]
Subject: Re: [mpls-tp] mpls wg last callon	draft-ietf-mpls-tp-linear-protection-04
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 17:57:43 -0000

Hi Jie-

  Yaacov has replied to most of your comments, but let me add two
things:


>=20
> 6. Section 4.2.2, 4th paragraph,
> " The Fpath field SHALL identify the path that is reporting the
failure
> condition (i.e. if protection path then Fpath is set to 0...".
> Since PSC message are only transmitted on protection path, if
protection
> path has signal fail, the PSC message may not be able to be sent out
to
> far-end.


As Yaacov has mentioned, we would like the PSC to send messages anyways
in the chance that they may get through.  This is explicitly noted in
section 4.3.3.2:

---
"When the domain is in unavailable state the PSC messages may not get
through and therefore the protection is more dependent on the local
inputs rather than the remote messages (that may not be received)."
----

Is that sufficient, or do you think we need additional text to reinforce
this point?

> 8. Section 4.3.3, I go through this part fast, a general question is:
are
> the PSC operations for 4 different protection types identical ? In
this
> section there is no description about operation of each specific
> protection type, but to my understanding, there may be different
> operations, e.g., for bidirectional 1:1 protection, the end point may
need
> to switch the sink selector and transmitting bridge simultaneously
> according to some input, but for unidirectional 1:1 the end point may
only
> need to switch the transmitting bridge OR the sink selector. And the
PSC
> message sent may also be different for different protection types.
(Please
> correct me if there is anything wrong with this thought).


PSC is not, in my view, tightly coupled to the four protection types.
That is to say, PSC is a tool that allows the device vendor and network
operator to build protection in an MPLS-TP network.  This protection can
be one of the four protection types you describe, but PSC is merely a
protocol to accomplish the end goal.  It may, for example, be possible
in the future to use PSC to build one or more types of 1:n protection;
when and if this is done, the message types would likely remain the same
as they are now.



eric



>=20
>=20
> Best Regards,
> Jie
>=20
> > -----Original Message-----
> > From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On
> > Behalf Of Loa Andersson
> > Sent: Thursday, February 03, 2011 7:42 PM
> > To: mpls-tp@ietf.org; mpls@ietf.org
> > Cc: ahmpls-tp@lists.itu.int
> > Subject: [mpls-tp] mpls wg last call on
> draft-ietf-mpls-tp-linear-protection-04
> >
> > Working Group,
> >
> > this is to start a four week working group last call on "MPLS-TP
> > Linear Protection" (draft-ietf-mpls-tp-linear-protection-04).
> >
> > Please send comments to the mpls-tp@ietf.org mailing list.
> >
> > This working group last call ends on February 28, 2011.
> >
> >
> >
> > Loa, George and Ross
> >
> > MPLS wg co-chairs
> >
> >
> >
> > --
> >
> >
> > Loa Andersson                         email:
> > loa.andersson@ericsson.com
> > Sr Strategy and Standards Manager            loa@pi.nu
> > Ericsson Inc                          phone: +46 10 717 52 13
> >                                               +46 767 72 92 13
> > _______________________________________________
> > mpls-tp mailing list
> > mpls-tp@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls-tp
>=20
>=20
>=20
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp

From dai.xuehui@zte.com.cn  Wed Feb 16 18:55:14 2011
Return-Path: <dai.xuehui@zte.com.cn>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 82A343A6C31; Wed, 16 Feb 2011 18:55:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.776
X-Spam-Level: 
X-Spam-Status: No, score=-95.776 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
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 k5VKTkrMQu4b; Wed, 16 Feb 2011 18:55:13 -0800 (PST)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 4127E3A6CE5; Wed, 16 Feb 2011 18:55:12 -0800 (PST)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 205951911657480; Thu, 17 Feb 2011 10:50:38 +0800 (CST)
Received: from [10.30.3.21] by [192.168.168.15] with StormMail ESMTP id 84746.3038837400; Thu, 17 Feb 2011 10:55:34 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id p1H2tStJ072957; Thu, 17 Feb 2011 10:55:28 +0800 (GMT-8) (envelope-from dai.xuehui@zte.com.cn)
In-Reply-To: <4D4A9478.7050704@pi.nu>
To: Loa Andersson <loa@pi.nu>
MIME-Version: 1.0
X-KeepSent: A15D6179:FFA847CB-4825783A:000F9AEF; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFA15D6179.FFA847CB-ON4825783A.000F9AEF-4825783A.001011BD@zte.com.cn>
From: dai.xuehui@zte.com.cn
Date: Thu, 17 Feb 2011 10:55:26 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-02-17 10:55:28, Serialize complete at 2011-02-17 10:55:28
Content-Type: multipart/alternative; boundary="=_alternative 001011BB4825783A_="
X-MAIL: mse02.zte.com.cn p1H2tStJ072957
Cc: mpls@ietf.org, ahmpls-tp@lists.itu.int, mpls-tp-bounces@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls-tp] mpls wg last call on draft-ietf-mpls-tp-linear-protection-04
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Feb 2011 02:55:14 -0000

This is a multipart message in MIME format.
--=_alternative 001011BB4825783A_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

RGVhciBhdXRob3Jzo6wNCg0KQmVsb3cgYXJlIHR3byBjb21tZW50czoNCg0KMS4gaW4gc2VjdGlv
biAzLjEuNi4gIFBTQyBDb250cm9sIFN0YXRlcw0KdGhlIGRlZmluaXRpb24gb2YgdW5hdmFpbGFi
bGUgc3RhdGUgaXMgOg0KIlVuYXZhaWxhYmxlIHN0YXRlIC0gVGhlIHByb3RlY3Rpb24gcGF0aCBp
cyB1bmF2YWlsYWJsZSAtIGVpdGhlciBhcyBhIA0KcmVzdWx0IG9mIGFuIG9wZXJhdG9yIExvY2tv
dXQgY29tbWFuZCBvciBhIGZhaWx1cmUvZGVncmFkZSBjb25kaXRpb24gDQpkZXRlY3RlZCBvbiB0
aGUgcHJvdGVjdGlvbiBwYXRoLiINCmJ1dCBpbiB0aGUgZmlyc3QgcGFyYWdyYXBoIG9mIHNlY3Rp
b24gNC4zLjMuMi4sICB0aGUgY2F1c2Ugb2YgdW5hdmFpbGFibGUgDQpzdGF0ZSBkb2VzIG5vdCBp
bmNsdWRlICB0aGlzIGRlZ3JhZGUgY29uZGl0aW9uIGRldGVjdGVkIG9uIHRoZSBwcm90ZWN0aW9u
IA0KcGF0aC4NCg0KdGhlc2UgdHdvIGRlc2NyaXB0aW9ucyBhcmUgbm90IGNvbnNpc3RlbnQuDQoN
CjIuIHR5cG8gDQp0aGUgZmlyc3QgcGFyYWdyYWdoICBpbiBzZWN0aW9uIDQuMy4zLjQuLCAicmVt
b3RlIFNGIFBDUyBtZXNzYWdlIiBzaGFsbCBiZSANCmNoYW5nZWQgdG8gInJlbW90ZSBTRiBQU0Mg
IG1lc3NhZ2UiIA0KDQpCZXN0IFJlZ2FyZHMsDQp4dWVodWkNCg0KDQoNCg0KTG9hIEFuZGVyc3Nv
biA8bG9hQHBpLm51PiANCreivP7IyzogIG1wbHMtdHAtYm91bmNlc0BpZXRmLm9yZw0KMjAxMS0w
Mi0wMyAxOTo0MQ0KDQrK1bz+yMsNCm1wbHMtdHBAaWV0Zi5vcmcsIG1wbHNAaWV0Zi5vcmcNCrOt
y80NCmFobXBscy10cEBsaXN0cy5pdHUuaW50DQrW98ziDQpbbXBscy10cF0gbXBscyB3ZyBsYXN0
IGNhbGwgb24gIGRyYWZ0LWlldGYtbXBscy10cC1saW5lYXItcHJvdGVjdGlvbi0wNA0KDQoNCg0K
DQoNCg0KV29ya2luZyBHcm91cCwNCg0KdGhpcyBpcyB0byBzdGFydCBhIGZvdXIgd2VlayB3b3Jr
aW5nIGdyb3VwIGxhc3QgY2FsbCBvbg0KIk1QTFMtVFAgTGluZWFyIFByb3RlY3Rpb24iIChkcmFm
dC1pZXRmLW1wbHMtdHAtbGluZWFyLXByb3RlY3Rpb24tMDQpLg0KDQpQbGVhc2Ugc2VuZCBjb21t
ZW50cyB0byB0aGUgbXBscy10cEBpZXRmLm9yZyBtYWlsaW5nIGxpc3QuDQoNClRoaXMgd29ya2lu
ZyBncm91cCBsYXN0IGNhbGwgZW5kcyBvbiBGZWJydWFyeSAyOCwgMjAxMS4NCg0KDQoNCkxvYSwg
R2VvcmdlIGFuZCBSb3NzDQoNCk1QTFMgd2cgY28tY2hhaXJzDQoNCg0KDQotLSANCg0KDQpMb2Eg
QW5kZXJzc29uICAgICAgICAgICAgICAgICAgICAgICAgIGVtYWlsOiBsb2EuYW5kZXJzc29uQGVy
aWNzc29uLmNvbQ0KU3IgU3RyYXRlZ3kgYW5kIFN0YW5kYXJkcyBNYW5hZ2VyICAgICAgICAgICAg
bG9hQHBpLm51DQpFcmljc3NvbiBJbmMgICAgICAgICAgICAgICAgICAgICAgICAgIHBob25lOiAr
NDYgMTAgNzE3IDUyIDEzDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgKzQ2IDc2NyA3MiA5MiAxMw0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18NCm1wbHMtdHAgbWFpbGluZyBsaXN0DQptcGxzLXRwQGlldGYub3JnDQpo
dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21wbHMtdHANCg0KDQoNCg==
--=_alternative 001011BB4825783A_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkRlYXIgYXV0aG9yc6OsPC9mb250
Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5CZWxvdyBhcmUgdHdv
IGNvbW1lbnRzOjwvZm9udD4NCjxicj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJp
ZiI+MS4gaW4gc2VjdGlvbiAzLjEuNi4gJm5ic3A7UFNDIENvbnRyb2wNClN0YXRlczwvZm9udD4N
Cjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+dGhlIGRlZmluaXRpb24gb2YgdW5h
dmFpbGFibGUgc3RhdGUNCmlzIDo8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMt
c2VyaWYiPiZxdW90O1VuYXZhaWxhYmxlIHN0YXRlIC0gVGhlIHByb3RlY3Rpb24NCnBhdGggaXMg
dW5hdmFpbGFibGUgLSBlaXRoZXIgYXMgYSByZXN1bHQgb2YgYW4gb3BlcmF0b3IgTG9ja291dCBj
b21tYW5kDQpvciBhIGZhaWx1cmUvZGVncmFkZSBjb25kaXRpb24gZGV0ZWN0ZWQgb24gdGhlIHBy
b3RlY3Rpb24gcGF0aC4mcXVvdDs8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMt
c2VyaWYiPmJ1dCBpbiB0aGUgZmlyc3QgcGFyYWdyYXBoIG9mIHNlY3Rpb24NCjQuMy4zLjIuLCAm
bmJzcDt0aGUgY2F1c2Ugb2YgdW5hdmFpbGFibGUgc3RhdGUgZG9lcyBub3QgaW5jbHVkZSAmbmJz
cDt0aGlzDQpkZWdyYWRlIGNvbmRpdGlvbiBkZXRlY3RlZCBvbiB0aGUgcHJvdGVjdGlvbiBwYXRo
LjwvZm9udD4NCjxicj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+dGhlc2Ug
dHdvIGRlc2NyaXB0aW9ucyBhcmUgbm90IGNvbnNpc3RlbnQuPC9mb250Pg0KPGJyPg0KPGJyPjxm
b250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4yLiB0eXBvIDwvZm9udD4NCjxicj48Zm9udCBz
aXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+dGhlIGZpcnN0IHBhcmFncmFnaCAmbmJzcDtpbiBzZWN0
aW9uDQo0LjMuMy40LiwgJnF1b3Q7cmVtb3RlIFNGIFBDUyBtZXNzYWdlJnF1b3Q7IHNoYWxsIGJl
IGNoYW5nZWQgdG8gJnF1b3Q7cmVtb3RlDQpTRiBQU0MgJm5ic3A7bWVzc2FnZSZxdW90OyA8L2Zv
bnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkJlc3QgUmVnYXJk
cyw8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPnh1ZWh1aTwvZm9u
dD4NCjxicj4NCjxicj4NCjxicj4NCjxicj4NCjx0YWJsZSB3aWR0aD0xMDAlPg0KPHRyIHZhbGln
bj10b3A+DQo8dGQgd2lkdGg9MzUlPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj48Yj5M
b2EgQW5kZXJzc29uICZsdDtsb2FAcGkubnUmZ3Q7PC9iPg0KPC9mb250Pg0KPGJyPjxmb250IHNp
emU9MSBmYWNlPSJzYW5zLXNlcmlmIj63orz+yMs6ICZuYnNwO21wbHMtdHAtYm91bmNlc0BpZXRm
Lm9yZzwvZm9udD4NCjxwPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj4yMDExLTAyLTAz
IDE5OjQxPC9mb250Pg0KPHRkIHdpZHRoPTY0JT4NCjx0YWJsZSB3aWR0aD0xMDAlPg0KPHRyIHZh
bGlnbj10b3A+DQo8dGQ+DQo8ZGl2IGFsaWduPXJpZ2h0Pjxmb250IHNpemU9MSBmYWNlPSJzYW5z
LXNlcmlmIj7K1bz+yMs8L2ZvbnQ+PC9kaXY+DQo8dGQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMt
c2VyaWYiPm1wbHMtdHBAaWV0Zi5vcmcsIG1wbHNAaWV0Zi5vcmc8L2ZvbnQ+DQo8dHIgdmFsaWdu
PXRvcD4NCjx0ZD4NCjxkaXYgYWxpZ249cmlnaHQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2Vy
aWYiPrOty808L2ZvbnQ+PC9kaXY+DQo8dGQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYi
PmFobXBscy10cEBsaXN0cy5pdHUuaW50PC9mb250Pg0KPHRyIHZhbGlnbj10b3A+DQo8dGQ+DQo8
ZGl2IGFsaWduPXJpZ2h0Pjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj7W98ziPC9mb250
PjwvZGl2Pg0KPHRkPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj5bbXBscy10cF0gbXBs
cyB3ZyBsYXN0IGNhbGwgb24gJm5ic3A7DQombmJzcDsgJm5ic3A7ICZuYnNwO2RyYWZ0LWlldGYt
bXBscy10cC1saW5lYXItcHJvdGVjdGlvbi0wNDwvZm9udD48L3RhYmxlPg0KPGJyPg0KPHRhYmxl
Pg0KPHRyIHZhbGlnbj10b3A+DQo8dGQ+DQo8dGQ+PC90YWJsZT4NCjxicj48L3RhYmxlPg0KPGJy
Pg0KPGJyPg0KPGJyPjx0dD48Zm9udCBzaXplPTI+V29ya2luZyBHcm91cCw8YnI+DQo8YnI+DQp0
aGlzIGlzIHRvIHN0YXJ0IGEgZm91ciB3ZWVrIHdvcmtpbmcgZ3JvdXAgbGFzdCBjYWxsIG9uPGJy
Pg0KJnF1b3Q7TVBMUy1UUCBMaW5lYXIgUHJvdGVjdGlvbiZxdW90OyAoZHJhZnQtaWV0Zi1tcGxz
LXRwLWxpbmVhci1wcm90ZWN0aW9uLTA0KS48YnI+DQo8YnI+DQpQbGVhc2Ugc2VuZCBjb21tZW50
cyB0byB0aGUgbXBscy10cEBpZXRmLm9yZyBtYWlsaW5nIGxpc3QuPGJyPg0KPGJyPg0KVGhpcyB3
b3JraW5nIGdyb3VwIGxhc3QgY2FsbCBlbmRzIG9uIEZlYnJ1YXJ5IDI4LCAyMDExLjxicj4NCjxi
cj4NCjxicj4NCjxicj4NCkxvYSwgR2VvcmdlIGFuZCBSb3NzPGJyPg0KPGJyPg0KTVBMUyB3ZyBj
by1jaGFpcnM8YnI+DQo8YnI+DQo8YnI+DQo8YnI+DQotLSA8YnI+DQo8YnI+DQo8YnI+DQpMb2Eg
QW5kZXJzc29uICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7DQombmJzcDsgJm5ic3A7ICZuYnNwOyBlbWFpbDogbG9hLmFuZGVyc3Nv
bkBlcmljc3Nvbi5jb208YnI+DQpTciBTdHJhdGVneSBhbmQgU3RhbmRhcmRzIE1hbmFnZXIgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtsb2FAcGkubnU8YnI+DQpFcmlj
c3NvbiBJbmMgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsNCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO3Bob25lOiArNDYgMTAg
NzE3IDUyIDEzPGJyPg0KICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOw0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOw0KJm5ic3A7
ICZuYnNwOys0NiA3NjcgNzIgOTIgMTM8YnI+DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXzxicj4NCm1wbHMtdHAgbWFpbGluZyBsaXN0PGJyPg0KbXBscy10
cEBpZXRmLm9yZzxicj4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbXBs
cy10cDxicj4NCjxicj4NCjwvZm9udD48L3R0Pg0KPGJyPg0K
--=_alternative 001011BB4825783A_=--


From Feng.f.Huang@alcatel-sbell.com.cn  Wed Feb 16 22:27:33 2011
Return-Path: <Feng.f.Huang@alcatel-sbell.com.cn>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6C5FD3A6D7B; Wed, 16 Feb 2011 22:27:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.149
X-Spam-Level: 
X-Spam-Status: No, score=-0.149 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_CHARSET_FARAWAY=2.45]
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 6+0PcCC6XG-p; Wed, 16 Feb 2011 22:27:24 -0800 (PST)
Received: from cnshjsmin03.alcatel-sbell.com.cn (cnshjsmin03.alcatel-sbell.com.cn [211.144.215.47]) by core3.amsl.com (Postfix) with ESMTP id D6A043A6D6A; Wed, 16 Feb 2011 22:27:20 -0800 (PST)
X-AuditID: ac189297-b7c82ae0000013a2-31-4d5cbfe5a0c5
Received: from cnshgsbhs01.ad4.ad.alcatel.com (smtp.cn.alcatel-lucent.com [172.24.146.145]) by cnshjsmin03.alcatel-sbell.com.cn (Symantec Brightmail Gateway) with SMTP id 7F.69.05026.5EFBC5D4; Thu, 17 Feb 2011 14:27:49 +0800 (HKT)
Received: from CNSHGSMBS01.ad4.ad.alcatel.com ([172.24.146.171]) by cnshgsbhs01.ad4.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 17 Feb 2011 14:27:16 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 17 Feb 2011 14:27:12 +0800
Message-ID: <FF8F3C1FD6EDF74CB6DD38B90FDEBADB075596E2@CNSHGSMBS01.ad4.ad.alcatel.com>
In-Reply-To: <60C093A41B5E45409A19D42CF7786DFD51CDFCE2D0@EUSAACMS0703.eamcs.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] [mpls-tp] mpls wg last callondraft-ietf-mpls-tp-cc-cv-rdi-03
Thread-Index: AcvDrJpCvXJpavHRRhKBBXlDzw1/zAFFYIGQABGDQCAAAKcQEAAlE/oAAA0+koABCO/PQAAAVVfQAABHbLA=
References: <4D4AB81D.3080907@pi.nu> <06c901cbc8d4$d682a820$8387f860$@com><60C093A41B5E45409A19D42CF7786DFD51CDF3F790@EUSAACMS0703.eamcs.ericsson.se><075b01cbc9c3$5a4ca810$0ee5f830$@com> <60C093A41B5E45409A19D42CF7786DFD51CDF3FEBE@EUSAACMS0703.eamcs.ericsson.se> <FF8F3C1FD6EDF74CB6DD38B90FDEBADB07559154@CNSHGSMBS01.ad4.ad.alcatel.com> <60C093A41B5E45409A19D42CF7786DFD51CDFCE2D0@EUSAACMS0703.eamcs.ericsson.se>
From: "HUANG Feng F" <Feng.f.Huang@alcatel-sbell.com.cn>
To: "David Allan I" <david.i.allan@ericsson.com>, <mpls-tp@ietf.org>, <mpls@ietf.org>, <ahmpls-tp@lists.itu.int>
X-OriginalArrivalTime: 17 Feb 2011 06:27:16.0410 (UTC) FILETIME=[B899C9A0:01CBCE6B]
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [mpls-tp] [mpls] mpls wg last callondraft-ietf-mpls-tp-cc-cv-rdi-03
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Feb 2011 06:27:33 -0000

Hi,Dave,
     Thanks, LSP MEP ID in draft-ietf-mpls-tp-identifiers-03 is: =
Node_ID::Tunnel_Num::LSP_Num, =20

and for LSP MEG ID: (7.1.2.1.)
    Since a MEG pertains to a single MPLS-TP LSP, IP compatible MEG_IDs
   for MPLS-TP LSPs are simply the corresponding LSP_IDs.  We note that
   while the two identifiers are syntactically identical, they have
   different semantics.  This semantic difference needs to be made
   clear.  For instance if both a MPLS-TP LSP_ID and MPLS-TP LSP MEG_IDs
   are to be encoded in TLVs different types need to be assigned for
   these two identifiers.
=20
you can only detect wrong MEP ID, that's Unexpected MEP, it is not =
Mis-merge.

     =20
If period negotiation is not used, how to insure interoperability with =
BFD used in IP/MPLS asked always by providers?

B.R.
Feng
=20

-----Original Message-----
From: David Allan I [mailto:david.i.allan@ericsson.com]=20
Sent: 2011=C4=EA2=D4=C217=C8=D5 0:51
To: HUANG Feng F; mpls-tp@ietf.org; mpls@ietf.org; =
ahmpls-tp@lists.itu.int
Cc: Loa Andersson
Subject: RE: [mpls] [mpls-tp] mpls wg last =
callondraft-ietf-mpls-tp-cc-cv-rdi-03

HI Feng:

See section 7.1 of =
http://tools.ietf.org/html/draft-ietf-mpls-tp-identifiers-03 . IMO it is =
simply a terminology issue as to whether a MEG is encoded in the LSP and =
PW formats or not.

Section 3.5.1 of the CC-CV-BFD draft identifies that period negotiation =
is not used. So unexpected period occurs when one end unpexpectedly =
changes the period advertised.

I hope this helps
Dave=20

-----Original Message-----
From: HUANG Feng F [mailto:Feng.f.Huang@alcatel-sbell.com.cn]
Sent: Wednesday, February 16, 2011 5:43 PM
To: David Allan I; mpls-tp@ietf.org; mpls@ietf.org; =
ahmpls-tp@lists.itu.int
Cc: Loa Andersson
Subject: RE: [mpls] [mpls-tp] mpls wg last callon =
draft-ietf-mpls-tp-cc-cv-rdi-03


 Dear Dave,
     In 3.3. MPLS BFD proactive CV Message format, LSP/PW MEP ID is =
defined without MEG, how to detect Mismerge?
     And BFD protocol is enabled for period negotiation, when period is =
different, lower one is used, then how to detection Uexpect period?
B.R.
Feng


-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of =
David Allan I
Sent: 2011=C4=EA2=D4=C211=C8=D5 18:12
To: Mach Chen; 'Loa Andersson'; mpls-tp@ietf.org; mpls@ietf.org; =
ahmpls-tp@lists.itu.int
Subject: Re: [mpls] [mpls-tp] mpls wg last callon =
draft-ietf-mpls-tp-cc-cv-rdi-03

OK, will do...

Dave=20

-----Original Message-----
From: Mach Chen [mailto:mach@huawei.com]
Sent: Friday, February 11, 2011 12:12 AM
To: David Allan I; 'Loa Andersson'; mpls-tp@ietf.org; mpls@ietf.org; =
ahmpls-tp@lists.itu.int
Subject: RE: [mpls] [mpls-tp] mpls wg last call on =
draft-ietf-mpls-tp-cc-cv-rdi-03

Hi Dave,

Thanks for your prompt response!

> >3 Section 3.5.2
> >" 4. Receipt of an expected session discriminator with an unexpected
label
> (mis-connectivity defect).", For a receiver, how does it know that the =

> session >discriminator is valid but the label is invalid? IMHO, this
defect is just
> another description of defect 3 . Suggest to remove it.
>=20
> If the session discriminator exists in the BFD database, it is
superficially a valid
> descriminator but the label of arrival can be incorrect. This may=20
> indicate
an
> implementation problem at the source MEP. What we were referring to in =
'3'
> was a session discriminator that did not exist in the local database,=20
> BFD
had
> never handed it out hence it could not be found.
>=20

OK, but more clarification text would be helpful.

Best regards,
Mach


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From david.i.allan@ericsson.com  Thu Feb 17 00:01:35 2011
Return-Path: <david.i.allan@ericsson.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DD7583A6D84; Thu, 17 Feb 2011 00:01:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[AWL=0.149,  BAYES_00=-2.599]
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 CmuaEbvQfXwH; Thu, 17 Feb 2011 00:01:34 -0800 (PST)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by core3.amsl.com (Postfix) with ESMTP id AC02B3A6D48; Thu, 17 Feb 2011 00:01:34 -0800 (PST)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id p1H821OF032709 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 17 Feb 2011 02:02:01 -0600
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.66]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Thu, 17 Feb 2011 03:02:01 -0500
From: David Allan I <david.i.allan@ericsson.com>
To: HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>, "ahmpls-tp@lists.itu.int" <ahmpls-tp@lists.itu.int>
Date: Thu, 17 Feb 2011 03:01:34 -0500
Thread-Topic: [mpls] [mpls-tp] mpls wg last callondraft-ietf-mpls-tp-cc-cv-rdi-03
Thread-Index: AcvDrJpCvXJpavHRRhKBBXlDzw1/zAFFYIGQABGDQCAAAKcQEAAlE/oAAA0+koABCO/PQAAAVVfQAABHbLAAH2laQA==
Message-ID: <60C093A41B5E45409A19D42CF7786DFD51CDFCE7FC@EUSAACMS0703.eamcs.ericsson.se>
References: <4D4AB81D.3080907@pi.nu> <06c901cbc8d4$d682a820$8387f860$@com><60C093A41B5E45409A19D42CF7786DFD51CDF3F790@EUSAACMS0703.eamcs.ericsson.se><075b01cbc9c3$5a4ca810$0ee5f830$@com> <60C093A41B5E45409A19D42CF7786DFD51CDF3FEBE@EUSAACMS0703.eamcs.ericsson.se> <FF8F3C1FD6EDF74CB6DD38B90FDEBADB07559154@CNSHGSMBS01.ad4.ad.alcatel.com> <60C093A41B5E45409A19D42CF7786DFD51CDFCE2D0@EUSAACMS0703.eamcs.ericsson.se> <FF8F3C1FD6EDF74CB6DD38B90FDEBADB075596E2@CNSHGSMBS01.ad4.ad.alcatel.com>
In-Reply-To: <FF8F3C1FD6EDF74CB6DD38B90FDEBADB075596E2@CNSHGSMBS01.ad4.ad.alcatel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [mpls-tp] [mpls] mpls wg last callondraft-ietf-mpls-tp-cc-cv-rdi-03
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Feb 2011 08:01:36 -0000

Hi Feng:

I'm not sure how unexpected MEP is not indicative of a mismerge. Either the=
 source MEP ID has been misconfigured, or you are receiving a message from =
a MEP due to LIB corruption or similar defect somewhere in the network.=20

As for your second point, it is not that negotiation is not used, there is =
simply no give and take allowed, so the procedures are simply modified slig=
htly in the TP case . If the far end refuses to support the requested perio=
dicity for whatever reason, you do not progress beyond the INIT state and p=
resumably send some indication to management that the session could not com=
e "UP". You have that option whether you are conformant to CC-CV-RDI draft =
or simply RFC 5884. So as far as I can tell interoperability options exist,=
 they were always there in the protocol, we are simply providing implementa=
tion guidelines for the TP application...

I hope this helps
Dave

-----Original Message-----
From: HUANG Feng F [mailto:Feng.f.Huang@alcatel-sbell.com.cn]=20
Sent: Thursday, February 17, 2011 7:27 AM
To: David Allan I; mpls-tp@ietf.org; mpls@ietf.org; ahmpls-tp@lists.itu.int
Cc: Loa Andersson
Subject: RE: [mpls] [mpls-tp] mpls wg last callondraft-ietf-mpls-tp-cc-cv-r=
di-03

Hi,Dave,
     Thanks, LSP MEP ID in draft-ietf-mpls-tp-identifiers-03 is: Node_ID::T=
unnel_Num::LSP_Num, =20

and for LSP MEG ID: (7.1.2.1.)
    Since a MEG pertains to a single MPLS-TP LSP, IP compatible MEG_IDs
   for MPLS-TP LSPs are simply the corresponding LSP_IDs.  We note that
   while the two identifiers are syntactically identical, they have
   different semantics.  This semantic difference needs to be made
   clear.  For instance if both a MPLS-TP LSP_ID and MPLS-TP LSP MEG_IDs
   are to be encoded in TLVs different types need to be assigned for
   these two identifiers.
=20
you can only detect wrong MEP ID, that's Unexpected MEP, it is not Mis-merg=
e.

     =20
If period negotiation is not used, how to insure interoperability with BFD =
used in IP/MPLS asked always by providers?

B.R.
Feng
=20

-----Original Message-----
From: David Allan I [mailto:david.i.allan@ericsson.com]
Sent: 2011=1B$BG/=1B(B2=1B$B7n=1B(B17=1B$BF|=1B(B 0:51
To: HUANG Feng F; mpls-tp@ietf.org; mpls@ietf.org; ahmpls-tp@lists.itu.int
Cc: Loa Andersson
Subject: RE: [mpls] [mpls-tp] mpls wg last callondraft-ietf-mpls-tp-cc-cv-r=
di-03

HI Feng:

See section 7.1 of http://tools.ietf.org/html/draft-ietf-mpls-tp-identifier=
s-03 . IMO it is simply a terminology issue as to whether a MEG is encoded =
in the LSP and PW formats or not.

Section 3.5.1 of the CC-CV-BFD draft identifies that period negotiation is =
not used. So unexpected period occurs when one end unpexpectedly changes th=
e period advertised.

I hope this helps
Dave=20

-----Original Message-----
From: HUANG Feng F [mailto:Feng.f.Huang@alcatel-sbell.com.cn]
Sent: Wednesday, February 16, 2011 5:43 PM
To: David Allan I; mpls-tp@ietf.org; mpls@ietf.org; ahmpls-tp@lists.itu.int
Cc: Loa Andersson
Subject: RE: [mpls] [mpls-tp] mpls wg last callon draft-ietf-mpls-tp-cc-cv-=
rdi-03


 Dear Dave,
     In 3.3. MPLS BFD proactive CV Message format, LSP/PW MEP ID is defined=
 without MEG, how to detect Mismerge?
     And BFD protocol is enabled for period negotiation, when period is dif=
ferent, lower one is used, then how to detection Uexpect period?
B.R.
Feng


-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Dav=
id Allan I
Sent: 2011=1B$BG/=1B(B2=1B$B7n=1B(B11=1B$BF|=1B(B 18:12
To: Mach Chen; 'Loa Andersson'; mpls-tp@ietf.org; mpls@ietf.org; ahmpls-tp@=
lists.itu.int
Subject: Re: [mpls] [mpls-tp] mpls wg last callon draft-ietf-mpls-tp-cc-cv-=
rdi-03

OK, will do...

Dave=20

-----Original Message-----
From: Mach Chen [mailto:mach@huawei.com]
Sent: Friday, February 11, 2011 12:12 AM
To: David Allan I; 'Loa Andersson'; mpls-tp@ietf.org; mpls@ietf.org; ahmpls=
-tp@lists.itu.int
Subject: RE: [mpls] [mpls-tp] mpls wg last call on draft-ietf-mpls-tp-cc-cv=
-rdi-03

Hi Dave,

Thanks for your prompt response!

> >3 Section 3.5.2
> >" 4. Receipt of an expected session discriminator with an unexpected
label
> (mis-connectivity defect).", For a receiver, how does it know that the=20
> session >discriminator is valid but the label is invalid? IMHO, this
defect is just
> another description of defect 3 . Suggest to remove it.
>=20
> If the session discriminator exists in the BFD database, it is
superficially a valid
> descriminator but the label of arrival can be incorrect. This may=20
> indicate
an
> implementation problem at the source MEP. What we were referring to in '3=
'
> was a session discriminator that did not exist in the local database,=20
> BFD
had
> never handed it out hence it could not be found.
>=20

OK, but more clarification text would be helpful.

Best regards,
Mach


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From matthew.bocci@alcatel-lucent.com  Thu Feb 17 05:34:11 2011
Return-Path: <matthew.bocci@alcatel-lucent.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 29ED63A6CCA; Thu, 17 Feb 2011 05:34:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.249
X-Spam-Level: 
X-Spam-Status: No, score=-104.249 tagged_above=-999 required=5 tests=[AWL=2.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 7UWl1YKipeAQ; Thu, 17 Feb 2011 05:34:09 -0800 (PST)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by core3.amsl.com (Postfix) with ESMTP id 292023A6CAE; Thu, 17 Feb 2011 05:34:08 -0800 (PST)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p1HDXfjc008936 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 17 Feb 2011 14:34:38 +0100
Received: from FRMRSSXCHMBSA3.dc-m.alcatel-lucent.com ([135.120.45.38]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Thu, 17 Feb 2011 14:34:35 +0100
From: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Date: Thu, 17 Feb 2011 14:34:34 +0100
Thread-Topic: PWE3 WG LC on draft-ietf-pwe3-mpls-tp-gal-in-pw-00
Thread-Index: AcvOp2qo3CL3sSTlSLeLd/7Gd8zznQ==
Message-ID: <C982D469.98F5%matthew.bocci@alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.0.101115
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.83
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: [mpls-tp] PWE3 WG LC on draft-ietf-pwe3-mpls-tp-gal-in-pw-00
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Feb 2011 13:34:11 -0000

This email begins a working group last call for
draft-ietf-pwe3-mpls-tp-gal-in-pw-00.txt.

This is a very short draft but since there are other MPLS-TP-related last
calls going on concurrently, this will be a three-week last call.

This WG LC will end of 11th March 2011.

Please respond with any comments to the PWE3 mailing list.

Regards,

Matthew and Andy
=20


From mukund.mani@gmail.com  Thu Feb 17 06:07:50 2011
Return-Path: <mukund.mani@gmail.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 00BC23A6E0F; Thu, 17 Feb 2011 06:07:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 CHnYJv8hs01Y; Thu, 17 Feb 2011 06:07:48 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 17BC13A6D1A; Thu, 17 Feb 2011 06:07:47 -0800 (PST)
Received: by wyf23 with SMTP id 23so2711607wyf.31 for <multiple recipients>; Thu, 17 Feb 2011 06:08:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=bL5ILy66JKGs5ofhJBxjTpViSMUgVn2IFdL2uvuThxM=; b=OJC/LPFDy0AtzG4om1mISO3DvB1oIZbGVkSkX46xEx8THHmzuMMTzymfNwUk1QCAtH WVBamsNRKi122ri3SsM5AN1BxIiINph7DYfE7WtxqWdze2ykPGS4+SU2Wy8bodaovrqD CKHuJXnwbCWwLxTBCOKDTA0AURkvvcUEXP3ho=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=hFBgh256a3E2z9j+eqtU+MDXQ3knSEkuyKbxOr9zQCC77FUvt7XdVaPTRwnPI1JS9d mCRr6hygpr2VxFAkn0yGjcwQcN2r4svCh03R+Gx07yIn8EYGgWEuuUtmMnxqxackrxLW s3XgQaiMmmM3ijYwWqhR0MBzu/DKOPkGz0HUY=
MIME-Version: 1.0
Received: by 10.227.165.6 with SMTP id g6mr1701512wby.181.1297951698284; Thu, 17 Feb 2011 06:08:18 -0800 (PST)
Received: by 10.227.146.76 with HTTP; Thu, 17 Feb 2011 06:08:18 -0800 (PST)
In-Reply-To: <60C093A41B5E45409A19D42CF7786DFD51CDF3F8EE@EUSAACMS0703.eamcs.ericsson.se>
References: <AANLkTi=zeJTVn8gx_ZFefaS6adnFb20kWAnpDnDo2fP1@mail.gmail.com> <60C093A41B5E45409A19D42CF7786DFD51CDEF1D53@EUSAACMS0703.eamcs.ericsson.se> <AANLkTim_tQ46Ox=vYLm2fuzV=FP5zkOhM=b7m6qou2We@mail.gmail.com> <60C093A41B5E45409A19D42CF7786DFD51CDF3F8EE@EUSAACMS0703.eamcs.ericsson.se>
Date: Thu, 17 Feb 2011 19:38:18 +0530
Message-ID: <AANLkTi=e1YN7FDardhaEpcmh91R9NZsBsQMrbAC+6qRX@mail.gmail.com>
From: Mukund Mani <mukund.mani@gmail.com>
To: David Allan I <david.i.allan@ericsson.com>
Content-Type: multipart/alternative; boundary=20cf30025e78e971ca049c7aedbe
Cc: rtg-bfd@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls-tp] MPLS-ACH-IP and MPLS-IP encapsulations for BFD in MPLS-TP
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Feb 2011 14:07:50 -0000

--20cf30025e78e971ca049c7aedbe
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Dave

Thanks for your response..

Just want to touch upon further on this: "knowledge of the IP address of th=
e
source of the BFD packets".

We could ideally have the knowledge of source IP from the source IP address
of the established path over which BFD runs. But then should BFD (data
plane) actually depend on the source IP address of a control plane
established path, to do CV?

For instance, a tunnel (four tuple - Tunnel id, instance, ingress and egres=
s
id) could have the ingress id as the router id.

BFD control packets on the other hand could have the source IP as the
interface IP address.

How do we actually achieve CV in such a case ?

OR is it expected (by say a configuration mechanism) that each peer knows
the source IP of BFD packets for every session?

With Regards
Mukund

On Thu, Feb 10, 2011 at 9:06 PM, David Allan I
<david.i.allan@ericsson.com>wrote:

>  Hi Mikund:
>
> If I understand your question correctly, you would need knowledge of the =
IP
> address of the source of the BFD packets.
>
> cheers
> Dave
>
>  ------------------------------
> *From:* Mukund Mani [mailto:mukund.mani@gmail.com]
> *Sent:* Thursday, February 10, 2011 5:10 AM
> *To:* David Allan I
> *Cc:* rtg-bfd@ietf.org; mpls-tp@ietf.org
> *Subject:* Re: [mpls-tp] MPLS-ACH-IP and MPLS-IP encapsulations for BFD i=
n
> MPLS-TP
>
>   Hi Dave
>
> Not really clear on the first one.. Here we are not including trailing ME=
P
> TLV. How do we do CV for the first BFD packet with MPLS-IP encap ?
>
> With Regards
> Mukund
> On Wed, Feb 9, 2011 at 1:25 PM, David Allan I <david.i.allan@ericsson.com=
>wrote:
>
>>  *HI Mikund:*
>> **
>> *    You asked*
>>
>>           MPLS-IP encapsulation is valid for MPLS-TP when IP addressing
>> is being used.
>>           (i.e in this case ACH will not be used).  If we follow the
>> procedures defined in BFD-base
>>           drafts or BFD-MPLS, how exactly is it expected to achieve CV
>> (connectivity verification)
>>           when ACH is not used in MPLS-TP? Is it acheived using Source I=
P
>> comparison?
>>
>> *    Yes,.see cc-cv-rdi draft 03 version section 3 *
>>
>> A further artifact of IP encapsulation is that CV mis-connectivity defec=
t
>> detection can be performed by inferring MEP_ID on the basis of the
>> combination of the source IP address and "my discriminator" fields.
>>
>> **
>>
>> 2.
>> Is the usage of ACH TLV=92s allowed when MPLS-ACH-IP encapsulation is us=
ed
>> in MPLS-TP?
>> Question arises from the fact that to do CV in MPLS-TP, MEP identificati=
on
>> (carrying MEP TLV)
>> is required and thus ACH needs to be included even if IP addressing is
>> available.
>> Else there should be a mechanism to do CV with IP (Ref: Question 1)
>> **
>> *The CC-CV-RDI draft deprecated the use of the ACH TLV in favor of a
>> trailing TLV for MEP ID, and we do not mandate the use of the trailing T=
LV
>> when MPLS-ACH-IP encapsulation would be used (different code points).*
>> **
>> *I hope this helps*
>> *Dave *
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>

--20cf30025e78e971ca049c7aedbe
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div>Hi Dave</div>
<div>=A0</div>
<div>Thanks for your response..</div>
<div>=A0</div>
<div>Just want to touch upon further on this: &quot;knowledge of the IP add=
ress of the source of the BFD packets&quot;.</div>
<div>=A0</div>
<div>We could ideally have the knowledge of source IP from the source IP ad=
dress of the established path over which BFD runs. But then should BFD (dat=
a plane)=A0actually depend on the source IP address of a control plane esta=
blished path, to do CV? </div>

<div>=A0</div>
<div>For instance, a tunnel (four tuple - Tunnel id, instance, ingress and =
egress id) could have the ingress id as the router id. </div>
<div>=A0</div>
<div>BFD control packets on the other hand could have the source IP as the =
interface IP address. </div>
<div>=A0</div>
<div>How do we actually achieve CV in such a case ?</div>
<div>=A0</div>
<div>OR is it expected (by say a configuration mechanism) that each peer kn=
ows the source IP of BFD packets for every session?</div>
<div>=A0</div>
<div>With Regards</div>
<div>Mukund<br><br></div>
<div class=3D"gmail_quote">On Thu, Feb 10, 2011 at 9:06 PM, David Allan I <=
span dir=3D"ltr">&lt;<a href=3D"mailto:david.i.allan@ericsson.com">david.i.=
allan@ericsson.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div dir=3D"ltr" align=3D"left"><span><font face=3D"Arial" color=3D"#0000ff=
" size=3D"2">Hi Mikund:</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font face=3D"Arial" color=3D"#0000ff=
" size=3D"2"></font></span>=A0</div>
<div dir=3D"ltr" align=3D"left"><span><font face=3D"Arial" color=3D"#0000ff=
" size=3D"2">If I understand your question correctly, you would need knowle=
dge of the IP address of the source of the BFD packets. </font></span></div=
>
<div dir=3D"ltr" align=3D"left"><span><font face=3D"Arial" color=3D"#0000ff=
" size=3D"2"></font></span>=A0</div>
<div dir=3D"ltr" align=3D"left"><span><font face=3D"Arial" color=3D"#0000ff=
" size=3D"2">cheers</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font face=3D"Arial" color=3D"#0000ff=
" size=3D"2">Dave</font></span></div><br>
<div lang=3D"en-us" dir=3D"ltr" align=3D"left">
<hr>
<font face=3D"Tahoma" size=3D"2"><b>From:</b> Mukund Mani [mailto:<a href=
=3D"mailto:mukund.mani@gmail.com" target=3D"_blank">mukund.mani@gmail.com</=
a>] <br><b>Sent:</b> Thursday, February 10, 2011 5:10 AM<br><b>To:</b> Davi=
d Allan I<br>
<b>Cc:</b> <a href=3D"mailto:rtg-bfd@ietf.org" target=3D"_blank">rtg-bfd@ie=
tf.org</a>; <a href=3D"mailto:mpls-tp@ietf.org" target=3D"_blank">mpls-tp@i=
etf.org</a><br><b>Subject:</b> Re: [mpls-tp] MPLS-ACH-IP and MPLS-IP encaps=
ulations for BFD in MPLS-TP<br>
</font><br></div>
<div>
<div></div>
<div class=3D"h5">
<div></div>
<div>Hi Dave</div>
<div>=A0</div>
<div>Not really clear on the first one.. Here we are not including trailing=
 MEP TLV.=A0How do we do=A0CV for the first BFD packet with MPLS-IP encap ?=
 </div>
<div>=A0</div>
<div>With Regards</div>
<div>Mukund<br></div>
<div class=3D"gmail_quote">On Wed, Feb 9, 2011 at 1:25 PM, David Allan I <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:david.i.allan@ericsson.com" target=3D=
"_blank">david.i.allan@ericsson.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div dir=3D"ltr" align=3D"left"><span><font face=3D"Arial" color=3D"#0000ff=
" size=3D"2"><strong>HI Mikund:</strong></font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font face=3D"Arial" color=3D"#0000ff=
" size=3D"2"><strong></strong></font></span>=A0</div>
<div><span style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><span=
><strong>=A0=A0=A0 You asked</strong></span></span></div>
<div>
<div><span style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><span=
><font face=3D"Times New Roman" color=3D"#000000" size=3D"3">=A0=A0=A0 </fo=
nt></span></span></div>
<div><span style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><span=
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0</span>MPLS-IP encapsulation is valid for MP=
LS-TP when IP addressing is being used. </span></div>
<div><span style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><span=
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0</span>(i.e in this case ACH will not be use=
d).=A0=A0</span><span style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: A=
rial">If we follow the procedures defined in BFD-base </span></div>

<div><span style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><span=
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0</span>drafts or BFD-MPLS, how exactly is it=
 expected to achieve CV (connectivity verification) </span></div>
<div><span style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><span=
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0</span>when ACH is not used in MPLS-TP? Is i=
t acheived using Source IP comparison?<span>=A0</span></span></div>
<div><span style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><span=
></span></span>=A0</div></div>
<div><span style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><span=
><strong>=A0=A0=A0 Yes,.see cc-cv-rdi draft 03 version section 3=A0</strong=
></span></span></div>
<div><span style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><span=
>
<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 12pt 21.6pt"><font size=3D"=
3"><font color=3D"#000000"><font face=3D"Courier New"><span lang=3D"EN">A f=
urther artifact of IP encapsulation is that CV mis-connectivity defect dete=
ction can be performed by inferring MEP_ID on the basis of the combination =
of the source IP address and </span>&quot;<span lang=3D"EN">my discriminato=
r</span>&quot; fields.<span lang=3D"EN"></span></font></font></font></p>
</span></span></div>
<div><pre style=3D"MARGIN-LEFT: 0.25in"><b><font face=3D"Courier New" size=
=3D"2"><span lang=3D"EN" style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt"></spa=
n></font></b></pre>
<div style=3D"MARGIN-LEFT: 0.5in"><font color=3D"blue" size=3D"2"><span lan=
g=3D"EN" style=3D"FONT-SIZE: 10pt; COLOR: blue">2. </span></font></div>
<div style=3D"MARGIN-LEFT: 0.5in"><font color=3D"blue" size=3D"2"><span lan=
g=3D"EN" style=3D"FONT-SIZE: 10pt; COLOR: blue">Is the usage of ACH TLV=92s=
 allowed when MPLS-ACH-IP encapsulation is used in MPLS-TP? </span></font><=
/div>
<div style=3D"MARGIN-LEFT: 0.5in"><font color=3D"blue" size=3D"2"><span lan=
g=3D"EN" style=3D"FONT-SIZE: 10pt; COLOR: blue">Question arises from the fa=
ct that to do CV in MPLS-TP, MEP identification (carrying MEP TLV) </span><=
/font></div>

<div style=3D"MARGIN-LEFT: 0.5in"><font color=3D"blue" size=3D"2"><span lan=
g=3D"EN" style=3D"FONT-SIZE: 10pt; COLOR: blue">is required and thus ACH ne=
eds to be included even if IP addressing is available. </span></font></div>
<div style=3D"MARGIN-LEFT: 0.5in"><span lang=3D"EN" style=3D"FONT-SIZE: 10p=
t; COLOR: blue">Else there should be a mechanism to do CV with IP (Ref: Que=
stion 1)<span><font face=3D"Arial">=A0</font></span></span></div>
<div style=3D"MARGIN-LEFT: 0.5in"><span lang=3D"EN" style=3D"FONT-SIZE: 10p=
t; COLOR: blue"><span><font face=3D"Arial"><strong></strong></font></span><=
/span>=A0</div></div>
<div style=3D"MARGIN-LEFT: 0.5in"><span lang=3D"EN" style=3D"FONT-SIZE: 10p=
t; COLOR: blue"><span><font face=3D"Arial"><strong>The CC-CV-RDI draft depr=
ecated the use of the ACH TLV in favor of a trailing TLV for MEP ID, and we=
 do not mandate the use of the trailing TLV when MPLS-ACH-IP encapsulation=
=A0would be used (different code points).</strong></font></span></span></di=
v>

<div style=3D"MARGIN-LEFT: 0.5in"><span lang=3D"EN" style=3D"FONT-SIZE: 10p=
t; COLOR: blue"><span><strong></strong></span></span>=A0</div>
<div style=3D"MARGIN-LEFT: 0.5in"><span lang=3D"EN" style=3D"FONT-SIZE: 10p=
t; COLOR: blue"><span><font face=3D"Arial"><strong>I hope this helps</stron=
g></font></span></span></div>
<div style=3D"MARGIN-LEFT: 0.5in"><strong><span lang=3D"EN" style=3D"FONT-S=
IZE: 10pt; COLOR: blue"><span><font face=3D"Arial">Dave</font>=A0</span></s=
pan><span style=3D"COLOR: blue"></span></strong></div>
<div><font face=3D"Arial" color=3D"#0000ff" size=3D"2"></font>=A0</div>
<div><font face=3D"Arial" color=3D"#0000ff" size=3D"2"></font>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div></div></blockquote></div><br></div></div></div></blockquote><=
/div><br>

--20cf30025e78e971ca049c7aedbe--

From matthew.bocci@alcatel-lucent.com  Thu Feb 17 06:47:38 2011
Return-Path: <matthew.bocci@alcatel-lucent.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B303E3A6E58; Thu, 17 Feb 2011 06:47:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.582
X-Spam-Level: 
X-Spam-Status: No, score=-105.582 tagged_above=-999 required=5 tests=[AWL=0.666, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 eMt2TdPGGAGN; Thu, 17 Feb 2011 06:47:37 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by core3.amsl.com (Postfix) with ESMTP id 2C8633A6E49; Thu, 17 Feb 2011 06:47:36 -0800 (PST)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p1HEkPQC010389 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 17 Feb 2011 15:46:49 +0100
Received: from FRMRSSXCHMBSA3.dc-m.alcatel-lucent.com ([135.120.45.38]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Thu, 17 Feb 2011 15:46:29 +0100
From: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>
To: "greg.jones@itu.int" <greg.jones@itu.int>
Date: Thu, 17 Feb 2011 15:46:26 +0100
Thread-Topic: IETF PWE3 Working Group Last Call on draft-ietf-pwe3-mpls-tp-gal-in-pw-00 
Thread-Index: AcvOsXXjHjesPGdNSf2nivDjEEvehQ==
Message-ID: <C982E542.995E%matthew.bocci@alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.0.101115
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C982E542995Ematthewboccialcatellucentcom_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Cc: "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "ahmpls-tp@lists.itu.int" <ahmpls-tp@lists.itu.int>, "yoichi.maeda@ttc.or.jp" <yoichi.maeda@ttc.or.jp>, "Lam, Hing-Kam \(Kam\)" <kam.lam@alcatel-lucent.com>, "pwe3@ietf.org" <pwe3@ietf.org>, "adrian.farrel@huawei.com" <adrian.farrel@huawei.com>, "tsbsg15@itu.int" <tsbsg15@itu.int>, "hhelvoort@huawei.com" <hhelvoort@huawei.com>, "Andrew. Malis" <andrew.g.malis@verizon.com>, "ghani.abbas@ericsson.com" <ghani.abbas@ericsson.com>
Subject: [mpls-tp] IETF PWE3 Working Group Last Call on draft-ietf-pwe3-mpls-tp-gal-in-pw-00
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Feb 2011 14:47:38 -0000

--_000_C982E542995Ematthewboccialcatellucentcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Title: IETF PWE3 Working Group Last Call on draft-ietf-pwe3-mpls-tp-gal-in-=
pw-00

Submission Date:    2011-02-17

From:    IETF PWE3 WG (Matthew Bocci)
To:     SG15, Q9, Q10, Q12 and Q14 (greg.jones@itu.int<mailto:greg.jones@it=
u.int>)
Cc:    yoichi.maeda@ttc.or.jp<mailto:yoichi.maeda@ttc.or.jp>
greg.jones@itu.int<mailto:greg.jones@itu.int>
ghani.abbas@ericsson.com<mailto:ghani.abbas@ericsson.com>
hhelvoort@huawei.com<mailto:hhelvoort@huawei.com>
malcolm.betts@zte.com.cn<mailto:malcolm.betts@zte.com.cn>
kam.lam@alcatel-lucent.com<mailto:kam.lam@alcatel-lucent.com>
tsbsg15@itu.int<mailto:tsbsg15@itu.int>
ahmpls-tp@lists.itu.int<mailto:ahmpls-tp@lists.itu.int>
adrian.farrel@huawei.com<mailto:adrian.farrel@huawei.com>
stbryant@cisco.com<mailto:stbryant@cisco.com>
pwe3@ietf.org<mailto:pwe3@ietf.org>
mpls-tp@ietf.org<mailto:mpls-tp@ietf.org>
mpls@ietf.org
Response Contact:    matthew.bocci@alcatel-lucent.com<mailto:matthew.bocci@=
alcatel-lucent.com>
andrew.g.malis@verizon.com<mailto:andrew.malis@verizon.com>
Technical Contact:    andrew.malis@verizon.com<mailto:andrew.malis@verizon.=
com>
Purpose:    For action
Deadline:    2011-03-11 Action Needed
Attachments:     (none)
Body:


The PWE3 working group would like to inform you that we have started a work=
ing group last call on "Using the Generic Associated Channel Label for Pseu=
dowire in MPLS-TP" (draft-ietf-pwe3-mpls-tp-gal-in-pw-00).

This is a very short draft but since there are other MPLS-TP-related last c=
alls going on concurrently, this will be a three-week last call.

Since we intend to work the comments received through this working  group l=
ast call into the documents that will be discussed at the IETF meeting in P=
rague, we would like to receive comments from the ITU-T by March 11, 2011.


Matthew Bocci
Andrew Malis

IETF PWE3 Working Group Chairs

--_000_C982E542995Ematthewboccialcatellucentcom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode:=
 space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-si=
ze: 14px; font-family: Calibri, sans-serif; "><div><span class=3D"Apple-sty=
le-span" style=3D"font-size: 12px; font-family: Consolas, monospace; "><div=
>Title:&nbsp;IETF PWE3 Working Group Last Call on draft-ietf-pwe3-mpls-tp-g=
al-in-pw-00</div><div><br></div><div>Submission Date:&nbsp;&nbsp;&nbsp;&nbs=
p;2011-02-17</div><div><br></div><div>From:&nbsp;&nbsp;&nbsp;&nbsp;IETF PWE=
3 WG (Matthew Bocci)</div><div>To:&nbsp;&nbsp;&nbsp;&nbsp; SG15, Q9, Q10, Q=
12 and Q14 (<a href=3D"mailto:greg.jones@itu.int">greg.jones@itu.int</a>)</=
div><div>Cc:&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"mailto:yoichi.maeda@ttc.or.j=
p">yoichi.maeda@ttc.or.jp</a></div><div><a href=3D"mailto:greg.jones@itu.in=
t">greg.jones@itu.int</a></div><div><a href=3D"mailto:ghani.abbas@ericsson.=
com">ghani.abbas@ericsson.com</a></div><div><a href=3D"mailto:hhelvoort@hua=
wei.com">hhelvoort@huawei.com</a></div><div><a href=3D"mailto:malcolm.betts=
@zte.com.cn">malcolm.betts@zte.com.cn</a></div><div><a href=3D"mailto:kam.l=
am@alcatel-lucent.com">kam.lam@alcatel-lucent.com</a></div><div><a href=3D"=
mailto:tsbsg15@itu.int">tsbsg15@itu.int</a></div><div><a href=3D"mailto:ahm=
pls-tp@lists.itu.int">ahmpls-tp@lists.itu.int</a></div><div><a href=3D"mail=
to:adrian.farrel@huawei.com">adrian.farrel@huawei.com</a></div><div><a href=
=3D"mailto:stbryant@cisco.com">stbryant@cisco.com</a></div><div><a href=3D"=
mailto:pwe3@ietf.org">pwe3@ietf.org</a></div><div><a href=3D"mailto:mpls-tp=
@ietf.org">mpls-tp@ietf.org</a></div><div>mpls@ietf.org</div><div>Response =
Contact:&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"mailto:matthew.bocci@alcatel-luc=
ent.com">matthew.bocci@alcatel-lucent.com</a></div><div><a href=3D"mailto:a=
ndrew.malis@verizon.com">andrew.g.malis@verizon.com</a></div><div>Technical=
 Contact:&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"mailto:andrew.malis@verizon.com=
">andrew.malis@verizon.com</a></div><div>Purpose:&nbsp;&nbsp;&nbsp;&nbsp;Fo=
r action</div><div>Deadline:&nbsp;&nbsp;&nbsp;&nbsp;2011-03-11 Action Neede=
d</div><div>Attachments:&nbsp;&nbsp;&nbsp;&nbsp; (none)</div><div>Body:&nbs=
p;&nbsp;&nbsp;&nbsp;</div><div><br></div><div><br></div><div>The PWE3 worki=
ng group would like to inform you that we have started a working group last=
 call on "Using the Generic Associated Channel Label for Pseudowire in MPLS=
-TP" (draft-ietf-pwe3-mpls-tp-gal-in-pw-00).</div><div><br></div><div>This =
is a very short draft but since there are other MPLS-TP-related last calls =
going on concurrently, this will be a three-week last call.</div><div><br><=
/div><div>Since we intend to work the comments received through this workin=
g&nbsp;&nbsp;group last call into the documents that will be discussed at t=
he IETF meeting in Prague, we would like to receive comments from the ITU-T=
 by March 11, 2011.</div><div><br></div><div><br></div><div>Matthew Bocci</=
div><div>Andrew Malis</div><div><br></div><div>IETF PWE3 Working Group Chai=
rs</div></span></div></body></html>

--_000_C982E542995Ematthewboccialcatellucentcom_--

From venkatflex@gmail.com  Thu Feb 17 07:41:55 2011
Return-Path: <venkatflex@gmail.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AE5853A6F2F; Thu, 17 Feb 2011 07:41:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 tmUCO9cLchvs; Thu, 17 Feb 2011 07:41:53 -0800 (PST)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id 4D2573A6DFE; Thu, 17 Feb 2011 07:41:53 -0800 (PST)
Received: by qwi2 with SMTP id 2so2716485qwi.31 for <multiple recipients>; Thu, 17 Feb 2011 07:42:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=IyelI0DjS865cW3cXKFj4Vt8S7MgxcJx915NZy95aCU=; b=fC3Qb902mUBJ7B02RMba4g/LskUtmNWWgwY4iSJEED2i8mRhuXGypgWXXbi5XLGvI3 jdGBFgQ2MZv8NgCUp54CDsU2h8EP2exy6XNsOLguFd9ALBAOGoHVVMsNCmUKd5sPxLFT ixAmQxGuVdjkNWog6MoVvl/t8+SqQNUcpDoT8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=ZcHxJIjB4AvnhNUaMsCLDwHBjIgb41Ef11aDeQfJdoP1JCTTXzHxLbI1dl1dgs/XpC NoKbOcQYNIwJDK/xneTRWjugsv01H+an/ZpKzDbT9IDG3tVN3IPU7lykrCUg5UNw9eHv Ljem30yeC0NPRpvrjXYMSHLnLWkpkqGg89a0s=
MIME-Version: 1.0
Received: by 10.224.37.140 with SMTP id x12mr2709784qad.158.1297957343414; Thu, 17 Feb 2011 07:42:23 -0800 (PST)
Received: by 10.224.20.71 with HTTP; Thu, 17 Feb 2011 07:42:23 -0800 (PST)
Date: Thu, 17 Feb 2011 10:42:23 -0500
Message-ID: <AANLkTinjT6otKgstYmG0EmD6XZRfnQAr+Nu0eY5MWOhZ@mail.gmail.com>
From: venkatesan mahalingam <venkatflex@gmail.com>
To: mpls-tp@ietf.org, mpls <mpls@ietf.org>, david.i.allan@ericsson.com
Content-Type: multipart/alternative; boundary=0015175ce016634902049c7c3ecf
Subject: Re: [mpls-tp] [mpls] mpls wg last callondraft-ietf-mpls-tp-cc-cv-rdi-03
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Feb 2011 15:41:55 -0000

--0015175ce016634902049c7c3ecf
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

W.r.t ITU standard, Mismerge and Unexpected MEP are identified as follows,

If a CCM frame with same MEG Level but with a MEG ID different than the
receiving MEP=E2=80=99s own MEG ID is
received, *Mismerge* is detected.

=E2=80=A2 If a CCM frame with the same MEG Level and a correct MEG ID but w=
ith an
incorrect MEP ID, including
receiving MEP=E2=80=99s own MEP ID, is received, *Unexpected MEP* is detect=
ed.

I think, the authors should clearly differentiate the unexpected MEP and
Mismerge defects in the MPLS-TP OAM?

--=20
BR,
Venkat.

Hi Feng:

I'm not sure how unexpected MEP is not indicative of a mismerge.
Either the source MEP ID has been misconfigured, or you are receiving
a message from a MEP due to LIB corruption or similar defect somewhere
in the network.

As for your second point, it is not that negotiation is not used,
there is simply no give and take allowed, so the procedures are simply
modified slightly in the TP case . If the far end refuses to support
the requested periodicity for whatever reason, you do not progress
beyond the INIT state and presumably send some indication to
management that the session could not come "UP". You have that option
whether you are conformant to CC-CV-RDI draft or simply RFC 5884. So
as far as I can tell interoperability options exist, they were always
there in the protocol, we are simply providing implementation
guidelines for the TP application...

I hope this helps
Dave

----- Original Message -----
From: HUANG Feng F
[mailto:Feng.f.Huang@alcatel-sbell.com.cn<https://inowa.aricent.com/owa/red=
ir.aspx?C=3D85c311909efa463381c5914b036b0942&URL=3Dmailto%3aFeng.f.Huang%40=
alcatel-sbell.com.cn>
]
Sent: Thursday, February 17, 2011 11:57 AM
To: David Allan I <david.i.allan@ericsson.com>; MPLS TP; mpls@ietf.org <
mpls@ietf.org>; ahmpls-tp@lists.itu.int <ahmpls-tp@lists.itu.int>
Subject: Re: [mpls-tp] [mpls] mpls wg last
callondraft-ietf-mpls-tp-cc-cv-rdi-03

Hi,Dave,
     Thanks, LSP MEP ID in draft-ietf-mpls-tp-identifiers-03 is:
Node_ID::Tunnel_Num::LSP_Num,

and for LSP MEG ID: (7.1.2.1.)
    Since a MEG pertains to a single MPLS-TP LSP, IP compatible MEG_IDs
   for MPLS-TP LSPs are simply the corresponding LSP_IDs.  We note that
   while the two identifiers are syntactically identical, they have
   different semantics.  This semantic difference needs to be made
   clear.  For instance if both a MPLS-TP LSP_ID and MPLS-TP LSP MEG_IDs
   are to be encoded in TLVs different types need to be assigned for
   these two identifiers.

you can only detect wrong MEP ID, that's Unexpected MEP, it is not
Mis-merge.


If period negotiation is not used, how to insure interoperability with BFD
used in IP/MPLS asked always by providers?

B.R.
Feng


-----Original Message-----
From: David Allan I
[mailto:david.i.allan@ericsson.com<https://inowa.aricent.com/owa/redir.aspx=
?C=3D85c311909efa463381c5914b036b0942&URL=3Dmailto%3adavid.i.allan%40ericss=
on.com>
]
Sent: 2011=E5=B9=B42=E6=9C=8817=E6=97=A5 0:51
To: HUANG Feng F; mpls-tp@ietf.org; mpls@ietf.org; ahmpls-tp@lists.itu.int
Cc: Loa Andersson
Subject: RE: [mpls] [mpls-tp] mpls wg last
callondraft-ietf-mpls-tp-cc-cv-rdi-03

HI Feng:

See section 7.1 of
http://tools.ietf.org/html/draft-ietf-mpls-tp-identifiers-03<https://inowa.=
aricent.com/owa/redir.aspx?C=3D85c311909efa463381c5914b036b0942&URL=3Dhttp%=
3a%2f%2ftools.ietf.org%2fhtml%2fdraft-ietf-mpls-tp-identifiers-03>
 . IMO it is simply a terminology issue as to whether a MEG is encoded in
the LSP and PW formats or not.

Section 3.5.1 of the CC-CV-BFD draft identifies that period negotiation is
not used. So unexpected period occurs when one end unpexpectedly changes th=
e
period advertised.

I hope this helps
Dave

-----Original Message-----
From: HUANG Feng F
[mailto:Feng.f.Huang@alcatel-sbell.com.cn<https://inowa.aricent.com/owa/red=
ir.aspx?C=3D85c311909efa463381c5914b036b0942&URL=3Dmailto%3aFeng.f.Huang%40=
alcatel-sbell.com.cn>
]
Sent: Wednesday, February 16, 2011 5:43 PM
To: David Allan I; mpls-tp@ietf.org; mpls@ietf.org; ahmpls-tp@lists.itu.int
Cc: Loa Andersson
Subject: RE: [mpls] [mpls-tp] mpls wg last callon
draft-ietf-mpls-tp-cc-cv-rdi-03


 Dear Dave,
     In 3.3. MPLS BFD proactive CV Message format, LSP/PW MEP ID is defined
without MEG, how to detect Mismerge?
     And BFD protocol is enabled for period negotiation, when period is
different, lower one is used, then how to detection Uexpect period?
B.R.
Feng


-----Original Message-----
From: mpls-bounces@ietf.org
[mailto:mpls-bounces@ietf.org<https://inowa.aricent.com/owa/redir.aspx?C=3D=
85c311909efa463381c5914b036b0942&URL=3Dmailto%3ampls-bounces%40ietf.org>]
On Behalf Of David Allan I
Sent: 2011=E5=B9=B42=E6=9C=8811=E6=97=A5 18:12
To: Mach Chen; 'Loa Andersson'; mpls-tp@ietf.org; mpls@ietf.org;
ahmpls-tp@lists.itu.int
Subject: Re: [mpls] [mpls-tp] mpls wg last callon
draft-ietf-mpls-tp-cc-cv-rdi-03

OK, will do...

Dave

-----Original Message-----
From: Mach Chen
[mailto:mach@huawei.com<https://inowa.aricent.com/owa/redir.aspx?C=3D85c311=
909efa463381c5914b036b0942&URL=3Dmailto%3amach%40huawei.com>
]
Sent: Friday, February 11, 2011 12:12 AM
To: David Allan I; 'Loa Andersson'; mpls-tp@ietf.org; mpls@ietf.org;
ahmpls-tp@lists.itu.int
Subject: RE: [mpls] [mpls-tp] mpls wg last call on
draft-ietf-mpls-tp-cc-cv-rdi-03

Hi Dave,

Thanks for your prompt response!

> >3 Section 3.5.2
> >" 4. Receipt of an expected session discriminator with an unexpected
label
> (mis-connectivity defect).", For a receiver, how does it know that the
> session >discriminator is valid but the label is invalid? IMHO, this
defect is just
> another description of defect 3 . Suggest to remove it.
>
> If the session discriminator exists in the BFD database, it is
superficially a valid
> descriminator but the label of arrival can be incorrect. This may
> indicate
an
> implementation problem at the source MEP. What we were referring to in '3=
'
> was a session discriminator that did not exist in the local database,
> BFD
had
> never handed it out hence it could not be found.
>

OK, but more clarification text would be helpful.

Best regards,
Mach

--0015175ce016634902049c7c3ecf
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div>Hi,</div><div><br></div><div>W.r.t ITU standard, Mismerge and Unexpect=
ed MEP are identified as follows,</div><div><br></div><div>If a CCM frame w=
ith same MEG Level but with a MEG ID different than the receiving MEP=E2=80=
=99s own MEG ID is=C2=A0</div>
<div>received, <b>Mismerge</b> is detected.</div><div><br></div><div>=E2=80=
=A2 If a CCM frame with the same MEG Level and a correct MEG ID but with an=
 incorrect MEP ID, including=C2=A0</div><div>receiving MEP=E2=80=99s own ME=
P ID, is received, <b>Unexpected MEP</b> is detected.</div>
<div><br></div>I think, the authors should clearly=C2=A0differentiate=C2=A0=
the unexpected MEP and Mismerge defects in the MPLS-TP OAM?<br><br><div>-- =
<br>BR,<br>Venkat.<br>
<div><br></div><div><span class=3D"Apple-style-span" style=3D"font-family: =
&#39;Times New Roman&#39;; font-size: medium; "><pre style=3D"white-space: =
pre-wrap; word-wrap: break-word; width: 1266px; ">Hi Feng:

I&#39;m not sure how unexpected MEP is not indicative of a mismerge. Either=
 the source MEP ID has been misconfigured, or you are receiving a message f=
rom a MEP due to LIB corruption or similar defect somewhere in the network.=
=20

As for your second point, it is not that negotiation is not used, there is =
simply no give and take allowed, so the procedures are simply modified slig=
htly in the TP case . If the far end refuses to support the requested perio=
dicity for whatever reason, you do not progress beyond the INIT state and p=
resumably send some indication to management that the session could not com=
e &quot;UP&quot;. You have that option whether you are conformant to CC-CV-=
RDI draft or simply RFC 5884. So as far as I can tell interoperability opti=
ons exist, they were always there in the protocol, we are simply providing =
implementation guidelines for the TP application...

I hope this helps
Dave
</pre><div><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18=
030, SimSun, monospace; font-size: 14px; ">----- Original Message -----</sp=
an></div></span></div><div><span class=3D"Apple-style-span" style=3D"font-f=
amily: SimSun-18030, SimSun, monospace; font-size: 14px; ">From: HUANG Feng=
 F [</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18=
030, SimSun, monospace; font-size: 14px; "><a href=3D"https://inowa.aricent=
.com/owa/redir.aspx?C=3D85c311909efa463381c5914b036b0942&amp;URL=3Dmailto%3=
aFeng.f.Huang%40alcatel-sbell.com.cn">mailto:Feng.f.Huang@alcatel-sbell.com=
.cn</a></span><span class=3D"Apple-style-span" style=3D"font-family: SimSun=
-18030, SimSun, monospace; font-size: 14px; ">]</span><span class=3D"Apple-=
style-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-siz=
e: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">Sent: Thursday, February 17, 2011 11=
:57 AM</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-=
18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">To: David Allan I &lt;<a href=3D"mai=
lto:david.i.allan@ericsson.com">david.i.allan@ericsson.com</a>&gt;; MPLS TP=
; <a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a> &lt;<a href=3D"mailto:=
mpls@ietf.org">mpls@ietf.org</a>&gt;; <a href=3D"mailto:ahmpls-tp@lists.itu=
.int">ahmpls-tp@lists.itu.int</a> &lt;<a href=3D"mailto:ahmpls-tp@lists.itu=
.int">ahmpls-tp@lists.itu.int</a>&gt;</span><span class=3D"Apple-style-span=
" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 14px; "=
><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">Subject: Re: [mpls-tp] [mpls] mpls w=
g last=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 callondraft-ietf-mpls-tp-cc-cv-rdi-03<=
/span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030, =
SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; "><br></span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; ">Hi,Dave,</span><span class=3D"Apple-style-span" style=3D"font-family=
: SimSun-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">=C2=A0=C2=A0=C2=A0=C2=A0 Thanks, LSP=
 MEP ID in draft-ietf-mpls-tp-identifiers-03 is: Node_ID::Tunnel_Num::LSP_N=
um,=C2=A0</span><span class=3D"Apple-style-span" style=3D"font-family: SimS=
un-18030, SimSun, monospace; font-size: 14px; ">=C2=A0</span><span class=3D=
"Apple-style-span" style=3D"font-family: SimSun-18030, SimSun, monospace; f=
ont-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; "><br></span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; ">and for LSP MEG ID: (7.1.2.1.)</span><span class=3D"Apple-style-span=
" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 14px; "=
><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">=C2=A0=C2=A0=C2=A0 Since a MEG perta=
ins to a single MPLS-TP LSP, IP compatible MEG_IDs</span><span class=3D"App=
le-style-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-=
size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">=C2=A0=C2=A0 for MPLS-TP LSPs are si=
mply the corresponding LSP_IDs.=C2=A0 We note that</span><span class=3D"App=
le-style-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-=
size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">=C2=A0=C2=A0 while the two identifie=
rs are syntactically identical, they have</span><span class=3D"Apple-style-=
span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 14p=
x; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">=C2=A0=C2=A0 different semantics.=C2=
=A0 This semantic difference needs to be made</span><span class=3D"Apple-st=
yle-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size:=
 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">=C2=A0=C2=A0 clear.=C2=A0 For instan=
ce if both a MPLS-TP LSP_ID and MPLS-TP LSP MEG_IDs</span><span class=3D"Ap=
ple-style-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font=
-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">=C2=A0=C2=A0 are to be encoded in TL=
Vs different types need to be assigned for</span><span class=3D"Apple-style=
-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 14=
px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">=C2=A0=C2=A0 these two identifiers.<=
/span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030, =
SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">=C2=A0</span><span class=3D"Apple-st=
yle-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size:=
 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">you can only detect wrong MEP ID, th=
at&#39;s Unexpected MEP, it is not Mis-merge.</span><span class=3D"Apple-st=
yle-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size:=
 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; "><br></span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; ">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0</span><span class=3D"Apple-style-span=
" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 14px; "=
>=C2=A0</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun=
-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">If period negotiation is not used, h=
ow to insure interoperability with BFD used in IP/MPLS asked always by prov=
iders?</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-=
18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; "><br></span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; ">B.R.</span><span class=3D"Apple-style-span" style=3D"font-family: Si=
mSun-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">Feng</span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">=C2=A0</span><span class=3D"Apple-st=
yle-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size:=
 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; "><br></span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; ">-----Original Message-----</span><span class=3D"Apple-style-span" st=
yle=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 14px; "><br=
>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">From: David Allan I [</span><span cl=
ass=3D"Apple-style-span" style=3D"font-family: SimSun-18030, SimSun, monosp=
ace; font-size: 14px; "><a href=3D"https://inowa.aricent.com/owa/redir.aspx=
?C=3D85c311909efa463381c5914b036b0942&amp;URL=3Dmailto%3adavid.i.allan%40er=
icsson.com">mailto:david.i.allan@ericsson.com</a></span><span class=3D"Appl=
e-style-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-s=
ize: 14px; ">]</span><span class=3D"Apple-style-span" style=3D"font-family:=
 SimSun-18030, SimSun, monospace; font-size: 14px; ">=C2=A0</span><span cla=
ss=3D"Apple-style-span" style=3D"font-family: SimSun-18030, SimSun, monospa=
ce; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">Sent: 2011=E5=B9=B42=E6=9C=8817=E6=
=97=A5 0:51</span><span class=3D"Apple-style-span" style=3D"font-family: Si=
mSun-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">To: HUANG Feng F; <a href=3D"mailto:=
mpls-tp@ietf.org">mpls-tp@ietf.org</a>; <a href=3D"mailto:mpls@ietf.org">mp=
ls@ietf.org</a>; <a href=3D"mailto:ahmpls-tp@lists.itu.int">ahmpls-tp@lists=
.itu.int</a></span><span class=3D"Apple-style-span" style=3D"font-family: S=
imSun-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">Cc: Loa Andersson</span><span class=
=3D"Apple-style-span" style=3D"font-family: SimSun-18030, SimSun, monospace=
; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">Subject: RE: [mpls] [mpls-tp] mpls w=
g last callondraft-ietf-mpls-tp-cc-cv-rdi-03</span><span class=3D"Apple-sty=
le-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: =
14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; "><br></span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; ">HI Feng:</span><span class=3D"Apple-style-span" style=3D"font-family=
: SimSun-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; "><br></span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; ">See section 7.1 of</span><span class=3D"Apple-style-span" style=3D"f=
ont-family: SimSun-18030, SimSun, monospace; font-size: 14px; ">=C2=A0</spa=
n><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030, SimS=
un, monospace; font-size: 14px; "><a href=3D"https://inowa.aricent.com/owa/=
redir.aspx?C=3D85c311909efa463381c5914b036b0942&amp;URL=3Dhttp%3a%2f%2ftool=
s.ietf.org%2fhtml%2fdraft-ietf-mpls-tp-identifiers-03" target=3D"_blank">ht=
tp://tools.ietf.org/html/draft-ietf-mpls-tp-identifiers-03</a></span><span =
class=3D"Apple-style-span" style=3D"font-family: SimSun-18030, SimSun, mono=
space; font-size: 14px; ">=C2=A0</span><span class=3D"Apple-style-span" sty=
le=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 14px; ">. IM=
O it is simply a terminology issue as to whether a MEG is encoded in the LS=
P and PW formats or not.</span><span class=3D"Apple-style-span" style=3D"fo=
nt-family: SimSun-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; "><br></span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; ">Section 3.5.1 of the CC-CV-BFD draft identifies that period negotiat=
ion is not used. So unexpected period occurs when one end unpexpectedly cha=
nges the period advertised.</span><span class=3D"Apple-style-span" style=3D=
"font-family: SimSun-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; "><br></span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; ">I hope this helps</span><span class=3D"Apple-style-span" style=3D"fo=
nt-family: SimSun-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">Dave</span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; ">=C2=A0</span><span class=3D"Apple-style-span" style=3D"font-family: =
SimSun-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; "><br></span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; ">-----Original Message-----</span><span class=3D"Apple-style-span" st=
yle=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 14px; "><br=
>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">From: HUANG Feng F [</span><span cla=
ss=3D"Apple-style-span" style=3D"font-family: SimSun-18030, SimSun, monospa=
ce; font-size: 14px; "><a href=3D"https://inowa.aricent.com/owa/redir.aspx?=
C=3D85c311909efa463381c5914b036b0942&amp;URL=3Dmailto%3aFeng.f.Huang%40alca=
tel-sbell.com.cn">mailto:Feng.f.Huang@alcatel-sbell.com.cn</a></span><span =
class=3D"Apple-style-span" style=3D"font-family: SimSun-18030, SimSun, mono=
space; font-size: 14px; ">]</span><span class=3D"Apple-style-span" style=3D=
"font-family: SimSun-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">Sent: Wednesday, February 16, 2011 5=
:43 PM</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-=
18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">To: David Allan I; <a href=3D"mailto=
:mpls-tp@ietf.org">mpls-tp@ietf.org</a>; <a href=3D"mailto:mpls@ietf.org">m=
pls@ietf.org</a>; <a href=3D"mailto:ahmpls-tp@lists.itu.int">ahmpls-tp@list=
s.itu.int</a></span><span class=3D"Apple-style-span" style=3D"font-family: =
SimSun-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">Cc: Loa Andersson</span><span class=
=3D"Apple-style-span" style=3D"font-family: SimSun-18030, SimSun, monospace=
; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">Subject: RE: [mpls] [mpls-tp] mpls w=
g last callon draft-ietf-mpls-tp-cc-cv-rdi-03</span><span class=3D"Apple-st=
yle-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size:=
 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; "><br></span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">=C2=A0Dear Dave,</span><span class=
=3D"Apple-style-span" style=3D"font-family: SimSun-18030, SimSun, monospace=
; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">=C2=A0=C2=A0=C2=A0=C2=A0 In 3.3. MPL=
S BFD proactive CV Message format, LSP/PW MEP ID is defined without MEG, ho=
w to detect Mismerge?</span><span class=3D"Apple-style-span" style=3D"font-=
family: SimSun-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">=C2=A0=C2=A0=C2=A0=C2=A0 And BFD pro=
tocol is enabled for period negotiation, when period is different, lower on=
e is used, then how to detection Uexpect period?</span><span class=3D"Apple=
-style-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-si=
ze: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">B.R.</span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">Feng</span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; "><br></span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">-----Original Message-----</span><sp=
an class=3D"Apple-style-span" style=3D"font-family: SimSun-18030, SimSun, m=
onospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">From: <a href=3D"mailto:mpls-bounces=
@ietf.org">mpls-bounces@ietf.org</a> [</span><span class=3D"Apple-style-spa=
n" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 14px; =
"><a href=3D"https://inowa.aricent.com/owa/redir.aspx?C=3D85c311909efa46338=
1c5914b036b0942&amp;URL=3Dmailto%3ampls-bounces%40ietf.org">mailto:mpls-bou=
nces@ietf.org</a></span><span class=3D"Apple-style-span" style=3D"font-fami=
ly: SimSun-18030, SimSun, monospace; font-size: 14px; ">] On Behalf Of Davi=
d Allan I</span><span class=3D"Apple-style-span" style=3D"font-family: SimS=
un-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">Sent: 2011=E5=B9=B42=E6=9C=8811=E6=
=97=A5 18:12</span><span class=3D"Apple-style-span" style=3D"font-family: S=
imSun-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">To: Mach Chen; &#39;Loa Andersson&#3=
9;; <a href=3D"mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</a>; <a href=3D"ma=
ilto:mpls@ietf.org">mpls@ietf.org</a>; <a href=3D"mailto:ahmpls-tp@lists.it=
u.int">ahmpls-tp@lists.itu.int</a></span><span class=3D"Apple-style-span" s=
tyle=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 14px; "><b=
r>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">Subject: Re: [mpls] [mpls-tp] mpls w=
g last callon draft-ietf-mpls-tp-cc-cv-rdi-03</span><span class=3D"Apple-st=
yle-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size:=
 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; "><br></span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; ">OK, will do...</span><span class=3D"Apple-style-span" style=3D"font-=
family: SimSun-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; "><br></span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; ">Dave</span><span class=3D"Apple-style-span" style=3D"font-family: Si=
mSun-18030, SimSun, monospace; font-size: 14px; ">=C2=A0</span><span class=
=3D"Apple-style-span" style=3D"font-family: SimSun-18030, SimSun, monospace=
; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; "><br></span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; ">-----Original Message-----</span><span class=3D"Apple-style-span" st=
yle=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 14px; "><br=
>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">From: Mach Chen [</span><span class=
=3D"Apple-style-span" style=3D"font-family: SimSun-18030, SimSun, monospace=
; font-size: 14px; "><a href=3D"https://inowa.aricent.com/owa/redir.aspx?C=
=3D85c311909efa463381c5914b036b0942&amp;URL=3Dmailto%3amach%40huawei.com">m=
ailto:mach@huawei.com</a></span><span class=3D"Apple-style-span" style=3D"f=
ont-family: SimSun-18030, SimSun, monospace; font-size: 14px; ">]</span><sp=
an class=3D"Apple-style-span" style=3D"font-family: SimSun-18030, SimSun, m=
onospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">Sent: Friday, February 11, 2011 12:1=
2 AM</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18=
030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">To: David Allan I; &#39;Loa Andersso=
n&#39;; <a href=3D"mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</a>; <a href=
=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>; <a href=3D"mailto:ahmpls-tp@li=
sts.itu.int">ahmpls-tp@lists.itu.int</a></span><span class=3D"Apple-style-s=
pan" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 14px=
; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">Subject: RE: [mpls] [mpls-tp] mpls w=
g last call on draft-ietf-mpls-tp-cc-cv-rdi-03</span><span class=3D"Apple-s=
tyle-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size=
: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; "><br></span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; ">Hi Dave,</span><span class=3D"Apple-style-span" style=3D"font-family=
: SimSun-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; "><br></span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; ">Thanks for your prompt response!</span><span class=3D"Apple-style-sp=
an" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 14px;=
 "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; "><br></span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; ">&gt; &gt;3 Section 3.5.2</span><span class=3D"Apple-style-span" styl=
e=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">&gt; &gt;&quot; 4. Receipt of an exp=
ected session discriminator with an unexpected</span><span class=3D"Apple-s=
tyle-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size=
: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">label</span><span class=3D"Apple-sty=
le-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: =
14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">&gt; (mis-connectivity defect).&quot=
;, For a receiver, how does it know that the</span><span class=3D"Apple-sty=
le-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: =
14px; ">=C2=A0</span><span class=3D"Apple-style-span" style=3D"font-family:=
 SimSun-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">&gt; session &gt;discriminator is va=
lid but the label is invalid? IMHO, this</span><span class=3D"Apple-style-s=
pan" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 14px=
; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">defect is just</span><span class=3D"=
Apple-style-span" style=3D"font-family: SimSun-18030, SimSun, monospace; fo=
nt-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">&gt; another description of defect 3=
 . Suggest to remove it.</span><span class=3D"Apple-style-span" style=3D"fo=
nt-family: SimSun-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">&gt;</span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; ">=C2=A0</span><span class=3D"Apple-style-span" style=3D"font-family: =
SimSun-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">&gt; If the session discriminator ex=
ists in the BFD database, it is</span><span class=3D"Apple-style-span" styl=
e=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">superficially a valid</span><span cl=
ass=3D"Apple-style-span" style=3D"font-family: SimSun-18030, SimSun, monosp=
ace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">&gt; descriminator but the label of =
arrival can be incorrect. This may</span><span class=3D"Apple-style-span" s=
tyle=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 14px; ">=
=C2=A0</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-=
18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">&gt; indicate</span><span class=3D"A=
pple-style-span" style=3D"font-family: SimSun-18030, SimSun, monospace; fon=
t-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">an</span><span class=3D"Apple-style-=
span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 14p=
x; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">&gt; implementation problem at the s=
ource MEP. What we were referring to in &#39;3&#39;</span><span class=3D"Ap=
ple-style-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font=
-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">&gt; was a session discriminator tha=
t did not exist in the local database,</span><span class=3D"Apple-style-spa=
n" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 14px; =
">=C2=A0</span><span class=3D"Apple-style-span" style=3D"font-family: SimSu=
n-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">&gt; BFD</span><span class=3D"Apple-=
style-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-siz=
e: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">had</span><span class=3D"Apple-style=
-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 14=
px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">&gt; never handed it out hence it co=
uld not be found.</span><span class=3D"Apple-style-span" style=3D"font-fami=
ly: SimSun-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">&gt;</span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; ">=C2=A0</span><span class=3D"Apple-style-span" style=3D"font-family: =
SimSun-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; "><br></span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; ">OK, but more clarification text would be helpful.</span><span class=
=3D"Apple-style-span" style=3D"font-family: SimSun-18030, SimSun, monospace=
; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; "><br></span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; ">Best regards,</span><span class=3D"Apple-style-span" style=3D"font-f=
amily: SimSun-18030, SimSun, monospace; font-size: 14px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; ">Mach</span><span class=3D"Apple-styl=
e-span" style=3D"font-family: SimSun-18030, SimSun, monospace; font-size: 1=
4px; "><br>
</span><span class=3D"Apple-style-span" style=3D"font-family: SimSun-18030,=
 SimSun, monospace; font-size: 14px; "><br></span></div></div>

--0015175ce016634902049c7c3ecf--

From gregimirsky@gmail.com  Thu Feb 17 22:46:36 2011
Return-Path: <gregimirsky@gmail.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A11863A6D72; Thu, 17 Feb 2011 22:46:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.098
X-Spam-Level: 
X-Spam-Status: No, score=-3.098 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 SvZvAAJlzCXY; Thu, 17 Feb 2011 22:46:34 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 137123A6D6D; Thu, 17 Feb 2011 22:46:32 -0800 (PST)
Received: by vws7 with SMTP id 7so1857315vws.31 for <multiple recipients>; Thu, 17 Feb 2011 22:47:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to:cc :content-type; bh=xYg5vczfCME4GJsR8FblCbXMVCVcfzDurewQ8UrgMaE=; b=xExpT6gzSVSLXwmnCoukrkVsTDHI/sWu6W3TYtXC12AFj3QAUVBw/j2idBOPuHjmly b4gh6VAKhetN/a9aXP7CVaVXNvXy2JU3yJrRHFcQ7PygxRacnDyt/O/+fS6pM2cX7XkS +jEQtm73fjaWyn+cC6W5WqYwsf0RYzgVypVyQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=PpRD0yF7OSDzdI3kcYo9ItTIKzLUxbBqpkq+Q+v2F4iQHo5Bl91HDzBF9XBm8Q9mHd EqP9RKHiA7Fe53hXyAIGKlqJd7L6QC682vu7LXr8kmlbQ6xskmq9sK3iP2e3FvizIONI e/3YcjViVxfdhLmCpqPvwka1P+9M0pvtuxktw=
MIME-Version: 1.0
Received: by 10.52.157.65 with SMTP id wk1mr556497vdb.125.1298011624253; Thu, 17 Feb 2011 22:47:04 -0800 (PST)
Received: by 10.52.165.9 with HTTP; Thu, 17 Feb 2011 22:47:04 -0800 (PST)
Date: Thu, 17 Feb 2011 22:47:04 -0800
Message-ID: <AANLkTikcnCa5DQZyGgD_QawiQ_57KKA4BXQm7iRRayKA@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: Luca Martini <lmartini@cisco.com>
Content-Type: multipart/alternative; boundary=bcaec53f931fc72a77049c88e1ce
Cc: mpls@ietf.org, mpls-tp@ietf.org, lihan@chinamobile.com, pwe3 <pwe3@ietf.org>, HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>
Subject: [mpls-tp] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2011 06:46:36 -0000

--bcaec53f931fc72a77049c88e1ce
Content-Type: text/plain; charset=ISO-8859-1

Dear Authors and All,
prior to the meeting in Bejing and acceptance of this proposal as WG
document Luca and I agreed that use of GAL with PW VCCV presents a problem.
I was not attending the IETF-79, nor I found discussion of this issue in the
minutes. I think that this issue should be specified, explained. In my view,
this document updates not only RFC 5586
but RFC 5085 too.

Regards,
Greg

Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt

On Sat, Oct 30, 2010 at 10:14 AM, Luca Martini <lmartini@cisco.com> wrote:

>  Greg,
>
> You are correct , the proposed update does not propose any changes to VCCV.
> However the problem with vccv is not as simple as to ask for a new code
> point from IANA.
> Given the good amount of discussion on this point, we should probably have
> a discussion in Beijing.
>
> Luca
>
>
>
> On 10/29/2010 05:07 PM, Greg Mirsky wrote:
>
> Dear Authors,
> I think that proposed update of the Section 4.2. RFC 5586 makes it possible
> to use GAL on MPLS-TP PW that uses Control Word. I consider it to be
> conflict between PW VCCV CC types because use of GAL is not negotiated
> through PW VCCV negotiation. To avoid such situation I propose:
>
>    - in Section 5 request IANA to assign new CC Type "MPLS Generic
>    Associated Channel Label"
>    - assign precedence to new CC Type that affects Section 7 RFC 5085
>
> Regards,
> Greg
>
>
>
> _______________________________________________
> mpls mailing listmpls@ietf.orghttps://www.ietf.org/mailman/listinfo/mpls
>
>
>

--bcaec53f931fc72a77049c88e1ce
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear Authors and All,<br>prior to the meeting in Bejing and acceptance of t=
his proposal as WG document Luca and I agreed that use of GAL with PW VCCV =
presents a problem.<br>I was not attending the IETF-79, nor I found discuss=
ion of this issue in the minutes. I think that this issue should be specifi=
ed, explained. In my view, this document updates not only RFC 5586<br>
but RFC 5085 too.<br><br>Regards,<br>Greg<br><br>Comment to draft-lm-pwe3-m=
pls-tp-gal-in-pw-00.txt<br><br><div class=3D"gmail_quote">On Sat, Oct 30, 2=
010 at 10:14 AM, Luca Martini <span dir=3D"ltr">&lt;<a href=3D"mailto:lmart=
ini@cisco.com">lmartini@cisco.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">

 =20
   =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#ffffff">
    Greg,<br>
    <br>
    You are correct , the proposed update does not propose any changes
    to VCCV.<br>
    However the problem with vccv is not as simple as to ask for a new
    code point from IANA.<br>
    Given the good amount of discussion on this point, we should
    probably have a discussion in Beijing.<br>
    <br>
    Luca<div><div></div><div class=3D"h5"><br>
    <br>
    <br>
    On 10/29/2010 05:07 PM, Greg Mirsky wrote:
    </div></div><blockquote type=3D"cite"><div><div></div><div class=3D"h5"=
>
      <pre>Dear Authors,
I think that proposed update of the Section 4.2. RFC 5586 makes it possible
to use GAL on MPLS-TP PW that uses Control Word. I consider it to be
conflict between PW VCCV CC types because use of GAL is not negotiated
through PW VCCV negotiation. To avoid such situation I propose:

   - in Section 5 request IANA to assign new CC Type &quot;MPLS Generic
   Associated Channel Label&quot;
   - assign precedence to new CC Type that affects Section 7 RFC 5085

Regards,
Greg

</pre>
      </div></div><pre><fieldset></fieldset>
_______________________________________________
mpls mailing list
<a href=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls@ietf.org</a>
<a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/mpls</a>
</pre>
    </blockquote>
    <br>
  </div>

</blockquote></div><br>

--bcaec53f931fc72a77049c88e1ce--

From Alexander.Vainshtein@ecitele.com  Thu Feb 17 23:07:36 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A03EB3A68DD; Thu, 17 Feb 2011 23:07:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 GdrWklM+u8kJ; Thu, 17 Feb 2011 23:07:34 -0800 (PST)
Received: from ilptbmg01.ecitele.com (ilptbmg01-out.ecitele.com [147.234.242.234]) by core3.amsl.com (Postfix) with ESMTP id 247803A6A84; Thu, 17 Feb 2011 23:07:32 -0800 (PST)
X-AuditID: 93eaf2e7-b7b9cae000002a0e-67-4d5e1ad78877
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id 58.04.10766.7DA1E5D4; Fri, 18 Feb 2011 09:08:07 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Fri, 18 Feb 2011 09:08:04 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Greg Mirsky <gregimirsky@gmail.com>
Date: Fri, 18 Feb 2011 09:05:19 +0200
Thread-Topic: [mpls-tp] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
Thread-Index: AcvPN6zTJGq/0XxDTGy6v16DWGU3fgAAocFM
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D6FB8BEA8B@ILPTMAIL02.ecitele.com>
References: <AANLkTikcnCa5DQZyGgD_QawiQ_57KKA4BXQm7iRRayKA@mail.gmail.com>
In-Reply-To: <AANLkTikcnCa5DQZyGgD_QawiQ_57KKA4BXQm7iRRayKA@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_A3C5DF08D38B6049839A6F553B331C76D6FB8BEA8BILPTMAIL02eci_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAARci5Uo=
Cc: Robert Rennison <Robert.Rennison@ecitele.com>, "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, Mishael Wexler <Mishael.Wexler@ecitele.com>, "lihan@chinamobile.com" <lihan@chinamobile.com>, pwe3 <pwe3@ietf.org>, Rotem, HUANG, Feng F <Feng.f.Huang@alcatel-sbell.com.cn>, Cohen <Rotem.Cohen@ecitele.com>
Subject: Re: [mpls-tp] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2011 07:07:37 -0000

--_000_A3C5DF08D38B6049839A6F553B331C76D6FB8BEA8BILPTMAIL02eci_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Greg, and all,
I concur with Greg.
Using GAL with PWs is highly problematic, and all the related issues (raise=
d during the poll on accepting this draft as a WG item) have not, AFAIK, be=
en resolved.

Regards,
     Sasha

________________________________
From: mpls-tp-bounces@ietf.org [mpls-tp-bounces@ietf.org] On Behalf Of Greg=
 Mirsky [gregimirsky@gmail.com]
Sent: Friday, February 18, 2011 8:47 AM
To: Luca Martini
Cc: mpls@ietf.org; mpls-tp@ietf.org; lihan@chinamobile.com; pwe3; HUANG Fen=
g F
Subject: [mpls-tp] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt

Dear Authors and All,
prior to the meeting in Bejing and acceptance of this proposal as WG docume=
nt Luca and I agreed that use of GAL with PW VCCV presents a problem.
I was not attending the IETF-79, nor I found discussion of this issue in th=
e minutes. I think that this issue should be specified, explained. In my vi=
ew, this document updates not only RFC 5586
but RFC 5085 too.

Regards,
Greg

Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt

On Sat, Oct 30, 2010 at 10:14 AM, Luca Martini <lmartini@cisco.com<mailto:l=
martini@cisco.com>> wrote:
Greg,

You are correct , the proposed update does not propose any changes to VCCV.
However the problem with vccv is not as simple as to ask for a new code poi=
nt from IANA.
Given the good amount of discussion on this point, we should probably have =
a discussion in Beijing.

Luca



On 10/29/2010 05:07 PM, Greg Mirsky wrote:

Dear Authors,
I think that proposed update of the Section 4.2. RFC 5586 makes it possible
to use GAL on MPLS-TP PW that uses Control Word. I consider it to be
conflict between PW VCCV CC types because use of GAL is not negotiated
through PW VCCV negotiation. To avoid such situation I propose:

   - in Section 5 request IANA to assign new CC Type "MPLS Generic
   Associated Channel Label"
   - assign precedence to new CC Type that affects Section 7 RFC 5085

Regards,
Greg




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




--_000_A3C5DF08D38B6049839A6F553B331C76D6FB8BEA8BILPTMAIL02eci_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr"><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta content=3D"MSHTML 6.00.6000.17063" name=3D"GENERATOR">
<style id=3D"owaTempEditStyle"></style><style title=3D"owaParaStyle"><!--P =
{
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
--></style>
</head>
<body ocsi=3D"x">
<div style=3D"FONT-SIZE: 16px; COLOR: #000000; DIRECTION: ltr; FONT-FAMILY:=
 Times New Roman">
<div>Greg, and all,</div>
<div><font face=3D"times new roman">I concur with Greg.</font></div>
<div><font face=3D"times new roman">Using GAL with PWs is highly problemati=
c, and all the related issues (raised during the poll on accepting this dra=
ft as a WG item) have not, AFAIK, been resolved.</font></div>
<div><font face=3D"times new roman"></font>&nbsp;</div>
<div><font face=3D"times new roman">Regards,</font></div>
<div><font face=3D"times new roman">&nbsp;&nbsp;&nbsp;&nbsp; Sasha</font></=
div>
<div dir=3D"ltr"><font face=3D"Times New Roman" color=3D"#000000" size=3D"3=
"></font>&nbsp;</div>
<div id=3D"divRpF628095" style=3D"DIRECTION: ltr">
<hr tabindex=3D"-1">
<font face=3D"Tahoma" color=3D"#000000" size=3D"2"><b>From:</b> mpls-tp-bou=
nces@ietf.org [mpls-tp-bounces@ietf.org] On Behalf Of Greg Mirsky [gregimir=
sky@gmail.com]<br>
<b>Sent:</b> Friday, February 18, 2011 8:47 AM<br>
<b>To:</b> Luca Martini<br>
<b>Cc:</b> mpls@ietf.org; mpls-tp@ietf.org; lihan@chinamobile.com; pwe3; HU=
ANG Feng F<br>
<b>Subject:</b> [mpls-tp] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt<br>
</font><br>
</div>
<div></div>
<div>Dear Authors and All,<br>
prior to the meeting in Bejing and acceptance of this proposal as WG docume=
nt Luca and I agreed that use of GAL with PW VCCV presents a problem.<br>
I was not attending the IETF-79, nor I found discussion of this issue in th=
e minutes. I think that this issue should be specified, explained. In my vi=
ew, this document updates not only RFC 5586<br>
but RFC 5085 too.<br>
<br>
Regards,<br>
Greg<br>
<br>
Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt<br>
<br>
<div class=3D"gmail_quote">On Sat, Oct 30, 2010 at 10:14 AM, Luca Martini <=
span dir=3D"ltr">
&lt;<a href=3D"mailto:lmartini@cisco.com">lmartini@cisco.com</a>&gt;</span>=
 wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0=
pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<div bgcolor=3D"#ffffff">Greg,<br>
<br>
You are correct , the proposed update does not propose any changes to VCCV.=
<br>
However the problem with vccv is not as simple as to ask for a new code poi=
nt from IANA.<br>
Given the good amount of discussion on this point, we should probably have =
a discussion in Beijing.<br>
<br>
Luca
<div>
<div></div>
<div class=3D"h5"><br>
<br>
<br>
On 10/29/2010 05:07 PM, Greg Mirsky wrote: </div>
</div>
<blockquote type=3D"cite">
<div>
<div></div>
<div class=3D"h5">
<pre>Dear Authors,
I think that proposed update of the Section 4.2. RFC 5586 makes it possible
to use GAL on MPLS-TP PW that uses Control Word. I consider it to be
conflict between PW VCCV CC types because use of GAL is not negotiated
through PW VCCV negotiation. To avoid such situation I propose:

   - in Section 5 request IANA to assign new CC Type &quot;MPLS Generic
   Associated Channel Label&quot;
   - assign precedence to new CC Type that affects Section 7 RFC 5085

Regards,
Greg

</pre>
</div>
</div>
<pre><fieldset></fieldset>
_______________________________________________
mpls mailing list
<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>
<a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/mpls</a>
</pre>
</blockquote>
<br>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</body>
</html>

--_000_A3C5DF08D38B6049839A6F553B331C76D6FB8BEA8BILPTMAIL02eci_--

From jie.dong@huawei.com  Fri Feb 18 00:57:49 2011
Return-Path: <jie.dong@huawei.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1166D3A6E0C; Fri, 18 Feb 2011 00:57:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.105
X-Spam-Level: 
X-Spam-Status: No, score=0.105 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  J_CHICKENPOX_35=0.6, RDNS_NONE=0.1]
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 sBFDlL+KYYS8; Fri, 18 Feb 2011 00:57:48 -0800 (PST)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id AA0043A6EAE; Fri, 18 Feb 2011 00:57:47 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LGT006TP26N5T@szxga05-in.huawei.com>; Fri, 18 Feb 2011 16:56:47 +0800 (CST)
Received: from szxeml202-edg.china.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTP id <0LGT003MH26MXV@szxga05-in.huawei.com>; Fri, 18 Feb 2011 16:56:46 +0800 (CST)
Received: from SZXEML404-HUB.china.huawei.com (10.82.67.59) by szxeml202-edg.china.huawei.com (172.24.2.42) with Microsoft SMTP Server (TLS) id 14.1.270.1; Fri, 18 Feb 2011 16:55:33 +0800
Received: from SZXEML508-MBX.china.huawei.com ([169.254.6.65]) by szxeml404-hub.china.huawei.com ([fe80::75b7:3db9:fedc:a56d%13]) with mapi id 14.01.0270.001; Fri, 18 Feb 2011 16:56:45 +0800
Date: Fri, 18 Feb 2011 08:56:45 +0000
From: Jie Dong <jie.dong@huawei.com>
In-reply-to: <E4873516F3FC7547BCFE792C7D94039C05F0D5@DEMUEXC013.nsn-intra.net>
X-Originating-IP: [10.110.98.31]
To: "Weingarten, Yaacov (NSN - IL/Hod HaSharon)" <yaacov.weingarten@nsn.com>,  "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Message-id: <76CD132C3ADEF848BD84D028D243C927AADC7B@szxeml508-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: zh-CN
Content-transfer-encoding: 7BIT
Accept-Language: zh-CN, en-US
Thread-topic: [mpls-tp] mpls wg last callon draft-ietf-mpls-tp-linear-protection-04
Thread-index: AcvDl10fqyGU6Z/HTcaxkW43UzP3eAFXdT1gATjyzUAAWWFeIA==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <4D4A9478.7050704@pi.nu> <021101cbc9c7$d7c8b140$875a13c0$@com> <E4873516F3FC7547BCFE792C7D94039C05F0D5@DEMUEXC013.nsn-intra.net>
Subject: Re: [mpls-tp] mpls wg last callon	draft-ietf-mpls-tp-linear-protection-04
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2011 08:57:49 -0000

Hi Yaacov,

Thanks for your reply, and please see in-line with [Jie]: 

> >> 6. Section 4.2.2, 4th paragraph,
> >> " The Fpath field SHALL identify the path that is reporting the
> >> failure
> >> condition (i.e. if protection path then Fpath is set to 0...".
> >> Since PSC message are only transmitted on protection path, if
> >> protection
> >> path has signal fail, the PSC message may not be able to be sent out
> >> to
> >> far-end.
> 
> yw>  Actually, if there is a signal failure on the protection path,
> there is a possibility that the messages may not be received by the
> far-end, however, it is advisable that the source end-point continue to
> transmit these messages.

[Jie] Actually this comment is also about the first sentence in 4.1:
"The PSC control packets SHALL be transmitted over the protection path only"
IMO, If the transmitting end knows (either through remote PSC message or local information) the transmitting direction of the protection path is in fault, it may use working path to send PSC message. This way the PSC message would always be sent on only one path, and the remote end could still receive this message in protection path failure scenarios.

> >> 7. Section 4.3.2, there is signal degrade on working path as input,
> >> but no
> >> signal degrade on protection path.
> 
> yw> Currently, the signal degrade input in this list is a place holder -
> the issue of how to deal with SD in general is for further study as
> stated in section 4.2.2.  Note - there have been lengthy discussions at
> several IETF meetings on how to deal with SD without any conclusions.

[Jie] OK. So will the SD part be added to this draft later, or it will be specified in a separate document?

> >> 8. Section 4.3.3, I go through this part fast, a general question is:
> >> are
> >> the PSC operations for 4 different protection types identical ? In
> >> this
> >> section there is no description about operation of each specific
> >> protection
> >> type, but to my understanding, there may be different operations,
> >> e.g., for
> >> bidirectional 1:1 protection, the end point may need to switch the
> >> sink
> >> selector and transmitting bridge simultaneously according to some
> >> input, but
> >> for unidirectional 1:1 the end point may only need to switch the
> >> transmitting bridge OR the sink selector. And the PSC message sent
> may
> >> also
> >> be different for different protection types. (Please correct me if
> >> there is
> >> anything wrong with this thought).
> 
> yw> Can you clarify for which scenario you believe that the messages
> generated should be different dependent upon the protection type (aside
> from the value of the protection type field)?  The exact actions of the
> selector and transmitting bridges are not fully described in the
> document aside from the note at the end of section 4.3.1.  In addition,
> in the introductory text of each state description in section 4.3.3.3.x
> describe how the user data is being transmitted.  Is there a feeling
> that we need to describe this separately for each scenario?

[Jie] As draft-sur-fwk specified, 
"For bidirectional P2P paths, both unidirectional and bidirectional protection switching are supported."

So an example is one end of the bidirectional path receives local signal fail on working path. This would normally be a failure in receiving direction on working path.
For 1:1 unidirectional protection, the protection actions in each direction are independent, then maybe one direction has switched to the protection path, while in the opposite direction the traffic is still on the working path. In this case the output PSC message should indicate the remote end to switch the transmitting bridge to protection path and keep the remote selector bridge unchanged. For this the "Path" Field may need to be extended to TxPath and RxPath, and the PSC message with the format REQ(Fpath, TxPath, RxPath) would be SF(1,0,1). 
If later a remote signal fail on working path is received, then the output message would be changed to SF(1,1,1).

For 1+1 bidirectional protection, the output PSC message should indicate the remote end to switch both the transmitting bridge and the selector bridge to protection path. Thus the output message would be SF(1,1,1).

Thus IMO for unidirectional and bidirectional protection the action would be different, and the messages may need be different to convey clear information.


Best regards,
Jie

> >> > -----Original Message-----
> >> > From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On
> >> > Behalf Of Loa Andersson
> >> > Sent: Thursday, February 03, 2011 7:42 PM
> >> > To: mpls-tp@ietf.org; mpls@ietf.org
> >> > Cc: ahmpls-tp@lists.itu.int
> >> > Subject: [mpls-tp] mpls wg last call on
> >> draft-ietf-mpls-tp-linear-protection-04
> >> >
> >> > Working Group,
> >> >
> >> > this is to start a four week working group last call on
> >> > "MPLS-TP Linear Protection" (draft-ietf-mpls-tp-linear-protection-
> >> 04).
> >> >
> >> > Please send comments to the mpls-tp@ietf.org mailing list.
> >> >
> >> > This working group last call ends on February 28, 2011.
> >> >
> >> >
> >> >
> >> > Loa, George and Ross
> >> >
> >> > MPLS wg co-chairs
> >> >
> >> >
> >> >
> >> > --
> >> >
> >> >
> >> > Loa Andersson                         email:
> >> > loa.andersson@ericsson.com
> >> > Sr Strategy and Standards Manager            loa@pi.nu
> >> > Ericsson Inc                          phone: +46 10 717 52 13
> >> >                                               +46 767 72 92 13
> >> > _______________________________________________
> >> > mpls-tp mailing list
> >> > mpls-tp@ietf.org
> >> > https://www.ietf.org/mailman/listinfo/mpls-tp
> >>
> >>
> >>
> >> _______________________________________________
> >> mpls-tp mailing list
> >> mpls-tp@ietf.org
> >> https://www.ietf.org/mailman/listinfo/mpls-tp

From jie.dong@huawei.com  Fri Feb 18 01:15:13 2011
Return-Path: <jie.dong@huawei.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 096BD3A6E88; Fri, 18 Feb 2011 01:15:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.195
X-Spam-Level: 
X-Spam-Status: No, score=-2.195 tagged_above=-999 required=5 tests=[AWL=2.300,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
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 Up9FCBfkQh+l; Fri, 18 Feb 2011 01:15:12 -0800 (PST)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id BFE3B3A6E81; Fri, 18 Feb 2011 01:15:11 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LGT000L730DRY@szxga03-in.huawei.com>; Fri, 18 Feb 2011 17:14:37 +0800 (CST)
Received: from szxeml201-edg.china.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTP id <0LGT004JO30B2Q@szxga03-in.huawei.com>; Fri, 18 Feb 2011 17:14:37 +0800 (CST)
Received: from SZXEML401-HUB.china.huawei.com (10.82.67.31) by szxeml201-edg.china.huawei.com (172.24.2.39) with Microsoft SMTP Server (TLS) id 14.1.270.1; Fri, 18 Feb 2011 17:14:32 +0800
Received: from SZXEML508-MBX.china.huawei.com ([169.254.6.65]) by SZXEML401-HUB.china.huawei.com ([10.82.67.31]) with mapi id 14.01.0270.001; Fri, 18 Feb 2011 17:14:34 +0800
Date: Fri, 18 Feb 2011 09:14:33 +0000
From: Jie Dong <jie.dong@huawei.com>
In-reply-to: <D29E470202D67745B61059870F433B540461B15B@XMB-RCD-202.cisco.com>
X-Originating-IP: [10.110.98.31]
To: "Eric Osborne (eosborne)" <eosborne@cisco.com>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Message-id: <76CD132C3ADEF848BD84D028D243C927AADCA1@szxeml508-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: zh-CN
Content-transfer-encoding: 7BIT
Accept-Language: zh-CN, en-US
Thread-topic: [mpls-tp] mpls wg last callon draft-ietf-mpls-tp-linear-protection-04
Thread-index: AcvDl10fqyGU6Z/HTcaxkW43UzP3eAFXdT1gAUNLvlAAUdyZIA==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <4D4A9478.7050704@pi.nu> <021101cbc9c7$d7c8b140$875a13c0$@com> <D29E470202D67745B61059870F433B540461B15B@XMB-RCD-202.cisco.com>
Subject: Re: [mpls-tp] mpls wg last callon	draft-ietf-mpls-tp-linear-protection-04
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2011 09:15:13 -0000

Hi Eric, 

Thanks for your reply, and please see in-line with [Jie]:

> -----Original Message-----
> From: Eric Osborne (eosborne) [mailto:eosborne@cisco.com]
> Sent: Thursday, February 17, 2011 1:58 AM
> To: Jie Dong; mpls-tp@ietf.org; mpls@ietf.org
> Subject: RE: [mpls-tp] mpls wg last callon
> draft-ietf-mpls-tp-linear-protection-04
> 
> Hi Jie-
> 
>   Yaacov has replied to most of your comments, but let me add two
> things:
> 
> 
> >
> > 6. Section 4.2.2, 4th paragraph,
> > " The Fpath field SHALL identify the path that is reporting the
> failure
> > condition (i.e. if protection path then Fpath is set to 0...".
> > Since PSC message are only transmitted on protection path, if
> protection
> > path has signal fail, the PSC message may not be able to be sent out
> to
> > far-end.
> 
> 
> As Yaacov has mentioned, we would like the PSC to send messages anyways
> in the chance that they may get through.  This is explicitly noted in
> section 4.3.3.2:

> ---
> "When the domain is in unavailable state the PSC messages may not get
> through and therefore the protection is more dependent on the local
> inputs rather than the remote messages (that may not be received)."
> ----
> 
> Is that sufficient, or do you think we need additional text to reinforce
> this point?

[Jie] I acknowledge this purpose, and my further comment would be the same as to Yaacov: what about sending this message through working path if it is known the transmitting direction of the protection path is in failure? In this way the message is still sent on only one path.

> > 8. Section 4.3.3, I go through this part fast, a general question is:
> are
> > the PSC operations for 4 different protection types identical ? In
> this
> > section there is no description about operation of each specific
> > protection type, but to my understanding, there may be different
> > operations, e.g., for bidirectional 1:1 protection, the end point may
> need
> > to switch the sink selector and transmitting bridge simultaneously
> > according to some input, but for unidirectional 1:1 the end point may
> only
> > need to switch the transmitting bridge OR the sink selector. And the
> PSC
> > message sent may also be different for different protection types.
> (Please
> > correct me if there is anything wrong with this thought).
> 
> 
> PSC is not, in my view, tightly coupled to the four protection types.
> That is to say, PSC is a tool that allows the device vendor and network
> operator to build protection in an MPLS-TP network.  This protection can
> be one of the four protection types you describe, but PSC is merely a
> protocol to accomplish the end goal.  It may, for example, be possible
> in the future to use PSC to build one or more types of 1:n protection;
> when and if this is done, the message types would likely remain the same
> as they are now.
> 

I agree that PSC protocol can be used for all these protection types, and may also be applicable to 1:n protection, but for each protection type the state machine may be slightly different. The draft-tp-cc-cv-rdi also works in this way. The message types are likely the same, but some fields in the message may be different.


Best regards,
Jie

> >
> > > -----Original Message-----
> > > From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On
> > > Behalf Of Loa Andersson
> > > Sent: Thursday, February 03, 2011 7:42 PM
> > > To: mpls-tp@ietf.org; mpls@ietf.org
> > > Cc: ahmpls-tp@lists.itu.int
> > > Subject: [mpls-tp] mpls wg last call on
> > draft-ietf-mpls-tp-linear-protection-04
> > >
> > > Working Group,
> > >
> > > this is to start a four week working group last call on "MPLS-TP
> > > Linear Protection" (draft-ietf-mpls-tp-linear-protection-04).
> > >
> > > Please send comments to the mpls-tp@ietf.org mailing list.
> > >
> > > This working group last call ends on February 28, 2011.
> > >
> > >
> > >
> > > Loa, George and Ross
> > >
> > > MPLS wg co-chairs
> > >
> > >
> > >
> > > --
> > >
> > >
> > > Loa Andersson                         email:
> > > loa.andersson@ericsson.com
> > > Sr Strategy and Standards Manager            loa@pi.nu
> > > Ericsson Inc                          phone: +46 10 717 52 13
> > >                                               +46 767 72 92 13
> > > _______________________________________________
> > > mpls-tp mailing list
> > > mpls-tp@ietf.org
> > > https://www.ietf.org/mailman/listinfo/mpls-tp
> >
> >
> >
> > _______________________________________________
> > mpls-tp mailing list
> > mpls-tp@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls-tp

From neil.2.harrison@bt.com  Fri Feb 18 01:17:28 2011
Return-Path: <neil.2.harrison@bt.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DCA853A6E81; Fri, 18 Feb 2011 01:17:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.445
X-Spam-Level: 
X-Spam-Status: No, score=-1.445 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_21=0.6]
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 eMwjF7K2DcqV; Fri, 18 Feb 2011 01:17:27 -0800 (PST)
Received: from smtpe1.intersmtp.com (smtp63.intersmtp.COM [62.239.224.236]) by core3.amsl.com (Postfix) with ESMTP id B9C183A6E0C; Fri, 18 Feb 2011 01:17:26 -0800 (PST)
Received: from EVMHT67-UKRD.domain1.systemhost.net (10.36.3.104) by RDW083A007ED63.smtp-e3.hygiene.service (10.187.98.12) with Microsoft SMTP Server (TLS) id 8.3.106.1; Fri, 18 Feb 2011 09:17:58 +0000
Received: from EMV62-UKRD.domain1.systemhost.net ([169.254.2.15]) by EVMHT67-UKRD.domain1.systemhost.net ([10.36.3.104]) with mapi; Fri, 18 Feb 2011 09:17:58 +0000
From: <neil.2.harrison@bt.com>
To: <Alexander.Vainshtein@ecitele.com>, <gregimirsky@gmail.com>
Date: Fri, 18 Feb 2011 09:17:54 +0000
Thread-Topic: [mpls-tp] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
Thread-Index: AcvPN6zTJGq/0XxDTGy6v16DWGU3fgAAocFMAAQ7z9A=
Message-ID: <6D3D47CB84BDE349BC23BF1C94E316E440145CA70F@EMV62-UKRD.domain1.systemhost.net>
References: <AANLkTikcnCa5DQZyGgD_QawiQ_57KKA4BXQm7iRRayKA@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C76D6FB8BEA8B@ILPTMAIL02.ecitele.com>
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C76D6FB8BEA8B@ILPTMAIL02.ecitele.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: multipart/alternative; boundary="_000_6D3D47CB84BDE349BC23BF1C94E316E440145CA70FEMV62UKRDdoma_"
MIME-Version: 1.0
Cc: mpls@ietf.org, HUANG@core3.amsl.com, Rotem@core3.amsl.com, mpls-tp@ietf.org, Mishael.Wexler@ecitele.com, lihan@chinamobile.com, pwe3@ietf.org, Feng.f.Huang@alcatel-sbell.com.cn, Robert.Rennison@ecitele.com, Rotem.Cohen@ecitele.com
Subject: Re: [mpls-tp] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2011 09:17:29 -0000

--_000_6D3D47CB84BDE349BC23BF1C94E316E440145CA70FEMV62UKRDdoma_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Sasha/Greg,



I would certainly agree that the use of the GAL with PWs is wrong....but th=
e reason for that is simply that PWs per se violate the whole purpose of MP=
LS-TP as a *transparent* transport network, noting that a true transport ne=
twork must treat all client symbols equally...that is just a fact.



However, given PWs are being carried forward into MPLS-TP then we also have=
 to deal with the issue that CP/MP of a transport network needs to logicall=
y OOB wrt to the DP traffic.  The GAL provides this function for the MPLS-T=
P layer network itself (though it also gets this a wee bit wrong by asking =
it to play a DP OAM role too,) but what about the PW layer network?



MS PWs for sure are their own/different layer network....so they will need =
their own access point addressing, OAM, routing, signalling, etc.  I asked =
some time ago why we were not using RSVP signalling here but T-LDP instead.=
..and I was told that RSVP cannot handle the PW signalling messages (nor th=
e access addressing formats I assume...and we will of course need a new ins=
tance of routing that will).



So how is T-LDP being taken OOB wrt to the PW DP?



regards, Neil

Neil Harrison
BT Design

Tel: +44 (0) 1 803 812 545
Email: neil.2.harrison@bt.com<mailto:neil.2.harrison@bt.com>
Web: www.bt.com<http://www.bt.com/>
This email contains BT information, which may be privileged or confidential=
.
It's meant only for the individual(s) or entity named above. If you're not =
the intended
recipient, note that disclosing, copying, distributing or using this inform=
ation
is prohibited. If you've received this email in error, please let me know i=
mmediately
on the email address above. Thank you.
We monitor our email system, and may record your emails.
British Telecommunications plc
Registered office: 81 Newgate Street London EC1A 7AJ
Registered in England no: 1800000





From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Ale=
xander Vainshtein
Sent: 18 February 2011 07:05
To: Greg Mirsky
Cc: Robert Rennison; mpls@ietf.org; Luca Martini; mpls-tp@ietf.org; Mishael=
 Wexler; lihan@chinamobile.com; pwe3; Rotem@core3.amsl.com; HUANG@core3.ams=
l.com; Feng F; Cohen
Subject: Re: [PWE3] [mpls-tp] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt

Greg, and all,
I concur with Greg.
Using GAL with PWs is highly problematic, and all the related issues (raise=
d during the poll on accepting this draft as a WG item) have not, AFAIK, be=
en resolved.

Regards,
     Sasha

________________________________
From: mpls-tp-bounces@ietf.org [mpls-tp-bounces@ietf.org] On Behalf Of Greg=
 Mirsky [gregimirsky@gmail.com]
Sent: Friday, February 18, 2011 8:47 AM
To: Luca Martini
Cc: mpls@ietf.org; mpls-tp@ietf.org; lihan@chinamobile.com; pwe3; HUANG Fen=
g F
Subject: [mpls-tp] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
Dear Authors and All,
prior to the meeting in Bejing and acceptance of this proposal as WG docume=
nt Luca and I agreed that use of GAL with PW VCCV presents a problem.
I was not attending the IETF-79, nor I found discussion of this issue in th=
e minutes. I think that this issue should be specified, explained. In my vi=
ew, this document updates not only RFC 5586
but RFC 5085 too.

Regards,
Greg

Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
On Sat, Oct 30, 2010 at 10:14 AM, Luca Martini <lmartini@cisco.com<mailto:l=
martini@cisco.com>> wrote:
Greg,

You are correct , the proposed update does not propose any changes to VCCV.
However the problem with vccv is not as simple as to ask for a new code poi=
nt from IANA.
Given the good amount of discussion on this point, we should probably have =
a discussion in Beijing.

Luca



On 10/29/2010 05:07 PM, Greg Mirsky wrote:

Dear Authors,

I think that proposed update of the Section 4.2. RFC 5586 makes it possible

to use GAL on MPLS-TP PW that uses Control Word. I consider it to be

conflict between PW VCCV CC types because use of GAL is not negotiated

through PW VCCV negotiation. To avoid such situation I propose:



   - in Section 5 request IANA to assign new CC Type "MPLS Generic

   Associated Channel Label"

   - assign precedence to new CC Type that affects Section 7 RFC 5085



Regards,

Greg





_______________________________________________

mpls mailing list

mpls@ietf.org<mailto:mpls@ietf.org>

https://www.ietf.org/mailman/listinfo/mpls



--_000_6D3D47CB84BDE349BC23BF1C94E316E440145CA70FEMV62UKRDdoma_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"Comic Sans MS";
	panose-1:3 15 7 2 3 3 2 2 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
p
	{mso-style-priority:99;
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Courier New";}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Verdana","sans-serif";
	color:#632423;
	font-weight:normal;
	font-style:normal;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-GB link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoPlainText>Sasha/Greg,<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>I would certainly agree that the use of the GAL wit=
h PWs
is wrong....but the reason for that is simply that PWs per se violate the w=
hole
purpose of MPLS-TP as a *transparent* transport network, noting that a true
transport network must treat all client symbols equally...that is just a
fact.&nbsp; <o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>However, given PWs are being carried forward into M=
PLS-TP
then we also have to deal with the issue that CP/MP of a transport network
needs to logically OOB wrt to the DP traffic.&nbsp; The GAL provides this
function for the MPLS-TP layer network itself (though it also gets this a w=
ee
bit wrong by asking it to play a DP OAM role too,) but what about the PW la=
yer
network?<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>MS PWs for sure are their own/different layer
network....so they will need their own access point addressing, OAM, routin=
g,
signalling, etc.&nbsp; I asked some time ago why we were not using RSVP
signalling here but T-LDP instead...and I was told that RSVP cannot handle =
the
PW signalling messages (nor the access addressing formats I assume...and we
will of course need a new instance of routing that will).<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>So how is T-LDP being taken OOB wrt to the PW DP?<o=
:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>regards, Neil<o:p></o:p></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:5.0pt;margin-right:0cm;mar=
gin-bottom:
5.0pt;margin-left:0cm;text-autospace:none'><b><i><span style=3D'font-size:9=
.0pt;
font-family:"Calibri","sans-serif";color:navy'>Neil Harrison<br>
BT Design<br>
</span></i></b><span style=3D'font-size:9.0pt;font-family:"Calibri","sans-s=
erif";
color:#632423'><br>
</span><span style=3D'font-size:9.0pt;font-family:"Calibri","sans-serif";
color:gray'>Tel: +44 (0) 1 803 812 545<br>
Email: <a href=3D"mailto:neil.2.harrison@bt.com"><span style=3D'color:gray'=
>neil.2.harrison@bt.com</span></a><br>
Web: <a href=3D"http://www.bt.com/"><span style=3D'color:gray'>www.bt.com</=
span></a><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:5.0pt;margin-right:0cm;mar=
gin-bottom:
5.0pt;margin-left:0cm;text-autospace:none'><span style=3D'font-size:7.0pt;
font-family:"Calibri","sans-serif";color:gray'>This email contains BT
information, which may be privileged or confidential.<br>
It's meant only for the individual(s) or entity named above. If you're not =
the
intended<br>
recipient, note that disclosing, copying, distributing or using this
information<br>
is prohibited. If you've received this email in error, please let me know
immediately<br>
on the email address above. Thank you.<br>
We monitor our email system, and may record your emails.<o:p></o:p></span><=
/p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span style=3D'font-size=
:7.0pt;
font-family:"Calibri","sans-serif";color:gray'>British Telecommunications p=
lc<br>
Registered office: 81 Newgate Street London EC1A 7AJ<br>
Registered in England no: 1800000</span><span style=3D'font-size:10.0pt;
font-family:"Comic Sans MS";color:maroon'><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'>

<p class=3DMsoNormal><b><span lang=3DEN-US style=3D'font-size:10.0pt;font-f=
amily:
"Tahoma","sans-serif"'>From:</span></b><span lang=3DEN-US style=3D'font-siz=
e:10.0pt;
font-family:"Tahoma","sans-serif"'> pwe3-bounces@ietf.org
[mailto:pwe3-bounces@ietf.org] <b>On Behalf Of </b>Alexander Vainshtein<br>
<b>Sent:</b> 18 February 2011 07:05<br>
<b>To:</b> Greg Mirsky<br>
<b>Cc:</b> Robert Rennison; mpls@ietf.org; Luca Martini; mpls-tp@ietf.org;
Mishael Wexler; lihan@chinamobile.com; pwe3; Rotem@core3.amsl.com;
HUANG@core3.amsl.com; Feng F; Cohen<br>
<b>Subject:</b> Re: [PWE3] [mpls-tp] WG LC
draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<div>

<div>

<p class=3DMsoNormal><span style=3D'color:black'>Greg, and all,<o:p></o:p><=
/span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'color:black'>I concur with Greg.<o:p></=
o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'color:black'>Using GAL with PWs is high=
ly
problematic, and all the related issues (raised during the poll on acceptin=
g
this draft as a WG item) have not, AFAIK, been resolved.<o:p></o:p></span><=
/p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'color:black'>&nbsp;<o:p></o:p></span></=
p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'color:black'>Regards,<o:p></o:p></span>=
</p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'color:black'>&nbsp;&nbsp;&nbsp;&nbsp; S=
asha<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'color:black'>&nbsp;<o:p></o:p></span></=
p>

</div>

<div id=3DdivRpF628095>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span
style=3D'color:black'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><span style=3D'font-=
size:10.0pt;
font-family:"Tahoma","sans-serif";color:black'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>
mpls-tp-bounces@ietf.org [mpls-tp-bounces@ietf.org] On Behalf Of Greg Mirsk=
y
[gregimirsky@gmail.com]<br>
<b>Sent:</b> Friday, February 18, 2011 8:47 AM<br>
<b>To:</b> Luca Martini<br>
<b>Cc:</b> mpls@ietf.org; mpls-tp@ietf.org; lihan@chinamobile.com; pwe3; HU=
ANG
Feng F<br>
<b>Subject:</b> [mpls-tp] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt</spa=
n><span
style=3D'color:black'><o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span style=3D'color:bl=
ack'>Dear
Authors and All,<br>
prior to the meeting in Bejing and acceptance of this proposal as WG docume=
nt
Luca and I agreed that use of GAL with PW VCCV presents a problem.<br>
I was not attending the IETF-79, nor I found discussion of this issue in th=
e
minutes. I think that this issue should be specified, explained. In my view=
,
this document updates not only RFC 5586<br>
but RFC 5085 too.<br>
<br>
Regards,<br>
Greg<br>
<br>
Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt<o:p></o:p></span></p>

<div>

<p class=3DMsoNormal><span style=3D'color:black'>On Sat, Oct 30, 2010 at 10=
:14 AM,
Luca Martini &lt;<a href=3D"mailto:lmartini@cisco.com">lmartini@cisco.com</=
a>&gt;
wrote:<o:p></o:p></span></p>

<div>

<p class=3DMsoNormal><span style=3D'color:black'>Greg,<br>
<br>
You are correct , the proposed update does not propose any changes to VCCV.=
<br>
However the problem with vccv is not as simple as to ask for a new code poi=
nt
from IANA.<br>
Given the good amount of discussion on this point, we should probably have =
a
discussion in Beijing.<br>
<br>
Luca <o:p></o:p></span></p>

<div>

<div>

<p class=3DMsoNormal><span style=3D'color:black'><br>
<br>
<br>
On 10/29/2010 05:07 PM, Greg Mirsky wrote: <o:p></o:p></span></p>

</div>

</div>

<blockquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt'>

<div>

<div><pre><span style=3D'color:black'>Dear Authors,<o:p></o:p></span></pre>=
<pre><span
style=3D'color:black'>I think that proposed update of the Section 4.2. RFC =
5586 makes it possible<o:p></o:p></span></pre><pre><span
style=3D'color:black'>to use GAL on MPLS-TP PW that uses Control Word. I co=
nsider it to be<o:p></o:p></span></pre><pre><span
style=3D'color:black'>conflict between PW VCCV CC types because use of GAL =
is not negotiated<o:p></o:p></span></pre><pre><span
style=3D'color:black'>through PW VCCV negotiation. To avoid such situation =
I propose:<o:p></o:p></span></pre><pre><span
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span style=3D'col=
or:black'>&nbsp;&nbsp; - in Section 5 request IANA to assign new CC Type &q=
uot;MPLS Generic<o:p></o:p></span></pre><pre><span
style=3D'color:black'>&nbsp;&nbsp; Associated Channel Label&quot;<o:p></o:p=
></span></pre><pre><span
style=3D'color:black'>&nbsp;&nbsp; - assign precedence to new CC Type that =
affects Section 7 RFC 5085<o:p></o:p></span></pre><pre><span
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span style=3D'col=
or:black'>Regards,<o:p></o:p></span></pre><pre><span
style=3D'color:black'>Greg<o:p></o:p></span></pre><pre><span style=3D'color=
:black'><o:p>&nbsp;</o:p></span></pre></div>

</div>

<pre><span style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span
style=3D'color:black'>_______________________________________________<o:p><=
/o:p></span></pre><pre><span
style=3D'color:black'>mpls mailing list<o:p></o:p></span></pre><pre><span
style=3D'color:black'><a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><o:=
p></o:p></span></pre><pre><span
style=3D'color:black'><a href=3D"https://www.ietf.org/mailman/listinfo/mpls=
"
target=3D"_blank">https://www.ietf.org/mailman/listinfo/mpls</a><o:p></o:p>=
</span></pre></blockquote>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

</div>

</div>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

</div>

</div>

</div>

</div>

</body>

</html>

--_000_6D3D47CB84BDE349BC23BF1C94E316E440145CA70FEMV62UKRDdoma_--

From martin.vigoureux@alcatel-lucent.com  Fri Feb 18 05:26:09 2011
Return-Path: <martin.vigoureux@alcatel-lucent.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 52A5F3A6EF9; Fri, 18 Feb 2011 05:26:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 6HuQ+IrA0d44; Fri, 18 Feb 2011 05:26:08 -0800 (PST)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id 430873A6C80; Fri, 18 Feb 2011 05:26:07 -0800 (PST)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail5.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p1IDQeVJ009599 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 18 Feb 2011 14:26:40 +0100
Received: from [135.244.197.111] (135.120.57.7) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (135.120.45.61) with Microsoft SMTP Server (TLS) id 8.3.106.1; Fri, 18 Feb 2011 14:26:40 +0100
Message-ID: <4D5E7389.7040604@alcatel-lucent.com>
Date: Fri, 18 Feb 2011 14:26:33 +0100
From: Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: "MPLS @ IETF" <mpls@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.13
Cc: "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: [mpls-tp] Slots requests for IETF 80 - Prague
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2011 13:26:09 -0000

All,

it is time we start building the agenda for Prague.
Please send me your requests for a presentation slot indicating:
draft name, speaker and duration

Please be aware that we might not be able to satisfy all requests.

Thank you.

regards,
martin

From lmartini@cisco.com  Fri Feb 18 07:45:50 2011
Return-Path: <lmartini@cisco.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B20B93A6F0A; Fri, 18 Feb 2011 07:45:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 8nEUV7B-PuYx; Fri, 18 Feb 2011 07:45:49 -0800 (PST)
Received: from napoleon.monoski.com (napoleon.monoski.com [70.90.113.113]) by core3.amsl.com (Postfix) with ESMTP id 96D6A3A6D47; Fri, 18 Feb 2011 07:45:49 -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 p1IFkAcH000113 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Fri, 18 Feb 2011 08:46:11 -0700 (MST)
Message-ID: <4D5E9442.3030101@cisco.com>
Date: Fri, 18 Feb 2011 08:46:10 -0700
From: Luca Martini <lmartini@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 ThunderBrowse/3.3.4
MIME-Version: 1.0
To: Greg Mirsky <gregimirsky@gmail.com>
References: <AANLkTikcnCa5DQZyGgD_QawiQ_57KKA4BXQm7iRRayKA@mail.gmail.com>
In-Reply-To: <AANLkTikcnCa5DQZyGgD_QawiQ_57KKA4BXQm7iRRayKA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: lihan@chinamobile.com, mpls@ietf.org, pwe3 <pwe3@ietf.org>, HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>, mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2011 15:45:50 -0000

Greg,

Sorry, but I do not remember the point you mention.
Can you explain again here ?
Thanks.
Luca


On 02/17/11 23:47, Greg Mirsky wrote:
> Dear Authors and All,
> prior to the meeting in Bejing and acceptance of this proposal as WG
> document Luca and I agreed that use of GAL with PW VCCV presents a
> problem.
> I was not attending the IETF-79, nor I found discussion of this issue
> in the minutes. I think that this issue should be specified,
> explained. In my view, this document updates not only RFC 5586
> but RFC 5085 too.
>
> Regards,
> Greg
>
> Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
>
> On Sat, Oct 30, 2010 at 10:14 AM, Luca Martini <lmartini@cisco.com
> <mailto:lmartini@cisco.com>> wrote:
>
>     Greg,
>
>     You are correct , the proposed update does not propose any changes
>     to VCCV.
>     However the problem with vccv is not as simple as to ask for a new
>     code point from IANA.
>     Given the good amount of discussion on this point, we should
>     probably have a discussion in Beijing.
>
>     Luca
>
>
>
>     On 10/29/2010 05:07 PM, Greg Mirsky wrote:
>>     Dear Authors,
>>     I think that proposed update of the Section 4.2. RFC 5586 makes it possible
>>     to use GAL on MPLS-TP PW that uses Control Word. I consider it to be
>>     conflict between PW VCCV CC types because use of GAL is not negotiated
>>     through PW VCCV negotiation. To avoid such situation I propose:
>>
>>        - in Section 5 request IANA to assign new CC Type "MPLS Generic
>>        Associated Channel Label"
>>        - assign precedence to new CC Type that affects Section 7 RFC 5085
>>
>>     Regards,
>>     Greg
>>
>>
>>
>>     _______________________________________________
>>     mpls mailing list
>>     mpls@ietf.org <mailto:mpls@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/mpls
>
>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


From davari@broadcom.com  Fri Feb 18 09:15:40 2011
Return-Path: <davari@broadcom.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A8AF83A6D56; Fri, 18 Feb 2011 09:15:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.348
X-Spam-Level: 
X-Spam-Status: No, score=-2.348 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BAD_LINEBREAK=0.5]
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 yWTUe9upzuNI; Fri, 18 Feb 2011 09:15:39 -0800 (PST)
Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by core3.amsl.com (Postfix) with ESMTP id 56EE03A6CC7; Fri, 18 Feb 2011 09:15:39 -0800 (PST)
Received: from [10.16.192.232] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Fri, 18 Feb 2011 09:17:34 -0800
X-Server-Uuid: D3C04415-6FA8-4F2C-93C1-920E106A2031
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB02.corp.ad.broadcom.com ([10.16.192.232]) with mapi; Fri, 18 Feb 2011 09:15:37 -0800
From: "Shahram Davari" <davari@broadcom.com>
To: "'Alexander.Vainshtein@ecitele.com'" <Alexander.Vainshtein@ecitele.com>, "'gregimirsky@gmail.com'" <gregimirsky@gmail.com>
Date: Fri, 18 Feb 2011 09:15:36 -0800
Thread-Topic: [PWE3] [mpls-tp] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
Thread-Index: AcvPN6zTJGq/0XxDTGy6v16DWGU3fgAAocFMABVQVLE=
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD69419A002F9@SJEXCHCCR02.corp.ad.broadcom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 614076275OK8247826-01-01
Content-Type: multipart/alternative; boundary=_000_2C2F1EBA8050E74EA81502D5740B4BD69419A002F9SJEXCHCCR02co_
Cc: "'mpls@ietf.org'" <mpls@ietf.org>, "'HUANG@core3.amsl.com'" <HUANG@core3.amsl.com>, "'Rotem@core3.amsl.com'" <Rotem@core3.amsl.com>, "'mpls-tp@ietf.org'" <mpls-tp@ietf.org>, "'Mishael.Wexler@ecitele.com'" <Mishael.Wexler@ecitele.com>, "'lihan@chinamobile.com'" <lihan@chinamobile.com>, "'pwe3@ietf.org'" <pwe3@ietf.org>, "'Feng.f.Huang@alcatel-sbell.com.cn'" <Feng.f.Huang@alcatel-sbell.com.cn>, "'Robert.Rennison@ecitele.com'" <Robert.Rennison@ecitele.com>, "'Rotem.Cohen@ecitele.com'" <Rotem.Cohen@ecitele.com>
Subject: Re: [mpls-tp] [PWE3]  WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2011 17:15:40 -0000

--_000_2C2F1EBA8050E74EA81502D5740B4BD69419A002F9SJEXCHCCR02co_
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: base64

SSBhbHNvIGFncmVlIHdpdGggU2FzaGEuIENyZWF0aW5nIGEgVkNDViB0eXBlIDQgaXMgcHJvYmxl
bWF0aWMsIGFsbW9zdCBubyBoYXJkd2FyZSBleGlzdCBmb3IgaXQgYW5kIGNhdXNlcyBpbnRlcndv
cmtpbmcgaXNzdWVzLiBTaWduYWxpbmcgVkNDViBuZWVkcyB0byBjaGFuZ2UgYXMgd2VsbC4NCg0K
VGh4DQpTaGFocmFtDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpGcm9tOiBw
d2UzLWJvdW5jZXNAaWV0Zi5vcmcgPHB3ZTMtYm91bmNlc0BpZXRmLm9yZz4NClRvOiBHcmVnIE1p
cnNreSA8Z3JlZ2ltaXJza3lAZ21haWwuY29tPg0KQ2M6IFJvYmVydCBSZW5uaXNvbiA8Um9iZXJ0
LlJlbm5pc29uQGVjaXRlbGUuY29tPjsgbXBsc0BpZXRmLm9yZyA8bXBsc0BpZXRmLm9yZz47IEx1
Y2EgTWFydGluaSA8bG1hcnRpbmlAY2lzY28uY29tPjsgbXBscy10cEBpZXRmLm9yZyA8bXBscy10
cEBpZXRmLm9yZz47IE1pc2hhZWwgV2V4bGVyIDxNaXNoYWVsLldleGxlckBlY2l0ZWxlLmNvbT47
IGxpaGFuQGNoaW5hbW9iaWxlLmNvbSA8bGloYW5AY2hpbmFtb2JpbGUuY29tPjsgcHdlMyA8cHdl
M0BpZXRmLm9yZz47IFJvdGVtQGNvcmUzLmFtc2wuY29tIDxSb3RlbUBjb3JlMy5hbXNsLmNvbT47
IEhVQU5HQGNvcmUzLmFtc2wuY29tIDxIVUFOR0Bjb3JlMy5hbXNsLmNvbT47IEZlbmcgRiA8RmVu
Zy5mLkh1YW5nQGFsY2F0ZWwtc2JlbGwuY29tLmNuPjsgQ29oZW4gPFJvdGVtLkNvaGVuQGVjaXRl
bGUuY29tPg0KU2VudDogVGh1IEZlYiAxNyAyMzowNToxOSAyMDExDQpTdWJqZWN0OiBSZTogW1BX
RTNdIFttcGxzLXRwXSBXRyBMQyBkcmFmdC1sbS1wd2UzLW1wbHMtdHAtZ2FsLWluLXB3LTAwLnR4
dA0KDQpHcmVnLCBhbmQgYWxsLA0KSSBjb25jdXIgd2l0aCBHcmVnLg0KVXNpbmcgR0FMIHdpdGgg
UFdzIGlzIGhpZ2hseSBwcm9ibGVtYXRpYywgYW5kIGFsbCB0aGUgcmVsYXRlZCBpc3N1ZXMgKHJh
aXNlZCBkdXJpbmcgdGhlIHBvbGwgb24gYWNjZXB0aW5nIHRoaXMgZHJhZnQgYXMgYSBXRyBpdGVt
KSBoYXZlIG5vdCwgQUZBSUssIGJlZW4gcmVzb2x2ZWQuDQoNClJlZ2FyZHMsDQogICAgIFNhc2hh
DQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpGcm9tOiBtcGxzLXRwLWJvdW5j
ZXNAaWV0Zi5vcmcgW21wbHMtdHAtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIEdyZWcg
TWlyc2t5IFtncmVnaW1pcnNreUBnbWFpbC5jb21dDQpTZW50OiBGcmlkYXksIEZlYnJ1YXJ5IDE4
LCAyMDExIDg6NDcgQU0NClRvOiBMdWNhIE1hcnRpbmkNCkNjOiBtcGxzQGlldGYub3JnOyBtcGxz
LXRwQGlldGYub3JnOyBsaWhhbkBjaGluYW1vYmlsZS5jb207IHB3ZTM7IEhVQU5HIEZlbmcgRg0K
U3ViamVjdDogW21wbHMtdHBdIFdHIExDIGRyYWZ0LWxtLXB3ZTMtbXBscy10cC1nYWwtaW4tcHct
MDAudHh0DQoNCkRlYXIgQXV0aG9ycyBhbmQgQWxsLA0KcHJpb3IgdG8gdGhlIG1lZXRpbmcgaW4g
QmVqaW5nIGFuZCBhY2NlcHRhbmNlIG9mIHRoaXMgcHJvcG9zYWwgYXMgV0cgZG9jdW1lbnQgTHVj
YSBhbmQgSSBhZ3JlZWQgdGhhdCB1c2Ugb2YgR0FMIHdpdGggUFcgVkNDViBwcmVzZW50cyBhIHBy
b2JsZW0uDQpJIHdhcyBub3QgYXR0ZW5kaW5nIHRoZSBJRVRGLTc5LCBub3IgSSBmb3VuZCBkaXNj
dXNzaW9uIG9mIHRoaXMgaXNzdWUgaW4gdGhlIG1pbnV0ZXMuIEkgdGhpbmsgdGhhdCB0aGlzIGlz
c3VlIHNob3VsZCBiZSBzcGVjaWZpZWQsIGV4cGxhaW5lZC4gSW4gbXkgdmlldywgdGhpcyBkb2N1
bWVudCB1cGRhdGVzIG5vdCBvbmx5IFJGQyA1NTg2DQpidXQgUkZDIDUwODUgdG9vLg0KDQpSZWdh
cmRzLA0KR3JlZw0KDQpDb21tZW50IHRvIGRyYWZ0LWxtLXB3ZTMtbXBscy10cC1nYWwtaW4tcHct
MDAudHh0DQoNCk9uIFNhdCwgT2N0IDMwLCAyMDEwIGF0IDEwOjE0IEFNLCBMdWNhIE1hcnRpbmkg
PGxtYXJ0aW5pQGNpc2NvLmNvbTxtYWlsdG86bG1hcnRpbmlAY2lzY28uY29tPj4gd3JvdGU6DQpH
cmVnLA0KDQpZb3UgYXJlIGNvcnJlY3QgLCB0aGUgcHJvcG9zZWQgdXBkYXRlIGRvZXMgbm90IHBy
b3Bvc2UgYW55IGNoYW5nZXMgdG8gVkNDVi4NCkhvd2V2ZXIgdGhlIHByb2JsZW0gd2l0aCB2Y2N2
IGlzIG5vdCBhcyBzaW1wbGUgYXMgdG8gYXNrIGZvciBhIG5ldyBjb2RlIHBvaW50IGZyb20gSUFO
QS4NCkdpdmVuIHRoZSBnb29kIGFtb3VudCBvZiBkaXNjdXNzaW9uIG9uIHRoaXMgcG9pbnQsIHdl
IHNob3VsZCBwcm9iYWJseSBoYXZlIGEgZGlzY3Vzc2lvbiBpbiBCZWlqaW5nLg0KDQpMdWNhDQoN
Cg0KDQpPbiAxMC8yOS8yMDEwIDA1OjA3IFBNLCBHcmVnIE1pcnNreSB3cm90ZToNCg0KRGVhciBB
dXRob3JzLA0KSSB0aGluayB0aGF0IHByb3Bvc2VkIHVwZGF0ZSBvZiB0aGUgU2VjdGlvbiA0LjIu
IFJGQyA1NTg2IG1ha2VzIGl0IHBvc3NpYmxlDQp0byB1c2UgR0FMIG9uIE1QTFMtVFAgUFcgdGhh
dCB1c2VzIENvbnRyb2wgV29yZC4gSSBjb25zaWRlciBpdCB0byBiZQ0KY29uZmxpY3QgYmV0d2Vl
biBQVyBWQ0NWIENDIHR5cGVzIGJlY2F1c2UgdXNlIG9mIEdBTCBpcyBub3QgbmVnb3RpYXRlZA0K
dGhyb3VnaCBQVyBWQ0NWIG5lZ290aWF0aW9uLiBUbyBhdm9pZCBzdWNoIHNpdHVhdGlvbiBJIHBy
b3Bvc2U6DQoNCiAgIC0gaW4gU2VjdGlvbiA1IHJlcXVlc3QgSUFOQSB0byBhc3NpZ24gbmV3IEND
IFR5cGUgIk1QTFMgR2VuZXJpYw0KICAgQXNzb2NpYXRlZCBDaGFubmVsIExhYmVsIg0KICAgLSBh
c3NpZ24gcHJlY2VkZW5jZSB0byBuZXcgQ0MgVHlwZSB0aGF0IGFmZmVjdHMgU2VjdGlvbiA3IFJG
QyA1MDg1DQoNClJlZ2FyZHMsDQpHcmVnDQoNCg0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fDQptcGxzIG1haWxpbmcgbGlzdA0KbXBsc0BpZXRmLm9y
ZzxtYWlsdG86bXBsc0BpZXRmLm9yZz4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vbXBscw0KDQoNCg0K

--_000_2C2F1EBA8050E74EA81502D5740B4BD69419A002F9SJEXCHCCR02co_
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: base64

PGh0bWwgZGlyPSJsdHIiPjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBj
b250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9aXNvLTg4NTktMSI+DQo8bWV0YSBjb250ZW50PSJN
U0hUTUwgNi4wMC42MDAwLjE3MDYzIiBuYW1lPSJHRU5FUkFUT1IiPg0KPHN0eWxlIGlkPSJvd2FU
ZW1wRWRpdFN0eWxlIj48L3N0eWxlPjxzdHlsZSB0aXRsZT0ib3dhUGFyYVN0eWxlIj48IS0tUCB7
DQoJTUFSR0lOLVRPUDogMHB4OyBNQVJHSU4tQk9UVE9NOiAwcHgNCn0NCi0tPjwvc3R5bGU+DQo8
L2hlYWQ+DQo8Ym9keSBvY3NpPSJ4Ij48ZGl2Pjxmb250IHNpemU9MiBjb2xvcj1uYXZ5IGZhY2U9
QXJpYWw+DQpJIGFsc28gYWdyZWUgd2l0aCBTYXNoYS4gQ3JlYXRpbmcgYSBWQ0NWIHR5cGUgNCBp
cyBwcm9ibGVtYXRpYywgYWxtb3N0IG5vIGhhcmR3YXJlIGV4aXN0IGZvciBpdCBhbmQgY2F1c2Vz
IGludGVyd29ya2luZyBpc3N1ZXMuIFNpZ25hbGluZyBWQ0NWIG5lZWRzIHRvIGNoYW5nZSBhcyB3
ZWxsLjxicj48YnI+VGh4PGJyPlNoYWhyYW0gPC9mb250PjwvZGl2Pg0KPGJyPjxkaXY+PGhyIHNp
emU9MiB3aWR0aD0iMTAwJSIgYWxpZ249Y2VudGVyIHRhYmluZGV4PS0xPg0KPGZvbnQgZmFjZT1U
YWhvbWEgc2l6ZT0yPg0KPGI+RnJvbTwvYj46IHB3ZTMtYm91bmNlc0BpZXRmLm9yZyAmbHQ7cHdl
My1ib3VuY2VzQGlldGYub3JnJmd0Ow08YnI+PGI+VG88L2I+OiBHcmVnIE1pcnNreSAmbHQ7Z3Jl
Z2ltaXJza3lAZ21haWwuY29tJmd0Ow08YnI+PGI+Q2M8L2I+OiBSb2JlcnQgUmVubmlzb24gJmx0
O1JvYmVydC5SZW5uaXNvbkBlY2l0ZWxlLmNvbSZndDs7IG1wbHNAaWV0Zi5vcmcgJmx0O21wbHNA
aWV0Zi5vcmcmZ3Q7OyBMdWNhIE1hcnRpbmkgJmx0O2xtYXJ0aW5pQGNpc2NvLmNvbSZndDs7IG1w
bHMtdHBAaWV0Zi5vcmcgJmx0O21wbHMtdHBAaWV0Zi5vcmcmZ3Q7OyBNaXNoYWVsIFdleGxlciAm
bHQ7TWlzaGFlbC5XZXhsZXJAZWNpdGVsZS5jb20mZ3Q7OyBsaWhhbkBjaGluYW1vYmlsZS5jb20g
Jmx0O2xpaGFuQGNoaW5hbW9iaWxlLmNvbSZndDs7IHB3ZTMgJmx0O3B3ZTNAaWV0Zi5vcmcmZ3Q7
OyBSb3RlbUBjb3JlMy5hbXNsLmNvbSAmbHQ7Um90ZW1AY29yZTMuYW1zbC5jb20mZ3Q7OyBIVUFO
R0Bjb3JlMy5hbXNsLmNvbSAmbHQ7SFVBTkdAY29yZTMuYW1zbC5jb20mZ3Q7OyBGZW5nIEYgJmx0
O0ZlbmcuZi5IdWFuZ0BhbGNhdGVsLXNiZWxsLmNvbS5jbiZndDs7IENvaGVuICZsdDtSb3RlbS5D
b2hlbkBlY2l0ZWxlLmNvbSZndDsNPGJyPjxiPlNlbnQ8L2I+OiBUaHUgRmViIDE3IDIzOjA1OjE5
IDIwMTE8YnI+PGI+U3ViamVjdDwvYj46IFJlOiBbUFdFM10gW21wbHMtdHBdIFdHIExDIGRyYWZ0
LWxtLXB3ZTMtbXBscy10cC1nYWwtaW4tcHctMDAudHh0DTxicj48L2ZvbnQ+PGJyPjwvZGl2Pg0K
DQo8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE2cHg7IENPTE9SOiAjMDAwMDAwOyBESVJFQ1RJT046
IGx0cjsgRk9OVC1GQU1JTFk6IFRpbWVzIE5ldyBSb21hbiI+DQo8ZGl2PkdyZWcsIGFuZCBhbGws
PC9kaXY+DQo8ZGl2Pjxmb250IGZhY2U9InRpbWVzIG5ldyByb21hbiI+SSBjb25jdXIgd2l0aCBH
cmVnLjwvZm9udD48L2Rpdj4NCjxkaXY+PGZvbnQgZmFjZT0idGltZXMgbmV3IHJvbWFuIj5Vc2lu
ZyBHQUwgd2l0aCBQV3MgaXMgaGlnaGx5IHByb2JsZW1hdGljLCBhbmQgYWxsIHRoZSByZWxhdGVk
IGlzc3VlcyAocmFpc2VkIGR1cmluZyB0aGUgcG9sbCBvbiBhY2NlcHRpbmcgdGhpcyBkcmFmdCBh
cyBhIFdHIGl0ZW0pIGhhdmUgbm90LCBBRkFJSywgYmVlbiByZXNvbHZlZC48L2ZvbnQ+PC9kaXY+
DQo8ZGl2Pjxmb250IGZhY2U9InRpbWVzIG5ldyByb21hbiI+PC9mb250PiZuYnNwOzwvZGl2Pg0K
PGRpdj48Zm9udCBmYWNlPSJ0aW1lcyBuZXcgcm9tYW4iPlJlZ2FyZHMsPC9mb250PjwvZGl2Pg0K
PGRpdj48Zm9udCBmYWNlPSJ0aW1lcyBuZXcgcm9tYW4iPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyBTYXNoYTwvZm9udD48L2Rpdj4NCjxkaXYgZGlyPSJsdHIiPjxmb250IGZhY2U9IlRpbWVzIE5l
dyBSb21hbiIgY29sb3I9IiMwMDAwMDAiIHNpemU9IjMiPjwvZm9udD4mbmJzcDs8L2Rpdj4NCjxk
aXYgaWQ9ImRpdlJwRjYyODA5NSIgc3R5bGU9IkRJUkVDVElPTjogbHRyIj4NCjxociB0YWJpbmRl
eD0iLTEiPg0KPGZvbnQgZmFjZT0iVGFob21hIiBjb2xvcj0iIzAwMDAwMCIgc2l6ZT0iMiI+PGI+
RnJvbTo8L2I+IG1wbHMtdHAtYm91bmNlc0BpZXRmLm9yZyBbbXBscy10cC1ib3VuY2VzQGlldGYu
b3JnXSBPbiBCZWhhbGYgT2YgR3JlZyBNaXJza3kgW2dyZWdpbWlyc2t5QGdtYWlsLmNvbV08YnI+
DQo8Yj5TZW50OjwvYj4gRnJpZGF5LCBGZWJydWFyeSAxOCwgMjAxMSA4OjQ3IEFNPGJyPg0KPGI+
VG86PC9iPiBMdWNhIE1hcnRpbmk8YnI+DQo8Yj5DYzo8L2I+IG1wbHNAaWV0Zi5vcmc7IG1wbHMt
dHBAaWV0Zi5vcmc7IGxpaGFuQGNoaW5hbW9iaWxlLmNvbTsgcHdlMzsgSFVBTkcgRmVuZyBGPGJy
Pg0KPGI+U3ViamVjdDo8L2I+IFttcGxzLXRwXSBXRyBMQyBkcmFmdC1sbS1wd2UzLW1wbHMtdHAt
Z2FsLWluLXB3LTAwLnR4dDxicj4NCjwvZm9udD48YnI+DQo8L2Rpdj4NCjxkaXY+PC9kaXY+DQo8
ZGl2PkRlYXIgQXV0aG9ycyBhbmQgQWxsLDxicj4NCnByaW9yIHRvIHRoZSBtZWV0aW5nIGluIEJl
amluZyBhbmQgYWNjZXB0YW5jZSBvZiB0aGlzIHByb3Bvc2FsIGFzIFdHIGRvY3VtZW50IEx1Y2Eg
YW5kIEkgYWdyZWVkIHRoYXQgdXNlIG9mIEdBTCB3aXRoIFBXIFZDQ1YgcHJlc2VudHMgYSBwcm9i
bGVtLjxicj4NCkkgd2FzIG5vdCBhdHRlbmRpbmcgdGhlIElFVEYtNzksIG5vciBJIGZvdW5kIGRp
c2N1c3Npb24gb2YgdGhpcyBpc3N1ZSBpbiB0aGUgbWludXRlcy4gSSB0aGluayB0aGF0IHRoaXMg
aXNzdWUgc2hvdWxkIGJlIHNwZWNpZmllZCwgZXhwbGFpbmVkLiBJbiBteSB2aWV3LCB0aGlzIGRv
Y3VtZW50IHVwZGF0ZXMgbm90IG9ubHkgUkZDIDU1ODY8YnI+DQpidXQgUkZDIDUwODUgdG9vLjxi
cj4NCjxicj4NClJlZ2FyZHMsPGJyPg0KR3JlZzxicj4NCjxicj4NCkNvbW1lbnQgdG8gZHJhZnQt
bG0tcHdlMy1tcGxzLXRwLWdhbC1pbi1wdy0wMC50eHQ8YnI+DQo8YnI+DQo8ZGl2IGNsYXNzPSJn
bWFpbF9xdW90ZSI+T24gU2F0LCBPY3QgMzAsIDIwMTAgYXQgMTA6MTQgQU0sIEx1Y2EgTWFydGlu
aSA8c3BhbiBkaXI9Imx0ciI+DQombHQ7PGEgaHJlZj0ibWFpbHRvOmxtYXJ0aW5pQGNpc2NvLmNv
bSI+bG1hcnRpbmlAY2lzY28uY29tPC9hPiZndDs8L3NwYW4+IHdyb3RlOjxicj4NCjxibG9ja3F1
b3RlIGNsYXNzPSJnbWFpbF9xdW90ZSIgc3R5bGU9IlBBRERJTkctTEVGVDogMWV4OyBNQVJHSU46
IDBwdCAwcHQgMHB0IDAuOGV4OyBCT1JERVItTEVGVDogcmdiKDIwNCwyMDQsMjA0KSAxcHggc29s
aWQiPg0KPGRpdiBiZ2NvbG9yPSIjZmZmZmZmIj5HcmVnLDxicj4NCjxicj4NCllvdSBhcmUgY29y
cmVjdCAsIHRoZSBwcm9wb3NlZCB1cGRhdGUgZG9lcyBub3QgcHJvcG9zZSBhbnkgY2hhbmdlcyB0
byBWQ0NWLjxicj4NCkhvd2V2ZXIgdGhlIHByb2JsZW0gd2l0aCB2Y2N2IGlzIG5vdCBhcyBzaW1w
bGUgYXMgdG8gYXNrIGZvciBhIG5ldyBjb2RlIHBvaW50IGZyb20gSUFOQS48YnI+DQpHaXZlbiB0
aGUgZ29vZCBhbW91bnQgb2YgZGlzY3Vzc2lvbiBvbiB0aGlzIHBvaW50LCB3ZSBzaG91bGQgcHJv
YmFibHkgaGF2ZSBhIGRpc2N1c3Npb24gaW4gQmVpamluZy48YnI+DQo8YnI+DQpMdWNhDQo8ZGl2
Pg0KPGRpdj48L2Rpdj4NCjxkaXYgY2xhc3M9Img1Ij48YnI+DQo8YnI+DQo8YnI+DQpPbiAxMC8y
OS8yMDEwIDA1OjA3IFBNLCBHcmVnIE1pcnNreSB3cm90ZTogPC9kaXY+DQo8L2Rpdj4NCjxibG9j
a3F1b3RlIHR5cGU9ImNpdGUiPg0KPGRpdj4NCjxkaXY+PC9kaXY+DQo8ZGl2IGNsYXNzPSJoNSI+
DQo8cHJlPkRlYXIgQXV0aG9ycywNCkkgdGhpbmsgdGhhdCBwcm9wb3NlZCB1cGRhdGUgb2YgdGhl
IFNlY3Rpb24gNC4yLiBSRkMgNTU4NiBtYWtlcyBpdCBwb3NzaWJsZQ0KdG8gdXNlIEdBTCBvbiBN
UExTLVRQIFBXIHRoYXQgdXNlcyBDb250cm9sIFdvcmQuIEkgY29uc2lkZXIgaXQgdG8gYmUNCmNv
bmZsaWN0IGJldHdlZW4gUFcgVkNDViBDQyB0eXBlcyBiZWNhdXNlIHVzZSBvZiBHQUwgaXMgbm90
IG5lZ290aWF0ZWQNCnRocm91Z2ggUFcgVkNDViBuZWdvdGlhdGlvbi4gVG8gYXZvaWQgc3VjaCBz
aXR1YXRpb24gSSBwcm9wb3NlOg0KDQogICAtIGluIFNlY3Rpb24gNSByZXF1ZXN0IElBTkEgdG8g
YXNzaWduIG5ldyBDQyBUeXBlICZxdW90O01QTFMgR2VuZXJpYw0KICAgQXNzb2NpYXRlZCBDaGFu
bmVsIExhYmVsJnF1b3Q7DQogICAtIGFzc2lnbiBwcmVjZWRlbmNlIHRvIG5ldyBDQyBUeXBlIHRo
YXQgYWZmZWN0cyBTZWN0aW9uIDcgUkZDIDUwODUNCg0KUmVnYXJkcywNCkdyZWcNCg0KPC9wcmU+
DQo8L2Rpdj4NCjwvZGl2Pg0KPHByZT48ZmllbGRzZXQ+PC9maWVsZHNldD4NCl9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQptcGxzIG1haWxpbmcgbGlzdA0K
PGEgaHJlZj0ibWFpbHRvOm1wbHNAaWV0Zi5vcmciPm1wbHNAaWV0Zi5vcmc8L2E+DQo8YSBocmVm
PSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21wbHMiIHRhcmdldD0iX2Js
YW5rIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21wbHM8L2E+DQo8L3By
ZT4NCjwvYmxvY2txdW90ZT4NCjxicj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8
YnI+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_2C2F1EBA8050E74EA81502D5740B4BD69419A002F9SJEXCHCCR02co_--


From gregimirsky@gmail.com  Fri Feb 18 10:14:55 2011
Return-Path: <gregimirsky@gmail.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 247FB3A6D6A; Fri, 18 Feb 2011 10:14:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.848
X-Spam-Level: 
X-Spam-Status: No, score=-2.848 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 Jk3U5VHbczmr; Fri, 18 Feb 2011 10:14:54 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id 9D8E33A6D48; Fri, 18 Feb 2011 10:14:53 -0800 (PST)
Received: by vxi40 with SMTP id 40so2334276vxi.31 for <multiple recipients>; Fri, 18 Feb 2011 10:15:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=eFhbxbVkVd9RRDxruN1eHxWuzfkY9LqBZ17udURWnxI=; b=Eyw3njNi9WkoxdXq6rv6DfBqfhylFf3/LoS1KEOtAqtvDV3cdcJgDr78E5VlUpM2P1 Ylbd7TKcDv9u49VmyNRq3zkMppKwXJMvuDcdzEdE5foR04unDz+8uOzPCgWTGZAS0Hqq 1Km/WT6PytuY2a1FiaKrBTZrp2ugj2QmeOniM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=C8KfCMqjLbrj7/7LT+ldM0AolurQ3cZ8lRDVT08f8H962E9+r3oXco5QaMOeU+QzDr HMsTbIy+Nw/96Lz8lElBzultAuw9qltnHYe8oyzo+N31KBtGH4+OT6cKJl2lBPgrReMK FMZdb8V/POafL1EFBx6cwms/89yqOSaVHgecI=
MIME-Version: 1.0
Received: by 10.52.164.166 with SMTP id yr6mr1831510vdb.245.1298052926692; Fri, 18 Feb 2011 10:15:26 -0800 (PST)
Received: by 10.52.165.9 with HTTP; Fri, 18 Feb 2011 10:15:26 -0800 (PST)
In-Reply-To: <4D5E9442.3030101@cisco.com>
References: <AANLkTikcnCa5DQZyGgD_QawiQ_57KKA4BXQm7iRRayKA@mail.gmail.com> <4D5E9442.3030101@cisco.com>
Date: Fri, 18 Feb 2011 10:15:26 -0800
Message-ID: <AANLkTikmTjBZgtxNQRrAbBVQEmEKFAvyvAapk7Qbdf9O@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: Luca Martini <lmartini@cisco.com>
Content-Type: multipart/alternative; boundary=bcaec53f9359985e7f049c927f19
Cc: lihan@chinamobile.com, mpls@ietf.org, pwe3 <pwe3@ietf.org>, HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>, mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2011 18:14:55 -0000

--bcaec53f9359985e7f049c927f19
Content-Type: text/plain; charset=ISO-8859-1

Dear Luca,
I see at least two issues:

   - use of GAL for PW, in my view, is another VCCV CC type that has to be
   negotiated as described in RFC 5085.
   - use of GAL creates ambiguous situation when PW CW is used. The benefit
   from extending GAL in PW, as I see, is for PWs that are not required to use
   PW CW. That might be a good enough reason to update RFC 5586 as proposed in
   the document but we must address use cases of GAL in PWs that require
   presence PW CW. If we prohibit or even discourage use of GAL for these PWs
   that have PW VCCV as native Associated Channel, then architecture of ACh for
   MPLS-TP PW not simplified as result of adopting the proposal.

Regards,
Greg

On Fri, Feb 18, 2011 at 7:46 AM, Luca Martini <lmartini@cisco.com> wrote:

> Greg,
>
> Sorry, but I do not remember the point you mention.
> Can you explain again here ?
> Thanks.
> Luca
>
>
> On 02/17/11 23:47, Greg Mirsky wrote:
> > Dear Authors and All,
> > prior to the meeting in Bejing and acceptance of this proposal as WG
> > document Luca and I agreed that use of GAL with PW VCCV presents a
> > problem.
> > I was not attending the IETF-79, nor I found discussion of this issue
> > in the minutes. I think that this issue should be specified,
> > explained. In my view, this document updates not only RFC 5586
> > but RFC 5085 too.
> >
> > Regards,
> > Greg
> >
> > Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
> >
> > On Sat, Oct 30, 2010 at 10:14 AM, Luca Martini <lmartini@cisco.com
> > <mailto:lmartini@cisco.com>> wrote:
> >
> >     Greg,
> >
> >     You are correct , the proposed update does not propose any changes
> >     to VCCV.
> >     However the problem with vccv is not as simple as to ask for a new
> >     code point from IANA.
> >     Given the good amount of discussion on this point, we should
> >     probably have a discussion in Beijing.
> >
> >     Luca
> >
> >
> >
> >     On 10/29/2010 05:07 PM, Greg Mirsky wrote:
> >>     Dear Authors,
> >>     I think that proposed update of the Section 4.2. RFC 5586 makes it
> possible
> >>     to use GAL on MPLS-TP PW that uses Control Word. I consider it to be
> >>     conflict between PW VCCV CC types because use of GAL is not
> negotiated
> >>     through PW VCCV negotiation. To avoid such situation I propose:
> >>
> >>        - in Section 5 request IANA to assign new CC Type "MPLS Generic
> >>        Associated Channel Label"
> >>        - assign precedence to new CC Type that affects Section 7 RFC
> 5085
> >>
> >>     Regards,
> >>     Greg
> >>
> >>
> >>
> >>     _______________________________________________
> >>     mpls mailing list
> >>     mpls@ietf.org <mailto:mpls@ietf.org>
> >>     https://www.ietf.org/mailman/listinfo/mpls
> >
> >
> >
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls
>
>

--bcaec53f9359985e7f049c927f19
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear Luca,<br>I see at least two issues:<br><ul><li>use of GAL for PW, in m=
y view, is another VCCV CC type that has to be negotiated as described in R=
FC 5085.</li><li>use of GAL creates ambiguous situation when PW CW is used.=
 The benefit from extending GAL in PW, as I see, is for PWs that are not re=
quired to use PW CW. That might be a good enough reason to update RFC 5586 =
as proposed in the document but we must address use cases of GAL in PWs tha=
t require presence PW CW. If we prohibit or even discourage use of GAL for =
these PWs that have PW VCCV as native Associated Channel, then architecture=
 of ACh for MPLS-TP PW not simplified as result of adopting the proposal.</=
li>
</ul>Regards,<br>Greg<br><br><div class=3D"gmail_quote">On Fri, Feb 18, 201=
1 at 7:46 AM, Luca Martini <span dir=3D"ltr">&lt;<a href=3D"mailto:lmartini=
@cisco.com">lmartini@cisco.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204, 204); margin=
: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Greg,<br>
<br>
Sorry, but I do not remember the point you mention.<br>
Can you explain again here ?<br>
Thanks.<br>
Luca<br>
<div class=3D"im"><br>
<br>
On 02/17/11 23:47, Greg Mirsky wrote:<br>
&gt; Dear Authors and All,<br>
&gt; prior to the meeting in Bejing and acceptance of this proposal as WG<b=
r>
&gt; document Luca and I agreed that use of GAL with PW VCCV presents a<br>
&gt; problem.<br>
&gt; I was not attending the IETF-79, nor I found discussion of this issue<=
br>
&gt; in the minutes. I think that this issue should be specified,<br>
&gt; explained. In my view, this document updates not only RFC 5586<br>
&gt; but RFC 5085 too.<br>
&gt;<br>
&gt; Regards,<br>
&gt; Greg<br>
&gt;<br>
&gt; Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt<br>
&gt;<br>
&gt; On Sat, Oct 30, 2010 at 10:14 AM, Luca Martini &lt;<a href=3D"mailto:l=
martini@cisco.com">lmartini@cisco.com</a><br>
</div><div class=3D"im">&gt; &lt;mailto:<a href=3D"mailto:lmartini@cisco.co=
m">lmartini@cisco.com</a>&gt;&gt; wrote:<br>
&gt;<br>
&gt; =A0 =A0 Greg,<br>
&gt;<br>
&gt; =A0 =A0 You are correct , the proposed update does not propose any cha=
nges<br>
&gt; =A0 =A0 to VCCV.<br>
&gt; =A0 =A0 However the problem with vccv is not as simple as to ask for a=
 new<br>
&gt; =A0 =A0 code point from IANA.<br>
&gt; =A0 =A0 Given the good amount of discussion on this point, we should<b=
r>
&gt; =A0 =A0 probably have a discussion in Beijing.<br>
&gt;<br>
&gt; =A0 =A0 Luca<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 On 10/29/2010 05:07 PM, Greg Mirsky wrote:<br>
&gt;&gt; =A0 =A0 Dear Authors,<br>
&gt;&gt; =A0 =A0 I think that proposed update of the Section 4.2. RFC 5586 =
makes it possible<br>
&gt;&gt; =A0 =A0 to use GAL on MPLS-TP PW that uses Control Word. I conside=
r it to be<br>
&gt;&gt; =A0 =A0 conflict between PW VCCV CC types because use of GAL is no=
t negotiated<br>
&gt;&gt; =A0 =A0 through PW VCCV negotiation. To avoid such situation I pro=
pose:<br>
&gt;&gt;<br>
&gt;&gt; =A0 =A0 =A0 =A0- in Section 5 request IANA to assign new CC Type &=
quot;MPLS Generic<br>
&gt;&gt; =A0 =A0 =A0 =A0Associated Channel Label&quot;<br>
&gt;&gt; =A0 =A0 =A0 =A0- assign precedence to new CC Type that affects Sec=
tion 7 RFC 5085<br>
&gt;&gt;<br>
&gt;&gt; =A0 =A0 Regards,<br>
&gt;&gt; =A0 =A0 Greg<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; =A0 =A0 _______________________________________________<br>
&gt;&gt; =A0 =A0 mpls mailing list<br>
</div>&gt;&gt; =A0 =A0 <a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a> &=
lt;mailto:<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>&gt;<br>
<div><div></div><div class=3D"h5">&gt;&gt; =A0 =A0 <a href=3D"https://www.i=
etf.org/mailman/listinfo/mpls" target=3D"_blank">https://www.ietf.org/mailm=
an/listinfo/mpls</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; mpls mailing list<br>
&gt; <a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/mpls</a><br>
<br>
</div></div></blockquote></div><br>

--bcaec53f9359985e7f049c927f19--

From takeda.tomonori@lab.ntt.co.jp  Sun Feb 20 22:53:04 2011
Return-Path: <takeda.tomonori@lab.ntt.co.jp>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B1F7F3A6F96; Sun, 20 Feb 2011 22:53:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.89
X-Spam-Level: 
X-Spam-Status: No, score=-98.89 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_13=0.6, J_CHICKENPOX_21=0.6, USER_IN_WHITELIST=-100]
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 jUz2ls4kJ2uo; Sun, 20 Feb 2011 22:53:02 -0800 (PST)
Received: from tama50.ecl.ntt.co.jp (tama50.ecl.ntt.co.jp [129.60.39.147]) by core3.amsl.com (Postfix) with ESMTP id ADCAA3A6F93; Sun, 20 Feb 2011 22:53:02 -0800 (PST)
Received: from mfs6.rdh.ecl.ntt.co.jp (mfs6.rdh.ecl.ntt.co.jp [129.60.39.149]) by tama50.ecl.ntt.co.jp (8.14.4/8.14.4) with ESMTP id p1L6rgkq019415; Mon, 21 Feb 2011 15:53:42 +0900 (JST)
Received: from mfs6.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 289E665F1; Mon, 21 Feb 2011 15:53:42 +0900 (JST)
Received: from imail2.m.ecl.ntt.co.jp (imail2.m.ecl.ntt.co.jp [129.60.5.247]) by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 1003A65EB; Mon, 21 Feb 2011 15:53:42 +0900 (JST)
Received: from [127.0.0.1] ([129.60.80.55]) by imail2.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id p1L6reHU009271;  Mon, 21 Feb 2011 15:53:42 +0900
Message-ID: <4D620BDD.7000504@lab.ntt.co.jp>
Date: Mon, 21 Feb 2011 15:53:17 +0900
From: Tomonori TAKEDA <takeda.tomonori@lab.ntt.co.jp>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: ccamp@ietf.org, pce@ietf.org, mpls@ietf.org, mpls-tp@ietf.org
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: iPOP2011-tpc-sec@pilab.jp
Subject: [mpls-tp] iPOP2011 Call for Presentation (corrected version)
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Feb 2011 06:53:05 -0000

(Apologies if you received multiple copies of this message.)

Dear CCAMP, PCE, MPLS and MPLS-TP subscribers,

The email sent on Feb. 10th titled "iPOP2011 Call for Presentation"
states wrong dates. It should be year "2011", not "2010".

Please find the corrected CFP as follows.

Sorry for your inconvenience.

Tomonori Takeda

-------------------------------------------------------------------
                     Call for Presentation

7th  International Conference on IP + Optical Network (iPOP 2011)
                         June 2-3, 2011
               NEC Tamagawa Plant, Kanagawa, Japan
                  http://www.pilab.jp/ipop2011/

The conference is intended to share among the industry and the academia,
the knowledge, new findings, and experience on the state-of-the art of
IP and optical networking technologies. It features technical sessions
and planned exhibitions. The opportunity to participate is open to all.

Important Dates:
Submission deadline of one-page abstract: February 25, 2011
Notification of acceptance: April 4, 2011
Submission deadline of final presentation slides: April 22, 2011

The Technical Program Committee for iPOP 2011 is soliciting presentation
proposals for this conference. Protocol design, experiment, theory,
implementation, and operational experiences are solicited.
The topics of the conference will include but not limited to the following:

* GMPLS/ASON technologies
* GMPLS Network management, OA&M
* Multi-layer network (MLN) / Multi-region network (MRN)
* Path Computation Element (PCE), Traffic engineering
* Inter-area/Inter-AS network
* L1VPN, Bandwidth on Demand, and Photonic Grid
* Wavelength Switched Optical Networks  (WSON), Routing wavelength
  assignment, Impairment management
* GMPLS-controlled Ethernet Label Switching  (GELS) and related Ethernet
  transport technologies
* Carrier Ethernet and MPLS-TP
* Photonic Network for NxGN and NwGN
* Application with high-bandwidth demand
* Testbed, field trial

If you wish to submit a topic for consideration, please send an Extended
Abstracts of a 400 words and a maximum of 1 page, including figures and
diagrams, speaker$B!G(Bs name, affiliation, and contact information
to the Technical Program Committee at ipop2011-CFP@pilab.jp.
Please see http://www.pilab.jp/ipop2011/ for more details.
-----------------------------------------------------------------------


From binnyjeshan@gmail.com  Mon Feb 21 00:59:23 2011
Return-Path: <binnyjeshan@gmail.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 91E443A6FBE for <mpls-tp@core3.amsl.com>; Mon, 21 Feb 2011 00:59:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 CEL2SXVyaduf for <mpls-tp@core3.amsl.com>; Mon, 21 Feb 2011 00:59:22 -0800 (PST)
Received: from mail-vw0-f42.google.com (mail-vw0-f42.google.com [209.85.212.42]) by core3.amsl.com (Postfix) with ESMTP id B285F3A6F84 for <mpls-tp@ietf.org>; Mon, 21 Feb 2011 00:59:22 -0800 (PST)
Received: by vws10 with SMTP id 10so1356293vws.15 for <mpls-tp@ietf.org>; Mon, 21 Feb 2011 01:00:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=wnxExxU3O4l1QHfODlplBOTdEmbmlx74Pu2y6NFIR9k=; b=Nl1Avhy41Jul2gL8i8iL1JXujD8BB3sDXfGUkDMZruKwldXdQCYWP0ewHvHQlth00T IB3uRKbB/xD3gHYiqkqpRvhdsx9jmOUFkUWAvVmVjrc4EmZc5qCuv4uG5qovYLkOYaQV hbijwKBfWeDRV1CVuZHrSS84QjLCRTIaXEisw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=VXblKthtW6kioLTDSWGDROmAWGoBcS5rTwj28+7q9AhEH4+bSnEkD+OGCJZ2c2fo2f Ho/C8sxAzoSEDMxMpDZssIUrPDh2fvJWTOlo+qdp/EqXl/dgYOB0jPOIeOU7n0dUElYE Y/rwAB4/HW/vH3u6aenVMIVsT9dlcPxrs9uU8=
MIME-Version: 1.0
Received: by 10.52.160.37 with SMTP id xh5mr1409164vdb.249.1298278803560; Mon, 21 Feb 2011 01:00:03 -0800 (PST)
Received: by 10.52.163.69 with HTTP; Mon, 21 Feb 2011 01:00:03 -0800 (PST)
Date: Mon, 21 Feb 2011 17:00:03 +0800
Message-ID: <AANLkTi=TT4BpjPTrOuiHqm4N+YdEs-sY6i-5G=Kdh7sQ@mail.gmail.com>
From: binny jeshan <binnyjeshan@gmail.com>
To: mpls-tp@ietf.org
Content-Type: multipart/alternative; boundary=bcaec53f944fe7d8e1049cc7166a
Subject: [mpls-tp] Question on MPLS-TP OAM UMC code in draft-ietf-mpls-tp-identifiers-03
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Feb 2011 08:59:23 -0000

--bcaec53f944fe7d8e1049cc7166a
Content-Type: text/plain; charset=ISO-8859-1

Hello draft authors,

I have a question for some clarity regarding UMC code in  section 7.1.1 of
http://tools.ietf.org/html/draft-ietf-mpls-tp-identifiers-03 .

It says,

 In this case, the MEG_ID is a string of up to thirteen characters,
   each character being either alphabetic (i.e.  A-Z) or numeric (i.e.
   0-9) characters.  It consists of two subfields: the ICC (as defined
   in section 3) followed by a unique MEG code (UMC).  The UMC MUST be
   unique within the organization identified by the ICC.

As i understand from the above, UMC code should not be configurable for each
MEG created for a path, but instead all MEG for an operator should use UMC
allocated by ITU.

Please correct me if i am anywhere wrong in my understanding. Please let me
know if your opinion is different.

Thanks,
Binny.

--bcaec53f944fe7d8e1049cc7166a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello draft authors,<div><br></div><div><div>I have a question for some cla=
rity regarding UMC code in=A0=A0section 7.1.1 of=A0<a href=3D"http://tools.=
ietf.org/html/draft-ietf-mpls-tp-identifiers-03" target=3D"_blank">http://t=
ools.ietf.org/html/draft-ietf-mpls-tp-identifiers-03</a>=A0.</div>
</div><div><br></div><div><div>It says,</div></div><div><br></div><div><div=
><font class=3D"Apple-style-span" color=3D"#660000">=A0</font><font class=
=3D"Apple-style-span" color=3D"#000099">In this case, the MEG_ID is a strin=
g of up to thirteen characters,</font></div>
<div><font class=3D"Apple-style-span" color=3D"#000099">=A0=A0 each charact=
er being either alphabetic (i.e. =A0A-Z) or numeric (i.e.</font></div><div>=
<font class=3D"Apple-style-span" color=3D"#000099">=A0=A0 0-9) characters. =
=A0It consists of two subfields: the ICC (as defined</font></div>
<div><font class=3D"Apple-style-span" color=3D"#000099">=A0=A0 in section 3=
) followed by a unique MEG code (UMC). =A0The UMC MUST be</font></div><div>=
<font class=3D"Apple-style-span" color=3D"#000099">=A0=A0 unique within the=
 organization identified by the ICC.</font></div>
</div><div><br></div><div><div>As i understand from the above, UMC code sho=
uld not be configurable for each MEG created for a path, but instead all ME=
G for an operator should use UMC allocated by ITU.</div><div><br></div>
<div>Please correct me if i am anywhere wrong in my understanding. Please l=
et me know if your opinion is different.</div><div><br></div><div>Thanks,</=
div><div>Binny.</div>
</div>

--bcaec53f944fe7d8e1049cc7166a--

From selvan619@gmail.com  Mon Feb 21 02:57:17 2011
Return-Path: <selvan619@gmail.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B0F613A706C for <mpls-tp@core3.amsl.com>; Mon, 21 Feb 2011 02:57:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 W1F8RyfohFoj for <mpls-tp@core3.amsl.com>; Mon, 21 Feb 2011 02:57:17 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id AE8183A6FCD for <mpls-tp@ietf.org>; Mon, 21 Feb 2011 02:57:16 -0800 (PST)
Received: by fxm15 with SMTP id 15so2322183fxm.31 for <mpls-tp@ietf.org>; Mon, 21 Feb 2011 02:57:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=rQdlXfW4vn5ZgeGfBC9q5Oz1oehScj4sJrZx41McX9s=; b=jEX7mqSVGdfPdCWoF5ra2RobUfCOKkMOV+mtxOs93LLtrB5ilQev2cCMGCKKcYWwud /ym7UOFKaDqpDjZa/jIkvhqVEJ8X/xvEZrw16pECmgvD8QsYnChEV3amTV4geJpqExUa m693YQIyovwrp95a0TMNtmiBfpkVR7q2Egw70=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=dl8L/VJd/TGzT/1rtGnycdXmNu2uixONGmR0tifP9cl6P6n1W7+CqeWgRB/CJrMnxi C9pEXvOkOuBSmdJ67Y/VfxBX2sR/syUYkvsRCojOgkX7vGHE4r+vzEKA9qKdpsWTZE+g Blqp3SkOyM1FziG9wC3Jj4OPy3/+qkBEkFGks=
MIME-Version: 1.0
Received: by 10.223.72.10 with SMTP id k10mr1642124faj.31.1298285877405; Mon, 21 Feb 2011 02:57:57 -0800 (PST)
Received: by 10.223.93.144 with HTTP; Mon, 21 Feb 2011 02:57:57 -0800 (PST)
Date: Mon, 21 Feb 2011 16:27:57 +0530
Message-ID: <AANLkTi=jbBHMT4BuOX7T7pz2obCXY5cmc=7_scNL7DWA@mail.gmail.com>
From: Selvan <selvan619@gmail.com>
To: mpls-tp@ietf.org
Content-Type: multipart/alternative; boundary=20cf3054a2858a29e2049cc8bcf1
Subject: [mpls-tp] Query regarding use of NodeId in case of IP aware MPLS-TP network
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Feb 2011 10:57:17 -0000

--20cf3054a2858a29e2049cc8bcf1
Content-Type: text/plain; charset=ISO-8859-1

Hello All,

Section 4 of the MPLS-TP identifiers draft-03 specifies:

   "Where IPv4 addresses are used, it is
   "convenient" to use the Node's IPv4 loopback address as the Node_ID,
   however the Node_ID does not need to have any association with the
   IPv4 address space used in the operator's IGP or BGP.  Where IPv6
   addresses are used exclusively, a domain unique 32- bit value is
   assigned"

When IP based addressing is used isnt it a "MUST" to use Node-Id as
an IPv4 address (sayIPv4 loopback address or router id).
>From the above text it looks that in such a case NodeId need not
mandatorily be an IPv4 address.


Thanks
Selvan

--20cf3054a2858a29e2049cc8bcf1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Hello All,</div>
<div>=A0</div>
<div>Section 4 of the MPLS-TP identifiers draft-03 specifies:</div>
<p>=A0=A0 &quot;Where IPv4 addresses are used, it is<br>=A0=A0 &quot;conven=
ient&quot; to use the Node&#39;s IPv4 loopback address as the Node_ID,<br>=
=A0=A0 however the Node_ID does not need to have any association with the<b=
r>=A0=A0 IPv4 address space used in the operator&#39;s IGP or BGP.=A0 Where=
 IPv6<br>
=A0=A0 addresses are used exclusively, a domain unique 32- bit value is<br>=
=A0=A0 assigned&quot;</p>
<div><br>When IP based addressing is used isnt it a &quot;MUST&quot; to use=
 Node-Id as <br>an IPv4 address (sayIPv4 loopback address or router id). </=
div>
<div>From the above text it looks that in such a case NodeId need not </div=
>
<div>mandatorily be an IPv4 address.</div>
<div>=A0</div>
<div>=A0</div>
<div>Thanks</div>
<div>Selvan</div>

--20cf3054a2858a29e2049cc8bcf1--

From vivien.sterling@gmail.com  Tue Feb 22 01:26:13 2011
Return-Path: <vivien.sterling@gmail.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8537C3A677E; Tue, 22 Feb 2011 01:26:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 5EN9ynjaHZMJ; Tue, 22 Feb 2011 01:26:12 -0800 (PST)
Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by core3.amsl.com (Postfix) with ESMTP id 059923A65A6; Tue, 22 Feb 2011 01:26:11 -0800 (PST)
Received: by bwz12 with SMTP id 12so3447407bwz.27 for <multiple recipients>; Tue, 22 Feb 2011 01:26:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=G2etffR/qjnXH9giDS7En2AQmiLTc9K6/oRRgvusS9A=; b=q93fpiJtv8SUL/75YA2DPVOZ7qip1ryJPP5Zqd7Pm+3B5KJ9RRbbV4w2cXCdjVl0IB spI4EvVvUjZB1nD7rDldVcmT7uN7xM+0vjsMS8nF8GFTAQJVhueCB8uqqZB4s9ybZcHk DkYC/wMqvgOp6Me42G0nlb++fj5ffpyW/zfAw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=NEwfpDjkJtfcO935VWzXB9QfKMnfuJoAWX65BTNLK11VPWJqEYWk8i9jte8ZSOgY3N p7BaUxM8msAZULGTI2WwvXHgvXq8XxawGnWmruXj5ihCH5qrUJJSLn1oyp4/IEyTwbM2 q+/TAzZ25DONtG+l+GtmleL2+WDLX1hUs+Vvs=
MIME-Version: 1.0
Received: by 10.204.46.154 with SMTP id j26mr2195524bkf.134.1298366815068; Tue, 22 Feb 2011 01:26:55 -0800 (PST)
Received: by 10.204.32.82 with HTTP; Tue, 22 Feb 2011 01:26:55 -0800 (PST)
In-Reply-To: <C982D469.98F5%matthew.bocci@alcatel-lucent.com>
References: <C982D469.98F5%matthew.bocci@alcatel-lucent.com>
Date: Tue, 22 Feb 2011 10:26:55 +0100
Message-ID: <AANLkTimVTGia4-NKV_D3U7Mwoi+iE=X-CirZaydNXw6Z@mail.gmail.com>
From: Vivien Sterling <vivien.sterling@gmail.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Content-Type: multipart/alternative; boundary=0016e6d77f15cce387049cdb942e
Subject: Re: [mpls-tp] [PWE3] PWE3 WG LC on draft-ietf-pwe3-mpls-tp-gal-in-pw-00
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Feb 2011 09:26:13 -0000

--0016e6d77f15cce387049cdb942e
Content-Type: text/plain; charset=ISO-8859-1

Yes, support.

-- 
Cheers,
Vivien


On Thu, Feb 17, 2011 at 2:34 PM, Bocci, Matthew (Matthew) <
matthew.bocci@alcatel-lucent.com> wrote:

> This email begins a working group last call for
> draft-ietf-pwe3-mpls-tp-gal-in-pw-00.txt.
>
> This is a very short draft but since there are other MPLS-TP-related last
> calls going on concurrently, this will be a three-week last call.
>
> This WG LC will end of 11th March 2011.
>
> Please respond with any comments to the PWE3 mailing list.
>
> Regards,
>
> Matthew and Andy
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>

--0016e6d77f15cce387049cdb942e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Yes, support.</div>
<div>=A0</div>
<div>-- <br>Cheers,<br>Vivien<br><br><br></div>
<div class=3D"gmail_quote">On Thu, Feb 17, 2011 at 2:34 PM, Bocci, Matthew =
(Matthew) <span dir=3D"ltr">&lt;<a href=3D"mailto:matthew.bocci@alcatel-luc=
ent.com">matthew.bocci@alcatel-lucent.com</a>&gt;</span> wrote:<br>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">This email begins a working grou=
p last call for<br>draft-ietf-pwe3-mpls-tp-gal-in-pw-00.txt.<br><br>This is=
 a very short draft but since there are other MPLS-TP-related last<br>
calls going on concurrently, this will be a three-week last call.<br><br>Th=
is WG LC will end of 11th March 2011.<br><br>Please respond with any commen=
ts to the PWE3 mailing list.<br><br>Regards,<br><br>Matthew and Andy<br>
<br><br>_______________________________________________<br>pwe3 mailing lis=
t<br><a href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a><br><a href=3D"https=
://www.ietf.org/mailman/listinfo/pwe3" target=3D"_blank">https://www.ietf.o=
rg/mailman/listinfo/pwe3</a><br>
</blockquote></div><br>

--0016e6d77f15cce387049cdb942e--

From eosborne@cisco.com  Wed Feb 23 05:30:45 2011
Return-Path: <eosborne@cisco.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1D1B63A69F2; Wed, 23 Feb 2011 05:30:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 aJYXQCnFrRc5; Wed, 23 Feb 2011 05:30:43 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 722533A6A05; Wed, 23 Feb 2011 05:30:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eosborne@cisco.com; l=5507; q=dns/txt; s=iport; t=1298467890; x=1299677490; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=XnO2/s5i8i8Tjmfs6H+jxS/1hETcv50MrWkXh+6oNTI=; b=VPEB5IeAVZ5sZigjeHRQHtqHSU7fyb/MCxuetU6lYSofOR0qyJZdVXkB KbynFS9mQXXvsQJVFT/9cauMr9jg7maRABV4gCYJK5gRZRocZ8eX9V6FT nVb+sTjzVqhHQQr0Y6I+7/77NbV5nD68rOcexJXw73zTVh7Q4b04QJtI3 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AggBAJabZE2tJV2c/2dsb2JhbACXTY5Mc6A8m3EChVwEhQ2Fd4RT
X-IronPort-AV: E=Sophos;i="4.62,212,1297036800"; d="scan'208";a="218618650"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rtp-iport-1.cisco.com with ESMTP; 23 Feb 2011 13:31:29 +0000
Received: from xbh-rcd-301.cisco.com (xbh-rcd-301.cisco.com [72.163.63.8]) by rcdn-core-5.cisco.com (8.14.3/8.14.3) with ESMTP id p1NDVTDw006349;  Wed, 23 Feb 2011 13:31:29 GMT
Received: from xmb-rcd-202.cisco.com ([72.163.62.209]) by xbh-rcd-301.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 23 Feb 2011 07:31:29 -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
Date: Wed, 23 Feb 2011 07:31:15 -0600
Message-ID: <D29E470202D67745B61059870F433B54046CBF99@XMB-RCD-202.cisco.com>
In-Reply-To: A<76CD132C3ADEF848BD84D028D243C927AADCA1@szxeml508-mbx.china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls-tp] mpls wg last callondraft-ietf-mpls-tp-linear-protection-04
Thread-Index: AcvDl10fqyGU6Z/HTcaxkW43UzP3eAFXdT1gAUNLvlAAUdyZIAEE1HVQ
References: <4D4A9478.7050704@pi.nu> <021101cbc9c7$d7c8b140$875a13c0$@com> <D29E470202D67745B61059870F433B540461B15B@XMB-RCD-202.cisco.com> A<76CD132C3ADEF848BD84D028D243C927AADCA1@szxeml508-mbx.china.huawei.com>
From: "Eric Osborne (eosborne)" <eosborne@cisco.com>
To: "Jie Dong" <jie.dong@huawei.com>, <mpls-tp@ietf.org>, <mpls@ietf.org>
X-OriginalArrivalTime: 23 Feb 2011 13:31:29.0612 (UTC) FILETIME=[FA5EB0C0:01CBD35D]
Subject: Re: [mpls-tp] mpls wg last callondraft-ietf-mpls-tp-linear-protection-04
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Feb 2011 13:30:45 -0000

Hi Jie-

  Two comments inline with EO#

> > As Yaacov has mentioned, we would like the PSC to send messages
> > anyways in the chance that they may get through.  This is explicitly
> > noted in section 4.3.3.2:
>=20
> > ---
> > "When the domain is in unavailable state the PSC messages may not
get
> > through and therefore the protection is more dependent on the local
> > inputs rather than the remote messages (that may not be received)."
> > ----
> >
> > Is that sufficient, or do you think we need additional text to
> > reinforce this point?
>=20
> [Jie] I acknowledge this purpose, and my further comment would be the
same
> as to Yaacov: what about sending this message through working path if
it
> is known the transmitting direction of the protection path is in
failure?
> In this way the message is still sent on only one path.


EO#

  We discussed this early on when writing the draft, but decided against
it.  The concern was that providing multiple channels to send a message
on could open us up to complications and race conditions.  What happens,
for example, if you get different messages on the W and P SPMEs, for
example?  I see your point about only sending the message on one path,
but there are some types of failure where one end could think an SPME is
down and the other might not.  What happens if the rx node thinks the P
SPME is down (and thus expects messages on the W SPME), but the tx node
thinks the P SPME is up, and thus does not send anything on the W SPME?

  Bottom line is that there are always going to be ugly cases we can't
easily resolve, especially with the constraint that this protocol must
be fairly simple; the more dynamic it is, the longer it will take to
react to a failure, and in a protection protocol that's not something we
can afford.

> > > 8. Section 4.3.3, I go through this part fast, a general question
is:
> > are
> > > the PSC operations for 4 different protection types identical ? In
> > this
> > > section there is no description about operation of each specific
> > > protection type, but to my understanding, there may be different
> > > operations, e.g., for bidirectional 1:1 protection, the end point
> > > may
> > need
> > > to switch the sink selector and transmitting bridge simultaneously
> > > according to some input, but for unidirectional 1:1 the end point
> > > may
> > only
> > > need to switch the transmitting bridge OR the sink selector. And
the
> > PSC
> > > message sent may also be different for different protection types.
> > (Please
> > > correct me if there is anything wrong with this thought).
> >
> >
> > PSC is not, in my view, tightly coupled to the four protection
types.
> > That is to say, PSC is a tool that allows the device vendor and
> > network operator to build protection in an MPLS-TP network.  This
> > protection can be one of the four protection types you describe, but
> > PSC is merely a protocol to accomplish the end goal.  It may, for
> > example, be possible in the future to use PSC to build one or more
> > types of 1:n protection; when and if this is done, the message types
> > would likely remain the same as they are now.
> >
>=20
> I agree that PSC protocol can be used for all these protection types,
and
> may also be applicable to 1:n protection, but for each protection type
the
> state machine may be slightly different. The draft-tp-cc-cv-rdi also
works
> in this way. The message types are likely the same, but some fields in
the
> message may be different.

EO#  Can you be more specific?  Which field(s) would be different?  What
functionality would these fields provide that can't be provided with PSC
as defined in our draft?  As part of the PSC work we looked at other
protection protocols (you may notice a striking similarity to APS), and
I didn't see any type-specific redefinition of fields in those.



eric


>=20
>=20
> Best regards,
> Jie
>=20
> > >
> > > > -----Original Message-----
> > > > From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org]
> > > > On Behalf Of Loa Andersson
> > > > Sent: Thursday, February 03, 2011 7:42 PM
> > > > To: mpls-tp@ietf.org; mpls@ietf.org
> > > > Cc: ahmpls-tp@lists.itu.int
> > > > Subject: [mpls-tp] mpls wg last call on
> > > draft-ietf-mpls-tp-linear-protection-04
> > > >
> > > > Working Group,
> > > >
> > > > this is to start a four week working group last call on "MPLS-TP
> > > > Linear Protection" (draft-ietf-mpls-tp-linear-protection-04).
> > > >
> > > > Please send comments to the mpls-tp@ietf.org mailing list.
> > > >
> > > > This working group last call ends on February 28, 2011.
> > > >
> > > >
> > > >
> > > > Loa, George and Ross
> > > >
> > > > MPLS wg co-chairs
> > > >
> > > >
> > > >
> > > > --
> > > >
> > > >
> > > > Loa Andersson                         email:
> > > > loa.andersson@ericsson.com
> > > > Sr Strategy and Standards Manager            loa@pi.nu
> > > > Ericsson Inc                          phone: +46 10 717 52 13
> > > >                                               +46 767 72 92 13
> > > > _______________________________________________
> > > > mpls-tp mailing list
> > > > mpls-tp@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/mpls-tp
> > >
> > >
> > >
> > > _______________________________________________
> > > mpls-tp mailing list
> > > mpls-tp@ietf.org
> > > https://www.ietf.org/mailman/listinfo/mpls-tp

From takeda.tomonori@lab.ntt.co.jp  Wed Feb 23 20:39:00 2011
Return-Path: <takeda.tomonori@lab.ntt.co.jp>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D4FC3A6968; Wed, 23 Feb 2011 20:39:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.89
X-Spam-Level: 
X-Spam-Status: No, score=-98.89 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_13=0.6, J_CHICKENPOX_21=0.6, USER_IN_WHITELIST=-100]
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 lGGJG-92sssF; Wed, 23 Feb 2011 20:38:59 -0800 (PST)
Received: from tama500.ecl.ntt.co.jp (tama500.ecl.ntt.co.jp [129.60.39.148]) by core3.amsl.com (Postfix) with ESMTP id 53EAF3A6953; Wed, 23 Feb 2011 20:38:59 -0800 (PST)
Received: from mfs6.rdh.ecl.ntt.co.jp (mfs6.rdh.ecl.ntt.co.jp [129.60.39.149]) by tama500.ecl.ntt.co.jp (8.14.4/8.14.4) with ESMTP id p1O4dlWD007905; Thu, 24 Feb 2011 13:39:47 +0900 (JST)
Received: from mfs6.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 0B17065F9; Thu, 24 Feb 2011 13:39:47 +0900 (JST)
Received: from imail2.m.ecl.ntt.co.jp (imail2.m.ecl.ntt.co.jp [129.60.5.247]) by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 046BB65F1; Thu, 24 Feb 2011 13:39:47 +0900 (JST)
Received: from [127.0.0.1] ([129.60.80.55]) by imail2.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id p1O4dYV4001648;  Thu, 24 Feb 2011 13:39:46 +0900
Message-ID: <4D65E0F6.7050004@lab.ntt.co.jp>
Date: Thu, 24 Feb 2011 13:39:18 +0900
From: Tomonori TAKEDA <takeda.tomonori@lab.ntt.co.jp>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: ccamp@ietf.org, pce@ietf.org, mpls@ietf.org, mpls-tp@ietf.org
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: [mpls-tp] iPOP 2011 submission deadline extended to March 4
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Feb 2011 04:39:00 -0000

(Apologies if you receive multiple copies of this message.)

CCAMP, MPLS, MPLS-TP and PCE subscribers,

Please find below iPOP 2011 CFP with the extended deadline (March 4th).

Tomonori Takeda

-------------------------------------------------------------
                     Call for Presentation

7th  International Conference on IP + Optical Network (iPOP 2011)
                         June 2-3, 2011
               NEC Tamagawa Plant, Kanagawa, Japan
                  http://www.pilab.jp/ipop2011/

The conference is intended to share among the industry and the academia,
the knowledge, new findings, and experience on the state-of-the art of
IP and optical networking technologies. It features technical sessions
and planned exhibitions. The opportunity to participate is open to all.

Important Dates:
Submission deadline of one-page abstract: March 4, 2011 (extended)
Notification of acceptance: April 4, 2011
Submission deadline of final presentation slides: April 22, 2011

The Technical Program Committee for iPOP 2011 is soliciting presentation
proposals for this conference. Protocol design, experiment, theory,
implementation, and operational experiences are solicited.
The topics of the conference will include but not limited to the following:

* GMPLS/ASON technologies
* GMPLS Network management, OA&M
* Multi-layer network (MLN) / Multi-region network (MRN)
* Path Computation Element (PCE), Traffic engineering
* Inter-area/Inter-AS network
* L1VPN, Bandwidth on Demand, and Photonic Grid
* Wavelength Switched Optical Networks  (WSON), Routing wavelength
  assignment, Impairment management
* GMPLS-controlled Ethernet Label Switching  (GELS) and related Ethernet
  transport technologies
* Carrier Ethernet and MPLS-TP
* Photonic Network for NxGN and NwGN
* Application with high-bandwidth demand
* Testbed, field trial

If you wish to submit a topic for consideration, please send an Extended
Abstracts of a 400 words and a maximum of 1 page, including figures and
diagrams, speaker$B!G(Bs name, affiliation, and contact information
to the Technical Program Committee at ipop2011-CFP@pilab.jp.
Please see http://www.pilab.jp/ipop2011/ for more details.
----------------------------------------------------------------



From zhang.fei3@zte.com.cn  Sun Feb 27 17:33:12 2011
Return-Path: <zhang.fei3@zte.com.cn>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C417A3A6961; Sun, 27 Feb 2011 17:33:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.349
X-Spam-Level: 
X-Spam-Status: No, score=-100.349 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
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 Q9JuQv6RYP2F; Sun, 27 Feb 2011 17:33:11 -0800 (PST)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id D3CD13A695E; Sun, 27 Feb 2011 17:33:10 -0800 (PST)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 205952043691617; Mon, 28 Feb 2011 09:28:59 +0800 (CST)
Received: from [10.30.3.20] by [192.168.168.16] with StormMail ESMTP id 47420.2043691617; Mon, 28 Feb 2011 09:24:55 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id p1S1Xsf6038947; Mon, 28 Feb 2011 09:33:54 +0800 (GMT-8) (envelope-from zhang.fei3@zte.com.cn)
To: ccamp@ietf.org, mpls@ietf.org, mpls-tp@ietf.org
MIME-Version: 1.0
X-KeepSent: 3D2BCB7D:7BE0C902-48257845:00045755; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF3D2BCB7D.7BE0C902-ON48257845.00045755-48257845.0008966A@zte.com.cn>
From: zhang.fei3@zte.com.cn
Date: Mon, 28 Feb 2011 09:34:00 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-02-28 09:33:53, Serialize complete at 2011-02-28 09:33:53
Content-Type: multipart/alternative; boundary="=_alternative 0008966748257845_="
X-MAIL: mse01.zte.com.cn p1S1Xsf6038947
Subject: [mpls-tp] draft-zhang-mpls-tp-rsvpte-ext-associated-lsp-03
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2011 01:33:13 -0000

This is a multipart message in MIME format.
--=_alternative 0008966748257845_=
Content-Type: text/plain; charset="US-ASCII"

Dear All

We just updated the document about the creating of associated 
bidirectional LSPs, and below is the link:

http://tools.ietf.org/id/draft-zhang-mpls-tp-rsvpte-ext-associated-lsp-03.txt


Compared with last version, the main changes are about the section of 
asymmetric associated bidirectional LSP:

We used the object UPSTREAM_TSPEC to trigger the peer end to set up the 
reverse unidirectional LSP in last version, however the application 
scenario defined in 
http://tools.ietf.org/html/draft-ietf-ccamp-asymm-bw-bidir-lsps-bis-01 is 
different from here. So a new object called REVERSE_TSPEC is used to 
replace the UPSTREAM_TSPCE object in this version.

The other revisions are structural and editoral in nature, such as 
complementing more considerations about security, adding one sub-section 
of informativereference, temporarily moving George from the position of 
co-authors....

The authors would like to have more feedback from the mailing list before 
pushing this work forward. 

Grateful if you could review the document and post comments on the mailing 
list.
 
Thanks and best regards
 
Fei


--=_alternative 0008966748257845_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=3>Dear All</font>
<br>
<br><font size=3>We just updated the document about the creating of associated
bidirectional LSPs, and below is the link:</font>
<br>
<br><font size=3>http://tools.ietf.org/id/draft-zhang-mpls-tp-rsvpte-ext-associated-lsp-03.txt<br>
</font>
<br><font size=3>Compared with last version, the main changes are about
the section of asymmetric associated bidirectional LSP:</font>
<br>
<br><font size=3>We used the object UPSTREAM_TSPEC to trigger the peer
end to set up the reverse unidirectional LSP in last version, however the
application scenario defined in http://tools.ietf.org/html/draft-ietf-ccamp-asymm-bw-bidir-lsps-bis-01
is different from here. So a new object called REVERSE_TSPEC is used to
replace the UPSTREAM_TSPCE object in this version.</font>
<br>
<br><font size=3>The other revisions are structural and editoral in nature,
such as complementing more considerations about security, adding one sub-section
of informativereference, temporarily moving George from the position of
co-authors....</font>
<br>
<table width=100%>
<tr>
<td width=100%><font size=3>The authors would like to have more feedback
from the mailing list before pushing this work forward. </font>
<br>
<br><font size=3>Grateful if you could review the document and post comments
on the mailing list.</font></table>
<br><font size=3>&nbsp;<br>
Thanks and best regards<br>
 <br>
Fei</font>
<br><font size=2 face="sans-serif"><br>
</font>
--=_alternative 0008966748257845_=--


From venkatflex@gmail.com  Sun Feb 27 19:19:45 2011
Return-Path: <venkatflex@gmail.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2A1943A6A6D; Sun, 27 Feb 2011 19:19:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.531
X-Spam-Level: 
X-Spam-Status: No, score=-3.531 tagged_above=-999 required=5 tests=[AWL=-0.067, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_OTHER=0.135]
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 wvJ-t14-7DYN; Sun, 27 Feb 2011 19:19:41 -0800 (PST)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id 865233A6998; Sun, 27 Feb 2011 19:19:41 -0800 (PST)
Received: by qwh6 with SMTP id 6so2815231qwh.31 for <multiple recipients>; Sun, 27 Feb 2011 19:20:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=U8jMtV6i+2/vlAluEIVrpkK2gvhV9NJjQOpbJTQxSdU=; b=B0Rj8HJq4KRaAATqyjr6334TRwzH1LNdJr1ge20/iCGR07A2i6EQFlAj8HQlALjql9 Cbz5sQyqt7cyKGfiTg6Hi8qWxS2y5hr97MJgsmvtO8AI+8snKkc4xkf1Kyc7zYF0SmrV 7efnzLg8FyTO0V2R3/4QsdWm561u3N75eyz7M=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=wtqpY0aGCLU9BaU2fSRZj3XRTZ9uzKWYMLq/vinoEV5/goKrWF2vUwv1t1cZlWcXj4 jYpFvmYmt9xkjAJasraJeo0sXOIcBS+qdtdhelesZkGC90i7lEbIwvmECcZTC7/7XP8g Dv5yeaIVVN3omaRbhHRTX4phgx6BQs5/VkAnI=
MIME-Version: 1.0
Received: by 10.224.28.147 with SMTP id m19mr4073011qac.255.1298863240321; Sun, 27 Feb 2011 19:20:40 -0800 (PST)
Received: by 10.224.20.71 with HTTP; Sun, 27 Feb 2011 19:20:40 -0800 (PST)
Date: Sun, 27 Feb 2011 22:20:40 -0500
Message-ID: <AANLkTimb3SCx7=xsJxG3-O=kfnECRwqGPqzm79+M8cCB@mail.gmail.com>
From: venkatesan mahalingam <venkatflex@gmail.com>
To: mpls <mpls@ietf.org>, mpls-tp@ietf.org
Content-Type: multipart/alternative; boundary=0015175cb07c0d1b76049d4f2a5f
Subject: [mpls-tp] New draft-vkst-mpls-tp-te-mib-00 draft for review
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2011 03:19:45 -0000

--0015175cb07c0d1b76049d4f2a5f
Content-Type: text/plain; charset=ISO-8859-1

Hi Team,
We have uploaded the MPLS-TP TE MIB draft last week into IETF repository.

This document provides an enhancement to the RFC-3812 for managing the
Traffic Engineering tunnels
for MPLS based transport networks in IP and Non-IP operator environments.

Please review the draft and provide your valuable comments/suggestions.

A URL of the draft is:
http://tools.ietf.org/id/draft-vkst-mpls-tp-te-mib-00.txt
<http://tools.ietf.org/id/draft-vkst-mpls-tp-te-mib-00.txt>
-- 
Best Regards,
Venkatesan Mahalingam.

--0015175cb07c0d1b76049d4f2a5f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Team,<div>We have uploaded the MPLS-TP TE MIB draft last week into IETF =
repository.</div><div><br></div><div>This document provides an enhancement =
to the RFC-3812 for managing the Traffic Engineering tunnels=A0</div><div>
for MPLS based transport networks in IP and Non-IP operator environments.</=
div><div><br></div><div>Please review the draft and provide your valuable c=
omments/suggestions.</div><div><br></div><div>A URL of the draft is:</div>
<div><a href=3D"http://tools.ietf.org/id/draft-vkst-mpls-tp-te-mib-00.txt">=
http://tools.ietf.org/id/draft-vkst-mpls-tp-te-mib-00.txt</a><div><a href=
=3D"http://tools.ietf.org/id/draft-vkst-mpls-tp-te-mib-00.txt"></a><br>-- <=
br>
Best Regards,<br>Venkatesan Mahalingam.<br>
</div></div>

--0015175cb07c0d1b76049d4f2a5f--

From vijayc@hcl.com  Sun Feb 27 23:54:14 2011
Return-Path: <vijayc@hcl.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 659503A6AD4 for <mpls-tp@core3.amsl.com>; Sun, 27 Feb 2011 23:54:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.522
X-Spam-Level: 
X-Spam-Status: No, score=-0.522 tagged_above=-999 required=5 tests=[AWL=0.947,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RELAY_IS_203=0.994, SARE_SUB_OBFU_OTHER=0.135]
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 BaStv-ms-C5X for <mpls-tp@core3.amsl.com>; Sun, 27 Feb 2011 23:54:09 -0800 (PST)
Received: from gws08.hcl.com (gws08.hcl.com [203.105.186.26]) by core3.amsl.com (Postfix) with ESMTP id DAE643A6AC8 for <mpls-tp@ietf.org>; Sun, 27 Feb 2011 23:54:07 -0800 (PST)
Received: from chn-hclin-ht02.CORP.HCL.IN (10.249.64.36) by CHN-HCLIN-EDGE4.HCL.COM (10.249.64.141) with Microsoft SMTP Server id 8.2.254.0; Mon, 28 Feb 2011 13:24:27 +0530
Received: from CHN-HCLT-CASHT1.HCLT.CORP.HCL.IN (10.108.45.33) by chn-hclin-ht02.CORP.HCL.IN (10.249.64.36) with Microsoft SMTP Server (TLS) id 8.2.254.0; Mon, 28 Feb 2011 13:25:04 +0530
Received: from CHN-HCLT-EVS07.HCLT.CORP.HCL.IN ([fe80::f46b:fdf2:3218:985d]) by CHN-HCLT-CASHT1.HCLT.CORP.HCL.IN ([::1]) with mapi; Mon, 28 Feb 2011 13:25:04 +0530
From: "Vijayanand C - ERS, HCL Tech" <vijayc@hcl.com>
To: venkatesan mahalingam <venkatflex@gmail.com>, "Kannan.Sampath@aricent.com" <Kannan.Sampath@aricent.com>, "aldrin.ietf@gmail.com" <aldrin.ietf@gmail.com>, "tnadeau@lucidvision.com" <tnadeau@lucidvision.com>
Date: Mon, 28 Feb 2011 13:25:03 +0530
Thread-Topic: [mpls] New draft-vkst-mpls-tp-te-mib-00 draft for review
Thread-Index: AcvW9oRAM9fFSJ7ESF26LiKCHkjL5AAI2t0A
Message-ID: <66E3DDEEA70F0D469D1FFE238526B6ED3E446EE737@CHN-HCLT-EVS07.HCLT.CORP.HCL.IN>
References: <AANLkTimb3SCx7=xsJxG3-O=kfnECRwqGPqzm79+M8cCB@mail.gmail.com>
In-Reply-To: <AANLkTimb3SCx7=xsJxG3-O=kfnECRwqGPqzm79+M8cCB@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_66E3DDEEA70F0D469D1FFE238526B6ED3E446EE737CHNHCLTEVS07H_"
MIME-Version: 1.0
Cc: "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls-tp] [mpls] New draft-vkst-mpls-tp-te-mib-00 draft for review
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2011 07:54:14 -0000

--_000_66E3DDEEA70F0D469D1FFE238526B6ED3E446EE737CHNHCLTEVS07H_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi venkatesh and authors,
This draft specifies that for bidirectional LSPs there will be two cross-co=
nnects with different mplsXCIndex but unique mplsXCLspId.
Are you saying thsat the mplsXCLspId has to be globally unique ( rfc3813 sa=
ys it's the mplsLSPID  which rfc 3811 says is the two byte LSPID in the cas=
e of RSVP-TE LSPs) and be used to tie up the forward and reverse cross conn=
ect entries ?


You have also used the mplsXCLspId in the mplsTunnelXCPointer filed of the =
mplsTunnelTable

(mplsTunnelXCPointer          =3D
                                 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.12,
)
 The XCPointer usually holds the index of the XC entry. ( xcindex,inseginde=
x,outsegindex). For mpls-tp bidirectional LSPs are you mandating the use of=
 mplsXClspid in the XCPointer implicitly makign it one of the index fields =
of the XCEntry ?

Regards
Vijay
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of ven=
katesan mahalingam
Sent: Monday, February 28, 2011 8:51 AM
To: mpls; mpls-tp@ietf.org
Subject: [mpls] New draft-vkst-mpls-tp-te-mib-00 draft for review

Hi Team,
We have uploaded the MPLS-TP TE MIB draft last week into IETF repository.

This document provides an enhancement to the RFC-3812 for managing the Traf=
fic Engineering tunnels
for MPLS based transport networks in IP and Non-IP operator environments.

Please review the draft and provide your valuable comments/suggestions.

A URL of the draft is:
http://tools.ietf.org/id/draft-vkst-mpls-tp-te-mib-00.txt

--
Best Regards,
Venkatesan Mahalingam.

________________________________
::DISCLAIMER::
---------------------------------------------------------------------------=
--------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and inte=
nded for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its affiliate=
s. Any views or opinions presented in
this email are solely those of the author and may not necessarily reflect t=
he opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification,=
 distribution and / or publication of
this message without the prior written consent of the author of this e-mail=
 is strictly prohibited. If you have
received this email in error please delete it and notify the sender immedia=
tely. Before opening any mail and
attachments please check them for viruses and defect.

---------------------------------------------------------------------------=
--------------------------------------------

--_000_66E3DDEEA70F0D469D1FFE238526B6ED3E446EE737CHNHCLTEVS07H_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"Section1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Hi venkatesh and authors,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">This draft specifies that for bidirectional LSPs there will =
be two cross-connects with different mplsXCIndex but unique mplsXCLspId.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Are you saying thsat the mplsXCLspId has to be globally uniq=
ue ( rfc3813 says it&#8217;s the mplsLSPID &nbsp;which rfc 3811 says is the=
 two byte LSPID in the case of
 RSVP-TE LSPs) and be used to tie up the forward and reverse cross connect =
entries ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<pre><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;
color:#1F497D">You have also used the mplsXCLspId in the mplsTunnelXCPointe=
r filed of the mplsTunnelTable <o:p></o:p></span></pre>
<pre><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1F497D">(</span>mplsTunnelXCPointer&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D <o:p></o:p></pre>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mplsXCLspId.4.0=
.0.0.1.1.0.4.0.0.0.12,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">&nbsp;The XCPointer usually holds the index of the XC entry.=
 ( xcindex,insegindex,outsegindex). For mpls-tp bidirectional LSPs are you =
mandating the use of mplsXClspid
 in the XCPointer implicitly makign it one of the index fields of the XCEnt=
ry ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;
color:#1F497D">Regards</span><span style=3D"color:#1F497D"><o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;
color:#1F497D">Vijay</span><span style=3D"font-size:11.0pt;font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p></o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> mpls-bou=
nces@ietf.org [mailto:mpls-bounces@ietf.org]
<b>On Behalf Of </b>venkatesan mahalingam<br>
<b>Sent:</b> Monday, February 28, 2011 8:51 AM<br>
<b>To:</b> mpls; mpls-tp@ietf.org<br>
<b>Subject:</b> [mpls] New draft-vkst-mpls-tp-te-mib-00 draft for review<o:=
p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi Team,<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">We have uploaded the MPLS-TP TE MIB draft last week =
into IETF repository.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">This document provides an enhancement to the RFC-381=
2 for managing the Traffic Engineering tunnels&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">for MPLS based transport networks in IP and Non-IP o=
perator environments.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Please review the draft and provide your valuable co=
mments/suggestions.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">A URL of the draft is:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/id/draft-vkst-mpls-=
tp-te-mib-00.txt">http://tools.ietf.org/id/draft-vkst-mpls-tp-te-mib-00.txt=
</a><o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><br>
-- <br>
Best Regards,<br>
Venkatesan Mahalingam.<o:p></o:p></p>
</div>
</div>
</div>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1">::DISCLAIMER::<br>
---------------------------------------------------------------------------=
--------------------------------------------<br>
<br>
The contents of this e-mail and any attachment(s) are confidential and inte=
nded for the named recipient(s) only.<br>
It shall not attach any liability on the originator or HCL or its affiliate=
s. Any views or opinions presented in<br>
this email are solely those of the author and may not necessarily reflect t=
he opinions of HCL or its affiliates.<br>
Any form of reproduction, dissemination, copying, disclosure, modification,=
 distribution and / or publication of<br>
this message without the prior written consent of the author of this e-mail=
 is strictly prohibited. If you have<br>
received this email in error please delete it and notify the sender immedia=
tely. Before opening any mail and<br>
attachments please check them for viruses and defect.<br>
<br>
---------------------------------------------------------------------------=
--------------------------------------------<br>
</font>
</body>
</html>

--_000_66E3DDEEA70F0D469D1FFE238526B6ED3E446EE737CHNHCLTEVS07H_--

From tochio@jp.fujitsu.com  Mon Feb 28 02:58:47 2011
Return-Path: <tochio@jp.fujitsu.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6F7BB3A6B21 for <mpls-tp@core3.amsl.com>; Mon, 28 Feb 2011 02:58:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.09
X-Spam-Level: 
X-Spam-Status: No, score=-100.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, USER_IN_WHITELIST=-100]
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 YHs5w9JPHQBo for <mpls-tp@core3.amsl.com>; Mon, 28 Feb 2011 02:58:46 -0800 (PST)
Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by core3.amsl.com (Postfix) with ESMTP id 553A83A6B17 for <mpls-tp@ietf.org>; Mon, 28 Feb 2011 02:58:46 -0800 (PST)
Received: from m1.gw.fujitsu.co.jp (unknown [10.0.50.71]) by fgwmail6.fujitsu.co.jp (Postfix) with ESMTP id B8F3B3EE0BB for <mpls-tp@ietf.org>; Mon, 28 Feb 2011 19:59:45 +0900 (JST)
Received: from smail (m1 [127.0.0.1]) by outgoing.m1.gw.fujitsu.co.jp (Postfix) with ESMTP id A0B5245DE54 for <mpls-tp@ietf.org>; Mon, 28 Feb 2011 19:59:45 +0900 (JST)
Received: from s1.gw.fujitsu.co.jp (s1.gw.fujitsu.co.jp [10.0.50.91]) by m1.gw.fujitsu.co.jp (Postfix) with ESMTP id 7F1D845DD02 for <mpls-tp@ietf.org>; Mon, 28 Feb 2011 19:59:45 +0900 (JST)
Received: from s1.gw.fujitsu.co.jp (localhost.localdomain [127.0.0.1]) by s1.gw.fujitsu.co.jp (Postfix) with ESMTP id 6EB88E08002 for <mpls-tp@ietf.org>; Mon, 28 Feb 2011 19:59:45 +0900 (JST)
Received: from dm.kawasaki.flab.fujitsu.co.jp (dm.kawasaki.flab.fujitsu.co.jp [10.25.192.105]) by s1.gw.fujitsu.co.jp (Postfix) with ESMTP id 3BAD6E08001 for <mpls-tp@ietf.org>; Mon, 28 Feb 2011 19:59:45 +0900 (JST)
Received: from vs.kawasaki.flab.fujitsu.co.jp (vs.kawasaki.flab.fujitsu.co.jp [10.25.192.38]) by dm.kawasaki.flab.fujitsu.co.jp (8.14.4/8.14.4/100813-Fujitsu Labs. Kawasaki Domain Mail Master) with ESMTP id p1SAxicW004056 for <mpls-tp@ietf.org>; Mon, 28 Feb 2011 19:59:44 +0900 (JST)
X-AuditID: 0a19c026-00000004000001f6-c4-4d6b80206313
Received: from dm.kawasaki.flab.fujitsu.co.jp (dm.kawasaki.flab.fujitsu.co.jp [10.25.192.105]) by vs.kawasaki.flab.fujitsu.co.jp (Symantec Mail Security) with ESMTP id 912C5298A5 for <mpls-tp@ietf.org>; Mon, 28 Feb 2011 19:59:44 +0900 (JST)
Received: from [127.0.0.1] (dhcp98.dream.flab.fujitsu.co.jp [10.25.144.157]) by dm.kawasaki.flab.fujitsu.co.jp (8.14.4/8.14.4/100813-Fujitsu Labs. Kawasaki Domain Mail Master) with ESMTP id p1SAxi3J004041 for <mpls-tp@ietf.org>; Mon, 28 Feb 2011 19:59:44 +0900 (JST)
X-SecurityPolicyCheck: OK by SHieldMailChecker v1.5.1
Message-ID: <4D6B8010.6000002@jp.fujitsu.com>
Date: Mon, 28 Feb 2011 19:59:28 +0900
From: Yuji Tochio <tochio@jp.fujitsu.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: "mpls-tp@ietf.org" <mpls-tp@ietf.org>
References: <4D4A934F.5020206@pi.nu>
In-Reply-To: <4D4A934F.5020206@pi.nu>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [mpls-tp] wg last call on draft-ietf-mpls-tp-fault-03
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2011 10:58:47 -0000

Hi,

Some comments

* Section 2.1 (, 2.1.1)
There are some use of fatal. Please clarify what fatal means.
And it is better to have the definition of this both for AIS
and for LDI


* Section 2.1.1
Use of protection seems to relate to the usage for LDI, differentiated
from AIS.
And "The setting of the LDI flag can be predetermined based
on the protection state If the Server Layer is protected...."means
that there is server layer protection scheme and this prederminnes
the usage of LDI.
This server layer protection scheme should be more clarified.
Is the server layer supposed to have 1:1?
How about 1+1?

And active MEP should be active Server MEP

This had been already pointed out in general by
http://www.ietf.org/mail-archive/web/mpls-tp/current/msg02793.html
(last part in that mail)

* Section 4
Please clarify the reception behavior when
- Msg type= reserved
- Msg type = LCK & L-flag set
(should be ignored and this should be described in 5.3)


* Section 5.1
Following sentence is unclear
"The message MUST be refreshed two more times at an interval
of one second."
I guess this implies that messages should be more than specified
at first second. Is this right? Does this apply to refresh timer is 1?

And in early review from ITU-T, it is proposed to remove the refresh timer
but it still remains. It is better to have the clear reason why it is needed.

Section 5.3
It says:
A message is considered a refresh if the message type and IF_ID match
an existing condition and the R-Flag is set to zero.

How about this case?
A-->B-->C-->D
D is receiving AIS or LDI with IF_ID = B. But another failure at C
happens D starts to receive LDI with IF_ID = C.
In this case, does D have to have two timers for B and C

...And it is confused that is "refresh(ed)"
It seems that following cases are used in common, but different places
- the receiver, MEP that refresh timer is in for reception process
- the transmitter (as fault detection by refresh timer)
- the transmitter (as message generation makes format refresh by over-written)

Regards,
Yuji

(2011/02/03 20:36), Loa Andersson wrote:
> Working Group,
>
> this is to start a four week working group last call
> on "MPLS Fault Management OAM" (draft-ietf-mpls-tp-fault-03).
>
> Please send comments to the mpls-tp@ietf.org mailing list.
>
> This working group last call ends on February 28, 2011.
>
>
>
> Loa, George and Ross
>
> MPLS wg co-chairs
>
> -- 
>
> Loa Andersson email: loa.andersson@ericsson.com
> Sr Strategy and Standards Manager loa@pi.nu
> Ericsson Inc phone: +46 10 717 52 13
> +46 767 72 92 13
>
>
>
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp
>
>



From tochio@jp.fujitsu.com  Mon Feb 28 03:48:27 2011
Return-Path: <tochio@jp.fujitsu.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B59133A69CD for <mpls-tp@core3.amsl.com>; Mon, 28 Feb 2011 03:48:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.09
X-Spam-Level: 
X-Spam-Status: No, score=-100.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, USER_IN_WHITELIST=-100]
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 64Dz7jwuJtci for <mpls-tp@core3.amsl.com>; Mon, 28 Feb 2011 03:48:27 -0800 (PST)
Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by core3.amsl.com (Postfix) with ESMTP id 46D503A6B2E for <mpls-tp@ietf.org>; Mon, 28 Feb 2011 03:48:21 -0800 (PST)
Received: from m1.gw.fujitsu.co.jp (unknown [10.0.50.71]) by fgwmail6.fujitsu.co.jp (Postfix) with ESMTP id 191E63EE0B5 for <mpls-tp@ietf.org>; Mon, 28 Feb 2011 20:49:21 +0900 (JST)
Received: from smail (m1 [127.0.0.1]) by outgoing.m1.gw.fujitsu.co.jp (Postfix) with ESMTP id 038C245DE54 for <mpls-tp@ietf.org>; Mon, 28 Feb 2011 20:49:21 +0900 (JST)
Received: from s1.gw.fujitsu.co.jp (s1.gw.fujitsu.co.jp [10.0.50.91]) by m1.gw.fujitsu.co.jp (Postfix) with ESMTP id E21B145DE53 for <mpls-tp@ietf.org>; Mon, 28 Feb 2011 20:49:20 +0900 (JST)
Received: from s1.gw.fujitsu.co.jp (localhost.localdomain [127.0.0.1]) by s1.gw.fujitsu.co.jp (Postfix) with ESMTP id D675FE08001 for <mpls-tp@ietf.org>; Mon, 28 Feb 2011 20:49:20 +0900 (JST)
Received: from dm.kawasaki.flab.fujitsu.co.jp (dm.kawasaki.flab.fujitsu.co.jp [10.25.192.105]) by s1.gw.fujitsu.co.jp (Postfix) with ESMTP id A7D28E08003 for <mpls-tp@ietf.org>; Mon, 28 Feb 2011 20:49:20 +0900 (JST)
Received: from vs.kawasaki.flab.fujitsu.co.jp (vs.kawasaki.flab.fujitsu.co.jp [10.25.192.38]) by dm.kawasaki.flab.fujitsu.co.jp (8.14.4/8.14.4/100813-Fujitsu Labs. Kawasaki Domain Mail Master) with ESMTP id p1SBnKTL012476 for <mpls-tp@ietf.org>; Mon, 28 Feb 2011 20:49:20 +0900 (JST)
X-AuditID: 0a19c026-0000000a000001f6-7a-4d6b8bc06ff0
Received: from dm.kawasaki.flab.fujitsu.co.jp (dm.kawasaki.flab.fujitsu.co.jp [10.25.192.105]) by vs.kawasaki.flab.fujitsu.co.jp (Symantec Mail Security) with ESMTP id 73B86298A3 for <mpls-tp@ietf.org>; Mon, 28 Feb 2011 20:49:20 +0900 (JST)
Received: from [127.0.0.1] (dhcp98.dream.flab.fujitsu.co.jp [10.25.144.157]) by dm.kawasaki.flab.fujitsu.co.jp (8.14.4/8.14.4/100813-Fujitsu Labs. Kawasaki Domain Mail Master) with ESMTP id p1SBnKQ3012473 for <mpls-tp@ietf.org>; Mon, 28 Feb 2011 20:49:20 +0900 (JST)
X-SecurityPolicyCheck: OK by SHieldMailChecker v1.5.1
Message-ID: <4D6B8BB0.3060608@jp.fujitsu.com>
Date: Mon, 28 Feb 2011 20:49:04 +0900
From: Yuji Tochio <tochio@jp.fujitsu.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: "mpls-tp@ietf.org" <mpls-tp@ietf.org>
References: <4D4AB81D.3080907@pi.nu>
In-Reply-To: <4D4AB81D.3080907@pi.nu>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [mpls-tp] mpls wg last call on draft-ietf-mpls-tp-cc-cv-rdi-03
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2011 11:48:27 -0000

Hi

A few comments... (Since a number of comments are seen in archives
or LS statement from ITU-T)

1) As I addressed over microphone in IETF, I am still wondering on the
necessity of "session" for MPLS-TP since:
- Already ME exists and cc-cv-rdi runs over this
- No description on RFC5654 and RFC5860 (only saying "End Points of
PWs, LSPs...",)
- RFC5880 says "A BFD session is established based on the needs of the
application that will be making use of it." What do you mean by application
in terms of MPLS-TP? This could be "the CC or proactive CV functionality
enabler on ME". If so, as in first bullet, cc-cv-rai runs over ME after all, .
Please clarify why session is reasonably required.

2) Even if the session is inevitable, the consideration in the usage under
SPME working along LSP. For example, session in SPME down, this should
affect on the end-to-end LSP. i,e, Some action outside of SPME LSP from
two ends of session should be made and text for this case is required.

Regards,
Yuji

(2011/02/03 23:13), Loa Andersson wrote:
> Working Group,
>
> this is to start a four week working group last call on
> "Proactive Connectivity Verification, Continuity Check and
> Remote Defect indication for MPLS Transport Profile"
> (draft-ietf-mpls-tp-cc-cv-rdi-03.txt).
>
> Please send comments to the mpls-tp@ietf.org mailing list.
>
> This working group last call ends on February 28, 2011.
>
>
> Loa, George and Ross
>
> MPLS wg co-chairs



From maarten.vissers@huawei.com  Mon Feb 28 04:47:59 2011
Return-Path: <maarten.vissers@huawei.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D5C183A684F for <mpls-tp@core3.amsl.com>; Mon, 28 Feb 2011 04:47:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 4oLF4vFvlQMr for <mpls-tp@core3.amsl.com>; Mon, 28 Feb 2011 04:47:59 -0800 (PST)
Received: from lhrga02-in.huawei.com (lhrga02-in.huawei.com [195.33.106.143]) by core3.amsl.com (Postfix) with ESMTP id D6B683A6B11 for <mpls-tp@ietf.org>; Mon, 28 Feb 2011 04:47:58 -0800 (PST)
Received: from huawei.com (lhrga02-in [172.18.7.45]) by lhrga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LHB002X1VKUUU@lhrga02-in.huawei.com> for mpls-tp@ietf.org; Mon, 28 Feb 2011 12:48:31 +0000 (GMT)
Received: from LHREML201-EDG.china.huawei.com ([172.18.7.118]) by lhrga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPS id <0LHB00CNLVKU27@lhrga02-in.huawei.com> for mpls-tp@ietf.org; Mon, 28 Feb 2011 12:48:30 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.30) by LHREML201-EDG.china.huawei.com (172.18.7.188) with Microsoft SMTP Server (TLS) id 14.1.270.1; Mon, 28 Feb 2011 12:48:53 +0000
Received: from LHREML501-MBX.china.huawei.com ([fe80::85b6:15b7:c624:8912]) by LHREML401-HUB.china.huawei.com ([::1]) with mapi id 14.01.0270.001; Mon, 28 Feb 2011 12:48:56 +0000
Date: Mon, 28 Feb 2011 12:48:55 +0000
From: Maarten vissers <maarten.vissers@huawei.com>
In-reply-to: <4D6B8010.6000002@jp.fujitsu.com>
X-Originating-IP: [10.202.112.103]
To: "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Message-id: <D62E6669B3621943B7632961308F8F9E02D96D@LHREML501-MBX.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: en-US
Content-transfer-encoding: 7BIT
Accept-Language: en-GB, en-US
Thread-topic: [mpls-tp] wg last call on draft-ietf-mpls-tp-fault-03
Thread-index: AQHL1zcqtyz+QO1ioUOlD8ckZLDEdpQWyHlA
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <4D4A934F.5020206@pi.nu> <4D6B8010.6000002@jp.fujitsu.com>
Subject: Re: [mpls-tp] wg last call on draft-ietf-mpls-tp-fault-03
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2011 12:48:00 -0000

Comment on LDI operation:

LSPs can be nested, and it is possible to have an LSP stack with e.g. five LSPs (A,B,C,D,E) as follows:

MEP1-----------------------(A)--------------------------MEP2
       MEP3----------(B)----------MEP4   MEP5--(C)---MEP6
             W.MEP7--(D)--W.MEP8
             P.MEP9--(E)--P.MEP10

When LSP(D) fails, LSP(B) and LSP(A) fail as well. 
W.MEP8, MEP4 and MEP2 will detect this failure and will insert AIS.
  - W.MEP8 can send AIS(L-flag=0).
  - MEP4 and MEP2 have no immediate knowledge of the 
    server layer/sublayer protection, and send AIS(L-flag=1). 

As there is protection present at a server (sub)layer and both working and protection paths are available before the fault occurs, MEP4 and MEP2 should have send AIS(L-flag=0) instead of AIS(L-flag=1).

How to control that MEP4 and MEP2 set the LDI flag to "clear" when working and protection paths are both available in this case?

Regards,
Maarten


(2011/02/03 20:36), Loa Andersson wrote:
> Working Group,
>
> this is to start a four week working group last call
> on "MPLS Fault Management OAM" (draft-ietf-mpls-tp-fault-03).
>
> Please send comments to the mpls-tp@ietf.org mailing list.
>
> This working group last call ends on February 28, 2011.
>
> Loa, George and Ross
> MPLS wg co-chairs
> --
> Loa Andersson email: loa.andersson@ericsson.com
> Sr Strategy and Standards Manager loa@pi.nu
> Ericsson Inc phone: +46 10 717 52 13
> +46 767 72 92 13

From venkatflex@gmail.com  Mon Feb 28 05:38:21 2011
Return-Path: <venkatflex@gmail.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5A53F3A6BF9; Mon, 28 Feb 2011 05:38:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.508
X-Spam-Level: 
X-Spam-Status: No, score=-3.508 tagged_above=-999 required=5 tests=[AWL=-0.045, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_OTHER=0.135]
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 VCSOFuFoz+yW; Mon, 28 Feb 2011 05:38:20 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id B0DE23A6BF8; Mon, 28 Feb 2011 05:38:19 -0800 (PST)
Received: by qyk29 with SMTP id 29so2048996qyk.10 for <multiple recipients>; Mon, 28 Feb 2011 05:39:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Hb2yrX6eVaKrJd+LYR5f0+/q8vk1q91WAT21W6JSCRc=; b=I/unJ3oNwm1PQG3Ob9Gw9hQ8AP1LAt9dwuDChr/yTYmxvuQnojgZbCYYzp8HlSUeb2 59iX/I2nz3hBIyAdn9CiQyXHf50/7ZMU01hQHxMPGTdgeIpD3c0xxhURQsfGbafvlkln z9sLPQ0Wwz9rJ4CQt+vU+WB3N6b2SLjkQYNTc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=GakKRG20ffvgOlvI7O5LyOazlxM/gLOoytWmqPSWjlZdLexcpqLMkZyahCsaLyK4bs vsT8etlRKrirwM4iH9IgFW1AkzgBj/ABekDy+sVVxR8NFG6FE6/kPLU8WWuc5jhhULVE XYBd7zGgdg9ufQdOlQPG4cc4blT4cwPyDv+c0=
MIME-Version: 1.0
Received: by 10.224.20.11 with SMTP id d11mr2420881qab.205.1298900359526; Mon, 28 Feb 2011 05:39:19 -0800 (PST)
Received: by 10.224.20.71 with HTTP; Mon, 28 Feb 2011 05:39:19 -0800 (PST)
In-Reply-To: <66E3DDEEA70F0D469D1FFE238526B6ED3E446EE737@CHN-HCLT-EVS07.HCLT.CORP.HCL.IN>
References: <AANLkTimb3SCx7=xsJxG3-O=kfnECRwqGPqzm79+M8cCB@mail.gmail.com> <66E3DDEEA70F0D469D1FFE238526B6ED3E446EE737@CHN-HCLT-EVS07.HCLT.CORP.HCL.IN>
Date: Mon, 28 Feb 2011 08:39:19 -0500
Message-ID: <AANLkTimFWz-fVPTH2SF342MNBe_FFM+YEYxxNj1bvuQQ@mail.gmail.com>
From: venkatesan mahalingam <venkatflex@gmail.com>
To: "Vijayanand C - ERS, HCL Tech" <vijayc@hcl.com>
Content-Type: multipart/alternative; boundary=0015175cb83e873b92049d57cedd
Cc: mpls <mpls@ietf.org>, mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] New draft-vkst-mpls-tp-te-mib-00 draft for review
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2011 13:38:21 -0000

--0015175cb83e873b92049d57cedd
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Vijay,
Thanks for your review.

Please find the responses inline.

Regards,
Venkat.

On Mon, Feb 28, 2011 at 2:55 AM, Vijayanand C - ERS, HCL Tech <
vijayc@hcl.com> wrote:

>  Hi venkatesh and authors,
>
> This draft specifies that for bidirectional LSPs there will be two
> cross-connects with different mplsXCIndex but unique mplsXCLspId.
>
> VM>> There is a typo in the draft, there should be two cross-connects wit=
h
same mplsXCIndex for co-routed bidirectional tunnel.


> Are you saying thsat the mplsXCLspId has to be globally unique ( rfc3813
> says it=92s the mplsLSPID  which rfc 3811 says is the two byte LSPID in t=
he
> case of RSVP-TE LSPs) and be used to tie up the forward and reverse cross
> connect entries ?
>
>
>
> You have also used the mplsXCLspId in the mplsTunnelXCPointer filed of th=
e mplsTunnelTable
>
> (mplsTunnelXCPointer          =3D
>
>                                  mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.12,
>
> )
>
>  The XCPointer usually holds the index of the XC entry. (
> xcindex,insegindex,outsegindex). For mpls-tp bidirectional LSPs are you
> mandating the use of mplsXClspid in the XCPointer implicitly makign it on=
e
> of the index fields of the XCEntry ?
>
>
>
VM>> No, we are not implicitly making mplsXClspid as the index field. We
point any accessible XC mib object into an mplsTunnelXCPointer i.e associat=
e
any forward or reverse XC entry to an tunnel entry to get the XC index. Thi=
s
XC index will be used to fetch the forward and reverse XC informations for
co-routed bi-directional tunnel.

Hope this helps.

Regards
>
> Vijay
>
> *From:* mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] *On Behalf O=
f
> *venkatesan mahalingam
> *Sent:* Monday, February 28, 2011 8:51 AM
> *To:* mpls; mpls-tp@ietf.org
> *Subject:* [mpls] New draft-vkst-mpls-tp-te-mib-00 draft for review
>
>
>
> Hi Team,
>
> We have uploaded the MPLS-TP TE MIB draft last week into IETF repository.
>
>
>
> This document provides an enhancement to the RFC-3812 for managing the
> Traffic Engineering tunnels
>
> for MPLS based transport networks in IP and Non-IP operator environments.
>
>
>
> Please review the draft and provide your valuable comments/suggestions.
>
>
>
> A URL of the draft is:
>
> http://tools.ietf.org/id/draft-vkst-mpls-tp-te-mib-00.txt
>
>
> --
> Best Regards,
> Venkatesan Mahalingam.
>
> ------------------------------
> ::DISCLAIMER::
>
> -------------------------------------------------------------------------=
----------------------------------------------
>
> The contents of this e-mail and any attachment(s) are confidential and
> intended for the named recipient(s) only.
> It shall not attach any liability on the originator or HCL or its
> affiliates. Any views or opinions presented in
> this email are solely those of the author and may not necessarily reflect
> the opinions of HCL or its affiliates.
> Any form of reproduction, dissemination, copying, disclosure, modificatio=
n,
> distribution and / or publication of
> this message without the prior written consent of the author of this e-ma=
il
> is strictly prohibited. If you have
> received this email in error please delete it and notify the sender
> immediately. Before opening any mail and
> attachments please check them for viruses and defect.
>
>
> -------------------------------------------------------------------------=
----------------------------------------------
>



--=20
Best Regards,
Venkatesan Mahalingam.

--0015175cb83e873b92049d57cedd
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Vijay,<div>Thanks for your review.</div><div><br></div><div>Please find =
the responses inline.</div><div><br>Regards,</div><div>Venkat.</div><div><b=
r><div class=3D"gmail_quote">On Mon, Feb 28, 2011 at 2:55 AM, Vijayanand C =
- ERS, HCL Tech <span dir=3D"ltr">&lt;<a href=3D"mailto:vijayc@hcl.com">vij=
ayc@hcl.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">Hi ve=
nkatesh and authors,</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">This =
draft specifies that for bidirectional LSPs there will be two cross-connect=
s with different mplsXCIndex but unique mplsXCLspId.
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D"></spa=
n></p></div></div></blockquote><div>VM&gt;&gt; There is a typo in the draft=
, there should be two cross-connects with same mplsXCIndex for co-routed bi=
directional tunnel.</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;"><div lang=3D"EN-US" link=3D"b=
lue" vlink=3D"purple"><div><p class=3D"MsoNormal"><span style=3D"font-size:=
11.0pt;color:#1F497D">Are you saying thsat the mplsXCLspId has to be global=
ly unique ( rfc3813 says it=92s the mplsLSPID =A0which rfc 3811 says is the=
 two byte LSPID in the case of
 RSVP-TE LSPs) and be used to tie up the forward and reverse cross connect =
entries ?</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">=A0</=
span></p>
<pre><span style=3D"font-size:11.0pt;color:#1F497D">You have also used the =
mplsXCLspId in the mplsTunnelXCPointer filed of the mplsTunnelTable </span>=
</pre>
<pre><span style=3D"font-size:11.0pt;color:#1F497D">(</span>mplsTunnelXCPoi=
nter=A0=A0=A0=A0=A0=A0=A0=A0=A0 =3D </pre>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1=
2,</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">)</sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">=A0Th=
e XCPointer usually holds the index of the XC entry. ( xcindex,insegindex,o=
utsegindex). For mpls-tp bidirectional LSPs are you mandating the use of mp=
lsXClspid
 in the XCPointer implicitly makign it one of the index fields of the XCEnt=
ry ?</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;color:#1F497D">=A0</=
span></p></div></div></blockquote><div>VM&gt;&gt; No, we are not implicitly=
 making mplsXClspid as the index field. We point any accessible XC mib obje=
ct into an mplsTunnelXCPointer i.e associate any forward or reverse XC entr=
y to an tunnel entry to get the XC index. This XC index will be used to fet=
ch the forward and reverse XC informations for co-routed bi-directional tun=
nel.</div>
<div><br></div><div>Hope this helps.</div><div><br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex;"><div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;color:#1F497D">Regar=
ds</span><span style=3D"color:#1F497D"></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;color:#1F497D">Vijay=
</span><span style=3D"font-size:11.0pt;color:#1F497D"></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt">From:</span></b>=
<span style=3D"font-size:10.0pt"> <a href=3D"mailto:mpls-bounces@ietf.org" =
target=3D"_blank">mpls-bounces@ietf.org</a> [mailto:<a href=3D"mailto:mpls-=
bounces@ietf.org" target=3D"_blank">mpls-bounces@ietf.org</a>]
<b>On Behalf Of </b>venkatesan mahalingam<br>
<b>Sent:</b> Monday, February 28, 2011 8:51 AM<br>
<b>To:</b> mpls; <a href=3D"mailto:mpls-tp@ietf.org" target=3D"_blank">mpls=
-tp@ietf.org</a><br>
<b>Subject:</b> [mpls] New draft-vkst-mpls-tp-te-mib-00 draft for review</s=
pan></p>
</div>
</div><div><div></div><div class=3D"h5">
<p class=3D"MsoNormal">=A0</p>
<p class=3D"MsoNormal">Hi Team,</p>
<div>
<p class=3D"MsoNormal">We have uploaded the MPLS-TP TE MIB draft last week =
into IETF repository.</p>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal">This document provides an enhancement to the RFC-381=
2 for managing the Traffic Engineering tunnels=A0</p>
</div>
<div>
<p class=3D"MsoNormal">for MPLS based transport networks in IP and Non-IP o=
perator environments.</p>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal">Please review the draft and provide your valuable co=
mments/suggestions.</p>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal">A URL of the draft is:</p>
</div>
<div>
<p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/id/draft-vkst-mpls-=
tp-te-mib-00.txt" target=3D"_blank">http://tools.ietf.org/id/draft-vkst-mpl=
s-tp-te-mib-00.txt</a></p>
<div>
<p class=3D"MsoNormal"><br>
-- <br>
Best Regards,<br>
Venkatesan Mahalingam.</p>
</div>
</div>
</div></div></div>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1">::DISCLAIMER::<br>
---------------------------------------------------------------------------=
--------------------------------------------<br>
<br>
The contents of this e-mail and any attachment(s) are confidential and inte=
nded for the named recipient(s) only.<br>
It shall not attach any liability on the originator or HCL or its affiliate=
s. Any views or opinions presented in<br>
this email are solely those of the author and may not necessarily reflect t=
he opinions of HCL or its affiliates.<br>
Any form of reproduction, dissemination, copying, disclosure, modification,=
 distribution and / or publication of<br>
this message without the prior written consent of the author of this e-mail=
 is strictly prohibited. If you have<br>
received this email in error please delete it and notify the sender immedia=
tely. Before opening any mail and<br>
attachments please check them for viruses and defect.<br>
<br>
---------------------------------------------------------------------------=
--------------------------------------------<br>
</font>
</div>

</blockquote></div><br><br clear=3D"all"><br>-- <br>Best Regards,<br>Venkat=
esan Mahalingam.<br>
</div>

--0015175cb83e873b92049d57cedd--

From eosborne@cisco.com  Mon Feb 28 14:23:07 2011
Return-Path: <eosborne@cisco.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AFA2D3A6C97 for <mpls-tp@core3.amsl.com>; Mon, 28 Feb 2011 14:23:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 VN9ABOq0tl9Z for <mpls-tp@core3.amsl.com>; Mon, 28 Feb 2011 14:23:06 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 6A1BF3A6A00 for <mpls-tp@ietf.org>; Mon, 28 Feb 2011 14:23:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eosborne@cisco.com; l=2618; q=dns/txt; s=iport; t=1298931848; x=1300141448; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=NWzRu4eRmyeWvYK7oxvanWAqe4SBpNVCp5xgy3CmDhU=; b=K93XnCZF6zu4xng2/k5sZO6LQk65KYXFYkJuUYeFQZvKReLGeh7x66WO khDPxZnUK5r1uSUgd5lwWxV6VC1z8Yzb/OpKqnEAJ6xtnQAinknFlYp7I 0mTlJSrXN8p7VjlBJ2hwtpucdjoSvzPxV9v/LMrQ6GwXW47XqzUAAzrg1 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvEAAE+va02tJV2b/2dsb2JhbACXcY5UdKABm2MChV8EhQ+KUQ
X-IronPort-AV: E=Sophos;i="4.62,242,1297036800"; d="scan'208";a="221261848"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rtp-iport-2.cisco.com with ESMTP; 28 Feb 2011 22:24:06 +0000
Received: from xbh-rcd-301.cisco.com (xbh-rcd-301.cisco.com [72.163.63.8]) by rcdn-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p1SMO6Pa008511;  Mon, 28 Feb 2011 22:24:06 GMT
Received: from xmb-rcd-202.cisco.com ([72.163.62.209]) by xbh-rcd-301.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 28 Feb 2011 16:24:06 -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
Date: Mon, 28 Feb 2011 16:24:08 -0600
Message-ID: <D29E470202D67745B61059870F433B54047A1DF4@XMB-RCD-202.cisco.com>
In-Reply-To: <D62E6669B3621943B7632961308F8F9E02D96D@LHREML501-MBX.china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls-tp] wg last call on draft-ietf-mpls-tp-fault-03
Thread-Index: AQHL1zcqtyz+QO1ioUOlD8ckZLDEdpQWyHlAgAC0aEA=
References: <4D4A934F.5020206@pi.nu> <4D6B8010.6000002@jp.fujitsu.com> <D62E6669B3621943B7632961308F8F9E02D96D@LHREML501-MBX.china.huawei.com>
From: "Eric Osborne (eosborne)" <eosborne@cisco.com>
To: "Maarten vissers" <maarten.vissers@huawei.com>, <mpls-tp@ietf.org>
X-OriginalArrivalTime: 28 Feb 2011 22:24:06.0667 (UTC) FILETIME=[36530DB0:01CBD796]
Subject: Re: [mpls-tp] wg last call on draft-ietf-mpls-tp-fault-03
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2011 22:23:07 -0000

Hi Maarten-

  It's not my draft, so I can only respond as a possible implementor.
But what you ask seems like it is entirely an implementation issue, and
a pretty straightforward one at that.  A node (say, MEP3) could send
L=3D1, then send L=3D0 when it receieves L=3D0.  Or MEP3 could have been
configured with a priori knowledge that the failure of SPME B should be
L=3D0.  The draft alludes to this latter approach in section 2.1.1.  The
way I read the draft, the important thing is that a MEP advertises what
it knows; how it determines that is out of scope, IMO.




eric



> -----Original Message-----
> From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On
Behalf
> Of Maarten vissers
> Sent: Monday, February 28, 2011 7:49 AM
> To: mpls-tp@ietf.org
> Subject: Re: [mpls-tp] wg last call on draft-ietf-mpls-tp-fault-03
>=20
> Comment on LDI operation:
>=20
> LSPs can be nested, and it is possible to have an LSP stack with e.g.
five
> LSPs (A,B,C,D,E) as follows:
>=20
> MEP1-----------------------(A)--------------------------MEP2
>        MEP3----------(B)----------MEP4   MEP5--(C)---MEP6
>              W.MEP7--(D)--W.MEP8
>              P.MEP9--(E)--P.MEP10
>=20
> When LSP(D) fails, LSP(B) and LSP(A) fail as well.
> W.MEP8, MEP4 and MEP2 will detect this failure and will insert AIS.
>   - W.MEP8 can send AIS(L-flag=3D0).
>   - MEP4 and MEP2 have no immediate knowledge of the
>     server layer/sublayer protection, and send AIS(L-flag=3D1).
>=20
> As there is protection present at a server (sub)layer and both working
and
> protection paths are available before the fault occurs, MEP4 and MEP2
> should have send AIS(L-flag=3D0) instead of AIS(L-flag=3D1).
>=20
> How to control that MEP4 and MEP2 set the LDI flag to "clear" when
working
> and protection paths are both available in this case?
>=20
> Regards,
> Maarten
>=20
>=20
> (2011/02/03 20:36), Loa Andersson wrote:
> > Working Group,
> >
> > this is to start a four week working group last call on "MPLS Fault
> > Management OAM" (draft-ietf-mpls-tp-fault-03).
> >
> > Please send comments to the mpls-tp@ietf.org mailing list.
> >
> > This working group last call ends on February 28, 2011.
> >
> > Loa, George and Ross
> > MPLS wg co-chairs
> > --
> > Loa Andersson email: loa.andersson@ericsson.com Sr Strategy and
> > Standards Manager loa@pi.nu Ericsson Inc phone: +46 10 717 52 13
> > +46 767 72 92 13
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp

From velantechie@gmail.com  Mon Feb 28 22:49:18 2011
Return-Path: <velantechie@gmail.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 118903A6DB2 for <mpls-tp@core3.amsl.com>; Mon, 28 Feb 2011 22:49:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 HcCZD3rIeq5O for <mpls-tp@core3.amsl.com>; Mon, 28 Feb 2011 22:48:55 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id E695C3A6D75 for <mpls-tp@ietf.org>; Mon, 28 Feb 2011 22:48:34 -0800 (PST)
Received: by wyb42 with SMTP id 42so4816373wyb.31 for <mpls-tp@ietf.org>; Mon, 28 Feb 2011 22:48:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=ve5uZqQM6Q3NCcQkPF1AjE414UWQkZLLTHi+zfsOFtU=; b=O0Jx8ZD5R3Zwk7MVWyYkaTPO8m79dbxgriOHH45zeLPVNFu8pGpNplXH41t1N8buBv oqvoc/b6rmbdhZuNgc4YYSqMgtEnqPCyKF+TqaO2d+yJt457W/laXQaD9iGleKQi4WZQ yFGLu9yqqGQs1uvMmiwuR4I5mw67CXdPG6h0s=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=CY0AxjS7fKQZHsy9eqkDbgDdisaMoy13og15PF0Ec7I+nMkmFF4cBfzDhKWDf5fBoZ T750pqxWiQSQfMNqlRu7TOAoRR811WpHR1L7hYguN6WFSL48uNEuLHXfi9vacWKlsB4E ywZaQb4Ne1JFe5ek7LHOu4X3Y4b75Wh3k4J08=
MIME-Version: 1.0
Received: by 10.227.143.66 with SMTP id t2mr5770284wbu.83.1298962111305; Mon, 28 Feb 2011 22:48:31 -0800 (PST)
Received: by 10.227.11.133 with HTTP; Mon, 28 Feb 2011 22:48:31 -0800 (PST)
Date: Mon, 28 Feb 2011 22:48:31 -0800
Message-ID: <AANLkTikqgFVrFaOp1Q4P0vKm9F1pZu+VC54NFj-P_zMT@mail.gmail.com>
From: Velan S <velantechie@gmail.com>
To: mpls-tp@ietf.org
Content-Type: multipart/alternative; boundary=001636832f1a3898ea049d662f0e
Subject: [mpls-tp] MPLS-TP LSP questions
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 06:49:18 -0000

--001636832f1a3898ea049d662f0e
Content-Type: text/plain; charset=ISO-8859-1

Hi Experts,

I quickly wanted to check with you all,

Can both,  MPLS-TP LSP and traditional MPLS LSP, exist in a LSR?  If both
can exist, there is possibility of merging of these LSPs at a LSR.  How can
we detect such merging LSPs?

Thanks in advance.
S.Velan

--001636832f1a3898ea049d662f0e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Hi Experts,</div>
<div>=A0</div>
<div>I quickly wanted to check with you all,</div>
<div>=A0</div>
<div>Can both, =A0MPLS-TP LSP and traditional MPLS LSP, exist in a LSR?=A0 =
If both can exist, there is possibility of merging of these LSPs at a=A0LSR=
.=A0 How can we detect such merging LSPs?</div>
<div>=A0</div>
<div>Thanks in advance.</div>
<div>S.Velan</div>
<div>=A0</div>

--001636832f1a3898ea049d662f0e--
