Re: [mpls-tp] mpls-tp-dicover

Scott Mansfield <scott.mansfield@ericsson.com> Fri, 13 November 2009 02:32 UTC

Return-Path: <scott.mansfield@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 B49EB28C148 for <mpls-tp@core3.amsl.com>; Thu, 12 Nov 2009 18:32:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.387
X-Spam-Level:
X-Spam-Status: No, score=-0.387 tagged_above=-999 required=5 tests=[AWL=-1.191, BAYES_50=0.001, J_CHICKENPOX_47=0.6, 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 4LRlPYM87wcf for <mpls-tp@core3.amsl.com>; Thu, 12 Nov 2009 18:32:19 -0800 (PST)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id 606543A6A33 for <mpls-tp@ietf.org>; Thu, 12 Nov 2009 18:32:19 -0800 (PST)
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id nAD2WlHB017009; Thu, 12 Nov 2009 20:32:48 -0600
Received: from eusrcmw750.eamcs.ericsson.se ([138.85.77.50]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Thu, 12 Nov 2009 20:31:56 -0600
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Thu, 12 Nov 2009 20:31:55 -0600
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.35]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Thu, 12 Nov 2009 21:31:54 -0500
From: Scott Mansfield <scott.mansfield@ericsson.com>
To: Adrian Farrel <adrian@olddog.co.uk>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Date: Thu, 12 Nov 2009 21:30:28 -0500
Thread-Topic: [mpls-tp] mpls-tp-dicover
Thread-Index: AcpkBvPpbYUnQ+hDRKeebBPCLkIhrwAAdnQw
Message-ID: <FDC72027C316A44F82F425284E1C4C32011279124B@EUSAACMS0701.eamcs.ericsson.se>
References: <OFF1498A12.8EC901D6-ON4825766D.000561F9-4825766D.00059D4D@zte.com.cn> <819FE42E4B6D4B78AC76D9D96C6AE609@your029b8cecfe>
In-Reply-To: <819FE42E4B6D4B78AC76D9D96C6AE609@your029b8cecfe>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginalArrivalTime: 13 Nov 2009 02:31:55.0454 (UTC) FILETIME=[776C25E0:01CA6409]
Subject: Re: [mpls-tp] mpls-tp-dicover
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, 13 Nov 2009 02:32:20 -0000

The plug and play discovery and the network topology discovery description belongs in the NM framework document.  The verification of configuration functionality is something that can be done in an NMS solution, but doesn't necessarily need to be described in the framework document.

-scott. 

-----Original Message-----
From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf Of Adrian Farrel
Sent: Thursday, November 12, 2009 9:13 PM
To: mpls-tp@ietf.org; chen.qiaogang@zte.com.cn
Subject: Re: [mpls-tp] mpls-tp-dicover

Hi thanks for these.

My point at the microphone (which seemed to cause some confusion) was to ask for a separation between...
a. plug and play discovery
b. verification of configuration
c. network topology discovery

For c. we have control plane IGP or management plane (we could use OAM as well, but that would be reinventing routing and inserting it into OAM!)

For b. We have control plane (we could add OAM if there is a requirement - but I would resist the idea of completely reinventing the control plane and putting it into OAM)

For a. *if* this function is required (we have not yet established that there is support for your requirements) we could use existing plug and play discovery protocols (PPP NLC - see current G.7714, LMP discovery (see old
G.7714)

Cheers,
Adrian

----- Original Message -----
From: <chen.qiaogang@zte.com.cn>
To: <mpls-tp@ietf.org>
Sent: Friday, November 13, 2009 1:02 AM
Subject: [mpls-tp] mpls-tp-dicover


> Hello All,
>     Here attached my presentation and Internet Draft this moring. Please
> take a look.
> For the questions arose this moring, I will consider it and respond soon.
> Regards.
>
>
>
> -----------------------------------------------
> Wireline NM Platform System Design Dept.
> ZTE Corporation
> FAX:+86-755-26773583
> TEL:+86-755-26770000-3840
> Mobile:18603018937 13077888087
> E_mail:chen.qiaogang@zte.com.cn
> Addr:Network Management Center. R&D Building 3
>     ZTE Industrial Park, XiLi LiuXian Rd.
>     NanShan District, ShenZhen, China.
> Addr:深圳南山西丽留仙大道中兴通讯工业园研3楼网管中心系统部
> Post:518055
> -----------------------------------------------
>
>
> --------------------------------------------------------
> 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.
>


--------------------------------------------------------------------------------


> _______________________________________________
> 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