draft-ietf-ospf-cap-02.txt   draft-ietf-ospf-cap-03.txt 
Network Working Group Acee Lindem Network Working Group Acee Lindem
Internet Draft Naiming Shen Internet Draft Naiming Shen
Expiration Date: December 2004 Redback Networks Expiration Date: February 2005 Redback Networks
Rahul Aggarwal Rahul Aggarwal
Juniper Networks Juniper Networks
Scott Shaffer Scott Shaffer
Level 3 Communications Level 3 Communications
JP Vasseur JP Vasseur
Cisco Systems, Inc Cisco Systems, Inc
Extensions to OSPF for Advertising Optional Router Capabilities Extensions to OSPF for Advertising Optional Router Capabilities
draft-ietf-ospf-cap-02.txt draft-ietf-ospf-cap-03.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, I certify that any applicable
patent or IPR claims of which I am aware have been disclosed, and patent or IPR claims of which I am aware have been disclosed, and
any of which I become aware will be disclosed, in accordance with any of which I become aware will be disclosed, in accordance with
RFC 3668. RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 4, line 32 skipping to change at page 4, line 32
TLV is padded to four-octet alignment; padding is not included in TLV is padded to four-octet alignment; padding is not included in
the length field (so a three octet value would have a length of the length field (so a three octet value would have a length of
three, but the total size of the TLV would be eight octets). Nested three, but the total size of the TLV would be eight octets). Nested
TLV's are also 32-bit aligned. For example, a one byte value TLV's are also 32-bit aligned. For example, a one byte value
would have the length field set to 1, and three bytes of padding would have the length field set to 1, and three bytes of padding
would be added to the end of the value portion of the TLV. would be added to the end of the value portion of the TLV.
Unrecognized types are ignored. Unrecognized types are ignored.
2.1 OSPF Router Capabilities TLV 2.1 OSPF Router Capabilities TLV
The first defined TLV in the body of a RI opaque LSA is The first defined TLV in the body of an RI opaque LSA is
the Router Capabilities TLV. A router advertising a RI opaque LSA the Router Capabilities TLV. A router advertising an RI opaque LSA
SHOULD include the Router Capabilities TLV and SHOULD correctly SHOULD include the Router Capabilities TLV and SHOULD correctly
identify the status of the capabilities defined in section 2.2. identify the status of the capabilities defined in section 2.2.
The format of the Router Capabilities TLV is as follows: The format of the Router Capabilities TLV is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 6, line 7 skipping to change at page 6, line 7
4 OSPF graceful restart capable [5] 4 OSPF graceful restart capable [5]
5 OSPF graceful restart helper [5] 5 OSPF graceful restart helper [5]
6 Stub Router support [6] 6 Stub Router support [6]
7 Traffic Engineering support [4] 7 Traffic Engineering support [4]
8 OSPF point-to-point over LAN [9] 8 OSPF point-to-point over LAN [9]
9 OSPF Path Computation Server discovery [7, 8] 9 OSPF Path Computation Server discovery [7, 8]
10-31 Future assignments 10-31 Future assignments
2.3 Flooding Scope of the Router Information LSA 2.3 Flooding Scope of the Router Information LSA
The flooding scope of the 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 used. If a type 11 opaque LSA type 11 (AS-scoped) opaque LSA may be flooded. If a type 11 opaque
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 values in advertised NSSA/stub area type 10 advertise different capabilities when both NSSA/stub area type 10
LSA(s) and its AS scoped type 11 opaque LSA. The choice of LSA(s) and an AS scoped type 11 opaque LSA is advertised. The choice
flooding scope is made by the advertising router and is a matter of of flooding scope is made by the advertising router and is a matter
local policy. The originating router MAY advertise multiple Router of local policy. The originating router MAY advertise multiple RI
Information LSAs as long as the flooding scope differs. TLV opaque LSAs as long as the flooding scopes differ. TLV flooding
flooding scope rules will be specified on a per-TLV basis. scope rules will be specified on a per-TLV basis.
3. Security Consideration 3. Security Consideration
This memo does not create any new security issues for the OSPF This memo does not create any new security issues for the OSPF
protocol. Security considerations for the base OSPF protocol are protocol. Security considerations for the base OSPF protocol are
covered in [1]. covered in [1].
4. Acknowledgments 4. 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 would like to thanks Peter Psenak for his review and helpful
comments early versions of the draft. comments early versions of the draft.
Funding for the RFC Editor function is currently provided by the
Internet Society.
5. IANA Considerations 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 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. TLV's and sub-TLV's will be subject to OSPF WG review.
6. References 6. References
skipping to change at page 8, line 5 skipping to change at page 8, line 5
for OSPF", Internet Draft, work in progress. for OSPF", Internet Draft, work in progress.
[8] Vasseur, J., et al, "RSVP Path computation request and reply [8] Vasseur, J., et al, "RSVP Path computation request and reply
messages", draft-vasseur-mpls-computation-rsvp-te-03.txt, messages", draft-vasseur-mpls-computation-rsvp-te-03.txt,
work in progress work in progress
[9] N. Shen, et al, "Point-to-point operation over LAN in [9] N. Shen, et al, "Point-to-point operation over LAN in
link-state-routing protocols", Internet Draft, work in link-state-routing protocols", Internet Draft, work in
progress. progress.
9. Author Information 7. Author Information
Acee Lindem Acee Lindem
Redback Networks Redback Networks
350 Holger Way 350 Holger Way
San Jose, CA 95134 San Jose, CA 95134
e-mail: acee@redback.com e-mail: acee@redback.com
Naiming Shen Naiming Shen
Redback Networks Redback Networks
350 Holger Way 350 Holger Way
skipping to change at page 9, line 5 skipping to change at page 9, line 5
Scott Shaffer Scott Shaffer
Level 3 Communications Level 3 Communications
e-mail: scott.shaffer@level3.com e-mail: scott.shaffer@level3.com
JP Vasseur JP Vasseur
Cisco Systems, Inc. Cisco Systems, Inc.
300 Apollo Drive 300 Apollo Drive
Chelmsford, MA 01824 Chelmsford, MA 01824
e-mail: jpv@cisco.com e-mail: jpv@cisco.com
10. IPR Notice 8. Full Copyright Statement
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
11. Full Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78 and
except as set forth therein, the authors retain all their rights.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
9. Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
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
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
10. Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 

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