Hi, It will be great if we can also have a plan for: draft-ietf-spring-srv6-yang-02 - YANG Data Model for SRv6 Base and Static <https://datatracker.ietf.org/doc/draft-ietf-spring-srv6-yang/> The IGP SRv6 YANG models have dependencies on this draft.
Thanks, Yingzhen On Sun, Dec 3, 2023 at 5:55 AM Adrian Farrel <adr...@olddog.co.uk> wrote: > Hey there, > > > > So, it’s over a year since Bruno asked this question, and eight months > since the current revision expired. > > > > I don’ see anything on the list, and there was no mention in the meeting > at IETF-118. > > > > Can we have a status and plan, please? > > It’s OK if the authors have decided to give up on their efforts with the > draft, but unless the WG has also given up (it was an adopted draft) it may > be time assign new editors to move forward. > > > > Thanks, > > Adrian > > > > *From:* spring <spring-boun...@ietf.org> *On Behalf Of * > bruno.decra...@orange.com > *Sent:* 26 September 2022 12:52 > *To:* Kamran Raza (skraza) <skr...@cisco.com>; > draft-ietf-spring-sr-policy-y...@ietf.org > *Cc:* SPRING WG <spring@ietf.org>; Dhruv Dhody <dhruv.i...@gmail.com> > *Subject:* Re: [spring] draft-ietf-spring-sr-policy-yang-01 > > > > Hi Kamran, authors, > > > > Thanks for the refreshed draft. > > > > What’s the status/ETA with regards to incorporating comments from the WG, > e.g. the ones below from Dhruv which are two years/revisions old. > > > > Thank you, > > Bruno > > > > *From:* spring <spring-boun...@ietf.org> *On Behalf Of *Dhruv Dhody > *Sent:* Wednesday, July 13, 2022 6:00 AM > *To:* Kamran Raza (skraza) <skr...@cisco.com> > *Cc:* draft-ietf-spring-sr-policy-y...@ietf.org; SPRING WG < > spring@ietf.org> > *Subject:* Re: [spring] draft-ietf-spring-sr-policy-yang-01 > > > > Hi Kamran, > > > > Thank you! The most important thing to me would be to make the model work > at the device as well as the controller (an example that would be adding > headend into the SR-policy). > > > > Thanks! > > Dhruv > > PS. Past comments I sent during adoption - > https://mailarchive.ietf.org/arch/msg/spring/KzXFvavQxwkYLG6unN70JK0Mwno/ > > > > On Tue, Jul 12, 2022 at 8:29 PM Kamran Raza (skraza) <skr...@cisco.com> > wrote: > > Hi Dhruv, > > > > The I.D will be refreshed and updated once submissions reopen. > > Apologies for the extended delay in updating it .. > > > > Rgds. > > > > *From: *Dhruv Dhody <dhruv.i...@gmail.com> > *Date: *Tuesday, July 12, 2022 at 10:12 AM > *To: *draft-ietf-spring-sr-policy-y...@ietf.org < > draft-ietf-spring-sr-policy-y...@ietf.org>, SPRING WG <spring@ietf.org> > *Subject: *draft-ietf-spring-sr-policy-yang-01 > > Hi Authors/WG, > > > > The I-D in question expired last year! > > > > In fact, there has been no change since its adoption back in May of 2019. > None of the comments received during the adoption calls are handled - > https://mailarchive.ietf.org/arch/msg/spring/9Hy8jfOmVP9vmXXaSJ6mISwYCRM/ > > > > BTW there are various documents that are importing it - > https://www.yangcatalog.org/yang-search/impact_analysis?rfcs=1&show_subm=1&show_dir=dependents&modtags=ietf-sr-pol...@2019-11-04.yang,ietf-sr-policy-ty...@2019-11-04.yang&orgtags=ietf > > > > Could we get clarity on the status of this I-D? > > > > Thanks! > > Dhruv > > > > Orange Restricted > > _________________________________________________________________________________________________________________________ > > > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > > they should not be distributed, used or copied without authorisation. > > If you have received this email in error, please notify the sender and delete > this message and its attachments. > > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > > Thank you. > > _______________________________________________ > spring mailing list > spring@ietf.org > https://www.ietf.org/mailman/listinfo/spring >
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
