ISIS IETF 68 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 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 and RFC 3979. 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 for details.
Agenda • Chairs: Intro, administrivia - 3 mins • Doc Update - 11 mins • Les Ginsberg - Genapp - 13 mins • Bhatia, Manral - crypto reqmts - 5 mins • Bhatia, Manral, White - hmac-sha - 7 mins
Administrivia, WG news • Note taker pls • Recharter/update revisited w/ Ads • Going to move forward • Reaching out to Liasons for Doc movement
Doc Status & movement.1 RFC to PS - discussed on list • RFC 1195: Use of OSI IS-IS for Routing in TCP/IP and Dual Environments • RFC 2763: Dynamic Hostname Exchange Mechanism for IS-IS • RFC 2966: Domain-wide Prefix Distribution with Two-Level IS-IS • RFC 3373: Three-Way Handshake for IS-IS Point-to-Point Adjacencies • RFC 3567: Intermediate System to Intermediate System (IS-IS) Cryptographic Authentication • RFC 3784: IS-IS extensions for Traffic Engineering • RFC 3874: Restart signaling for IS-IS • RFC 4205: Intermediate System to Intermediate System (IS-IS) Extensions in Support of Multi-Protocol Label Switching (GMPLS) • RFC 4444: Management Information Base for Intermediate System to Intermediate System (IS-IS)
Doc Status & movement.2 Drafts to PS - discussed on list • Routing IPv6 with IS-IS (draft-ietf-isis-ipv6-06.txt) • M-ISIS: Multi Topology (MT) Routing in IS-IS (draft-ietf-isis-wg-multi-topology-11.txt) • A Policy Control Mechanism is IS-IS Using Administrative Tags (draft-ietf-isis-admin-tags-03.txt) • Definition of an IS-IS Link Attribute sub-TLV (draft-ietf-isis-link-attr-02.txt) • IPv6 Traffic Engineering in IS-IS (draft-ietf-isis-ipv6-te-03.txt) • IS-IS Extensions for Advertising Router Information (draft-ietf-isis-caps-06.txt) • Simplified Extension of LSP Space for IS-IS (draft-ietf-isis-wg-extlsp-00.txt) • IS-IS HMAC SHA Cryptographic Authentication (draft-ietf-isis-hmac-sha-00.txt)
Doc Status & movement.3 NOT To PS - discussed on list • RFC 2973: IS-IS Mesh Groups • Reason: No interoperability issues • RFC 3277: IS-IS Transient Blackhole Avoidance • Reason: No interoperability issues. SA bit in restart draft is better mechanism • RFC 3358: Optional Checksums in ISIS • Reason: Cryptographic Auth provides better functionality • RFC 3359: Reserved TLV Codepoints in ISIS • Reason: Obsolete - replaced by IANA registry • RFC 3719: Recommendations for Interoperable Networks using IS-IS • Reason: This is intended to be an informational/BCP type of document.
Doc Status & movement.4 NOT To PS - discussed on list • RFC 3786: Extending the Number of IS-IS LSP Fragments Beyond the 256 Limit • Reason: Soon to be obsolete • RFC 3787: Recommendations for Interoperable IP Networks using IS-IS • Reason: This is intended to be an informational/BCP type of document. • RFC 3563: Cooperative Agreement Between the ISOC/IETF and ISO/IEC Joint Technical Committee 1/Sub Committee 6 (JTC1/SC6) on IS-IS Routing Protocol Development • Reason: Administrative • RFC 3906: Calculating Interior Gateway Protocol (IGP) Routes Over Traffic Engineering Tunnels • Reason: Different algorithms can still interoperate - although it is good to have one expected behavior.
Doc Status & movement.5 May To PS - discussed on list • Point-to-point operation over LAN in link-state routing protocols (draft-ietf-isis-igp-p2p-over-lan-06.txt) • Reason: Technically, this is mainly a consistent configuration issue and so could be informational. However, if, for example, the ISs multicast address is not used by everyone for sending PDUs, then some could be missed depending on whether a system was L1 or L1L2.
Doc Status & movement.6 Issues w/ ITU Internet-specific IS-IS Extensions: a) do not modify the Core IS-IS Mechanisms and do not change operation of non-IP or affect compatibility with non-IP and dual implementations of IS-IS, or … Under this definition, we think the following items may require coordination w ITU: • Point-to-point operation over LAN in link-state routing protocols(draft-ietf-isis-igp-p2p-over-lan-06.txt) • RFC 3373: Three-Way Handshake for IS-IS Point-to-Point Adjacencies
Presentations DWard to give: Genapp CHopps to give: Crypto reqmts CHopps to give: hhmac-sha