IS-IS for IP Internets (isis)
-----------------------------

Charter
Last Modified: 2009-10-16

Current Status: Active Working Group

Chair(s):
    Chris Hopps  <[email protected]>
    David Ward  <[email protected]>

Routing Area Director(s):
    Stewart Bryant  <[email protected]>
    Adrian Farrel  <[email protected]>

Routing Area Advisor:
    Stewart Bryant  <[email protected]>

Mailing Lists:
    General Discussion:[email protected]
    To Subscribe:      [email protected]
        In Body:       subscribe
    Archive:           http://www.ietf.org/mail-archive/web/isis-wg/index.html

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.

The status of the WG documents maintained by the WG chairs can be
found
at http://skat.usc.edu/~tli/Schedule.htm.

Goals and Milestones:

  Done         Submit I-D on IS-IS Traffic Engineering Extensions

  Done         Submit I-D on IS-IS HMAC-MD5 Authentication

  Done         Submit I-D on Maintaining more than 255 adjacencies in IS-IS

  Done         Submit I-D on Optional Checksums on IIHs, CSNPs, and PSNPs in
               IS-IS

  Done         Submit I-D on IS-IS MIB

  Done         Submit IS-IS Traffic Engineering Extensions to IESG for
               publication as an Informational RFC

  Done         Submit IS-IS HMAC-MD5 Authentication to IESG for publication as
               an Informational RFC

  Done         Submit Maintaining more than 255 adjacencies in IS-IS to IESG
               for publication as an Informational RFC

  Done         Submit Optional Checksums on IIHs, CSNPs, and PSNPs in IS-IS to
               IESG for publication as an Informational RFC

  Done         Submit IPv6 to IESG for publication as an Informational RFC

  Done         Submit M-ISIS to IESG for publication as an Informational RFC

  Done         Submit 256+ Fragments to IESG for publication as an
               Informational RFC

  Done         Submit Administrative Tags to IESG for publication as an
               Informational RFC

  Done         Submit Interoperable IP Networks to IESG for publication as an
               Informational RFC

  Done         Submit Interoperable Networks to IESG for publication as an
               Informational RFC

  Done         Submit P2P over LAN to IESG for publication as an Informational
               RFC

  Done         Submit Gracefull Restart to IESG for publication as an
               Informational RFC

  Jun 2005       Submit Experimental TLVs to IESG for publication as an
               Informational RFC

  Done         Submit Definition of an IS-IS Link Attribute sub-TLV to IESG
               for publication as Informational RFC

  Done         Submit A Policy Control Mechanism in IS-IS Using Administrative
               Tags to IESG for publication as Informational RFC

  Done         Submit IS-IS MIB to IESG for consideration as a Proposed
               Standard

  Done         Submit IS-IS extensions for advertising router information to
               IESG for publication as Informational RFC

  Done         Submit Multi Topology (MT) Routing in ISIS to IESG for
               publication as Informational RFC

  Done         Submit Routing IPv6 with IS-IS to IESG for publication as
               Proposed Standard

  Nov 2005       Review WG's priorities and future potential


Internet-Drafts:

Posted Revised         I-D Title   <Filename>
------ ------- --------------------------------------------
Nov 2007 Nov 2010   <draft-ietf-isis-genapp-04.txt>
               Advertising Generic Information in IS-IS

Mar 2008 Jan 2011   <draft-ietf-isis-bfd-tlv-03.txt>
               IS-IS BFD Enabled TLV

Mar 2009 Feb 2011   <draft-ietf-isis-layer2-11.txt>
               Extensions to IS-IS for Layer-2 Systems

May 2010 Oct 2010   <draft-ietf-isis-purge-tlv-05.txt>
               Purge Originator Identification TLV for IS-IS

Jul 2010 Feb 2011   <draft-ietf-isis-ieee-aq-04.txt>
               IS-IS Extensions Supporting IEEE 802.1aq Shortest Path Bridging

Aug 2010 Feb 2011   <draft-ietf-isis-trill-05.txt>
               TRILL Use of IS-IS

Oct 2010 Mar 2011   <draft-ietf-isis-reg-purge-01.txt>
               IS-IS Registry Extension for Purges

Request For Comments:

 RFC   Stat Published     Title
------- -- ----------- ------------------------------------
RFC1195 PS   Dec 1990    Use of OSI IS-IS for Routing in TCP/IP and Dual
                      Environments

RFC2763 I    Feb 2000    Dynamic Hostname Exchange Mechanism for IS-IS

RFC2966 I    Oct 2000    Domain-wide Prefix Distribution with Two-Level IS-IS

RFC2973 I    Oct 2000    IS-IS Mesh Groups

RFC3277 I    May 2002    IS-IS Transient Blackhole Avoidance

RFC3358 I    Aug 2002    Optional Checksums in ISIS

RFC3359 I    Aug 2002    Reserved TLV Codepoints in ISIS

RFC3373 I    Sep 2002    Three-Way Handshake for IS-IS Point-to-Point Adjacencies

RFC3567 I    Jul 2003    Intermediate System to Intermediate System
                      (IS-IS)Cryptographic Authentication

RFC3719 I    Mar 2004    Recommendations for Interoperable Networks using IS-IS

RFC3786 I    May 2004    Extending the Number of IS-IS LSP Fragments Beyond the
                      256 Limit

RFC3787 I    May 2004    Recommendations for Interoperable IP Networks using
                      IS-IS

RFC3784 I    Jun 2004    IS-IS extensions for Traffic Engineering

RFC3847 I    Jul 2004    Restart signaling for IS-IS

RFC4205 I    Oct 2005    Intermediate System to Intermediate System (IS-IS)
                      Extensions in Support of Multi-Protocol Label Switching
                      (GMPLS)

RFC4444 PS   Apr 2006    Management Information Base for Intermediate System to
                      Intermediate System (IS-IS)

RFC4971 PS   Jul 2007    Intermediate System to Intermediate System (IS-IS)
                      Extensions for Advertising Router Information

RFC5029 PS   Sep 2007    Definition of an IS-IS Link Attribute sub-TLV

RFC5120 PS   Feb 2008    M-ISIS: Multi Topology (MT) Routing in Intermediate
                      System to Intermediate Systems (IS-ISs)

RFC5130 PS   Feb 2008    A Policy Control Mechanism in IS-IS Using Administrative
                      Tags

RFC5309 I    Oct 2008    Point-to-point operation over LAN in link-state routing
                      protocols

RFC5308 PS   Oct 2008    Routing IPv6 with IS-IS

RFC5307 PS   Oct 2008    Intermediate System to Intermediate System (IS-IS)
                      Extensions in Support of Generalized Multi-Protocol
                      Label Switching (GMPLS)

RFC5306 PS   Oct 2008    Restart Signaling for Intermediate System to
                      Intermediate System (IS-IS)

RFC5305 PS   Oct 2008    IS-IS extensions for Traffic Engineering

RFC5304 PS   Oct 2008    Intermediate System to Intermediate System (IS-IS)
                      Cryptographic Authentication

RFC5303 PS   Oct 2008    Three-Way Handshake for Intermediate System to
                      Intermediate System (IS-IS) Point-to-Point Adjacencies

RFC5302 PS   Oct 2008    Domain-wide Prefix Distribution with Two-Level IS-IS

RFC5301 PS   Oct 2008    Dynamic Hostname Exchange Mechanism for IS-IS

RFC5311 PS   Feb 2009    Simplified Extension of Link State PDU (LSP) Space for
                      IS-IS

RFC5310 PS   Feb 2009    IS-IS Generic Cryptographic Authentication

RFC6119 PS   Feb 2011    IPv6 Traffic Engineering in IS-IS

You are viewing proxied material from ftp.icm.edu.pl. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.