Subject: [Isis-wg] RFC 4971 on Intermediate System to Intermediate System (IS-IS) Extensions for Advertising Router Information

From: [email-masked]
Date: Tue, 31 Jul 2007 18:08:22 -0700 (PDT)

A new Request for Comments is now available in online RFC libraries.

        RFC 4971

        Title:      Intermediate System to Intermediate System 

                    (IS-IS) Extensions for Advertising Router Information 

        Author:     JP. Vasseur, Ed.,

                    N. Shen, Ed.,

                    R. Aggarwal, Ed.

        Status:     Standards Track

        Date:       July 2007

        Mailbox:    [email-masked], 

                    [email-masked], 

                    [email-masked]

        Pages:      9

        Characters: 18541

        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-isis-caps-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4971.txt

This document defines a new optional Intermediate System to

Intermediate System (IS-IS) TLV named CAPABILITY,

formed of multiple sub-TLVs, which allows a router to announce its

capabilities within an IS-IS level or the entire routing domain.  [STANDARDS TRACK]

This document is a product of the IS-IS for IP Internets

Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track

protocol for the Internet community,and requests discussion and suggestions

for improvements.Please refer to the current edition of the Internet

 Official Protocol Standards (STD 1) for the standardization state and

 status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.

Requests to be added to or deleted from the IETF distribution list

should be sent to [email-masked].  Requests to be

added to or deleted from the RFC-DIST distribution list should

be sent to [email-masked].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending

an EMAIL message to [email-masked] with the message body 

help: ways_to_get_rfcs. For example:

        To: [email-masked]

        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the

author of the RFC in question, or to [email-masked].  Unless

specifically noted otherwise on the RFC itself, all RFCs are for

unlimited distribution.

Submissions for Requests for Comments should be sent to

[email-masked].  Please consult RFC 2223, Instructions to RFC

Authors, for further information.

The RFC Editor Team

USC/Information Sciences Institute

...

_______________________________________________
Isis-wg mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/isis-wg