RFC Errata
RFC 6527, "Definitions of Managed Objects for Virtual Router Redundancy Protocol Version 3 (VRRPv3)", March 2012
Source of RFC: IETF - NON WORKING GROUPSee Also: RFC 6527 w/ inline errata
Errata ID: 4168
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: vrrpv3OperationsAcceptMode description seems not proper
Date Reported: 2014-11-06
Verifier Name: Adrian Farrel
Date Verified: 2014-12-09
Section 10 says:
vrrpv3OperationsAcceptMode OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Controls whether a virtual router in master state will accept packets addressed to the address owner's IPv6 address as its own if it is not the IPv6 address owner. Default is false(2). This object is not relevant for rows representing VRRP over IPv4 and should be set to false(2)." DEFVAL { false } ::= { vrrpv3OperationsEntry 11 }
It should say:
vrrpv3OperationsAcceptMode OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Controls whether a virtual router in master state will accept packets addressed to the address owner's address as its own if it is not the address owner. Default is false(2). DEFVAL { false } ::= { vrrpv3OperationsEntry 11 }
Notes:
The correction is to remove the specialization on IPv4 and IPv6.
The original description says not allow to set to True for IPv4. But in practice IPv4 has use case for acceptMode-as-true too.
Here is the related state-machine description on accept mode in VRRP RFC. Step 650 doesn't not distinguish IPv4 and IPv6.
(650) - MUST accept packets addressed to the IPvX address(es)
associated with the virtual router if it is the IPvX address owner
or if Accept_Mode is True. Otherwise, MUST NOT accept these
packets.