2.5.4 IS-IS for IP Internets (isis)

NOTE: This charter is a snapshot of the 56th IETF Meeting in San Francisco, California USA. It may now be out-of-date.

Last Modified: 2003-02-25

Chair(s):
Tony Li <tli@procket.com>
Tony Przygienda <prz@xebeo.com>
Routing Area Director(s):
Bill Fenner <fenner@research.att.com>
Alex Zinin <zinin@psg.com>
Routing Area Advisor:
Alex Zinin <zinin@psg.com>
Mailing Lists:
General Discussion: isis-wg@ietf.org
To Subscribe: isis-wg-request@ietf.org
In Body: subscribe
Archive: ftp://ftp.ietf.org/ietf-mail-archive/isis-wg
Description of Working Group:
IS-IS is an IGP specified and standarized by ISO and incorporating extensions to support IP. It has been deployed successfully in the Internet for several years years. The IS-IS Working Group is chartered to document current protocol implementation practices and improvements, as well as to propose further extensions to be used within the scope of IS-IS and IP routing. Short term, the WG is expected to deliver a set of documents describing common implementation practices and extensions necessary to scale the protocol. These specifications will encourage multiple, inter-operable vendor implementations.

This working group will interact with other standards bodies that have responsibility for standardizing IS-IS.

Goals and Milestones:
DEC 98  Submit I-D on IETF recommendations for improvements to IS-IS
DEC 98  Submit I-D on IETF comments on the proposed second edition of IS-IS
DEC 98  Submit I-D on IS-IS Traffic Engineering Extensions
DEC 98  Submit I-D on IS-IS HMAC-MD5 Authentication
DEC 98  Submit I-D on IS-IS over IPv4
DEC 98  Submit I-D on Maintaining more than 255 adjacencies in IS-IS
DEC 98  Submit I-D on Optional Checksums on IIHs, CSNPs, and PSNPs in IS-IS
MAR 99  Submit I-D on IS-IS MIB
MAR 99  Submit IETF recommendations for improvements to IS-IS to IESG for publication as an Informational RFC.
MAR 99  Submit IS-IS Traffic Engineering Extensions to IESG for publication as an Informational RFC
MAR 99  Submit IS-IS HMAC-MD5 Authentication to IESG for publication as an Informational RFC
MAR 99  Submit IS-IS over IPv4 to IESG for publication as an Informational RFC
MAR 99  Submit Maintaining more than 255 adjacencies in IS-IS to IESG for publication as an Informational RFC
MAR 99  Submit Optional Checksums on IIHs, CSNPs, and PSNPs in IS-IS to IESG for publication as an Informational RFC
MAR 99  Review WG's priorities and future potential
JUL 99  Submit IS-IS MIB to IESG for consideration as a Proposed Standard.
Internet-Drafts:
  • - draft-ietf-isis-wg-mib-11.txt
  • - draft-ietf-isis-hmac-03.txt
  • - draft-ietf-isis-traffic-04.txt
  • - draft-ietf-isis-ipv6-05.txt
  • - draft-ietf-isis-gmpls-extensions-16.txt
  • - draft-ietf-isis-wg-multi-topology-05.txt
  • - draft-ietf-isis-ext-eth-01.txt
  • - draft-ietf-isis-restart-03.txt
  • - draft-ietf-isis-igp-p2p-over-lan-01.txt
  • - draft-ietf-isis-ext-lsp-frags-02.txt
  • - draft-ietf-isis-interoperable-01.txt
  • - draft-ietf-isis-auto-encap-02.txt
  • - draft-ietf-isis-admin-tags-01.txt
  • - draft-ietf-isis-proprietary-tlv-00.txt
  • - draft-ietf-isis-ip-interoperable-00.txt
  • - draft-ietf-isis-iso-interoperable-00.txt
  • - draft-ietf-isis-experimental-tlv-00.txt
  • Request For Comments:
    RFCStatusTitle
    RFC1195 PS Use of OSI IS-IS for Routing in TCP/IP and Dual Environments
    RFC2763 I Dynamic Hostname Exchange Mechanism for IS-IS
    RFC2966 I Domain-wide Prefix Distribution with Two-Level IS-IS
    RFC2973 I IS-IS Mesh Groups
    RFC3277 I IS-IS Transient Blackhole Avoidance
    RFC3358 I Optional Checksums in ISIS
    RFC3359 I Reserved TLV Codepoints in ISIS
    RFC3373 I Three-Way Handshake for IS-IS Point-to-Point Adjacencies

    Current Meeting Report

    None received.

    Slides

    Agenda
    Protocol Topology Support for IS-IS