draft-ietf-ospf-cap-10.txt   draft-ietf-ospf-cap-11.txt 
Network Working Group A. Lindem (Editor) Network Working Group A. Lindem (Editor)
Internet-Draft Redback Networks Internet-Draft Redback Networks
Intended status: Standards Track N. Shen Intended status: Standards Track N. Shen
Expires: August 13, 2007 J. Vasseur Expires: November 8, 2007 J. Vasseur
Cisco Systems Cisco Systems
R. Aggarwal R. Aggarwal
Juniper Networks Juniper Networks
S. Shaffer S. Shaffer
BridgePort Networks BridgePort Networks
February 9, 2007 May 7, 2007
Extensions to OSPF for Advertising Optional Router Capabilities Extensions to OSPF for Advertising Optional Router Capabilities
draft-ietf-ospf-cap-10.txt draft-ietf-ospf-cap-11.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
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 1, line 40 skipping to change at page 1, line 40
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 August 13, 2007. This Internet-Draft will expire on November 8, 2007.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
It is useful for routers in an OSPFv2 or OSPFv3 routing domain to It is useful for routers in an OSPFv2 or OSPFv3 routing domain to
know the capabilities of their neighbors and other routers in the know the capabilities of their neighbors and other routers in the
routing domain. This draft proposes extensions to OSPFv2 and OSPFv3 routing domain. This draft proposes extensions to OSPFv2 and OSPFv3
skipping to change at page 10, line 40 skipping to change at page 10, line 40
| | | | | |
| 256-8175 | Reserved | | 256-8175 | Reserved |
| | | | | |
| 8176-8183 | Experimentation | | 8176-8183 | Experimentation |
| | | | | |
| 8184-8191 | Vendor Private Use | | 8184-8191 | Vendor Private Use |
+-----------+--------------------+ +-----------+--------------------+
OSPFv3 LSA Function Codes OSPFv3 LSA Function Codes
* OSPFv3 LSA function codes in the range 256-8175 are for * OSPFv3 LSA function codes in the range 256-8175 are not to be
experimental use; these will not be registered with IANA and
MUST NOT be mentioned by RFCs.
* OSPFv3 LSA function codes in the range 8176-8183 are not to be
assigned at this time. Before any assignments can be made in assigned at this time. Before any assignments can be made in
this range, there MUST be a Standards Track RFC that specifies this range, there MUST be a Standards Track RFC that specifies
IANA Considerations that covers the range being assigned. IANA Considerations that covers the range being assigned.
* OSPFv3 LSA function codes in the range 8176-8181 are for
experimental use; these will not be registered with IANA and
MUST NOT be mentioned by RFCs.
* OSPFv3 LSAs with an LSA Function Code in the Vendor Private * OSPFv3 LSAs with an LSA Function Code in the Vendor Private
Use range 8184-8191 MUST include the Vendor Enterprise Code as Use range 8184-8191 MUST include the Vendor Enterprise Code as
the first four octets following the 20 octets of LSA header. the first four octets following the 20 octets of LSA header.
* If a new LSA Function Code is documented, the documentation * If a new LSA Function Code is documented, the documentation
MUST include the valid combinations of the U, S2 and S1 bits MUST include the valid combinations of the U, S2 and S1 bits
for the LSA. It SHOULD also describe how the Link State ID is for the LSA. It SHOULD also describe how the Link State ID is
to be assigned. to be assigned.
2. Registry for OSPF RI TLVs - This top-level registry will be 2. Registry for OSPF RI TLVs - This top-level registry will be
 End of changes. 6 change blocks. 
9 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/