Re: [CCAMP] I-D Action: draft-lee-ccamp-wson-impairment-yang-00.txt

Gert Grammel <ggrammel@juniper.net> Wed, 10 October 2018 14:42 UTC

Return-Path: <ggrammel@juniper.net>
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 16DDA130F13 for <ccamp@ietfa.amsl.com>; Wed, 10 Oct 2018 07:42:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.156
X-Spam-Level:
X-Spam-Status: No, score=-3.156 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 SNymM0B0rX0Y for <ccamp@ietfa.amsl.com>; Wed, 10 Oct 2018 07:41:59 -0700 (PDT)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 2DC2C130DD9 for <ccamp@ietf.org>; Wed, 10 Oct 2018 07:41:59 -0700 (PDT)
Received: from pps.filterd (m0108156.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w9AEdkFO030987; Wed, 10 Oct 2018 07:41:54 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=PPS1017; bh=z3zY3PjmLocpuX1L7pVq+qM9sI1itMSE7JTNtFNTKQg=; b=DttJ/84tS9ncXldzqVM77CzqGqegHctWYWyA9Fk1cChwjw95dTV15ODOYUSiPg+AySUF 0OvEH5e3Da+D9P/Isw2rCS6f+zkJQdx/Gyw4mr9jGugiC4AheAegOWrdo07mxFuUFs+E 2nLFxCoiq+Q/Q9uYNXV61X1Ln5KKdq7MkSY40N8YcJPIfrNRwVv8eO57HhHsAVtk8zQj jVkkK5q6o/d6vnf47bDZSN7pz2JViaBQyItPv7LB9bYWInxn1dhNR4kzG0AHcd1HO8dj dwkmRUvz2SDFrWYZosDWe7k9meMQEht2yG0zby2RNg3je7bYxC+qEOhMya9GwEHJFal2 Jw==
Received: from nam05-by2-obe.outbound.protection.outlook.com (mail-by2nam05lp0239.outbound.protection.outlook.com [216.32.181.239]) by mx0a-00273201.pphosted.com with ESMTP id 2n1e93rm5q-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 10 Oct 2018 07:41:53 -0700
Received: from BN7PR05MB4034.namprd05.prod.outlook.com (52.132.219.20) by BN7PR05MB3971.namprd05.prod.outlook.com (52.132.216.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1228.20; Wed, 10 Oct 2018 14:41:50 +0000
Received: from BN7PR05MB4034.namprd05.prod.outlook.com ([fe80::a54b:cedd:ecae:c780]) by BN7PR05MB4034.namprd05.prod.outlook.com ([fe80::a54b:cedd:ecae:c780%4]) with mapi id 15.20.1228.020; Wed, 10 Oct 2018 14:41:49 +0000
From: Gert Grammel <ggrammel@juniper.net>
To: Leeyoung <leeyoung@huawei.com>, "ccamp@ietf.org" <ccamp@ietf.org>
Thread-Topic: [CCAMP] I-D Action: draft-lee-ccamp-wson-impairment-yang-00.txt
Thread-Index: AQHUVkGJAJHH9ZW/WE+VJQPmsLe0P6UYYruAgAA51oCAACd3AA==
Date: Wed, 10 Oct 2018 14:41:49 +0000
Message-ID: <16D5DDC1-12C7-423F-8A3B-B72677AB68DE@juniper.net>
References: <153577337941.29073.132620799131044718@ietfa.amsl.com> <3be83a17-85af-c425-5228-b4b28eb48598@nokia.com> <ECBD0632-0CAB-4BB2-8D8F-377E5CFFE2C3@juniper.net> <7AEB3D6833318045B4AE71C2C87E8E173D0680EF@sjceml521-mbx.china.huawei.com>
In-Reply-To: <7AEB3D6833318045B4AE71C2C87E8E173D0680EF@sjceml521-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.2.180910
x-originating-ip: [193.110.55.12]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN7PR05MB3971; 6:mPNJMkg/PA0aVDvaMOFXwC9DZOQS3RUw4sMsE9BmZT5V56mRbVPyHLK0KdCBld5GAP6ru2rJudhbeLCwLNyld+Dvzcy6T+of8Cfy8JMKZXEIXCLHxjcjNEtVTy0KpWo5QCX2eKkGbBZaM1wZ3YN1RbYItLTQ30BhBxfahCezjvP0QrWAqhBd0CKwVe9thKTiFLwuVRZFmhWWG/LibDHwNBufjgeDXn0RDZc21TDcO7BjaLFL5f10K6LdOWFyYZ/KckVUVPtLpvGhsWzCDuPChLsduuK9PmiYGSrlf8lsSppqIOoBkZcHu8lTB2HQOyHW78vxJgsybd1qSGs3tkVIDjhvpyPjvQLn3m3tp+4H7wowUFYm42xQAq78qW30dRw9BpT5j0RMmc6Fx9hGwUB1UaZM/vLrCMWI7QxR3C6AGWQVFSDPkdR6M5X+z5VLdq4SBrx60s+Ak0mfl+eI5mwOUA==; 5:iQNGjDZV4usSrJ19593CPdzp/3QrVW0b1BwAZnAuS1RQw82zqsHet5J9io0qksqDDsepVz2rqvuzvixpyxDwrSX+vmHN/gYEehhixzUVzdcU2TqB/zwn5tt6BQk7C2al/T50HOr9dM9IInGkVPXOPqWNW1XMAWOJYNWWhsXNrWM=; 7:nDnclEhnbHBVklacN0cwQ/8TINZOXUaugfmuszRBR9zmgD7O6UeqSLmamAJzs7xZOzAZjiILjlD8n6iz92AiD+HRG8jND78f4j4kUaABrOYhL6SxvljzEUSsoFt3m7Ksh0GbvB3SHFlvNcWXPuxG1n6PCzHPbrikPVyw6Vu6vl27Q/21Yk9qpnYpnBUKNfOGlXK9TJ4GEY+lAA8/7mitX1WDxwV3pbjFnSSV6Y++iObHBgVGiuvyHxpO/bxBHfls
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 08ca869b-5a87-4e3c-e2d2-08d62ebe8311
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:BN7PR05MB3971;
x-ms-traffictypediagnostic: BN7PR05MB3971:
x-microsoft-antispam-prvs: <BN7PR05MB3971FF55A6E97904FCA28570CEE00@BN7PR05MB3971.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(50582790962513)(138986009662008)(82608151540597)(109105607167333)(195916259791689)(131327999870524)(120809045254105)(21748063052155)(28532068793085)(190501279198761);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3002001)(3231355)(944501410)(4982022)(52105095)(6055026)(149066)(150057)(6041310)(20161123558120)(20161123564045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(201708071742011)(7699051)(76991055); SRVR:BN7PR05MB3971; BCL:0; PCL:0; RULEID:; SRVR:BN7PR05MB3971;
x-forefront-prvs: 08213D42D3
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(136003)(366004)(39860400002)(396003)(346002)(189003)(199004)(86362001)(25786009)(3846002)(606006)(966005)(478600001)(6116002)(76176011)(2900100001)(2616005)(6506007)(476003)(53546011)(105586002)(6246003)(71200400001)(7736002)(4326008)(8936002)(82746002)(68736007)(2906002)(83716004)(14454004)(71190400001)(81166006)(36756003)(5660300001)(256004)(53936002)(53946003)(8676002)(110136005)(54906003)(2501003)(33656002)(236005)(14444005)(6306002)(6486002)(6436002)(6512007)(54896002)(229853002)(5250100002)(97736004)(26005)(6346003)(66066001)(102836004)(99286004)(486006)(316002)(81156014)(106356001)(58126008)(93886005)(11346002)(446003)(186003)(579004); DIR:OUT; SFP:1102; SCL:1; SRVR:BN7PR05MB3971; H:BN7PR05MB4034.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: uHduAmeStFofSrpuWUkniZPjYynzc8zQajtObvDIYA/d6LJT6bvBs+OzBNrQP1ujv1hokfeCTP55U/Vmp1wSZ+e6c/gX/m6AoJw1p5+YHOotxZdqVWEILuezHO8v9IWOBeuk3a5CGc2N8tbx4WXzmjS0IhOyVGmh5FequGMOrxrhZ1wpRMebHvsL7OAMSQrbImA1vLjHz14PxdrzdaUb9Bph7ger1+NDcKN8GumrBRyH4nfSXuVgSqyI8GaXCcWjTk92w9U6ao9l/egQVbMlEB9a0ggzAPCIPxxmmo/WRgTJiiDu0CyqGpxHqmKR03PndsMiWIklUe8dyV7L3cJTf5sBSuK4G71CiDE0DuFGha0=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_16D5DDC112C7423F8A3BB72677AB68DEjunipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 08ca869b-5a87-4e3c-e2d2-08d62ebe8311
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Oct 2018 14:41:49.6284 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN7PR05MB3971
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-10-10_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1810100145
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/S9t6sJ9Bd04OLV1MGAnXyj0VC64>
Subject: Re: [CCAMP] I-D Action: draft-lee-ccamp-wson-impairment-yang-00.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: Wed, 10 Oct 2018 14:42:04 -0000

Yang,

I was referring to
augment /nw:networks/nw:network/nw:node/tet:te/tet:tunnel-termination-point:
       +--ro available-modulation*   identityref
       +--ro modulation-enabled?     boolean
       +--ro modulation-type?        identityref
       +--ro available-FEC*          identityref
       +--ro FEC-enabled?            boolean
       +--ro FEC-type?               identityref
       +--ro FEC-code-rate?          decimal64
       +--ro FEC-threshold?          decimal64

For example:
The modulation is part of the application code (from the actual G.698.2 a bit shortened for readability):
The application code notation is constructed as follows: DScW-ytz(v)
where,
D is the indicator of DWDM applications.
S indicates options of maximum spectral excursion such as:
·         –  N indicating narrow spectral excursion.
·         –  W indicating wide spectral excursion. c is the channel spacing in GHz.
W indicates the black link dispersion compensation regime as follows:
·         –  C indicating that the chromatic dispersion values are appropriate to a black link that is
dispersion compensated.
·         –  U indicating that the chromatic dispersion values are appropriate to a black link that is dispersion uncompensated.
y indicates the highest class of optical tributary signal supported:
o    –  1 indicating NRZ 2.5G.
o    –  2 indicating NRZ 10G.
t is a letter indicating the configuration supported by the application code. In the current version of this Recommendation, the only value used is:
– A indicating that the black link may contain optical amplifiers. z indicates the fibre types, as follows:
·         –  2 indicating ITU-T G.652 fibre.
·         –  3 indicating ITU-T G.653 fibre.
·         –  5 indicating ITU-T G.655 fibre.
v indicates the operating wavelength range in terms of spectral bands (see [b-ITU-T G-Sup.39]):
If more than one spectral band is used, then v becomes the band letters separated by "+", e.g., for an application requiring the use of both of the C and L bands, v would be "C+L".
For some application codes, a suffix is added to the end of the code. The only suffix currently defined is:
– F to indicate that this application requires FEC bytes as specified in [ITU-T G.709] to be transmitted.

So under the assumption the application code is defined for the tunnel termination point:
augment /nw:networks/nw:network/nw:node/tet:te/tet:tunnel-termination-point:
       +--ro available-modulation*   identityref --> Parameter y
       +--ro modulation-enabled?     Boolean --> the code defines only one modulation, not enabled/disabled
       +--ro modulation-type?        Identityref --> parameter y
       +--ro available-FEC*          identityref --> parameter F is a Boolean
       +--ro FEC-enabled?            Boolean  --> enabled/disabled would result in two different application codes (with and without tailing F)
       +--ro FEC-type?               Identityref --> F
       +--ro FEC-code-rate?          decimal64 --> since F is defined, this one is defined too
       +--ro FEC-threshold?          decimal64 --> since F is defined, this one is defined too


Best

Gert


From: 'Leeyoung' <leeyoung@huawei.com>;
Date: Wednesday, October 10, 2018 at 16:21
To: Gert Grammel <ggrammel@juniper.net>;, CCAMP <ccamp@ietf.org>;
Cc: Dieter Beller <Dieter.Beller@nokia.com>;, "Zhenghaomian (Zhenghaomian, Optical &Microwave Technology Research Dept)" <zhenghaomian@huawei.com>;
Subject: RE: [CCAMP] I-D Action: draft-lee-ccamp-wson-impairment-yang-00.txt

Hi Gert,

In the current WSON model, we have the following:

augment /nw:networks/nw:network/nw:node/tet:te/tet:tunnel-termination-point:
    +--rw supported-operational-modes*    te-wson-types:operational-mode
    +--rw configured-operational-modes?   te-wson-types:operational-mode
    +--rw supported-fec-types*            identityref
    +--rw supported-termination-types*    identityref
    +--rw supports-bit-stuffing?          boolean

So we are describing application codes in the TTP. Is this what you meant to describe application code in the Termination Point?

Thanks.
Young

From: Gert Grammel [mailto:ggrammel@juniper.net]
Sent: Wednesday, October 10, 2018 3:54 AM
To: ccamp@ietf.org
Cc: Dieter Beller <Dieter.Beller@nokia.com>;; Leeyoung <leeyoung@huawei.com>;; Zhenghaomian (Zhenghaomian, Optical &Microwave Technology Research Dept) <zhenghaomian@huawei.com>;
Subject: Re: [CCAMP] I-D Action: draft-lee-ccamp-wson-impairment-yang-00.txt


The draft triggered a question about the approach we are using in ccamp to address WSON going forward. In the past, the group aimed for alignment with ITU-T and using application codes to describe optical capabilities. Is this still the way forward?
If so, my expectation would be to find application codes as description of termination points.
If the view changed, it should be spelled out.

Gert


From: CCAMP <ccamp-bounces@ietf.org<mailto:ccamp-bounces@ietf.org>> on behalf of Dieter Beller <Dieter.Beller@nokia.com<mailto:Dieter.Beller@nokia.com>>
Organization: Nokia
Date: Thursday, September 27, 2018 at 11:07
To: 'Leeyoung' <leeyoung@huawei.com<mailto:leeyoung@huawei.com>>, Zhenghaomian <zhenghaomian@huawei.com<mailto:zhenghaomian@huawei.com>>
Cc: CCAMP <ccamp@ietf.org<mailto:ccamp@ietf.org>>
Subject: Re: [CCAMP] I-D Action: draft-lee-ccamp-wson-impairment-yang-00.txt

Hi Young and Haomian,

I had a look at draft-lee-ccamp-wson-impairment-yang-00, which you submitted a few weeks ago and I have the following concerns:

The abstract and introduction states:

Abstract



   This document provides a YANG data model for the impairment-aware TE

   topology in wavelength switched optical networks (WSONs).


1. Introduction



   ...



   This document provides a YANG data model for the impairment-aware

   Traffic Engineering (TE) topology in wavelength switched optical

   networks (WSONs). The YANG model described in this document is a

   WSON technology-specific Yang model based on the information model

   developed in [RFC7446<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc7446&d=DwMDaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=Sf-T94Aod4TTEURQzTXYYw-Q-H8PyeOsweqqcNyVIcU&m=zk3zS00lx60_LBxIKggxhMkHsPCBJ4biAFdpDYpeTGA&s=t3EVJKIBbfBziQCv67C_SIGqCsL1lLO5QfzEzD1wC0Y&e=>;] and the two encoding documents [RFC7581<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc7581&d=DwMDaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=Sf-T94Aod4TTEURQzTXYYw-Q-H8PyeOsweqqcNyVIcU&m=zk3zS00lx60_LBxIKggxhMkHsPCBJ4biAFdpDYpeTGA&s=S4OUJ2my7xLw9DxcGX9NUyph3GbY44XOtQud1wwYp-A&e=>;] and

   [RFC7579<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc7579&d=DwMDaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=Sf-T94Aod4TTEURQzTXYYw-Q-H8PyeOsweqqcNyVIcU&m=zk3zS00lx60_LBxIKggxhMkHsPCBJ4biAFdpDYpeTGA&s=V6LYiY4JVdT0RvJb6BoDJ0MWyLwIBz-nlotLCl8iNWk&e=>;] that developed protocol independent encodings based on

   [RFC7446<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc7446&d=DwMDaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=Sf-T94Aod4TTEURQzTXYYw-Q-H8PyeOsweqqcNyVIcU&m=zk3zS00lx60_LBxIKggxhMkHsPCBJ4biAFdpDYpeTGA&s=t3EVJKIBbfBziQCv67C_SIGqCsL1lLO5QfzEzD1wC0Y&e=>;].



Based on this scope, I was expecting that this I-D provides te-link augmentations for WSON networks.
Examples of WSON specific te-link attributes are fiber type, spectrum availability, chromatic dispersion, PMD, PDL, OSNR contribution (if the link includes ILAs) just to list a few.

However, the only te-link augmentation is:

     augment /nw:networks/nw:network/nt:link/tet:te/tet:te-link-attributes:

       +--ro power?   int32

It is also reasonable to define WSON augmentations for termination points representing the line side of optical transponders as they can be considered as topological elements
even if these attributes are not representing optical impairments!:

     augment /nw:networks/nw:network/nw:node/tet:te/tet:tunnel-termination-point:

       +--ro available-modulation*   identityref

       +--ro modulation-enabled?     boolean

       +--ro modulation-type?        identityref

       +--ro available-FEC*          identityref

       +--ro FEC-enabled?            boolean

       +--ro FEC-type?               identityref

       +--ro FEC-code-rate?          decimal64

       +--ro FEC-threshold?          decimal64


I don't understand why all the OT attributes are defined as ro attributes. State of the art OTs typically provide multiple operational modes. Hence, these attributes should
be defined as rw attributes.


All other augmentations are defined for paths (te-tunnels) or termination points, which is a bit strange! Here are two examples:

     augment /nw:networks/nw:network/nt:link/tet:te/tet:te-link-

   attributes/tet:underlay/tet:primary-path/tet:path-

   element/tet:type/tet:label/tet:label-hop/tet:te-label/tet:technology:

       +--:(wson-imp-topo)

          +--rw (grid-type)?

          |  +--:(dwdm)

          |  |  +--ro channel-freq?         decimal64

          |  +--:(cwdm)

          |     +--ro channel-wavelength?   uint32

          +--ro bit-rate?             decimal64

          +--ro BER?                  decimal64

          +--ro pmd?                  decimal64

          +--ro cd?                   decimal64

          +--ro osnr?                 decimal64

          +--ro q-factor?             decimal64

channel-freq/channel-wavelength, bit-rate, BER are definitively service (te-tunnel) attributes and do not represent optical impairments for a WSON network topology.
For pmd, cd, and q-factor (definition?), it looks like these are attributes for all the links along the path. Why are these impairments defined for a path and are not te-link
augmentations?

I was expecting that this draft defines optical impairments for the topological entities in a WSON network where optical impairments matter. Could you please clarify.


Thanks,
Dieter


On 01.09.2018 05:42, internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> wrote:

A New Internet-Draft is available from the on-line Internet-Drafts directories.





        Title           : A Yang Data Model for Impairment-Aware WSON Optical Networks

        Authors         : Young Lee

                          Haomian Zheng

  Filename        : draft-lee-ccamp-wson-impairment-yang-00.txt

  Pages           : 18

  Date            : 2018-08-31



Abstract:

   This document provides a YANG data model for the impairment-aware TE

   topology in wavelength switched optical networks (WSONs).









The IETF datatracker status page for this draft is:

https://datatracker.ietf.org/doc/draft-lee-ccamp-wson-impairment-yang/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dlee-2Dccamp-2Dwson-2Dimpairment-2Dyang_&d=DwMDaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=Sf-T94Aod4TTEURQzTXYYw-Q-H8PyeOsweqqcNyVIcU&m=zk3zS00lx60_LBxIKggxhMkHsPCBJ4biAFdpDYpeTGA&s=uI9XVdKyAYxfJxgBNbJzFb7PcL4ucbR7pQ3vwpUtFww&e=>



There are also htmlized versions available at:

https://tools.ietf.org/html/draft-lee-ccamp-wson-impairment-yang-00<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dlee-2Dccamp-2Dwson-2Dimpairment-2Dyang-2D00&d=DwMDaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=Sf-T94Aod4TTEURQzTXYYw-Q-H8PyeOsweqqcNyVIcU&m=zk3zS00lx60_LBxIKggxhMkHsPCBJ4biAFdpDYpeTGA&s=9LRKj19B6QDmn2a-h5BQmCAtnorDM8ZXdbZeH9OrK3U&e=>

https://datatracker.ietf.org/doc/html/draft-lee-ccamp-wson-impairment-yang-00<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_html_draft-2Dlee-2Dccamp-2Dwson-2Dimpairment-2Dyang-2D00&d=DwMDaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=Sf-T94Aod4TTEURQzTXYYw-Q-H8PyeOsweqqcNyVIcU&m=zk3zS00lx60_LBxIKggxhMkHsPCBJ4biAFdpDYpeTGA&s=yYQwBhf6k5pjyQs5AzU42jJPSWagS6hRERQh6xmBKpQ&e=>





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/<https://urldefense.proofpoint.com/v2/url?u=ftp-3A__ftp.ietf.org_internet-2Ddrafts_&d=DwMDaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=Sf-T94Aod4TTEURQzTXYYw-Q-H8PyeOsweqqcNyVIcU&m=zk3zS00lx60_LBxIKggxhMkHsPCBJ4biAFdpDYpeTGA&s=INR37WxNxA8xTIwaS6H619I9PtANk9yce9uZ5K0JUPo&e=>



_______________________________________________

I-D-Announce mailing list

I-D-Announce@ietf.org<mailto:I-D-Announce@ietf.org>

https://www.ietf.org/mailman/listinfo/i-d-announce<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_i-2Dd-2Dannounce&d=DwMDaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=Sf-T94Aod4TTEURQzTXYYw-Q-H8PyeOsweqqcNyVIcU&m=zk3zS00lx60_LBxIKggxhMkHsPCBJ4biAFdpDYpeTGA&s=y7F8N-yRSsfKTyuRhcdGIldonUXJm1JjYAVeCDOpKGA&e=>

Internet-Draft directories: http://www.ietf.org/shadow.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ietf.org_shadow.html&d=DwMDaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=Sf-T94Aod4TTEURQzTXYYw-Q-H8PyeOsweqqcNyVIcU&m=zk3zS00lx60_LBxIKggxhMkHsPCBJ4biAFdpDYpeTGA&s=3I5S3Q84_0hym70TgOlwjPHUfcqCWflXKfQQNwLIdTE&e=>

or ftp://ftp.ietf.org/ietf/1shadow-sites.txt<https://urldefense.proofpoint.com/v2/url?u=ftp-3A__ftp.ietf.org_ietf_1shadow-2Dsites.txt&d=DwMDaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=Sf-T94Aod4TTEURQzTXYYw-Q-H8PyeOsweqqcNyVIcU&m=zk3zS00lx60_LBxIKggxhMkHsPCBJ4biAFdpDYpeTGA&s=nqyp7tceQcl0YDvaQkoXSngBC3d39UaNlPP564Bjj0A&e=>