1 / 7

Note Well

Note Well.

cleary
Download Presentation

Note Well

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. 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 • Any Birds of a Feather (BOF) session • 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.

  2. Access Node Control Protocol (ANCP) IETF 83, Paris Wojciech Dec (wdec@cisco.com) Matthew Bocci (matthew.bocci@alcatel-lucent.com)

  3. Agenda • 15 mins WG Status and Update – Chairs • 30 mins – Multicast Extensions for ANCP - draft-ietf-ancp-mc-extensions-06.txt - Tom Taylor

  4. Administrivia • Blue Sheets • Note takers + Jabber Scribe • Mailing List: General Discussion: ancp@ietf.org To Subscribe: ancp-request@ietf.org In Body: subscribe your_email_address Archive: http://www.ietf.org/mail-archive/web/ancp/index.html

  5. New Milestones (to be updated) Done - Accept WG I-D for ANCP Framework and Requirements Done - Accept WG I-D for Access Node Control Protocol (ANCP) Done - Accept WG ID for Security Threats analysis Done - Accept WG I-D for ANCP MIB Done - Security Threats Analysis last call Done - Framework and Requirements last call Done - Accept WG I-D for ANCP Multicast Extensions Done - Accept WG I-D for ANCP applicability to PON Done Sept 2010- Access Node Control Protocol (ANCP) Last Call June 2012 Dec 2010 - ANCP MIB Last Call DoneDec 2010 - ANCP Multicast Extensions last call DoneJune Jan 2011 - ANCP applicability to PON last call JuneMarch2012- Re-charter or conclude Working Group

  6. WG Drafts • New RFCs • ANCP Protocol • RFC 6320 • With IESG : • ANCP for PON • draft-ietf-ancp-pon-02

  7. WG Drafts • Work in progress: • Multicast extensions • On agenda • draft-ietf-ancp-mc-extensions-06.txt • WG LC attracted no comments, despite interest • Would like to see evidence of WG review before progressing • Access Node MIB • draft-ietf-ancp-mib-an-05.txt • WG last call after this IETF?

More Related