[mpls-tp] Questions on MPLS-TP Sections (draft-ietf-mpls-tp-rosetta-stone-03)
wei.hongbo@zte.com.cn Thu, 02 December 2010 07:13 UTC
Return-Path: <wei.hongbo@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 6D6553A68C1 for <mpls-tp@core3.amsl.com>;
Wed, 1 Dec 2010 23:13:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.938
X-Spam-Level:
X-Spam-Status: No, score=-100.938 tagged_above=-999 required=5 tests=[AWL=0.300,
BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_42=0.6,
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 XV3yp997Udip for
<mpls-tp@core3.amsl.com>; Wed, 1 Dec 2010 23:13:26 -0800 (PST)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by
core3.amsl.com (Postfix) with ESMTP id 64C7C28C0CF for <mpls-tp@ietf.org>;
Wed, 1 Dec 2010 23:13:01 -0800 (PST)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id
20595764009499; Thu, 2 Dec 2010 14:39:44 +0800 (CST)
Received: from [10.30.3.19] by [192.168.168.15] with StormMail ESMTP id
55813.6109586863; Thu, 2 Dec 2010 14:43:08 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with
ESMTP id oB26gt8v097967;
Thu, 2 Dec 2010 14:42:56 +0800 (CST) (envelope-from wei.hongbo@zte.com.cn)
To: hhelvoort@huawei.com, loa.andersson@ericsson.com, nurit.sprecher@nsn.com,
matthew.bocci@alcatel-lucent.com, swallow@cisco.com, eric.gray@ericsson.com
MIME-Version: 1.0
Importance: High
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OF9B6C6BB3.88D4BF89-ON482577ED.002045D9-482577ED.0024EA19@zte.com.cn>
From: wei.hongbo@zte.com.cn
Date: Thu, 2 Dec 2010 14:40:07 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July
25, 2010) at 2010-12-02 14:42:43, Serialize complete at 2010-12-02 14:42:43
Content-Type: multipart/alternative;
boundary="=_alternative 0024EA14482577ED_="
X-MAIL: mse2.zte.com.cn oB26gt8v097967
Cc: mpls-tp@ietf.org
Subject: [mpls-tp] Questions on MPLS-TP Sections
(draft-ietf-mpls-tp-rosetta-stone-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, 02 Dec 2010 07:14:09 -0000
Hello All,
I have some questions on MPLS-TP Sections. In
draft-ietf-mpls-tp-rosetta-stone-03 "section 3.14 Section Layer Network"
written:
>>>A section layer is a server layer (which may be MPLS-TP or a
>>>different technology) that provides for the transfer of the section-
>>>layer client information between adjacent nodes in the transport-
>>>path layer or transport-service layer. A section layer may provide
>>>for aggregation of multiple MPLS-TP clients. Note that [ITU-
>>>T_G.805] defines the section layer as one of the two layer networks
>>>in a transmission-media layer network. The other layer network is
>>>the physical-media layer network.
>>>Section layer networks are concerned with all the functions which
>>>provide for the transfer of information between locations in path
>>>layer networks.
>>>Physical media layer networks are concerned with the actual fibres,
>>>metallic wires or radio frequency channels which support a section
>>>layer network.
Q1: what is MPLS-TP Section's Identifiers? (MAC address or IP address or
something else?)
IMO, MPLS-TP is co-ps technology, so we MUST collect context from
packets. In LSP Layer, the LSP's In-Label provide that; In PW layer, the
PW's In-Label provide that;In Section layer, I think it should be the MAC
Address to do the same thing.(eg, ethernet interface)
Q2: Do we need to provide Sections between logical interfaces?
On some PTN devices, we have logical interfaces (eg, VLAN interface,
have IP address) and physical interface (eg, FEI interface, have NO IP
address). If we provide Sections between logical interfaces, Does that
mean we will use IP address to identify Section Entity?
Q3: Recently, I noticed that Cisco's CPT600 have supported MPLS-TP OAM;
Can Cisco's expert give some advice about this?
Best regards,
steven
--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.