draft-ietf-ospf-mt-08.txt   draft-ietf-ospf-mt-09.txt 
Network Working Group P. Psenak Network Working Group P. Psenak
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Standards Track S. Mirtorabi Intended status: Standards Track S. Mirtorabi
Expires: July 24, 2007 Force10 Networks Expires: July 5, 2007 Force10 Networks
A. Roy A. Roy
L. Nguyen L. Nguyen
P. Pillay-Esnault P. Pillay-Esnault
Cisco Systems Cisco Systems
January 20, 2007 January 2007
Multi-Topology (MT) Routing in OSPF Multi-Topology (MT) Routing in OSPF
draft-ietf-ospf-mt-08.txt draft-ietf-ospf-mt-09.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 39 skipping to change at page 1, line 39
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 July 24, 2007. This Internet-Draft will expire on July 5, 2007.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This draft describes an extension to Open Shortest Path First (OSPF) This draft describes an extension to Open Shortest Path First (OSPF)
in order to define independent IP topologies called Multi-Topologies in order to define independent IP topologies called Multi-Topologies
(MTs). The Multi-Topologies extension can be used for computing (MTs). The Multi-Topologies extension can be used for computing
skipping to change at page 16, line 8 skipping to change at page 16, line 8
forwarded through those nodes during network topology changes. forwarded through those nodes during network topology changes.
8. Security Considerations 8. Security Considerations
This document does not raise any security issues that are not already This document does not raise any security issues that are not already
covered in [OSPF]. covered in [OSPF].
9. IANA Considerations 9. IANA Considerations
The T-bit as defined in [TOS-OSPF] for a router's TOS capability is The T-bit as defined in [TOS-OSPF] for a router's TOS capability is
redefined as the MT-bit in this document. No IANA action is required redefined as the MT-bit in this document. IANA is requested to
for the MT-bit. assign the MT-bit as defined in section Section 4.1.
Similarly, the TOS field for Router-LSAs, Summary-LSAs, Type-5 and Similarly, the TOS field for Router-LSAs, Summary-LSAs, Type-5 and
Type-7 AS-external LSAs as defined in [OSPF] is redefined as MT-ID in Type-7 AS-external LSAs as defined in [OSPF] is redefined as MT-ID in
Section 3.7. Section 3.7.
IANA is requested to create a new registry, "OSPF multi-topology ID IANA is requested to create a new registry, "OSPF multi-topology ID
values" with the assignment listed in Section 3.7 of this document values" with the assignment listed in Section 3.7 of this document
and registration policies for future assignments. and registration policies for future assignments.
10. References 10. References
skipping to change at page 20, line 50 skipping to change at page 20, line 50
Note that network LSA does not contain any MT-ID fields as the cost Note that network LSA does not contain any MT-ID fields as the cost
of the network to the attached routers is 0 and DR is shared by all of the network to the attached routers is 0 and DR is shared by all
topologies. topologies.
B.3. Summary-LSAs B.3. Summary-LSAs
Summary-LSAs are the Type 3 and 4 LSAs. These LSAs are originated by Summary-LSAs are the Type 3 and 4 LSAs. These LSAs are originated by
area border routers. Summary-LSAs describe inter-area destinations. area border routers. Summary-LSAs describe inter-area destinations.
For details concerning the construction of summary-LSAs, see Section For details concerning the construction of summary-LSAs, see Section
12.4.3 [OSPF]. 12.4.3 of [OSPF].
Type 3 summary-LSAs are used when the destination is an IP network. Type 3 summary-LSAs are used when the destination is an IP network.
In this case the LSA's Link State ID field is an IP network number In this case the LSA's Link State ID field is an IP network number
(if necessary, the Link State ID can also have one or more of the (if necessary, the Link State ID can also have one or more of the
network's "host" bits set; see Appendix E [OSPF] for details). When network's "host" bits set; see Appendix E [OSPF] for details). When
the destination is an AS boundary router, a Type 4 summary-LSA is the destination is an AS boundary router, a Type 4 summary-LSA is
used, and the Link State ID field is the AS boundary router's OSPF used, and the Link State ID field is the AS boundary router's OSPF
Router ID. (To see why it is necessary to advertise the location of Router ID. (To see why it is necessary to advertise the location of
each ASBR, consult Section 16.4 of [OSPF]). Other than the each ASBR, consult Section 16.4 of [OSPF]). Other than the
difference in the Link State ID field, the format of Type 3 and 4 difference in the Link State ID field, the format of Type 3 and 4
 End of changes. 6 change blocks. 
7 lines changed or deleted 7 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/