[Actn] 答复: ACTN progress
Zhenghaomian <zhenghaomian@huawei.com> Thu, 15 January 2015 03:08 UTC
Return-Path: <zhenghaomian@huawei.com>
X-Original-To: actn@ietfa.amsl.com
Delivered-To: actn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B399A1B2AD7 for <actn@ietfa.amsl.com>; Wed, 14 Jan 2015 19:08:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.74
X-Spam-Level: *
X-Spam-Status: No, score=1.74 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qjNpXrsbABoO for <actn@ietfa.amsl.com>; Wed, 14 Jan 2015 19:08:53 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F139F1ACED1 for <actn@ietf.org>; Wed, 14 Jan 2015 19:08:52 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BRJ04696; Thu, 15 Jan 2015 03:08:51 +0000 (GMT)
Received: from SZXEMA413-HUB.china.huawei.com (10.82.72.72) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 15 Jan 2015 03:08:50 +0000
Received: from SZXEMA504-MBX.china.huawei.com ([169.254.7.215]) by SZXEMA413-HUB.china.huawei.com ([10.82.72.72]) with mapi id 14.03.0158.001; Thu, 15 Jan 2015 11:08:41 +0800
From: Zhenghaomian <zhenghaomian@huawei.com>
To: Leeyoung <leeyoung@huawei.com>, "actn@ietf.org" <actn@ietf.org>
Thread-Topic: [Actn] ACTN progress
Thread-Index: AQHQMDTGV9eTqi8Jz0y0yoNa8orNmJzAd2Jw
Date: Thu, 15 Jan 2015 03:08:40 +0000
Message-ID: <E0C26CAA2504C84093A49B2CAC3261A438C4D961@SZXEMA504-MBX.china.huawei.com>
References: <7AEB3D6833318045B4AE71C2C87E8E1729C70587@dfweml706-chm> <eecc34a2c82e438fb09897d328c03d0a@ATL-SRV-MBX1.advaoptical.com> <7AEB3D6833318045B4AE71C2C87E8E1729C719C6@dfweml706-chm>
In-Reply-To: <7AEB3D6833318045B4AE71C2C87E8E1729C719C6@dfweml706-chm>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.66.53.113]
Content-Type: multipart/alternative; boundary="_000_E0C26CAA2504C84093A49B2CAC3261A438C4D961SZXEMA504MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/actn/47fuNcsES0Z7wNbDqW5IFyAuj6o>
Cc: Igor Bryskin <IBryskin@advaoptical.com>
Subject: [Actn] 答复: ACTN progress
X-BeenThere: actn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Abstraction and Control of Transport Networks \(ACTN\)" <actn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/actn>, <mailto:actn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/actn/>
List-Post: <mailto:actn@ietf.org>
List-Help: <mailto:actn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/actn>, <mailto:actn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jan 2015 03:08:56 -0000
Hi, Young and Igor, Thanks for the sharing, great to see a more converged architecture. From my perspective, the model work mentioned are all necessary, but it seems such model should be dependent on protocol works, i.e., we need to complete protocol first and then modeling. Parallel style is also good for protocol and model, but I prefer we turn to protocol if they have some inconsistency between protocol and model. Besides I still have some questions: In the previous mail, I am a little bit confused with the limitation on MDSC connection. It seems MDSC is not clear with who it is connecting by mentioning “MDSC should not be able to distinguish if it interfaces MDSC or PNCs (i.e., the same interface)”. My opinion is it is not necessary to limit the knowledge of MDSC, i.e., it is fine if a MDSC has the ability to detect whether it is connecting with a PNC or another MDSC. At least, a MDSC MUST have the ability to identify CNC from MDSC/PNCs. Or maybe you are saying “A PNC can become MDSC if there is recursive hierarchy? ”. I like this due to the dynamic topology growing in the network. By reading “CNC interfacing MDSC should be essentially the same interface as MDSC interfacing another MDSC or PNCs”, I feel that the functionalities on interface B and C (defined in fwk draft) are becoming similar, which quite confuse me as well. I agree that these interfaces may have similar message flow during service request, provisioning and so on, but they are quite different during OAM, recovery and resource mgmt. I don’t think it is a good idea to consider these two interface “the same as each other”. Would you please help explain the issue above? Thanks a lot. Best wishes, Haomian 发件人: Leeyoung [mailto:leeyoung@huawei.com] 发送时间: 2015年1月15日 3:12 收件人: actn@ietf.org 主题: [Actn] ACTN progress Hi All, Just wanted to share some private emails exchanged among a limited interested parties in the past week with a permission with Igor. In a nutshell, I think we are converging with a common view on ACTN interfaces and architecture. Please check the following email thread. Please comment if you have any question. Thanks, Young From: Igor Bryskin [mailto:IBryskin@advaoptical.com] Sent: Thursday, January 08, 2015 2:13 PM To: Leeyoung; Daniele Ceccarelli Cc: AshwoodsmithPeter Subject: RE: Recap this morning's call Hi Young, You’ve captured all pretty accurately. I nominate you for the ACTN scribe job :=) Igor From: Leeyoung [mailto:leeyoung@huawei.com] Sent: Thursday, January 08, 2015 3:09 PM To: Igor Bryskin; Daniele Ceccarelli Cc: AshwoodsmithPeter Subject: Recap this morning's call Hi Igor, Thanks for this morning’s call. I just wanted to recap what was agreed upon. Please feel free to correct if anything needs to be corrected. We have identified several models to be implemented in ACTN control hierarchy (CNC-MDSC-PNC). Among them are, but not limited to: 1. Topology Model 2. Provisioning Model 3. Service Model 4. OAM Model 5. Client Mapping/Policy Model There could be more to the list. We can identify and add later on if we will. Now, with these models, different components (i.e., different controller type) will implement whatever relevant models and support its interfaces. For instance, PNC may need not support Client mapping/policy model while CNC may not need to support Provisioning model. We also agree that MDSC can interface another MDSC or PNCs with transparency. MDSC should not be able to distinguish if it interfaces MDSC or PNCs (i.e., the same interface). And you also said, CNC interfacing MDSC should be essentially the same interface as MDSC interfacing another MDSC or PNCs. Let us start from here. Then we can discuss further. Thanks, Young
- [Actn] ACTN progress Leeyoung
- [Actn] 答复: ACTN progress Zhenghaomian
- Re: [Actn] ACTN progress Leeyoung
- Re: [Actn] ACTN progress 윤빈영
- [Actn] 答复: ACTN progress Zhenghaomian
- Re: [Actn] ACTN progress Igor Bryskin
- Re: [Actn] ACTN progress Leeyoung
- Re: [Actn] ACTN progress Leeyoung
- Re: [Actn] ACTN progress 윤빈영
- Re: [Actn] ACTN progress Leeyoung
- Re: [Actn] ACTN progress BELOTTI, SERGIO (SERGIO)
- Re: [Actn] ACTN progress Arashmid Akhavain
- Re: [Actn] ACTN progress Daniele Ceccarelli
- Re: [Actn] ACTN progress Dhruv Dhody
- [Actn] 答复: ACTN progress Zhenghaomian
- Re: [Actn] 答复: ACTN progress Dhruv Dhody
- [Actn] R: 答复: ACTN progress Daniele Ceccarelli
- [Actn] 答复: 答复: ACTN progress Zhenghaomian
- Re: [Actn] ACTN progress 윤빈영
- Re: [Actn] ACTN progress BELOTTI, SERGIO (SERGIO)
- Re: [Actn] 答复: 答复: ACTN progress Daniele Ceccarelli
- Re: [Actn] ACTN progress Igor Bryskin
- Re: [Actn] ACTN progress Daniele Ceccarelli
- Re: [Actn] ACTN progress Igor Bryskin
- Re: [Actn] ACTN progress Dave Hood
- Re: [Actn] ACTN progress Igor Bryskin
- Re: [Actn] ACTN progress Arashmid Akhavain
- Re: [Actn] ACTN progress Igor Bryskin
- Re: [Actn] ACTN progress Leeyoung
- Re: [Actn] ACTN progress Leeyoung
- Re: [Actn] ACTN progress Arashmid Akhavain
- Re: [Actn] ACTN progress Arashmid Akhavain
- Re: [Actn] ACTN progress Leeyoung
- Re: [Actn] ACTN progress 윤빈영
- Re: [Actn] ACTN progress Zhangxian (Xian)
- Re: [Actn] ACTN progress BELOTTI, SERGIO (SERGIO)
- [Actn] MSDC-PNC m:n (was R: ACTN progress) Daniele Ceccarelli
- Re: [Actn] MSDC-PNC m:n (was R: ACTN progress) BELOTTI, SERGIO (SERGIO)
- Re: [Actn] MSDC-PNC m:n (was R: ACTN progress) Leeyoung
- Re: [Actn] MSDC-PNC m:n (was R: ACTN progress) Leeyoung
- Re: [Actn] MSDC-PNC m:n (was R: ACTN progress) Arashmid Akhavain
- Re: [Actn] MSDC-PNC m:n (was R: ACTN progress) Arashmid Akhavain
- Re: [Actn] MSDC-PNC m:n (was R: ACTN progress) Dave Hood
- [Actn] 答复: MSDC-PNC m:n (was R: ACTN progress) Zhenghaomian
- Re: [Actn] MSDC-PNC m:n (was R: ACTN progress) 윤빈영
- Re: [Actn] MSDC-PNC m:n (was R: ACTN progress) Zhangxian (Xian)
- [Actn] R: MSDC-PNC m:n (was R: ACTN progress) Daniele Ceccarelli
- [Actn] R: MSDC-PNC m:n (was R: ACTN progress) Daniele Ceccarelli
- Re: [Actn] MSDC-PNC m:n (was R: ACTN progress) Dave Hood
- Re: [Actn] MSDC-PNC m:n (was R: ACTN progress) Daniele Ceccarelli
- Re: [Actn] MSDC-PNC m:n (was R: ACTN progress) Arashmid Akhavain