Hi Joe, all, Thank you for the summary.
I ack that I didn't see any follow-up to the last message you pointed to. Given that full three weeks elapsed since then, I naively assumed that point was resolved. I think that we are ready to move forward. Cheers, Med > -----Message d'origine----- > De : OPSAWG <[email protected]> De la part de Joe Clarke > (jclarke) > Envoyé : mardi 17 mai 2022 17:49 > À : Joe Clarke (jclarke) <[email protected]>; > [email protected] > Objet : Re: [OPSAWG] WG LC: draft-ietf-opsawg-sap > > I am closing the WG LC for this document. The LC prompted some > good comments from DIR reviews and a comprehensive review from > Adrian which led to a TEAS cross-review. > > The biggest discussion came between Tom P and the WG/authors on > the > definition of what a SAP is in the vein of this doc. While some > of his > suggestions have made it into the latest revision of the document, > I am not certain this discussion has been fully resolved. > > The last email I saw was > https://mailarchive.ietf.org/arch/msg/opsawg/D- > z_rGqFl8V47fHlAkwSqiOxEDk/. > Is this resolved? > > Based on that, we can take -05 forward to the IESG once we get a > shepherd. But this point seems important to resolve. > > Joe > > On 4/22/22 15:07, Joe Clarke (jclarke) wrote: > > Hello, Opsawg. The last round of comments on this draft have > been > > discussed/resolved, and we'd like to kick off a three-week WG LC > for > > this work. Please provide any and all feedback on list before > the end > > of the day May 13, 2022. > > > > Authors, if you have suggestions for a good shepherd for this > > document, we'd love to hear them. > > > > I have requested reviews from Ops and Routing on this work. > > > > Thanks. > > > > Joe > > > > _______________________________________________ > > OPSAWG mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/opsawg > > > > > _______________________________________________ > OPSAWG mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/opsawg _________________________________________________________________________________________________________________________ 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. _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
