Re: [CCAMP] layer 0 type versioning

Daniele Ceccarelli <> Thu, 09 May 2019 13:51 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9A89D1202AB for <>; Thu, 9 May 2019 06:51:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id lKimg4_ECa7b for <>; Thu, 9 May 2019 06:51:31 -0700 (PDT)
Received: from ( [IPv6:2a01:111:f400:fe02::606]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4C1C71201F8 for <>; Thu, 9 May 2019 06:51:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=By/saDK5XsajVu1+C10OOrKoBaURZjZONRQuekhXU6I=; b=jyIdgsNe2o/vILtdXlhGrGFBh81Q+om6wdTTG+ypqW22H3b9d0OB1yPx7e8cf+mSdnGksc3CXu8Kfm7wn0l8+DfNk9HYDkrpoBYdq15P5JWzAtk9aN5dwa3sPfRn5fPrM9DSP7AKV1NS+gL1MRW+l/27l3Eq6zTAyo5gOVehz/8=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1878.18; Thu, 9 May 2019 13:51:28 +0000
Received: from ([fe80::4822:6daf:1994:3b30]) by ([fe80::4822:6daf:1994:3b30%3]) with mapi id 15.20.1878.019; Thu, 9 May 2019 13:51:28 +0000
From: Daniele Ceccarelli <>
To: Leeyoung <>, "CCAMP (" <>, Fatai Zhang <>
Thread-Topic: layer 0 type versioning
Thread-Index: AdUF48x2Wij6BRWCTXuzzIPERW/foAAgFLYgAAHYqvAAAKczIA==
Date: Thu, 9 May 2019 13:51:28 +0000
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
authentication-results: spf=none (sender IP is );
x-originating-ip: []
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 7928c0f2-dfca-4cbf-701e-08d6d4856fb2
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(49563074)(7193020); SRVR:AM0PR07MB5347;
x-ms-traffictypediagnostic: AM0PR07MB5347:
x-microsoft-antispam-prvs: <>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 003245E729
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(366004)(346002)(376002)(396003)(39860400002)(189003)(199004)(186003)(110136005)(66066001)(11346002)(44832011)(7696005)(99286004)(76176011)(476003)(446003)(486006)(66946007)(25786009)(99936001)(6246003)(256004)(71190400001)(71200400001)(66476007)(66616009)(66556008)(64756008)(73956011)(66446008)(76116006)(86362001)(229853002)(74316002)(7116003)(68736007)(53936002)(81156014)(81166006)(8676002)(5660300002)(236005)(9686003)(6436002)(33656002)(52536014)(54896002)(55016002)(6306002)(6116002)(790700001)(3846002)(102836004)(478600001)(2906002)(14454004)(4001150100001)(8936002)(7736002)(26005)(316002)(6506007)(53546011); DIR:OUT; SFP:1101; SCL:1; SRVR:AM0PR07MB5347;; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None ( does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 9gwXRkJfxBSPxUTt3IqX5Kk5aLc+rFxG5Ey73IhgLHkSjT6hIHT6k2Lks5WMkAxdBDZPY7nlAariVCTy/7WiiorkL+tnys31IlCn/gCbAdg5T0BTBj0C2gBTIBJtexcqgAV3+fAVNA6377l3Ie5HvfZ2sCJiSQ9s3LPEVvbaH78s9V65+V6iSrWm7NUhwLC+5UxhkkT8o1swESRZMd+nfsXMK9zKmyaC28dwURdNCTQZ0jLk2Vbabru5GLhbqerBoKRZqF2hskUvoGrREQBfQ7PxJgATBnF1hD3GJWRF1cjG5aCr0iqIHdnvu/0gy2ZYkAByJjOvtBZ0XzDkE+RBFoIfeT3H2txObBbt928vMcTUqYZEIPStu2qUFOGeZgr2533ga3Ad94qJS5tenUEionp0nOSiadAN891U0bmt144=
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_017A_01D5067F.0F672990"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 7928c0f2-dfca-4cbf-701e-08d6d4856fb2
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 May 2019 13:51:28.8448 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR07MB5347
Archived-At: <>
Subject: Re: [CCAMP] layer 0 type versioning
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion list for the CCAMP working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 09 May 2019 13:51:37 -0000

Ah ok,


I misunderstood this sentence: I will publish soon the two drafts (one for
WSON topo and another for layer0-types).

One is the actual WSON draft (that I see you've already updated). I thought
you were talking about 2 new draft. 


Great, thanks!




From: Leeyoung <>; 
Sent: den 9 maj 2019 15:40
To: Daniele Ceccarelli <>;; CCAMP
( <>;; Fatai Zhang <>;
Subject: RE: layer 0 type versioning


Hi Daniele,


Here we are talking about one single document for layer0-types to define all
groupings and data types that are used by WSON and SSON and possibly used by
any other layer0 related draft such as the upcoming optical impairment





From: Daniele Ceccarelli [] 
Sent: Thursday, May 9, 2019 7:43 AM
To: Leeyoung < <> >; CCAMP
( <> ) <
<> >; Fatai Zhang <
<> >
Subject: RE: layer 0 type versioning


Hi Young,


Ok, please do so.

Just one question (maybe we already discussed it but I don't
that case apologies in advance): why one document for WSON topo and one for
layer0-types? In TEAS there is a single document for TE types.





From: Leeyoung < <> > 
Sent: den 8 maj 2019 23:37
To: CCAMP ( <> ) <
<> >; Fatai Zhang <
<> >; Daniele Ceccarelli
< <> >
Subject: layer 0 type versioning


Hi WG,


In the Prague meeting, in regard to ietf-layer0-type, the conclusion was
converged toward having a separate draft for keeping ietf-layer0-types file
from WSON topology draft (similar to what te-types did for TE
topology/tunnel). As Italo suggested, I think it is sound to create
different versions of ietf-layer0-types while the current version can move
with WSON and Flexi-grid drafts. If we need change/add new
grouping/parameters in the future, we can create a new version of
ietf-layer0-types (with a new date, e.g.,  ietf-layer0-types@2020-10-10) to
differentiate from the last version. This way, we can manage different
versions of types file and avoid drafts from getting stuck with MISSREF in
the RFC Queue.


So the action is to separate ietf-layer0-types from the WSON topology draft
into a separate draft with a proposed draft name:
draft-ietf-ccamp-layer0-types (once rectified by the chairs). I will publish
soon the two drafts (one for WSON topo and another for layer0-types). Please
let us know if you have any comment/concern on this action. 



Young (on behalf of co-authors)