[{"author": "Cheng Li", "text": "

Good day everyone!

", "time": "2023-07-26T16:33:07Z"}, {"author": "Antoine Fressancourt", "text": "

I am interested in contributiong to security work

", "time": "2023-07-26T16:35:20Z"}, {"author": "Alvaro Retana", "text": "

Please send email to spring-chairs@ Thanks!

", "time": "2023-07-26T16:35:50Z"}, {"author": "Antoine Fressancourt", "text": "

will do !

", "time": "2023-07-26T16:36:28Z"}, {"author": "Cheng Li", "text": "

I am interested as well

", "time": "2023-07-26T16:37:19Z"}, {"author": "Alvaro Retana", "text": "

As Bruno mentioned, we'll send out a message to the list. Please reply with your interest -- to spring-chairs@ That will make it easier to keep all interested people in one place.

", "time": "2023-07-26T16:40:14Z"}, {"author": "Darren Dukes", "text": "

Thanks Alvaro.

", "time": "2023-07-26T16:41:10Z"}, {"author": "Martin Vigoureux", "text": "

Since I can't make a comment on the microphone, I would like to note that although the list of behaviors has been updated in the draft, a number of IANA values are still not allocated.

", "time": "2023-07-26T16:55:57Z"}, {"author": "Alvaro Retana", "text": "

Thanks Martin!

", "time": "2023-07-26T16:57:09Z"}, {"author": "Joel Halpern", "text": "

Typically, unless early allocation is requested, IANA allocation from RFCs are done as TBD1, TBD2, ... For implementation a number of code points have been allocated using the FCFS policy, we need to make sure things line up at the end of the process.

", "time": "2023-07-26T16:57:16Z"}, {"author": "Boris Khasanov", "text": "

Great work Rakesh!

", "time": "2023-07-26T17:13:48Z"}, {"author": "Dhruv Dhody", "text": "

Also, do we really need a new term \"SR Policy group\"?

", "time": "2023-07-26T17:41:40Z"}, {"author": "Cheng Li", "text": "

It confuses me as well, I may need to read more about the use cases of SR policy group

", "time": "2023-07-26T17:42:58Z"}, {"author": "Ketan Talaulikar", "text": "

@Jim Guichard , I asked the question because the document was standards track but the authors clarified that is should be informational. Informational status is appropriate for the content. The Q is if the WG wants to consider adopting such work items - to me this is just one form of \"configuration template\".

", "time": "2023-07-26T17:43:00Z"}, {"author": "Ketan Talaulikar", "text": "

@Dhruv Dhody , we don't need it at the SPRING WG in IETF in my view ... vendors/operators are free to form their own templates on the routers or in their automation systems.

", "time": "2023-07-26T17:44:31Z"}, {"author": "Daniel Bernier", "text": "

+1 Ketan

", "time": "2023-07-26T17:44:47Z"}, {"author": "Joel Halpern", "text": "

Please read and discuss on the list :-)

", "time": "2023-07-26T17:44:50Z"}, {"author": "Daniel Bernier", "text": "

will do @Joel

", "time": "2023-07-26T17:45:16Z"}, {"author": "Joel Halpern", "text": "

Speaking personally, I am not at all sure that a head end can reliably determine the available bandwidth on a path?

", "time": "2023-07-26T17:48:51Z"}, {"author": "Greg Mirsky", "text": "

I'd like to bring your attention to the work on the Precision Availability Metrics https://datatracker.ietf.org/doc/draft-ietf-ippm-pam/

", "time": "2023-07-26T17:51:08Z"}, {"author": "Cheng Li", "text": "

I think this is useful

", "time": "2023-07-26T17:51:31Z"}, {"author": "Ketan Talaulikar", "text": "

draft-chen-spring-sr-policy-cp-validity is the other draft that I was referring to.

", "time": "2023-07-26T17:54:13Z"}, {"author": "Shuping Peng", "text": "

thank you for providing the references @Greg @Ketan

", "time": "2023-07-26T17:55:26Z"}]