OSPFv3 Protocol Principle

Internal
ODP500049 OSPFv3
Protocol Principle
ISSUE 1.0 www.huawei.com
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved

The Open Shortest Path First (OSPF)
Version 2 standard was first released in
RFC1247 of 1991. After multiple
revisions, the current standard is
established in RFC2328 in 1998. The
RFC2470 defines the basic standard of
OSPFv3. Modifications to OSPFv2 are
made to meet the requirements of IPv6
environment.
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 2

References
z OSPF_version_3 Overview
z RFC2740--OSPF for IPv6
z RFC2328--OSPF Version 2
z RFC2460--IPv6 Specification
z RFC2373--IP Version 6 Addressing

Architecture

z Upon completion of this course, you
will be able to:
> Understand the differences
between OSPFv3 and OSPFv2
> Protocol packet and LSA changes
> OSPFv3 protocol operation

Chapter 1 Differences Between OSPFv2
and OSPFv3
Chapter 2 OSPFv3 Protocol Packet
Chapter 3 LSA
Chapter 4 Protocol Operation

Chapter 1 Differences
1.1 Independency from the Network

Protocol
1.2 Scalability and Adaptation
1.3 Clear and Concise Features
1.4 Protocol Packet Format Changes

Independency from the Network Protocol
Link Based Operating
z OSPFv2 runs over the IP subnet.

> All nodes on the same link are located in one IP subnet or network.
> One of the preconditions for setting up the neighbor relationship is
that the two connected interfaces must be in the same IP subnet.
> The next hop address of each route is the IP address in the same
network segment as that of the router interface.
z OSPFv3 runs over the link.
> The two nodes on the same link do not have to possess the same
prefix.
> Independent of the network protocol, it is easy to expand to adapt
various protocols.

The Addressing Semantics are Removed
z The defined data format of the OSPFv2 protocol is related to the IP

protocol. Many fields in the protocol packet and the LSA are from an
IP address, mask or IP subnet number over the network.
z In OSPFv3, the address of IPv6 only appears in the LSA load carried
in the LSU packet, but does not appear in the OSPF packet any more.
z The Router ID and Area ID in SPFv3 and Link State ID of LSA are
still 32 bits, and they are used as numbers only.

Using the local link address
z Use the local address of the link as the next hop of the route, except
the Virtual-Link.
z It is independent of the IP, and can expand the route to support

multiple protocols.

Using the specify LSA to advertise the prefix
z OSPFv3 uses Link-LSA and Inter-Area-Prefix-LSA to advertise the

prefix.
> The IPv6 prefix information within a link is announced by the link-
LSA.
> The inter-area-prefix-LSA is responsible for announcing the IPv6
prefix to the local area.
z With the separate transfer of topology and prefix information,

OSPFv3 is independent of the network protocol.


Protocol

Scalability and Adaptation
Scalability and Adaptation
z Supporting multiple instances
z Handling unknown LSAs

> Being treated as having Link-Local flooding scope, and
flooded to the local link.
> Being handled as a known LSA, stored and flooded.
− Note: This LSA does not participate in the calculation of
the LSA of the local router.


Protocol

Clear and Concise Features
Clear and Concise Features
z OSPF authentication changes

z Identifying neighbors by Router ID
z Changes of the flooding scope
z Stub area support


Protocol

Protocol Packet Format Changes
z OSPFv3 packet type:
> Hello, DBD, LSR, LSU, LSAck
z OSPF packet format changes
> The Hello packet does not contain the address information;
> The Option fields in the Hello packet and the DBD packet are extended
to 24 bits.
> Two option bits R bit and V6 bit are added to the Options field.
> The authentication of the OSPF packet header and the authentication
type field (AuType) are cancelled.
> The OSPF packet header introduces an Instance ID, so than multiple
OSPF instances run over one link

LSA format changes
z The Options field in the LSA header is moved to the following LSA:
> Router-LSA、Network-LSA、Inter-Area-Router-LSA and Link-
LSA。
z The LS Type field of the LSA header is extended to 16 bits.
z The address in the LSA is expressed in the mode of [prefix, prefix
length].
z All addressing semantics are deleted.
z The interface information can be released through multiple Router-
LSAs.
z LSA——Link-LSA and Intra-Area-Prefix-LSA are introduced.
z Type-3 LSA is renamed Inter-Area-Prefix-LSA, and Type-4 LSA is
renamed Inter-Area-Router-LSA.

Protocol Packet Format Changes (Cont.)
LSA format changes
z In Inter-Area-Prefix-LSA, Inter-Area-Router-LSA and AS-external-

LSA, the Link State ID does not have the addressing semantics any
more, but it is only used to identify an LSA.
z The forwarding address in the AS-external-LSA can be optional.
z The Options field of the Network LSA is set to logical OR of the

Options field value announced in the Lin-LSA of each router.

and OSPFv3
Chapter 3 LSA

2.1 Protocol Packet Encapsulation
2.2 Option Field
2.3 Protocol Packet Header
2.4 Various protocol packets

Protocol Packet Encapsulation
Protocol Packet Encapsulation
z The OSPFv3 protocol number is still 89, which is identified in the IPv6
Next Header.
IPv6
IPv6 OSPF
OSPF Packet
Packet
Next
Next Header
Header 89
89
z The TYPE field in the packet header is used to identify five packet
types.
z It sends protocol packets through the multicast address, while the
IPv6 Hop Limit is 1, and Virtual-Link sends update packets through
the unicast.
> AllSPfRouters：FF02::5
> AllDRouters：FF02::6

2.2 Option Field

Option Field
Option Field
0 18 19 20 21 22 23
DC R N MC E V6
z It appears in some protocol packets and LSA.

> Hello，DBD，Router-LSA，Network-LSA，Inter-Area-Router-
LSA and Link-LSA
z It enables the router to support optional capabilities and to announce
the capabilities to other routers mutually each other.
z The routers with different capabilities can work in one OSPF route
domain.

2.2 Option Field

Protocol Packet Header
Comparison of packet header
Version # Type Packet length
Router ID
z OSPFv2 Area ID
> 24 Bytes Checksum AuType

Authentication
Authentication
Version # Type Packet length

z OSPFv3 Router ID
Area ID
> 16 Bytes
Checksum Instance ID 0

2.2 Option Field
2.4 Various Protocol Packets

Various Protocol Packets
Protocol Packet Types

z Hello
> It is used to detect neighbors, elect DR and BDR, and maintain
adjacency relation.
z DBD (Database Description)
> It is used to describe the content of the link status database.
z LSR (Link State Request)
> It uses the LSR packet to request the desired LSA from the
neighbor.
z LSU (Link State Update)
> The transfer of the LSA is finally completed through the LSU.
z LSAck (Link State Acknowledgment)
> LSAck acknowledges the received LSU.

and OSPFv3
Chapter 3 LSA

Chapter 3 LSA
3.1 LSA Header
3.2 Prefix Option Field
3.3 Various LSAs

LSA Header
Comparison of LSA header format
LS Age Options LS Type
Link State ID
z OSPFv2
Advertising Router
> 20 Bytes LS Sequence Number
LS CheckSum Length
LS Age LS Type
Link State ID
z OSPFv3 Advertising Router
> 20 Bytes LS Sequence Number
LS CheckSum Length

LSA Header
LS Type
U
U S2
S2 S1
S1 LSA
LSA Function
Function Code
Code
zU：It identifies the method for handling unknown LSAs.
zS2 and S1: It identifies the flooding scope of the LSA.

>00: Link-local flooding scope
>01: Area flooding scope
>10: AS flooding scope
>11: Reserved

LSA Header
LS Type
LSA Function Code LS Value

Router-LSA 1 0x2001
Network-LSA 2 0x2002
Inter-Area-Prefix-LSA 3 0x2003
Inter-Area-Router-LSA 4 0x2004
AS-External-LSA 5 0x4005
Type-7-LSA 7 0x2007
Link-LSA 8 0x0008
Intra-Area-Prefix-LSA 9 0x2009

LSA Header
Flooding
Advertising Router Link-State ID
Scope
Router-LSA All router Area Router ID of router
Network-LSA DR Area Router ID of DR
Inter-Area-Prefix-LSA ABR Area Random
Inter-Area-Router-LSA ABR Area Random
AS-External-LSA ASBR AS Random
the router’s interface ID of

Link-LSA All router Link-Local
the link
Intra-Area-Prefix-LSA All router Area Random

Chapter 3 LSA
3.1 LSA Header
3.3 Various LSAs

Prefix Option Field
Prefix Option
0 4 5 6 7
P
P MC
MC LA
LA NU
NU
zIt is used to express some features of a prefix to implement corresponding judging

and processing during various routing calculation.
zNU
>Non-Unicast Bit
zLA
>Local Address Bit
zMC
>Multicast Bit
zP
>Propagate Bit

Chapter 3 LSA
3.1 LSA Header
3.3 Various LSAs

LSA Types
Router-LSA 32 bits
Flag Options
z LS Type：0x2001；Flooding
scope: area 1 Byte 3 Bytes
z Each Router-LSA contains several Type 0 Metric

link descriptions, and each link
description describes the
information about one interface of Interface ID
the router.
z Itcan use the description Neighbor Interface ID
information about multiple Router-
LSAs, and use the Link-State ID to
distinguish multiple different Neighbor Router ID
Router-LSAs.

LSA Types
Flag Field of Router-LSA
0 31
00 W
W E
E V
V B
B Options
Options
zW
>When it is 1, it indicates that this router is a multicast wild-card
receiver.
zE
>When it is 1, it indicates that this router is an ASBR.
zV
>When it is 1, it indicates that this router is an endpoint of one
virtual link across the local area.
zB
>When it is 1, it indicates that this router is an ABR.

LSA Types
Type Field of Router-LSA
Type description Peer Router-ID Peer Interface-ID

It connects to another
1 router in point-to-point Peer Router-ID Peer Interface ID
mode
It connects to the Transit
2 DR’s Router-ID DR’s Interface ID
network.
3 Reserved --- ---
Peer VLINK Interface

4 Virtual connection Peer Router-ID
ID

Router-LSA Example
<RTA> display ospfv3 lsdb router originate-router 1.1.1.1
Router-LSA (Area 0.0.0.0)
LS Age: 872 2.2.2.2

LS Type: Router-LSA
Link State ID: 0.0.0.0 4.4.4.4 1.1.1.1
Originating Router: 1.1.1.1 RTB
LS Seq Number: 0x80000008
Checksum: 0x0FC2 RTD RTA
Length: 56 3.3.3.3
Flags: 0x00 (-|-|-|-)
Options: 0x000013 (-|R|-|-|E|V6) Area 0
RTC
Link connected to: a Transit Network
Metric: 1
Interface ID: 0x18000202
Neighbor Interface ID: 0x18000202 Å DR Interface ID
Neighbor Router ID: 2.2.2.2 Å DR Router ID
Link connected to: another Router (point-to-point)

Metric: 1562
Interface ID: 0x18000286
Neighbor Interface ID: 0x18000206 ÅNeighbor Interface ID
Neighbor Router ID: 4.4.4.4 ÅNeighbor Router ID

LSA Types
Network-LSA
z LS Type：0x2002；Flooding scope: area.

32 bits
z Options：
0 Options
>It forms a logical OR relation with the 1 Byte 3 Bytes
Options of the Link-LSA.
Attached Router 1
z Attached Router：
……
>Router ID of all routers over this link
Attached Router n
z It has the Broadcast of two or more routers
or one Network-LSA needs to be set up by
the DR for the NBMA network.
z One Network-LSA lists all connected
routers over this link.

Network-LSA Example
<RTA>display ospfv3 lsdb network
OSPFv3 Router with ID (1.1.1.1) (Process 1)
Network-LSA (Area 0.0.0.0)
LS Age: 95
LS Type: Network-LSA
Link State ID: 24.0.2.2 Å DR Interface ID 2.2.2.2
Originating Router: 2.2.2.2 Å DR Router ID
4.4.4.4 1.1.1.1
LS Seq Number: 0x80000006 RTB
Checksum: 0xCB18
Length: 36 RTD RTA
3.3.3.3
Options: 0x000013 (-|R|-|-|E|V6)
Attached Router: 2.2.2.2 Å Router ID of RTB
Area 0
Attached Router: 1.1.1.1 Å Router ID of RTA RTC
Attached Router: 3.3.3.3 Å Router ID of RTC

LSA Types
Inter-Area-Prefix-LSA
32 bits
0 Metric
z The value of the LS type is 1 Byte 3 Bytes

0x2003. Flooding scope: area. Prefix Prefix
0
Length Option
2 Bytes
1 Byte 1 Byte
z InIPv4, the Inter-Area-Prefix-
Prefix Address
LSA is called Type 3
128 Bit
Summary-LSA.
……
Prefix address
128 Bit

Inter-Area-Prefix-LSA Selection
<RTC>display ospfv3 lsdb inter-prefix originate-

router 1.1.1.1
Inter-Area-Prefix-LSA (Area 0.0.0.1)

Area 0 2.2.2.2
LS Age: 89
4.4.4.4 1.1.1.1
LS Type: Inter-Area-Prefix-LSA RTB
Link State ID: 0.0.0.3
RTD RTA
Originating Router: 1.1.1.1 3.3.3.3
LS Seq Number: 0x80000002
Serial 6/0/0:
Checksum: 0xB5F6 3000:1:1::1/48 Inter-Area-Prefix-LSA RTC
Length: 36 3000:2:2::1/48 Area 1
Metric: 1562 Loopback 0:

Prefix: 3000:1:1::/48 3000:3:3::3/128
Prefix Options: 0

LSA Types
32 bits
Inter-Area-Router-LSA
0 Options
1 Byte 3 Bytes
z The value of the LS type is
0 Metric
0x2004. Flooding scope: area.
1 Byte 3 Bytes
Destination Router ID
z InIPv4, the Inter-Area-Router- 4 Bytes
LSA is called Type 4
Summary-LSA.

Inter-Area-Router-LSA Example
<RTB>display ospfv3 lsdb inter-router
Inter-Area-Router-LSA (Area 0.0.0.1) Static Route:

3001:1:1::/ 48
LS Age: 38 2.2.2.2
LS Type: Inter-Area-Router-LSA Import
4.4.4.4 1.1.1.1
Link State ID: 0.0.0.1 RTB
Originating Router: 1.1.1.1
RTD RTA
LS Seq Number: 0x80000001 3.3.3.3
Checksum: 0xEF02
Area 0
Length: 32 RTC
Area 1
Options: 0x000013 (-|R|-|-|E|V6)
Metric: 1562
Destination Router ID: 4.4.4.4 Å ASBR Router ID

LSA Types
32 bits
AS-External-LSA
Metric
Flag
z The value of the LS type 3 Bytes
is 0x4005. Flooding scope: Prefix Prefix
Referenced LS Type
AS Length Options
2 Bytes
1 Byte 1 Byte
z Each AS-external-LSA Address Prefix
describes the path of a 128 Bits
prefix which arrives at the Forwarding Address (Optional)

external of the
External Route Tag (Optional)
autonomous system.
Referenced Link State ID (Optional)

AS-External-LSA Example
<RTB>display ospfv3 lsdb external
AS-External-LSA
Static Route:
3001:1:1::/ 48
LS Age: 1027
2.2.2.2
LS Type: AS-External-LSA
Import
Link State ID: 0.0.0.1 4.4.4.4 1.1.1.1
RTB
LS Seq Number: 0x80000004 RTD RTA
Checksum: 0xD0C7 3.3.3.3
Length: 36
Area 0
Metric Type: 2 (Larger than any link state path) RTC
Area 1
Metric: 1
Prefix: 3001:1:1::/48 Å Import static route
Prefix Options: 0 (-|-|-|-)

LSA Types
Link-LSA
z Each connected link generates a Link-LSA

z Link Flooding Scope
z Function:
> Notifying other routers over the link of the local Link-Local
address, that is, local next hop address
> Collecting all IPv6 prefixes configured by the local router over
the link and notifying other routers over the link.
> Providing option information for the Network-LSA. It collects all
Link-LSAs over the link and option information obtained during
the operation in the Network-LSA over the link.

LSA Types 32 bits
Options
Link-LSA Rtr Pri
3 Bytes
z Rtr Pri: Priority of the router

over the link (Router Priority) Link-Local Interface Address
z Options: It provides Options of 128 Bits

the Network LSA.
z Link Local address configured # Prefixes
on the interface connecting the 32 Bits
router to the link (Link Local Prefix Prefix
address appears in the Link Length Options
0
LSA only)
z #Prefix: How many IPv6 Address Prefix
address prefixes does the LSA
128 Bits
contain?
z Other: Prefix triplet.
……

Link-LSA Selection
[RTA]display ospfv3 lsdb link 24.0.2.134
Link-LSA (Interface Serial6/0/0)
LS Age: 17
LS Type: Link-LSA
Link State ID: 24.0.2.134 Å Interface Index 2.2.2.2
Originating Router: 1.1.1.1 4.4.4.4 1.1.1.1
LS Seq Number: 0x80000024 RTB
Checksum: 0x7F10 RTD RTA

Length: 68 3.3.3.3
Priority: 1 Serial 6/0/0:

3000:1:1::1/48 Area 0
Options: 0x000013 (-|R|-|-|E|V6) RTC
3000:2:2::1/48
Link-Local Address: FE80::5ECC:5200:1
Number of Prefixes: 2
Prefix: 3000:1:1::/48
Prefix: 3000:2:2::/48

LSA Types
Intra-Area-Prefix-LSA
z Why to import the Intra-Area-Prefix-LSA?
> In OSPFv2, the subnet attached to the router and the Stub network
appears in the Router LSA. And the subnet attached to the Transit
network appears in the Network-LSA. In OSPFv3, the Router-LSA and
Network-LSA do not contain the address information any more, so the
Intra-Area-Prefix-LSA is imported.
z Intra-Area-Prefix-LSA contains the intra-area IPv6 Prefix information.
> Prefix attached to the router

> Prefix attached to the Stub network
> Prefix attached to the Transit network
z Each router or Transit network can generate multiple Intra-Area-Prefix-LSAs.

LSA Types
32 bits
Intra-Area-Prefix-LSA
# Prefix Referenced LS Type
16 Bits 16 Bits
z The LS type of the intra-
Referenced Link State ID
area-prefix-LSA is 0x2009.
32 Bits
Referenced Advertising Router

z With area flooding scope. 32 Bits
Prefix Prefix
Metric
Length Options
Address Prefix
128 Bits
……

Intra-Area-Prefix-LSA(Router) Example
<RTA>display ospfv3 lsdb intra-prefix originate-router 1.1.1.1
Intra-Area-Prefix-LSA (Area 0.0.0.0)
LS Age: 20
LS Type: Intra-Area-Prefix-LSA
Link State ID: 0.0.0.1
LS Seq Number: 0x8000003E
Checksum: 0xA932 2.2.2.2
Length: 76
Number of Prefixes: 3 4.4.4.4 1.1.1.1
Referenced LS Type: 0x2001 Å Referenced Router LSA RTB
Referenced Link State ID: 0.0.0.0 Å First Router LSA LS ID
Referenced Originating Router: 1.1.1.1 Å Router ID RTD RTA
3.3.3.3
Prefix: 3000:2:2::/48 Serial 6/0/0:
Prefix Options: 0 (-|-|-|-) 3000:1:1::1/48
Metric: 1562 Area 0 RTC
3000:2:2::1/48
Prefix: 3000:1:1::/48
Prefix Options: 0 (-|-|-|-) Loopback 0:
Metric: 1562
3000:3:3::3/128
Prefix: 3000:3:3::3/128
Prefix Options: 2 (-|-|LA|-) Å Local host address
Metric: 0

Intra-Area-Prefix-LSA(Transit) Example
<RTA>display ospfv3 lsdb intra-prefix originate-router 2.2.2.2
Intra-Area-Prefix-LSA (Area 0.0.0.0)
LS Age: 1407
LS Type: Intra-Area-Prefix-LSA Ethernet 6/0/0:
Link State ID: 0.0.0.2 2000:2:2::2/48
LS Seq Number: 0x80000028 Ethernet 6/0/0:
Checksum: 0xB1E7 2000:1:1::1/48 2.2.2.2
Length: 68
Number of Prefixes: 3 4.4.4.4 1.1.1.1
Referenced LS Type: 0x2002 Å Referenced Network-LSA RTB
Referenced Link State ID: 24.0.2.2 Å DR interface ID
Referenced Originating Router: 2.2.2.2 Å DR Router ID RTA
RTD
3.3.3.3
Prefix: 2000:1:1::/48
Metric: 0 Area 0 RTC
Prefix: 2000:2:2::/48
Metric: 0 Ethernet 6/0/0:
2000:3:3::3/48
Prefix: 2000:3:3::/48
Metric: 0

and OSPFv3
Chapter 3 LSA

4.1 Electing DR and BDR
4.2 LSDB
4.3 LSA Flooding
4.4 Routing Calculation
4.5 Virtual-Link

Protocol Operation
Electing DR and BDR
z Sameness:
> The election algorithm is invariable, and is
consistent with the OSPFv2 algorithm.
z Difference:
> The interface address is not used as the identifier
any more, but the Router ID is used instead.

4.2 LSDB
4.3 LSA Flooding
4.5 Virtual-Link

Protocol Operation
LSDB
z LSDB Classification：
> Link LSDB
− Storing the LSA with link local flooding scope.
> Area LSDB
− Storing the LSA with area flooding scope.
> AS LSDB
− Storing the LSA with AS flooding scope.

Protocol Operation
LSDB
Flooring Scope LS Type U Bit LSDB

Known -- Link
Link-Local Unknown 0 Link
Unknown 1 Link
Known -- Area
Area Unknown 0 Link
Unknown 1 Area
Known -- AS
AS Unknown 0 Link
Unknown 1 AS

4.2 LSDB
4.3 LSA Flooding
4.5 Virtual-Link

Protocol Operation
LSA Flooring Scope
z Receiving LSA
> LSA flooring scope
> Settings of U bit in the LS type
> New specifications of the Stub area
z Sending LSA
> LSA flooding scope and legal interface
> Whether the LSA has recognized LS type
> Settings of the U bit in the LS type

4.2 LSDB
4.3 LSA Flooding
4.5 Virtual-Link

Protocol Operation
Routing Calculation
z During the SPF calculation procedure, the topology generation and

the routing calculation procedures are separated.
> Step1: Calculate the Router-LSA and Network-LSA to get the
network topology.
> Step2: Calculate the Intra-Area-Prefix-LSA to get the route.
z The intra-area, inter-area, AS external and route recalculation are

basically the same as those of OSPFv2.

4.2 LSDB
4.3 LSA Flooding
4.5 Virtual-Link

Protocol Operation
Virtual-Link
z Any LSA with AS flooding scope cannot traverse the Virtual-Link.
z The Site-Local or Global Scope address must be used as the source

address or next hop of the Virtual-Link.

z Understand differences between
小结 OSPFv2 and OSPFv3
z OSPFv3 protocol packet and various
LSAs
z Similar protocol algorithm

Thank You
www.huawei.com

OSPFv3 Protocol Principle

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OSPFv3 Protocol Principle

Uploaded by

Copyright:

Available Formats

Internal

ISSUE 1.0 www.huawei.com

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 2

z RFC2740--OSPF for IPv6

z RFC2373--IP Version 6 Addressing

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 3

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 4

Chapter 2 OSPFv3 Protocol Packet

Chapter 4 Protocol Operation

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 5

1.1 Independency from the Network

1.2 Scalability and Adaptation

1.3 Clear and Concise Features

1.4 Protocol Packet Format Changes

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 6

Link Based Operating

z OSPFv2 runs over the IP subnet.

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 7

The Addressing Semantics are Removed

z The defined data format of the OSPFv2 protocol is related to the IP

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 8

Using the local link address

z It is independent of the IP, and can expand the route to support

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 9

Using the specify LSA to advertise the prefix

z OSPFv3 uses Link-LSA and Inter-Area-Prefix-LSA to advertise the

z With the separate transfer of topology and prefix information,

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 10

1.1 Independency from the Network

1.2 Scalability and Adaptation

1.3 Clear and Concise Features

1.4 Protocol Packet Format Changes

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 11

Scalability and Adaptation

z Supporting multiple instances

z Handling unknown LSAs

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 12

1.1 Independency from the Network

1.2 Scalability and Adaptation

1.3 Clear and Concise Features

1.4 Protocol Packet Format Changes

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 13

Clear and Concise Features

z OSPF authentication changes

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 14

1.1 Independency from the Network

1.2 Scalability and Adaptation

1.3 Clear and Concise Features

1.4 Protocol Packet Format Changes

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 15

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 16

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 17

LSA format changes

z In Inter-Area-Prefix-LSA, Inter-Area-Router-LSA and AS-external-

z The forwarding address in the AS-external-LSA can be optional.

z The Options field of the Network LSA is set to logical OR of the

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 18

Chapter 2 OSPFv3 Protocol Packet

Chapter 4 Protocol Operation

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 19

2.1 Protocol Packet Encapsulation

2.2 Option Field

2.3 Protocol Packet Header