Re: [VRRP] vrrpv3 with global IPv6
Seiichi Kawamura <kawamucho@mesh.ad.jp> Fri, 30 July 2010 22:28 UTC
Return-Path: <kawamucho@mesh.ad.jp>
X-Original-To: vrrp@core3.amsl.com
Delivered-To: vrrp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4CA4E3A69A5 for <vrrp@core3.amsl.com>; Fri, 30 Jul 2010 15:28:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.187
X-Spam-Level:
X-Spam-Status: No, score=0.187 tagged_above=-999 required=5 tests=[AWL=0.277, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7JJP1wMi-WG6 for <vrrp@core3.amsl.com>; Fri, 30 Jul 2010 15:28:14 -0700 (PDT)
Received: from tyo201.gate.nec.co.jp (TYO201.gate.nec.co.jp [202.32.8.193]) by core3.amsl.com (Postfix) with ESMTP id 0ABD63A6986 for <vrrp@ietf.org>; Fri, 30 Jul 2010 15:28:13 -0700 (PDT)
Received: from mailgate3.nec.co.jp ([10.7.69.195]) by tyo201.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id o6UMSaq5019363; Sat, 31 Jul 2010 07:28:36 +0900 (JST)
Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id o6UMSao04464; Sat, 31 Jul 2010 07:28:36 +0900 (JST)
Received: from bgas200085.sys.biglobe.nec.co.jp (bgas200085.sys.biglobe.nec.co.jp [10.82.141.45]) by mailsv.nec.co.jp (8.13.8/8.13.4) with ESMTP id o6UMSaQD007790; Sat, 31 Jul 2010 07:28:36 +0900 (JST)
Received: from mail.sys.biglobe.nec.co.jp (localhost [127.0.0.1]) by bgas200085.sys.biglobe.nec.co.jp (BINGO/BINGO/06101717) with ESMTP id o6UMSZiK028939; Sat, 31 Jul 2010 07:28:35 +0900
Received: from mail.sys.biglobe.nec.co.jp (bgsx5626.sys.biglobe.nec.co.jp [10.18.151.10]) (envelope-from kawamucho@mesh.ad.jp) by mail.sys.biglobe.nec.co.jp (BINGO/BINGO/10031711) with ESMTP id o6UMSZpK021817 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 31 Jul 2010 07:28:35 +0900
Received: from [127.0.0.1] (edonet065.sys.biglobe.nec.co.jp [10.19.137.65]) (authenticated bits=0) (envelope-from kawamucho@mesh.ad.jp) by mail.sys.biglobe.nec.co.jp (BINGO/BINGO/10031711) with ESMTP id o6UMSZng011180 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 31 Jul 2010 07:28:35 +0900
Message-ID: <4C535212.6040303@mesh.ad.jp>
Date: Sat, 31 Jul 2010 07:28:34 +0900
From: Seiichi Kawamura <kawamucho@mesh.ad.jp>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: "John Cruz (johcruz)" <johcruz@cisco.com>
References: <4C52C8B5.8080601@mesh.ad.jp> <9D0602B62D632D499E0A26CBCDA74A7D0841D4D6@xmb-sjc-22a.amer.cisco.com>
In-Reply-To: <9D0602B62D632D499E0A26CBCDA74A7D0841D4D6@xmb-sjc-22a.amer.cisco.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: randy@psg.com, narten@us.ibm.com, brian@innovationslab.net, vrrp@ietf.org
Subject: Re: [VRRP] vrrpv3 with global IPv6
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Router Redundancy Protocol <vrrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 30 Jul 2010 22:28:15 -0000
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi John John Cruz (johcruz) wrote: > Hi, > > To the best of my knowledge, the one of the earlier drafts > mentioned link-local addresses only. This might be the reason > why certain implementations support link-local addresses > only. Thanks for this. That would be reason enough to explain for some of the implementations that have been around for a while. I've heard of recent implementations that do not support global though... > > The current standards supports virtual addresses that have > global scope. Can you point to a specific phrase in the RFC where it says so? I could not find any mention of the word global in the RFC nor any RFC2119 words relating to scopes of addresses. Regards, Seiichi > > Regards > John > >> -----Original Message----- >> From: vrrp-bounces@ietf.org [mailto:vrrp-bounces@ietf.org] On Behalf > Of >> Seiichi Kawamura >> Sent: Friday, July 30, 2010 5:42 AM >> To: vrrp@ietf.org >> Cc: randy@psg.com; narten@us.ibm.com; brian@innovationslab.net >> Subject: [VRRP] vrrpv3 with global IPv6 >> > I've been discussing this with a few people this week > and thought that it was worth asking this list. > > rfc5798 says in section 5.2.9 > > For IPv6, the first address must be the IPv6 link-local address > associated with the virtual router. > > It implies that a global address can be associated > with the virtual router, but some routers > implement link-local capability only becuase only the > link-local address is mentioned here. > > The problem is, operators need global scope addresses with > virtual routers and we have to ask each vendor to > implement it if they have not already done so. The main > reason we need this is becausewe need to monitor the address > from a remote network as we do with IPv4. > > I just joined this list, but can someone > tell me what was the thinking was behind not > mentioning global addresses in this RFC? > > Thank you > > Regards, > Seiichi > _______________________________________________ vrrp mailing list vrrp@ietf.org https://www.ietf.org/mailman/listinfo/vrrp -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAkxTUhEACgkQcrhTYfxyMkKL1wCgjlVy8g4RhiMF1Upq++3zs3Vi nCkAn34uQUGI4XJtaFXuh+i0C+k2gsJR =OL8C -----END PGP SIGNATURE-----
- [VRRP] vrrpv3 with global IPv6 Seiichi Kawamura
- Re: [VRRP] vrrpv3 with global IPv6 John Cruz (johcruz)
- Re: [VRRP] vrrpv3 with global IPv6 Seiichi Kawamura
- Re: [VRRP] vrrpv3 with global IPv6 John Cruz (johcruz)
- Re: [VRRP] vrrpv3 with global IPv6 Seiichi Kawamura