< draft-ietf-ospf-ospfv3-autoconfig-00.txt   draft-ietf-ospf-ospfv3-autoconfig-01.txt >
Network Working Group A. Lindem Network Working Group A. Lindem
Internet-Draft J. Arkko Internet-Draft J. Arkko
Intended status: Standards Track Ericsson Intended status: Standards Track Ericsson
Expires: April 8, 2013 October 5, 2012 Expires: October 16, 2013 April 14, 2013
OSPFv3 Auto-Configuration OSPFv3 Auto-Configuration
draft-ietf-ospf-ospfv3-autoconfig-00.txt draft-ietf-ospf-ospfv3-autoconfig-01.txt
Abstract Abstract
OSPFv3 is a candidate for deployments in environments where auto- OSPFv3 is a candidate for deployments in environments where auto-
configuration is a requirement. One such environment is the IPv6 configuration is a requirement. One such environment is the IPv6
home network where users expect to simply plug in a router and have home network where users expect to simply plug in a router and have
it automatically use OSPFv3 for intra-domain routing. This document it automatically use OSPFv3 for intra-domain routing. This document
describes the necessary mechanisms for OSPFv3 to be self-configuring. describes the necessary mechanisms for OSPFv3 to be self-configuring.
Status of this Memo Status of this Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on April 8, 2013. This Internet-Draft will expire on October 16, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 22 skipping to change at page 2, line 22
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements notation . . . . . . . . . . . . . . . . . . 3 1.1. Requirements notation . . . . . . . . . . . . . . . . . . 3
1.2. Acknowledgments . . . . . . . . . . . . . . . . . . . . . 3 1.2. Acknowledgments . . . . . . . . . . . . . . . . . . . . . 3
2. OSPFv3 Default Configuration . . . . . . . . . . . . . . . . . 4 2. OSPFv3 Default Configuration . . . . . . . . . . . . . . . . . 5
2.1. Wait Timer Reduction . . . . . . . . . . . . . . . . . . . 4 3. OSPFv3 HelloInterval/RouterDeadInterval Flexibility . . . . . 6
3. OSPFv3 Router ID Selection . . . . . . . . . . . . . . . . . . 6 3.1. Wait Timer Reduction . . . . . . . . . . . . . . . . . . . 6
4. OSPFv3 Adjacency Formation . . . . . . . . . . . . . . . . . . 7 4. OSPFv3 Router ID Selection . . . . . . . . . . . . . . . . . . 7
5. OSPFv3 Duplicate Router-ID Detection and Resolution . . . . . 8 5. OSPFv3 Adjacency Formation . . . . . . . . . . . . . . . . . . 8
5.1. Duplicate Router-ID Detection for Neighbors . . . . . . . 8 6. OSPFv3 Duplicate Router ID Detection and Resolution . . . . . 9
5.2. Duplicate Router-ID Detection for OSPFv3 Routers that 6.1. Duplicate Router ID Detection for Neighbors . . . . . . . 9
are not Neighbors . . . . . . . . . . . . . . . . . . . . 8 6.2. Duplicate Router ID Detection for OSPFv3 Routers that
5.2.1. OSPFv3 Router Auto-Configuration LSA . . . . . . . . . 8 are not Neighbors . . . . . . . . . . . . . . . . . . . . 9
5.2.2. Router-Hardware-Fingerprint TLV . . . . . . . . . . . 10 6.2.1. OSPFv3 Router Auto-Configuration LSA . . . . . . . . . 9
5.3. Duplicate Router-ID Resolution . . . . . . . . . . . . . . 10 6.2.2. Router-Hardware-Fingerprint TLV . . . . . . . . . . . 11
5.4. Change to Received Self-Originated LSA Processing . . . . 11 6.3. Duplicate Router ID Resolution . . . . . . . . . . . . . . 11
6. Security Considerations . . . . . . . . . . . . . . . . . . . 12 6.4. Change to Received Self-Originated LSA Processing . . . . 12
7. Management Considerations . . . . . . . . . . . . . . . . . . 13 7. Security Considerations . . . . . . . . . . . . . . . . . . . 13
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 8. Management Considerations . . . . . . . . . . . . . . . . . . 14
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
9.1. Normative References . . . . . . . . . . . . . . . . . . . 15 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
9.2. Informative References . . . . . . . . . . . . . . . . . . 15 10.1. Normative References . . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16 10.2. Informative References . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction 1. Introduction
OSPFv3 [OSPFV3] is a candidate for deployments in environments where OSPFv3 [OSPFV3] is a candidate for deployments in environments where
auto-configuration is a requirement. Its operation is largely auto-configuration is a requirement. Its operation is largely
unchanged from the base OSPFv3 protocol specification [OSPFV3]. unchanged from the base OSPFv3 protocol specification [OSPFV3].
The following aspects of OSPFv3 auto-configuration are described: The following aspects of OSPFv3 auto-configuration are described:
1. Default OSPFv3 Configuration 1. Default OSPFv3 Configuration
2. Unique OSPFv3 Router-ID generation 2. HelloInterval/RouterDeadInterval Flexibility
3. OSPFv3 Adjacency Formation 3. Unique OSPFv3 Router-ID generation
4. Duplicate OSPFv3 Router-ID Resolution 4. OSPFv3 Adjacency Formation
5. Duplicate OSPFv3 Router-ID Resolution
1.1. Requirements notation 1.1. Requirements notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC-KEYWORDS]. document are to be interpreted as described in [RFC-KEYWORDS].
1.2. Acknowledgments 1.2. Acknowledgments
This specification was inspired by the work presented in the Homenet This specification was inspired by the work presented in the Homenet
skipping to change at page 4, line 17 skipping to change at page 5, line 17
For complete auto-configuration, OSPFv3 will need to choose suitable For complete auto-configuration, OSPFv3 will need to choose suitable
configuration defaults. These include: configuration defaults. These include:
1. Area 0 Only - All auto-configured OSPFv3 interfaces MUST be in 1. Area 0 Only - All auto-configured OSPFv3 interfaces MUST be in
area 0. area 0.
2. OSPFv3 SHOULD be auto-configured on for IPv6 on all interfaces 2. OSPFv3 SHOULD be auto-configured on for IPv6 on all interfaces
intended as general IPv6-capable routers. Optionally, an intended as general IPv6-capable routers. Optionally, an
interface MAY be excluded if it is clear that running OSPFv3 on interface MAY be excluded if it is clear that running OSPFv3 on
the interface is not required. For example, if manual the interface is not required. For example, if manual
configuration or an other condition indicates that an interface configuration or another condition indicates that an interface is
is connected to an Internet Service Provider (ISP) and there is connected to an Internet Service Provider (ISP) and there is no
no Border Gateway Protocol (BGP) [BGP] peering, there is Border Gateway Protocol (BGP) [BGP] peering, there is typically
typically no need to employ OSPFv3. However, note that in many no need to employ OSPFv3. However, note that in many
environments it can be useful to test whether an OSPFv3 adjacency environments it can be useful to test whether an OSPFv3 adjacency
can be established. In home networking environments, an can be established. In home networking environments, an
interface where no OSPFv3 neighbors are found but a DHCP prefix interface where no OSPFv3 neighbors are found but a DHCP IPv6
can be acquired may be considered as an ISP interface. prefix can be acquired may be considered as an ISP-facing
interface and running OSPFv3 is unnecessary.
3. OSPFv3 interfaces will be auto-configured to an interface type 3. OSPFv3 interfaces will be auto-configured to an interface type
corresponding to their layer-2 capability. For example, Ethernet corresponding to their layer-2 capability. For example, Ethernet
interfaces will be auto-configured as broadcast networks and interfaces will be auto-configured as broadcast networks and
Point-to-Point Protocol (PPP) interfaces will be auto-configured Point-to-Point Protocol (PPP) interfaces will be auto-configured
as Point-to-Point interfaces. Most extant OSPFv3 implementations as Point-to-Point interfaces. Most extant OSPFv3 implementations
do this already. do this already. Auto-configured operation over wireless
networks required point-to-multipoint (P2MP) and dynamic metrics
based on wireless feedback is not within the scope of this
document. However, auto-configuration is not precluded in these
environments.
4. OSPFv3 interfaces MUST use the default HelloInterval, 10 seconds, 4. OSPFv3 interfaces MAY use arbitrary HelloInterval and
and RouterDeadInterval, 40 seconds, as suggested in Appendix C of RouterDeadInterval as specified in Section 3. Of course,
[OSPFV3]. identical an HelloInterval and RouterDeadInterval will still be
required to form an adjacency with an OSPFv3 router not
supporting auto-configuration [OSPFV3].
5. All OSPFv3 interfaces SHOULD be auto-configured to use an 5. All OSPFv3 interfaces SHOULD be auto-configured to use an
Interface Instance ID of 0 that corresponds to the base IPv6 Interface Instance ID of 0 that corresponds to the base IPv6
unicast address family instance ID as defined in [OSPFV3-AF]. unicast address family instance ID as defined in [OSPFV3-AF].
Similarly, if IPv4 unicast addresses are advertised in a separate Similarly, if IPv4 unicast addresses are advertised in a separate
auto-configured OSPFv3 instance, the base IPv4 unicast address auto-configured OSPFv3 instance, the base IPv4 unicast address
family instance ID value, i.e., 64, SHOULD be auto-configured as family instance ID value, i.e., 64, SHOULD be auto-configured as
the Interface Instance ID for all interfaces corresponding to the the Interface Instance ID for all interfaces corresponding to the
OSPFv3 instance [OSPFV3-AF]. OSPFv3 instance [OSPFV3-AF].
2.1. Wait Timer Reduction 3. OSPFv3 HelloInterval/RouterDeadInterval Flexibility
Auto-configured OSPFv3 routers will not require identical an
HelloInterval and RouterDeadInterval to form adjacencies. Rather,
the received HelloInterval will be ignored and the received
RouterDeadInterval will be used to determine OSPFv3 liveliness with
the sending router. In other words, the Inactivity Timer for each
neighbor will reflect that neighbor's advertised RouterDeadInterval
and MAY be different from other OSPFv3 routers on the link without
impacting adjacency formation. A similar mechanism requiring
additional signaling is being proposed for all OSPFv2 and OSPFv3
routers [ASYNC-HELLO].
3.1. Wait Timer Reduction
In many situations, auto-configured OSPFv3 routers will be deployed In many situations, auto-configured OSPFv3 routers will be deployed
in environments where back-to-back ethernet connections are utilized. in environments where back-to-back ethernet connections are utilized.
When this is the case, an OSPFv3 broadcast interface will not come up When this is the case, an OSPFv3 broadcast interface will not come up
until the other OSPFv3 router is connected and the routers will wait until the other OSPFv3 router is connected and the routers will wait
RouterDeadInterval seconds before forming an adjacency [OSPFV2]. In RouterDeadInterval seconds before forming an adjacency [OSPFV2]. In
order to reduce this delay, an auto-configured OSPFv3 router MAY order to reduce this delay, an auto-configured OSPFv3 router MAY
reduce the wait interval to a value no less than (HelloInterval + 1), reduce the wait interval to a value no less than (HelloInterval + 1),
i.e., 11 seconds. Reducing the setting will slightly increase the i.e., 11 seconds. Reducing the setting will slightly increase the
likelihood of the Designated Router (DR) flapping but is preferable likelihood of the Designated Router (DR) flapping but is preferable
to the long adjacency formation delay. Note that this value is not to the long adjacency formation delay. Note that this value is not
included in OSPFv3 Hello packets and does not impact included in OSPFv3 Hello packets and does not impact
interoperability. interoperability.
3. OSPFv3 Router ID Selection 4. OSPFv3 Router ID Selection
As OSPFv3 Router implementing this specification must select a unique As OSPFv3 Router implementing this specification must select a unique
Router-ID. A pseudo-random number SHOULD be used for the OSPFv3 Router ID. A pseudo-random number SHOULD be used for the OSPFv3
Router-ID. The generation should be seeded with a variable that is Router ID. The generation should be seeded with a variable that is
likely to be unique in that environment. A good choice of seed would likely to be unique in that environment. A good choice of seed would
be some portion or hash of the Route-Hardware-Fingerprint as be some portion or hash of the Route-Hardware-Fingerprint as
described in Section 5.2.2. described in Section 6.2.2.
Since there is a possibility of a Router ID collision, duplicate Since there is a possibility of a Router ID collision, duplicate
Router ID detection and resolution are required as described in Router ID detection and resolution are required as described in
Section 5 and Section 5.3. Section 6 and Section 6.3.
4. OSPFv3 Adjacency Formation 5. OSPFv3 Adjacency Formation
Since OSPFv3 uses IPv6 link-local addresses for all protocol messages Since OSPFv3 uses IPv6 link-local addresses for all protocol messages
other than message sent on virtual links (which are not applicable to other than messages sent on virtual links (which are not applicable
auto-configuration), OSPFv3 adjacency formation can proceed as soon to auto-configuration), OSPFv3 adjacency formation can proceed as
as a Router-ID has been selected and the IPv6 link-local address has soon as a Router ID has been selected and the IPv6 link-local address
completed Duplicate Address Detection (DAD) as specified in IPv6 has completed Duplicate Address Detection (DAD) as specified in IPv6
Stateless Address Autoconfiguration [SLAAC]. Otherwise, there is no Stateless Address Autoconfiguration [SLAAC]. Otherwise, the only
change to the OSPFv3 base specification except with respect to changes to the OSPFv3 base specification are supporting
duplicate Router-ID detection and resolution as described in HelloInterval/RouterDeadInterval flexibility as described in
Section 5 and Section 5.3. Section 3. and duplicate Router ID detection and resolution as
described in Section 6 and Section 6.3.
5. OSPFv3 Duplicate Router-ID Detection and Resolution 6. OSPFv3 Duplicate Router ID Detection and Resolution
There are two cases of duplicate OSPFv3 Router-ID detection. One There are two cases of duplicate OSPFv3 Router ID detection. One
where the OSPFv3 router with the duplicate Router-ID is directly where the OSPFv3 router with the duplicate Router ID is directly
connected and one where it is not. In both cases, the resolution is connected and one where it is not. In both cases, the resolution is
for one of the routers with the duplicate OSPFv3 Router-ID to select for one of the routers with the duplicate OSPFv3 Router ID to select
a new one. a new one.
5.1. Duplicate Router-ID Detection for Neighbors 6.1. Duplicate Router ID Detection for Neighbors
In this case, a duplicate Router-ID is detected if any valid OSPFv3 In this case, a duplicate Router ID is detected if any valid OSPFv3
packet is received with the same OSPFv3 Router-ID but a different packet is received with the same OSPFv3 Router ID but a different
IPv6 link-local source address. Once that occurs, the OSPFv3 router IPv6 link-local source address. Once that occurs, the OSPFv3 router
with the numerically smaller IPv6 link-local address will need to with the numerically smaller IPv6 link-local address will need to
select a new Router-ID as described in Section 5.3. Note that the select a new Router ID as described in Section 6.3. Note that the
fact that the OSPFv3 router is a neighbor on a non-virtual interface fact that the OSPFv3 router is a neighbor on a non-virtual interface
implies that the router is directly connected. An OSPFv3 router implies that the router is directly connected. An OSPFv3 router
implementing this specification should assure that the inadvertent implementing this specification should assure that the inadvertent
connection of multiple router interfaces to the same physical link in connection of multiple router interfaces to the same physical link is
not misconstrued as detection of a different OSPFv3 router with a not misconstrued as detection of a different OSPFv3 router with a
duplicate Router-ID. duplicate Router ID.
5.2. Duplicate Router-ID Detection for OSPFv3 Routers that are not 6.2. Duplicate Router ID Detection for OSPFv3 Routers that are not
Neighbors Neighbors
OSPFv3 Routers implementing auto-configuration, as specified herein, OSPFv3 Routers implementing auto-configuration, as specified herein,
MUST originate an Auto-Config (AC) Link State Advertisement (LSA) MUST originate an Auto-Config (AC) Link State Advertisement (LSA)
including the Router-Hardware-Fingerprint Type-Length-Value (TLV). including the Router-Hardware-Fingerprint Type-Length-Value (TLV).
The Router-Hardware-Fingerprint TLV contains a variable length value The Router-Hardware-Fingerprint TLV contains a variable length value
that has a very high probability of uniquely identifying the that has a very high probability of uniquely identifying the
advertising OSPFv3 router. An OSPFv3 router implementing this advertising OSPFv3 router. An OSPFv3 router implementing this
specification MUST compare a received self-originated Auto-Config specification MUST compare a received self-originated Auto-Config
LSA's Router-Hardware-Fingerprint TLV against its own router hardware LSA's Router-Hardware-Fingerprint TLV against its own router hardware
fingerprint. If the fingerprints are not equal, there is a Router-ID fingerprint. If the fingerprints are not equal, there is a Router ID
conflict and the OSPFv3 Router with the numerically smaller router conflict and the OSPFv3 Router with the numerically smaller router
hardware fingerprint MUST select a new Router-ID as described in hardware fingerprint MUST select a new Router ID as described in
Section 5.3. Section 6.3.
This new LSA is designated for information related to OSPFv3 Auto- This new LSA is designated for information related to OSPFv3 Auto-
configuration and, in the future, could be used other auto- configuration and, in the future, could be used other auto-
configuration information, e.g., global IPv6 prefixes. However, this configuration information, e.g., global IPv6 prefixes. However, this
is beyond the scope of this document. is beyond the scope of this document.
5.2.1. OSPFv3 Router Auto-Configuration LSA 6.2.1. OSPFv3 Router Auto-Configuration LSA
The OSPFv3 Auto-Configuration (AC) LSA has a function code of TBD and The OSPFv3 Auto-Configuration (AC) LSA has a function code of TBD and
the S2/S1 bits set to 01 indicating Area Flooding Scope. The U bit the S2/S1 bits set to 01 indicating Area Flooding Scope. The U bit
will be set indicating that the OSPFv3 AC LSA should be flooded even will be set indicating that the OSPFv3 AC LSA should be flooded even
if it is not understood. The Link State ID (LSID) value will be a if it is not understood. The Link State ID (LSID) value will be a
integer index used to discriminate between multiple AC LSAs integer index used to discriminate between multiple AC LSAs
originated by the same OSPF Router. This specification only originated by the same OSPFv3 Router. This specification only
describes the contents of an AC LSA with a Link State ID (LSID) of 0. describes the contents of an AC LSA with a Link State ID (LSID) of 0.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS age |1|0|1| TBD | | LS age |1|0|1| TBD |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link State ID | | Link State ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Advertising Router | | Advertising Router |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS sequence number | | LS sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS checksum | Length | | LS checksum | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+- TLVs -+ +- TLVs -+
| ... | | ... |
OSPFv3 Auto-Configuration (AC) LSA OSPFv3 Auto-Configuration (AC) LSA
The format of the TLVs within the body of an AC LSA is the same as The format of the TLVs within the body of an AC LSA is the same as
the format used by the Traffic Engineering Extensions to OSPF [TE]. the format used by the Traffic Engineering Extensions to OSPF [TE].
The LSA payload consists of one or more nested Type/Length/Value The LSA payload consists of one or more nested Type/Length/Value
skipping to change at page 10, line 14 skipping to change at page 11, line 14
field (so a 3-octet value would have a length of 3, but the total field (so a 3-octet value would have a length of 3, but the total
size of the TLV would be 8 octets). Nested TLVs are also 32-bit size of the TLV would be 8 octets). Nested TLVs are also 32-bit
aligned. For example, a 1-byte value would have the length field set aligned. For example, a 1-byte value would have the length field set
to 1, and 3 octets of padding would be added to the end of the value to 1, and 3 octets of padding would be added to the end of the value
portion of the TLV. Unrecognized types are ignored. portion of the TLV. Unrecognized types are ignored.
The new LSA is designated for information related to OSPFv3 Auto- The new LSA is designated for information related to OSPFv3 Auto-
configuration and, in the future, can be used other auto- configuration and, in the future, can be used other auto-
configuration information, e.g., global IPv6 prefixes. configuration information, e.g., global IPv6 prefixes.
5.2.2. Router-Hardware-Fingerprint TLV 6.2.2. Router-Hardware-Fingerprint TLV
The Router-Hardware-Fingerprint TLV is the first TLV defined for the The Router-Hardware-Fingerprint TLV is the first TLV defined for the
OSPFv3 Auto-Configuration (AC) LSA. It will have type 1 and MUST be OSPFv3 Auto-Configuration (AC) LSA. It will have type 1 and MUST be
advertised in the LSID OSPFv3 AC LSA with an LSID of 0. It SHOULD advertised in the LSID OSPFv3 AC LSA with an LSID of 0. It SHOULD
occur, at most, once and the first instance of the TLV will take occur, at most, once and the first instance of the TLV will take
precedence over preceding TLV instances. The length of the Router- precedence over subsequent TLV instances. The length of the Router-
Hardware-Fingerprint is variable but must be 32 bytes or greater. Hardware-Fingerprint is variable but must be 32 bytes or greater.
The contents of the hardware fingerprint should be some combination The contents of the hardware fingerprint should be some combination
of MAC addresses, CPU ID, or serial number(s) that provides an of MAC addresses, CPU ID, or serial number(s) that provides an
extremely high probability of uniqueness. It MUST be based on extremely high probability of uniqueness. It MUST be based on
hardware attributes that will not change across hard and soft hardware attributes that will not change across hard and soft
restarts. restarts.
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
skipping to change at page 10, line 43 skipping to change at page 11, line 43
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Router Hardware Fingerprint | | Router Hardware Fingerprint |
o o
o o
o o
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Router-Hardware-Fingerprint TLV Format Router-Hardware-Fingerprint TLV Format
5.3. Duplicate Router-ID Resolution 6.3. Duplicate Router ID Resolution
The OSPFv3 Router selected to resolve the duplicate OSPFv3 Router-ID The OSPFv3 Router selected to resolve the duplicate OSPFv3 Router ID
condition must select a new OSPFv3 Router-ID. After selecting a new condition must select a new OSPFv3 Router ID. After selecting a new
Router-ID, the Router-LSA with the prior duplicate Router-ID MUST be Router ID, the Router-LSA with the prior duplicate Router ID MUST be
purged. all self-originated LSAs MUST be reoriginated, and any OSPFv3 purged. All self-originated LSAs MUST be reoriginated, and any
neighbor adjacencies MUST be reestablished. OSPFv3 neighbor adjacencies MUST be reestablished.
5.4. Change to Received Self-Originated LSA Processing 6.4. Change to Received Self-Originated LSA Processing
RFC 2328 [OSPFV2], Section 13.4, describes the processing of received RFC 2328 [OSPFV2], Section 13.4, describes the processing of received
self-originated LSAs. If the received LSA doesn't exist, the self-originated LSAs. If the received LSA doesn't exist, the
receiving router will purge it from the OSPF routing domain. If the receiving router will purge it from the OSPF routing domain. If the
LSA is newer than the version in the Link State Database (LSDB), the LSA is newer than the version in the Link State Database (LSDB), the
receiving router will originate a newer version by advancing the LSA receiving router will originate a newer version by advancing the LSA
sequence number and reflooding. Since it is possible for an auto- sequence number and reflooding. Since it is possible for an auto-
configured OSPFv3 router to choose a duplicate OSPFv3 Router-ID, configured OSPFv3 router to choose a duplicate OSPFv3 Router ID,
OSPFv3 routers implementing this specification should detect when OSPFv3 routers implementing this specification should detect when
multiple instances of the same self-originated LSA are purged or multiple instances of the same self-originated LSA are purged or
reoriginated since this is indicative of an OSPFv3 router with a reoriginated since this is indicative of an OSPFv3 router with a
duplicate Router-ID in the OSPFv3 routing domain. When this duplicate Router ID in the OSPFv3 routing domain. When this
condition is detected, the OSPFv3 Router SHOULD delay self-originated condition is detected, the OSPFv3 Router SHOULD delay self-originated
LSA processing for LSAs that have recently been purged or reflooded. LSA processing for LSAs that have recently been purged or reflooded.
This specification recommends 10 seconds as the interval defining This specification recommends 10 seconds as the interval defining
recent self-originated LSA processing and an exponential back off of recent self-originated LSA processing and an exponential back off of
1 to 8 seconds for the processing delay. 1 to 8 seconds for the processing delay.
6. Security Considerations 7. Security Considerations
A unique OSPFv3 Interface Instance ID is used for auto-configuration A unique OSPFv3 Interface Instance ID is used for auto-configuration
to prevent inadvertent OSPFv3 adjacency formation, see Section 2 to prevent inadvertent OSPFv3 adjacency formation, see Section 2
The goals of security and complete OSPFv3 auto-configuration are The goals of security and complete OSPFv3 auto-configuration are
somewhat contradictory. When no explicit security configuration somewhat contradictory. When no explicit security configuration
takes place, auto-configuration implies that additional devices takes place, auto-configuration implies that additional devices
placed in the network are automatically adopted as a part of the placed in the network are automatically adopted as a part of the
network. However, auto-configuration can also be combined with network. However, auto-configuration can also be combined with
password configuration (see below) or future extensions for automatic password configuration (see below) or future extensions for automatic
pairing between devices. These mechanisms can help provide an pairing between devices. These mechanisms can help provide an
automatically configured, securely routed network. automatically configured, securely routed network.
It is RECOMMENDED that OSPFv3 routers supporting this specification It is RECOMMENDED that OSPFv3 routers supporting this specification
also offer an option to explicitly configure a password for HMAC- SHA also offer an option to explicitly configure a password for HMAC-SHA
authentication as described in [OSPFV3-AUTH-TRAILER]. When authentication as described in [OSPFV3-AUTH-TRAILER]. When
configured, the password will be used on all auto-configured configured, the password will be used on all auto-configured
interfaces with the Security Association Identifier (SA ID) set to 1 interfaces with the Security Association Identifier (SA ID) set to 1
and HMAC-SHA-256 will be used as the authentication algorithm. and HMAC-SHA-256 used as the authentication algorithm.
7. Management Considerations 8. Management Considerations
It is RECOMMENDED that OSPFv3 routers supporting this specification It is RECOMMENDED that OSPFv3 routers supporting this specification
also allow explicit configuration of OSPFv3 parameters as specified also allow explicit configuration of OSPFv3 parameters as specified
in Appendix C of [OSPFV3]. This is in addition to the authentication in Appendix C of [OSPFV3]. This is in addition to the authentication
key configuration recommended in Section 6. However, it is key configuration recommended in Section 7. However, it is
acknowledged that there may be some deployment scenarios where manual acknowledged that there may be some deployment scenarios where manual
configuration is not required. authentication key configuration is not required.
8. IANA Considerations 9. IANA Considerations
This specification allocates a new OSPFv3 LSA, OSPFv3 Auto- This specification allocates a new OSPFv3 LSA, OSPFv3 Auto-
Configuration (AC) LSA, TBD, as described in Section 5.2.1. Configuration (AC) LSA, TBD, as described in Section 6.2.1.
This specification also creates a registry for OSPFv3 Auto- This specification also creates a registry for OSPFv3 Auto-
Configuration (AC) LSA TLVs. This registry should be placed in the Configuration (AC) LSA TLVs. This registry should be placed in the
existing OSPFv3 IANA registry, and new values can be allocated via existing OSPFv3 IANA registry, and new values can be allocated via
IETF Consensus or IESG Approval. IETF Consensus or IESG Approval.
Three initial values are allocated: Three initial values are allocated:
o 0 is marked as reserved. o 0 is marked as reserved.
o 1 is Router-Hardware-Fingerprint TLV (Section 5.2.2). o 1 is Router-Hardware-Fingerprint TLV (Section 6.2.2).
o 65535 is an Auto-configuration-Experiment-TLV, a common value that o 65535 is an Auto-configuration-Experiment-TLV, a common value that
can be used for experimental purposes. can be used for experimental purposes.
9. References 10. References
9.1. Normative References 10.1. Normative References
[OSPFV2] Moy, J., "OSPF Version 2", RFC 2328, April 1998. [OSPFV2] Moy, J., "OSPF Version 2", RFC 2328, April 1998.
[OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF [OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF
for IPv6", RFC 5340, July 2008. for IPv6", RFC 5340, July 2008.
[OSPFV3-AF] [OSPFV3-AF]
Lindem, A., Mirtorabi, S., Roy, A., Barnes, M., and R. Lindem, A., Mirtorabi, S., Roy, A., Barnes, M., and R.
Aggarwal, "Support of Address Families in OSPFv3", Aggarwal, "Support of Address Families in OSPFv3",
RFC 5838, April 2010. RFC 5838, April 2010.
skipping to change at page 15, line 34 skipping to change at page 16, line 34
[RFC-KEYWORDS] [RFC-KEYWORDS]
Bradner, S., "Key words for use in RFCs to Indicate Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, March 1997. Requirement Levels", RFC 2119, March 1997.
[SLAAC] Thomson, S., Narten, T., and J. Tatuya, "IPv6 Stateless [SLAAC] Thomson, S., Narten, T., and J. Tatuya, "IPv6 Stateless
Address Autoconfiguration", RFC 4862, September 2007. Address Autoconfiguration", RFC 4862, September 2007.
[TE] Katz, D., Yeung, D., and K. Kompella, "Traffic Engineering [TE] Katz, D., Yeung, D., and K. Kompella, "Traffic Engineering
Extensions to OSPF", RFC 3630, September 2003. Extensions to OSPF", RFC 3630, September 2003.
9.2. Informative References 10.2. Informative References
[ASYNC-HELLO]
Anand, M., Grover, H., and A. Roy, "Asymmetric OSPF Hold
Timer", draft-madhukar-ospf-agr-asymmetric-00.txt (work in
progress).
[BGP] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway [BGP] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
Protocol 4 (BGP-4)", RFC 4271, January 2006. Protocol 4 (BGP-4)", RFC 4271, January 2006.
Authors' Addresses Authors' Addresses
Acee Lindem Acee Lindem
Ericsson Ericsson
102 Carric Bend Court 102 Carric Bend Court
Cary, NC 27519 Cary, NC 27519
 End of changes. 52 change blocks. 
91 lines changed or deleted 120 lines changed or added

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