[Teas] Issue in draft-ietf-teas-te-service-mapping-yang

Adrian Farrel <adrian@olddog.co.uk> Wed, 01 September 2021 20:20 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 397793A18D0; Wed, 1 Sep 2021 13:20:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Tp1ZsN00a4ef; Wed, 1 Sep 2021 13:20:47 -0700 (PDT)
Received: from mta8.iomartmail.com (mta8.iomartmail.com []) (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 636BD3A18C5; Wed, 1 Sep 2021 13:20:42 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com []) by mta8.iomartmail.com (8.14.4/8.14.4) with ESMTP id 181KKeER011305; Wed, 1 Sep 2021 21:20:40 +0100
Received: from vs3.iomartmail.com (unknown []) by IMSVA (Postfix) with ESMTP id EDF004604B; Wed, 1 Sep 2021 21:20:39 +0100 (BST)
Received: from vs3.iomartmail.com (unknown []) by IMSVA (Postfix) with ESMTP id DDC974604A; Wed, 1 Sep 2021 21:20:39 +0100 (BST)
Received: from asmtp1.iomartmail.com (unknown []) by vs3.iomartmail.com (Postfix) with ESMTPS; Wed, 1 Sep 2021 21:20:39 +0100 (BST)
Received: from LAPTOPK7AS653V ([]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id 181KKcIZ022078 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 1 Sep 2021 21:20:39 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <draft-ietf-teas-te-service-mapping-yang@ietf.org>
Cc: "'TEAS WG'" <teas@ietf.org>
Date: Wed, 1 Sep 2021 21:20:36 +0100
Organization: Old Dog Consulting
Message-ID: <0cc301d79f6e$d40cda30$7c268e90$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdefbAiAkuOXjSTsSxSHvLOH9J7vlg==
Content-Language: en-gb
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-Product-Ver: IMSVA-
X-TM-AS-Result: No--4.560-10.0-31-10
X-imss-scan-details: No--4.560-10.0-31-10
X-TMASE-Result: 10--4.560100-10.000000
X-TMASE-MatchedRID: b4ZI3dF1kUQDYP7H+M1ZMzjNGpWCIvfT4lzqEpaPQLUtferJ/d7Ab9+s ARRlOOvB9vs27eorq1NguPOOQBvTSi3UeYOWBocyY320FnKsuJErYfICdggcJj52fBZSOkyaHFJ yCMrdNkkLczQ2inWnPZMEvxDv+Gb4bTSwI/A2DvCqFx2c/3V5cQ73P4/aDCIF1+OTFqKF59kagP iGmljT1nyoOzE/2kVgGu1ZDK/RJVzvsMmNMolQf54CIKY/Hg3AtOt1ofVlaoJEOq3khOk7RhQab jOuIvShC24oEZ6SpSmcfuxsiY4QFB3H+lGWvZFm+LgcnHEaI0EwGb9k9LOFdMj0RK25CLAxxhWL 6pVN9MWYReWN/1ChOI5be3Hzd+XhirGf0n3PWeYBW+K8EX0fZOQ/bJqlQQ/copZ51QxAj3fx+wL 7E8WTG+w2n3R9PgSOsBTJSD2iAW0=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/6qRPt3Fyte09mAROO_y5ShNPGgU>
Subject: [Teas] Issue in draft-ietf-teas-te-service-mapping-yang
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: Wed, 01 Sep 2021 20:20:53 -0000


Looking at Appendix B, I see that there is an open discussion issue:

   *  Support for Calendaring and scheduling TE resources.

I think we had a similar discussion as we went through the work on PCE and
RSVP-TE. The way we approached it then was to acknowledge that calendaring
and scheduling is an important function for network operators, but to leave
it out of the core work. We concentrated on ensuring that the core work
would be extensible so that calendaring could be added at a later stage.

I suggest that we take the same approach here. That is, we add some text to
say that "Scheduling is currently out of scope, although an operator could
use their own scheduling mechanism on top of this YANG model. In future
augmentations to this model might be designed to integrate scheduling."