Re: [CCAMP] I-D Action: draft-ietf-ccamp-wson-yang-18.txt
Leeyoung <leeyoung@huawei.com> Fri, 07 December 2018 17:01 UTC
Return-Path: <leeyoung@huawei.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4811F130EA1 for <ccamp@ietfa.amsl.com>; Fri, 7 Dec 2018 09:01:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.589
X-Spam-Level:
X-Spam-Status: No, score=-1.589 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=no autolearn_force=no
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 zT01REwv5lkT for <ccamp@ietfa.amsl.com>; Fri, 7 Dec 2018 09:01:46 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFA81130EAE for <ccamp@ietf.org>; Fri, 7 Dec 2018 09:01:45 -0800 (PST)
Received: from lhreml705-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 2155C56B4AC5F for <ccamp@ietf.org>; Fri, 7 Dec 2018 17:01:42 +0000 (GMT)
Received: from SJCEML701-CHM.china.huawei.com (10.208.112.40) by lhreml705-cah.china.huawei.com (10.201.108.46) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 7 Dec 2018 17:01:43 +0000
Received: from SJCEML521-MBB.china.huawei.com ([169.254.6.33]) by SJCEML701-CHM.china.huawei.com ([169.254.3.198]) with mapi id 14.03.0415.000; Fri, 7 Dec 2018 09:01:34 -0800
From: Leeyoung <leeyoung@huawei.com>
To: "Aihuaguo (Aihua Guo, CRC)" <aihuaguo@huawei.com>, "Beller, Dieter (Nokia - DE/Stuttgart)" <dieter.beller@nokia.com>, "ccamp@ietf.org" <ccamp@ietf.org>
Thread-Topic: [CCAMP] I-D Action: draft-ietf-ccamp-wson-yang-18.txt
Thread-Index: AQHUjL6hoFeFYc4MWU+jA66sTwaQxKVwZIKQgANzSoCAADC8gP//ekZw
Date: Fri, 07 Dec 2018 17:01:34 +0000
Message-ID: <7AEB3D6833318045B4AE71C2C87E8E173D0A0D94@SJCEML521-MBB.china.huawei.com>
References: <154403028111.31922.11742637644752499043@ietfa.amsl.com> <7AEB3D6833318045B4AE71C2C87E8E173D0A03A9@SJCEML521-MBB.china.huawei.com> <70378e29-bbee-79bb-b6b5-65070567feb1@nokia.com> <AEF103518CA8F84D97E39F644BC803CB28A45BE8@SJCEML521-MBB.china.huawei.com>
In-Reply-To: <AEF103518CA8F84D97E39F644BC803CB28A45BE8@SJCEML521-MBB.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.192.11.123]
Content-Type: multipart/alternative; boundary="_000_7AEB3D6833318045B4AE71C2C87E8E173D0A0D94SJCEML521MBBchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/6KMIc6bHhhl6MLYKhoDftOTCc_I>
Subject: Re: [CCAMP] I-D Action: draft-ietf-ccamp-wson-yang-18.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Dec 2018 17:01:48 -0000
Hi Aihua and Dieter, One more thing to add on FEC type: Actually ITU-T G.698.2 Application Codes DScW-ytz(v) or B-DScW-ytz(v) does not mandate FEC code. It says: “An optional F can be added to indicate a FEC encoding”. Thus, I think we can add supported-fec-types here. Thanks. Young From: Aihuaguo (Aihua Guo, CRC) Sent: Friday, December 7, 2018 10:58 AM To: Beller, Dieter (Nokia - DE/Stuttgart) <dieter.beller@nokia.com>; Leeyoung <leeyoung@huawei.com>; ccamp@ietf.org Subject: RE: [CCAMP] I-D Action: draft-ietf-ccamp-wson-yang-18.txt Hi Dieter, For “supported-fec-types”, do we have all of the FEC types (standard and vendor-specific) that can be covered by the operational modes? If yes then I think we can remove this parameter. For inverse multiplexing, or “super channel”, this TTP represent all of the subcarriers of the super channel, and my understanding is usually all subcarrier channels in a super channel go through the same route and has the same optical characteristics except for different wavelength, otherwise it will be too difficult to manage and optically engineer it. For bit stuffing, it is used for mapping constant bit-rate tributary signals to ODU frame to accommodate high clock accuracies. We need to understand the capabilities for both ends of the TTPs by using the topology model and create OCH trails by coordinating this setting at both ends of the transponder. Aihua From: CCAMP [mailto:ccamp-bounces@ietf.org] On Behalf Of Beller, Dieter (Nokia - DE/Stuttgart) Sent: Friday, December 07, 2018 9:03 AM To: Leeyoung <leeyoung@huawei.com<mailto:leeyoung@huawei.com>>; ccamp@ietf.org<mailto:ccamp@ietf.org> Subject: Re: [CCAMP] I-D Action: draft-ietf-ccamp-wson-yang-18.txt Hi Young, IMO this augmentation has issues: augment /nw:networks/nw:network/nw:node/tet:te/tet:tunnel-termination-point: +-rw supported-operational-modes* layer0-types:operational-mode +-rw configured-operational-modes? layer0-types:operational-mode +-rw supported-fec-types* identityref +-rw supported-termination-types* identityref +-rw supports-bit-stuffing? boolean +-rw is-tunable? boolean +-rw max-subcarrier-channel-num? uint8 supported-operational-modes should be ro configured-operational-modes should be configured-operational-mode (without "s", singular) supported-fec-types is normally included in the supported-operational-modes max-subcarrier-channel-num: I thought that in case of inverse multiplexing, a termination-point is needed for each (sub-)carrier. There might be carrier-specific properties that differ from (sub-)carrier to (sub-)carrier. It needs to be clarified also whether the tunnel-termination-point is encompassing all (sub-)carriers that are forming an inverse multiplexing group. supports-bit-stuffing: meaning is unclear and the description below doesn't say anything where and how bit-stuffing is applied. This is a property of the mapping function that maps a client signal into a server layer frame, I suppose. leaf supports-bit-stuffing { type boolean; description "Indicates whether bit stuffing is supported by this TTP"; Thanks, Dieter On 05.12.2018 18:23, Leeyoung wrote: Hi, This revision, we hope, incorporated all comments from Tom and others. The co-authors believe that it is ready for WG LC. Thanks & best regards, Young -----Original Message----- From: CCAMP [mailto:ccamp-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> Sent: Wednesday, December 5, 2018 11:18 AM To: i-d-announce@ietf.org<mailto:i-d-announce@ietf.org> Cc: ccamp@ietf.org<mailto:ccamp@ietf.org> Subject: [CCAMP] I-D Action: draft-ietf-ccamp-wson-yang-18.txt 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 WG of the IETF. Title : A YANG Data Model for WSON (Wavelength Switched Optical Networks) Authors : Young Lee Dhruv Dhody Aihua Guo Victor Lopez Daniel King Filename : draft-ietf-ccamp-wson-yang-18.txt Pages : 77 Date : 2018-12-05 Abstract: This document provides a YANG data model for the routing and wavelength assignment (RWA) TE topology in wavelength switched optical networks (WSONs). The YANG data model defined in this document conforms to the Network Management Datastore Architecture defined in RFC 8342. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-ccamp-wson-yang/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-ccamp-wson-yang-18 https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-wson-yang-18 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-ccamp-wson-yang-18 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ CCAMP mailing list CCAMP@ietf.org<mailto:CCAMP@ietf.org> https://www.ietf.org/mailman/listinfo/ccamp _______________________________________________ CCAMP mailing list CCAMP@ietf.org<mailto:CCAMP@ietf.org> https://www.ietf.org/mailman/listinfo/ccamp
- [CCAMP] I-D Action: draft-ietf-ccamp-wson-yang-18… internet-drafts
- Re: [CCAMP] I-D Action: draft-ietf-ccamp-wson-yan… Leeyoung
- Re: [CCAMP] I-D Action: draft-ietf-ccamp-wson-yan… tom petch
- Re: [CCAMP] I-D Action: draft-ietf-ccamp-wson-yan… Beller, Dieter (Nokia - DE/Stuttgart)
- Re: [CCAMP] I-D Action: draft-ietf-ccamp-wson-yan… Aihuaguo (Aihua Guo, CRC)
- Re: [CCAMP] I-D Action: draft-ietf-ccamp-wson-yan… Leeyoung
- Re: [CCAMP] I-D Action: draft-ietf-ccamp-wson-yan… Leeyoung
- Re: [CCAMP] I-D Action: draft-ietf-ccamp-wson-yan… Leeyoung
- Re: [CCAMP] I-D Action: draft-ietf-ccamp-wson-yan… tom petch
- Re: [CCAMP] I-D Action: draft-ietf-ccamp-wson-yan… Leeyoung