Hi Ketan,
> On Feb 5, 2025, at 11:26 PM, Ketan Talaulikar <ketant.i...@gmail.com> wrote: > > < copying SPRING WG and authors of the SR Policy YANG draft > > > Hi Mahesh, > > Thanks for your review of the document. > > Since your comments are for draft-ietf-spring-sr-policy-yang, I should relay > them to the authors of that document and the SPRING WG. AFAIK that document > is still work-in-progress. That is the right thing to do, though I was hoping for a little more than that. I would like the authors of this draft to provide guidance on what those counters should be, e.g., by documenting it here. Since this is a non-blocking comment, I will let the authors decide how best they want to achieve that. Thanks. > > Thanks, > Ketan > > > On Thu, Feb 6, 2025 at 3:03 AM Mahesh Jethanandani via Datatracker > <nore...@ietf.org <mailto:nore...@ietf.org>> wrote: > Mahesh Jethanandani has entered the following ballot position for > draft-ietf-idr-sr-policy-safi-11: No Objection > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > > Please refer to > https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ > <https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/> > > for more information about how to handle DISCUSS and COMMENT positions. > > > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/draft-ietf-idr-sr-policy-safi/ > <https://datatracker.ietf.org/doc/draft-ietf-idr-sr-policy-safi/> > > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > Thanks for adding a separate manageability section to outline how the feature > is going to be managed. And thanks to Roman for catching the fact that the > referenced YANG module draft had expired. > > Looking at draft-ietf-spring-sr-policy-yang and granted it is still a draft, I > could not help noticing the paucity of statistics being maintained for the > feature supported by this draft. Granted, this comment is more for the other > draft, but I wonder if enough thought has been given to what would be required > to manage the feature in the network. For example, these are the only counters > associated with policies that I could find. > > description > "Counters containing stats related to forwarding"; > > leaf pkts { > type yang:counter64; > description "Number of packets forwarded"; > } > leaf octets { > type yang:counter64; > units "byte"; > description "Number of bytes forwarded"; > } > > Description or lack of it aside, what it appears to be counting is the number > of packets or octets forwarded when the policy is successfully installed. How > do these stats help with debugging if the policy was learned by the headend in > the first place or the number of candidate paths it learned? > > > Mahesh Jethanandani mjethanand...@gmail.com
_______________________________________________ spring mailing list -- spring@ietf.org To unsubscribe send an email to spring-le...@ietf.org
