Re: [CCAMP] YANG prefix for flexi-grid (was RE: FW: Proposal for YANG model prefix naming)

tom petch <ietfc@btconnect.com> Thu, 01 April 2021 15:40 UTC

Return-Path: <ietfc@btconnect.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 1B52F3A1926 for <ccamp@ietfa.amsl.com>; Thu, 1 Apr 2021 08:40:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
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 endVLwxSGxZ3 for <ccamp@ietfa.amsl.com>; Thu, 1 Apr 2021 08:40:13 -0700 (PDT)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-eopbgr70119.outbound.protection.outlook.com [40.107.7.119]) (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 94A9B3A1922 for <ccamp@ietf.org>; Thu, 1 Apr 2021 08:40:08 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=YckTIT+DFGUBlJgG/CLunpF7+vA2CIwNJdIdtVNM+i973UvMnRKAxzCu7C9UvV639g50K7qwvuBHsaAlkomwzVgKKnxZ/8SRgpAb7n/eEJ4ODdepfSYTjDfp7GMUjsgm9GXlqU/ibnBjyfACTyKNGbBOIPqeaIELpoPftlLs6/tZPirxW2v7jXg9x0nhwjyIfs09Ux6UgCX1vbytPLfLzNB4XRGvrB4HGF2gPTxqZqXK5yKZFGzC1CMTH8BDiOO7EkNAC9bbNbddNKUD1MS+RBJJ1BPwwPngQBWWfkwJkSXqI93xuBYRk+JfGLPRRdT8y5VpZJW/Ggswb3K5sS7eUA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=jEqX3/RFI+C3cc+5HXqR7jOhOrLNsiostejo2DewZIU=; b=FyPzOHW21FO30Xtqsa4qtT3jYf7Z4CbGqzQ1gpc0xvjYkGxdxXu0zzTxR9/Eu9d09cQzuTwLAZtkctZNIw9xfEzrfSKpGZYMEGgJ1yvyrWaMVshcs9dce989wqaRfNVmP2TZZvEuoaYZm6qXpOX0sghW5Xv2MpRQjTvIWPud0NX2Qfkv11ThC/3cUYHpJ9Dc3fjyiQ6gpqKt59xszvY9XIrYwkiT8HaN9eUiKA9MqrrzX4hgAB4RdZW1djQxLIo2FdjR7qfwpPNXTk++vNdpaOKdvnWMDdULcRn3pPlJ60DwV+pKO2Quv0U/zx2RIji7/6L7hc9btZpr/FfPtav//Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=jEqX3/RFI+C3cc+5HXqR7jOhOrLNsiostejo2DewZIU=; b=aMhLNbqwezp7xduAXX/Uf5HsDAA4kw7pK0sTi3tX/9ReehWF/BT6dx1hWnHxXfaIE0a2QIi5JHy0m2jrb7Zzi1PWEE+QxWDFDVFdmy5ZH2VQKVT+0Z+v5ZDlsPHQ4A8x464gqZY5HssSRktEhUuf9vUzhcUqiUnK7TXyr53jehs=
Received: from AM7PR07MB6248.eurprd07.prod.outlook.com (2603:10a6:20b:134::11) by AM5PR0701MB2915.eurprd07.prod.outlook.com (2603:10a6:203:42::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3999.16; Thu, 1 Apr 2021 15:40:03 +0000
Received: from AM7PR07MB6248.eurprd07.prod.outlook.com ([fe80::543d:497d:ba3f:5576]) by AM7PR07MB6248.eurprd07.prod.outlook.com ([fe80::543d:497d:ba3f:5576%3]) with mapi id 15.20.3999.027; Thu, 1 Apr 2021 15:40:03 +0000
From: tom petch <ietfc@btconnect.com>
To: Italo Busi <Italo.Busi@huawei.com>, CCAMP <ccamp@ietf.org>
Thread-Topic: [CCAMP] YANG prefix for flexi-grid (was RE: FW: Proposal for YANG model prefix naming)
Thread-Index: AdcmRV6FDXSEVSmoSNaaAj9xeE5I1AAxxOZQ
Date: Thu, 1 Apr 2021 15:40:03 +0000
Message-ID: <AM7PR07MB6248192DAA92F629B5DE5236A07B9@AM7PR07MB6248.eurprd07.prod.outlook.com>
References: <980b707253e84978871a39b95e683959@huawei.com>
In-Reply-To: <980b707253e84978871a39b95e683959@huawei.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: huawei.com; dkim=none (message not signed) header.d=none;huawei.com; dmarc=none action=none header.from=btconnect.com;
x-originating-ip: [86.146.121.140]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 2beec101-bb6e-4689-3e54-08d8f5246b24
x-ms-traffictypediagnostic: AM5PR0701MB2915:
x-microsoft-antispam-prvs: <AM5PR0701MB2915DD779480ADF89D076794A07B9@AM5PR0701MB2915.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: PvoxMS4FY5hGgbBgb+AUPGwTHjxIV+EpGLIx6cwvv0xdFuz2q5M9krHr3EYk6gerYZU6s8vvPF4Y04d1ZDXxchVYfhtjDOZGteP6Be+he12pv4TG+ycLXXNn7P6/5ZTI+mHT9+DKi3WKfvtAf5qUDmgnNcZUbHCqYQPZjfeHGlZbAZpFS+6mMi2LxDZ4S8doqf0LeFn80gWYjY/vh38qQsO/X3Qgh0wnmElpvXuYN8Pyaaut4xhe2RVKRWgFlRLuWgj1rTAkXiLECFPZRGYE3RIF/NQGsaFplZuq35GiDwtdtindghzGQ/PI2I2rwRN9QJqQ8CGzYcDQ6lrZrKdMutPCBdZwOUbaLO2aPQbesQ63Im7FeZwi6x8YIHAa6y8756bAurBiG2Cyz8hPip0D9++bpMZj+7Pq1ujatIIwDZVirp/9KZXhiSUb1HE1VbwiAPKSIuxN9TOrJ+kyhMq0DCgJL7oDjt3fYbkO+0rDf2SOPXdxPzsth0tpK7G5Lvs5subH5m5WGSGAla799bDNo2GqS06XL22FnMbkQ5a7xRCBNhu68qiGaRcx0zxb1HXj6gevfoaAE2RAMR3xCTlLrGjYsPGR+shLPt3n70XM4RSF3df5FqwVp+hTtejYSQlCTaary8o5PykkGcy+cvq5pCb8pqo+V5KorfBY1YU5EM4JJ5R3WfBnWzcVSbfiybJQjMdG8kELbXcklKtv/oODhw252b+kDanbaiCIwAkgYKHGWNP2xdLL9FbTVPCc/wMMitl5Kiv5zTQsboE8jQ7x0tlE1XGY5bPfUlSzERHUdNc=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM7PR07MB6248.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(346002)(366004)(396003)(39860400002)(376002)(136003)(83380400001)(91956017)(478600001)(53546011)(64756008)(966005)(66446008)(66556008)(66476007)(8936002)(26005)(186003)(6506007)(9686003)(7696005)(52536014)(8676002)(30864003)(5660300002)(55016002)(110136005)(71200400001)(66946007)(38100700001)(316002)(33656002)(86362001)(2906002)(76116006)(473944003)(414714003); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: =?iso-8859-1?Q?tgV4V07jJMKtNbSVS++CmFcwoYtF/US0XlaJMgTgQkOOMGh5SNGUhY4Dgp?= =?iso-8859-1?Q?Fs6H51n4cAeWeCKWi1OkkcFls1/qSqNU58ljusM12ihQp0oXWM9ygJah3u?= =?iso-8859-1?Q?bpW1E9kuqJB+WyOQYXgRtU4TdyCwTBRTA8XtzhOjO9zbLk6jTLxoMYTDNH?= =?iso-8859-1?Q?SF1nNbyrkeVkjTNgtxh1p5aAWO8719w93NybzlOGkxJ8TFjLRtznK9Jopb?= =?iso-8859-1?Q?/NlcR823llxhHcfKgYkygrkpZFllBGMvJ68cMJLYf/PeI3b4Hk9vNpRHRw?= =?iso-8859-1?Q?JUA6Fw1ewFvxuLJlMqOaHcykwthNExVDhBgKXVAwJQ6RQ6ZzIx80U3DtF8?= =?iso-8859-1?Q?lszbkKMvaB+SYD4TtG5ev1UYh0pdv1mB9fccf1ut2ED34KMItI2+vuH6jG?= =?iso-8859-1?Q?RmVC7U/9FFoswNyQ3z1xjrmepOvOm9fx4HU+En/fJHWFp5XvRou0k43feY?= =?iso-8859-1?Q?AubPzcMDgXtJICXBmNBTV6+WDgCQMHGLPBewi0ubboJeyoYcNPw8NfQUME?= =?iso-8859-1?Q?QRRMrYN7y9OJ6Urp6JNtENCWKhn84uAJr1Fc7qDFee7uKQz1ooHtZcwuzA?= =?iso-8859-1?Q?srq+g3ZR+tQSJUYJqTrnUiWFvPO82SSkL3CYKOSYWlkdgJ2VLpMebDzWIz?= =?iso-8859-1?Q?SMYWlqs9Krpfj5nyB7XaSCWjTXHLpZekJsEJ4e4gAjuCIXmhGBIc++g4+1?= =?iso-8859-1?Q?xnDuY79vnegJKyX7odZSDyFWTwm6Z3tCOYd0zlpUzITzHprVeOt3q9D7zB?= =?iso-8859-1?Q?s8WNASJ/X4diDQDcAT+th2IBwEXJ2tsn/eMAnIDADWNr9w6qmhA2c5NYr5?= =?iso-8859-1?Q?in0QbN/q9B10hYYUuxIFWornKw+Clv5ZDeyruXcotwQMSsuC6IEHG4o7zc?= =?iso-8859-1?Q?HV10YXVUbL+SVXe/KNHjDDXvM+uefzI3KVIIjROinViOPRx/I4yjbDUEa4?= =?iso-8859-1?Q?+x9g4HtkHzfNcEkL/j0hYfDYiOVavCMp0znnDDfrwiaqpqjNW5asdalE6y?= =?iso-8859-1?Q?1+KMkOmCV45XwtHhkUBD3GO6XReC6KAgF/JnnInDFb1K39HQhlFoCFDn22?= =?iso-8859-1?Q?cEXcIE+WY+zbsJVBRtP/+EaGVCtSAte5Ofn1mGr6by97jn5BVd8AlnZfc8?= =?iso-8859-1?Q?lXDr4evw51CWbd5Py62O6rfJnG4zKvbSkJVREENxVXKiwAQVHSLY3VNFFe?= =?iso-8859-1?Q?XL+te8SUcErY0213TsfShVcFqmu9F/DXpelcSaiAWz+Vx8vTIiaDTmygjs?= =?iso-8859-1?Q?Dd1lG2EfkYtJriaF6tynzXOlJB2860ehyXzK1PLKWQTL8DvqUaov8CJ2Q8?= =?iso-8859-1?Q?InC6BCtZS2l6Q4j0v9OtjaD8Gs6PAfpGMtDzyIjqzdgVmoddAUslbjKnFt?= =?iso-8859-1?Q?yZ1Lz0Layx?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: AM7PR07MB6248.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 2beec101-bb6e-4689-3e54-08d8f5246b24
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Apr 2021 15:40:03.6965 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: vWkNJ2uT6jXmavTlzTIczXi4vGCkj1FfoRU2eCZ2pTIdqQtRsVSZYYN7MbAeJ8h3UTjfDikjUN+HlMjwn4XPPQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0701MB2915
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/f19579CLTz2tUUlQ3ruXW1A_eyY>
Subject: Re: [CCAMP] YANG prefix for flexi-grid (was RE: FW: Proposal for YANG model prefix naming)
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: Thu, 01 Apr 2021 15:40:18 -0000

From: CCAMP <ccamp-bounces@ietf.org> on behalf of Italo Busi <Italo.Busi@huawei.com>
Sent: 31 March 2021 16:49

It seems that addressing this issue on a step by step has worked well for the topology models

Let's then consider a second question/convention about the prefix to use for flexi-grid YANG model

I think that "flexi-grid" (which would lead to "flexi-gt" for flexi-grid Topology) is a bit too long for a prefix

I have not found any better option to shorten flexible other than flexi or flex. I think f is really too short to be meaningful and fx can be misunderstood as fixed as well

Therefore, I think we can shorten it to either "flexig" or "flexg" (which would lead to "flexigt" or "flexgt" respectively for flexi-grid Topology)

I have a slight preference for the latter option ("flexg" leading to "flexgt" for flexi-grid Topology) but I am open to other opinions or better proposals

Any other opinion?

<tp>
I prefer flexg of the options you suggest.  

There is something un-English about flexig, it just sounds wrong, and flexigt is worse.

(In passing, flex-g looks wrong to me with just one letter after the hyphen, it needs two).

Tom Petch

Thanks, Italo

> -----Original Message-----
> From: tom petch [mailto:ietfc@btconnect.com]
> Sent: lunedì 15 marzo 2021 13:00
> To: Daniele Ceccarelli <daniele.ceccarelli=40ericsson.com@dmarc.ietf.org>rg>;
> CCAMP <ccamp@ietf.org>
> Subject: Re: [CCAMP] FW: Proposal for YANG model prefix naming
>
> From: CCAMP <ccamp-bounces@ietf.org> on behalf of Daniele Ceccarelli
> <daniele.ceccarelli=40ericsson.com@dmarc.ietf.org>
> Sent: 11 March 2021 16:38
>
> as previously anticipated during the CCAMP session today, we will ask the RFC
> editor to update the YANG model prefix for the WSON topology to "wsont".
>
> Many thanks for sharing your thoughts and participating to the discussion.
>
> <tp>
> I await the minutes with interest!
>
> Meanwhile ccamp-flexigrid-yang is plain wrong.  Under IANA it registers flexi-
> grid-topology whereas the when statements have tet-flexig which I would
> characterise as ugly and uglier!  And I seem to recall this is not my first post on
> the prefix in this I-D which clearly is not ready for Last Call:-(
>
> Tom Petch
>
>
> Daniele
>
> -----Original Message-----
> From: CCAMP <ccamp-bounces@ietf.org> On Behalf Of Daniele Ceccarelli
> Sent: den 15 februari 2021 16:17
> To: tom petch <ietfc@btconnect.com>om>; Italo Busi <Italo.Busi@huawei.com>om>;
> 'CCAMP' <ccamp@ietf.org>rg>; adrian@olddog.co.uk
> Cc: rkrejci@cesnet.cz
> Subject: Re: [CCAMP] Proposal for YANG model prefix naming
>
> Thanks for your feedback Tom.
>
> Working group, other opinions?
>
> Thanks,
> Daniele
>
> -----Original Message-----
> From: tom petch <ietfc@btconnect.com>
> Sent: den 12 februari 2021 13:29
> To: Italo Busi <Italo.Busi@huawei.com>om>; Daniele Ceccarelli
> <daniele.ceccarelli@ericsson.com>om>; 'CCAMP' <ccamp@ietf.org>rg>;
> adrian@olddog.co.uk
> Cc: rkrejci@cesnet.cz
> Subject: Re: [CCAMP] Proposal for YANG model prefix naming
>
> From: Italo Busi <Italo.Busi@huawei.com>
> Sent: 12 February 2021 09:02
>
> Thanks Daniele
>
> FYI: we are discussing these options also with TEAS experts:
>
> https://protect2.fireeye.com/v1/url?k=d3d01972-8c4b2077-d3d059e9-
> 86959e472243-ddf7de26918206cd&q=1&e=586b5fcf-a971-4d25-81f3-
> 4c64316f0395&u=https%3A%2F%2Fgithub.com%2Ftsaad-
> dev%2Fte%2Fissues%2F125
>
> Let's see if we can get an agreement at least for these two drafts which are in
> RFC queue:
>
> > draft-ietf-ccamp-layer0-types
> > ietf-layer0-types (l0-types) --->(l0-types)
>
> I think we can agree with this prefix since all the proposals are aligned.
>
> > draft-ietf-ccamp-wson-yang
> > ietf-wson-topology  (wson) --->(wson-topo)
>
> Here, I think we have two candidates: wson-topo and wsont
>
> I have a slight preference for wsont since it is aligned with tet and nt prefix
> conventions used in RFC8795 and RFC8345 but I can accept wson-topo (it
> could be seen as aligned with wson-tunnel or wson-tnl prefix conventions).
>
> What do you think?
>
> <tp>
> Since TEAS already has its tanks on the lawn, I would go for wsont.
>
> Adrian expressed a preference for ...topo but I think that wrong as it gets too
> long IMHO as with ethtetopo or else eth-te-topo
>
> Tom Petch
> Italo
>
> > -----Original Message-----
> > From: Daniele Ceccarelli [mailto:daniele.ceccarelli@ericsson.com]
> > Sent: giovedì 4 febbraio 2021 09:14
> > To: tom petch <ietfc@btconnect.com>om>; 'CCAMP' <ccamp@ietf.org>rg>;
> > adrian@olddog.co.uk
> > Cc: rkrejci@cesnet.cz
> > Subject: Re: [CCAMP] Proposal for YANG model prefix naming
> >
> > Tom, Adrian, all,
> >
> > The L0 types and the WSON topology drafts are now on hold. We can
> > include them in the updated prefix naming.
> > The RFC editor will delay processing these documents until the updated
> > versions are available. The AD (John or Deborah) will need to approve
> > the changes.
> >
> > This will also affect the IANA registries, they have been informed as well.
> >
> > BR
> > Daniele
> >
> > -----Original Message-----
> > From: CCAMP <ccamp-bounces@ietf.org> On Behalf Of tom petch
> > Sent: den 3 februari 2021 17:44
> > To: 'CCAMP' <ccamp@ietf.org>rg>; adrian@olddog.co.uk
> > Cc: rkrejci@cesnet.cz
> > Subject: Re: [CCAMP] Proposal for YANG model prefix naming
> >
> > From: Adrian Farrel <adrian@olddog.co.uk>
> > Sent: 03 February 2021 12:12
> >
> > Hi Tom,
> >
> > >> Proposal for YANG model prefix naming.
> > >>
> > >> Radek and then Tom raised the issue of consistency in prefix naming
> > >> based
> > on
> > >> the fact that the TE topology model uses 'tet' and the TE topology
> > >> state model uses 'tet-s'
> > >
> > > I think that the starting point is a list of I-D/RFC and I see some
> > glitches in your list.
> > >
> > > draft-ietf-client-signal-yang probably should be
> > draft-ietf-ccamp-client-signal-yang
> >
> > Yes, typo.
> >
> > > I see two flexigrid I-D but you only list one
> >
> > I'm at https://datatracker.ietf.org/wg/ccamp/documents/ looking at
> > extant WG documents.
> > Looks like draft-ietf-ccamp-flexigrid-media-channel-yang expired
> > almost 6 months ago.
> >
> > > wson-yang and l1types have been approved by the IESG so I regard
> > > those as
> > fixed
> > > points that it is now too late to change and which we should build
> > > around
> >
> > Well, colour me confused.
> > I thought this whole thing came up in debate of the WSON YANG model.
> > If that debate is now closed, let's all move on and not worry about
> > any of this any more.
> >
> > > I have seen more than one wson model
> >
> > There's an information model in draft-ietf-ccamp-wson-iv-info, but no
> > data model.
> > draft-ietf-ccamp-wson-tunnel-model expired almost 6 months ago
> >
> > > microwave seems to be missing
> >
> > draft-ietf-ccamp-mw-topo-yang expired almost 18 months ago
> >
> > <tp>
> >
> > Adrian,
> >
> > The progress of I-D in the routing area can be erratic.  The fact that
> > the IETF has expired the I-D does not mean that it will not come back
> > to life - a whole raft of I-D that were produced in a rush just before
> > the IETF meeting have just expired 6 months later and some are now
> > being resuscitated, others will be in future, others will not.  Some re-appear
> years later when their time has come.
> >
> > To me, an expired draft says that someone was interested enough to put
> > in a lot of work and even if that work is not current, then it would
> > be a short- sighted naming convention, although well in keeping with
> > the traditions of the IETF, not to cater for such work in future.
> >
> > For myself, I like names that start with the most important property
> > and for me, that is WSON. OTN, RSVP and so on, and that is the basis
> > on which I reviewed them, and not the fact that they are te - the
> > rival proposal is for te to be the centre of the universe around which
> > everything revolves, regardless of which WG  - TEAS, CCAMP, ... -it may be in.
> I am not a fan of this approach.
> >
> > Tom Petch
> >
> > CCAMP is currently working on plenty of YANG models, so it might be
> > worth stepping back and getting the prefixes consistent across all of our
> work.
> > I'm not sure this is the most important thing on our list, and perhaps
> > it would be better to discuss the colour of the bike shed, but to make
> > sure that we do this just once, here is my attempt.
> >
> > My conclusion is that, although it would be nice to be consistent with
> > using just a suffix of 't' to indicate 'topology', this becomes messy
> > with some of the longer names, and it is clearer to always use 'topo'
> > (leaving the TE topology model as the odd one out).
> >
> > This proposal only extends to CCAMP YANG models, and I don't think
> > this list can debate the wider scoping of prefixes, but I think it
> > would extend well enough.
> >
> > The list shows...
> > Draftname
> > Modelname (currentprefix)--->(proposedprefix)
> >
> > draft-ietf-ccamp-client-signal-yang
> > ietf-eth-tran-service (ethtsvc)--->(etht-svc) ietf-eth-tran-types
> > (etht-types) ---
> > >(etht-types) ietf-trans-client-service (clntsvc) --->(tclnt-svc)
> > >ietf-trans-client-
> > svc-types (clntsvc-types) --->(tclnt-svc-types)
> >
> > draft-ietf-ccamp-dwdm-if-param-yang
> > ietf-ext-xponder-wdm-if
> > (ietf-ext-xponder-wdm-if)--->(ext-xponder-wdm-if)
> >
> > draft-ietf-ccamp-flexigrid-yang
> > ietf-flexi-grid-topology (flexi-grid-topology) --->(flexi-grid-topo)
> >
> > draft-ietf-ccamp-l1csm-yang
> > ietf-l1csm (l1csm) --->(l1csm)
> >
> > draft-ietf-ccamp-layer0-types
> > ietf-layer0-types (l0-types) --->(l0-types)
> >
> > draft-ietf-ccamp-layer1-types
> > ietf-layer1-types (l1-types) --->(l1types)
> >
> > draft-ietf-ccamp-optical-impairment-topology-yang
> > ietf-optical-impairment-topology (optical-imp-topo)
> > --->(optical-imp-topo)
> >
> > draft-ietf-ccamp-otn-topo-yang
> > ietf-otn-topology (otntopo) --->(otn-topo)
> >
> > draft-ietf-ccamp-otn-tunnel-model
> > ietf-otn-tunnel (otn-tunnel) --->(otn-tunnel)
> >
> > draft-ietf-ccamp-wson-yang
> > ietf-wson-topology  (wson) --->(wson-topo)
> >
> >
> > _______________________________________________
> > CCAMP mailing list
> > CCAMP@ietf.org
> > https://www.ietf.org/mailman/listinfo/ccamp
> > =
> >
> >
> > _______________________________________________
> > CCAMP mailing list
> > CCAMP@ietf.org
> > https://www.ietf.org/mailman/listinfo/ccamp
> >
>
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
>
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
>

_______________________________________________
CCAMP mailing list
CCAMP@ietf.org
https://www.ietf.org/mailman/listinfo/ccamp