draft-ietf-ospf-mt-ospfv3-00.txt   draft-ietf-ospf-mt-ospfv3-01.txt 
Network Working Group Sina Mirtorabi Network Working Group Sina Mirtorabi
Internet Draft Abhay Roy Internet Draft Abhay Roy
Expiration Date: October 2005 Cisco Systems Expiration Date: September 2006 Cisco Systems
File name: draft-ietf-ospf-mt-ospfv3-00.txt File name: draft-ietf-ospf-mt-ospfv3-01.txt
April 2005 March 2006
Multi-topology routing in OSPFv3 (MT-OSPFv3) Multi-topology routing in OSPFv3 (MT-OSPFv3)
draft-ietf-ospf-mt-ospfv3-00.txt draft-ietf-ospf-mt-ospfv3-01.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions By submitting this Internet-Draft, each author represents that any
of section 3 of RFC 3667. By submitting this Internet-Draft, each applicable patent or other IPR claims of which he or she is aware
author represents that any applicable patent or other IPR claims of have been or will be disclosed, and any of which he or she becomes
which he or she is aware have been or will be disclosed, and any of aware will be disclosed, in accordance with Section 6 of BCP 79.
which he or she become aware will be disclosed, in accordance with
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
other groups may also distribute working documents as other groups may also distribute working documents as Internet-
Internet-Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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 September 5, 2006.
Copyright Notice
Copyright (C) The Internet Society (2006).
Abstract Abstract
This document describes an extensible mechanism to support multiple This document describes an extensible mechanism to support multiple
topologies (MT) in OSPFv3. These topologies can be used within the topologies (MT) in OSPFv3. These topologies can be used within the
same address family in order to compute different paths for different same address family in order to compute different paths for different
classes of service, or belong to different address families allowing classes of service, or belong to different address families allowing
an integrated definition of address family with OSPFv3. The extension an integrated definition of address family with OSPFv3. The extension
described in this document can further facilitate any future described in this document can further facilitate any future
extensions of OSPFv3. extensions of OSPFv3.
skipping to change at page 9, line 14 skipping to change at page 9, line 14
All fields are defined as in [OSPFv3]. All fields are defined as in [OSPFv3].
We define a Link-description TLV (LD-TLV). This TLV extends the We define a Link-description TLV (LD-TLV). This TLV extends the
router-LSA payload by defining sub-TLVs within each link description. router-LSA payload by defining sub-TLVs within each link description.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 1 (LD-TLV) | TLV Length | | 1 (LD-TLV) | TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link-Type | 0 | | Link-Type | Reserved | Link-Block Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface ID | | Interface ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Neighbor Interface ID | | Neighbor Interface ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Neighbor Router ID | | Neighbor Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
. sub-TLVs . . sub-TLVs .
. . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link-Type | 0 | | Link-Type | Reserved | Link-Block Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface ID | | Interface ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Neighbor Interface ID | | Neighbor Interface ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Neighbor Router ID | | Neighbor Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
. sub-TLVs . . sub-TLVs .
. . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | | ... |
All fields are defined as in [OSPFv3]. Link-Block Length : Define the length of link block including
Link-Type, Reserved, Link-Block Length, fixed ID
fields and sub-TLVs.
All other fields are defined as in [OSPFv3].
LD-TLV is the only top level TLV defined in this document. This TLV LD-TLV is the only top level TLV defined in this document. This TLV
should not be repeated within an E-router-LSA fragment, instead should not be repeated within an E-router-LSA fragment, instead
multiple link descriptions are included within the LD-TLV (Total multiple link descriptions are included within the LD-TLV (Total
sub-TLV length indicates the next link description). sub-TLV length indicates the next link description).
We define a Router Multi-Topology sub-TLV (RMT-sTLV) below. This We define a Router Multi-Topology sub-TLV (RMT-sTLV) below. This
sub-TLV could further contain sub-TLVs. sub-TLV could further contain sub-TLVs.
E-router-LSA must contain the LD-TLV and each link description must E-router-LSA must contain the LD-TLV and each link description must
skipping to change at page 18, line 7 skipping to change at page 18, line 7
| Referenced Link State ID (Optional) | | Referenced Link State ID (Optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | | ... |
Note that when the sub-TLV is present (S-bit set in the Note that when the sub-TLV is present (S-bit set in the
PrefixOptions) the sub-TLV is placed after Forwarding address and PrefixOptions) the sub-TLV is placed after Forwarding address and
external route Tag if they are present. external route Tag if they are present.
20.6 Extended Link-LSA 20.6 Extended Link-LSA
We define a new E-link-LSA with LS type of 0x1008. This LSA is We define a new E-link-LSA with LS type of 0x9008. This LSA is
generated for each link and carries each link's prefix in the generated for each link and carries each link's prefix in the
corresponding topology. It also carries next hop IP information corresponding topology. It also carries next hop IP information
for the supported address families. for the supported address families.
The processing and generation of this LSA is the same as for link-lsa The processing and generation of this LSA is the same as for link-lsa
as defined in [OSPFv3]. This LSA has a fixed portion followed by as defined in [OSPFv3]. This LSA has a fixed portion followed by
TLVs. TLVs.
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
 End of changes. 9 change blocks. 
16 lines changed or deleted 24 lines changed or added

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