ISIS IETF 70 Chris Hopps, David Ward. Note Well Any submission to the IETF intended by the...

7
ISIS IETF 70 Chris Hopps, David Ward

Transcript of ISIS IETF 70 Chris Hopps, David Ward. Note Well Any submission to the IETF intended by the...

Page 1: ISIS IETF 70 Chris Hopps, David Ward. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft.

ISIS

IETF 70

Chris Hopps, David Ward

Page 2: ISIS IETF 70 Chris Hopps, David Ward. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft.

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,– any IETF working group or portion thereof,– The IESG, or any member thereof on behalf of the IESG,– the IAB or any member thereof on behalf of the IAB,– any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF

auspices,– the RFC Editor or the Internet-Drafts function

• All IETF Contributions are subject to the rules of RFC 3978 (updated by RFC 4748) and RFC 3979.

• 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.

• 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 3978 (updated by RFC 4748) for details.

Page 3: ISIS IETF 70 Chris Hopps, David Ward. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft.

Agenda

• 5m - Intro, Adminastriva

• 5m - EXTLSP Update - Les Ginsberg

• draft-ietf-isis-wg-extlsp-01.txt

• 5m - GENAPP Update - Les Ginsberg

• draft-ietf-isis-genapp-00.txt

• 15m - IS-IS BFD TLV - Les Ginsberg

• draft-chopps-isis-bfd-tlv-01.txt

• 10m - IS-IS Detailed IP Reachability Extension - George Swallow

• draft-swallow-isis-detailed-reach-00.txt

• 10m - IS-IS Generic Cryptographic Authentication - Russ White

• draft-ietf-isis-hmac-sha-04.txt

• 5m - Proposed Standard Update - Chris Hopps

Page 4: ISIS IETF 70 Chris Hopps, David Ward. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft.

Remaining Steps To Proposed Standard

• Require that there are 2 independent implementations

• Non legacy RFCs/Drafts requiring implementation reports.– RFC 3847 (restart), RFC 4205 (gmpls-ext), RFC 4971 (caps), RFC 5029

(link-attr), ExtLSP, IPv6 TE, Admin Tags, M-ISIS, IPv6 (done), hmac-sha

• Legacy RFCs not requiring implementation reports– RFC 2763 (hostname), RFC 2966 (domain-wide), RFC 3373 (3-way), RFC

3567 (hmac), RFC 3784 (IPv4 TE)

Page 5: ISIS IETF 70 Chris Hopps, David Ward. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft.

RFCs completed

RFC 2763: Dynamic Hostname Exchange Mechanism for IS-IS Done: draft-ietf-isis-rfc2763bis-00.txt

RFC 3277: IS-IS Transient Blackhole AvoidanceDone: draft-ietf-isis-rfc3277bis-00.txt

RFC 3784: IS-IS extensions for Traffic EngineeringDone: [need to resurrect] draft-ietf-isis-te-bis-00.txt

RFC 3847: Restart signaling for IS-ISDone: draft-ietf-isis-rfc3847bis-00.txt

RFC 4205: Intermediate System to Intermediate System (IS-IS) Extensions in Support of Multi-Protocol Label Switching (GMPLS)

Done: [need to resurrect] draft-ietf-isis-rfc4205bis-00.txt

Page 6: ISIS IETF 70 Chris Hopps, David Ward. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft.

Drafts - completed

Simplified Extension of LSP Space for IS-ISDone: draft-ietf-isis-wg-extlsp-01.txt

Routing IPv6 with IS-ISDone: draft-ietf-isis-ipv6-07.txt

IPv6 Traffic Engineering in IS-ISDone: draft-ietf-isis-ipv6-te-04.txt

A Policy Control Mechanism in IS-IS Using Administrative Tags RFC Ed Q: draft-ietf-isis-admin-tags-04.txt

M-ISIS: Multi Topology (MT) Routing in IS-ISRFC Ed Q: draft-ietf-isis-wg-multi-topology-12.txt

Page 7: ISIS IETF 70 Chris Hopps, David Ward. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft.

RFCs - revisions needed

RFC 2966: Domain-wide Prefix Distribution with Two-Level IS-IS

RFC 3567: Intermediate System to Intermediate System (IS-IS) Cryptographic Authentication

Current Volunteer: Tony Li

RFC 3373: Three-Way Handshake for IS-IS Point-to-Point Adjacencies

Will be posted after review: draft-ietf-isis-rfc3373bis-00.txt