[OSPF] RFC 4970 on Extensions to OSPF for Advertising Optional Router Capabilities

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

        RFC 4970

        Title:      Extensions to OSPF for Advertising 

                    Optional Router Capabilities 

        Author:     A. Lindem, Ed.,

                    N. Shen, JP. Vasseur,

                    R. Aggarwal, S. Shaffer

        Status:     Standards Track

        Date:       July 2007

        Mailbox:    acee@redback.com, 

                    naiming@cisco.com, 

                    jpv@cisco.com,  rahul@juniper.net, 

                    sshaffer@bridgeport-networks.com

        Pages:      13

        Characters: 26416

        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ospf-cap-11.txt

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

It is useful for routers in an OSPFv2 or OSPFv3 routing domain to

know the capabilities of their neighbors and other routers in the

routing domain.  This document proposes extensions to OSPFv2 and

OSPFv3 for advertising optional router capabilities.  A new Router

Information (RI) Link State Advertisement (LSA) is proposed for this

purpose.  In OSPFv2, the RI LSA will be implemented with a new opaque

LSA type ID.  In OSPFv3, the RI LSA will be implemented with a new

LSA type function code.  In both protocols, the RI LSA can be

advertised at any of the defined flooding scopes (link, area, or

autonomous system (AS)).  [STANDARDS TRACK]

This document is a product of the Open Shortest Path First IGP

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 IETF-REQUEST@IETF.ORG.  Requests to be

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

be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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

an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG

        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 RFC-Manager@RFC-EDITOR.ORG.  Unless

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

unlimited distribution.

Submissions for Requests for Comments should be sent to

RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC

Authors, for further information.

The RFC Editor Team

USC/Information Sciences Institute

...

_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www1.ietf.org/mailman/listinfo/ospf