
From stephen.nadas@ericsson.com  Mon Apr  6 15:10:43 2009
Return-Path: <stephen.nadas@ericsson.com>
X-Original-To: vrrp@core3.amsl.com
Delivered-To: vrrp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3BF843A6A2F for <vrrp@core3.amsl.com>; Mon,  6 Apr 2009 15:10:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KfD8SD7B+LxP for <vrrp@core3.amsl.com>; Mon,  6 Apr 2009 15:10:37 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id D57893A63CB for <vrrp@ietf.org>; Mon,  6 Apr 2009 15:10:37 -0700 (PDT)
Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se [138.85.77.50]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id n36MKNPC024363; Mon, 6 Apr 2009 17:20:23 -0500
Received: from eusrcmw720.eamcs.ericsson.se ([138.85.77.20]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 6 Apr 2009 17:11:33 -0500
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 6 Apr 2009 17:11:31 -0500
Message-ID: <DF78BDF6956FDD4780D5DAD88A073CF4017533A9@eusrcmw720.eamcs.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: May, should, must confusing section 7.1 vrrp 
Thread-Index: Acm3BKPHdUflj8j0SIWq9K5JSFRPkw==
From: "Stephen Nadas" <stephen.nadas@ericsson.com>
To: <dprovan@bivio.net>
X-OriginalArrivalTime: 06 Apr 2009 22:11:33.0002 (UTC) FILETIME=[A4D626A0:01C9B704]
Cc: M.Handley@cs.ucl.ac.uk, vrrp@ietf.org
Subject: [VRRP] May, should, must confusing section 7.1 vrrp
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vrrp>, <mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vrrp>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vrrp>, <mailto:vrrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Apr 2009 22:10:43 -0000

Hi Don,=20

I'm trying, once again, to clean this up.   Been busy elsewhere...=20

Mark H. pointed out:=20

> Section 7.1:
>=20
> - MAY verify that "Count IPvX Addrs" and the list of IPvX Address
>       matches the IPvX Address(es) configured for the VRID
>=20
>    If the above check fails, the receiver SHOULD log the event and MAY
>    indicate via network management that a misconfiguration=20
> was detected.
>    If the packet was not generated by the address owner (Priority does
>    not equal 255 (decimal)), the receiver MUST drop the packet,
>    otherwise continue processing.
>=20
> This combination of MAY, SHOULD and MUST is confusing.  Also=20
> it's not clear if the second "If" is conditional on the first=20
> "If".  It seems like you may have a mandatory action that you=20
> can't do unless you do an optional action.
>=20

So I agree it's confusing.  The text (from rfc, and -v6 and from
combined) all say the same.  In particular the immediately prior text
isn't much better:=20

      - MUST verify that the VRID is configured on the receiving
        interface and the local router is not the IPv6 Address owner
        (Priority equals 255 (decimal)).

   If any one of the above checks fails, the receiver MUST discard the
   packet, SHOULD log the event and SHOULD indicate via network
   management that an error occurred.

      - MAY verify that the IPv6 Address matches the IPv6_Address
(As above...)

So here's my questions:=20

1) the check that the _local router_ isn't the IPvX address owner need
not say anything about _Priority 255_.  Right?  That is confusing and
afaict irelevant (If I get an adv for an address I own I must drop  &
shld log) =20

2) I am confused about the check that the packet came from the address
owner.  (Why can't I can get an adv from a master who is not the address
owner, eg a dfferent backup for a down master address owner.) =20

Is this latter a stand alone check that is really needed? (or maybe some
text that has just been carried along?)  it doesn't seem to have
anything to do with the preceeding MAY (which seems to be essence of
Mark's comment.)=20

Thanks,
Steve=20

      =20

From stephen.nadas@ericsson.com  Mon Apr  6 16:12:52 2009
Return-Path: <stephen.nadas@ericsson.com>
X-Original-To: vrrp@core3.amsl.com
Delivered-To: vrrp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8495D3A6A96 for <vrrp@core3.amsl.com>; Mon,  6 Apr 2009 16:12:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E38ATZ4M+yz2 for <vrrp@core3.amsl.com>; Mon,  6 Apr 2009 16:12:51 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id D4DA43A68A0 for <vrrp@ietf.org>; Mon,  6 Apr 2009 16:12:51 -0700 (PDT)
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id n36NMbgk005666; Mon, 6 Apr 2009 18:22:39 -0500
Received: from eusrcmw720.eamcs.ericsson.se ([138.85.77.20]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 6 Apr 2009 18:13:50 -0500
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9B70D.585B3B09"
Date: Mon, 6 Apr 2009 18:13:49 -0500
Message-ID: <DF78BDF6956FDD4780D5DAD88A073CF40175344E@eusrcmw720.eamcs.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Is virtual mac a parameter? 
Thread-Index: Acm3DVf6p7CH55/LSja3DX6wBUcVog==
From: "Stephen Nadas" <stephen.nadas@ericsson.com>
To: <dprovan@bivio.net>
X-OriginalArrivalTime: 06 Apr 2009 23:13:50.0526 (UTC) FILETIME=[58930DE0:01C9B70D]
Cc: vrrp@ietf.org
Subject: [VRRP] Is virtual mac a parameter?
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vrrp>, <mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vrrp>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vrrp>, <mailto:vrrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Apr 2009 23:12:52 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9B70D.585B3B09
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable


Don,=20

One last item - Mark H mentioned:=20

> Section 6.1.  Should the VR MAC address be a parameter?  I=20
> think it should.
>

Your thoughts please.=20

Thanks,=20
Steve =20







------_=_NextPart_001_01C9B70D.585B3B09
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7654.12">
<TITLE>Is virtual mac a parameter? </TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Don, </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">One last item - Mark H mentioned: =
</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; Section 6.1.&nbsp; Should the VR =
MAC address be a parameter?&nbsp; I </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; think it should.</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt;</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Your thoughts please. </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Thanks, </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Steve&nbsp; </FONT>
</P>
<BR>
<BR>
<BR>
<BR>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C9B70D.585B3B09--

From Cathy.Zhou@Sun.COM  Thu Apr 16 14:22:08 2009
Return-Path: <Cathy.Zhou@Sun.COM>
X-Original-To: vrrp@core3.amsl.com
Delivered-To: vrrp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 26B8E3A6BBA for <vrrp@core3.amsl.com>; Thu, 16 Apr 2009 14:22:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.554
X-Spam-Level: 
X-Spam-Status: No, score=-4.554 tagged_above=-999 required=5 tests=[AWL=0.556,  BAYES_05=-1.11, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xv6-q0bKBu0P for <vrrp@core3.amsl.com>; Thu, 16 Apr 2009 14:22:07 -0700 (PDT)
Received: from sineb-mail-1.sun.com (sineb-mail-1.sun.com [192.18.19.6]) by core3.amsl.com (Postfix) with ESMTP id 0A6FD3A6D15 for <vrrp@ietf.org>; Thu, 16 Apr 2009 14:22:06 -0700 (PDT)
Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3GLNC9N018328 for <vrrp@ietf.org>; Thu, 16 Apr 2009 21:23:19 GMT
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KI700J00PPCXO00@mail-apac.sun.com> for vrrp@ietf.org; Fri, 17 Apr 2009 05:23:12 +0800 (SGT)
Received: from [129.146.108.16] ([unknown] [129.146.108.16]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KI700K8UQ2N0QD0@mail-apac.sun.com> for vrrp@ietf.org; Fri, 17 Apr 2009 05:23:12 +0800 (SGT)
Date: Thu, 16 Apr 2009 14:22:17 -0700
From: Cathy Zhou <Cathy.Zhou@Sun.COM>
Sender: Cathy.Zhou@Sun.COM
To: vrrp@ietf.org
Message-id: <49E7A189.7010408@sun.com>
User-Agent: Thunderbird 2.0.0.12 (X11/20080422)
Subject: [VRRP] question about the primary IP address
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vrrp>, <mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vrrp>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vrrp>, <mailto:vrrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Apr 2009 21:23:31 -0000

Hi,

I am trying to understand how this primary IP address works. In the draft 
(vrrp-unified-spec-02), it says this IP address is "selected from the set 
of real interface addresses". But this IP address is also used as the 
source IP address for the VRRP protocol advertisement packets (multicast) 
in which the mac address is set to the virtual MAC address.

I don't understand how this would work without causing any confusion. If 
this is a real interface address, can it be used by any other application 
other than the VRRP protocol? Do we suppose to respond to an ARP for this 
IP address using the real physical MAC address? But the neighbor bridges 
would already learnt that this IP maps to the virtual MAC address from the 
VRRP advertisement packet...

Thanks
- Cathy

From Cathy.Zhou@Sun.COM  Thu Apr 16 17:36:53 2009
Return-Path: <Cathy.Zhou@Sun.COM>
X-Original-To: vrrp@core3.amsl.com
Delivered-To: vrrp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C3C4E3A6885 for <vrrp@core3.amsl.com>; Thu, 16 Apr 2009 17:36:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.918
X-Spam-Level: 
X-Spam-Status: No, score=-5.918 tagged_above=-999 required=5 tests=[AWL=0.682,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MtwWTcxVy8kN for <vrrp@core3.amsl.com>; Thu, 16 Apr 2009 17:36:52 -0700 (PDT)
Received: from sineb-mail-2.sun.com (sineb-mail-2.sun.com [192.18.19.7]) by core3.amsl.com (Postfix) with ESMTP id D89E53A6831 for <vrrp@ietf.org>; Thu, 16 Apr 2009 17:36:47 -0700 (PDT)
Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3H0bhOO020349 for <vrrp@ietf.org>; Fri, 17 Apr 2009 00:37:56 GMT
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KI700L00Z1HZ100@mail-apac.sun.com> for vrrp@ietf.org; Fri, 17 Apr 2009 08:37:43 +0800 (SGT)
Received: from [129.146.108.16] ([unknown] [129.146.108.16]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KI700KSSZ2U0QF0@mail-apac.sun.com>; Fri, 17 Apr 2009 08:37:43 +0800 (SGT)
Date: Thu, 16 Apr 2009 17:36:49 -0700
From: Cathy Zhou <Cathy.Zhou@Sun.COM>
In-reply-to: <D83235F0F3C86D4D889D8B9A0DA8C6D7043CA7A0@corpexc01.corp.networkrobots.com>
Sender: Cathy.Zhou@Sun.COM
To: Don Provan <dprovan@bivio.net>
Message-id: <49E7CF21.5050507@Sun.COM>
References: <49E7A189.7010408@sun.com> <D83235F0F3C86D4D889D8B9A0DA8C6D7043CA7A0@corpexc01.corp.networkrobots.com>
User-Agent: Thunderbird 2.0.0.12 (X11/20080422)
Cc: vrrp@ietf.org
Subject: Re: [VRRP] question about the primary IP address
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vrrp>, <mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vrrp>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vrrp>, <mailto:vrrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Apr 2009 00:36:53 -0000

Don,

Thanks very much for your reply. See more inline:

> ARP packets involving the VR IP address should always, always map
> it to the VR MAC address, never ever to the physical MAC address.
> My implementation went out of its way to avoid any ARP packets
> mapping it to the physical MAC during system initialization before
> VRRP was started because such errant mappings caused us so much
> trouble.
> 
> The VR IP address owner can use the address normally. It turns out
> that it can (and I would say should) use its physical MAC address as
> the source in all ethernet packets *except* the VRRP advertisements.
> In VR advertisements, it must use the VR MAC address as the source.
> 
> Bridges will learn about both MAC addresses, but all IP traffic will
> be sent to the VR MAC address.
> 
I see.

> By the way, personally, when I deployed VRRP, I found that an "owner"
> was more trouble than it was worth, so I always invented a new VR IP
> address that no one used except when they were the VR master, i.e.,
> an address that *wasn't* a real interface address anywhere.
> 
... and the only purpose of this IP Address is being used as the source IP 
address in the VR advertisement?

What exactly problem did you see when you use one of the "owned" addresses 
to send the advertisement?

One more question regarding the read of section 7.4. In the IPv6 case, the 
primary link local IPv6 address used as the VR advertisement source 
address should be formed by the physical MAC addresses, is this correct? 
Also, it sounds like that the first protected IPv6 address embedded in the 
advertisement can be formed by the virtual MAC address?

Thanks
- Cathy

> -don
> 
> -----Original Message-----
> From: vrrp-bounces@ietf.org [mailto:vrrp-bounces@ietf.org] On Behalf Of
> Cathy Zhou
> Sent: Thursday, April 16, 2009 2:22 PM
> To: vrrp@ietf.org
> Subject: [VRRP] question about the primary IP address
> 
> Hi,
> 
> I am trying to understand how this primary IP address works. In the
> draft 
> (vrrp-unified-spec-02), it says this IP address is "selected from the
> set 
> of real interface addresses". But this IP address is also used as the 
> source IP address for the VRRP protocol advertisement packets
> (multicast) 
> in which the mac address is set to the virtual MAC address.
> 
> I don't understand how this would work without causing any confusion. If
> 
> this is a real interface address, can it be used by any other
> application 
> other than the VRRP protocol? Do we suppose to respond to an ARP for
> this 
> IP address using the real physical MAC address? But the neighbor bridges
> 
> would already learnt that this IP maps to the virtual MAC address from
> the 
> VRRP advertisement packet...
> 
> Thanks
> - Cathy
> _______________________________________________
> vrrp mailing list
> vrrp@ietf.org
> https://www.ietf.org/mailman/listinfo/vrrp


From Cathy.Zhou@Sun.COM  Fri Apr 17 11:51:19 2009
Return-Path: <Cathy.Zhou@Sun.COM>
X-Original-To: vrrp@core3.amsl.com
Delivered-To: vrrp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 20E453A6A9E for <vrrp@core3.amsl.com>; Fri, 17 Apr 2009 11:51:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.088
X-Spam-Level: 
X-Spam-Status: No, score=-6.088 tagged_above=-999 required=5 tests=[AWL=0.511,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PZTyyyM5eSaq for <vrrp@core3.amsl.com>; Fri, 17 Apr 2009 11:51:18 -0700 (PDT)
Received: from sineb-mail-1.sun.com (sineb-mail-1.sun.com [192.18.19.6]) by core3.amsl.com (Postfix) with ESMTP id EF6A93A6E39 for <vrrp@ietf.org>; Fri, 17 Apr 2009 11:50:46 -0700 (PDT)
Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3HIpj08015164 for <vrrp@ietf.org>; Fri, 17 Apr 2009 18:51:59 GMT
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KI900I00DFGWD00@mail-apac.sun.com> for vrrp@ietf.org; Sat, 18 Apr 2009 02:51:45 +0800 (SGT)
Received: from [129.146.108.16] ([unknown] [129.146.108.16]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KI90025VDQ74930@mail-apac.sun.com>; Sat, 18 Apr 2009 02:51:45 +0800 (SGT)
Date: Fri, 17 Apr 2009 11:50:49 -0700
From: Cathy Zhou <Cathy.Zhou@Sun.COM>
In-reply-to: <D83235F0F3C86D4D889D8B9A0DA8C6D7043CA859@corpexc01.corp.networkrobots.com>
Sender: Cathy.Zhou@Sun.COM
To: Don Provan <dprovan@bivio.net>
Message-id: <49E8CF89.4000306@Sun.COM>
References: <49E7A189.7010408@sun.com> <D83235F0F3C86D4D889D8B9A0DA8C6D7043CA7A0@corpexc01.corp.networkrobots.com> <49E7CF21.5050507@Sun.COM> <D83235F0F3C86D4D889D8B9A0DA8C6D7043CA859@corpexc01.corp.networkrobots.com>
User-Agent: Thunderbird 2.0.0.12 (X11/20080422)
Cc: vrrp@ietf.org
Subject: Re: [VRRP] question about the primary IP address
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vrrp>, <mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vrrp>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vrrp>, <mailto:vrrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Apr 2009 18:51:19 -0000

> It turns out that the VR IP address should *not* be the source IP
> address
> in the VR advertisement: an address the router owns should be used.
> (Obviously these overlap for the VR IP address owner.) 

That is exactly what confuses me: For the VR IP address owner, can we 
or can we not use that VR IP address as the source IP address of VR 
advertisement?

Thanks
- Cathy
