Re: [mpls] Question on scope of draft-frost-mpls-loss-delay-00

Stewart Bryant <stbryant@cisco.com> Mon, 20 December 2010 14:27 UTC

Return-Path: <stbryant@cisco.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8807D3A69FC; Mon, 20 Dec 2010 06:27:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.533
X-Spam-Level:
X-Spam-Status: No, score=-110.533 tagged_above=-999 required=5 tests=[AWL=0.066, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 hYzJspzGQfGq; Mon, 20 Dec 2010 06:27:51 -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 859573A69B2; Mon, 20 Dec 2010 06:27:51 -0800 (PST)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="4.60,202,1291593600"; d="scan'208";a="195120586"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 20 Dec 2010 14:29:45 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id oBKETiT7019578; Mon, 20 Dec 2010 14:29:44 GMT
Received: from stbryant-mac2.lan (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id oBKETg816318; Mon, 20 Dec 2010 14:29:42 GMT
Message-ID: <4D0F6855.2000806@cisco.com>
Date: Mon, 20 Dec 2010 14:29:41 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Greg Mirsky <gregimirsky@gmail.com>
References: <AANLkTimOe8veJW_RK6ZJfkaqXPrA1Szo=0Vtaj0w5iwR@mail.gmail.com>
In-Reply-To: <AANLkTimOe8veJW_RK6ZJfkaqXPrA1Szo=0Vtaj0w5iwR@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: mpls@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls] Question on scope of draft-frost-mpls-loss-delay-00
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Dec 2010 14:27:52 -0000

On 20/12/2010 03:34, Greg Mirsky wrote:
> Dear Dan and Stewart,
> bullet two in Introduction and Section 2.7.1 Type of Channels list 
> only link (section, LSP or a PW as channels over which LM and DM could 
> be conducted. But the Section 2.7.4 Intermediate Nodes describes 
> operation of LM and DM by using TTL exception method. Though LM and DM 
> operation does not differentiate whether querier and addressee are MEP 
> or MIP reference to use of TTL implies to LM/DM directed at MIP. I 
> view it as case of Segment. Do you see that querier might be MIP as 
> well or LM/DM on generic Segment can be performed only with SPME?
>
> Regards,
> Greg
In MPLS  I can see no reason why one could not make the measurement 
between any two nodes on the LSP using the TTL method.

Within the MPLS-TP of this, the convention is to only initiate the OAM 
exchange at an LSP endpoint, thus requiring an SPME to monitor the 
traffic between a pair of midpoint LSRs. We may need to add some text on 
this in the MPLS-TP for loss-delay.

- Stewart