< draft-ietf-ospf-ospfv3-autoconfig-07.txt   draft-ietf-ospf-ospfv3-autoconfig-08.txt >
Network Working Group A. Lindem Network Working Group A. Lindem
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Standards Track J. Arkko Intended status: Standards Track J. Arkko
Expires: February 11, 2015 Ericsson Expires: February 28, 2015 Ericsson
August 10, 2014 August 27, 2014
OSPFv3 Auto-Configuration OSPFv3 Auto-Configuration
draft-ietf-ospf-ospfv3-autoconfig-07.txt draft-ietf-ospf-ospfv3-autoconfig-08.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 35 skipping to change at page 1, line 35
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 February 11, 2015. This Internet-Draft will expire on February 28, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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
skipping to change at page 2, line 26 skipping to change at page 2, line 26
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 . . . . . . . . . . . . . . . . . 5 2. OSPFv3 Default Configuration . . . . . . . . . . . . . . . . . 5
3. OSPFv3 HelloInterval/RouterDeadInterval Flexibility . . . . . 7 3. OSPFv3 HelloInterval/RouterDeadInterval Flexibility . . . . . 7
3.1. Wait Timer Reduction . . . . . . . . . . . . . . . . . . . 7 3.1. Wait Timer Reduction . . . . . . . . . . . . . . . . . . . 7
4. OSPFv3 Router ID Selection . . . . . . . . . . . . . . . . . . 8 4. OSPFv3 Minimal Authentication Configuration . . . . . . . . . 8
5. OSPFv3 Adjacency Formation . . . . . . . . . . . . . . . . . . 9 5. OSPFv3 Router ID Selection . . . . . . . . . . . . . . . . . . 9
6. OSPFv3 Duplicate Router ID Detection and Resolution . . . . . 10 6. OSPFv3 Adjacency Formation . . . . . . . . . . . . . . . . . . 10
6.1. Duplicate Router ID Detection for Neighbors . . . . . . . 10 7. OSPFv3 Duplicate Router ID Detection and Resolution . . . . . 11
6.2. Duplicate Router ID Detection for OSPFv3 Routers that 7.1. Duplicate Router ID Detection for Neighbors . . . . . . . 11
are not Neighbors . . . . . . . . . . . . . . . . . . . . 10 7.2. Duplicate Router ID Detection for OSPFv3 Routers that
6.2.1. OSPFv3 Router Auto-Configuration LSA . . . . . . . . . 10 are not Neighbors . . . . . . . . . . . . . . . . . . . . 11
6.2.2. Router-Hardware-Fingerprint TLV . . . . . . . . . . . 12 7.2.1. OSPFv3 Router Auto-Configuration LSA . . . . . . . . . 11
6.3. Duplicate Router ID Resolution . . . . . . . . . . . . . . 13 7.2.2. Router-Hardware-Fingerprint TLV . . . . . . . . . . . 13
6.4. Change to RFC 2328 Section 13.4, 'Receiving 7.3. Duplicate Router ID Resolution . . . . . . . . . . . . . . 14
Self-Originated LSA' Processing . . . . . . . . . . . . . 13 7.4. Change to RFC 2328 Section 13.4, 'Receiving
7. Security Considerations . . . . . . . . . . . . . . . . . . . 14 Self-Originated LSA' Processing . . . . . . . . . . . . . 14
8. Management Considerations . . . . . . . . . . . . . . . . . . 15 8. Security Considerations . . . . . . . . . . . . . . . . . . . 15
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 9. Management Considerations . . . . . . . . . . . . . . . . . . 16
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
10.1. Normative References . . . . . . . . . . . . . . . . . . . 17 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
10.2. Informative References . . . . . . . . . . . . . . . . . . 17 11.1. Normative References . . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18 11.2. Informative References . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19
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
skipping to change at page 4, line 11 skipping to change at page 4, line 11
Thanks to Mark Smith for the requirement to reduce the adjacency Thanks to Mark Smith for the requirement to reduce the adjacency
formation delay in the back-to-back ethernet topologies that are formation delay in the back-to-back ethernet topologies that are
prevalent in home networks. prevalent in home networks.
Thanks to Les Ginsberg for document review and recommendations on Thanks to Les Ginsberg for document review and recommendations on
OSPFv3 hardware fingerprint content. OSPFv3 hardware fingerprint content.
Thanks to Curtis Villamizar for document review and analysis of Thanks to Curtis Villamizar for document review and analysis of
duplicate router-id resolution nuances. duplicate router-id resolution nuances.
The RFC text was produced using Marshall Rose's xml2rfc tool. Thanks to Uma Chunduri for comments during OSPF WG last call.
Special thanks go to Markus Stenberg for his implementation of this Special thanks go to Markus Stenberg for his implementation of this
specification. specification in Bird.
Special thanks also go to David Lamparter for his implementation of
this specification in Quagga.
The RFC text was produced using Marshall Rose's xml2rfc tool.
2. OSPFv3 Default Configuration 2. OSPFv3 Default Configuration
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
skipping to change at page 8, line 5 skipping to change at page 8, line 5
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).
Reducing the setting will slightly increase the likelihood of the Reducing the setting will slightly increase the likelihood of the
Designated Router (DR) flapping but is preferable to the long Designated Router (DR) flapping but is preferable to the long
adjacency formation delay. Note that this value is not included in adjacency formation delay. Note that this value is not included in
OSPFv3 Hello packets and does not impact interoperability. OSPFv3 Hello packets and does not impact interoperability.
4. OSPFv3 Router ID Selection 4. OSPFv3 Minimal Authentication Configuration
In many deployments, the requirement for OSPFv3 authentication
overrides the goal of complete OSPFv3 autoconfiguration. Therefore,
it is RECOMMENDED that OSPFv3 routers supporting this specification
minimally offer an option to explicitly configure a single password
for HMAC-SHA authentication as described in [OSPFV3-AUTH-TRAILER].
When configured, the password will be used on all auto-configured
interfaces with the Security Association Identifier (SA ID) set to 1
and HMAC-SHA-256 used as the authentication algorithm.
5. 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 the applicable OSPFv3 router deployment. A likely to be unique in the applicable OSPFv3 router deployment. A
good choice of seed would be some portion or hash of the Router- good choice of seed would be some portion or hash of the Router-
Hardware-Fingerprint as described in Section 6.2.2. Hardware-Fingerprint as described in Section 7.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 6 and Section 6.3. OSPFv3 Routers SHOULD maintain the last Section 7 and Section 7.3. OSPFv3 Routers SHOULD maintain the last
successfully chosen Router ID in non-volatile storage to avoid successfully chosen Router ID in non-volatile storage to avoid
collisions subsequent to when an autoconfigured OSPFv3 router is collisions subsequent to when an autoconfigured OSPFv3 router is
first added to the OSPFv3 routing domain. first added to the OSPFv3 routing domain.
5. OSPFv3 Adjacency Formation 6. 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 messages sent on virtual links (which are not applicable other than messages sent on virtual links (which are not applicable
to auto-configuration), OSPFv3 adjacency formation can proceed as to auto-configuration), OSPFv3 adjacency formation can proceed as
soon as a Router ID has been selected and the IPv6 link-local address soon as a Router ID has been selected and the IPv6 link-local address
has completed Duplicate Address Detection (DAD) as specified in IPv6 has completed Duplicate Address Detection (DAD) as specified in IPv6
Stateless Address Autoconfiguration [SLAAC]. Otherwise, the only Stateless Address Autoconfiguration [SLAAC]. Otherwise, the only
changes to the OSPFv3 base specification are supporting changes to the OSPFv3 base specification are supporting
HelloInterval/RouterDeadInterval flexibility as described in HelloInterval/RouterDeadInterval flexibility as described in
Section 3 and duplicate Router ID detection and resolution as Section 3 and duplicate Router ID detection and resolution as
described in Section 6 and Section 6.3. described in Section 7 and Section 7.3.
6. OSPFv3 Duplicate Router ID Detection and Resolution 7. 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 duplicate connected and one where it is not. In both cases, the duplicate
resolution is for one of the routers to select a new OSPFv3 Router resolution is for one of the routers to select a new OSPFv3 Router
ID. ID.
6.1. Duplicate Router ID Detection for Neighbors 7.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 this occurs, the OSPFv3 router IPv6 link-local source address. Once this 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 6.3. Note that the select a new Router ID as described in Section 7.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 is connection of multiple router interfaces to the same physical link is
not misconstrued as detection of an OSPFv3 neighbor with a duplicate not misconstrued as detection of an OSPFv3 neighbor with a duplicate
Router ID. Router ID.
6.2. Duplicate Router ID Detection for OSPFv3 Routers that are not 7.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-Configuration (AC) Link State Advertisement MUST originate an Auto-Configuration (AC) Link State Advertisement
(LSA) including the Router-Hardware-Fingerprint Type-Length-Value (LSA) including the Router-Hardware-Fingerprint Type-Length-Value
(TLV). The Router-Hardware-Fingerprint TLV contains a variable (TLV). The Router-Hardware-Fingerprint TLV contains a variable
length value that has a very high probability of uniquely identifying length value that has a very high probability of uniquely identifying
the advertising OSPFv3 router. An OSPFv3 router implementing this the advertising OSPFv3 router. An OSPFv3 router implementing this
specification MUST compare a received self-originated Auto- specification MUST compare a received self-originated Auto-
Configuration LSA's Router-Hardware-Fingerprint TLV against its own Configuration LSA's Router-Hardware-Fingerprint TLV against its own
router hardware fingerprint. If the fingerprints are not equal, router hardware fingerprint. If the fingerprints are not equal,
there is a duplicate Router ID conflict and the OSPFv3 Router with there is a duplicate Router ID conflict and the OSPFv3 Router with
the numerically smaller router hardware fingerprint MUST select a new the numerically smaller router hardware fingerprint MUST select a new
Router ID as described in Section 6.3. Router ID as described in Section 7.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.
6.2.1. OSPFv3 Router Auto-Configuration LSA 7.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 OSPFv3 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
skipping to change at page 12, line 14 skipping to change at page 13, 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. configuration information.
6.2.2. Router-Hardware-Fingerprint TLV 7.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 subsequent 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 octets or greater. Hardware-Fingerprint is variable but must be 32 octets or greater.
The contents of the hardware fingerprint MUST be some combination of The contents of the hardware fingerprint MUST be some combination of
MAC addresses, CPU ID, or serial number(s) that provides an extremely MAC addresses, CPU ID, or serial number(s) that provides an extremely
skipping to change at page 13, line 5 skipping to change at page 14, line 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Router Hardware Fingerprint | | Router Hardware Fingerprint |
o o
o o
o o
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Router-Hardware-Fingerprint TLV Format Router-Hardware-Fingerprint TLV Format
6.3. Duplicate Router ID Resolution 7.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, all self-originated LSAs MUST be reoriginated, and any Router ID, all self-originated LSAs MUST be reoriginated, and any
OSPFv3 neighbor adjacencies MUST be reestablished. The OSPFv3 router OSPFv3 neighbor adjacencies MUST be reestablished. The OSPFv3 router
retaining the Router ID causing the conflict will reoriginate or retaining the Router ID causing the conflict will reoriginate or
purge stale any LSAs as described in Section 13.4 [OSPFV2]. purge stale any LSAs as described in Section 13.4 [OSPFV2].
6.4. Change to RFC 2328 Section 13.4, 'Receiving Self-Originated LSA' 7.4. Change to RFC 2328 Section 13.4, 'Receiving Self-Originated LSA'
Processing 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. This additional delay 1 to 8 seconds for the processing delay. This additional delay
should allow for the mechanisms described in Section 6 to resolve the should allow for the mechanisms described in Section 7 to resolve the
duplicate OSPFv3 Router ID conflict. duplicate OSPFv3 Router ID conflict.
7. Security Considerations 8. 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 Section 4) or future extensions for
pairing between devices. These mechanisms can help provide an automatic pairing between devices. These mechanisms can help provide
automatically configured, securely routed network. an automatically configured, securely routed network.
It is RECOMMENDED that OSPFv3 routers supporting this specification
also offer an option to explicitly configure a password for HMAC-SHA
authentication as described in [OSPFV3-AUTH-TRAILER]. When
configured, the password will be used on all auto-configured
interfaces with the Security Association Identifier (SA ID) set to 1
and HMAC-SHA-256 used as the authentication algorithm.
8. Management Considerations 9. 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 7. However, it is key configuration recommended in Section 4. However, it is
acknowledged that there may be some deployment scenarios where manual acknowledged that there may be some deployment scenarios where manual
authentication key configuration is not required. authentication key configuration is not required.
Since there is a small possibility of OSPFv3 Router ID collisions, Since there is a small possibility of OSPFv3 Router ID collisions,
manual configuration of OSPFv3 Router-IDs is RECOMMENDED in OSPFv3 manual configuration of OSPFv3 Router-IDs is RECOMMENDED in OSPFv3
routing domains where route recovergence due to a router ID change is routing domains where route recovergence due to a router ID change is
intolerable. intolerable.
9. IANA Considerations 10. IANA Considerations
This specification defines an OSPFv3 LSA Type for the OSPFv3 Auto- This specification defines an OSPFv3 LSA Type for the OSPFv3 Auto-
Configuration (AC) LSA, as described in Section 6.2.1. The value TBD Configuration (AC) LSA, as described in Section 7.2.1. The value TBD
will be allocated from the existing "OSPFv3 LSA Function Code" will be allocated from the existing "OSPFv3 LSA Function Code"
registry for the OSPFv3 Auto-Configuration LSA. registry for the OSPFv3 Auto-Configuration LSA.
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 6.2.2). o 1 is Router-Hardware-Fingerprint TLV (Section 7.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.
10. References 11. References
10.1. Normative References 11.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.
[OSPFV3-AUTH-TRAILER] [OSPFV3-AUTH-TRAILER]
Bhatia, M., Manral, V., and A. Lindem, "Supporting Bhatia, M., Manral, V., and A. Lindem, "Supporting
Authentication Trailer for OSPFv3", RFC 6506, Authentication Trailer for OSPFv3", RFC 7166,
February 2012. February 2012.
[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.
10.2. Informative References 11.2. Informative References
[ASYNC-HELLO] [ASYNC-HELLO]
Anand, M., Grover, H., and A. Roy, "Asymmetric OSPF Hold Anand, M., Grover, H., and A. Roy, "Asymmetric OSPF Hold
Timer", draft-madhukar-ospf-agr-asymmetric-01.txt (work in Timer", draft-madhukar-ospf-agr-asymmetric-01.txt (work in
progress). 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.
[EUI64] IEEE, "Guidelines for 64-bit Global Identifier (EUI-64) [EUI64] IEEE, "Guidelines for 64-bit Global Identifier (EUI-64)
 End of changes. 32 change blocks. 
59 lines changed or deleted 69 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/