I would be happy to collaborate on the progression of these two drafts to RFC as well as the single compression solution that the WG has final consensus to adopt and progress to RFC.
Kind Regards Gyan Verizon On Fri, Sep 10, 2021 at 10:11 AM Gyan Mishra <[email protected]> wrote: > > I support WG adoption of these two documents. > > Hats off for all the dedication and focus by the design team to > successfully complete the requirements document as well as complete the > well documented detailed analysis on the compression solutions. > > In the compression analysis conclusion section before this draft is > published, I believe the WG should come to a final consensus on a single > compression solution and document the compression solution at the end of > the conclusion section. > > I believe the solutions draft that the WG has consensus on should as well > be adopted and progressed to RFC updating RFC 8986 SRv6 PGM and RFC 8754 > SRH on the SRv6 compression algorithm integration into the SRv6 > specification. > > Kind Regards > > Gyan > > On Fri, Sep 10, 2021 at 9:50 AM Rabadan, Jorge (Nokia - US/Mountain View) < > [email protected]> wrote: > >> I support the adoption of the two documents as WG documents. >> >> The design team has done a great job, and the result is pretty good. The >> documents are a great reference and should be adopted. >> >> >> >> Thanks. >> >> Jorge >> >> >> >> *From: *spring <[email protected]> on behalf of >> [email protected] <[email protected]> >> *Date: *Tuesday, September 7, 2021 at 3:13 PM >> *To: *[email protected] <[email protected]> >> *Subject: *[spring] WG Adoption call - >> draft-srcompdt-spring-compression-requirement - >> draft-srcompdt-spring-compression-analysis >> >> Dear WG, >> >> >> >> >> >> The Design Team has produced two documents: >> >> - A requirement document: draft-srcompdt-spring-compression-requirement >> >> - A solution analysis document: draft-srcompdt-spring-compression-analysis >> >> >> >> Both have been presented to the WG and triggered some discussions but are >> still individual documents. >> >> We believe it's now time for the WG to consider taking ownership of those >> two documents. >> >> Note that, especially for those two documents, WG adoption does not >> necessarily mean RFC publication in particular if it turns out that the >> benefit of long term archive would not justify the WG and IESG effort to >> finalize those two documents. >> >> >> >> >> >> This message starts a 2 week WG adoption call, ending September 20th >> 2021, for: >> >> >> https://datatracker.ietf.org/doc/html/draft-srcompdt-spring-compression-requirement >> >> >> https://datatracker.ietf.org/doc/html/draft-srcompdt-spring-compression-analysis >> >> >> >> >> >> After review of the document(s) please indicate support (or not) for WG >> adoption of the document(s) to the mailing list. >> >> Please also provide comments/reasons for your support (or lack thereof) >> as this is a stronger way to indicate your (non) support as this is not a >> vote. >> >> >> >> If you are willing to work on the document(s), please state this >> explicitly. This gives the chairs an indication of the energy level of >> people in the working group willing to work on the document. >> >> >> >> Thanks! >> >> >> >> Jim, Bruno & Joel >> >> >> >> _________________________________________________________________________________________________________________________ >> >> >> >> 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 >> [email protected] >> https://www.ietf.org/mailman/listinfo/spring >> > -- > > <http://www.verizon.com/> > > *Gyan Mishra* > > *Network Solutions A**rchitect * > > *Email [email protected] <[email protected]>* > > > > *M 301 502-1347* > > -- <http://www.verizon.com/> *Gyan Mishra* *Network Solutions A**rchitect * *Email [email protected] <[email protected]>* *M 301 502-1347*
_______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring
