Re: [Teas] I-D Action: draft-ietf-teas-actn-vn-yang-07.txt
"t.petch" <ietfa@btconnect.com> Fri, 29 November 2019 16:50 UTC
Return-Path: <ietfa@btconnect.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 135B4120A33 for <teas@ietfa.amsl.com>; Fri, 29 Nov 2019 08:50:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 erHShxPrWYxt for <teas@ietfa.amsl.com>; Fri, 29 Nov 2019 08:50:08 -0800 (PST)
Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-eopbgr10135.outbound.protection.outlook.com [40.107.1.135]) (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 47DFB120894 for <teas@ietf.org>; Fri, 29 Nov 2019 08:49:58 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=J3gqWFkb4JnjOIyUyqfZ0CUfZz6zaLcNHf6ivyVzRocj35EMjjk1xKA7j+/LpkgjZn18ZWJqwLzn6KO2ObTHhzN3SWyiqIwciMtPKvfoTdXQcBChD2XOY8uugzPejCnabuFcMJGT1UxbhfoA53gn4V9fdG/OcVF3ZvUxwB4hcI4KFCKXLjtwdWzcIaWoQiAYHmmiasqdCmznpjrd1UqBAM+QJmejU/hcht0JP5CM3CAgLjGtlRRej34ZQNxkArvnzxql+6A9mSzrPuwr/enQexteKDHNlhgbpS87Fq+A8p2fZQEKKiwkSRQcysHtS6T60C1iSk1M5bTvuxbwKiFNPw==
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=25P1fV27GkzKwj9zMaBi+jeu/dLbGW6a+EY1m5eSru4=; b=iFQiXlMASvvb24DO6xPgUQK2X8KtsntvVtkYS1gFC5s3pMg4bJmJHxb6UF9JOZfwvs7gbNkW+nS82fxKzLYdtoe8OG5eU7/hirhzH/sBS5GWpJ+QDnNDTfUCYC8hSaSmKXfAzPK2mK7CgIT4TPih5Nj/AwllRK9KUrBGZFSVGz1Qw2kdVOcsdqej+uvhIPPRaw0eVCAtNNachn3NUoVPf/tvupJbmzGx9vqiG+K9NCGiX6g10eqPo5lCBiGqAhjFdevDHH7c8yyWhpmPh7u+M3RurdSWcUlJaGpK7zldyKmX7y934+GkX6HRGUhKymD7rr+UqYp0Ez5X/X5aPsqG8A==
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=25P1fV27GkzKwj9zMaBi+jeu/dLbGW6a+EY1m5eSru4=; b=scRxsj3oVV1ffIXB4PPmgqBj5T/i0ZgN8PRv3jMwit1l7+Bf1kL6RRcbD5wqmjBuh+IROGCFTQ6u67BOqBHyMTBdf29QEAhkeyJ4CaaGvNzCdehQuaDNfgyN/MSh7NjSdm8TUhhIGI6zE7iWbWc8ApXgyTqUhsnSx75grNHC4hk=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=ietfa@btconnect.com;
Received: from DB7PR07MB5451.eurprd07.prod.outlook.com (20.178.45.149) by DB7PR07MB6028.eurprd07.prod.outlook.com (20.178.106.85) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2516.4; Fri, 29 Nov 2019 16:49:55 +0000
Received: from DB7PR07MB5451.eurprd07.prod.outlook.com ([fe80::5c25:d41c:c54c:bb19]) by DB7PR07MB5451.eurprd07.prod.outlook.com ([fe80::5c25:d41c:c54c:bb19%7]) with mapi id 15.20.2516.003; Fri, 29 Nov 2019 16:49:55 +0000
Message-ID: <008501d5a6d4$edf176c0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfa@btconnect.com>
To: Young Lee <younglee.tx@gmail.com>
Cc: teas@ietf.org
References: <157251765647.30404.18087034866262544442@ietfa.amsl.com>
Date: Wed, 27 Nov 2019 12:31:55 -0000
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-ClientProxiedBy: LO2P265CA0195.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:9e::15) To DB7PR07MB5451.eurprd07.prod.outlook.com (2603:10a6:10:76::21)
MIME-Version: 1.0
Received: from pc6 (86.139.211.103) by LO2P265CA0195.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:9e::15) with Microsoft SMTP Server (version=TLS1_0, cipher=) via Frontend Transport; Fri, 29 Nov 2019 16:49:54 +0000
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [86.139.211.103]
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 3ce19781-fb39-4e41-8834-08d774ec2956
X-MS-TrafficTypeDiagnostic: DB7PR07MB6028:
X-Microsoft-Antispam-PRVS: <DB7PR07MB6028E68CBE0A0AABD2A0A9A6A2460@DB7PR07MB6028.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:849;
X-Forefront-PRVS: 0236114672
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(396003)(346002)(376002)(39860400002)(366004)(136003)(199004)(189003)(13464003)(81816011)(81166006)(66066001)(478600001)(5660300002)(6496006)(81156014)(966005)(316002)(81686011)(52116002)(50466002)(50226002)(6916009)(2906002)(4720700003)(76176011)(8936002)(25786009)(6486002)(6436002)(14496001)(4326008)(44736005)(6116002)(62236002)(44716002)(66574012)(305945005)(7736002)(229853002)(1556002)(6306002)(66946007)(26005)(3846002)(16526019)(186003)(66556008)(66476007)(230700001)(47776003)(86362001)(23756003)(386003)(956004)(6246003)(446003)(9686003)(4001150100001)(8676002)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB7PR07MB6028; H:DB7PR07MB5451.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1;
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: k/SOSaetXHLoMtbLgSSB3OcUrj1LfCV2RlGXeH+mjLBRSmqjzb7fRaTsOy2SbPu/gElpZgxDVBS/qKK2yvzx/nxuZgSSTi8LeYYXRhxaq86RR5yHd+mKCjLQS1PaTLmzic44XFY53YnBM+ab0rwGfz245wRiy6GXRsoIW4s3LxMWcNgGomzu9GWT0EcYkTSRj/tQ/O9BpkBA2nBYMNOMbngtZVgxsTp67w5wmBvipJplFcBJiK8iJH1hZcY88iuSvw0zlSc/GZmydn9DAIOdgxYTIpPMc0hkdU3tYPICa1nOU5aThdZrTNr0OZ88eQB7Vlz6NffGa1mcWbh6LlsbXN37BoCkjK+rKOe81mTN3AwlJFRo+UmACtY13SOJs0YzIzYQumdf64XUWZwlyxb78skWafvDPBYwHRUoyNXhpZYfmQ8uR8G0AuJ5z6Iw2x86OSd/RhIx5h54c194ygh5EZ2NqY5RCpzbd4hKEN80jfU=
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 3ce19781-fb39-4e41-8834-08d774ec2956
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 29 Nov 2019 16:49:55.5362 (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: Z+JJWPYUcAinDeBLUix2WAJmhURj2YasQXJ9fmIQdngJnVtL9CHjGFMyL/36q4hyjn5TCBbgLKZHadBf/BkJGQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB7PR07MB6028
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/FdHPPlipFKc8RfT78GeDXALxuLo>
Subject: Re: [Teas] I-D Action: draft-ietf-teas-actn-vn-yang-07.txt
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Nov 2019 16:50:11 -0000
I like the Normative References in this version; I would like a few
more!
s.1 YANG - could do with a reference here, either 1.1 or both 1.0 and
1.0
s.1.3
| te-types | ietf-te-types | [I-D.ietf-teas-yang-te] |
Um, no should be
draft-ietf-teas-yang-te-types
the YANG module gets this right
Bearing in mind that the YANG module will exist outside any RFC, I would
like references in the YANG module for
VN
vn-disjointness (I see no mention of this in RFC8453)
vnap (perhaps a reference RFC8453 s.6)
ltp (I see no ltp in RFC8453)
connectivity-matrix-id (perhaps reference TE-topo)
vn-id
The YANG module needs a copyright statement
identity vn-compute-state-computatione-failed {
suggest
identity vn-compute-state-computation-failed {
YANG is sometimes Yang and yang - I suggest YANG where it appears in the
text (which is what YANG Guidelines does)
Tom Petch
----- Original Message -----
From: <internet-drafts@ietf.org>
To: <i-d-announce@ietf.org>
Cc: <teas@ietf.org>
Sent: Thursday, October 31, 2019 10:27 AM
>
> A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> This draft is a work item of the Traffic Engineering Architecture and
Signaling WG of the IETF.
>
> Title : A Yang Data Model for VN Operation
> Authors : Young Lee
> Dhruv Dhody
> Daniele Ceccarelli
> Igor Bryskin
> Bin Yeong Yoon
> Filename : draft-ietf-teas-actn-vn-yang-07.txt
> Pages : 54
> Date : 2019-10-31
>
> Abstract:
> This document provides a YANG data model generally applicable to
any
> mode of Virtual Network (VN) operation.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-teas-actn-vn-yang/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-teas-actn-vn-yang-07
> https://datatracker.ietf.org/doc/html/draft-ietf-teas-actn-vn-yang-07
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-actn-vn-yang-07
>
>
> 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/
>
- [Teas] I-D Action: draft-ietf-teas-actn-vn-yang-0… internet-drafts
- Re: [Teas] I-D Action: draft-ietf-teas-actn-vn-ya… t.petch