I support WG adoption of this draft. I am very interested In development of this draft from a protocol specification standpoint as well as progressing the draft through Spring WG. I am also interested in related protocol extension development in other WGs.
As a member of PIM and MBONED and lifetime advocate of all multicast related technologies and technical SME in the multicast area, I believe this draft is critical for SR development for native multicast p-tree to come to fruition. Kind Regards Gyan On Tue, Jun 23, 2020 at 1:48 AM Ketan Talaulikar (ketant) <ketant= 40cisco....@dmarc.ietf.org> wrote: > I support the adoption of this document and would be willing to work on > its progression through Spring WG as well it's related protocol extensions > in other routing WGs. > > Thanks, > Ketan > > -----Original Message----- > From: spring <spring-boun...@ietf.org> On Behalf Of > bruno.decra...@orange.com > Sent: 22 June 2020 20:16 > To: spring@ietf.org > Subject: [spring] WG adoption call for > draft-voyer-spring-sr-replication-segment > > Hi SPRING WG, > > Authors of draft-voyer-spring-sr-replication-segment [1] have asked for WG > adoption. > > Please indicate your support, comments, or objection, for adopting this > draft as a working group item by July 6th 2020. > > Could those who are willing to work on this document, please notify the > list. That gives us an indication of the energy level in the working group > to work on this. > > As a reminder, the call for IPR has been done last November. [2] > > Thanks, > Regards, > Bruno, Jim, Joel > > [1] https://tools.ietf.org/html/draft-voyer-spring-sr-replication-segment > [2] > https://mailarchive.ietf.org/arch/msg/spring/tW-HHK7QzCw3ZBbFD0Dl7Eszd3k/ > > > > _________________________________________________________________________________________________________________________ > > 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 > -- <http://www.verizon.com/> *Gyan Mishra* *Network Solutions A**rchitect * *M 301 502-134713101 Columbia Pike *Silver Spring, MD
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
