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

Dhruv Dhody <> Thu, 02 September 2021 07:14 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5F8DC3A1053; Thu, 2 Sep 2021 00:14:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Status: No, score=-1.897 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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id qDeKaVHgg8Yw; Thu, 2 Sep 2021 00:14:21 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 55C7A3A104F; Thu, 2 Sep 2021 00:14:21 -0700 (PDT)
Received: from (unknown []) by (SkyGuard) with ESMTP id 4H0XDw6SyCz67YMc; Thu, 2 Sep 2021 15:12:32 +0800 (CST)
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.8; Thu, 2 Sep 2021 09:14:16 +0200
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.8; Thu, 2 Sep 2021 12:44:13 +0530
Received: from ([]) by ([]) with mapi id 15.01.2308.008; Thu, 2 Sep 2021 12:44:13 +0530
From: Dhruv Dhody <>
To: "" <>, "" <>
CC: 'TEAS WG' <>, Dhruv Dhody <>
Thread-Topic: [Teas] Issue in draft-ietf-teas-te-service-mapping-yang
Thread-Index: AdefbAiAkuOXjSTsSxSHvLOH9J7vlgAXlX3A
Date: Thu, 2 Sep 2021 07:14:13 +0000
Message-ID: <>
References: <0cc301d79f6e$d40cda30$7c268e90$>
In-Reply-To: <0cc301d79f6e$d40cda30$7c268e90$>
Accept-Language: en-GB, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [Teas] Issue in draft-ietf-teas-te-service-mapping-yang
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 02 Sep 2021 07:14:39 -0000

Hi Adrian, 

That is a good suggestion. Unless I hear objections I will update the I-D accordingly. 


-----Original Message-----
From: Teas [] On Behalf Of Adrian Farrel
Sent: 02 September 2021 01:51
Cc: 'TEAS WG' <>
Subject: [Teas] Issue in draft-ietf-teas-te-service-mapping-yang


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."


Teas mailing list