[VRRP] RFC5798 requires usage of RAs?
Daniel Roesen <dr@cluenet.de> Fri, 15 April 2011 08:57 UTC
Return-Path: <dr@cluenet.de>
X-Original-To: vrrp@ietfc.amsl.com
Delivered-To: vrrp@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 55708E0694 for <vrrp@ietfc.amsl.com>; Fri, 15 Apr 2011 01:57:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.191
X-Spam-Level:
X-Spam-Status: No, score=-0.191 tagged_above=-999 required=5 tests=[AWL=2.409, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Za3zJV1j6plu for <vrrp@ietfc.amsl.com>; Fri, 15 Apr 2011 01:57:09 -0700 (PDT)
Received: from mail1.cluenet.de (mail1.cluenet.de [IPv6:2001:1440:201:101::5]) by ietfc.amsl.com (Postfix) with ESMTP id AE08CE065A for <vrrp@ietf.org>; Fri, 15 Apr 2011 01:57:09 -0700 (PDT)
Received: by mail1.cluenet.de (Postfix, from userid 500) id 422B8108094; Fri, 15 Apr 2011 10:57:09 +0200 (CEST)
Date: Fri, 15 Apr 2011 10:57:09 +0200
From: Daniel Roesen <dr@cluenet.de>
To: vrrp@ietf.org
Message-ID: <20110415085709.GA3742@srv03.cluenet.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.17 (2007-11-01)
Subject: [VRRP] RFC5798 requires usage of RAs?
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Fri, 15 Apr 2011 08:57:10 -0000
Hi, JUNOS (Juniper router firmware) issues warnings when committing config changes, noting that RAs are not configured for an interface where VRRP for IPv6 is configured: vrrpd[15299]: %CONFLICT-0-WARNING: 'router-advertisement' is not configured for interface ge-9/2/2.662 RFC5798 states: 6.4.3. Master ... (630) ++ MUST send ND Router Advertisements for the virtual router. That makes no sense to us when RAs are generally not used on the segment, and hosts are manually configured to point to the VRRP virtual address as default gateway. We do not want to use RAs in some scenarios at all. I've found an older posting on this list, where someone raised the same question (Q-2): http://www.ietf.org/mail-archive/web/vrrp/current/msg00763.html John Cruz' answer seems to clarify, but noone seemed to have envisioned that the spec lingo actually motivates vendors to assume RAs as being mandatory when implementing VRRPv6... :-/ RFC5798 states in the introductory section about IPv6 (1.3): IPv6 hosts on a LAN will usually learn about one or more default routers by receiving Router Advertisements sent using the IPv6 Neighbor Discovery (ND) protocol [RFC4861]. Given that it says "usually", it recognizes that there are scenarios where RAs are NOT being used. Unfortunately several bits of language in the RFC doesn't reflect that, so I would like to suggest changing specifically rule 630 and section 8.2.3 to reflect no-RA scenarios. Best regards, Daniel
- [VRRP] RFC5798 requires usage of RAs? Daniel Roesen
- Re: [VRRP] RFC5798 requires usage of RAs? Stephen Nadas
- Re: [VRRP] RFC5798 requires usage of RAs? Daniel Roesen
- Re: [VRRP] RFC5798 requires usage of RAs? Stephen Nadas