I agree with Tianran. The scope of this document would be broader than just use within UCL-ACL if I understand the intent of the split.
Joe From: OPSAWG <opsawg-boun...@ietf.org> on behalf of Tianran Zhou <zhoutianran=40huawei....@dmarc.ietf.org> Date: Monday, October 9, 2023 at 23:38 To: adr...@olddog.co.uk <adr...@olddog.co.uk>, maqiufang (A) <maqiufa...@huawei.com>, opsawg@ietf.org <opsawg@ietf.org> Cc: draft-ietf-opsawg-ucl-...@ietf.org <draft-ietf-opsawg-ucl-...@ietf.org> Subject: Re: [OPSAWG] Should the schedule YANG model be seperated from draft-ietf-opsawg-ucl-acl? QUESTION FOR THE CHAIRS If this is split out, does it o into an individual draft for a further adoption poll, or can it be split into a second WG ID at once? ZTR> In my opinion, it should go into an individual draft. We adopted draft-ietf-opsawg-ucl-acl because of the whole solution. Scheduling in this solution is only a component and very specific. If we want to generalize the scheduling for services, resources, etc, the common model is new work. Best, Tianran 发件人: OPSAWG <opsawg-boun...@ietf.org> 代表 Adrian Farrel 发送时间: 2023年10月10日 10:06 收件人: maqiufang (A) <maqiufa...@huawei.com>; opsawg@ietf.org 抄送: draft-ietf-opsawg-ucl-...@ietf.org 主题: Re: [OPSAWG] Should the schedule YANG model be seperated from draft-ietf-opsawg-ucl-acl? As I said in my original comment, I’d like to see this separation. Various recent conversations suggest that scheduling (services, resources, ACLs, etc.) is becoming a Big Thing. Having a common model to facilitate this would be really helpful. QUESTION FOR THE CHAIRS If this is split out, does it o into an individual draft for a further adoption poll, or can it be split into a second WG ID at once? A From: OPSAWG <opsawg-boun...@ietf.org<mailto:opsawg-boun...@ietf.org>> On Behalf Of maqiufang (A) Sent: 07 October 2023 11:48 To: opsawg@ietf.org<mailto:opsawg@ietf.org> Cc: draft-ietf-opsawg-ucl-...@ietf.org<mailto:draft-ietf-opsawg-ucl-...@ietf.org> Subject: [OPSAWG] Should the schedule YANG model be seperated from draft-ietf-opsawg-ucl-acl? Hi, all Based on the comments we’ve received during the adoption call of draft-ma-opsawg-ucl-acl [1], the authors would like to start a separate thread to highlight a question raised by Adrian: should the schedule model be moved out into a separate document? And we would like to collect more feedback from the WG. It is indeed that the ietf-schedule YANG model in the draft is now designed to be applicable in other common scheduling contexts and not specific to ACL policies. The authors already see some usage of it in other date and time based context[2], and it might seem awkward for it (and other potential ones in the future) to reference draft-ietf-opsawg-ucl-acl for reusing the scheduling groupings. It would be good to know if the WG think it useful for this model to be defined in a separate document, so that the authors will take the time to work on it if there is consensus. Would appreciate any of your input, thanks a lot! [1] https://datatracker.ietf.org/doc/draft-ietf-opsawg-ucl-acl/ [2] https://datatracker.ietf.org/doc/draft-contreras-opsawg-scheduling-oam-tests/ Best Regards, Qiufang
_______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
