| Internet-Draft | Stub Router RA Flag | February 2024 |
| Hui | Expires 30 August 2024 | [Page] |
This document defines a new Stub Router flag in the Router Advertisement message that can be used to distinguish configuration information sent by stub routers from information sent by infrastructure routers.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 30 August 2024.¶
Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
A stub router provides IP connectivity between a stub network and an infrastructure network. A common stub router example is a device that attaches a 6LoWPAN-based network to a home network.¶
To support IPv6 reachability between infrastructure network devices and stub network devices, routable IPv6 addresses must be configured on both the infrastructure and stub networks. Stub routers decide whether or not to advertise their ULA prefixes [RFC4193] on the infrastructure network to which they are connected by tracking the presence of infrastructure-provided IPv6 service. When a stub router sees a new prefix advertised on infrastructure, this prefix may be coming from an infrastructure router, or from another stub router. In the second case, the two stub routers could wind up in a cycle of publishing and deprecating their prefixes as they see prefixes from the other stub router show up.¶
The stub router document [I-D.ietf-snac-simple] explains how two stub routers decide which one has precedence in the event of a conflict. However, the infrastructure prefix always has precedence over a prefix provided by any stub router. In order to differentiate between prefixes advertised by infrastructure and those advertised by stub routers, it is necessary to be able to mark RAs sent by stub routers.¶
Additionally, the RA header includes M and O flags that indicate whether DHCPv6 is available on the link. Section 6.3.4 of [RFC4861] specifies that hosts consider the most recently received information as authoritative. As a result, stub routers must mirror the M and O values in RAs received from infrastructure routers. The Stub Router flag allows stub routers to easily identify which RAs are sent by infrastructure routers.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
This document defines a new "Stub Router" flag as flag bit 6 in the Router Advertisement flags field.¶
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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Code | Checksum | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Cur Hop Limit |M|O|H|Prf|P|S|R| Router Lifetime | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Reachable Time | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Retrans Timer | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Options ... +-+-+-+-+-+-+-+-+-+-+-+-¶
The S flag is the "Stub Router" flag.¶
The M, O, H, Prf, P, and R flags are as defined in [RFC5175].¶
A stub router that is not explicitly configured as part of the infrastructure network MUST set the Stub Router flag in outgoing RA messages.¶
How and when a stub router sets the M and O flags in outgoing RAs is specified in [I-D.ietf-snac-simple].¶
IANA is requested to allocate a flag from the "IPv6 ND Router Advertisement flags" registry of [RFC5175], as specified below:¶
| RA Option Bit | Description | Reference |
| 6 | S - Stub Router Flag | This Document |
This protocol shares the security issues of NDP that are documented in the "Security Considerations" section of [RFC4861].¶