From exim@www1.ietf.org  Thu Nov  6 19:47:27 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10541
	for <vrrp-archive@odin.ietf.org>; Thu, 6 Nov 2003 19:47:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHumK-0001bT-CJ
	for vrrp-archive@odin.ietf.org; Thu, 06 Nov 2003 19:47:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA70l8N3006159
	for vrrp-archive@odin.ietf.org; Thu, 6 Nov 2003 19:47:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHumK-0001bG-7e
	for vrrp-web-archive@optimus.ietf.org; Thu, 06 Nov 2003 19:47:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10527
	for <vrrp-web-archive@ietf.org>; Thu, 6 Nov 2003 19:46:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHumI-0003fn-00
	for vrrp-web-archive@ietf.org; Thu, 06 Nov 2003 19:47:06 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHumH-0003fj-00
	for vrrp-web-archive@ietf.org; Thu, 06 Nov 2003 19:47:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHumC-0001aQ-RF; Thu, 06 Nov 2003 19:47:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHulx-0001Zs-Kj
	for vrrp@optimus.ietf.org; Thu, 06 Nov 2003 19:46:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10509
	for <vrrp@ietf.org>; Thu, 6 Nov 2003 19:46:34 -0500 (EST)
From: Mukesh.Gupta@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHulv-0003fG-00
	for vrrp@ietf.org; Thu, 06 Nov 2003 19:46:43 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHulv-0003fD-00
	for vrrp@ietf.org; Thu, 06 Nov 2003 19:46:43 -0500
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hA70kgY18752
	for <vrrp@ietf.org>; Fri, 7 Nov 2003 02:46:42 +0200 (EET)
Received: from daebh002.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65c07e506bac158f21082@esvir01nok.ntc.nokia.com> for <vrrp@ietf.org>;
 Fri, 7 Nov 2003 02:46:40 +0200
Received: from daebe009.NOE.Nokia.com ([172.18.242.190]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Thu, 6 Nov 2003 18:46:39 -0600
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MIMEOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Thu, 6 Nov 2003 18:46:39 -0600
Message-ID: <8D260779A766FB4A9C1739A476F84FA401546ED5@daebe009.americas.nokia.com>
Thread-Topic: Scribes for the meeting..
thread-index: AcOkyJo6KzNZ2NPfSBmvDvhe8GlRLA==
To: <vrrp@ietf.org>
X-OriginalArrivalTime: 07 Nov 2003 00:46:39.0573 (UTC) FILETIME=[9AE6B050:01C3A4C8]
Content-Transfer-Encoding: quoted-printable
Subject: [VRRP] Scribes for the meeting..
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi,

The chairs are looking for volunteer scribes for the
meeting minutes and for jabber.

Please send a mail if you would like to be "The One" :)

Regards
Mukesh

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Tue Nov 11 12:34:25 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12179
	for <vrrp-archive@odin.ietf.org>; Tue, 11 Nov 2003 12:34:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJcP2-0004VN-1N
	for vrrp-archive@odin.ietf.org; Tue, 11 Nov 2003 12:34:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hABHY8pP017316
	for vrrp-archive@odin.ietf.org; Tue, 11 Nov 2003 12:34:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJcP1-0004VD-SO
	for vrrp-web-archive@optimus.ietf.org; Tue, 11 Nov 2003 12:34:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12153
	for <vrrp-web-archive@ietf.org>; Tue, 11 Nov 2003 12:33:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJcP0-0006mH-00
	for vrrp-web-archive@ietf.org; Tue, 11 Nov 2003 12:34:06 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJcOz-0006mD-00
	for vrrp-web-archive@ietf.org; Tue, 11 Nov 2003 12:34:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJcOw-0004Tm-B5; Tue, 11 Nov 2003 12:34:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJcOs-0004TF-JJ
	for vrrp@optimus.ietf.org; Tue, 11 Nov 2003 12:33:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12132;
	Tue, 11 Nov 2003 12:33:45 -0500 (EST)
From: Mukesh.Gupta@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJcOq-0006lg-00; Tue, 11 Nov 2003 12:33:56 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJcOp-0006lZ-00; Tue, 11 Nov 2003 12:33:56 -0500
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hABHXsB20576;
	Tue, 11 Nov 2003 19:33:54 +0200 (EET)
Received: from daebh001.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65d8b1ddedac158f21082@esvir01nok.ntc.nokia.com>;
 Tue, 11 Nov 2003 19:33:52 +0200
Received: from daebe009.NOE.Nokia.com ([10.241.35.109]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Tue, 11 Nov 2003 09:33:50 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 11 Nov 2003 11:33:49 -0600
Message-ID: <8D260779A766FB4A9C1739A476F84FA401546EF7@daebe009.NOE.Nokia.com>
Thread-Topic: CARP..
Thread-Index: AcOoefdIrODI4C3SQ6Oj+WZEaZXWig==
To: <routing-discussion@ietf.org>, <vrrp@ietf.org>
X-OriginalArrivalTime: 11 Nov 2003 17:33:50.0495 (UTC) FILETIME=[F8309AF0:01C3A879]
Content-Transfer-Encoding: quoted-printable
Subject: [VRRP] CARP..
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Folks,

Do we have anyone in the WG or routing-discussion list who=20
knows about CARP (Common Address Redundancy Protocol) and=20
can explain it to the WG (or just the chairs in person) in=20
the WG meeting on Thursday.

Please send me a mail asap. Your help will be highly
appreciated.

Regards
Mukesh

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Tue Nov 11 13:35:31 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14663
	for <vrrp-archive@odin.ietf.org>; Tue, 11 Nov 2003 13:35:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJdM7-00012p-Bd
	for vrrp-archive@odin.ietf.org; Tue, 11 Nov 2003 13:35:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hABIZB8j004009
	for vrrp-archive@odin.ietf.org; Tue, 11 Nov 2003 13:35:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJdM7-00012a-3T
	for vrrp-web-archive@optimus.ietf.org; Tue, 11 Nov 2003 13:35:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14652
	for <vrrp-web-archive@ietf.org>; Tue, 11 Nov 2003 13:34:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJdM4-0007dp-00
	for vrrp-web-archive@ietf.org; Tue, 11 Nov 2003 13:35:08 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJdM4-0007dm-00
	for vrrp-web-archive@ietf.org; Tue, 11 Nov 2003 13:35:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJdLx-0000zS-0R; Tue, 11 Nov 2003 13:35:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJdLN-0000yv-3h
	for vrrp@optimus.ietf.org; Tue, 11 Nov 2003 13:34:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14587;
	Tue, 11 Nov 2003 13:34:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJdLK-0007d4-00; Tue, 11 Nov 2003 13:34:22 -0500
Received: from mail.ibsncentral.com ([69.44.125.178] helo=OMEGA.denver.ibsncentral.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJdLK-0007cC-00; Tue, 11 Nov 2003 13:34:22 -0500
Received: from [192.168.0.175] ([192.168.0.175]) by OMEGA.denver.ibsncentral.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 11 Nov 2003 11:33:40 -0700
In-Reply-To: <8D260779A766FB4A9C1739A476F84FA401546EF7@daebe009.NOE.Nokia.com>
References: <8D260779A766FB4A9C1739A476F84FA401546EF7@daebe009.NOE.Nokia.com>
Mime-Version: 1.0 (Apple Message framework v606)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <9248241A-1475-11D8-93FA-000A95EA00C0@ibsncentral.com>
Content-Transfer-Encoding: 7bit
Cc: <routing-discussion@ietf.org>, <vrrp@ietf.org>
From: PC Drew <drewpc@ibsncentral.com>
Subject: Re: [VRRP] CARP..
Date: Tue, 11 Nov 2003 11:33:40 -0700
To: Mukesh.Gupta@nokia.com
X-Mailer: Apple Mail (2.606)
X-OriginalArrivalTime: 11 Nov 2003 18:33:40.0956 (UTC) FILETIME=[544579C0:01C3A882]
Content-Transfer-Encoding: 7bit
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

The man page is located here:

http://www.openbsd.org/cgi-bin/man.cgi? 
query=carp&apropos=0&sektion=0&manpath=OpenBSD+Current&arch=i386&format= 
html

The original post to the mailing list is here:

http://marc.theaimsgroup.com/?l=openbsd-misc&m=106642790513590&w=2

I would recommend contacting the following people for more information:

Ryan McBride: mcbride@openbsd.org
Theo de Raadt: deraadt@openbsd.org

On Nov 11, 2003, at 10:33 AM, Mukesh.Gupta@nokia.com wrote:

> Folks,
>
> Do we have anyone in the WG or routing-discussion list who
> knows about CARP (Common Address Redundancy Protocol) and
> can explain it to the WG (or just the chairs in person) in
> the WG meeting on Thursday.
>
> Please send me a mail asap. Your help will be highly
> appreciated.
>
> Regards
> Mukesh
>
> _______________________________________________
> vrrp mailing list
> vrrp@ietf.org
> https://www1.ietf.org/mailman/listinfo/vrrp
>
--
PC Drew
Manager, Dominet

IBSN
1600 Broadway, Suite 400
Denver, CO 80202

Phone: 303-984-4727 x107
Cell: 720-841-4543
Fax: 303-984-4730
Email: drewpc@ibsncentral.com


_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Tue Nov 11 18:13:26 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27540
	for <vrrp-archive@odin.ietf.org>; Tue, 11 Nov 2003 18:13:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJhh7-00075e-5z
	for vrrp-archive@odin.ietf.org; Tue, 11 Nov 2003 18:13:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hABND9q6027243
	for vrrp-archive@odin.ietf.org; Tue, 11 Nov 2003 18:13:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJhh7-00074k-0O
	for vrrp-web-archive@optimus.ietf.org; Tue, 11 Nov 2003 18:13:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27460
	for <vrrp-web-archive@ietf.org>; Tue, 11 Nov 2003 18:12:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJhh3-00049B-00
	for vrrp-web-archive@ietf.org; Tue, 11 Nov 2003 18:13:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJhh3-000498-00
	for vrrp-web-archive@ietf.org; Tue, 11 Nov 2003 18:13:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJhgz-0006yL-Vi; Tue, 11 Nov 2003 18:13:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJhga-0006xj-VL
	for vrrp@optimus.ietf.org; Tue, 11 Nov 2003 18:12:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27406
	for <vrrp@ietf.org>; Tue, 11 Nov 2003 18:12:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJhgY-00048n-00
	for vrrp@ietf.org; Tue, 11 Nov 2003 18:12:34 -0500
Received: from zcamail03.zca.compaq.com ([161.114.32.103])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJhgX-00048c-00
	for vrrp@ietf.org; Tue, 11 Nov 2003 18:12:33 -0500
Received: from mailrelay01.cac.cpqcorp.net (mailrelay01.cac.cpqcorp.net [16.47.132.152])
	by zcamail03.zca.compaq.com (Postfix) with ESMTP id A9CEAB7D6
	for <vrrp@ietf.org>; Tue, 11 Nov 2003 15:12:03 -0800 (PST)
Received: from ucxaxp.ucx.lkg.dec.com (ucxaxp.ucx.lkg.dec.com [16.20.208.53])
	by mailrelay01.cac.cpqcorp.net (Postfix) with SMTP id 84C148E4
	for <vrrp@ietf.org>; Tue, 11 Nov 2003 15:11:48 -0800 (PST)
Received: from unknown.hostname (16.115.199.49)
	 by ucxaxp.ucx.lkg.dec.com (V5.0A-1H, OpenVMS V7.1-1H2 Alpha);
	Tue, 11 Nov 2003 18:12:00 -0500 (EST)
Message-ID: <027401c3a8a8$bbefc190$b6308182@PORTABRAIN>
From: "M. T. Hollinger" <myth@ucx.lkg.dec.com>
To: <vrrp@ietf.org>
Date: Tue, 11 Nov 2003 18:08:30 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Subject: [VRRP] Scope of Valid VRRP Configurations
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Consider the following configuration:

Rtr0 is a big, beefy router with a couple of T3 upstream connections.  When
Rtr0 is up and running, the site administrator wants it to handle all
non-local traffic.  Thus, it gets configured as the Master Router (MR) for
both VRID=1 and VRID=2 on some particular link, where Rtr0 has only one line
card connected.

Rtr1 and Rtr2 are wimpy older boxes with only T1 connections.  Each is the
Backup Router (BR) for only one VRID.  When Rtr0 is shut down, Rtr1 becomes
the new master for VRID=1, and Rtr2 becomes the new master for VRID=2.

Is this setup within the scope of VRRPv3?  It isn't explicitly prohibited,
but we may run into trouble because the current draft says:

> IPv6 Routers running VRRP MUST create their Interface Identifiers in
> the normal manner (e.g., RFC2464 "Transmission of IPv6 Packets over
> Ethernet").

If Rtr0 generates its link-local address in this way, and it becomes the
IPv6 address associated with both VRID's, then what happens when Rtr0 fails?
Both Rtr1 and Rtr2 will try to use that same link-local address at the same
time.

It's funny how carefully one has to read a draft while preparing an analysis
of proposed changes.  I'm noticing things today which I breezed right past
earlier.  For example, the term "backup" is overloaded, leading to confusion
when saying something like, "when the Backup Router is in Master state", as
there is also a Backup state.  I would have changed one "Backup" to
Secondary, Standby, Contingency, or the like, but that's a nit.  I have a
few other clarifiying questions and obervations, but I will send them in
separate messages to facilitate issue tracking.

              - Mark


_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Tue Nov 11 19:48:27 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01089
	for <vrrp-archive@odin.ietf.org>; Tue, 11 Nov 2003 19:48:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJjB1-00069N-MP
	for vrrp-archive@odin.ietf.org; Tue, 11 Nov 2003 19:48:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAC0m7f9023629
	for vrrp-archive@odin.ietf.org; Tue, 11 Nov 2003 19:48:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJjB1-000691-Gi
	for vrrp-web-archive@optimus.ietf.org; Tue, 11 Nov 2003 19:48:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01030
	for <vrrp-web-archive@ietf.org>; Tue, 11 Nov 2003 19:47:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJjAz-0005Rx-00
	for vrrp-web-archive@ietf.org; Tue, 11 Nov 2003 19:48:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJjAy-0005Rr-00
	for vrrp-web-archive@ietf.org; Tue, 11 Nov 2003 19:48:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJjAv-00067k-Px; Tue, 11 Nov 2003 19:48:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJiPq-00021x-K0
	for vrrp@optimus.ietf.org; Tue, 11 Nov 2003 18:59:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29447
	for <vrrp@ietf.org>; Tue, 11 Nov 2003 18:59:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJiPn-0004kb-00
	for vrrp@ietf.org; Tue, 11 Nov 2003 18:59:19 -0500
Received: from zcamail03.zca.compaq.com ([161.114.32.103])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJiPm-0004kA-00
	for vrrp@ietf.org; Tue, 11 Nov 2003 18:59:18 -0500
Received: from mailrelay01.cac.cpqcorp.net (mailrelay01.cac.cpqcorp.net [16.47.132.152])
	by zcamail03.zca.compaq.com (Postfix) with ESMTP id 0B054B965
	for <vrrp@ietf.org>; Tue, 11 Nov 2003 15:58:48 -0800 (PST)
Received: from ucxaxp.ucx.lkg.dec.com (ucxaxp.ucx.lkg.dec.com [16.20.208.53])
	by mailrelay01.cac.cpqcorp.net (Postfix) with SMTP id 1C9E31D60
	for <vrrp@ietf.org>; Tue, 11 Nov 2003 15:58:34 -0800 (PST)
Received: from unknown.hostname (16.115.194.160)
	 by ucxaxp.ucx.lkg.dec.com (V5.0A-1H, OpenVMS V7.1-1H2 Alpha);
	Tue, 11 Nov 2003 18:58:46 -0500 (EST)
Message-ID: <028e01c3a8af$449403c0$b6308182@PORTABRAIN>
From: "M. T. Hollinger" <MyTH@hp.com>
To: <vrrp@ietf.org>
Date: Tue, 11 Nov 2003 18:55:12 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Subject: [VRRP] Changing Adver Interval
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Suppose an administrator initially deploys 3 VRRP routers for a single VRID,
sending advertisements at 2 second intervals.  At some point in the future,
he decides to change back to the default 1 second interval, but one of the
Backup Routers doesn't get changed.  Maybe it was down for maintenance at
the time and didn't return until the following week.

The VRRPv3 draft says that upon receiving a VRRP packet, a router:

>   - MUST verify that the Adver Interval in the packet is the same as
>     the locally configured for this virtual router
>
> If the above check fails, the receiver MUST discard the packet,

This would appear to mean that once the BR does come back, it will ignore
all the VRRP packets and enter Master state.  The network will then limp
along with two MR's until the administrator figures out the problem and
manually corrects it.  Is that what we intend?

Other options would be to:

  Have the BR log the discrepancy but accept the packet anyway

  Have the BR enter Initialize state (awaiting manual startup)

  Have the BR adjust its own interval and continue (see below)

If the Backup Rouer's interval is already greater than the one in the
received packet, then there is no danger in just accepting the packet.  The
BR expects a packet every 2 seconds, but the MR is sending one every second.
On the other hand, if the received interval is larger than the BR's own
interval, but still reasonable (say, within 10 seconds of the BR's
permanently configured interval), the BR could simply increase its own
interval to match.

Probably the main danger from accepting a bogus packet is a denial of
service attack, where an intruder maliciously shuts down a VRRP Backup
Router.  Of course, it wouldn't be possible to shut down a Master Router,
which doesn't look at received VRRP packets at all.  I think we could
maintain a certain level of resistance to attacks while also being more
robust to router misconfigurations than the current draft implies.

              - Mark


_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Tue Nov 11 19:51:23 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01255
	for <vrrp-archive@odin.ietf.org>; Tue, 11 Nov 2003 19:51:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJjDs-0006mn-AS
	for vrrp-archive@odin.ietf.org; Tue, 11 Nov 2003 19:51:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAC0p4Eg026079
	for vrrp-archive@odin.ietf.org; Tue, 11 Nov 2003 19:51:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJjDs-0006mY-5W
	for vrrp-web-archive@optimus.ietf.org; Tue, 11 Nov 2003 19:51:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01229
	for <vrrp-web-archive@ietf.org>; Tue, 11 Nov 2003 19:50:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJjDq-0005Vf-00
	for vrrp-web-archive@ietf.org; Tue, 11 Nov 2003 19:51:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJjDp-0005Vc-00
	for vrrp-web-archive@ietf.org; Tue, 11 Nov 2003 19:51:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJjDq-0006ka-37; Tue, 11 Nov 2003 19:51:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJjDB-0006Xq-F8
	for vrrp@optimus.ietf.org; Tue, 11 Nov 2003 19:50:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01205
	for <vrrp@ietf.org>; Tue, 11 Nov 2003 19:50:10 -0500 (EST)
From: Mukesh.Gupta@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJjD9-0005V1-00
	for vrrp@ietf.org; Tue, 11 Nov 2003 19:50:19 -0500
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJjD8-0005Uy-00
	for vrrp@ietf.org; Tue, 11 Nov 2003 19:50:19 -0500
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hAC0oIs00749
	for <vrrp@ietf.org>; Wed, 12 Nov 2003 02:50:18 +0200 (EET)
Received: from daebh001.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65da416fb9ac158f24077@esvir04nok.ntc.nokia.com>;
 Wed, 12 Nov 2003 02:50:18 +0200
Received: from daebe009.NOE.Nokia.com ([10.241.35.109]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Tue, 11 Nov 2003 16:50:16 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 11 Nov 2003 18:50:15 -0600
Message-ID: <8D260779A766FB4A9C1739A476F84FA401546EFD@daebe009.NOE.Nokia.com>
Thread-Topic: [VRRP] Scope of Valid VRRP Configurations
Thread-Index: AcOoqYyZZgOVf9QhThGdPKvBl5N3PQADRpsw
To: <myth@ucx.lkg.dec.com>, <vrrp@ietf.org>
X-OriginalArrivalTime: 12 Nov 2003 00:50:16.0759 (UTC) FILETIME=[F06B6470:01C3A8B6]
Content-Transfer-Encoding: quoted-printable
Subject: [VRRP] source email address for VRRP mailing list..
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Mark,

You probably are subscribed to VRRP mailing list with =
myth@ucx.lkg.dec.com.

Sending a mail from myth@hp.com would required my approval. So please
use myth@ucx.lkg.dec.com for further communication.

I have approved 2 mail sent from myth@hp.com for now.

Regards
Mukesh

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Tue Nov 11 19:53:22 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01341
	for <vrrp-archive@odin.ietf.org>; Tue, 11 Nov 2003 19:53:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJjFn-0006to-7I
	for vrrp-archive@odin.ietf.org; Tue, 11 Nov 2003 19:53:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAC0r3JE026514
	for vrrp-archive@odin.ietf.org; Tue, 11 Nov 2003 19:53:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJjFn-0006tZ-1d
	for vrrp-web-archive@optimus.ietf.org; Tue, 11 Nov 2003 19:53:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01322
	for <vrrp-web-archive@ietf.org>; Tue, 11 Nov 2003 19:52:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJjFk-0005Xu-00
	for vrrp-web-archive@ietf.org; Tue, 11 Nov 2003 19:53:01 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJjFk-0005Xl-00
	for vrrp-web-archive@ietf.org; Tue, 11 Nov 2003 19:53:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJjFk-0006r0-Vg; Tue, 11 Nov 2003 19:53:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJjFC-0006qM-Tl
	for vrrp@optimus.ietf.org; Tue, 11 Nov 2003 19:52:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01285
	for <vrrp@ietf.org>; Tue, 11 Nov 2003 19:52:15 -0500 (EST)
From: Mukesh.Gupta@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJjFA-0005Wq-00
	for vrrp@ietf.org; Tue, 11 Nov 2003 19:52:25 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJjFA-0005Wn-00
	for vrrp@ietf.org; Tue, 11 Nov 2003 19:52:24 -0500
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hAC0qOB16776
	for <vrrp@ietf.org>; Wed, 12 Nov 2003 02:52:24 +0200 (EET)
Received: from daebh002.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65da435798ac158f25417@esvir05nok.ntc.nokia.com> for <vrrp@ietf.org>;
 Wed, 12 Nov 2003 02:52:23 +0200
Received: from daebe009.NOE.Nokia.com ([10.241.35.109]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Tue, 11 Nov 2003 18:52:21 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 11 Nov 2003 18:52:21 -0600
Message-ID: <8D260779A766FB4A9C1739A476F84FA401546EFE@daebe009.NOE.Nokia.com>
Thread-Topic: [VRRP] Scope of Valid VRRP Configurations
Thread-Index: AcOoqYyZZgOVf9QhThGdPKvBl5N3PQADRpswAAAen/A=
To: <vrrp@ietf.org>
X-OriginalArrivalTime: 12 Nov 2003 00:52:21.0716 (UTC) FILETIME=[3AE65140:01C3A8B7]
Content-Transfer-Encoding: quoted-printable
Subject: [VRRP] FW: source email address for VRRP mailing list..
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Didn't mean to copy this mail to the WG :(

My bad !! Sorry !!

-----Original Message-----
From: Gupta Mukesh (IPRG/MtView)=20
Sent: Tuesday, November 11, 2003 6:50 PM
To: 'ext M. T. Hollinger'; vrrp@ietf.org
Subject: source email address for VRRP mailing list..


Mark,

You probably are subscribed to VRRP mailing list with =
myth@ucx.lkg.dec.com.

Sending a mail from myth@hp.com would required my approval. So please
use myth@ucx.lkg.dec.com for further communication.

I have approved 2 mail sent from myth@hp.com for now.

Regards
Mukesh

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Tue Nov 11 20:50:53 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01088
	for <vrrp-archive@odin.ietf.org>; Tue, 11 Nov 2003 19:48:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJjB1-00069W-Nt
	for vrrp-archive@odin.ietf.org; Tue, 11 Nov 2003 19:48:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAC0m7cj023643
	for vrrp-archive@odin.ietf.org; Tue, 11 Nov 2003 19:48:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJjB1-000692-I2
	for vrrp-web-archive@optimus.ietf.org; Tue, 11 Nov 2003 19:48:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01028
	for <vrrp-web-archive@ietf.org>; Tue, 11 Nov 2003 19:47:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJjAz-0005Ru-00
	for vrrp-web-archive@ietf.org; Tue, 11 Nov 2003 19:48:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJjAy-0005Rq-00
	for vrrp-web-archive@ietf.org; Tue, 11 Nov 2003 19:48:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJjAv-00067c-Gr; Tue, 11 Nov 2003 19:48:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJfbS-0004cE-Eg
	for vrrp@optimus.ietf.org; Tue, 11 Nov 2003 15:59:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21682
	for <vrrp@ietf.org>; Tue, 11 Nov 2003 15:58:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJfbQ-00020N-00
	for vrrp@ietf.org; Tue, 11 Nov 2003 15:59:08 -0500
Received: from zcamail05.zca.compaq.com ([161.114.32.105])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJfbP-0001zd-00
	for vrrp@ietf.org; Tue, 11 Nov 2003 15:59:07 -0500
Received: from taynzmail03.nz-tay.cpqcorp.net (taynzmail03.nz-tay.cpqcorp.net [16.47.4.103])
	by zcamail05.zca.compaq.com (Postfix) with ESMTP id A61D9DFFC
	for <vrrp@ietf.org>; Tue, 11 Nov 2003 12:58:32 -0800 (PST)
Received: from ucxaxp.ucx.lkg.dec.com (ucxaxp.ucx.lkg.dec.com [16.20.208.53])
	by taynzmail03.nz-tay.cpqcorp.net (Postfix) with SMTP id EA3991114
	for <vrrp@ietf.org>; Tue, 11 Nov 2003 15:58:31 -0500 (EST)
Received: from unknown.hostname (16.115.197.188)
	 by ucxaxp.ucx.lkg.dec.com (V5.0A-1H, OpenVMS V7.1-1H2 Alpha);
	Tue, 11 Nov 2003 15:58:30 -0500 (EST)
Message-ID: <020e01c3a896$16318250$b6308182@PORTABRAIN>
From: "M. T. Hollinger" <MyTH@hp.com>
To: <vrrp@ietf.org>
References: <4.3.2.7.2.20031022152233.034d2270@mailhost.iprg.nokia.com>
Subject: Re: [VRRP] newbie vrrp question
Date: Tue, 11 Nov 2003 15:55:03 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On October 22, 2003, Bob Hinden wrote:
> The reason for not accepting packets addressed to the IP address of the
> owner, if not the owner, is to make it easier to detect that one of the
> routers is down.  People have had problems with other redundancy protocols
> that did not have the behavior that their network management systems would
> not detect that one of the routers had failed because the IP address still
> responded to pings, SNMP queries, etc.  It is also confusing for routing
> protocols.  The desired behavior when one of the routers fails is to have
> user traffic keep flowing, but to have all network management bells start
> ringing.

Please, think of the poor end-user!  I know that when I visit a new network
(such as the flaky wireless LAN here at the IETF), and I am having trouble
communicating, one of the first things I do is try to PING the default
router.  If the default router doesn't respond to PINGs, I will assume it is
down and either report the problem to local network management folks or give
up on connecting and just try later.

Some hosts may use ICMP ECHO_REQUEST messages in the context of a network
troubleshooting wizard, essentially automating the same interactive
procedure I use to figure out whether my network connection is any good.

Although as you know, I like the idea of making router failure visible to
interested hosts, having the Backup Router not respond to PINGs is not a
good way to provide such visibility.  Surely, we can find some way to let
VRRP-aware network management stations detect and report failures without
causing the router to appear dead to non-VRRP-aware troubleshooting
procedures.  I disagree with that provision of the current VRRPv3 draft and
suggest that it be removed.

            - Mark


_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Wed Nov 12 00:24:41 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08773
	for <vrrp-archive@odin.ietf.org>; Wed, 12 Nov 2003 00:24:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJnUM-0008C4-KM
	for vrrp-archive@odin.ietf.org; Wed, 12 Nov 2003 00:24:24 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAC5OMEd031495
	for vrrp-archive@odin.ietf.org; Wed, 12 Nov 2003 00:24:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJnUM-0008Bu-H1
	for vrrp-web-archive@optimus.ietf.org; Wed, 12 Nov 2003 00:24:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08624
	for <vrrp-web-archive@ietf.org>; Wed, 12 Nov 2003 00:24:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJnUJ-000123-00
	for vrrp-web-archive@ietf.org; Wed, 12 Nov 2003 00:24:19 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJnUJ-000120-00
	for vrrp-web-archive@ietf.org; Wed, 12 Nov 2003 00:24:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJnUD-00087g-0u; Wed, 12 Nov 2003 00:24:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJnMa-0007LE-UW
	for vrrp@optimus.ietf.org; Wed, 12 Nov 2003 00:16:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08371
	for <vrrp@ietf.org>; Wed, 12 Nov 2003 00:16:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJnMY-0000wH-00
	for vrrp@ietf.org; Wed, 12 Nov 2003 00:16:18 -0500
Received: from ztxmail03.ztx.compaq.com ([161.114.1.207])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJnMX-0000wE-00
	for vrrp@ietf.org; Wed, 12 Nov 2003 00:16:17 -0500
Received: from mailrelay01.cac.cpqcorp.net (mailrelay01.cac.cpqcorp.net [16.47.132.152])
	by ztxmail03.ztx.compaq.com (Postfix) with ESMTP id EAB09A86F
	for <vrrp@ietf.org>; Tue, 11 Nov 2003 23:15:43 -0600 (CST)
Received: from ucxaxp.ucx.lkg.dec.com (ucxaxp.ucx.lkg.dec.com [16.20.208.53])
	by mailrelay01.cac.cpqcorp.net (Postfix) with SMTP id D59BC1657
	for <vrrp@ietf.org>; Tue, 11 Nov 2003 21:15:26 -0800 (PST)
Received: from unknown.hostname (16.115.199.195)
	 by ucxaxp.ucx.lkg.dec.com (V5.0A-1H, OpenVMS V7.1-1H2 Alpha);
	Wed, 12 Nov 2003 00:15:21 -0500 (EST)
Message-ID: <031201c3a8db$7f5cd3c0$b6308182@PORTABRAIN>
From: "M. T. Hollinger" <myth@ucx.lkg.dec.com>
To: "Don Provan" <dprovan@bivio.net>
Cc: <vrrp@ietf.org>
References: <005801c3a8c1$45b1f1b0$8918a8c0@corp.networkrobots.com>
Subject: Re: [VRRP] newbie vrrp question
Date: Wed, 12 Nov 2003 00:11:53 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi, Don.  Thanks for the response!

> Does the end user want to detect whether he has outside
> connectivity? Then he pings something outside to see if
> he has outside connectivity.

Sure, but what?  For the first 10 years I was out of college, I always used
to ping one of the servers back at school.  I couldn't ping any of the
systems at work from out on the open Internet because of our firewall, and I
wanted to ping something whose IP address I had memorized in order to take
DNS out of the equation (troubleshoot one thing at a time).

An automated diagnostic tool might do the same: try pinging a few hard-coded
addresses out on the net.  But if you just want to find out how well your
local link (e.g. wireless) is working, it's hard to match a quick 10-packet
ping of the default router to get statistics on loss and latency.

> So I think it's a case where you decide whether to continue
> to support what the end user learned to do back when he had
> one rickety router that failed all the time, or do you move
> on into the brave new world and let him discover new techniques.

Well, I think that depends.on how widely deployed VRRP becomes.  If VRRPv3
retains this behavior and becomes ubiquitous, then users (and automated
wizards) will eventually develop new techniques.  If VRRP remains a relative
rarity, then users (especially mobile users) won't learn.  When they visit a
network that does use VRRP, and a Backup Router happens to be active,
they'll think the network is really flaky.

            - M


_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Wed Nov 12 14:03:36 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02053
	for <vrrp-archive@odin.ietf.org>; Wed, 12 Nov 2003 14:03:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK0Gs-0007si-0P
	for vrrp-archive@odin.ietf.org; Wed, 12 Nov 2003 14:03:18 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hACJ3HuV030295
	for vrrp-archive@odin.ietf.org; Wed, 12 Nov 2003 14:03:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK0Gn-0007rl-M0
	for vrrp-web-archive@optimus.ietf.org; Wed, 12 Nov 2003 14:03:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02017
	for <vrrp-web-archive@ietf.org>; Wed, 12 Nov 2003 14:03:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK0Gl-0003xB-00
	for vrrp-web-archive@ietf.org; Wed, 12 Nov 2003 14:03:11 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK0Gk-0003x7-00
	for vrrp-web-archive@ietf.org; Wed, 12 Nov 2003 14:03:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK0Ga-0007r9-HX; Wed, 12 Nov 2003 14:03:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK0GY-0007qv-I5
	for vrrp@optimus.ietf.org; Wed, 12 Nov 2003 14:02:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02010
	for <vrrp@ietf.org>; Wed, 12 Nov 2003 14:02:46 -0500 (EST)
From: Kalyan.Tata@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK0GV-0003x1-00
	for vrrp@ietf.org; Wed, 12 Nov 2003 14:02:56 -0500
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK0GV-0003wx-00
	for vrrp@ietf.org; Wed, 12 Nov 2003 14:02:55 -0500
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hACJ2r613014
	for <vrrp@ietf.org>; Wed, 12 Nov 2003 21:02:53 +0200 (EET)
Received: from daebh001.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65de29b892ac158f24147@esvir04nok.ntc.nokia.com> for <vrrp@ietf.org>;
 Wed, 12 Nov 2003 21:02:53 +0200
Received: from mvebe001.NOE.Nokia.com ([172.18.140.37]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Wed, 12 Nov 2003 11:02:48 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 12 Nov 2003 11:01:56 -0800
Message-ID: <4D7B558499107545BB45044C63822DDE03ADD35B@mvebe001.americas.nokia.com>
Thread-Topic: I fixed the English...Re: VRRP MIB
Thread-Index: AcOo2U3NlWKwxBXfTKWGVWgB1BMhRwAdLm/A
To: <vrrp@ietf.org>
X-OriginalArrivalTime: 12 Nov 2003 19:02:49.0069 (UTC) FILETIME=[90A419D0:01C3A94F]
Content-Transfer-Encoding: quoted-printable
Subject: [VRRP] VRRP MIB
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

hi,
=A0=A0 I had a couple of personal discussions with various SNMP and MIB =
experts and the=20
=A0=A0 consensus is that we should go with a unified VRRP MIB. I am =
planning to=20
=A0=A0 propose going with the unified MIB at the WG meeting.
=A0=A0 As you are aware - Unified VRRP MIB means that existing =
implementations will=20
=A0=A0 have to change. I would strongly suggest any one having concerns =
with this=20
=A0=A0 approach to voice their opinion either in the mailing list or at =
the working=20
=A0=A0 group meeting.=20

	One of the reasons against a unified MIB is the loss of backward =
compatibility=20
 	with the existing VRRP MIB implementation. Could everyone having an =
existing=20
      VRRP MIB implementation respond so that we will have an idea of =
how many=20
      implementations are present.

=A0 Thanks
=A0 kalyan


_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Wed Nov 12 19:15:25 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18863
	for <vrrp-archive@odin.ietf.org>; Wed, 12 Nov 2003 19:15:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK58c-0004vh-PV
	for vrrp-archive@odin.ietf.org; Wed, 12 Nov 2003 19:15:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAD0F6Kv018945
	for vrrp-archive@odin.ietf.org; Wed, 12 Nov 2003 19:15:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK58c-0004vU-Kr
	for vrrp-web-archive@optimus.ietf.org; Wed, 12 Nov 2003 19:15:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18848
	for <vrrp-web-archive@ietf.org>; Wed, 12 Nov 2003 19:14:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK58b-0001hS-00
	for vrrp-web-archive@ietf.org; Wed, 12 Nov 2003 19:15:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK58a-0001hO-00
	for vrrp-web-archive@ietf.org; Wed, 12 Nov 2003 19:15:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK58Y-0004uD-TL; Wed, 12 Nov 2003 19:15:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK57f-0004ti-Eu
	for vrrp@optimus.ietf.org; Wed, 12 Nov 2003 19:14:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18829
	for <vrrp@ietf.org>; Wed, 12 Nov 2003 19:13:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK57d-0001gz-00
	for vrrp@ietf.org; Wed, 12 Nov 2003 19:14:05 -0500
Received: from [216.142.75.231] (helo=exmail.bivio.net)
	by ietf-mx with smtp (Exim 4.12)
	id 1AK57d-0001gb-00
	for vrrp@ietf.org; Wed, 12 Nov 2003 19:14:05 -0500
Received: from dprovan1 ([192.168.24.137]) by exmail.bivio.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Tue, 11 Nov 2003 18:04:14 -0800
From: "Don Provan" <dprovan@bivio.net>
To: "'M. T. Hollinger'" <MyTH@hp.com>
Cc: <vrrp@ietf.org>
Subject: RE: [VRRP] newbie vrrp question
Date: Tue, 11 Nov 2003 18:04:13 -0800
Message-ID: <005801c3a8c1$45b1f1b0$8918a8c0@corp.networkrobots.com>
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
In-Reply-To: <020e01c3a896$16318250$b6308182@PORTABRAIN>
X-OriginalArrivalTime: 12 Nov 2003 02:04:14.0857 (UTC) FILETIME=[45BB6790:01C3A8C1]
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>

Does the end user want to detect that his router is down?
Then he pings the address and that tells him whether his
router is down.

Does the end user want to detect whether he has outside
connectivity? Then he pings something outside to see if
he has outside connectivity.

VRRP is just providing one more way in which the two are
different and, in particular, where a failure of the
router does not mean loss of connectivity.

So I think it's a case where you decide whether to continue
to support what the end user learned to do back when he had
one rickety router that failed all the time, or do you move
on into the brave new world and let him discover new techniques.
Personally, I don't particularly care which path is taken,
but it appears the decision was to proceed along the second.

-don

> -----Original Message-----
> From: vrrp-admin@ietf.org [mailto:vrrp-admin@ietf.org]On
> Behalf Of M. T.
> Hollinger
> Sent: Tuesday, November 11, 2003 12:55 PM
> To: vrrp@ietf.org
> Subject: Re: [VRRP] newbie vrrp question
>
>
> On October 22, 2003, Bob Hinden wrote:
> > The reason for not accepting packets addressed to the IP
> address of the
> > owner, if not the owner, is to make it easier to detect
> that one of the
> > routers is down.  People have had problems with other
> redundancy protocols
> > that did not have the behavior that their network
> management systems would
> > not detect that one of the routers had failed because the
> IP address still
> > responded to pings, SNMP queries, etc.  It is also
> confusing for routing
> > protocols.  The desired behavior when one of the routers
> fails is to have
> > user traffic keep flowing, but to have all network
> management bells start
> > ringing.
>
> Please, think of the poor end-user!  I know that when I visit
> a new network
> (such as the flaky wireless LAN here at the IETF), and I am
> having trouble
> communicating, one of the first things I do is try to PING the default
> router.  If the default router doesn't respond to PINGs, I
> will assume it is
> down and either report the problem to local network
> management folks or give
> up on connecting and just try later.
>
> Some hosts may use ICMP ECHO_REQUEST messages in the context
> of a network
> troubleshooting wizard, essentially automating the same interactive
> procedure I use to figure out whether my network connection
> is any good.
>
> Although as you know, I like the idea of making router
> failure visible to
> interested hosts, having the Backup Router not respond to
> PINGs is not a
> good way to provide such visibility.  Surely, we can find
> some way to let
> VRRP-aware network management stations detect and report
> failures without
> causing the router to appear dead to non-VRRP-aware troubleshooting
> procedures.  I disagree with that provision of the current
> VRRPv3 draft and
> suggest that it be removed.
>
>             - Mark
>
>
> _______________________________________________
> vrrp mailing list
> vrrp@ietf.org
> https://www1.ietf.org/mailman/listinfo/vrrp



_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Wed Nov 12 20:11:26 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18864
	for <vrrp-archive@odin.ietf.org>; Wed, 12 Nov 2003 19:15:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK58d-0004vz-2J
	for vrrp-archive@odin.ietf.org; Wed, 12 Nov 2003 19:15:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAD0F7TL018961
	for vrrp-archive@odin.ietf.org; Wed, 12 Nov 2003 19:15:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK58c-0004vk-UH
	for vrrp-web-archive@optimus.ietf.org; Wed, 12 Nov 2003 19:15:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18849
	for <vrrp-web-archive@ietf.org>; Wed, 12 Nov 2003 19:14:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK58a-0001hV-00
	for vrrp-web-archive@ietf.org; Wed, 12 Nov 2003 19:15:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK58a-0001hP-00
	for vrrp-web-archive@ietf.org; Wed, 12 Nov 2003 19:15:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK58Y-0004u4-FB; Wed, 12 Nov 2003 19:15:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK57e-0004td-W8
	for vrrp@optimus.ietf.org; Wed, 12 Nov 2003 19:14:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18826
	for <vrrp@ietf.org>; Wed, 12 Nov 2003 19:13:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK57d-0001gt-00
	for vrrp@ietf.org; Wed, 12 Nov 2003 19:14:05 -0500
Received: from [216.142.75.231] (helo=exmail.bivio.net)
	by ietf-mx with smtp (Exim 4.12)
	id 1AK57c-0001gb-00
	for vrrp@ietf.org; Wed, 12 Nov 2003 19:14:05 -0500
Received: from dprovan1 ([192.168.24.137]) by exmail.bivio.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Tue, 11 Nov 2003 17:33:39 -0800
From: "Don Provan" <dprovan@bivio.net>
To: "'M. T. Hollinger'" <MyTH@hp.com>, <vrrp@ietf.org>
Subject: RE: [VRRP] Changing Adver Interval
Date: Tue, 11 Nov 2003 17:33:38 -0800
Message-ID: <005001c3a8bc$ffd17160$8918a8c0@corp.networkrobots.com>
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
In-Reply-To: <028e01c3a8af$449403c0$b6308182@PORTABRAIN>
X-OriginalArrivalTime: 12 Nov 2003 01:33:39.0580 (UTC) FILETIME=[FFD25BC0:01C3A8BC]
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>

Yeah, the more I deal with VRRP in practice, the sillier
dropping any packet that isn't what you're expecting seems.
The issue you raise doesn't require any special circumstances:
if you have to walk from one router to the next to change the
interval, the network will be conflicted while you're walking.

I decided the only reasonable attitude towards a different
interval is to assume that a change is in progress. So
any backup hearing a different interval from the master
uses the master's interval. If the master hears a faster
interval from anyone, he switches to that interval to make
sure the backup doesn't take over accidentally. As long as
you configure the master last when slowing down, it works
fine without any fighting.

-don



_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Wed Nov 12 22:22:26 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24577
	for <vrrp-archive@odin.ietf.org>; Wed, 12 Nov 2003 22:22:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK83d-0006P7-Mr
	for vrrp-archive@odin.ietf.org; Wed, 12 Nov 2003 22:22:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAD3M9tp024616
	for vrrp-archive@odin.ietf.org; Wed, 12 Nov 2003 22:22:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK83d-0006Ox-J3
	for vrrp-web-archive@optimus.ietf.org; Wed, 12 Nov 2003 22:22:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24564
	for <vrrp-web-archive@ietf.org>; Wed, 12 Nov 2003 22:21:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK83a-0004IE-00
	for vrrp-web-archive@ietf.org; Wed, 12 Nov 2003 22:22:06 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK83Z-0004I8-00
	for vrrp-web-archive@ietf.org; Wed, 12 Nov 2003 22:22:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK83V-0006NW-Uc; Wed, 12 Nov 2003 22:22:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK82u-0006MO-HC
	for vrrp@optimus.ietf.org; Wed, 12 Nov 2003 22:21:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24452
	for <vrrp@ietf.org>; Wed, 12 Nov 2003 22:21:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK82r-0004Fk-00
	for vrrp@ietf.org; Wed, 12 Nov 2003 22:21:21 -0500
Received: from ztxmail05.ztx.compaq.com ([161.114.1.209])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK82q-0004FY-00
	for vrrp@ietf.org; Wed, 12 Nov 2003 22:21:20 -0500
Received: from taynzmail03.nz-tay.cpqcorp.net (taynzmail03.nz-tay.cpqcorp.net [16.47.4.103])
	by ztxmail05.ztx.compaq.com (Postfix) with ESMTP id 0BD5FC9DB
	for <vrrp@ietf.org>; Wed, 12 Nov 2003 21:20:51 -0600 (CST)
Received: from ucxaxp.ucx.lkg.dec.com (ucxaxp.ucx.lkg.dec.com [16.20.208.53])
	by taynzmail03.nz-tay.cpqcorp.net (Postfix) with SMTP id 53EED833
	for <vrrp@ietf.org>; Wed, 12 Nov 2003 22:20:50 -0500 (EST)
Received: from unknown.hostname (16.115.198.79)
	 by ucxaxp.ucx.lkg.dec.com (V5.0A-1H, OpenVMS V7.1-1H2 Alpha);
	Wed, 12 Nov 2003 22:20:46 -0500 (EST)
Message-ID: <017101c3a994$a5f77da0$65878182@PORTABRAIN>
From: "M. T. Hollinger" <myth@ucx.lkg.dec.com>
To: <vrrp@ietf.org>
Date: Wed, 12 Nov 2003 22:17:10 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Subject: [VRRP] System Convergence Time
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

One VMAC-related topic I hope to discuss at tomorrow morning's meeting is
convergence time.  In order to offer useful connectivity, the whole system
has to converge -- not just VRRP.  Below (at the MAC layer), there is the
spanning tree algorithm of the learning bridges in the extended LAN.  Above,
there are the routing protocols.  Bidirectional traffic won't start flowing
again, after a failure, until all three converge.

Cisco has an interesting set of test results on convergence time of a
complete system involving the spanning tree algorithm.  This paper relates
to HSRP with IPv4, not VRRP with IPv6, but it's still great reading for
anyone contemplating the impact of spanning tree convergence time on router
availability.  See:

http://www.cisco.com/warp/public/cc/so/cuso/epso/entdes/hsrp_wp.htm .

These results really make you think about what a challenge achieving
subsecond failover will be for the system as a whole.  There are fast
versions of the bridge spanning tree protocol such as 802.1w, and of course,
fast routing protocols, but a network administrator desiring fast failover
will have to understand and deploy all of them.

              - M


_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Thu Nov 13 03:52:34 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16856
	for <vrrp-archive@odin.ietf.org>; Thu, 13 Nov 2003 03:52:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKDD4-0002ij-Og
	for vrrp-archive@odin.ietf.org; Thu, 13 Nov 2003 03:52:14 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAD8qEqr010456
	for vrrp-archive@odin.ietf.org; Thu, 13 Nov 2003 03:52:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKDD4-0002iY-8H
	for vrrp-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 03:52:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16835
	for <vrrp-web-archive@ietf.org>; Thu, 13 Nov 2003 03:52:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKDD1-00010J-00
	for vrrp-web-archive@ietf.org; Thu, 13 Nov 2003 03:52:11 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKDD1-00010G-00
	for vrrp-web-archive@ietf.org; Thu, 13 Nov 2003 03:52:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKDCr-0002ho-9b; Thu, 13 Nov 2003 03:52:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKDBy-0002gx-P0
	for vrrp@optimus.ietf.org; Thu, 13 Nov 2003 03:51:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16824
	for <vrrp@ietf.org>; Thu, 13 Nov 2003 03:50:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKDBw-0000zh-00
	for vrrp@ietf.org; Thu, 13 Nov 2003 03:51:04 -0500
Received: from zcamail03.zca.compaq.com ([161.114.32.103])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKDBv-0000zb-00
	for vrrp@ietf.org; Thu, 13 Nov 2003 03:51:03 -0500
Received: from taynzmail03.nz-tay.cpqcorp.net (taynzmail03.nz-tay.cpqcorp.net [16.47.4.103])
	by zcamail03.zca.compaq.com (Postfix) with ESMTP id E44B9B96C
	for <vrrp@ietf.org>; Thu, 13 Nov 2003 00:50:33 -0800 (PST)
Received: from ucxaxp.ucx.lkg.dec.com (ucxaxp.ucx.lkg.dec.com [16.20.208.53])
	by taynzmail03.nz-tay.cpqcorp.net (Postfix) with SMTP id 007B3A47
	for <vrrp@ietf.org>; Thu, 13 Nov 2003 03:50:33 -0500 (EST)
Received: from unknown.hostname (16.115.194.94)
	 by ucxaxp.ucx.lkg.dec.com (V5.0A-1H, OpenVMS V7.1-1H2 Alpha);
	Thu, 13 Nov 2003 03:50:30 -0500 (EST)
Message-ID: <008701c3a9c2$b4771b00$b6308182@PORTABRAIN>
From: "M. T. Hollinger" <myth@ucx.lkg.dec.com>
To: <vrrp@ietf.org>
Subject: Re: [VRRP] Scope of Valid VRRP Configurations
Date: Thu, 13 Nov 2003 01:38:58 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Since nobody has yet taken the bait and responded to the question I posted
Tuesday about Rtr0 being the primary master for multiple VRID's, I thought I
would send out some additional thoughts of my own on the same topic.

Again, I would clarify "may participate in one or more virtual routers"; can
a router participate as "IPv6 address owner" in more than one VR on a given
interface?  Note that a unique IPv6 address must be assigned to each, which
is fine because an IPv6 node can certainly own multiple addresses.

Partly for that reason, I would favor always assigning a unique IPv6 address
for each VRID, at least as an option, rather than overloading a link-local
address previously held by one of the participating routers.

I suggest clarifying the meaning of "IPv6 address owner" when multiple IP
addresses are used.  The current definition says, "the VRRP router that has
the virtual router's IPv6 address as real interface address," but that seems
to reflect an overly limited view.  Later in the existing document, a
parenthetical explanation says, "the local router is not the IPv6 Address
owner (Priority equals 255 (decimal))," which seems to me a better
definition.  However, if that's the definition, why not say so up front, in
the Definitions section?

We may wish to add clarifying text like:

    A priority value of 255 designates a particular rotuer
    as the "IPv6 address owner".  Care must be taken not
    to configure more than one router on the link in this
    way for a single VRID.

Perhaps in the same section, the text could also say:

    When there are multiple Backup Routers, their priority
    values should be uniformly distributed.  For example,
    if one BR has the default priority of 100 and another
    BR is added, a priority of 50 would be a better choice
    for it than 99 or 100 to facilitate faster convergence.

This clarification might be useful to dispel any notion that because the
protocol includes a provision for a tie-breaker, configuring multiple
routers with the same priority value is a good idea.  Taking the defaults,
someone setting up a Master Router and two BR's might leave the MR's
priority at 255 and both BR's at 100.  Oops.  They will then both have the
same Skew_Time, and both will try to grab control at the same instant
following a failure of the old Master.

Alternatively, the new claryifying text might say:

    Priority values SHOULD NOT be equal for two or more
    participating routers and SHOULD differ by at least 10.

We could also clarify, in the equal priority tie-breaking case, to use the
sender's address from the IP header -- not the IP address field in the VRRP
packet, which would be the one associated with the VRID in question, the
same for both participating routers.  Looking at the IP header will require
more cross-layer communication than some router implementations may offer,
but it's the only way to make the tie-breaker work.

The draft says, "It may be useful to support an override of the immediate
convergence to the preferred path," but then goes on to define a protocol
where the "IPv6 address owner" always preempts the current Master, even if
preemption is disabled.  If we expect that many deployments will be limited
to a single Backup Router, doesn't that make the preemption setting pretty
useless?

Building on my earlier observation that the notion of which router "owns" an
IPv6 address is rather arbitrary, I would propose a tweak to the design and
say:

    Routers with priority 255 will, as soon as they start up,
    preempt all lower priority routers.  Configure no more than
    one router on the link with priority 255.  If no router has
    this priority, and preemption is disabled, then no
    preemption will occur.

OK, so where would these new addresses come from?  One option might be to
use, by default, an IPv6 link-local address from a range reserved for VRRP
(much as the current draft does for the MAC address).  This would serve as a
convenient flag for troubleshooting purposes that VRRP is in use, but the
big win would be ease of configuration.  Rather than having to type in a
VRID number and a big long IPv6 address, you could just type in the VRID
number and take the associated default address.  Since it's so easy to make
a typo while entering an IPv6 address, we could avoid a lot of configuration
errors by generating the address automatically.

Duplicate Address Detection could even help to contain problems arising from
misconfigurations where, for example, two routers with prio=255 are
inadvertently connected to the same link, because they would be trying to
use the same IPv6 address.  We would probably want to disable DAD during
failover (upon transition from Backup to Master state) for performance
reasons, but it would be great to use at startup (transition from Initialize
to Master).

Another interesting option would be Cryptographically Generated Addresses,
as proposed in the SEND WG.  At some point, VRRP routers will probably need
to participate in secure neighbor discovery, and being able to generate and
share CGA's among participating routers may come in handy.  It's too early
to say exactly how that will work, and I certainly wouldn't advocate
delaying this nearly-complete VRRP work on the basis of early work in
another group.  However, leaving some latitude in this document around how a
network administrator might choose to allocate an IPv6 address for each VRRP
router sounds like a good idea and should not delay our progress.

           - M


_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Thu Nov 13 14:47:28 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15033
	for <vrrp-archive@odin.ietf.org>; Thu, 13 Nov 2003 14:47:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKNQs-0007x9-54
	for vrrp-archive@odin.ietf.org; Thu, 13 Nov 2003 14:47:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hADJlAha030567
	for vrrp-archive@odin.ietf.org; Thu, 13 Nov 2003 14:47:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKNQs-0007ww-1S
	for vrrp-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 14:47:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15024
	for <vrrp-web-archive@ietf.org>; Thu, 13 Nov 2003 14:46:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKNQp-0003jJ-00
	for vrrp-web-archive@ietf.org; Thu, 13 Nov 2003 14:47:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKNQo-0003jE-00
	for vrrp-web-archive@ietf.org; Thu, 13 Nov 2003 14:47:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKNQi-0007ui-UZ; Thu, 13 Nov 2003 14:47:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKNQJ-0007uC-Lh
	for vrrp@optimus.ietf.org; Thu, 13 Nov 2003 14:46:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15003
	for <vrrp@ietf.org>; Thu, 13 Nov 2003 14:46:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKNQE-0003hn-00
	for vrrp@ietf.org; Thu, 13 Nov 2003 14:46:30 -0500
Received: from oldmoon.mt.lv ([159.148.172.198] helo=snake.mt.lv)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKNQA-0003hj-00
	for vrrp@ietf.org; Thu, 13 Nov 2003 14:46:26 -0500
Received: from 10.1.0.144 (localhost [127.0.0.1])
	by snake.mt.lv (8.12.3/8.12.3/Debian-6.6) with ESMTP id hADJhoIg004965;
	Thu, 13 Nov 2003 21:43:50 +0200
From: Dmitry Golubev <dmitry@mikrotik.com>
To: vrrp@ietf.org
Date: Thu, 13 Nov 2003 21:44:52 +0200
User-Agent: KMail/1.5.4
References: <005801c3a8c1$45b1f1b0$8918a8c0@corp.networkrobots.com>
In-Reply-To: <005801c3a8c1$45b1f1b0$8918a8c0@corp.networkrobots.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200311132144.52408.dmitry@mikrotik.com>
Content-Transfer-Encoding: quoted-printable
Subject: [VRRP] Clearifying IP owner definition
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hello,=20

from the draft (in RFC there is, I think, the exact wording?):

IP Address Owner       The VRRP router that has the virtual router's
            		            IP address(es) as real interface address(es).
               		           This is the router that, when up, will respond
                 		    to packets addressed to one of these IP
                    		   addresses for ICMP pings, TCP connections,
                      		   etc.

=46rom this may appear misunderstanding (or maybe it is not a
misunderstanding, but the way it actual should work????) that
IP address owner is not required to have ALL the IP addresses
of the VR, and, furthermore, that there might be more than one
owners in the VR. Further in the text it is, of course, it becomes
clear, that this is really my misunderstanding (although there is
no single place where it is said directly).

So I think the word "all" should be added in the definition to
eliminate the possibility of such misunderstanding:
=2E..router that has all the virtual router's...

Also I think that the wording "...to one of these..." need to be
replaced to "...to any of these..." as I cannot imagine any other
need of having an IP address except for "ICMP pings, TCP
connections, etc."

Dmitry


_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Thu Nov 13 18:20:31 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28662
	for <vrrp-archive@odin.ietf.org>; Thu, 13 Nov 2003 18:20:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKQl2-0008Mg-G3
	for vrrp-archive@odin.ietf.org; Thu, 13 Nov 2003 18:20:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hADNKBJE032144
	for vrrp-archive@odin.ietf.org; Thu, 13 Nov 2003 18:20:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKQky-0008LW-M4
	for vrrp-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 18:20:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28658
	for <vrrp-web-archive@ietf.org>; Thu, 13 Nov 2003 18:19:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKQkv-0007iv-00
	for vrrp-web-archive@ietf.org; Thu, 13 Nov 2003 18:20:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKQkv-0007is-00
	for vrrp-web-archive@ietf.org; Thu, 13 Nov 2003 18:20:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKQkr-0008KU-PF; Thu, 13 Nov 2003 18:20:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKQk7-0008Jb-77
	for vrrp@optimus.ietf.org; Thu, 13 Nov 2003 18:19:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28609
	for <vrrp@ietf.org>; Thu, 13 Nov 2003 18:19:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKQk4-0007hy-00
	for vrrp@ietf.org; Thu, 13 Nov 2003 18:19:12 -0500
Received: from hoemail2.lucent.com ([192.11.226.163] helo=hoemail2.firewall.lucent.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKQk3-0007hh-00
	for vrrp@ietf.org; Thu, 13 Nov 2003 18:19:11 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail2.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id hADNI8q10082
	for <vrrp@ietf.org>; Thu, 13 Nov 2003 17:18:19 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2656.59)
	id <WMXRZ2VV>; Fri, 14 Nov 2003 00:18:07 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15502EAFCCD@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: vrrp@ietf.org
Subject: RE: [VRRP] VRRP MIB
Date: Fri, 14 Nov 2003 00:18:04 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Posting what I stated at the session this morning.

Mmm... they could accomodate existing implementations with
the current COMPLIANCE statement depreacted, no?

I forget what would cause complete incompatibility for
exisiting old implementations?

So unless you can refresh my memory, I am inclinde to=20
respond:

Kalyan writes:

> hi,
> =A0=A0 I had a couple of personal discussions with various SNMP=20
>    and MIB experts and the=20
> =A0=A0 consensus is that we should go with a unified VRRP MIB. I=20
>    am planning to=20
> =A0=A0 propose going with the unified MIB at the WG meeting.
> =A0=A0 As you are aware - Unified VRRP MIB means that existing=20
>    implementations will=20
> =A0=A0 have to change. I would strongly suggest any one having=20
>    concerns with this=20
> =A0=A0 approach to voice their opinion either in the mailing list=20
>    or at the working  group meeting.=20
>=20
> 	One of the reasons against a unified MIB is the loss of=20
>     backward compatibility with the existing VRRP
>     MIB implementation.

I think that if you properly deprecate objects and add new ones and
then properly define the MODULE-COMPLIANCE statements, that we can
in fact allow for backward compatibility for old existing=20
implementations. They would claim compliance with a deprecated
MODULE COMPLIANCE. Or so I think.=20

But the changes are big enough that if you want to go to the new
unified approach, which potentially changes indexing), then such
a change probably has a serious impact

>     Could everyone having an existing VRRP MIB implementation
>     respond so that we will have an idea of how many=20
>     implementations are present.
>=20

That would be good to know.

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Thu Nov 13 23:32:30 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11103
	for <vrrp-archive@odin.ietf.org>; Thu, 13 Nov 2003 23:32:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKVcx-0006aI-Tx
	for vrrp-archive@odin.ietf.org; Thu, 13 Nov 2003 23:32:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAE4WBPo025310
	for vrrp-archive@odin.ietf.org; Thu, 13 Nov 2003 23:32:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKVcx-0006a9-PC
	for vrrp-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 23:32:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11085
	for <vrrp-web-archive@ietf.org>; Thu, 13 Nov 2003 23:31:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKVcv-0005IA-00
	for vrrp-web-archive@ietf.org; Thu, 13 Nov 2003 23:32:09 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKVcv-0005I7-00
	for vrrp-web-archive@ietf.org; Thu, 13 Nov 2003 23:32:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKVco-0006XT-G4; Thu, 13 Nov 2003 23:32:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKVci-0006XH-IT
	for vrrp@optimus.ietf.org; Thu, 13 Nov 2003 23:31:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11076
	for <vrrp@ietf.org>; Thu, 13 Nov 2003 23:31:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKVcg-0005Hx-00
	for vrrp@ietf.org; Thu, 13 Nov 2003 23:31:54 -0500
Received: from ztxmail04.ztx.compaq.com ([161.114.1.208])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKVcf-0005Hl-00
	for vrrp@ietf.org; Thu, 13 Nov 2003 23:31:53 -0500
Received: from taynzmail03.nz-tay.cpqcorp.net (taynzmail03.nz-tay.cpqcorp.net [16.47.4.103])
	by ztxmail04.ztx.compaq.com (Postfix) with ESMTP id B8CD89EF0
	for <vrrp@ietf.org>; Thu, 13 Nov 2003 22:31:23 -0600 (CST)
Received: from ucxaxp.ucx.lkg.dec.com (ucxaxp.ucx.lkg.dec.com [16.20.208.53])
	by taynzmail03.nz-tay.cpqcorp.net (Postfix) with SMTP id 66382FC4
	for <vrrp@ietf.org>; Thu, 13 Nov 2003 23:31:22 -0500 (EST)
Received: from unknown.hostname (16.115.197.170)
	 by ucxaxp.ucx.lkg.dec.com (V5.0A-1H, OpenVMS V7.1-1H2 Alpha);
	Thu, 13 Nov 2003 23:31:20 -0500 (EST)
Message-ID: <03cf01c3aa67$a702d540$b6308182@PORTABRAIN>
From: "M. T. Hollinger" <myth@ucx.lkg.dec.com>
To: <vrrp@ietf.org>
Subject: Re: [VRRP] newbie vrrp question
Date: Thu, 13 Nov 2003 23:27:21 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

At today's meeting, we discussed this thread and, I believe, achieved a
resolution.  Still, since I'd already written up a paragraph further
explaining why I think routers should accept and respond to packets like
pings (er, ICMP ECHO_REQUESTs) even if they don't have priority 255, here it
is:

I think it's presumptuous for us to assume that the network administrator
will want alarms going off the entire time the "IPv6 address owner" is
unavailable.  VRRP provides 255 priorities, suggesting that there might be
more than one Backup Router available for a single VRID.  Since there may be
several BR's available, and it may take several days to get the main router
back online after a hardware failure, I believe the current Master should go
ahead and respond to pings.  Also, it should respond to SNMP queries because
the person wishing to query the router may know only the IPv6 address of the
virtual router.  If the current Master is not the "address owner", it could
take a lot of work to figure out the non-VRRP link-local address of the
Master.

Today, Bob Hinden (the document author) commented that he has seen
implementations which do respond, and it doesn't seem to break VRRP.  I
expect this behavior in some implementations will be a configuration
parameter.  There seemed to be consensus to weaken the "MUST NOT" language
in the current draft, and Bob agreed to update the next revision of the
draft to reflect that decision.

            - M


_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Fri Nov 14 16:12:28 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29551
	for <vrrp-archive@odin.ietf.org>; Fri, 14 Nov 2003 16:12:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKlEh-0000Xd-Ke
	for vrrp-archive@odin.ietf.org; Fri, 14 Nov 2003 16:12:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAELCBJ4002075
	for vrrp-archive@odin.ietf.org; Fri, 14 Nov 2003 16:12:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKlEh-0000XO-Fa
	for vrrp-web-archive@optimus.ietf.org; Fri, 14 Nov 2003 16:12:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29522
	for <vrrp-web-archive@ietf.org>; Fri, 14 Nov 2003 16:11:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKlEa-0004N4-00
	for vrrp-web-archive@ietf.org; Fri, 14 Nov 2003 16:12:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKlEa-0004N0-00
	for vrrp-web-archive@ietf.org; Fri, 14 Nov 2003 16:12:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKlEW-0000Uw-4m; Fri, 14 Nov 2003 16:12:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKlEA-0000UY-6T
	for vrrp@optimus.ietf.org; Fri, 14 Nov 2003 16:11:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29501
	for <vrrp@ietf.org>; Fri, 14 Nov 2003 16:11:24 -0500 (EST)
From: arun.mahajan@att.net
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKlE8-0004MD-00
	for vrrp@ietf.org; Fri, 14 Nov 2003 16:11:36 -0500
Received: from mtiwmhc13.worldnet.att.net ([204.127.131.117])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKlE8-0004Lu-00
	for vrrp@ietf.org; Fri, 14 Nov 2003 16:11:36 -0500
Received: from 204.127.135.59 ([204.127.135.59])
          by worldnet.att.net (mtiwmhc13) with SMTP
          id <2003111421110611300e3fd4e>; Fri, 14 Nov 2003 21:11:06 +0000
Received: from [12.146.153.254] by 204.127.135.59;
	Fri, 14 Nov 2003 21:11:04 +0000
To: vrrp@ietf.org
Date: Fri, 14 Nov 2003 21:11:04 +0000
Message-Id: <111420032111.23366.e9d@att.net>
X-Mailer: AT&T Message Center Version 1 (Oct 10 2003)
X-Authenticated-Sender: YXJ1bi5tYWhhamFuQGF0dC5uZXQ=
Subject: [VRRP] HSRP, conditions of use
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>


A couple of somewhat newbie questions if you please.

Has anybody implemented code such that it serves VRRP as well as
HSRP purposes? Ideally, I would like to do so such that there is
some sort of auto detection (or via configuration) and my code 
would behave appropriately. I would appreciate hearing about pitfalls
and perhaps pointers to doing this or if indeed it is not the
done thing.

Secondly, how does one go about getting a licence from Cisco for 
the use of HSRP (as stated in RFC 2281)?

I would appreciate any answers to my questions.

Thank you,

    Arun Mahajan



_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Fri Nov 14 17:09:41 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01269
	for <vrrp-archive@odin.ietf.org>; Fri, 14 Nov 2003 17:09:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKm85-0004wW-8k
	for vrrp-archive@odin.ietf.org; Fri, 14 Nov 2003 17:09:25 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAEM9PxC018994
	for vrrp-archive@odin.ietf.org; Fri, 14 Nov 2003 17:09:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKm85-0004wD-3Z
	for vrrp-web-archive@optimus.ietf.org; Fri, 14 Nov 2003 17:09:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01223
	for <vrrp-web-archive@ietf.org>; Fri, 14 Nov 2003 17:09:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKm81-00057k-00
	for vrrp-web-archive@ietf.org; Fri, 14 Nov 2003 17:09:21 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKm80-00057G-00
	for vrrp-web-archive@ietf.org; Fri, 14 Nov 2003 17:09:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKm7i-0004st-5U; Fri, 14 Nov 2003 17:09:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKm70-0004s5-05
	for vrrp@optimus.ietf.org; Fri, 14 Nov 2003 17:08:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01188
	for <vrrp@ietf.org>; Fri, 14 Nov 2003 17:08:03 -0500 (EST)
From: Mukesh.Gupta@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKm6x-000565-00
	for vrrp@ietf.org; Fri, 14 Nov 2003 17:08:15 -0500
Received: from manatick.foretec.com ([4.17.168.5] helo=manatick)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKm6x-00055w-00
	for vrrp@ietf.org; Fri, 14 Nov 2003 17:08:15 -0500
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by manatick with esmtp (Exim 4.24)
	id 1AKm3B-0007JN-Qp
	for vrrp@ietf.org; Fri, 14 Nov 2003 17:04:21 -0500
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hAEM4H609391
	for <vrrp@ietf.org>; Sat, 15 Nov 2003 00:04:17 +0200 (EET)
Received: from daebh001.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65e91c84d6ac158f2313b@esvir03nok.nokia.com>;
 Sat, 15 Nov 2003 00:04:17 +0200
Received: from daebe009.NOE.Nokia.com ([10.241.35.109]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Fri, 14 Nov 2003 14:04:08 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [VRRP] HSRP, conditions of use
Date: Fri, 14 Nov 2003 16:04:08 -0600
Message-ID: <8D260779A766FB4A9C1739A476F84FA401546F2B@daebe009.americas.nokia.com>
Thread-Topic: [VRRP] HSRP, conditions of use
Thread-Index: AcOq8/4QG1VMSKnxRmu1MhKpavlXQgABoYjw
To: <arun.mahajan@att.net>
Cc: <vrrp@ietf.org>
X-OriginalArrivalTime: 14 Nov 2003 22:04:08.0691 (UTC) FILETIME=[3A3A2C30:01C3AAFB]
Content-Transfer-Encoding: quoted-printable
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

> Secondly, how does one go about getting a licence from Cisco for=20
> the use of HSRP (as stated in RFC 2281)?

The message at=20
http://archives.neohapsis.com/archives/openbsd/2002-08/0203.html
from Jim Mazmus says that Cisco does not license patent for=20
implementation of HSRP.

Robert Barr (rbarr@cisco.com) should be able to help you with all=20
this anyway.

Regards
Mukesh

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Fri Nov 14 17:36:24 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02341
	for <vrrp-archive@odin.ietf.org>; Fri, 14 Nov 2003 17:36:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKmXw-0006yI-FI
	for vrrp-archive@odin.ietf.org; Fri, 14 Nov 2003 17:36:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAEMa8GO026797
	for vrrp-archive@odin.ietf.org; Fri, 14 Nov 2003 17:36:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKmXw-0006y8-99
	for vrrp-web-archive@optimus.ietf.org; Fri, 14 Nov 2003 17:36:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02300
	for <vrrp-web-archive@ietf.org>; Fri, 14 Nov 2003 17:35:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKmXt-0005cr-00
	for vrrp-web-archive@ietf.org; Fri, 14 Nov 2003 17:36:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKmXt-0005co-00
	for vrrp-web-archive@ietf.org; Fri, 14 Nov 2003 17:36:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKmXp-0006w6-QR; Fri, 14 Nov 2003 17:36:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKmXP-0006vY-UQ
	for vrrp@optimus.ietf.org; Fri, 14 Nov 2003 17:35:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02277
	for <vrrp@ietf.org>; Fri, 14 Nov 2003 17:35:20 -0500 (EST)
From: arun.mahajan@att.net
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKmXN-0005c1-00
	for vrrp@ietf.org; Fri, 14 Nov 2003 17:35:33 -0500
Received: from mtiwmhc12.worldnet.att.net ([204.127.131.116])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKmXN-0005bW-00
	for vrrp@ietf.org; Fri, 14 Nov 2003 17:35:33 -0500
Received: from 204.127.135.57 ([204.127.135.57])
          by worldnet.att.net (mtiwmhc12) with SMTP
          id <2003111422350211200co7ile>; Fri, 14 Nov 2003 22:35:02 +0000
Received: from [12.146.153.254] by 204.127.135.57;
	Fri, 14 Nov 2003 22:35:02 +0000
To: Mukesh.Gupta@nokia.com
Cc: <vrrp@ietf.org>
Subject: RE: [VRRP] HSRP, conditions of use
Date: Fri, 14 Nov 2003 22:35:02 +0000
Message-Id: <111420032235.22783.3972@att.net>
X-Mailer: AT&T Message Center Version 1 (Oct 10 2003)
X-Authenticated-Sender: YXJ1bi5tYWhhamFuQGF0dC5uZXQ=
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>

Thank you for the prompt response.

I will follow up on the links that you have pointed me to.

Regards,

    .arun
> > Secondly, how does one go about getting a licence from Cisco for 
> > the use of HSRP (as stated in RFC 2281)?
> 
> The message at 
> http://archives.neohapsis.com/archives/openbsd/2002-08/0203.html
> from Jim Mazmus says that Cisco does not license patent for 
> implementation of HSRP.
> 
> Robert Barr (rbarr@cisco.com) should be able to help you with all 
> this anyway.
> 
> Regards
> Mukesh
> 
> _______________________________________________
> vrrp mailing list
> vrrp@ietf.org
> https://www1.ietf.org/mailman/listinfo/vrrp

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Fri Nov 14 21:18:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10002
	for <vrrp-archive@odin.ietf.org>; Fri, 14 Nov 2003 21:18:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKq0j-0006SB-DZ
	for vrrp-archive@odin.ietf.org; Fri, 14 Nov 2003 21:18:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAF2I5Vr024803
	for vrrp-archive@odin.ietf.org; Fri, 14 Nov 2003 21:18:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKq0j-0006Ry-6d
	for vrrp-web-archive@optimus.ietf.org; Fri, 14 Nov 2003 21:18:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09978
	for <vrrp-web-archive@ietf.org>; Fri, 14 Nov 2003 21:17:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKq0g-0000f1-00
	for vrrp-web-archive@ietf.org; Fri, 14 Nov 2003 21:18:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKq0g-0000ey-00
	for vrrp-web-archive@ietf.org; Fri, 14 Nov 2003 21:18:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKq0f-0006Qr-JF; Fri, 14 Nov 2003 21:18:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKq0A-0006PD-7K
	for vrrp@optimus.ietf.org; Fri, 14 Nov 2003 21:17:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09934
	for <vrrp@ietf.org>; Fri, 14 Nov 2003 21:17:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKq07-0000e7-00
	for vrrp@ietf.org; Fri, 14 Nov 2003 21:17:27 -0500
Received: from zmamail03.zma.compaq.com ([161.114.64.103])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKq06-0000e4-00
	for vrrp@ietf.org; Fri, 14 Nov 2003 21:17:26 -0500
Received: from mailrelay01.cce.cpqcorp.net (mailrelay01.cce.cpqcorp.net [16.47.68.171])
	by zmamail03.zma.compaq.com (Postfix) with ESMTP id 5CAC611216
	for <vrrp@ietf.org>; Fri, 14 Nov 2003 21:17:27 -0500 (EST)
Received: from ucxaxp.ucx.lkg.dec.com (ucxaxp.ucx.lkg.dec.com [16.20.208.53])
	by mailrelay01.cce.cpqcorp.net (Postfix) with SMTP id 7330881F
	for <vrrp@ietf.org>; Fri, 14 Nov 2003 20:17:26 -0600 (CST)
Received: from unknown.hostname (16.115.193.12)
	 by ucxaxp.ucx.lkg.dec.com (V5.0A-1H, OpenVMS V7.1-1H2 Alpha);
	Fri, 14 Nov 2003 21:17:24 -0500 (EST)
Message-ID: <000201c3ab1e$1823bdf0$aa00a8c0@PORTABRAIN>
From: "M. T. Hollinger" <myth@ucx.lkg.dec.com>
To: <vrrp@ietf.org>
Subject: Re: [VRRP] newbie vrrp question
Date: Thu, 13 Nov 2003 23:23:35 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

At today's meeting, we discussed this thread and, I believe, achieved a
resolution.  Still, since I'd already written up a paragraph further
explaining why I think routers should accept and respond to packets like
pings (er, ICMP ECHO_REQUESTs) even if they don't have priority 255, here it
is:

I think it's presumptuous for us to assume that the network administrator
will want alarms going off the entire time the "IPv6 address owner" is
unavailable.  VRRP provides 255 priorities, suggesting that there might be
more than one Backup Router available for a single VRID.  If there are
several BR's available, and if it takes several days to get the main router
back online after a hardware failure, I believe the current Master should go
ahead and respond to pings.  Also, if someone wants to send an SNMP query,
and the current Master is not the "address owner", it could take a lot of
work to figure out the non-VRRP link-local address of the Master.

Today, Bob Hinden (the document author) commented that he has seen
implementations which do respond, and it doesn't seem to break VRRP.  I
expect this behavior in some implementations will be a configuration
parameter.  There seemed to be consensus to weaken the "MUST NOT" language
in the current draft, and Bob agreed to update the next revision of the
draft to reflect that decision.

            - M


_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Sat Nov 15 04:56:30 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02751
	for <vrrp-archive@odin.ietf.org>; Sat, 15 Nov 2003 04:56:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKxA4-000294-0m
	for vrrp-archive@odin.ietf.org; Sat, 15 Nov 2003 04:56:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAF9uBxC008247
	for vrrp-archive@odin.ietf.org; Sat, 15 Nov 2003 04:56:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKxA3-00028w-Jn
	for vrrp-web-archive@optimus.ietf.org; Sat, 15 Nov 2003 04:56:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02739
	for <vrrp-web-archive@ietf.org>; Sat, 15 Nov 2003 04:55:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKxA0-0005cX-00
	for vrrp-web-archive@ietf.org; Sat, 15 Nov 2003 04:56:08 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKx9z-0005cU-00
	for vrrp-web-archive@ietf.org; Sat, 15 Nov 2003 04:56:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKx9u-00028K-4d; Sat, 15 Nov 2003 04:56:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKx9F-00021J-VD
	for vrrp@optimus.ietf.org; Sat, 15 Nov 2003 04:55:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02731
	for <vrrp@ietf.org>; Sat, 15 Nov 2003 04:55:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKx9C-0005cK-00
	for vrrp@ietf.org; Sat, 15 Nov 2003 04:55:18 -0500
Received: from [216.142.75.231] (helo=exmail.bivio.net)
	by ietf-mx with smtp (Exim 4.12)
	id 1AKx9C-0005bp-00
	for vrrp@ietf.org; Sat, 15 Nov 2003 04:55:18 -0500
Received: from dprovan1 ([192.168.24.137]) by exmail.bivio.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Fri, 14 Nov 2003 10:08:19 -0800
From: "Don Provan" <dprovan@bivio.net>
To: "'M. T. Hollinger'" <myth@ucx.lkg.dec.com>
Cc: <vrrp@ietf.org>
Subject: RE: [VRRP] newbie vrrp question
Date: Fri, 14 Nov 2003 10:08:18 -0800
Message-ID: <000c01c3aada$48cc5910$8918a8c0@corp.networkrobots.com>
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
In-Reply-To: <03cf01c3aa67$a702d540$b6308182@PORTABRAIN>
X-OriginalArrivalTime: 14 Nov 2003 18:08:19.0839 (UTC) FILETIME=[48DAB0F0:01C3AADA]
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>

Mr. Hollinger and I have been having a "spirited debate" about
this topic offline, but I don't think we need to hash over it
here. But I did want to mention that it has brought up an
interesting disagreement about what a network manager wants to
see. In a nutshell, I've been contending that a network manager
is more interested in the state of his individual components,
while Mr. Hollinger believes the network manager mainly wants
to know what services are working with individual component
status being secondary.

Anyway, I'm OK with softening the MUST NOT about responding
to non-owner VR addresses. (Since my implementation does
actually respond, it would be somewhat hypocritical for me
to not support that.) But I'd like to request that this be
accompanied by a clear statement of why it is advantageous
for non-owners to not respond and what is given up when they
do.

What? Oh, dang, you're right. OK....

I started with the explanation Bob sent out a couple of weeks ago
in response to the original question, reworded and expanded it a
little to come up with this as an initial proposal:

"Master routers that do not own the VR address SHOULD NOT accept
packets addressed to the IP address of the owner. This makes it easier
to detect that one of the routers is down. Historically, redundancy
protocols that did not have the behavior have made it difficult for
network management systems detect that one of the routers had failed
because the IP address still responded to pings, SNMP queries, etc.
Routing protocols can also be confused if an address jumps from one
physical router to another. The desired behavior when one of the
routers fails is to have user traffic keep flowing, but to have all
network management bells start ringing.

"A router which respond to VR addresses they do not own make it
easier for end nodes to discover whether the routing service is
available, but at the expense of being able to discover the state
of the individual components."

Alas, the documents don't really leave a good place for this to
be added, so I'll leave that to people with more experience at
spec layout.

-don

> -----Original Message-----
> From: vrrp-admin@ietf.org [mailto:vrrp-admin@ietf.org]On
> Behalf Of M. T.
> Hollinger
> Sent: Thursday, November 13, 2003 8:27 PM
> To: vrrp@ietf.org
> Subject: Re: [VRRP] newbie vrrp question
>
>
> At today's meeting, we discussed this thread and, I believe,
> achieved a
> resolution.  Still, since I'd already written up a paragraph further
> explaining why I think routers should accept and respond to
> packets like
> pings (er, ICMP ECHO_REQUESTs) even if they don't have
> priority 255, here it
> is:
>
> I think it's presumptuous for us to assume that the network
> administrator
> will want alarms going off the entire time the "IPv6 address owner" is
> unavailable.  VRRP provides 255 priorities, suggesting that
> there might be
> more than one Backup Router available for a single VRID.
> Since there may be
> several BR's available, and it may take several days to get
> the main router
> back online after a hardware failure, I believe the current
> Master should go
> ahead and respond to pings.  Also, it should respond to SNMP
> queries because
> the person wishing to query the router may know only the IPv6
> address of the
> virtual router.  If the current Master is not the "address
> owner", it could
> take a lot of work to figure out the non-VRRP link-local
> address of the
> Master.
>
> Today, Bob Hinden (the document author) commented that he has seen
> implementations which do respond, and it doesn't seem to
> break VRRP.  I
> expect this behavior in some implementations will be a configuration
> parameter.  There seemed to be consensus to weaken the "MUST
> NOT" language
> in the current draft, and Bob agreed to update the next
> revision of the
> draft to reflect that decision.
>
>             - M
>
>
> _______________________________________________
> vrrp mailing list
> vrrp@ietf.org
> https://www1.ietf.org/mailman/listinfo/vrrp



_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Mon Nov 17 02:13:33 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03033
	for <vrrp-archive@odin.ietf.org>; Mon, 17 Nov 2003 02:13:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALdZR-0001he-VK
	for vrrp-archive@odin.ietf.org; Mon, 17 Nov 2003 02:13:14 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAH7DDU3006534
	for vrrp-archive@odin.ietf.org; Mon, 17 Nov 2003 02:13:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALdZR-0001hJ-3h
	for vrrp-web-archive@optimus.ietf.org; Mon, 17 Nov 2003 02:13:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02971
	for <vrrp-web-archive@ietf.org>; Mon, 17 Nov 2003 02:13:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALdZN-0002RT-00
	for vrrp-web-archive@ietf.org; Mon, 17 Nov 2003 02:13:09 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALdZN-0002RP-00
	for vrrp-web-archive@ietf.org; Mon, 17 Nov 2003 02:13:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALdZF-0001g7-Ac; Mon, 17 Nov 2003 02:13:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALdYo-0001da-Ig
	for vrrp@optimus.ietf.org; Mon, 17 Nov 2003 02:12:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02901
	for <vrrp@ietf.org>; Mon, 17 Nov 2003 02:12:21 -0500 (EST)
From: Kalyan.Tata@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALdYk-0002RG-00
	for vrrp@ietf.org; Mon, 17 Nov 2003 02:12:30 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALdYk-0002RB-00
	for vrrp@ietf.org; Mon, 17 Nov 2003 02:12:30 -0500
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hAH7CUA24347
	for <vrrp@ietf.org>; Mon, 17 Nov 2003 09:12:30 +0200 (EET)
Received: from daebh002.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65f55f24f4ac158f25078@esvir05nok.ntc.nokia.com>;
 Mon, 17 Nov 2003 09:12:30 +0200
Received: from mvebe001.NOE.Nokia.com ([172.18.140.37]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Mon, 17 Nov 2003 01:12:28 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [VRRP] VRRP MIB
Date: Sun, 16 Nov 2003 23:12:27 -0800
Message-ID: <4D7B558499107545BB45044C63822DDE03873C18@mvebe001.americas.nokia.com>
Thread-Topic: [VRRP] VRRP MIB
Thread-Index: AcOqPLaCGWpSpwhjTVmdk58r6qqkdwCZUFOA
To: <bwijnen@lucent.com>, <vrrp@ietf.org>, <dthaler@windows.microsoft.com>
X-OriginalArrivalTime: 17 Nov 2003 07:12:28.0270 (UTC) FILETIME=[28BB08E0:01C3ACDA]
Content-Transfer-Encoding: quoted-printable
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi I want to first thank Bert and Dave for taking time to review the IDs =

and guide us in the right direction with regard to this MIB.

Bert, Yes I was wrong in saying that "..loss of backward compatibility =
..."
As you mentioned we will be deprecating the existing mib compliance and =
adding
new compliance, old implementations will refer to deprecated compliance =
which
is not same as "not compatible".

Regarding the change of indexing for the vrrpOperTable, we need to =20
defining a new table called "vrrpUniOperTable" anyway.
we can change the indexing of this new table to (vrID,ifIndex)

The only problem is with vrrpRouterStatsTable, I was initially thinking =
of=20
keeping the existing table and adding IPv6 specific stats at the end. If =
we=20
think that the indexing should change, then the best way to go about is =
to=20
deprecate the existing table and define a new statistics table with =
changed=20
indexing. I think we should go with this (new table) approach and keep =
the=20
indexing consistent in both the tables as (vrID, ifIndex).

This pretty much means that will be redefining all the tables. :)=20

If any one has any reason to oppose change in the order of indexing from =
(ifIndex,vrID)=20
to (vrID, ifIndex) please let us know (The order will be changed in new =
tables not=20
existing tables).=20

thanks
kalyan

-----Original Message-----
From: vrrp-admin@ietf.org [mailto:vrrp-admin@ietf.org]On Behalf Of ext
Wijnen, Bert (Bert)
Sent: 13 November, 2003 15:18
To: vrrp@ietf.org
Subject: RE: [VRRP] VRRP MIB


Posting what I stated at the session this morning.

Mmm... they could accomodate existing implementations with
the current COMPLIANCE statement depreacted, no?

I forget what would cause complete incompatibility for
exisiting old implementations?

So unless you can refresh my memory, I am inclinde to=20
respond:

Kalyan writes:

> hi,
> =A0=A0 I had a couple of personal discussions with various SNMP=20
>    and MIB experts and the=20
> =A0=A0 consensus is that we should go with a unified VRRP MIB. I=20
>    am planning to=20
> =A0=A0 propose going with the unified MIB at the WG meeting.
> =A0=A0 As you are aware - Unified VRRP MIB means that existing=20
>    implementations will=20
> =A0=A0 have to change. I would strongly suggest any one having=20
>    concerns with this=20
> =A0=A0 approach to voice their opinion either in the mailing list=20
>    or at the working  group meeting.=20
>=20
> 	One of the reasons against a unified MIB is the loss of=20
>     backward compatibility with the existing VRRP
>     MIB implementation.

I think that if you properly deprecate objects and add new ones and
then properly define the MODULE-COMPLIANCE statements, that we can
in fact allow for backward compatibility for old existing=20
implementations. They would claim compliance with a deprecated
MODULE COMPLIANCE. Or so I think.=20

But the changes are big enough that if you want to go to the new
unified approach, which potentially changes indexing), then such
a change probably has a serious impact

>     Could everyone having an existing VRRP MIB implementation
>     respond so that we will have an idea of how many=20
>     implementations are present.
>=20

That would be good to know.

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Tue Nov 18 14:40:34 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09375
	for <vrrp-archive@odin.ietf.org>; Tue, 18 Nov 2003 14:40:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMBhv-0002Ih-Tp
	for vrrp-archive@odin.ietf.org; Tue, 18 Nov 2003 14:40:16 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAIJeFUE008837
	for vrrp-archive@odin.ietf.org; Tue, 18 Nov 2003 14:40:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMBhu-0002IS-K7
	for vrrp-web-archive@optimus.ietf.org; Tue, 18 Nov 2003 14:40:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09338
	for <vrrp-web-archive@ietf.org>; Tue, 18 Nov 2003 14:40:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMBhr-00044G-00
	for vrrp-web-archive@ietf.org; Tue, 18 Nov 2003 14:40:11 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMBhr-00044C-00
	for vrrp-web-archive@ietf.org; Tue, 18 Nov 2003 14:40:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMBhj-0002He-0v; Tue, 18 Nov 2003 14:40:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMBgu-0002GG-7S
	for vrrp@optimus.ietf.org; Tue, 18 Nov 2003 14:39:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09292
	for <vrrp@ietf.org>; Tue, 18 Nov 2003 14:38:59 -0500 (EST)
From: Mukesh.Gupta@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMBgr-00043J-00
	for vrrp@ietf.org; Tue, 18 Nov 2003 14:39:09 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMBgq-00043G-00
	for vrrp@ietf.org; Tue, 18 Nov 2003 14:39:08 -0500
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hAIJd8A17758
	for <vrrp@ietf.org>; Tue, 18 Nov 2003 21:39:08 +0200 (EET)
Received: from daebh002.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65fd310f18ac158f25127@esvir05nok.ntc.nokia.com>;
 Tue, 18 Nov 2003 21:39:07 +0200
Received: from daebe009.NOE.Nokia.com ([10.241.35.109]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Tue, 18 Nov 2003 13:38:47 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 18 Nov 2003 13:38:28 -0600
Message-ID: <8D260779A766FB4A9C1739A476F84FA42ABE02@daebe009.americas.nokia.com>
Thread-Topic: [VRRP] VRRP MIB
Thread-Index: AcOqPLaCGWpSpwhjTVmdk58r6qqkdwCZUFOAAFi98kA=
To: <Kalyan.Tata@nokia.com>
Cc: <vrrp@ietf.org>, <bwijnen@lucent.com>, <dthaler@windows.microsoft.com>
X-OriginalArrivalTime: 18 Nov 2003 19:38:47.0263 (UTC) FILETIME=[9580DEF0:01C3AE0B]
Content-Transfer-Encoding: quoted-printable
Subject: [VRRP] Comments on draft-ietf-vrrp-unified-mib-00.txt
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi Kalyan,

Here are my comments for the unified draft:

- The document should consistently use VRRP for IPv4 and=20
  VRRP for IPv6 instead of VRRPv2 and VRRPv3.

- The document has RFC editor note at some places but some
  places don't have it and it is needed. Please make it consistent.

- Do we need section 2 (Revision History) ? Is anyone else doing
  this ?? If yes, an extra space before the section title should
  be removed.

- The MAX-ACCESS for vrrpOperVrId should be read-only. Right ??

- We are deprecating vrrpNodeVersion but I don't see a new version
  number object anywhere. Did I miss it ??

- Why are we specifying the SYNTAX of vrrpOperPriority and=20
  vrrpOperIpAddrCount as Integer32 and not just Integer ??

- Should we specify the value of vrrpOperPrimaryAddrType,=20
  vrrpOperPrimaryIpAddr, vrrpAssoIpAddrTable and vrrpAssoIpAddrEntry
  objects for VRRP for IPv6 ??

- If we change the vrrpOperAdvertisementInterval to microseconds=20
  just for VRRP for IPv6, how are we going to accomodate that in=20
  the MIB ??

- The description of the object vrrpAssoIpAddrType is wrong.

- Is it possible to keep all the Auth related objects in the=20
  vrrpRouterStatsEntry table together ??

- Don't deprecate vrrpStatsAuthTypeMismatch for VRRP for IPv4.

- I think, we don't need HopLimitError and TtlErrors separately.
  Merging them with a good description would be a good idea.

- Do we need "Discontinuities in the value...." paragraph for
  vrrpStatsDiscontinuityTime and vrrpStatsRefreshRate ??

- Section 9 says "Added ifindex and vrrpOperVrId to=20
  vrrpTrapNewMaster but I don't see them in the definition
  of vrrpTrapNewMaster.

- Do we need section 10 here ?? Are there IPRs for the MIB ??

Nits:
- The expiry date needs to be corrected. I think, the word=20
  macro is messed up because both the drafts have this problem.
- The author names in the top header should have capital=20
  case K.
- "VRRPv3" in the title has small case "p".
- The header on each page should have capital K in "Karlekar"
- "obsoletes" is mis-spelled in the abstract
- Extra space after Protocol in "... employ the Virtual Router=20
  Redundancy Protocol  for both..." in abstract.
- Section 1: Paragraph 1: space needed before RFC in "section
  7 ofRFC 3410..."
- An extra space before the section 2 title should be removed.
- Authors' addresses need to be corrected.
	0 Fairchild is one word
	0 Phone number format should be consistent
	0 Zip code in Kripakaran's address should be 94043
- Format the section 11 properly.

I am getting tired of typing all the small nits. I will convey
them to you in a phone call :)

Regards
Mukesh

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Wed Nov 19 04:41:58 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10274
	for <vrrp-archive@odin.ietf.org>; Wed, 19 Nov 2003 04:41:58 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMOqA-0006mJ-HV
	for vrrp-archive@odin.ietf.org; Wed, 19 Nov 2003 04:41:41 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJ9fZpe026044
	for vrrp-archive@odin.ietf.org; Wed, 19 Nov 2003 04:41:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMOq3-0006ly-0D
	for vrrp-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 04:41:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10262
	for <vrrp-web-archive@ietf.org>; Wed, 19 Nov 2003 04:41:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMOpz-0003nN-00
	for vrrp-web-archive@ietf.org; Wed, 19 Nov 2003 04:41:27 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMOpz-0003nK-00
	for vrrp-web-archive@ietf.org; Wed, 19 Nov 2003 04:41:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMOpo-0006lL-J0; Wed, 19 Nov 2003 04:41:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMOor-0006fo-Ci
	for vrrp@optimus.ietf.org; Wed, 19 Nov 2003 04:40:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10242
	for <vrrp@ietf.org>; Wed, 19 Nov 2003 04:40:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMOon-0003ml-00
	for vrrp@ietf.org; Wed, 19 Nov 2003 04:40:13 -0500
Received: from [203.197.140.35] (helo=fsnt.future.futsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMOom-0003m4-00
	for vrrp@ietf.org; Wed, 19 Nov 2003 04:40:12 -0500
Received: from kailash.future.futsoft.com (unverified [203.197.140.36]) by 
    fsnt.future.futsoft.com (Content Technologies SMTPRS 4.3.6) with ESMTP id 
    <T6600f7a225cbc58c23598@fsnt.future.futsoft.com> for <vrrp@ietf.org>; Wed
    , 19 Nov 2003 15:14:53 +0530
Received: from gunav (gunav.future.futsoft.com [10.6.4.36]) by 
    kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id hAJ9dZ327499 for 
    <vrrp@ietf.org>; Wed, 19 Nov 2003 15:09:35 +0530
Reply-To: <gunav@future.futsoft.com>
From: "Gunaseelan V" <gunav@future.futsoft.com>
To: <vrrp@ietf.org>
Date: Wed, 19 Nov 2003 15:10:50 +0530
Message-ID: <001a01c3ae81$38671600$2404060a@future.futsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [VRRP] Query on Load sharing using VRRP
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Dear Gurus
I need a small clarification on the method of load sharing using 2 Virtual
routers ,

consider a case where  2 virtual routers are configured to share the load of
a LAN segment, so there will be 2 VRIDs in a single interface and both
routers will Act as Master for a single VRID and backup for the other,
accordingly the hosts will be grouped in to two , one group having VRID1's
IP address  as gwy and the other with VRID2's IP address.

My doubt in only forwarding the packets to hosts from the WAN side.

If both routers are alive then its ok, each will have to handle only one
VRID and forwarding packets will be sent with that Virtual Mac address,
incase if one of the Router goes off, then only single Router will be
available and it has to act as Master for Both VRID,

Now how it will forward packets to hosts, means with what MAC address it
will send ?

Are there any way of classifying Hosts' IP address of to VRIDs , Need some
help in this reg

Also pl hint me what type of support is needed from IP like Aliasing,
multinetting etc

Thanks in Advance

Best Regards
Gunaseelan V



***************************************************************************
This message is proprietary to Future Software Limited (FSL)
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information
and should not be circulated or used for any purpose other than for
what it is intended.

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message.
FSL accepts no responsibility for loss or damage arising from
the use of the information transmitted by this email including
damage from virus.
***************************************************************************


_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Wed Nov 19 14:21:27 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04947
	for <vrrp-archive@odin.ietf.org>; Wed, 19 Nov 2003 14:21:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMXsy-0000uF-45
	for vrrp-archive@odin.ietf.org; Wed, 19 Nov 2003 14:21:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJJL8fh003482
	for vrrp-archive@odin.ietf.org; Wed, 19 Nov 2003 14:21:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMXsy-0000tw-0D
	for vrrp-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 14:21:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04924
	for <vrrp-web-archive@ietf.org>; Wed, 19 Nov 2003 14:20:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMXst-0007bi-00
	for vrrp-web-archive@ietf.org; Wed, 19 Nov 2003 14:21:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMXst-0007bd-00
	for vrrp-web-archive@ietf.org; Wed, 19 Nov 2003 14:21:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMXss-0000si-5l; Wed, 19 Nov 2003 14:21:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMXsc-0000rm-4D
	for vrrp@optimus.ietf.org; Wed, 19 Nov 2003 14:20:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04902
	for <vrrp@ietf.org>; Wed, 19 Nov 2003 14:20:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMXsZ-0007b9-00
	for vrrp@ietf.org; Wed, 19 Nov 2003 14:20:43 -0500
Received: from nwkea-mail-1.sun.com ([192.18.42.13])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMXsY-0007Zo-00
	for vrrp@ietf.org; Wed, 19 Nov 2003 14:20:42 -0500
Received: from phys-bur1-1 ([129.148.13.15])
	by nwkea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id hAJJKBUR008171
	for <vrrp@ietf.org>; Wed, 19 Nov 2003 11:20:12 -0800 (PST)
Received: from bur-mail2.east.sun.com (bur-mail2 [129.148.13.31])
 by bur-mail2.east.sun.com
 (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
 with ESMTP id <0HOM00AHA5PNP1@bur-mail2.east.sun.com> for vrrp@ietf.org; Wed,
 19 Nov 2003 14:20:11 -0500 (EST)
Received: from [129.148.9.42] by bur-mail2.east.sun.com (mshttpd); Wed,
 19 Nov 2003 11:20:11 -0800
Date: Wed, 19 Nov 2003 11:20:11 -0800
From: Radia Perlman <Radia.Perlman@Sun.COM>
Subject: Re: [VRRP] Query on Load sharing using VRRP
To: gunav@future.futsoft.com
Cc: vrrp@ietf.org
Message-id: <23a61239ab.239ab23a61@bur-mail2.east.sun.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.16 (built May 14 2003)
Content-type: text/plain; charset=us-ascii
Content-language: en
Content-transfer-encoding: 7bit
Content-disposition: inline
X-Accept-Language: en
Priority: normal
Content-Transfer-Encoding: 7bit
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Re: Gunaseelan V's msg

I think you've raised more than one issue.

I think one thing you were asking is if you
have two VRs, A and B, and host H1 is using A
and host H2 is using B, then obviously off-LAN
traffic from H1 goes through router A and
off-LAN traffic from H2 goes through router B.
I think you're asking about traffic from the
WAN to the LAN. In that case it's irrelevant
which VRID the endnode is configured with.
Whichever router receives the packet from the WAN
will forward it directly to the endnode.

So now:

issue 1: What MAC address should A use when
forwarding a data packet from off-LAN to on-LAN.
I think
   a) it doesn't matter, so for instance it could
      use its own physical MAC address. I think
      it doesn't matter because endnodes don't
      do reverse learning (refresh their ARP
      cache based on seeing the source layer 2
      address in received data packets)
   b) the spec doesn't say
If I'm right about b), then the spec ought to
say something about it. If I'm right about a) then
it can pick anything (its own MAC address or the
VMAC address). If I'm wrong, and it matters, then
the spec should say whatever works.

As for what you said here:
> Are there any way of classifying Hosts' IP address of to VRIDs , 
> Need some
> help in this reg
> 
> Also pl hint me what type of support is needed from IP like Aliasing,
> multinetting etc

I can't quite parse it, so I'll let someone
else comment.

Radia



_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Thu Nov 20 06:36:23 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29442
	for <vrrp-archive@odin.ietf.org>; Thu, 20 Nov 2003 06:36:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMn6V-0001Rk-BQ
	for vrrp-archive@odin.ietf.org; Thu, 20 Nov 2003 06:36:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAKBa7Ix005560
	for vrrp-archive@odin.ietf.org; Thu, 20 Nov 2003 06:36:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMn6V-0001Rb-7l
	for vrrp-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 06:36:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29427
	for <vrrp-web-archive@ietf.org>; Thu, 20 Nov 2003 06:35:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMn6R-00011w-00
	for vrrp-web-archive@ietf.org; Thu, 20 Nov 2003 06:36:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMn6R-00011s-00
	for vrrp-web-archive@ietf.org; Thu, 20 Nov 2003 06:36:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMn6P-0001Qz-Kr; Thu, 20 Nov 2003 06:36:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMn5Z-0001OU-3K
	for vrrp@optimus.ietf.org; Thu, 20 Nov 2003 06:35:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29376
	for <vrrp@ietf.org>; Thu, 20 Nov 2003 06:34:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMn5V-00011H-00
	for vrrp@ietf.org; Thu, 20 Nov 2003 06:35:05 -0500
Received: from [203.197.140.35] (helo=fsnt.future.futsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMn5U-00010u-00
	for vrrp@ietf.org; Thu, 20 Nov 2003 06:35:05 -0500
Received: from kailash.future.futsoft.com (unverified [203.197.140.36]) by 
    fsnt.future.futsoft.com (Content Technologies SMTPRS 4.3.6) with ESMTP id 
    <T6606872362cbc58c234c0@fsnt.future.futsoft.com>; Thu, 20 Nov 2003 
    17:09:43 +0530
Received: from gunav (gunav.future.futsoft.com [10.6.4.36]) by 
    kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id hAKBYF326751; Thu
    , 20 Nov 2003 17:04:15 +0530
Reply-To: <gunav@future.futsoft.com>
From: "Gunaseelan V" <gunav@future.futsoft.com>
To: "'Don Provan'" <dprovan@bivio.net>,
        "'Radia Perlman'" 
    <Radia.Perlman@Sun.COM>
Cc: <vrrp@ietf.org>
Subject: RE: [VRRP] Query on Load sharing using VRRP
Date: Thu, 20 Nov 2003 17:05:32 +0530
Message-ID: <001601c3af5a$6954fa00$2404060a@future.futsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
In-Reply-To: <001701c3aed8$c6f41600$8918a8c0@corp.networkrobots.com>
Content-Transfer-Encoding: 7bit
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Thanks Don and Radia
Now I got the concept that VR MAC address to be used only in case of VRRP
packets, and other IP packets can be sent with either VMAC or physical Mac
address.

But does this cause any issues if we use the L2 switch/Bridge in the LAN
side of the Virtual Router, that learning of 2 diff Mac address for same
port/Router, Here I suppose this will cause only additional entires in the
Switch but no harm, am I correct.

I feel its not mentioned in the Spec , is there a way to include such
modifications also


Best Regards
Gunaseelan V


-----Original Message-----
From: Don Provan [mailto:dprovan@bivio.net]
Sent: Thursday, 20 November 2003 1:38 AM
To: 'Radia Perlman'; gunav@future.futsoft.com
Cc: vrrp@ietf.org
Subject: RE: [VRRP] Query on Load sharing using VRRP


As far as I can tell, the answer is that "the spec
doesn't say". I interpret this to mean that the spec
considers the question outside it's domain, so the
router should forward the traffic just as it does
without VRRP, which is using it's physical MAC
address as the source. I also claim that this is
the correct answer because the source MAC address
should unambiguously identify the local transmitter.

But I agree that the spec really should spell this
out. The question's come up a few times, and I also
remember spending quite a while puzzling out the
answer myself when I started. Now I consider it
obvious that only VRRP packets should use the
VR MAC address as the source, but I forget that the
spec never actually says that.
-don

> -----Original Message-----
> From: vrrp-admin@ietf.org [mailto:vrrp-admin@ietf.org]On
> Behalf Of Radia
> Perlman
> Sent: Wednesday, November 19, 2003 11:20 AM
> To: gunav@future.futsoft.com
> Cc: vrrp@ietf.org
> Subject: Re: [VRRP] Query on Load sharing using VRRP
>
>
> Re: Gunaseelan V's msg
>
> I think you've raised more than one issue.
>
> I think one thing you were asking is if you
> have two VRs, A and B, and host H1 is using A
> and host H2 is using B, then obviously off-LAN
> traffic from H1 goes through router A and
> off-LAN traffic from H2 goes through router B.
> I think you're asking about traffic from the
> WAN to the LAN. In that case it's irrelevant
> which VRID the endnode is configured with.
> Whichever router receives the packet from the WAN
> will forward it directly to the endnode.
>
> So now:
>
> issue 1: What MAC address should A use when
> forwarding a data packet from off-LAN to on-LAN.
> I think
>    a) it doesn't matter, so for instance it could
>       use its own physical MAC address. I think
>       it doesn't matter because endnodes don't
>       do reverse learning (refresh their ARP
>       cache based on seeing the source layer 2
>       address in received data packets)
>    b) the spec doesn't say
> If I'm right about b), then the spec ought to
> say something about it. If I'm right about a) then
> it can pick anything (its own MAC address or the
> VMAC address). If I'm wrong, and it matters, then
> the spec should say whatever works.
>
> As for what you said here:
> > Are there any way of classifying Hosts' IP address of to VRIDs ,
> > Need some
> > help in this reg
> >
> > Also pl hint me what type of support is needed from IP like
> Aliasing,
> > multinetting etc
>
> I can't quite parse it, so I'll let someone
> else comment.
>
> Radia
>
>
>
> _______________________________________________
> vrrp mailing list
> vrrp@ietf.org
> https://www1.ietf.org/mailman/listinfo/vrrp




***************************************************************************
This message is proprietary to Future Software Limited (FSL)
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information
and should not be circulated or used for any purpose other than for
what it is intended.

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message.
FSL accepts no responsibility for loss or damage arising from
the use of the information transmitted by this email including
damage from virus.
***************************************************************************


_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Thu Nov 20 13:21:26 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17059
	for <vrrp-archive@odin.ietf.org>; Thu, 20 Nov 2003 13:21:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMtQU-0006p5-Hc
	for vrrp-archive@odin.ietf.org; Thu, 20 Nov 2003 13:21:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAKILA8M026224
	for vrrp-archive@odin.ietf.org; Thu, 20 Nov 2003 13:21:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMtQU-0006ot-8c
	for vrrp-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 13:21:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17047
	for <vrrp-web-archive@ietf.org>; Thu, 20 Nov 2003 13:20:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMtQS-0007eH-00
	for vrrp-web-archive@ietf.org; Thu, 20 Nov 2003 13:21:08 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMtQR-0007eE-00
	for vrrp-web-archive@ietf.org; Thu, 20 Nov 2003 13:21:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMtQM-0006o7-1Z; Thu, 20 Nov 2003 13:21:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMtPW-0006mw-0h
	for vrrp@optimus.ietf.org; Thu, 20 Nov 2003 13:20:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16991
	for <vrrp@ietf.org>; Thu, 20 Nov 2003 13:19:55 -0500 (EST)
From: Mukesh.Gupta@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMtPT-0007dL-00
	for vrrp@ietf.org; Thu, 20 Nov 2003 13:20:07 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMtPT-0007dH-00
	for vrrp@ietf.org; Thu, 20 Nov 2003 13:20:07 -0500
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hAKIK6A17022
	for <vrrp@ietf.org>; Thu, 20 Nov 2003 20:20:06 +0200 (EET)
Received: from daebh001.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6607356b88ac158f21082@esvir01nok.ntc.nokia.com> for <vrrp@ietf.org>;
 Thu, 20 Nov 2003 20:20:05 +0200
Received: from daebe009.NOE.Nokia.com ([10.241.35.109]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Thu, 20 Nov 2003 10:19:20 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 20 Nov 2003 12:19:20 -0600
Message-ID: <8D260779A766FB4A9C1739A476F84FA42ABE06@daebe009.americas.nokia.com>
Thread-Topic: Minutes from IETF58th
Thread-Index: AcOvktBEIGiecAGxTsGfv+B7S6qMmg==
To: <vrrp@ietf.org>
X-OriginalArrivalTime: 20 Nov 2003 18:19:20.0887 (UTC) FILETIME=[D1591C70:01C3AF92]
Content-Transfer-Encoding: quoted-printable
Subject: [VRRP] Minutes from IETF58th
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Group,

Thanks to Karen for preparing good meeting minutes.

Let me know if anyone has any comments/correction.
I will submit the minutes for the proceedings on
Monday, 24th Nov.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
Virtual Router Redundancy Protocol WG (vrrp)
Thursday, November 13, 2003 at 0900-1130 in Rochester Room

Chairs:=09
Mukesh Gupta Mukesh.Gupta@nokia.com
Radia Perlman radia.perlman@sun.com

Minutes taken by Karen O'Donoghue.

The chairs provided a proposed agenda as follows:
Introduction and Review Agenda
VRRP MIB
Milestones/Plans
Current Drafts' status
VMACs vs ND
CARP (Common Address Redundancy Protocol)
Miscellaneous Issues

A discussion of the appropriate approach for the VRRP MIB was led=20
by Kalyan Tata. He presented a summary of the arguments for maintaining=20
a separate MIB for IPv4 and IPv6 or for merging the two MIBs into a=20
single unified MIB for both. Bert Wijnen clarified a misunderstanding=20
on the part of the working group on the meaning of deprecation and the=20
impact on backward compatibility. The consensus of the room was to=20
pursue the unified MIB approach.=20

Mukesh Gupta discussed the current status of the working group efforts=20
including milestones and current drafts. A revised list of milestones=20
based on slight delays in current efforts was presented. VRRPv2 (for=20
IPv4) is in the IESG review process with some minor clarifications being =

completed. VRRPv3 (for IPv6) needs to resolve the VMAC versus ND issue.=20
The VRRP MIB draft needs resolution of the separated versus unified MIB=20
approaches. With the completion of these remaining work items, the=20
working group needs to consider where to go next.=20

Mark Hollinger led a discussion of the issue of Neighbor Discovery (ND)=20
versus Virtual  MAC (VMAC) for VRRPv3. He discussed the historical =
context=20
of the use of VMAC. He also presented the advantages and disadvantages =
for=20
using VMAC. A number of scenarios were presented along with the =
performance=20
of VMAC in each scenario. Finally, a summary list of changes were =
proposed=20
for the incorporation of ND into VRRPv3. Radia Perlman asked the room =
who=20
wanted VMAC removed and who wanted ND used instead. Bob Hinden pointed =
out=20
that a proper evaluation of the ND approach could not be without seeing=20
the actual modifications to the document. Bob Hinden and Mark Hollinger=20
agreed to discuss the details offline. A decision can only be made once =
a=20
concrete proposal is on the table.=20

Jun-ihiro itojun Hagino from the OpenBSD community presented the common=20
address redundancy protocol (CARP). Points of contact for the effort=20
include mcbride@openbsd and deraadt@openbs.org. The goal of the CARP=20
effort is to have a protocol in this problem space that is completely=20
patent-free. The CARP community has evaluated VRRP and believes both =
VRRP=20
and CARP do not infringe on any HSRP claims. Bob Hinden questioned the=20
validity of this analysis and whether or not Cisco would agree with that =

analysis. The primary technical differences between CARP and VRRP were=20
summarized. The discussion evolved back to the topic of patents. Scott=20
Bradner expressed a concern about the CARP community not having =
discussed=20
their analysis with Cisco. Bob Hinden questioned the mechanics of the=20
reliability mechanism used by CARP. The conclusion of the discussion was =

that an internet-draft needs to be prepared in order to seriously =
consider=20
CARP in the context of this working group.=20

The chairs asked if there were any additional topics from the floor. =
Mark=20
Hollinger asked about the status of the subsecond work discussed at the=20
Vienna IETF. Karen O'Donoghue admitted that she had not completed the=20
draft on this issue in time for the draft cutoff. The routing AD =
indicated=20
that the BFD (bi-directional forwarding) work being discussed in the =
routing=20
area should be considered here as well. The routing AD agreed to forward =
the=20
BFD material to the VRRP WG.

The meeting was adjourned.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Wed Nov 26 21:17:25 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09047
	for <vrrp-archive@odin.ietf.org>; Wed, 26 Nov 2003 21:17:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1APBiP-0004Lc-HC
	for vrrp-archive@odin.ietf.org; Wed, 26 Nov 2003 21:17:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAR2H9OG016708
	for vrrp-archive@odin.ietf.org; Wed, 26 Nov 2003 21:17:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1APBiP-0004LP-B4
	for vrrp-web-archive@optimus.ietf.org; Wed, 26 Nov 2003 21:17:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09031
	for <vrrp-web-archive@ietf.org>; Wed, 26 Nov 2003 21:16:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1APBiM-00011n-00
	for vrrp-web-archive@ietf.org; Wed, 26 Nov 2003 21:17:06 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1APBiM-00011j-00
	for vrrp-web-archive@ietf.org; Wed, 26 Nov 2003 21:17:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1APBiH-0004Kr-1n; Wed, 26 Nov 2003 21:17:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1APBhw-0004Kg-Kx
	for vrrp@optimus.ietf.org; Wed, 26 Nov 2003 21:16:40 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09021
	for <vrrp@ietf.org>; Wed, 26 Nov 2003 21:16:26 -0500 (EST)
From: Mukesh.Gupta@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1APBht-00010C-00
	for vrrp@ietf.org; Wed, 26 Nov 2003 21:16:37 -0500
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1APBht-000108-00
	for vrrp@ietf.org; Wed, 26 Nov 2003 21:16:37 -0500
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hAR2GZQ24380
	for <vrrp@ietf.org>; Thu, 27 Nov 2003 04:16:36 +0200 (EET)
Received: from daebh001.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6627cfd396ac158f242d7@esvir04nok.ntc.nokia.com> for <vrrp@ietf.org>;
 Thu, 27 Nov 2003 04:16:35 +0200
Received: from daebe009.NOE.Nokia.com ([10.241.35.109]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Wed, 26 Nov 2003 18:16:32 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 26 Nov 2003 20:16:32 -0600
Message-ID: <8D260779A766FB4A9C1739A476F84FA401546F94@daebe009.americas.nokia.com>
Thread-Topic: Proceedings..
Thread-Index: AcO0jHmASvhK4alxRrusWQU+szbMaQ==
To: <vrrp@ietf.org>
X-OriginalArrivalTime: 27 Nov 2003 02:16:33.0066 (UTC) FILETIME=[79EF68A0:01C3B48C]
Content-Transfer-Encoding: quoted-printable
Subject: [VRRP] Proceedings..
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Folks,

Those of you who couldn't attend the WG meeting=20
in Minneapolis, the proceedings are available at
http://www.ietf.org/proceedings/03nov/index.html

Search for VRRP on the page and you will find
the minutes and the slides for all the presentations.

Happy Thanksgiving to everyone who celebrates it.

Regards
Mukesh

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Fri Nov 28 23:23:18 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22346
	for <vrrp-archive@odin.ietf.org>; Fri, 28 Nov 2003 23:23:17 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1APwdH-0002q5-Ds
	for vrrp-archive@odin.ietf.org; Fri, 28 Nov 2003 23:23:00 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAT4MxRS010909
	for vrrp-archive@odin.ietf.org; Fri, 28 Nov 2003 23:22:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1APwdH-0002po-01
	for vrrp-web-archive@optimus.ietf.org; Fri, 28 Nov 2003 23:22:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22111
	for <vrrp-web-archive@ietf.org>; Fri, 28 Nov 2003 23:22:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1APwdE-0006fI-00
	for vrrp-web-archive@ietf.org; Fri, 28 Nov 2003 23:22:57 -0500
Received: from manatick.foretec.com ([4.17.168.5] helo=manatick)
	by ietf-mx with esmtp (Exim 4.12)
	id 1APwdD-0006f2-00
	for vrrp-web-archive@ietf.org; Fri, 28 Nov 2003 23:22:56 -0500
Received: from [132.151.6.22] (helo=optimus.ietf.org)
	by manatick with esmtp (Exim 4.24)
	id 1APwdE-00039j-Jp
	for vrrp-web-archive@ietf.org; Fri, 28 Nov 2003 23:22:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1APwcN-0002Xo-Ox; Fri, 28 Nov 2003 23:22:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1APwbQ-0002Sz-QW
	for vrrp@optimus.ietf.org; Fri, 28 Nov 2003 23:21:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21728
	for <vrrp@ietf.org>; Fri, 28 Nov 2003 23:20:49 -0500 (EST)
From: Mukesh.Gupta@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1APwbN-0006Vu-00
	for vrrp@ietf.org; Fri, 28 Nov 2003 23:21:01 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1APwbM-0006Vq-00
	for vrrp@ietf.org; Fri, 28 Nov 2003 23:21:00 -0500
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hAT4L0825864
	for <vrrp@ietf.org>; Sat, 29 Nov 2003 06:21:00 +0200 (EET)
Received: from daebh001.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T66328e720eac158f25a71@esvir05nok.ntc.nokia.com> for <vrrp@ietf.org>;
 Sat, 29 Nov 2003 06:21:00 +0200
Received: from daebe009.NOE.Nokia.com ([10.241.35.109]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Fri, 28 Nov 2003 20:20:58 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 28 Nov 2003 22:20:58 -0600
Message-ID: <8D260779A766FB4A9C1739A476F84FA42ABE13@daebe009.americas.nokia.com>
Thread-Topic: Separate MIBs or Unified MIB
Thread-Index: AcO2MC/+F781RwUlTi21NcTsiPqiag==
To: <vrrp@ietf.org>
X-OriginalArrivalTime: 29 Nov 2003 04:20:59.0101 (UTC) FILETIME=[30DD70D0:01C3B630]
Content-Transfer-Encoding: quoted-printable
Subject: [VRRP] Separate MIBs or Unified MIB
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Folks,

As you would have read in the meeting minutes, the consensus=20
of the room in the meeting was to go forward with a unified=20
MIB for VRRP. (One MIB describing both VRRP for IPv4 and VRRP=20
for IPv6).

We would like to confirm this on the list.

So please reply and raise your objections if you think that=20
the separate MIBs will be better than the unified MIB.

If we don't hear anything from anyone within a week, we would=20
assume that everyone will prefer a unified MIB.

Regards
Mukesh

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Sat Nov 29 14:50:25 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24685
	for <vrrp-archive@odin.ietf.org>; Sat, 29 Nov 2003 14:50:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQB6Y-0007Ui-5D
	for vrrp-archive@odin.ietf.org; Sat, 29 Nov 2003 14:50:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hATJoAXr028802
	for vrrp-archive@odin.ietf.org; Sat, 29 Nov 2003 14:50:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQB6Y-0007UT-0J
	for vrrp-web-archive@optimus.ietf.org; Sat, 29 Nov 2003 14:50:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24663
	for <vrrp-web-archive@ietf.org>; Sat, 29 Nov 2003 14:49:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQB6V-0001sS-00
	for vrrp-web-archive@ietf.org; Sat, 29 Nov 2003 14:50:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQB6U-0001sP-00
	for vrrp-web-archive@ietf.org; Sat, 29 Nov 2003 14:50:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQB6Q-0007Ts-WC; Sat, 29 Nov 2003 14:50:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQB5j-0007TO-A9
	for vrrp@optimus.ietf.org; Sat, 29 Nov 2003 14:49:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24653
	for <vrrp@ietf.org>; Sat, 29 Nov 2003 14:49:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQB5g-0001s8-00
	for vrrp@ietf.org; Sat, 29 Nov 2003 14:49:16 -0500
Received: from plant.sfc.wide.ad.jp ([203.178.143.91])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQB5f-0001s5-00
	for vrrp@ietf.org; Sat, 29 Nov 2003 14:49:15 -0500
Received: from localhost (localhost [127.0.0.1])
	by plant.sfc.wide.ad.jp (Postfix) with ESMTP
	id 8892729030; Sun, 30 Nov 2003 04:49:12 +0900 (JST)
Date: Sun, 30 Nov 2003 04:49:12 +0900 (JST)
Message-Id: <20031130.044912.115670709.yasu@sfc.wide.ad.jp>
To: Mukesh.Gupta@nokia.com
Cc: vrrp@ietf.org
Subject: Re: [VRRP] Separate MIBs or Unified MIB
From: Yasuhiro Ohara <yasu@sfc.wide.ad.jp>
In-Reply-To: <8D260779A766FB4A9C1739A476F84FA42ABE13@daebe009.americas.nokia.com>
References: <8D260779A766FB4A9C1739A476F84FA42ABE13@daebe009.americas.nokia.com>
X-Mailer: Mew version 3.1 on Emacs 21.2 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Just curious, how one can retrieve specific protocol's data
(either VRRPv2 or VRRPv3) when both enabled on the target router ?

If vrrp version will be included in the object name (i.e.
"One MIB" just means that the document is one, MIB datas
are seperated but mixed in one MIB tree), that will be OK
but otherwise (e.g. the data retrieved will depend on transport
protocol family ..., I don't believe you mean this though)
it will bring operation real hard ...

regards,
yasu

From: Mukesh.Gupta@nokia.com
Subject: [VRRP] Separate MIBs or Unified MIB
Date: Fri, 28 Nov 2003 22:20:58 -0600

> Folks,
> 
> As you would have read in the meeting minutes, the consensus 
> of the room in the meeting was to go forward with a unified 
> MIB for VRRP. (One MIB describing both VRRP for IPv4 and VRRP 
> for IPv6).
> 
> We would like to confirm this on the list.
> 
> So please reply and raise your objections if you think that 
> the separate MIBs will be better than the unified MIB.
> 
> If we don't hear anything from anyone within a week, we would 
> assume that everyone will prefer a unified MIB.
> 
> Regards
> Mukesh
> 
> _______________________________________________
> vrrp mailing list
> vrrp@ietf.org
> https://www1.ietf.org/mailman/listinfo/vrrp

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Sat Nov 29 15:55:28 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26665
	for <vrrp-archive@odin.ietf.org>; Sat, 29 Nov 2003 15:55:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQC7U-0001Kk-6Y
	for vrrp-archive@odin.ietf.org; Sat, 29 Nov 2003 15:55:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hATKtCFw005127
	for vrrp-archive@odin.ietf.org; Sat, 29 Nov 2003 15:55:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQC7U-0001Kb-10
	for vrrp-web-archive@optimus.ietf.org; Sat, 29 Nov 2003 15:55:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26651
	for <vrrp-web-archive@ietf.org>; Sat, 29 Nov 2003 15:54:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQC7S-0002Qf-00
	for vrrp-web-archive@ietf.org; Sat, 29 Nov 2003 15:55:10 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQC7S-0002Qc-00
	for vrrp-web-archive@ietf.org; Sat, 29 Nov 2003 15:55:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQC7J-0001K1-TC; Sat, 29 Nov 2003 15:55:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQC7F-0001Jd-5q
	for vrrp@optimus.ietf.org; Sat, 29 Nov 2003 15:54:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26648
	for <vrrp@ietf.org>; Sat, 29 Nov 2003 15:54:42 -0500 (EST)
From: Mukesh.Gupta@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQC7D-0002QY-00
	for vrrp@ietf.org; Sat, 29 Nov 2003 15:54:55 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQC7C-0002QV-00
	for vrrp@ietf.org; Sat, 29 Nov 2003 15:54:55 -0500
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hATKss813637
	for <vrrp@ietf.org>; Sat, 29 Nov 2003 22:54:54 +0200 (EET)
Received: from daebh001.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T66361c610cac158f25a71@esvir05nok.ntc.nokia.com>;
 Sat, 29 Nov 2003 22:54:53 +0200
Received: from daebe009.NOE.Nokia.com ([10.241.35.109]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Sat, 29 Nov 2003 12:54:52 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [VRRP] Separate MIBs or Unified MIB
Date: Sat, 29 Nov 2003 14:54:51 -0600
Message-ID: <8D260779A766FB4A9C1739A476F84FA401546F98@daebe009.americas.nokia.com>
Thread-Topic: [VRRP] Separate MIBs or Unified MIB
Thread-Index: AcO2seNWkmyJJXR6ROabYOhVXSowdQACKRSQ
To: <yasu@sfc.wide.ad.jp>
Cc: <vrrp@ietf.org>
X-OriginalArrivalTime: 29 Nov 2003 20:54:52.0502 (UTC) FILETIME=[09244F60:01C3B6BB]
Content-Transfer-Encoding: quoted-printable
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Yasu,

VRID can be used as an unique identifier. A router can
run both VRRPv2 and VRRPv3 at the same time but it can't
use the same VRID for both.

So given an interface index and a VRID, you can identify
if the protocol running is VRRPv2 or VRRPv3.

Regards
Mukesh

> -----Original Message-----
> From: ext Yasuhiro Ohara [mailto:yasu@sfc.wide.ad.jp]
> Sent: Saturday, November 29, 2003 11:49 AM
> To: Gupta Mukesh (IPRG/MtView)
> Cc: vrrp@ietf.org
> Subject: Re: [VRRP] Separate MIBs or Unified MIB
>=20
>=20
>=20
> Just curious, how one can retrieve specific protocol's data
> (either VRRPv2 or VRRPv3) when both enabled on the target router ?
>=20
> If vrrp version will be included in the object name (i.e.
> "One MIB" just means that the document is one, MIB datas
> are seperated but mixed in one MIB tree), that will be OK
> but otherwise (e.g. the data retrieved will depend on transport
> protocol family ..., I don't believe you mean this though)
> it will bring operation real hard ...
>=20
> regards,
> yasu
>=20
> From: Mukesh.Gupta@nokia.com
> Subject: [VRRP] Separate MIBs or Unified MIB
> Date: Fri, 28 Nov 2003 22:20:58 -0600
>=20
> > Folks,
> >=20
> > As you would have read in the meeting minutes, the consensus=20
> > of the room in the meeting was to go forward with a unified=20
> > MIB for VRRP. (One MIB describing both VRRP for IPv4 and VRRP=20
> > for IPv6).
> >=20
> > We would like to confirm this on the list.
> >=20
> > So please reply and raise your objections if you think that=20
> > the separate MIBs will be better than the unified MIB.
> >=20
> > If we don't hear anything from anyone within a week, we would=20
> > assume that everyone will prefer a unified MIB.
> >=20
> > Regards
> > Mukesh
> >=20
> > _______________________________________________
> > vrrp mailing list
> > vrrp@ietf.org
> > https://www1.ietf.org/mailman/listinfo/vrrp
>=20

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Sat Nov 29 16:24:18 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27101
	for <vrrp-archive@odin.ietf.org>; Sat, 29 Nov 2003 16:24:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQCZP-0002Wl-Du
	for vrrp-archive@odin.ietf.org; Sat, 29 Nov 2003 16:24:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hATLO3Kb009709
	for vrrp-archive@odin.ietf.org; Sat, 29 Nov 2003 16:24:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQCZP-0002WW-AX
	for vrrp-web-archive@optimus.ietf.org; Sat, 29 Nov 2003 16:24:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27095
	for <vrrp-web-archive@ietf.org>; Sat, 29 Nov 2003 16:23:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQCZN-0002ic-00
	for vrrp-web-archive@ietf.org; Sat, 29 Nov 2003 16:24:01 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQCZM-0002iZ-00
	for vrrp-web-archive@ietf.org; Sat, 29 Nov 2003 16:24:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQCZM-0002Vy-Vk; Sat, 29 Nov 2003 16:24:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQCYi-0002Vi-2j
	for vrrp@optimus.ietf.org; Sat, 29 Nov 2003 16:23:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27086
	for <vrrp@ietf.org>; Sat, 29 Nov 2003 16:23:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQCYg-0002iR-00
	for vrrp@ietf.org; Sat, 29 Nov 2003 16:23:18 -0500
Received: from plant.sfc.wide.ad.jp ([203.178.143.91])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQCYf-0002iO-00
	for vrrp@ietf.org; Sat, 29 Nov 2003 16:23:17 -0500
Received: from localhost (localhost [127.0.0.1])
	by plant.sfc.wide.ad.jp (Postfix) with ESMTP
	id 0FCCC28CEE; Sun, 30 Nov 2003 06:23:16 +0900 (JST)
Date: Sun, 30 Nov 2003 06:23:15 +0900 (JST)
Message-Id: <20031130.062315.49398971.yasu@sfc.wide.ad.jp>
To: Mukesh.Gupta@nokia.com
Cc: vrrp@ietf.org
Subject: Re: [VRRP] Separate MIBs or Unified MIB
From: Yasuhiro Ohara <yasu@sfc.wide.ad.jp>
In-Reply-To: <8D260779A766FB4A9C1739A476F84FA401546F98@daebe009.americas.nokia.com>
References: <8D260779A766FB4A9C1739A476F84FA401546F98@daebe009.americas.nokia.com>
X-Mailer: Mew version 3.1 on Emacs 21.2 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Why ? I can't understand the problem (of using the same
VRID, say 1, for both VRRPv2 and VRRPv3 running).

I know the VMAC address will be the same. But it doesn't
matter with neither VRRP protocol transaction nor IP packet
forwarding, does it ?
Is it just the specification without any reason ?

Thanks in advance.

regards,
yasu

From: Mukesh.Gupta@nokia.com
Subject: RE: [VRRP] Separate MIBs or Unified MIB
Date: Sat, 29 Nov 2003 14:54:51 -0600

> Yasu,
> 
> VRID can be used as an unique identifier. A router can
> run both VRRPv2 and VRRPv3 at the same time but it can't
> use the same VRID for both.
> 
> So given an interface index and a VRID, you can identify
> if the protocol running is VRRPv2 or VRRPv3.
> 
> Regards
> Mukesh
> 
> > -----Original Message-----
> > From: ext Yasuhiro Ohara [mailto:yasu@sfc.wide.ad.jp]
> > Sent: Saturday, November 29, 2003 11:49 AM
> > To: Gupta Mukesh (IPRG/MtView)
> > Cc: vrrp@ietf.org
> > Subject: Re: [VRRP] Separate MIBs or Unified MIB
> > 
> > 
> > 
> > Just curious, how one can retrieve specific protocol's data
> > (either VRRPv2 or VRRPv3) when both enabled on the target router ?
> > 
> > If vrrp version will be included in the object name (i.e.
> > "One MIB" just means that the document is one, MIB datas
> > are seperated but mixed in one MIB tree), that will be OK
> > but otherwise (e.g. the data retrieved will depend on transport
> > protocol family ..., I don't believe you mean this though)
> > it will bring operation real hard ...
> > 
> > regards,
> > yasu
> > 
> > From: Mukesh.Gupta@nokia.com
> > Subject: [VRRP] Separate MIBs or Unified MIB
> > Date: Fri, 28 Nov 2003 22:20:58 -0600
> > 
> > > Folks,
> > > 
> > > As you would have read in the meeting minutes, the consensus 
> > > of the room in the meeting was to go forward with a unified 
> > > MIB for VRRP. (One MIB describing both VRRP for IPv4 and VRRP 
> > > for IPv6).
> > > 
> > > We would like to confirm this on the list.
> > > 
> > > So please reply and raise your objections if you think that 
> > > the separate MIBs will be better than the unified MIB.
> > > 
> > > If we don't hear anything from anyone within a week, we would 
> > > assume that everyone will prefer a unified MIB.
> > > 
> > > Regards
> > > Mukesh
> > > 
> > > _______________________________________________
> > > vrrp mailing list
> > > vrrp@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/vrrp
> > 
> 
> _______________________________________________
> vrrp mailing list
> vrrp@ietf.org
> https://www1.ietf.org/mailman/listinfo/vrrp

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Sat Nov 29 17:49:22 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29317
	for <vrrp-archive@odin.ietf.org>; Sat, 29 Nov 2003 17:49:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQDtj-00064A-QQ
	for vrrp-archive@odin.ietf.org; Sat, 29 Nov 2003 17:49:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hATMn7G2023312
	for vrrp-archive@odin.ietf.org; Sat, 29 Nov 2003 17:49:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQDtj-00063v-L8
	for vrrp-web-archive@optimus.ietf.org; Sat, 29 Nov 2003 17:49:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29296
	for <vrrp-web-archive@ietf.org>; Sat, 29 Nov 2003 17:48:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQDtg-0003tQ-00
	for vrrp-web-archive@ietf.org; Sat, 29 Nov 2003 17:49:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQDtg-0003tN-00
	for vrrp-web-archive@ietf.org; Sat, 29 Nov 2003 17:49:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQDtd-00063N-3s; Sat, 29 Nov 2003 17:49:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQDtU-000638-DV
	for vrrp@optimus.ietf.org; Sat, 29 Nov 2003 17:48:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29293
	for <vrrp@ietf.org>; Sat, 29 Nov 2003 17:48:35 -0500 (EST)
From: Mukesh.Gupta@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQDtR-0003tI-00
	for vrrp@ietf.org; Sat, 29 Nov 2003 17:48:49 -0500
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQDtR-0003tF-00
	for vrrp@ietf.org; Sat, 29 Nov 2003 17:48:49 -0500
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hATMmmY07961
	for <vrrp@ietf.org>; Sun, 30 Nov 2003 00:48:48 +0200 (EET)
Received: from daebh001.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T663684a950ac158f233e8@esvir03nok.nokia.com>;
 Sun, 30 Nov 2003 00:48:47 +0200
Received: from daebe009.NOE.Nokia.com ([10.241.35.109]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Sat, 29 Nov 2003 14:48:46 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [VRRP] Separate MIBs or Unified MIB
Date: Sat, 29 Nov 2003 16:48:45 -0600
Message-ID: <8D260779A766FB4A9C1739A476F84FA42ABE14@daebe009.americas.nokia.com>
Thread-Topic: [VRRP] Separate MIBs or Unified MIB
Thread-Index: AcO2vwQJ8JaUHfFCQuSw6+C0s4g6RAACZK2g
To: <yasu@sfc.wide.ad.jp>
Cc: <vrrp@ietf.org>
X-OriginalArrivalTime: 29 Nov 2003 22:48:46.0733 (UTC) FILETIME=[F2A933D0:01C3B6CA]
Content-Transfer-Encoding: quoted-printable
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Yasu,

Let say there are 2 routers A and B on the same lan running
VRRPv2 and VRRPv3. A is the Maser for VRRPv2 and B is the=20
Master for VRRPv3. If we are using the same VRID then both=20
of them will install the same VMAC address on their interfaces.=20
This will create a duplicate MAC address problem.

This is what I had in my mind before but after reading your=20
mail, I went and looked at the specs again and noticed that=20
the MAC addresses are not going to be exactly same. For VRRPv2
it will be 00-00-5E-00-01-{VRID} and for VRRPv3, it will be
00-00-5E-00-02-{VRID}. So I am not sure if I have a reason
why we couldn't use same VRIDs for both VRRPv2 and VRRPv3.

Anyone else has a reason for not using the same VRID for=20
both the protocols ??

Regards
Mukesh


> -----Original Message-----
> From: ext Yasuhiro Ohara [mailto:yasu@sfc.wide.ad.jp]
> Sent: Saturday, November 29, 2003 1:23 PM
> To: Gupta Mukesh (IPRG/MtView)
> Cc: vrrp@ietf.org
> Subject: Re: [VRRP] Separate MIBs or Unified MIB
>=20
>=20
>=20
> Why ? I can't understand the problem (of using the same
> VRID, say 1, for both VRRPv2 and VRRPv3 running).
>=20
> I know the VMAC address will be the same. But it doesn't
> matter with neither VRRP protocol transaction nor IP packet
> forwarding, does it ?
> Is it just the specification without any reason ?
>=20
> Thanks in advance.
>=20
> regards,
> yasu
>=20
> From: Mukesh.Gupta@nokia.com
> Subject: RE: [VRRP] Separate MIBs or Unified MIB
> Date: Sat, 29 Nov 2003 14:54:51 -0600
>=20
> > Yasu,
> >=20
> > VRID can be used as an unique identifier. A router can
> > run both VRRPv2 and VRRPv3 at the same time but it can't
> > use the same VRID for both.
> >=20
> > So given an interface index and a VRID, you can identify
> > if the protocol running is VRRPv2 or VRRPv3.
> >=20
> > Regards
> > Mukesh
> >=20
> > > -----Original Message-----
> > > From: ext Yasuhiro Ohara [mailto:yasu@sfc.wide.ad.jp]
> > > Sent: Saturday, November 29, 2003 11:49 AM
> > > To: Gupta Mukesh (IPRG/MtView)
> > > Cc: vrrp@ietf.org
> > > Subject: Re: [VRRP] Separate MIBs or Unified MIB
> > >=20
> > >=20
> > >=20
> > > Just curious, how one can retrieve specific protocol's data
> > > (either VRRPv2 or VRRPv3) when both enabled on the target router ?
> > >=20
> > > If vrrp version will be included in the object name (i.e.
> > > "One MIB" just means that the document is one, MIB datas
> > > are seperated but mixed in one MIB tree), that will be OK
> > > but otherwise (e.g. the data retrieved will depend on transport
> > > protocol family ..., I don't believe you mean this though)
> > > it will bring operation real hard ...
> > >=20
> > > regards,
> > > yasu
> > >=20
> > > From: Mukesh.Gupta@nokia.com
> > > Subject: [VRRP] Separate MIBs or Unified MIB
> > > Date: Fri, 28 Nov 2003 22:20:58 -0600
> > >=20
> > > > Folks,
> > > >=20
> > > > As you would have read in the meeting minutes, the consensus=20
> > > > of the room in the meeting was to go forward with a unified=20
> > > > MIB for VRRP. (One MIB describing both VRRP for IPv4 and VRRP=20
> > > > for IPv6).
> > > >=20
> > > > We would like to confirm this on the list.
> > > >=20
> > > > So please reply and raise your objections if you think that=20
> > > > the separate MIBs will be better than the unified MIB.
> > > >=20
> > > > If we don't hear anything from anyone within a week, we would=20
> > > > assume that everyone will prefer a unified MIB.
> > > >=20
> > > > Regards
> > > > Mukesh
> > > >=20
> > > > _______________________________________________
> > > > vrrp mailing list
> > > > vrrp@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/vrrp
> > >=20
> >=20
> > _______________________________________________
> > vrrp mailing list
> > vrrp@ietf.org
> > https://www1.ietf.org/mailman/listinfo/vrrp
>=20

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Sat Nov 29 18:03:18 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29561
	for <vrrp-archive@odin.ietf.org>; Sat, 29 Nov 2003 18:03:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQE7D-0006Jp-Gv
	for vrrp-archive@odin.ietf.org; Sat, 29 Nov 2003 18:03:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hATN33Mf024283
	for vrrp-archive@odin.ietf.org; Sat, 29 Nov 2003 18:03:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQE7D-0006Ja-BK
	for vrrp-web-archive@optimus.ietf.org; Sat, 29 Nov 2003 18:03:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29531
	for <vrrp-web-archive@ietf.org>; Sat, 29 Nov 2003 18:02:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQE7A-00042S-00
	for vrrp-web-archive@ietf.org; Sat, 29 Nov 2003 18:03:00 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQE7A-00042P-00
	for vrrp-web-archive@ietf.org; Sat, 29 Nov 2003 18:03:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQE7B-0006J2-8I; Sat, 29 Nov 2003 18:03:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQE6Q-0006I6-Iu
	for vrrp@optimus.ietf.org; Sat, 29 Nov 2003 18:02:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29517
	for <vrrp@ietf.org>; Sat, 29 Nov 2003 18:01:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQE6N-000427-00
	for vrrp@ietf.org; Sat, 29 Nov 2003 18:02:11 -0500
Received: from plant.sfc.wide.ad.jp ([203.178.143.91])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQE6M-000424-00
	for vrrp@ietf.org; Sat, 29 Nov 2003 18:02:11 -0500
Received: from localhost (localhost [127.0.0.1])
	by plant.sfc.wide.ad.jp (Postfix) with ESMTP
	id 0BF3D28CEE; Sun, 30 Nov 2003 08:02:08 +0900 (JST)
Date: Sun, 30 Nov 2003 08:02:07 +0900 (JST)
Message-Id: <20031130.080207.40756309.yasu@sfc.wide.ad.jp>
To: Mukesh.Gupta@nokia.com
Cc: vrrp@ietf.org
Subject: Re: [VRRP] Separate MIBs or Unified MIB
From: Yasuhiro Ohara <yasu@sfc.wide.ad.jp>
In-Reply-To: <8D260779A766FB4A9C1739A476F84FA42ABE14@daebe009.americas.nokia.com>
References: <8D260779A766FB4A9C1739A476F84FA42ABE14@daebe009.americas.nokia.com>
X-Mailer: Mew version 3.1 on Emacs 21.2 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


> Let say there are 2 routers A and B on the same lan running
> VRRPv2 and VRRPv3. A is the Maser for VRRPv2 and B is the 
> Master for VRRPv3. If we are using the same VRID then both 
> of them will install the same VMAC address on their interfaces. 
> This will create a duplicate MAC address problem.

Ah, the problem occurs in MAC address learning table in switches,
not in host's ARP/NDP table. I agree I was wrong.

> This is what I had in my mind before but after reading your 
> mail, I went and looked at the specs again and noticed that 
> the MAC addresses are not going to be exactly same. For VRRPv2
> it will be 00-00-5E-00-01-{VRID} and for VRRPv3, it will be
> 00-00-5E-00-02-{VRID}. So I am not sure if I have a reason
> why we couldn't use same VRIDs for both VRRPv2 and VRRPv3.

Glad to hear my question was not in vain, in a way ;p)

> Anyone else has a reason for not using the same VRID for 
> both the protocols ??

This is still in question ...

Anyway, thanks.

regards,
yasu



_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



