Hi, Both, this document and abno are architectural frameworks and to my thinking rtgwg as a good home for those. I'm glad to see support from the AD's here! To second Alia - please do express your support/ lack of such, we would like the decision to be driven by consensus (so far only "support" mails have been received)
In the future we are going to bring more of routing architecture relevant discussions, WAN, as well as DC. Thanks! Regards, Jeff On Jul 28, 2014, at 9:35 AM, "Alia Atlas" <[email protected]<mailto:[email protected]>> wrote: GROW & IDR both agreed that it wasn't in their charter. This falls under rtgwg having individual drafts without a good WG. I have agreed to AD-sponsor it, but would prefer that it get the focus and review and consensus from being in a WG. There are 2 drafts (this & abno) that we are trying this with. Alia On Jul 28, 2014 10:39 AM, <[email protected]<mailto:[email protected]>> wrote: Support. Wouldn't GROW be a better home than RTGWG? > -----Original Message----- > From: rtgwg [mailto:[email protected]<mailto:[email protected]>] On > Behalf Of Petr Lapukhov > Sent: Sunday, July 27, 2014 7:31 PM > To: [email protected]<mailto:[email protected]> > Subject: WG review for draft-lapukhov-bgp-routing-large-dc > > Hi, > > Authors of draft-lapukhov-bgp-routing-large-dc would like to submit it for > WG review and possible adoption as a workgroup document. In this draft we > summarize our experience of using BGP as the only protocol for routing in > large-scale data-center networks (100K+ bare metal servers, multiple > thousands of routers). > > Document location: http://tools.ietf.org/html/draft-lapukhov-bgp-routing- > large-dc/ > > Thank you! > > Petr > _______________________________________________ > rtgwg mailing list > [email protected]<mailto:[email protected]> > https://www.ietf.org/mailman/listinfo/rtgwg _________________________________________________________________________________________________________________________ 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. _______________________________________________ rtgwg mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/rtgwg _______________________________________________ rtgwg mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/rtgwg
_______________________________________________ rtgwg mailing list [email protected] https://www.ietf.org/mailman/listinfo/rtgwg
