1 / 4

GROW WG Status IETF-82 Taipei, Taiwan

GROW WG Status IETF-82 Taipei, Taiwan. Christopher Morrow christopher.morrow@gmail.com Peter Schoenmaker pds@lugs.com. Note Well.

hallam
Download Presentation

GROW WG Status IETF-82 Taipei, Taiwan

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. GROW WG Status IETF-82 Taipei, Taiwan Christopher Morrow christopher.morrow@gmail.com Peter Schoenmaker pds@lugs.com

  2. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: * The IETF plenary session * The IESG, or any member thereof on behalf of the IESG * Any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices * Any IETF working group or portion thereof * The IAB or any member thereof on behalf of the IAB * The RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 5378 and RFC 3979 (updated by RFC 4879). Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 5378 and RFC 3979 for details. A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements. A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public.

  3. Agenda • GROW update 10 • Administrivia • draft-ietf-grow-diverse-bgp-path-dist-05 • draft-ietf-grow-va-auto-04 • kirkham-private-ip-sp-cores • draft-mlevy-ixp-jumboframes-00 • Li Cheng 15 draft-cheng-grow-va-auto-extensions-00 • Elisa Jasinska 15 draft-hilliard-ix-bgp-route-server-operations • Shishio Tsuchiya 10 draft-shishio-grow-isp-rfd-implement-survey-02 • Cathy Aronson 10 draft-mlevy-ixp-jumboframes-00 • Ruediger Volk 10 BGP resilience

  4. RFCs • RFC 6198 4/2011 • draft-ietf-grow-bgp-graceful-shutdown-requirements • Bruno Decraene, Pierre Francois, CristelPelsser, Zubair Ahmad, Antonio Jose ElizondoArmengol, Tomonori Takeda • RFC 6382 10/2011 • draft-ietf-grow-unique-origin-as • Danny McPherson, Ryan Donnelly, Frank Scalzo • RFC 6396 10/2011 • draft-ietf-grow-mrt • Larry Blunk, Manish Karir, Craig Labovitz • RFC 6397 10/2011 • draft-ietf-grow-geomrt • Terry Manderson

More Related