draft-ietf-ospf-cap-04.txt   draft-ietf-ospf-cap-05.txt 
Network Working Group A. Lindem (Editor) Network Working Group A. Lindem (Editor)
Internet-Draft Cisco Systems, Inc Internet-Draft Cisco Systems, Inc
Expires: May 30, 2005 N. Shen Expires: July 8, 2005 N. Shen
BCN Networks, Inc Cisco Systems
R. Aggarwal R. Aggarwal
Juniper Networks Juniper Networks
S. Schaffer S. Shaffer
BridgePort Networks BridgePort Networks
JP. Vasseur JP. Vasseur
Cisco Systems, Inc Cisco Systems, Inc
November 29, 2004 January 7, 2005
Extensions to OSPF for Advertising Optional Router Capabilities Extensions to OSPF for Advertising Optional Router Capabilities
draft-ietf-ospf-cap-04.txt draft-ietf-ospf-cap-05.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions This document is an Internet-Draft and is subject to all provisions
of section 3 of RFC 3667. By submitting this Internet-Draft, each of section 3 of RFC 3667. By submitting this Internet-Draft, each
author represents that any applicable patent or other IPR claims of author represents that any applicable patent or other IPR claims of
which he or she is aware have been or will be disclosed, and any of which he or she is aware have been or will be disclosed, and any of
which he or she become aware will be disclosed, in accordance with which he or she become aware will be disclosed, in accordance with
RFC 3668. RFC 3668.
skipping to change at page 1, line 42 skipping to change at page 1, line 43
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 30, 2005. This Internet-Draft will expire on July 8, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). Copyright (C) The Internet Society (2005).
Abstract Abstract
It is useful for routers in an OSPF routing domain to know the It is useful for routers in an OSPF routing domain to know the
capabilities of their neighbors and other routers in the OSPF routing capabilities of their neighbors and other routers in the OSPF routing
domain. This draft proposes extensions to OSPF for advertising domain. This draft proposes extensions to OSPF for advertising
optional router capabilities. A new Router Information (RI) opaque optional router capabilities. A new Router Information (RI) opaque
LSA is proposed for this purpose. LSA is proposed for this purpose.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. OSPF Router Information (RI) Opaque LSA . . . . . . . . . . . 4 2. OSPF Router Information (RI) Opaque LSA . . . . . . . . . . . 4
2.1 OSPF Router Capabilities TLV . . . . . . . . . . . . . . . 5 2.1 OSPF Router Capabilities TLV . . . . . . . . . . . . . . . 5
2.2 Reserved OSPF Router Capability Bits . . . . . . . . . . . 6 2.2 Reserved OSPF Router Capability Bits . . . . . . . . . . . 6
2.3 Flooding Scope of the Router Information LSA . . . . . . . 6 2.3 Flooding Scope of the Router Information LSA . . . . . . . 6
3. Security Considerations . . . . . . . . . . . . . . . . . . . 8 3. Router Information LSA Opaque Usage and Applicability . . . . 8
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 4. Security Considerations . . . . . . . . . . . . . . . . . . . 9
5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
5.1 Normative References . . . . . . . . . . . . . . . . . . . . 10 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5.2 Informative References . . . . . . . . . . . . . . . . . . . 10 6.1 Normative References . . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 10 6.2 Informative References . . . . . . . . . . . . . . . . . . . 11
A. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 11
Intellectual Property and Copyright Statements . . . . . . . . 13 A. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13
Intellectual Property and Copyright Statements . . . . . . . . 14
1. Introduction 1. Introduction
It is useful for routers in an OSPF routing domain to know the It is useful for routers in an OSPF routing domain to know the
capabilities of their neighbors and other routers in the OSPF routing capabilities of their neighbors and other routers in the OSPF routing
domain. This can be useful for various applications: domain. This can be useful for various applications:
o In MPLS Traffic Engineering (TE), it can be used as a discovery o In MPLS Traffic Engineering (TE), it can be used as a discovery
mechanism [TECAP] to announce a LSR's TE capabilities like Path mechanism [TECAP] to announce a LSR's TE capabilities like Path
Computation Server capability (Capability of an LSR to be a Path Computation Server capability (Capability of an LSR to be a Path
Computation Server for TE LSP path computation) or the intention Computation Server for TE LSP path computation) or the intention
skipping to change at page 7, line 8 skipping to change at page 7, line 8
11-31 Future assignments 11-31 Future assignments
2.3 Flooding Scope of the Router Information LSA 2.3 Flooding Scope of the Router Information LSA
The flooding scope for a Router Information opaque LSA is determined The flooding scope for a Router Information opaque LSA is determined
by the LSA type. A type 9 (link-scope), type 10 (area-scoped), or a by the LSA type. A type 9 (link-scope), type 10 (area-scoped), or a
type 11 (AS-scoped) opaque LSA may be flooded. If a type 11 opaque type 11 (AS-scoped) opaque LSA may be flooded. If a type 11 opaque
LSA is chosen, the originating router should also advertise type 10 LSA is chosen, the originating router should also advertise type 10
LSA(s) into any attached NSSA/stub area(s). An OSPF router MAY LSA(s) into any attached NSSA/stub area(s). An OSPF router MAY
advertise different capabilities when both NSSA/stub area type 10 advertise different capabilities when both NSSA/stub area type 10
LSA(s) and an AS scoped type 11 opaque LSA is advertised. The choice LSA(s) and an AS scoped type 11 opaque LSA is advertised. This
of flooding scope is made by the advertising router and is a matter allows functional capabilities to be limited in scope. For example,
of local policy. The originating router MAY advertise multiple RI a router may be an area border router but only support traffic
engineering (TE) in a subset of its attached areas. The choice of
flooding scope is made by the advertising router and is a matter of
local policy. The originating router MAY advertise multiple RI
opaque LSAs as long as the flooding scopes differ. TLV flooding opaque LSAs as long as the flooding scopes differ. TLV flooding
scope rules will be specified on a per-TLV basis. scope rules will be specified on a per-TLV basis.
3. Security Considerations 3. Router Information LSA Opaque Usage and Applicability
This memo does not create any new security issues for the OSPF The purpose of the Router Information (RI) opaque LSA is to advertise
protocol. Security considerations for the base OSPF protocol are information relating to the aggregate OSPF router. Normally, this
covered in [OSPF]. should be confined to TLVs with a single value or very few values.
It is not meant to be a generic container to carry any and all
information. The intent is to both limit the size of the RI LSA to
the point where an OSPF router will always be able to contain the
TLVs in a single LSA and to keep the task of determining what has
changed between LSA instances reasonably simple. Hence, discretion
and sound engineering judgement MUST be adhered to when deciding
whether newly proposed TLV(s) in support of a new function are
advertised in the RI opaque LSA or warrent the creation of a function
specific opaque LSA.
4. IANA Considerations 4. Security Considerations
The function described in this document does not create any new
security issues for the OSPF protocol. Security considerations for
the base OSPF protocol are covered in [OSPF].
5. IANA Considerations
A new opaque LSA type will need to be assigned by IANA. A new opaque LSA type will need to be assigned by IANA.
Additionally, IANA will need to have registries for the Router Additionally, IANA will need to have registries for the Router
Information opaque LSA TLV's. The TLV assignee will be responsible Information opaque LSA TLV's. The TLV assignee will be responsible
for allocation of any sub-TLV's for the IANA assigned TLV. All TLV's for allocation of any sub-TLV's for the IANA assigned TLV. All TLV's
and sub-TLV's will be subject to OSPF WG review. and sub-TLV's will be subject to OSPF WG review.
5. References 6. References
5.1 Normative References 6.1 Normative References
[OSPF] Moy, J., "OSPF Version 2", RFC 2328, April 1998. [OSPF] Moy, J., "OSPF Version 2", RFC 2328, April 1998.
[RFC2119] Bradner, S., "Key words for use in RFC's to Indicate [RFC2119] Bradner, S., "Key words for use in RFC's to Indicate
Requirement Levels", RFC 2328, March 1977. Requirement Levels", RFC 2328, March 1977.
[TE] Katz, D., Yeung, D. and K. Kompella, "Traffic Engineering [TE] Katz, D., Yeung, D. and K. Kompella, "Traffic Engineering
Extensions to OSPF", RFC 3630, September 2003. Extensions to OSPF", RFC 3630, September 2003.
5.2 Informative References 6.2 Informative References
[EXPTE] Srisuresh, P. and P. Joseph, "OSPF OSPF-TE: An [EXPTE] Srisuresh, P. and P. Joseph, "OSPF OSPF-TE: An
experimental extension to OSPF for Traffic Engineering", experimental extension to OSPF for Traffic Engineering",
draft-srisuresh-ospf-te-07.txt (work in progress). draft-srisuresh-ospf-te-07.txt (work in progress).
[GRACE] Moy, J., Pillay-Esnault, P. and A. Lindem, "Graceful OSPF [GRACE] Moy, J., Pillay-Esnault, P. and A. Lindem, "Graceful OSPF
Restart", RFC 3623, November 2003. Restart", RFC 3623, November 2003.
[OPAQUE] Coltun, R., "The OSPF Opaque LSA Option", RFC 2370, July [OPAQUE] Coltun, R., "The OSPF Opaque LSA Option", RFC 2370, July
1998. 1998.
skipping to change at page 11, line 5 skipping to change at page 12, line 5
Authors' Addresses Authors' Addresses
Acee Lindem Acee Lindem
Cisco Systems, Inc Cisco Systems, Inc
7025 Kit Creek Road 7025 Kit Creek Road
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
USA USA
EMail: acee@cisco.com EMail: acee@cisco.com
Naiming Shen Naiming Shen
BCN Networks, Inc Cisco Systems
2975 San Ysidro Way 225 West Tasman Drive
Santa Clara, CA 95051 San Jose, CA 95134
USA USA
EMail: naiming@bcn-inc.net EMail: naiming@cisco.com
Rahul Aggarwal Rahul Aggarwal
Juniper Networks Juniper Networks
1194 N. Mathilda Ave. 1194 N. Mathilda Ave.
Sunnyvale, CA 94089 Sunnyvale, CA 94089
USA USA
EMail: rahul@juniper.net EMail: rahul@juniper.net
Scott Schaffer Scott Shaffer
BridgePort Networks BridgePort Networks
One Main Street, 7th Floor One Main Street, 7th Floor
Cambridge, MA 02142 Cambridge, MA 02142
USA USA
EMail: sschafferl@bridgeport-networks.com EMail: sshafferl@bridgeport-networks.com
Jean-Philippe Vasseur Jean-Philippe Vasseur
Cisco Systems, Inc Cisco Systems, Inc
300 Beaver Brook Road 300 Beaver Brook Road
Boxborough, MA 01719 Boxborough, MA 01719
USA USA
EMail: jpv@cisco.com EMail: jpv@cisco.com
Appendix A. Acknowledgments Appendix A. Acknowledgments
The idea for this work grew out of a conversation with Andrew Partan The idea for this work grew out of a conversation with Andrew Partan
and we would like to thank him for his contribution. The authors and we would like to thank him for his contribution. The authors
would like to thanks Peter Psenak for his review and helpful comments would like to thanks Peter Psenak for his review and helpful comments
early versions of the draft. early versions of the draft.
Comments from Abhay Roy, Vishwas Manral, and Vivek Dubey were
incorporated into the final draft version.
The RFC text was produced using Marshall Rose's xml2rfc tool. The RFC text was produced using Marshall Rose's xml2rfc tool.
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
skipping to change at page 13, line 41 skipping to change at page 14, line 41
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/