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

malana
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 IETF76 in Hiroshima

  3. Meetings in Hiroshima • MPLS wg Monday • MPLS wg Wednesday • Webex – non audio • PWE3 wg Thursday • Webex • PWE3 wg Friday • Webex (?) • CCAMP on Wednesday • CCAMP on Thursday

  4. WG Status • One new RFCs •  RFC 5654 “MPLS-TP Requirements” • Drafts in RFC-Editor’s queue • draft-ietf-mpls-3209-patherr • draft-ietf-mpls-gmpls-lsp-reroute • draft-ietf-mpls-soft-preemption • draft-ietf-mpls-ldp-end-of-lib • draft-ietf-mpls-tp-gach-dcn

  5. WG Organization • WG co-chairs • George and Loa • WG secretary • Martin • mpls@ietf.org • Eric • mpls-tp@itef.org & http://wiki.tools.ietf.org/misc/mpls-tp/ • Elisa

  6. MEAD team • Started as an MPLS interoperability design team • more than MPLS-TP • MPLS-TP was only the first task • Very efficient for the first 6-9 months • limited number of documents • Very focused • 1st priority of many of the members • 10 drafts to the IESG • Thank you for the effort!

  7. MEAD team • More and more like a working group • more IDs and RFCs than most working groups • started to look like a working group • … but design teams are not open? • A lot of perceptions • lot of things done behind closed doors • not possible for everyone to participate • Reality • most work done by ID authors and on the mpls-tp list • Long term effects • loss of focus • increasing work load • Conclusion • work for a working group – let the working groups do it! • activity is picking up again

  8. The “Steering Group” • The close down of MEAD resulted in at least on new group! • the mpls-tp steering group • no power as a group • but a good whistle • members from the IETF and ITU-T SG15 leadership • We will have a meeting here in Hiroshima

  9. WG Status • Drafts in IESG Processing • draft-ietf-mpls-mpls-and-gmpls-security-framework • In IETF Last Call • draft-ietf-mpls-p2mp-te-mib • Revised ID Needed • draft-ietf-mpls-tp-nm-req • In IETF Last Call • draft-ietf-mpls-tp-oam-requirements • Revised ID Needed

  10. WG Status • Active WG drafts • draft-ietf-mpls-tp-rosetta-stone • draft-ietf-mpls-tp-oam-framework (agenda item) • draft-ietf-mpls-rsvp-te-no-php-oob-mapping (agenda item) • draft-ietf-mpls-ldp-p2mp (agenda item) • draft-ietf-mpls-tp-survive-fwk (agenda item) • draft-ietf-mpls-lsp-ping-enhanced-dsmap (waiting for p2mp-lsp-ping) • draft-ietf-mpls-p2mp-lsp-ping (new version before xmas) • draft-ietf-mpls-tp-nm-framework (agenda item) • draft-ietf-mpls-tp-process (agenda item) • draft-ietf-mpls-tp-framework (agenda item) • draft-ietf-mpls-ldp-typed-wildcard (ready to request publication) • draft-ietf-mpls-rsvp-upstream (LC completed) • draft-ietf-mpls-ldp-upstream (LC completed - comments) • draft-ietf-mpls-fastreroute-mib • draft-ietf-mpls-ip-options (this is ready to go, but is waiting for write-up) • draft-ietf-mpls-tp-ach-tlv (there are tlvs proposed, and more to come)

  11. WG Status - outliers • IAB draft • draft-iab-mpls-tp-uncoord-harmful • auth48 • OPSAWG draft • draft-opsawg-mpls-tp-oam-def • CCAMP drafts • draft-bellagamba-ccamp-rsvp-te-mpls-tp-oam-ext • draft-abfb-mpls-tp-control-plane-framework

  12. MPLS-TP Mode of work • This is now working group work • mpls (lead), pwe3, ccamp, l2vpn, opsawg • We have regular phone conferences • to do initial reviews of documents • to keep up the progress • mpls-tp@ietf.org • the consensus list for mpls-tp work.

  13. OAM Draft post-Stockholm • BFD and LSP Ping Encapsulation for the ACH • draft-nitinb-mpls-tp-lsp-ping-bfd-procedures-01 • BFD Extensions • draft-asm-mpls-tp-bfd-cc-cv-01 • - LSP Ping Extensions • draft-nitinb-mpls-tp-lsp-ping-extensions-00 • - AIS and Lock Reporting • draft-sfv-mpls-tp-fault-00 • Lock Instruct • no draft yet (but will based in draft-boutros-mpls-tp-loopback) • Need to be merged with the lock-instruct draft • CFI • draft-he-mpls-tp-csf-01.txt (pwe3) -> covered by draft-martini-pwe3-static-pw-status-02.txt (pwe3) • Packet Loss & Packet Delay • merged into draft-frost-mpls-tp-loss-delay

  14. De-valuation • We have found that we have been to liberal with time allocation for slots, so we decided to de-value the minute with 10%

More Related