1 / 14

Note Well

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

sylvana-silas
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 • 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. MPLS Working Group IETF 79 – Beijing

  3. Meetings in Beijing • MPLS, Monday, 15:10-16:10 (WebEx) • MPLS, Wednesday, 09:00-11:30 (WebEx)

  4. Agenda Bashing • Please respect the time allocated to your presentation slot! • Fill in the Blue Sheets, and pass on! Return to WG Chairs

  5. Agenda Bashing • Multiprotocol Label Switching WG • http://www.ietf.org/proceedings/79/agenda/mpls.txt

  6. WG Status • 5 new RFCs • RFC 5918Label Distribution Protocol (LDP) 'Typed Wildcard' Forward Equivalence Class (FEC) • RFC 5919Signaling LDP Label Advertisement Completion • RFC 5950Network Management Framework for MPLS-based Transport Networks • RFC 5951Network Management Requirements for MPLS-based Transport Networks • RFC 5960MPLS Transport Profile Data Plane Architecture

  7. WG Status • Drafts in RFC-Editor’s queue • draft-ietf-mpls-tp-survive-fwk

  8. WG Status • Drafts in IESG Processing • draft-ietf-mpls-ldp-igp-sync-bcast • updated • draft-ietf-mpls-ldp-upstream • Waiting for AD Go-Ahead • draft-ietf-mpls-explicit-resource-control-bundle • Request to publish as an experimental RFC • draft-ietf-mpls-tp-oam-framework • IETF Last Call • draft-ietf-mpls-ip-options • AD Evaluation :: New ID needed

  9. WG Status • WG Drafts (Not on the Agenda - I) • draft-ietf-mpls-ldp-p2mp • Ready for wg last call • draft-ietf-mpls-p2mp-lsp-ping • draft-ietf-mpls-lsp-ping-enhanced-dsmap • Request for publication of the two drafts above will be at the same time • draft-ietf-mpls-mldp-in-band-signaling • New version available before Prague, comments welcome • draft-ietf-mpls-mldp-recurs-fec • Recently approved as wg document • draft-ietf-mpls-rsvp-te-no-php-oob-mapping • Updated after working group last call; document shepherd write-up needed • draft-manral-mpls-ldp-ipv6 • Recently approved as wg document • draft-farrel-mpls-tp-mib-management-overview • Recently approved as wg document

  10. WG Status • WG Drafts (Not on the Agenda - II) • draft-ietf-mpls-tp-li-lb • draft-ietf-mpls-tp-linear-protection • Updated after Maastricht discussion and other comments • Ready for wg last call • draft-ietf-mpls-tp-loss-delay • Will be updated • draft-ietf-mpls-tp-lsp-ping-bfd-procedures • draft-ietf-mpls-tp-oam-analysis • In wg last call • draft-ietf-mpls-tp-on-demand-cv • draft-ietf-mpls-tp-rosetta-stone

  11. WG Status • WG Drafts (Not on the Agenda - I) • draft-ietf-mpls-tp-uni-nni • In wg last call • draft-absw-mpls-lsp-ping-mpls-tp-oam-conf • Inherited from CCAMP • draft-ietf-mpls-tp-identifiers

  12. WG Status • Non MPLS WG Drafts • draft-ietf-ccamp-mpls-tp-cp-framework • In working group (CCAMP) last call • On the agenda

  13. WG Status • WG Drafts (on the agenda) • draft-ietf-mpls-tp-cc-cv-rdi • draft-ietf-mpls-tp-fault • draft-ietf-mpls-return-path-specified-lsp-ping

  14. WG Status • Early IANA allocations • Early code points allocation for draft-ietf-mpls-tp-on-demand-cv has been approved. • However we dropped the stone on our toes (oouuch!!) • Drafts with conflicting suggested IANA values • draft-ietf-mpls-p2mp-lsp-ping • draft-ietf-mpls-lsp-ping-enhanced-dsmap • draft-ietf-mpls-return-path-specified-lsp-ping • draft-ietf-mpls-tp-on-demand-cv • We will introduce a firm rule that we can’t introduce actual figures for code points in MPLS working group drafts until the allocation actually is done

More Related