[VRRP] Help needed with a VRRP Errata Report

"Adrian Farrel" <adrian@olddog.co.uk> Tue, 18 November 2014 18:24 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: vrrp@ietfa.amsl.com
Delivered-To: vrrp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 1CC591A0469 for <vrrp@ietfa.amsl.com>; Tue, 18 Nov 2014 10:24:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 7KOnBfSrK45w for <vrrp@ietfa.amsl.com>; Tue, 18 Nov 2014 10:23:57 -0800 (PST)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 067211A0372 for <vrrp@ietf.org>; Tue, 18 Nov 2014 10:23:56 -0800 (PST)
Received: from asmtp3.iomartmail.com (localhost.localdomain []) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id sAIINsCG010122 for <vrrp@ietf.org>; Tue, 18 Nov 2014 18:23:54 GMT
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com []) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id sAIINrS9010113 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <vrrp@ietf.org>; Tue, 18 Nov 2014 18:23:54 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <vrrp@ietf.org>
Date: Tue, 18 Nov 2014 18:23:53 -0000
Message-ID: <00d401d0035c$cf2e58a0$6d8b09e0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdADXMchlxSbPshPRCiy7Nz7fAyntw==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-
X-TM-AS-Result: No--0.448-10.0-31-10
X-imss-scan-details: No--0.448-10.0-31-10
X-TMASE-MatchedRID: wwUy3qUR3Ti6ju+uRM2btWgws6g0ewz2bb9qvlMXO4KoszQaueYJUA3b 6kSjpN75KnGf9dXxEj1KlDRco4AkldpVJxuKWNxsiFoorQjboWmeimGtNywjtpsoi2XrUn/JyeM tMD9QOgCrrVqVQLpWR+TCMddcL/gjxlblqLlYqXLuqsPuuvFG70MX0GQLl/6VQ+zSDBacBs+YIx IjXGIylap01jxM5m4hYc2zCM7gA4bt3H3IZbMl9YTq7NpivvVb2/1SSBvYKhQ2Fo4EfHNqXY5MJ KdFN6D6I9UhQYuUjidG3TVmsFmvfmY7eqLvyw0k
Archived-At: http://mailarchive.ietf.org/arch/msg/vrrp/wjt_eMD5NsoWptXbXTjpEC6-5bI
Subject: [VRRP] Help needed with a VRRP Errata Report
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Virtual Router Redundancy Protocol <vrrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vrrp>, <mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vrrp/>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vrrp>, <mailto:vrrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2014 18:24:00 -0000

Hi VRRP enthusiasts,

A report has been submitted against RFC6527, "Definitions of Managed Objects for
Virtual Router Redundancy Protocol Version 3 (VRRPv3)". You can see it at

The essence is that the Description clause of the vrrpv3OperationsAcceptMode
object appears to limit its meaning to IPv6 addresses. However, section 6.1 of
RFC 5798 describes Accept_Mode as applying to IPvX which implies IPv4 or IPv6.

Instruction 635 does appear to be limited to IPv6, but instruction 650 is
clearly relevant to both IPv4 and IPv6.

I think the report is correct.