From exim@www1.ietf.org  Sat May  1 12:53:10 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01494
	for <vrrp-archive@odin.ietf.org>; Sat, 1 May 2004 12:53:10 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJxD8-0005dZ-Iq
	for vrrp-archive@odin.ietf.org; Sat, 01 May 2004 12:19:30 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i41GJU3J021666
	for vrrp-archive@odin.ietf.org; Sat, 1 May 2004 12:19:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJuju-0006yu-JT
	for vrrp-web-archive@optimus.ietf.org; Sat, 01 May 2004 09:41:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14299
	for <vrrp-web-archive@ietf.org>; Sat, 1 May 2004 09:41:08 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BJujs-00050E-Qv
	for vrrp-web-archive@ietf.org; Sat, 01 May 2004 09:41:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJuj5-0004oH-00
	for vrrp-web-archive@ietf.org; Sat, 01 May 2004 09:40:20 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJuiD-0004c4-00
	for vrrp-web-archive@ietf.org; Sat, 01 May 2004 09:39:25 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJu8u-0001HQ-Is
	for vrrp-web-archive@ietf.org; Sat, 01 May 2004 09:02:56 -0400
Date: Sat, 01 May 2004 09:02:56 -0400
Message-ID: <20040501130256.27207.22182.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: vrrp-web-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: mailman-admin@ietf.org
Errors-To: mailman-admin@ietf.org
X-BeenThere: mailman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, vrrp-request@ietf.org) containing just the word
'help' in the message body, and an email message will be sent to you
with instructions.

***************************************************************************


                              Note Well

All statements related to the activities of the IETF and addressed to
the IETF are subject to all provisions of Section 10 of RFC 2026,
which grants to the IETF and its participants certain licenses and
rights in such statements. Such statements include verbal statements
in IETF meetings, as well as written and electronic communications
made at any time or place, which are addressed to

        * the IETF plenary session,
        * any IETF working group or portion thereof,
        * the IESG, or any member thereof on behalf of the IESG,
        * the IAB or any member thereof on behalf of the IAB,
        * any IETF mailing list, including the IETF list itself, any
working
            group or design team list, or any other list functioning
under IETF
            auspices,
        * the RFC Editor or the Internet-Drafts function

Statements made outside of an IETF meeting, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not subject to these provisions.

   
***************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@www1.ietf.org.  Thanks!

Passwords for vrrp-web-archive@ietf.org:

List                                     Password // URL
----                                     --------  
vrrp@ietf.org                            mPhD      
https://www1.ietf.org/mailman/options/vrrp/vrrp-web-archive%40ietf.org



From exim@www1.ietf.org  Wed May 12 05:14:53 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA19198
	for <vrrp-archive@odin.ietf.org>; Wed, 12 May 2004 05:14:52 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNpkF-0001Nx-F1
	for vrrp-archive@odin.ietf.org; Wed, 12 May 2004 05:09:43 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4C99ht3005309
	for vrrp-archive@odin.ietf.org; Wed, 12 May 2004 05:09:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNpgM-0000Qy-Pi
	for vrrp-web-archive@optimus.ietf.org; Wed, 12 May 2004 05:05:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18846
	for <vrrp-web-archive@ietf.org>; Wed, 12 May 2004 05:05:40 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNpgJ-00044a-J8
	for vrrp-web-archive@ietf.org; Wed, 12 May 2004 05:05:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNpfN-0003az-00
	for vrrp-web-archive@ietf.org; Wed, 12 May 2004 05:04:41 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNpeT-00037L-00
	for vrrp-web-archive@ietf.org; Wed, 12 May 2004 05:03:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNpXy-0007CF-DR; Wed, 12 May 2004 04:57:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNpNz-00034w-7s
	for vrrp@optimus.ietf.org; Wed, 12 May 2004 04:46:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17903
	for <vrrp@ietf.org>; Wed, 12 May 2004 04:46:40 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNpNw-0002Is-05
	for vrrp@ietf.org; Wed, 12 May 2004 04:46:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNpN5-0001oT-00
	for vrrp@ietf.org; Wed, 12 May 2004 04:45:48 -0400
Received: from web12101.mail.yahoo.com ([216.136.172.21])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNpMA-0001Hd-00
	for vrrp@ietf.org; Wed, 12 May 2004 04:44:50 -0400
Message-ID: <20040512084451.87009.qmail@web12101.mail.yahoo.com>
Received: from [212.234.218.193] by web12101.mail.yahoo.com via HTTP; Wed, 12 May 2004 01:44:50 PDT
Date: Wed, 12 May 2004 01:44:50 -0700 (PDT)
From: "Stéphane" Monnier <stephane_monnier@yahoo.com>
To: vrrp@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [VRRP] ARP Reply or Request
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Hi,

The paragraph 6.4.2 of the RFC 2338 and 3768 says the
router which becomes Master must send an ARP request.

Recently, I have tested two implementations : one
sends an ARP request and the other an ARP reply.
The two implementations interoperate well each other.

Is there a problem to send an ARP reply instead of an
ARP request ?

Best Regards,
Stephane 


	
		
__________________________________
Do you Yahoo!?
Yahoo! Movies - Buy advance tickets for 'Shrek 2'
http://movies.yahoo.com/showtimes/movie?mid=1808405861 

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



From exim@www1.ietf.org  Wed May 12 05:52:36 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20574
	for <vrrp-archive@odin.ietf.org>; Wed, 12 May 2004 05:52:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNqGn-0007vK-6w
	for vrrp-archive@odin.ietf.org; Wed, 12 May 2004 05:43:21 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4C9hLDR030459
	for vrrp-archive@odin.ietf.org; Wed, 12 May 2004 05:43:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNqCd-0007Hv-Cm
	for vrrp-web-archive@optimus.ietf.org; Wed, 12 May 2004 05:39:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20050
	for <vrrp-web-archive@ietf.org>; Wed, 12 May 2004 05:39:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNqCZ-0004n3-Vx
	for vrrp-web-archive@ietf.org; Wed, 12 May 2004 05:39:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNqBd-0004I0-00
	for vrrp-web-archive@ietf.org; Wed, 12 May 2004 05:38:01 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNqAt-0003mm-00
	for vrrp-web-archive@ietf.org; Wed, 12 May 2004 05:37:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNq6p-0005xE-2C; Wed, 12 May 2004 05:33:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNq0o-0004dX-Lf
	for vrrp@optimus.ietf.org; Wed, 12 May 2004 05:26:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA19645
	for <vrrp@ietf.org>; Wed, 12 May 2004 05:26:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNq0l-0006ef-9X
	for vrrp@ietf.org; Wed, 12 May 2004 05:26:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNpzs-0006An-00
	for vrrp@ietf.org; Wed, 12 May 2004 05:25:53 -0400
Received: from [203.129.222.68] (helo=lin.calsoft.co.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNpzL-0005gQ-00
	for vrrp@ietf.org; Wed, 12 May 2004 05:25:20 -0400
Received: from calsoftwilliam ([203.129.222.92])
	by lin.calsoft.co.in (8.11.0/8.11.0) with SMTP id i4C9DFE27562;
	Wed, 12 May 2004 14:43:15 +0530
Reply-To: <williams@calsoft.co.in>
From: "William StanisLaus" <williams@calsoft.co.in>
To: "'Stiphane Monnier'" <stephane_monnier@yahoo.com>, <vrrp@ietf.org>
Subject: RE: [VRRP] ARP Reply or Request
Date: Wed, 12 May 2004 14:53:37 +0530
Message-ID: <000101c43802$d719d160$8c0210ac@calsoftwilliam>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
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 V6.00.2800.1409
In-Reply-To: <20040512084451.87009.qmail@web12101.mail.yahoo.com>
X-MailScanner: Found to be clean
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,
	If i am not wrong it should be GARP which you are talking. i.e. ARP request
with its own ip address, sent when router becomes MASTER. This is used to
flush the HOST ARP cache information for the NEW MASTER. But if the OLD
MASTER still holds the virutal IP address, then he will respond to the GARP
(ARP request) as a ARP reply, in that case, he SHOULDNOT become as MASTER.

Best Regards,
William.



> -----Original Message-----
> From: vrrp-admin@ietf.org [mailto:vrrp-admin@ietf.org]On Behalf Of
> Stiphane Monnier
> Sent: Wednesday, May 12, 2004 2:15 PM
> To: vrrp@ietf.org
> Subject: [VRRP] ARP Reply or Request
>
>
> Hi,
>
> The paragraph 6.4.2 of the RFC 2338 and 3768 says the
> router which becomes Master must send an ARP request.
>
> Recently, I have tested two implementations : one
> sends an ARP request and the other an ARP reply.
> The two implementations interoperate well each other.
>
> Is there a problem to send an ARP reply instead of an
> ARP request ?
>
> Best Regards,
> Stephane
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Movies - Buy advance tickets for 'Shrek 2'
> http://movies.yahoo.com/showtimes/movie?mid=1808405861
>
> _______________________________________________
> 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 May 12 06:29:31 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22130
	for <vrrp-archive@odin.ietf.org>; Wed, 12 May 2004 06:29:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNqvo-0008Cx-8Y
	for vrrp-archive@odin.ietf.org; Wed, 12 May 2004 06:25:44 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4CAPiPQ031551
	for vrrp-archive@odin.ietf.org; Wed, 12 May 2004 06:25:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNqmS-0006fL-VL
	for vrrp-web-archive@optimus.ietf.org; Wed, 12 May 2004 06:16:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21578
	for <vrrp-web-archive@ietf.org>; Wed, 12 May 2004 06:16:01 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNqmP-0007mB-5w
	for vrrp-web-archive@ietf.org; Wed, 12 May 2004 06:16:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNqla-0007HV-00
	for vrrp-web-archive@ietf.org; Wed, 12 May 2004 06:15:11 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNqkt-0006m0-00
	for vrrp-web-archive@ietf.org; Wed, 12 May 2004 06:14:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNqef-00048x-6t; Wed, 12 May 2004 06:08:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNqcg-0003LV-09
	for vrrp@optimus.ietf.org; Wed, 12 May 2004 06:05:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21066
	for <vrrp@ietf.org>; Wed, 12 May 2004 06:05:54 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNqcc-0002cL-A1
	for vrrp@ietf.org; Wed, 12 May 2004 06:05:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNqbh-00027j-00
	for vrrp@ietf.org; Wed, 12 May 2004 06:04:58 -0400
Received: from web12103.mail.yahoo.com ([216.136.172.23])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNqb0-0001d1-00
	for vrrp@ietf.org; Wed, 12 May 2004 06:04:14 -0400
Message-ID: <20040512100415.60229.qmail@web12103.mail.yahoo.com>
Received: from [212.234.218.193] by web12103.mail.yahoo.com via HTTP; Wed, 12 May 2004 03:04:15 PDT
Date: Wed, 12 May 2004 03:04:15 -0700 (PDT)
From: "Stéphane" Monnier <stephane_monnier@yahoo.com>
Subject: RE: [VRRP] ARP Reply or Request
To: vrrp@ietf.org
In-Reply-To: <000101c43802$d719d160$8c0210ac@calsoftwilliam>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Hi,

Just to clarify my remarks.

The ARP request and reply are not send in the same
time by the two routers.

Let's say I have two routers (A and B) with VRRP
enabled.
A is master and B is backup. 
When B becomes master, he sends an ARP request (OK
with the RFC). But when A becomes master, he sends an
ARP reply ( KO with the RFC).

For my Linux Laptop, an ARP reply or request is not a
problem, he updates his ARP cache. But I don't know if
in certain cases, it could be a problem.

Best Regards,
Stephane
 
--- William StanisLaus <williams@calsoft.co.in> wrote:
> Hi,
> 	If i am not wrong it should be GARP which you are
> talking. i.e. ARP request
> with its own ip address, sent when router becomes
> MASTER. This is used to
> flush the HOST ARP cache information for the NEW
> MASTER. But if the OLD
> MASTER still holds the virutal IP address, then he
> will respond to the GARP
> (ARP request) as a ARP reply, in that case, he
> SHOULDNOT become as MASTER.
> 
> Best Regards,
> William.
> 
> 
> 
> > -----Original Message-----
> > From: vrrp-admin@ietf.org
> [mailto:vrrp-admin@ietf.org]On Behalf Of
> > Stiphane Monnier
> > Sent: Wednesday, May 12, 2004 2:15 PM
> > To: vrrp@ietf.org
> > Subject: [VRRP] ARP Reply or Request
> >
> >
> > Hi,
> >
> > The paragraph 6.4.2 of the RFC 2338 and 3768 says
> the
> > router which becomes Master must send an ARP
> request.
> >
> > Recently, I have tested two implementations : one
> > sends an ARP request and the other an ARP reply.
> > The two implementations interoperate well each
> other.
> >
> > Is there a problem to send an ARP reply instead of
> an
> > ARP request ?
> >
> > Best Regards,
> > Stephane
> >
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Movies - Buy advance tickets for 'Shrek 2'
> >
>
http://movies.yahoo.com/showtimes/movie?mid=1808405861
> >
> > _______________________________________________
> > 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



	
		
__________________________________
Do you Yahoo!?
Yahoo! Movies - Buy advance tickets for 'Shrek 2'
http://movies.yahoo.com/showtimes/movie?mid=1808405861 

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



From exim@www1.ietf.org  Wed May 12 06:53:04 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA23589
	for <vrrp-archive@odin.ietf.org>; Wed, 12 May 2004 06:53:04 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNrHq-0004zY-JZ
	for vrrp-archive@odin.ietf.org; Wed, 12 May 2004 06:48:30 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4CAmU0w019188
	for vrrp-archive@odin.ietf.org; Wed, 12 May 2004 06:48:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNrHF-0004mI-Ac
	for vrrp-web-archive@optimus.ietf.org; Wed, 12 May 2004 06:47:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA23437
	for <vrrp-web-archive@ietf.org>; Wed, 12 May 2004 06:47:49 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNrHB-0001C8-93
	for vrrp-web-archive@ietf.org; Wed, 12 May 2004 06:47:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNrG8-0000h1-00
	for vrrp-web-archive@ietf.org; Wed, 12 May 2004 06:46:45 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNrFs-0000Cf-00
	for vrrp-web-archive@ietf.org; Wed, 12 May 2004 06:46:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNrBZ-0003hK-Py; Wed, 12 May 2004 06:42:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNr9d-0003MA-LT
	for vrrp@optimus.ietf.org; Wed, 12 May 2004 06:40:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22949
	for <vrrp@ietf.org>; Wed, 12 May 2004 06:39:57 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNr9Z-0004dP-Jf
	for vrrp@ietf.org; Wed, 12 May 2004 06:39:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNr8d-00046W-00
	for vrrp@ietf.org; Wed, 12 May 2004 06:39:00 -0400
Received: from [203.129.222.68] (helo=lin.calsoft.co.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNr7q-0003Xa-00
	for vrrp@ietf.org; Wed, 12 May 2004 06:38:11 -0400
Received: from calsoftwilliam ([203.129.222.92])
	by lin.calsoft.co.in (8.11.0/8.11.0) with SMTP id i4CAQCE07103
	for <vrrp@ietf.org>; Wed, 12 May 2004 15:56:13 +0530
Reply-To: <williams@calsoft.co.in>
From: "William StanisLaus" <williams@calsoft.co.in>
To: <vrrp@ietf.org>
Subject: RE: [VRRP] ARP Reply or Request
Date: Wed, 12 May 2004 16:06:47 +0530
Message-ID: <000001c4380d$07a87f70$8c0210ac@calsoftwilliam>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
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)
In-Reply-To: <20040512100415.60229.qmail@web12103.mail.yahoo.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-MailScanner: Found to be clean
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Stephane,
  I wonder, how can ARP reply is sent from Router A when it take over
MASTER. i.e Switch back.
Because
1. ARP reply is a unicast.
2. For such unicast reply there should be a request.

now i have a quick question, to whom router A sending ARP reply??

Does any HOST update ARP cache from ARP reply <Unicast Packet>.....

Best Regards,
William.

> -----Original Message-----
> From: vrrp-admin@ietf.org [mailto:vrrp-admin@ietf.org]On Behalf Of
> Stiphane Monnier
> Sent: Wednesday, May 12, 2004 3:34 PM
> To: vrrp@ietf.org
> Subject: RE: [VRRP] ARP Reply or Request
>
>
> Hi,
>
> Just to clarify my remarks.
>
> The ARP request and reply are not send in the same
> time by the two routers.
>
> Let's say I have two routers (A and B) with VRRP
> enabled.
> A is master and B is backup.
> When B becomes master, he sends an ARP request (OK
> with the RFC). But when A becomes master, he sends an
> ARP reply ( KO with the RFC).
>
> For my Linux Laptop, an ARP reply or request is not a
> problem, he updates his ARP cache. But I don't know if
> in certain cases, it could be a problem.
>
> Best Regards,
> Stephane
>
> --- William StanisLaus <williams@calsoft.co.in> wrote:
> > Hi,
> > 	If i am not wrong it should be GARP which you are
> > talking. i.e. ARP request
> > with its own ip address, sent when router becomes
> > MASTER. This is used to
> > flush the HOST ARP cache information for the NEW
> > MASTER. But if the OLD
> > MASTER still holds the virutal IP address, then he
> > will respond to the GARP
> > (ARP request) as a ARP reply, in that case, he
> > SHOULDNOT become as MASTER.
> >
> > Best Regards,
> > William.
> >
> >
> >
> > > -----Original Message-----
> > > From: vrrp-admin@ietf.org
> > [mailto:vrrp-admin@ietf.org]On Behalf Of
> > > Stiphane Monnier
> > > Sent: Wednesday, May 12, 2004 2:15 PM
> > > To: vrrp@ietf.org
> > > Subject: [VRRP] ARP Reply or Request
> > >
> > >
> > > Hi,
> > >
> > > The paragraph 6.4.2 of the RFC 2338 and 3768 says
> > the
> > > router which becomes Master must send an ARP
> > request.
> > >
> > > Recently, I have tested two implementations : one
> > > sends an ARP request and the other an ARP reply.
> > > The two implementations interoperate well each
> > other.
> > >
> > > Is there a problem to send an ARP reply instead of
> > an
> > > ARP request ?
> > >
> > > Best Regards,
> > > Stephane
> > >
> > >
> > >
> > >
> > > __________________________________
> > > Do you Yahoo!?
> > > Yahoo! Movies - Buy advance tickets for 'Shrek 2'
> > >
> >
> http://movies.yahoo.com/showtimes/movie?mid=1808405861
> > >
> > > _______________________________________________
> > > 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
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Movies - Buy advance tickets for 'Shrek 2'
> http://movies.yahoo.com/showtimes/movie?mid=1808405861
>
> _______________________________________________
> 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 May 12 13:06:26 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26918
	for <vrrp-archive@odin.ietf.org>; Wed, 12 May 2004 13:06:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNxAA-0002r9-BT
	for vrrp-archive@odin.ietf.org; Wed, 12 May 2004 13:04:58 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4CH4wXo010969
	for vrrp-archive@odin.ietf.org; Wed, 12 May 2004 13:04:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNwsO-0005xJ-B3
	for vrrp-web-archive@optimus.ietf.org; Wed, 12 May 2004 12:46:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25696
	for <vrrp-web-archive@ietf.org>; Wed, 12 May 2004 12:46:33 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNwsM-00056e-NA
	for vrrp-web-archive@ietf.org; Wed, 12 May 2004 12:46:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNwrP-0004Zg-00
	for vrrp-web-archive@ietf.org; Wed, 12 May 2004 12:45:36 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNwqD-0003j5-00
	for vrrp-web-archive@ietf.org; Wed, 12 May 2004 12:44:21 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNweJ-00087o-GC; Wed, 12 May 2004 12:32:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNwKr-0006T4-JW
	for vrrp@optimus.ietf.org; Wed, 12 May 2004 12:11:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22227
	for <vrrp@ietf.org>; Wed, 12 May 2004 12:11:54 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNwKq-0004GK-63
	for vrrp@ietf.org; Wed, 12 May 2004 12:11:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNwJZ-0003de-00
	for vrrp@ietf.org; Wed, 12 May 2004 12:10:38 -0400
Received: from web12105.mail.yahoo.com ([216.136.172.25])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNwIT-0002iV-00
	for vrrp@ietf.org; Wed, 12 May 2004 12:09:29 -0400
Message-ID: <20040512160928.15150.qmail@web12105.mail.yahoo.com>
Received: from [212.234.218.193] by web12105.mail.yahoo.com via HTTP; Wed, 12 May 2004 09:09:28 PDT
Date: Wed, 12 May 2004 09:09:28 -0700 (PDT)
From: "Stéphane" Monnier <stephane_monnier@yahoo.com>
Subject: RE: [VRRP] ARP Reply or Request
To: vrrp@ietf.org
In-Reply-To: <000001c4380d$07a87f70$8c0210ac@calsoftwilliam>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Hi,

In fact, I agree with you. But when I inspect the ARP
reply, I show this :

Ethernet
    MAC source      : 00:00:5e:00:01:01
    MAC Destination : ff:ff:ff:ff:ff:ff
ARP
    Hard Type  : 0x0001
    Proto Type : Ox0800
    Hard size  : 6
    Proto size : 4
    OpCode     : 2 (Reply)
    Sender MAC : 00:00:5e:00:01:01
    Sender IP  : 10.10.10.254
    Target MAC : ff:ff:ff:ff:ff:ff
    Target IP  : 10.10.10.254

It is strange to have a "broadcast" ARP reply.

Best Regards,
Stephane

--- William StanisLaus <williams@calsoft.co.in> wrote:
> Hi Stephane,
>   I wonder, how can ARP reply is sent from Router A
> when it take over
> MASTER. i.e Switch back.
> Because
> 1. ARP reply is a unicast.
> 2. For such unicast reply there should be a request.
> 
> now i have a quick question, to whom router A
> sending ARP reply??
> 
> Does any HOST update ARP cache from ARP reply
> <Unicast Packet>.....
> 
> Best Regards,
> William.
> 
> > -----Original Message-----
> > From: vrrp-admin@ietf.org
> [mailto:vrrp-admin@ietf.org]On Behalf Of
> > Stiphane Monnier
> > Sent: Wednesday, May 12, 2004 3:34 PM
> > To: vrrp@ietf.org
> > Subject: RE: [VRRP] ARP Reply or Request
> >
> >
> > Hi,
> >
> > Just to clarify my remarks.
> >
> > The ARP request and reply are not send in the same
> > time by the two routers.
> >
> > Let's say I have two routers (A and B) with VRRP
> > enabled.
> > A is master and B is backup.
> > When B becomes master, he sends an ARP request (OK
> > with the RFC). But when A becomes master, he sends
> an
> > ARP reply ( KO with the RFC).
> >
> > For my Linux Laptop, an ARP reply or request is
> not a
> > problem, he updates his ARP cache. But I don't
> know if
> > in certain cases, it could be a problem.
> >
> > Best Regards,
> > Stephane
> >
> > --- William StanisLaus <williams@calsoft.co.in>
> wrote:
> > > Hi,
> > > 	If i am not wrong it should be GARP which you
> are
> > > talking. i.e. ARP request
> > > with its own ip address, sent when router
> becomes
> > > MASTER. This is used to
> > > flush the HOST ARP cache information for the NEW
> > > MASTER. But if the OLD
> > > MASTER still holds the virutal IP address, then
> he
> > > will respond to the GARP
> > > (ARP request) as a ARP reply, in that case, he
> > > SHOULDNOT become as MASTER.
> > >
> > > Best Regards,
> > > William.
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: vrrp-admin@ietf.org
> > > [mailto:vrrp-admin@ietf.org]On Behalf Of
> > > > Stiphane Monnier
> > > > Sent: Wednesday, May 12, 2004 2:15 PM
> > > > To: vrrp@ietf.org
> > > > Subject: [VRRP] ARP Reply or Request
> > > >
> > > >
> > > > Hi,
> > > >
> > > > The paragraph 6.4.2 of the RFC 2338 and 3768
> says
> > > the
> > > > router which becomes Master must send an ARP
> > > request.
> > > >
> > > > Recently, I have tested two implementations :
> one
> > > > sends an ARP request and the other an ARP
> reply.
> > > > The two implementations interoperate well each
> > > other.
> > > >
> > > > Is there a problem to send an ARP reply
> instead of
> > > an
> > > > ARP request ?
> > > >
> > > > Best Regards,
> > > > Stephane
> > > >
> > > >
> > > >
> > > >
> > > > __________________________________
> > > > Do you Yahoo!?
> > > > Yahoo! Movies - Buy advance tickets for 'Shrek
> 2'
> > > >
> > >
> >
>
http://movies.yahoo.com/showtimes/movie?mid=1808405861
> > > >
> > > >
> _______________________________________________
> > > > 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
> >
> >
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Movies - Buy advance tickets for 'Shrek 2'
> >
>
http://movies.yahoo.com/showtimes/movie?mid=1808405861
> >
> > _______________________________________________
> > 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



	
		
__________________________________
Do you Yahoo!?
Yahoo! Movies - Buy advance tickets for 'Shrek 2'
http://movies.yahoo.com/showtimes/movie?mid=1808405861 

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



From exim@www1.ietf.org  Wed May 12 15:43:43 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06383
	for <vrrp-archive@odin.ietf.org>; Wed, 12 May 2004 15:43:43 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNzXq-0003a4-FI
	for vrrp-archive@odin.ietf.org; Wed, 12 May 2004 15:38:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4CJbYuF013757
	for vrrp-archive@odin.ietf.org; Wed, 12 May 2004 15:37:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNzPP-0008Oz-UA
	for vrrp-web-archive@optimus.ietf.org; Wed, 12 May 2004 15:28:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05413
	for <vrrp-web-archive@ietf.org>; Wed, 12 May 2004 15:28:50 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNzPO-0001ov-Jf
	for vrrp-web-archive@ietf.org; Wed, 12 May 2004 15:28:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNzOT-0001IP-00
	for vrrp-web-archive@ietf.org; Wed, 12 May 2004 15:27:54 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNzNb-0000mu-00
	for vrrp-web-archive@ietf.org; Wed, 12 May 2004 15:26:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNzHw-0006X7-KH; Wed, 12 May 2004 15:21:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNz7V-0000T6-BA
	for vrrp@optimus.ietf.org; Wed, 12 May 2004 15:10:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01206
	for <vrrp@ietf.org>; Wed, 12 May 2004 14:19:38 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNyKQ-0006Ci-Kf
	for vrrp@ietf.org; Wed, 12 May 2004 14:19:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNyJV-0005jG-00
	for vrrp@ietf.org; Wed, 12 May 2004 14:18:42 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNyIj-0005Fg-00
	for vrrp@ietf.org; Wed, 12 May 2004 14:17:53 -0400
Received: from nofear-snat.bivio.net ([216.142.75.231] helo=exmail.bivio.net)
	by mx2.foretec.com with smtp (Exim 4.24)
	id 1BNyIe-00063O-09
	for vrrp@ietf.org; Wed, 12 May 2004 14:17:48 -0400
Received: from dprovan1 ([192.168.24.137]) by exmail.bivio.net with Microsoft SMTPSVC(5.0.2195.4453);
	 Wed, 12 May 2004 10:21:19 -0700
From: "Don Provan" <dprovan@bivio.net>
To: <vrrp@ietf.org>
Cc: "'Stiphane Monnier'" <stephane_monnier@yahoo.com>
Subject: RE: [VRRP] ARP Reply or Request
Date: Wed, 12 May 2004 10:21:17 -0700
Message-ID: <000601c43845$8a661020$8918a8c0@corp.networkrobots.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: base64
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 V6.00.2800.1409
In-Reply-To: <20040512084451.87009.qmail@web12101.mail.yahoo.com>
X-OriginalArrivalTime: 12 May 2004 17:21:19.0917 (UTC) FILETIME=[8A67BDD0:01C43845]
Content-Transfer-Encoding: base64
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=2.2 required=5.0 tests=MIME_BASE64_LATIN,
	MIME_BASE64_TEXT autolearn=no version=2.60
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

SSdtIG5vdCBzdXJlIHdoYXQgdGhlIFZSUlAgc3BlYyBhY3R1YWxseSBzYXlzIGFib3V0IHRoaXMs
DQpidXQgdGhlIEFSUCByZXF1aXJlbWVudCBpcyBhY3R1YWxseSBhIHJlcXVpcmVtZW50IGZvciBH
QVJQLg0KSSBkb24ndCBrbm93IHdoYXQgdGhlICpHQVJQKiBzcGVjIHNheXMsIGVpdGhlciAoY2Fu
J3QgZXZlbg0KcmVtZW1iZXIgaWYgdGhlcmUgaXMgYWN0dWFsbHkgYSBHQVJQIHNwZWMsIGJ1dCBp
ZiB0aGVyZSBpcywNCkknbSBzdXJlIGl0IGRvZXNuJ3QgY2FsbCBpdHNlbGYgIEdBUlApLCBidXQg
d2hhdCBJJ3ZlIHJlYWQNCmluIHZhcmlvdXMgR0FSUCBpbXBsZW1lbnRhdGlvbnMgaXMgdGhhdCBz
b21lIHN5c3RlbXMgdXBkYXRlDQp0aGVpciBjYWNoZSBpZiB5b3UgYnJvYWRjYXN0IGFuIEFSUCBy
ZXF1ZXN0LCBidXQgbm90IGlmIHlvdQ0KYnJvYWRjYXN0IGFuIEFSUCByZXBseSwgYW5kIHZpY2Ug
dmVyc2EsIHNvIG15IFZSUlAgaW1wbGVtZW50YXRpb24NCihhbmQgdGhlIEdBUlAgaW1wbGVtZW50
YXRpb24gSSBzdG9sZSBteSBjb2RlIGZyb20pIGJyb2FkY2FzdHMNCmJvdGggYSByZXF1ZXN0ICph
bmQqIGEgcmVwbHkuDQoNCkluIGFueSBjYXNlLCBJIGRvbid0IHRoaW5rIHRoaXMgaGFzIGFueXRo
aW5nIHRvIGRvIHdpdGggVlJSUC4NCkknbSBub3Qgc2F5aW5nIHlvdSdyZSBhc2tpbmcgaW4gdGhl
IHdyb25nIHBsYWNlLCBJJ20ganVzdA0Kc2F5aW5nIHRoZSBlbnN1aW5nIHByb3RvY29sIGRpc2N1
c3Npb24gYWJvdXQgaG93IFZSUlAgbWFzdGVycw0KcmVzcG9uZCB0byBHQVJQIG1lc3NhZ2VzIGlz
IG9mZiB0aGUgbWFyay4gVlJSUCBoYXMgdXR0ZXJseQ0KYW5kIGNvbXBsZXRlbHkgZmFpbGVkIGlm
IG9uZSBWUlJQIG1hc3RlciByZWNlaXZlcyBhIEdBUlANCm1lc3NhZ2UgZnJvbSBvbmUgb2YgaXRz
IFZSUlAgcGVlcnMuIEEgR0FSUCBtZXNzYWdlIGNvdWxkDQoqb25seSogY29tZSBmcm9tIGFuICJ1
bnJlbGF0ZWQiIG5vZGUsIGFsdGhvdWdoLCBhbGFzLCBmb3INClZSUlAsICJ1bnJlbGF0ZWQiIHNv
bWV0aW1lcyBtZWFucyBhbm90aGVyIFZSUlAgbm9kZSB3aXRoDQphIHNsaWdodGx5IGRpZmZlcmVu
dCBjb25maWd1cmF0aW9uLi4uLg0KDQotZG9uDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0t
LS0NCj4gRnJvbTogdnJycC1hZG1pbkBpZXRmLm9yZyBbbWFpbHRvOnZycnAtYWRtaW5AaWV0Zi5v
cmddT24gQmVoYWxmIE9mDQo+IFN0aXBoYW5lIE1vbm5pZXINCj4gU2VudDogV2VkbmVzZGF5LCBN
YXkgMTIsIDIwMDQgMTo0NSBBTQ0KPiBUbzogdnJycEBpZXRmLm9yZw0KPiBTdWJqZWN0OiBbVlJS
UF0gQVJQIFJlcGx5IG9yIFJlcXVlc3QNCj4gDQo+IA0KPiBIaSwNCj4gDQo+IFRoZSBwYXJhZ3Jh
cGggNi40LjIgb2YgdGhlIFJGQyAyMzM4IGFuZCAzNzY4IHNheXMgdGhlDQo+IHJvdXRlciB3aGlj
aCBiZWNvbWVzIE1hc3RlciBtdXN0IHNlbmQgYW4gQVJQIHJlcXVlc3QuDQo+IA0KPiBSZWNlbnRs
eSwgSSBoYXZlIHRlc3RlZCB0d28gaW1wbGVtZW50YXRpb25zIDogb25lDQo+IHNlbmRzIGFuIEFS
UCByZXF1ZXN0IGFuZCB0aGUgb3RoZXIgYW4gQVJQIHJlcGx5Lg0KPiBUaGUgdHdvIGltcGxlbWVu
dGF0aW9ucyBpbnRlcm9wZXJhdGUgd2VsbCBlYWNoIG90aGVyLg0KPiANCj4gSXMgdGhlcmUgYSBw
cm9ibGVtIHRvIHNlbmQgYW4gQVJQIHJlcGx5IGluc3RlYWQgb2YgYW4NCj4gQVJQIHJlcXVlc3Qg
Pw0KPiANCj4gQmVzdCBSZWdhcmRzLA0KPiBTdGVwaGFuZSANCj4gDQo+IA0KPiAJDQo+IAkJDQo+
IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gRG8geW91IFlhaG9vIT8NCj4g
WWFob28hIE1vdmllcyAtIEJ1eSBhZHZhbmNlIHRpY2tldHMgZm9yICdTaHJlayAyJw0KPiBodHRw
Oi8vbW92aWVzLnlhaG9vLmNvbS9zaG93dGltZXMvbW92aWU/bWlkPTE4MDg0MDU4NjEgDQo+IA0K
PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiB2cnJw
IG1haWxpbmcgbGlzdA0KPiB2cnJwQGlldGYub3JnDQo+IGh0dHBzOi8vd3d3MS5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL3ZycnA=


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



From exim@www1.ietf.org  Wed May 12 15:50:40 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06847
	for <vrrp-archive@odin.ietf.org>; Wed, 12 May 2004 15:50:40 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNzbs-0004yX-ST
	for vrrp-archive@odin.ietf.org; Wed, 12 May 2004 15:41:44 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4CJfiGr019124
	for vrrp-archive@odin.ietf.org; Wed, 12 May 2004 15:41:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNzV8-0002cZ-5O
	for vrrp-web-archive@optimus.ietf.org; Wed, 12 May 2004 15:34:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05839
	for <vrrp-web-archive@ietf.org>; Wed, 12 May 2004 15:34:44 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNzV6-0004yt-QR
	for vrrp-web-archive@ietf.org; Wed, 12 May 2004 15:34:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNzU3-0004RP-00
	for vrrp-web-archive@ietf.org; Wed, 12 May 2004 15:33:39 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNzT7-0003v1-00
	for vrrp-web-archive@ietf.org; Wed, 12 May 2004 15:32:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNzI1-0006Y0-Ib; Wed, 12 May 2004 15:21:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNzCJ-00037h-3e
	for vrrp@optimus.ietf.org; Wed, 12 May 2004 15:15:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01409
	for <vrrp@ietf.org>; Wed, 12 May 2004 14:25:46 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNyQM-0001Pc-G5
	for vrrp@ietf.org; Wed, 12 May 2004 14:25:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNyPQ-0000ul-00
	for vrrp@ietf.org; Wed, 12 May 2004 14:24:49 -0400
Received: from web50805.mail.yahoo.com ([206.190.38.114])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNyOS-0007ip-00
	for vrrp@ietf.org; Wed, 12 May 2004 14:23:48 -0400
Message-ID: <20040512175327.93831.qmail@web50805.mail.yahoo.com>
Received: from [66.243.153.70] by web50805.mail.yahoo.com via HTTP; Wed, 12 May 2004 10:53:27 PDT
Date: Wed, 12 May 2004 10:53:27 -0700 (PDT)
From: danny mitzel <danny_j_mitzel@yahoo.com>
Subject: RE: [VRRP] ARP Reply or Request
To: "Stéphane" Monnier <stephane_monnier@yahoo.com>, vrrp@ietf.org
Cc: mitzel@acm.org
In-Reply-To: <20040512100415.60229.qmail@web12103.mail.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

out of curiosity I'd find the answers to williams 
questions of interest.  i.e. is arp reply L2 bcast or
unicast, and what are all of arp payload fields:
sender hardware/protocol address, target hardware/
protocol address.

in reality the answers to those questions are mostly
inconsequential relating to vrrp protocol operation.
1. I've mentioned on this list before that vrrp usage
   of arp is typically not critical to the protocol
   operation.  it's mostly used as a mechanism to
   hopefully speed adoption of VMAC/VIP when vrrp is
   first enabled.  once vrrp is running and all
endhost
   are using VMAC/VIP then it really doesn't matter
   much whether an arp request, reply or nothing is
   sent because the net effect is no change in the
   VMAC/VIP mapping.
2. I'll assume the implementation you're investigating
   is sending the arp reply as L2 bcast.  in that case
   as long as the arp payload sender hardware/protocol
   address is VMAC/VIP then in theory it should be
   just as effective as an arp request.  any
   implementation that follows the recommended arp
   processing algorithm (rfc826) will perform the
   update of an existing sender hardware/protocol
   mapping before it even looks at the opcode.



	
		
__________________________________
Do you Yahoo!?
Yahoo! Movies - Buy advance tickets for 'Shrek 2'
http://movies.yahoo.com/showtimes/movie?mid=1808405861 

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



From exim@www1.ietf.org  Thu May 13 10:40:35 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16503
	for <vrrp-archive@odin.ietf.org>; Thu, 13 May 2004 10:40:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOHL4-0005Fh-MN
	for vrrp-archive@odin.ietf.org; Thu, 13 May 2004 10:37:34 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4DEbYSh020190
	for vrrp-archive@odin.ietf.org; Thu, 13 May 2004 10:37:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOHEu-0004B1-GB
	for vrrp-web-archive@optimus.ietf.org; Thu, 13 May 2004 10:31:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15924
	for <vrrp-web-archive@ietf.org>; Thu, 13 May 2004 10:31:08 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOHEs-0004n8-An
	for vrrp-web-archive@ietf.org; Thu, 13 May 2004 10:31:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOHDm-0004Di-00
	for vrrp-web-archive@ietf.org; Thu, 13 May 2004 10:30:02 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOHCp-0003eo-00
	for vrrp-web-archive@ietf.org; Thu, 13 May 2004 10:29:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOH71-0001w5-77; Thu, 13 May 2004 10:23:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOH0W-00083Z-9p
	for vrrp@optimus.ietf.org; Thu, 13 May 2004 10:16:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14872
	for <vrrp@ietf.org>; Thu, 13 May 2004 10:16:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOH0U-0004D1-1k
	for vrrp@ietf.org; Thu, 13 May 2004 10:16:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOGzj-0003ei-00
	for vrrp@ietf.org; Thu, 13 May 2004 10:15:32 -0400
Received: from [203.129.222.68] (helo=lin.calsoft.co.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOGym-00036d-00
	for vrrp@ietf.org; Thu, 13 May 2004 10:14:33 -0400
Received: from calsoftwilliam ([203.129.222.92])
	by lin.calsoft.co.in (8.11.0/8.11.0) with SMTP id i4DE1qE20934;
	Thu, 13 May 2004 19:31:53 +0530
Reply-To: <williams@calsoft.co.in>
From: "William StanisLaus" <williams@calsoft.co.in>
To: "'danny mitzel'" <danny_j_mitzel@yahoo.com>,
        "'Stiphane Monnier'" <stephane_monnier@yahoo.com>, <vrrp@ietf.org>
Cc: <mitzel@acm.org>
Subject: RE: [VRRP] ARP Reply or Request
Date: Thu, 13 May 2004 19:42:31 +0530
Message-ID: <002101c438f4$556255a0$8c0210ac@calsoftwilliam>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
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 V6.00.2800.1409
Importance: Normal
In-Reply-To: <20040512175327.93831.qmail@web50805.mail.yahoo.com>
X-MailScanner: Found to be clean
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I have a concern there, Might be VRRP doesn't have any issue with GRAP.
Actually GARP is used to update the HOST ARP cache entry within the subnet,
ALSO to check if there is any other HOST/ROUTER is configured with that
BROADCASTED IP ADDRESS. If the advertiser (one who sends the GARP) gets
response i.e. ARP reply, then it implies that there is some one in the
SUBNET holds the IP which SHOULD NOT be assigned to the ROUTER.

Regarding Point 2 by Danny, I doubt, unless otherwise the ARP packet is
completely validated no action is taken on the packet. Moreover any
operation is based on the opcode, if we receive wrong opcode we may endup in
wrong processing.

-William.

> -----Original Message-----
> From: vrrp-admin@ietf.org [mailto:vrrp-admin@ietf.org]On
> Behalf Of danny
> mitzel
> Sent: Wednesday, May 12, 2004 11:23 PM
> To: Stiphane Monnier; vrrp@ietf.org
> Cc: mitzel@acm.org
> Subject: RE: [VRRP] ARP Reply or Request
>
>
> out of curiosity I'd find the answers to williams
> questions of interest.  i.e. is arp reply L2 bcast or
> unicast, and what are all of arp payload fields:
> sender hardware/protocol address, target hardware/
> protocol address.
>
> in reality the answers to those questions are mostly
> inconsequential relating to vrrp protocol operation.
> 1. I've mentioned on this list before that vrrp usage
>    of arp is typically not critical to the protocol
>    operation.  it's mostly used as a mechanism to
>    hopefully speed adoption of VMAC/VIP when vrrp is
>    first enabled.  once vrrp is running and all
> endhost
>    are using VMAC/VIP then it really doesn't matter
>    much whether an arp request, reply or nothing is
>    sent because the net effect is no change in the
>    VMAC/VIP mapping.
> 2. I'll assume the implementation you're investigating
>    is sending the arp reply as L2 bcast.  in that case
>    as long as the arp payload sender hardware/protocol
>    address is VMAC/VIP then in theory it should be
>    just as effective as an arp request.  any
>    implementation that follows the recommended arp
>    processing algorithm (rfc826) will perform the
>    update of an existing sender hardware/protocol
>    mapping before it even looks at the opcode.
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Movies - Buy advance tickets for 'Shrek 2'
> http://movies.yahoo.com/showtimes/movie?mid=1808405861
>
> _______________________________________________
> 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 May 14 04:57:10 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08206
	for <vrrp-archive@odin.ietf.org>; Fri, 14 May 2004 04:57:09 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOYPg-0003ZS-QR
	for vrrp-archive@odin.ietf.org; Fri, 14 May 2004 04:51:29 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4E8pSC4013722
	for vrrp-archive@odin.ietf.org; Fri, 14 May 2004 04:51:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOYN7-0003DY-BX
	for vrrp-web-archive@optimus.ietf.org; Fri, 14 May 2004 04:48:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07732
	for <vrrp-web-archive@ietf.org>; Fri, 14 May 2004 04:48:46 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOYN4-00043l-Ad
	for vrrp-web-archive@ietf.org; Fri, 14 May 2004 04:48:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOYM3-0003W7-00
	for vrrp-web-archive@ietf.org; Fri, 14 May 2004 04:47:44 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOYKs-0002Zw-00
	for vrrp-web-archive@ietf.org; Fri, 14 May 2004 04:46:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOYJT-0002No-65; Fri, 14 May 2004 04:45:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOYFR-0001Ru-05
	for vrrp@optimus.ietf.org; Fri, 14 May 2004 04:40:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07440
	for <vrrp@ietf.org>; Fri, 14 May 2004 04:40:49 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOYFO-0007lJ-1J
	for vrrp@ietf.org; Fri, 14 May 2004 04:40:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOYES-0007HY-00
	for vrrp@ietf.org; Fri, 14 May 2004 04:39:53 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOYE2-0006nL-00
	for vrrp@ietf.org; Fri, 14 May 2004 04:39:26 -0400
Received: from nofear-snat.bivio.net ([216.142.75.231] helo=exmail.bivio.net)
	by mx2.foretec.com with smtp (Exim 4.24)
	id 1BOYE4-0003Xe-NG
	for vrrp@ietf.org; Fri, 14 May 2004 04:39:28 -0400
Received: from dprovan1 ([192.168.24.137]) by exmail.bivio.net with Microsoft SMTPSVC(5.0.2195.4453);
	 Wed, 12 May 2004 13:01:29 -0700
From: "Don Provan" <dprovan@bivio.net>
To: "'danny mitzel'" <danny_j_mitzel@yahoo.com>,
        "'Stiphane Monnier'" <stephane_monnier@yahoo.com>, <vrrp@ietf.org>
Cc: <mitzel@acm.org>
Subject: RE: [VRRP] ARP Reply or Request
Date: Wed, 12 May 2004 13:01:28 -0700
Message-ID: <000f01c4385b$ea4b2870$8918a8c0@corp.networkrobots.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: base64
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 V6.00.2800.1409
In-Reply-To: <20040512175327.93831.qmail@web50805.mail.yahoo.com>
X-OriginalArrivalTime: 12 May 2004 20:01:29.0707 (UTC) FILETIME=[EA4953B0:01C4385B]
Content-Transfer-Encoding: base64
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=2.2 required=5.0 tests=MIME_BASE64_LATIN,
	MIME_BASE64_TEXT autolearn=no version=2.60
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

Rmlyc3QsIGdvb2Qgc3VtbWFyeSBvZiB0aGUgcmVsYXRpb24gd2l0aCBWUlJQLg0KTm93IG9uIHdp
dGggdGhlIEdBUlAgdGFuZ2VudDoNCg0KPiAyLiBJJ2xsIGFzc3VtZSB0aGUgaW1wbGVtZW50YXRp
b24geW91J3JlIGludmVzdGlnYXRpbmcNCj4gICAgaXMgc2VuZGluZyB0aGUgYXJwIHJlcGx5IGFz
IEwyIGJjYXN0LiAgaW4gdGhhdCBjYXNlDQo+ICAgIGFzIGxvbmcgYXMgdGhlIGFycCBwYXlsb2Fk
IHNlbmRlciBoYXJkd2FyZS9wcm90b2NvbA0KPiAgICBhZGRyZXNzIGlzIFZNQUMvVklQIHRoZW4g
aW4gdGhlb3J5IGl0IHNob3VsZCBiZQ0KPiAgICBqdXN0IGFzIGVmZmVjdGl2ZSBhcyBhbiBhcnAg
cmVxdWVzdC4gIGFueQ0KPiAgICBpbXBsZW1lbnRhdGlvbiB0aGF0IGZvbGxvd3MgdGhlIHJlY29t
bWVuZGVkIGFycA0KPiAgICBwcm9jZXNzaW5nIGFsZ29yaXRobSAocmZjODI2KSB3aWxsIHBlcmZv
cm0gdGhlDQo+ICAgIHVwZGF0ZSBvZiBhbiBleGlzdGluZyBzZW5kZXIgaGFyZHdhcmUvcHJvdG9j
b2wNCj4gICAgbWFwcGluZyBiZWZvcmUgaXQgZXZlbiBsb29rcyBhdCB0aGUgb3Bjb2RlLg0KDQpZ
ZWFoLCBidXQgaW4gcHJhY3RpY2Ugc29tZSBpbXBsZW1lbnRhdGlvbnMgaWdub3JlIGJyb2FkY2Fz
dA0KQVJQIHJlcGxpZXMgZm9yIG9uZSBvZiB0d28gcmVhc29uczoNCg0KMS4gQVJQIHJlcGxpZXMg
InNob3VsZCBub3QiIGJlIGJyb2FkY2FzdCAobm90IGluIHRoZQ0KcHJvdG9jb2wgc2Vuc2Ugb2Yg
U0hPVUxEIE5PVCwgYnV0IGluIHRoZSBpbXBsZW1lbnRlcidzDQptaW5kKSwgc28gdGhpcyBBUlAg
bWVzc2FnZSBpcyBvYnZpb3VzbHkganVzdCBhbiBhdHRlbXB0IHRvDQpicmVhayBzZWN1cml0eS4g
QW5kLCBhY3R1YWxseSwgSSByZWNhbGwgdGhlcmUgd2FzIGFuDQphdHRhY2sgZGV2ZWxvcGVkIHRo
YXQgdXNlZCB0aGlzIHN0ZXAsIGJ1dCwgb2YgY291cnNlLCBpdCdzDQplYXN5IGVub3VnaCBmb3Ig
c29tZW9uZSB0aGF0IGNhbiBzZW5kIHN1Y2ggYSByZXBseSB0bw0KZGlzcnVwdCBhbiBBUlAgY2Fj
aGUgdXNpbmcgbW9yZSBzdWJ0bGUgbWV0aG9kcy4NCg0KMi4gVGhlIEFSUCByZXBseSBjb3VsZG4n
dCBiZSB0byBhIHJlcXVlc3QgdGhlIGltcGxlbWVudGF0aW9uDQpzZW50LCBzbyBpdCBpZ25vcmVz
IHRoZW0uDQoNCkknbSBub3QgZGVmZW5kaW5nIHRoZXNlIGltcGxlbWVudGF0aW9ucyAoYWx0aG91
Z2gsIGF0IHRoZQ0Kc2FtZSB0aW1lLCBJJ20gbm90IHN1cmUgdGhlcmUgaGF2ZW4ndCBiZWVuIHN1
YnNlcXVlbnQgUkZDcw0KdGhhdCByZWNvbW1lbmRlZCBvbmUgb3IgdGhlIG90aGVyIG9mIHRoZXNl
IHRlY2huaXF1ZXMgYXMNCnNvbWV3aGF0IGR1YmlvdXMgImRlZmVuc2l2ZSIgbWVhc3VyZXMpLCBi
dXQgSSd2ZSBlbmNvdW50ZXJlZA0KYm90aCBvZiB0aGVtIHBlcnNvbmFsbHkuIFNvIHRvIHN1cHBv
cnQgdGhlc2Uga25vd24gZmF1bHR5DQppbXBsZW1lbnRhdGlvbnMsIEkgcmVjb21tZW5kIHNlbmRp
bmcgYm90aCBhIHJlcXVlc3QgKmFuZCogYQ0KcmVwbHkuDQoNCkkndmUgYWxzbyBlbmNvdW50ZXJl
ZCBzeXN0ZW1zIHRoYXQgZG9uJ3QgdXBkYXRlIHRoZWlyDQpjYWNoZXMgYmFzZWQgb24gYSByZWNl
aXZpbmcgYSAqcmVxdWVzdCouIEkgc3VwcG9zZSB5b3UNCmNvdWxkIG1ha2UgdGhlIHNhbWUgYXJn
dW1lbnRzIGZvciB0aGF0IC0tIGFsdGhvdWdoIHRoZQ0KYWlyIGdldHMgKnF1aXRlKiB0aGluIHRo
ZXJlIC0tIGJ1dCB0aGUgY2FzZXMgSSBrbm93DQphYm91dCwgdGhlICpyZWFsKiBleHBsYW5hdGlv
biB3YXMganVzdCB0aGF0IHRoZXkNCndlcmUgYnJva2VuLi4uIFN0aWxsLCB0aGV5IHdlcmUgaW4g
cHJvZHVjdGlvbi4gSW4gZmFjdCwNCmEgaGFuZGZ1bCBvZiB0aGVtIHRhbGsgdG8gbXkgVlJSUCBp
bXBsZW1lbnRhdGlvbiBldmVuDQphcyB3ZSBzcGVhay4NCg0KLWRvbg0K


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



From exim@www1.ietf.org  Fri May 14 07:23:18 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15018
	for <vrrp-archive@odin.ietf.org>; Fri, 14 May 2004 07:23:18 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOahP-0002RL-Fd
	for vrrp-archive@odin.ietf.org; Fri, 14 May 2004 07:17:55 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4EBHtnP009379
	for vrrp-archive@odin.ietf.org; Fri, 14 May 2004 07:17:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOabe-0000sR-8y
	for vrrp-web-archive@optimus.ietf.org; Fri, 14 May 2004 07:11:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14558
	for <vrrp-web-archive@ietf.org>; Fri, 14 May 2004 07:11:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOaba-0006pw-2z
	for vrrp-web-archive@ietf.org; Fri, 14 May 2004 07:11:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOaag-0006KT-00
	for vrrp-web-archive@ietf.org; Fri, 14 May 2004 07:10:58 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOaZO-0005V6-00
	for vrrp-web-archive@ietf.org; Fri, 14 May 2004 07:09:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOaR5-0006gq-Dv; Fri, 14 May 2004 07:01:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOaPD-0006Ih-2Q
	for vrrp@optimus.ietf.org; Fri, 14 May 2004 06:59:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14108
	for <vrrp@ietf.org>; Fri, 14 May 2004 06:59:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOaP8-0000Mu-RT
	for vrrp@ietf.org; Fri, 14 May 2004 06:59:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOaOJ-0007dl-00
	for vrrp@ietf.org; Fri, 14 May 2004 06:58:12 -0400
Received: from mx02.cybersurf.com ([209.197.145.105])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOaNI-0006l5-00
	for vrrp@ietf.org; Fri, 14 May 2004 06:57:09 -0400
Received: from mail.cyberus.ca ([209.197.145.21])
	by mx02.cybersurf.com with esmtp (Exim 4.30)
	id 1BOaMr-0004xo-6U
	for vrrp@ietf.org; Fri, 14 May 2004 06:56:41 -0400
Received: from cpe0030ab124d2f-cm014500000962.cpe.net.cable.rogers.com ([24.103.99.32] helo=[10.0.0.21])
	by mail.cyberus.ca with esmtp (Exim 4.20)
	id 1BOaMo-0004PC-J3; Fri, 14 May 2004 06:56:38 -0400
Subject: RE: [VRRP] ARP Reply or Request
From: jamal <hadi@cyberus.ca>
Reply-To: hadi@cyberus.ca
To: Don Provan <dprovan@bivio.net>
Cc: vrrp@ietf.org, "'Stiphane Monnier'" <stephane_monnier@yahoo.com>
In-Reply-To: <000601c43845$8a661020$8918a8c0@corp.networkrobots.com>
References: <000601c43845$8a661020$8918a8c0@corp.networkrobots.com>
Content-Type: text/plain
Organization: jamalopolis
Message-Id: <1084532167.1036.128.camel@jzny.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2 
Date: 14 May 2004 06:56:07 -0400
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Wed, 2004-05-12 at 13:21, Don Provan wrote:
> I'm not sure what the VRRP spec actually says about this,
> but the ARP requirement is actually a requirement for GARP.
> I don't know what the *GARP* spec says, either (can't even
> remember if there is actually a GARP spec, but if there is,
> I'm sure it doesn't call itself  GARP), 

ive been getting the chills seeing grat ARP being reffered to as GARP.
You almost stopped the abuse above Don but didnt go far enough ;->
GARP is infact a well known IEEE 802.1P extension to its 802.1D
(spanning tree) specification. I beleive GARP stands for Generic
Attribute Registration Protocol (specs available at IEEE website). 
I have seen some glossy magazines refering to grat ARP as the "GARP
protocol" and it has irritated me there as well (unfortunately if i sent
an email to the editor theyd probably never publish it - so i dont
bother).
 
I guess i have to say something useful now to ease my guilt of going off
topic.
One valuable thing with grat ARPs is ability to update middle device
caches such as L2 switches with a new port where it makes sense i.e
cause a station movement. 

Consider a VRRP capable L3 device pair connected to ports Y and Z of an
L2 device. On port X of L2 switch is a sender. On port B of both L3
devices is a hub connection to a passive receiver. 
Traffic direction is from sender to receiver (unidirectional) most of
the time. 
Should the backup of the L3 devices take over and not send a grat ARP,
then sender will continue sending to the switch as it was; swithc will
be sending to the wrong port (i.e to old L3 device). Recovery will
happen when the arp cache on the sender expires and it(sender) issues an
ARP request. 
Of course all that was needed was a way to enforce a station movement.
So it could have been a unicast packet of any sort. It could also have
been a bcast address of any sort incase you have multiple L2 devices.
So why not something sensible like a bcast grat ARP which could be used
by hosts (OS sensitive) as well to update their caches? 

cheers,
jamal



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



From exim@www1.ietf.org  Fri May 14 14:21:01 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10398
	for <vrrp-archive@odin.ietf.org>; Fri, 14 May 2004 14:21:01 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOhEw-0001O9-90
	for vrrp-archive@odin.ietf.org; Fri, 14 May 2004 14:16:58 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4EIGwVH005337
	for vrrp-archive@odin.ietf.org; Fri, 14 May 2004 14:16:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOhAi-0000lS-2u
	for vrrp-web-archive@optimus.ietf.org; Fri, 14 May 2004 14:12:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09571
	for <vrrp-web-archive@ietf.org>; Fri, 14 May 2004 14:12:32 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOhAf-0004iz-MG
	for vrrp-web-archive@ietf.org; Fri, 14 May 2004 14:12:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOh9j-0004Bn-00
	for vrrp-web-archive@ietf.org; Fri, 14 May 2004 14:11:35 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOh8j-0003EQ-00
	for vrrp-web-archive@ietf.org; Fri, 14 May 2004 14:10:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOh5L-0007xZ-Jb; Fri, 14 May 2004 14:07:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOh39-0007X8-3P
	for vrrp@optimus.ietf.org; Fri, 14 May 2004 14:04:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09210
	for <vrrp@ietf.org>; Fri, 14 May 2004 14:04:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOh36-0000gT-O3
	for vrrp@ietf.org; Fri, 14 May 2004 14:04:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOh1t-0007f9-00
	for vrrp@ietf.org; Fri, 14 May 2004 14:03:30 -0400
Received: from web50801.mail.yahoo.com ([206.190.38.110])
	by ietf-mx with smtp (Exim 4.12)
	id 1BOgzz-0006Ni-00
	for vrrp@ietf.org; Fri, 14 May 2004 14:01:31 -0400
Message-ID: <20040514180101.72991.qmail@web50801.mail.yahoo.com>
Received: from [66.243.153.70] by web50801.mail.yahoo.com via HTTP; Fri, 14 May 2004 11:01:01 PDT
Date: Fri, 14 May 2004 11:01:01 -0700 (PDT)
From: danny mitzel <danny_j_mitzel@yahoo.com>
Subject: RE: [VRRP] ARP Reply or Request
To: hadi@cyberus.ca, vrrp@ietf.org
Cc: mitzel@acm.org
In-Reply-To: <1084532167.1036.128.camel@jzny.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


--- jamal <hadi@cyberus.ca> wrote:
> One valuable thing with grat ARPs is ability to
> update middle device caches such as L2 switches with
> a new port where it makes sense i.e cause a station 
> movement. 

if your example was just intended to explain how L2 
bridge/switch station learning functions then I agree
that any unicast or broadcast packet can trigger a
cache update.

if your example is implying that vrrp relies on
gratuitous arp in any way for updating L2 bridge/
switch station learning then I disagree.  as far as
I remember the vrrp protocol specification makes no
mandates on the L2 source MAC if/when a vrrp router
sends gratuitous arp (or regular arp, or forwarding
packets, or send/receive any non-vrrp protocol
packet).
what the vrrp specification mandates is that the vrrp 
Advertisement L2 source MAC must be VMAC and that is 
how vrrp ensures proper update of L2 bridge/switch 
station learning caches.

cheers,danny



	
		
__________________________________
Do you Yahoo!?
SBC Yahoo! - Internet access at a great low price.
http://promo.yahoo.com/sbc/

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



From exim@www1.ietf.org  Tue May 18 06:46:09 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02440
	for <vrrp-archive@odin.ietf.org>; Tue, 18 May 2004 06:46:09 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ1x1-00084t-7g
	for vrrp-archive@odin.ietf.org; Tue, 18 May 2004 06:35:59 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4IAZx6Y031048
	for vrrp-archive@odin.ietf.org; Tue, 18 May 2004 06:35:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ1t1-0007Ba-DB
	for vrrp-web-archive@optimus.ietf.org; Tue, 18 May 2004 06:31:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01564
	for <vrrp-web-archive@ietf.org>; Tue, 18 May 2004 06:31:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQ1sx-0001T1-G8
	for vrrp-web-archive@ietf.org; Tue, 18 May 2004 06:31:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ1rk-0000sW-00
	for vrrp-web-archive@ietf.org; Tue, 18 May 2004 06:30:32 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ1qY-0000Pl-00
	for vrrp-web-archive@ietf.org; Tue, 18 May 2004 06:29:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ1oN-0006FI-ST; Tue, 18 May 2004 06:27:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ1mT-0005TG-EH
	for vrrp@optimus.ietf.org; Tue, 18 May 2004 06:25:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01070
	for <vrrp@ietf.org>; Tue, 18 May 2004 06:25:01 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQ1mP-0006Ud-Hc
	for vrrp@ietf.org; Tue, 18 May 2004 06:25:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ1lb-00066G-00
	for vrrp@ietf.org; Tue, 18 May 2004 06:24:12 -0400
Received: from [203.129.222.68] (helo=lin.calsoft.co.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ1kn-0005hj-00
	for vrrp@ietf.org; Tue, 18 May 2004 06:23:22 -0400
Received: from calsoftwilliam ([203.129.222.92])
	by lin.calsoft.co.in (8.11.0/8.11.0) with SMTP id i4IAAXE26911;
	Tue, 18 May 2004 15:40:33 +0530
Reply-To: <williams@calsoft.co.in>
From: "William StanisLaus" <williams@calsoft.co.in>
To: "'danny mitzel'" <danny_j_mitzel@yahoo.com>, <hadi@cyberus.ca>,
        <vrrp@ietf.org>
Cc: <mitzel@acm.org>
Subject: RE: [VRRP] ARP Reply or Request
Date: Tue, 18 May 2004 15:51:36 +0530
Message-ID: <000201c43cc1$e745ea10$8c0210ac@calsoftwilliam>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
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 V6.00.2800.1409
In-reply-to: <20040514180101.72991.qmail@web50801.mail.yahoo.com>
Importance: Normal
X-MailScanner: Found to be clean
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I have a quick question, What if any HOST/ROUTER in the SUBNET replys to
Gratuitous ARP?? does the ROUTER boardcasting Gratuitous ARP (REQUEST) will
not take the IP (VRRP Virtual IP)  and will not become MASTER ??

-William.

> -----Original Message-----
> From: vrrp-admin@ietf.org [mailto:vrrp-admin@ietf.org]On
> Behalf Of danny
> mitzel
> Sent: Friday, May 14, 2004 11:31 PM
> To: hadi@cyberus.ca; vrrp@ietf.org
> Cc: mitzel@acm.org
> Subject: RE: [VRRP] ARP Reply or Request
>
>
>
> --- jamal <hadi@cyberus.ca> wrote:
> > One valuable thing with grat ARPs is ability to
> > update middle device caches such as L2 switches with
> > a new port where it makes sense i.e cause a station
> > movement.
>
> if your example was just intended to explain how L2
> bridge/switch station learning functions then I agree
> that any unicast or broadcast packet can trigger a
> cache update.
>
> if your example is implying that vrrp relies on
> gratuitous arp in any way for updating L2 bridge/
> switch station learning then I disagree.  as far as
> I remember the vrrp protocol specification makes no
> mandates on the L2 source MAC if/when a vrrp router
> sends gratuitous arp (or regular arp, or forwarding
> packets, or send/receive any non-vrrp protocol
> packet).
> what the vrrp specification mandates is that the vrrp
> Advertisement L2 source MAC must be VMAC and that is
> how vrrp ensures proper update of L2 bridge/switch
> station learning caches.
>
> cheers,danny
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> SBC Yahoo! - Internet access at a great low price.
> http://promo.yahoo.com/sbc/
>
> _______________________________________________
> 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 May 18 15:07:41 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06446
	for <vrrp-archive@odin.ietf.org>; Tue, 18 May 2004 15:07:41 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ9sL-0001vW-Pd
	for vrrp-archive@odin.ietf.org; Tue, 18 May 2004 15:03:42 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4IJ3fH8007407
	for vrrp-archive@odin.ietf.org; Tue, 18 May 2004 15:03:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ9mB-0005HP-5a
	for vrrp-web-archive@optimus.ietf.org; Tue, 18 May 2004 14:57:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05604
	for <vrrp-web-archive@ietf.org>; Tue, 18 May 2004 14:57:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQ9m8-0007DM-CH
	for vrrp-web-archive@ietf.org; Tue, 18 May 2004 14:57:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ9lF-0007AI-00
	for vrrp-web-archive@ietf.org; Tue, 18 May 2004 14:56:21 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ9kl-00077Y-00
	for vrrp-web-archive@ietf.org; Tue, 18 May 2004 14:55:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ9aR-0003SH-Mo; Tue, 18 May 2004 14:45:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ9Sm-0001uC-3g
	for vrrp@optimus.ietf.org; Tue, 18 May 2004 14:37:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04461
	for <vrrp@ietf.org>; Tue, 18 May 2004 14:37:13 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQ9Sj-0005xY-CS
	for vrrp@ietf.org; Tue, 18 May 2004 14:37:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ9Rv-0005vW-00
	for vrrp@ietf.org; Tue, 18 May 2004 14:36:24 -0400
Received: from web50802.mail.yahoo.com ([206.190.38.111])
	by ietf-mx with smtp (Exim 4.12)
	id 1BQ9RT-0005rj-00
	for vrrp@ietf.org; Tue, 18 May 2004 14:35:55 -0400
Message-ID: <20040518181113.40927.qmail@web50802.mail.yahoo.com>
Received: from [66.243.153.70] by web50802.mail.yahoo.com via HTTP; Tue, 18 May 2004 11:11:13 PDT
Date: Tue, 18 May 2004 11:11:13 -0700 (PDT)
From: danny mitzel <danny_j_mitzel@yahoo.com>
Subject: RE: [VRRP] ARP Reply or Request
To: williams@calsoft.co.in, vrrp@ietf.org
In-Reply-To: <000201c43cc1$e745ea10$8c0210ac@calsoftwilliam>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


--- William StanisLaus <williams@calsoft.co.in> wrote:
> I have a quick question, What if any HOST/ROUTER in
> the SUBNET replys to Gratuitous ARP?? does the 
> ROUTER boardcasting Gratuitous ARP (REQUEST) will
> not take the IP (VRRP Virtual IP)  and will not
> become MASTER ??

I don't think the protocol specification mandates
any specific behavior.  any vrrp protocol issues that 
can lead to multiple vrrp routers adopting an 
address should be detected and reported at the vrrp 
level.  these are supposed to be covered in the 
vrrp message processing rules, error reporting 
requirements, and network management/snmp mib.

I think the more general problem of reliably detecting

and reporting any combination or host or router or
vrrp-enabled router on a subnet with duplicate 
addresses is outside the scope of vrrp.



	
		
__________________________________
Do you Yahoo!?
SBC Yahoo! - Internet access at a great low price.
http://promo.yahoo.com/sbc/

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



