
From psandhya81@yahoo.com  Thu Oct 17 22:30:16 2013
Return-Path: <psandhya81@yahoo.com>
X-Original-To: vrrp@ietfa.amsl.com
Delivered-To: vrrp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2816521F9FF2 for <vrrp@ietfa.amsl.com>; Thu, 17 Oct 2013 22:30:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p2JXjiOFAsfJ for <vrrp@ietfa.amsl.com>; Thu, 17 Oct 2013 22:30:10 -0700 (PDT)
Received: from nm31.bullet.mail.ne1.yahoo.com (nm31.bullet.mail.ne1.yahoo.com [98.138.229.24]) by ietfa.amsl.com (Postfix) with SMTP id 5D2D321F9D1C for <vrrp@ietf.org>; Thu, 17 Oct 2013 22:30:10 -0700 (PDT)
Received: from [127.0.0.1] by nm31.bullet.mail.ne1.yahoo.com with NNFMP; 18 Oct 2013 05:30:10 -0000
Received: from [98.138.101.128] by nm31.bullet.mail.ne1.yahoo.com with NNFMP; 18 Oct 2013 05:27:22 -0000
Received: from [98.139.212.150] by tm16.bullet.mail.ne1.yahoo.com with NNFMP; 18 Oct 2013 05:27:22 -0000
Received: from [98.139.212.198] by tm7.bullet.mail.bf1.yahoo.com with NNFMP; 18 Oct 2013 05:27:22 -0000
Received: from [127.0.0.1] by omp1007.mail.bf1.yahoo.com with NNFMP; 18 Oct 2013 05:27:22 -0000
X-Yahoo-Newman-Property: ymail-4
X-Yahoo-Newman-Id: 161318.21897.bm@omp1007.mail.bf1.yahoo.com
Received: (qmail 37402 invoked by uid 60001); 18 Oct 2013 05:27:22 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1382074041; bh=Ro58vHki9KjuaxIENjN2LkcFB3k6Jw4kOJjGpHq4D2Y=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=4pPnmPIR4A3svRwqrbKHZSo0R/18rOoZQ6LlO0nMdAhS2x4u1QtRj503tfzt7t0pN4aLWZ7Vh5C5FkOuH8lZUYZfHh49S2P+auCDh7t82F8e7z4U0Vtk1K/th65UZ+ewqwEWN/vYT1eNaqqfezr/7GuC9Xqx00E+4cWU3+n9994=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=H6XUE3S/fclx6nyG7MG5/Gvn252T68TZzQ5rerRmwtWJwshi88GfKXANa2wGOQLxfEf0ggyNndeysvN3qRIlE7JbBTpZvVthlYDiS6FZMBEAitSEwslyEJ0AsTunWMvxWbnJS79ln/+y7CYegKmNuyjw7GjzmOKVOesQYLl1518=;
X-YMail-OSG: ObZ1KWUVM1nJaHwUHWix7X1vYnzQptMywcF6FQLmxSbh.NT cjemtDN1IDFbQAC54s6WpMlrWlM0z4BZv.tp9i8kzPOtQEFbOi_zH7cywMMf 5ImIqsfOOqOySVP53FxK_6vxZPoJJxIuQ0WbJWudv7OeQhAFQvWiQs2W1M7n z9SIprfmr1bUuGKa4QQeh7FlfNWBPBEW98lhZrB6aYiekfTS4IPtMOX20Ieo 3b9TThHyGEw0eZAK1tWzGCUvOvLmOYl.wwlo2qBREyefuSb_Gd4Ydqc9LXDW ltwH0UDshPFlfQIv4pkkMpx4Oq9V3lLE_Ch26aLLQderThGnzaP34r04.KT. nQvLUy3B4DDvh4Eubl5CS410jaFQp1jl_hfn0pgqv.2Tnsa7tqs5vzvOVvRx fhDRe3COgvETknJT2DphiVx64tCxy6ixy1KGiUGRLEWJZmYKBfW9CsNR5U41 pAnbH8jfVlhr508XpsA801FnAZZVGmsqQBpRieRyh.eAIQVIVTXJmagtgwqD gV3UfGfGJqCyk6ERonj3gwzpK7E6AWvBYTqeIymZv1kY7Yy8SmIkV2IicByK tvIw1RGR4kNP16dwBlqVYsCRFzkiuQXYxDOnO5dmwbYwBYE7Ni3pmO2v52nm qccaJTQ5xZ6yXioyqLi.E_aaD2ItruuokY.dVPrTK3eSh9ssGNhHWqfvgx0p dHRoT5P1HYUkSSZtNdq_3M1iXyA--
Received: from [203.91.201.57] by web160103.mail.bf1.yahoo.com via HTTP; Thu, 17 Oct 2013 22:27:21 PDT
X-Rocket-MIMEInfo: 002.001, CgpIaSwKCgpDb25zaWRlciB0aGUgYmVsb3cgdG9wb2xvZ3ksCkRVVDEgLS0tLS0gRFVUMgoKQ29uZmlndXJlZCBEVVQxIGFzIG93bmVyIHdpdGggdmlwIGFzIGZlODA6OmNhMzU6YjhmZjpmZWE4OjgyZmQuCkFuZCBjb25maWd1cmVkIERVVDIgYXMgbm90LW93bmVyIHdpdGggdmlwIGFzIGZlODA6OmNhMzU6YjhmZjpmZWE4OjgyMTIKClZJUCBvbiBEVVQxIGFuZCBEVVQyIGFyZSBkaWZmZXJlbnQuCgpXaGF0IHNob3VsZCBiZSB0aGUgc3RhdGVzIG9mIERVVDEgJiBEVVQyPwoKQWNjb3JkaW5nIHRvIGRyYWZ0IGgBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.160.587
References: <1382011510.94007.YahooMailBasic@web160102.mail.bf1.yahoo.com> <1382072525.97794.YahooMailNeo@web160102.mail.bf1.yahoo.com>
Message-ID: <1382074041.37205.YahooMailNeo@web160103.mail.bf1.yahoo.com>
Date: Thu, 17 Oct 2013 22:27:21 -0700 (PDT)
From: Sandhya Puppala <psandhya81@yahoo.com>
To: "vrrp@ietf.org" <vrrp@ietf.org>
In-Reply-To: <1382072525.97794.YahooMailNeo@web160102.mail.bf1.yahoo.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="1520606428-2142470677-1382074041=:37205"
Subject: [VRRP] VRRP IPV6 Session Configuration with different link local addresses (as VIP)
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Sandhya Puppala <psandhya81@yahoo.com>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vrrp>, <mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vrrp>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vrrp>, <mailto:vrrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Oct 2013 05:30:16 -0000

--1520606428-2142470677-1382074041=:37205
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

=0A=0AHi,=0A=0A=0AConsider the below topology,=0ADUT1 ----- DUT2=0A=0AConfi=
gured DUT1 as owner with vip as fe80::ca35:b8ff:fea8:82fd.=0AAnd configured=
 DUT2 as not-owner with vip as fe80::ca35:b8ff:fea8:8212=0A=0AVIP on DUT1 a=
nd DUT2 are different.=0A=0AWhat should be the states of DUT1 & DUT2?=0A=0A=
According to draft http://tools.ietf.org/html/draft-ietf-vrrp-ipv6-spec-07=
=0Asection 7.1, =0A=0AIf the packet was not generated by the address owner=
=0A(Priority does not equal 255 (decimal)), the receiver MUST drop the=0Apa=
cket, otherwise continue processing.=0A=0A1. Does it need to compare the vi=
p address of received packet and its vip address?=0A=A0=A0=A0 If there are =
different what need to be done?=0A=0AAs per RFC "DUT2 should accept the pac=
ket from DUT1".=0ADoes this mean DUT2 state should become backup?=0A=0A=0A=
=0AThanks,=0ASandhya
--1520606428-2142470677-1382074041=:37205
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:He=
lveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;fo=
nt-size:12pt"><div style=3D"display: block;" class=3D"yahoo_quoted"> <div s=
tyle=3D"font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucid=
a Grande, sans-serif; font-size: 12pt;"><div style=3D"font-family: Helvetic=
aNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-si=
ze: 12pt;"><br><div class=3D"y_msg_container"><div id=3D"yiv7502092840"><di=
v><div style=3D"color:#000;background-color:#fff;font-family:HelveticaNeue,=
 Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:12pt=
;"><div class=3D"yiv7502092840yahoo_quoted" style=3D"display:block;"><div s=
tyle=3D"font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida=
 Grande, sans-serif;font-size:12pt;"><div style=3D"font-family:HelveticaNeu=
e, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:12=
pt;">Hi,<br
 clear=3D"none"><div class=3D"yiv7502092840y_msg_container"><br clear=3D"no=
ne">Consider the below topology,<br clear=3D"none">DUT1 ----- DUT2<br clear=
=3D"none"><br clear=3D"none">Configured DUT1 as owner with vip as fe80::ca3=
5:b8ff:fea8:82fd.<br clear=3D"none">And configured DUT2 as not-owner with v=
ip as fe80::ca35:b8ff:fea8:8212<br clear=3D"none"><br clear=3D"none">VIP on=
 DUT1 and DUT2 are different.<br clear=3D"none"><br clear=3D"none">What sho=
uld be the states of DUT1 &amp; DUT2?<br clear=3D"none"><br clear=3D"none">=
According to draft <a rel=3D"nofollow" shape=3D"rect" target=3D"_blank" hre=
f=3D"http://tools.ietf.org/html/draft-ietf-vrrp-ipv6-spec-07">http://tools.=
ietf.org/html/draft-ietf-vrrp-ipv6-spec-07</a><br clear=3D"none">section 7.=
1,=0A <br clear=3D"none"><br clear=3D"none">If the packet was not generated=
 by the address owner<br clear=3D"none">(Priority does not equal 255 (decim=
al)), the receiver MUST drop the<br clear=3D"none">packet, otherwise contin=
ue processing.<br clear=3D"none"><br clear=3D"none">1. Does it need to comp=
are the vip address of received packet and its vip address?<br clear=3D"non=
e">&nbsp;&nbsp;&nbsp; If there are different what need to be done?<br clear=
=3D"none"><br clear=3D"none">As per RFC "DUT2 should accept the packet from=
 DUT1".<br clear=3D"none">Does this mean DUT2 state should become backup?<d=
iv class=3D"yiv7502092840yqt3430818775" id=3D"yiv7502092840yqtfd56270"><br =
clear=3D"none"><br clear=3D"none"><br clear=3D"none">Thanks,<br clear=3D"no=
ne">Sandhya<br clear=3D"none"><br clear=3D"none"><br clear=3D"none"></div><=
/div><div class=3D"yiv7502092840yqt3430818775" id=3D"yiv7502092840yqtfd5697=
0">  </div></div><div class=3D"yiv7502092840yqt3430818775" id=3D"yiv7502092=
840yqtfd05332"> </div></div><div
 class=3D"yiv7502092840yqt3430818775" id=3D"yiv7502092840yqtfd35409">  </di=
v></div><div class=3D"yiv7502092840yqt3430818775" id=3D"yiv7502092840yqtfd6=
7084"> </div></div></div></div><br><br></div>  </div> </div>  </div> </div>=
</body></html>
--1520606428-2142470677-1382074041=:37205--

From tperiyannan@extremenetworks.com  Fri Oct 18 12:36:03 2013
Return-Path: <tperiyannan@extremenetworks.com>
X-Original-To: vrrp@ietfa.amsl.com
Delivered-To: vrrp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58A3D11E81B8 for <vrrp@ietfa.amsl.com>; Fri, 18 Oct 2013 12:36:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S9KVHZwX5Z2i for <vrrp@ietfa.amsl.com>; Fri, 18 Oct 2013 12:35:59 -0700 (PDT)
Received: from usnc-casht-p1.extremenetworks.com (usnc-casht-p2.extremenetworks.com [12.38.15.167]) by ietfa.amsl.com (Postfix) with ESMTP id 74E5A11E82B9 for <vrrp@ietf.org>; Fri, 18 Oct 2013 12:35:58 -0700 (PDT)
Received: from inch-casht-p2.corp.extremenetworks.com (10.120.89.29) by USNC-CASHT-P1.corp.extremenetworks.com (10.6.17.63) with Microsoft SMTP Server (TLS) id 14.3.123.3; Fri, 18 Oct 2013 12:35:57 -0700
Received: from INEXCHANGE.corp.extremenetworks.com ([192.168.131.111]) by inch-casht-p2.corp.extremenetworks.com ([10.120.89.29]) with mapi; Sat, 19 Oct 2013 00:57:04 +0530
From: Thirumavalavan Periyannan <tperiyannan@extremenetworks.com>
To: "vrrp@ietf.org" <vrrp@ietf.org>
Date: Sat, 19 Oct 2013 01:02:02 +0530
Thread-Topic: vrrp Digest, Vol 88, Issue 1
Thread-Index: Ac7MNLlZ59a+hVLcSZ6Rd9/w3STvSwAAwY4Q
Message-ID: <617438426768D648ABBC00E677AA0149028C9A0DF814@INEXCHANGE.corp.extremenetworks.com>
References: <mailman.64.1382122881.5048.vrrp@ietf.org>
In-Reply-To: <mailman.64.1382122881.5048.vrrp@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_617438426768D648ABBC00E677AA0149028C9A0DF814INEXCHANGEc_"
MIME-Version: 1.0
Subject: Re: [VRRP] vrrp Digest, Vol 88, Issue 1
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vrrp>, <mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vrrp>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vrrp>, <mailto:vrrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Oct 2013 19:36:03 -0000

--_000_617438426768D648ABBC00E677AA0149028C9A0DF814INEXCHANGEc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,



Yes, If Virtual IP (including link local) is different for specific VRID th=
en it will be DUAL Master State on DUT1 & DUT2 routers.


Thanks & Regards,
Thirumavalavan Periyannan
Associate SQA Engineer, Extreme Networks



-----Original Message-----
From: vrrp-bounces@ietf.org [mailto:vrrp-bounces@ietf.org] On Behalf Of vrr=
p-request@ietf.org
Sent: Saturday, October 19, 2013 12:31 AM
To: vrrp@ietf.org
Subject: vrrp Digest, Vol 88, Issue 1



If you have received this digest without all the individual message attachm=
ents you will need to update your digest options in your list subscription.=
  To do so, go to



https://www.ietf.org/mailman/listinfo/vrrp



Click the 'Unsubscribe or edit options' button, log in, and set "Get MIME o=
r Plain Text Digests?" to MIME.  You can set this option globally for all t=
he list digests you receive at this point.







Send vrrp mailing list submissions to

            vrrp@ietf.org<mailto:vrrp@ietf.org>



To subscribe or unsubscribe via the World Wide Web, visit

            https://www.ietf.org/mailman/listinfo/vrrp

or, via email, send a message with subject or body 'help' to

            vrrp-request@ietf.org<mailto:vrrp-request@ietf.org>



You can reach the person managing the list at

            vrrp-owner@ietf.org<mailto:vrrp-owner@ietf.org>



When replying, please edit your Subject line so it is more specific than "R=
e: Contents of vrrp digest..."





Today's Topics:



   1. VRRP IPV6 Session Configuration with different link local

      addresses (as VIP) (Sandhya Puppala)





----------------------------------------------------------------------



Message: 1

Date: Thu, 17 Oct 2013 22:27:21 -0700 (PDT)

From: Sandhya Puppala <psandhya81@yahoo.com>

To: "vrrp@ietf.org" <vrrp@ietf.org>

Subject: [VRRP] VRRP IPV6 Session Configuration with different link

            local     addresses (as VIP)

Message-ID:

            <1382074041.37205.YahooMailNeo@web160103.mail.bf1.yahoo.com>

Content-Type: text/plain; charset=3D"iso-8859-1"







Hi,





Consider the below topology,

DUT1 ----- DUT2



Configured DUT1 as owner with vip as fe80::ca35:b8ff:fea8:82fd.

And configured DUT2 as not-owner with vip as fe80::ca35:b8ff:fea8:8212



VIP on DUT1 and DUT2 are different.



What should be the states of DUT1 & DUT2?



According to draft http://tools.ietf.org/html/draft-ietf-vrrp-ipv6-spec-07

section 7.1,



If the packet was not generated by the address owner (Priority does not equ=
al 255 (decimal)), the receiver MUST drop the packet, otherwise continue pr=
ocessing.



1. Does it need to compare the vip address of received packet and its vip a=
ddress?

??? If there are different what need to be done?



As per RFC "DUT2 should accept the packet from DUT1".

Does this mean DUT2 state should become backup?







Thanks,

Sandhya

-------------- next part --------------

An HTML attachment was scrubbed...

URL: <http://www.ietf.org/mail-archive/web/vrrp/attachments/20131017/5babdb=
8d/attachment.htm>



------------------------------



_______________________________________________

vrrp mailing list

vrrp@ietf.org<mailto:vrrp@ietf.org>

https://www.ietf.org/mailman/listinfo/vrrp





End of vrrp Digest, Vol 88, Issue 1

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

________________________________
DISCLAIMER:
This e-mail and any attachments to it may contain confidential and propriet=
ary material and is solely for the use of the intended recipient. Any revie=
w, use, disclosure, distribution or copying of this transmittal is prohibit=
ed except by or on behalf of the intended recipient. If you have received t=
his transmittal in error, please notify the sender and destroy this e-mail =
and any attachments and all copies, whether electronic or printed.

--_000_617438426768D648ABBC00E677AA0149028C9A0DF814INEXCHANGEc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Tahoma","sans-serif";
	color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Tahoma","sans-serif";
	color:black;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText"><span style=3D"font-family:&quot;Verdana&quot;,&q=
uot;sans-serif&quot;">Hi,<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-family:&quot;Verdana&quot;,&q=
uot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-family:&quot;Verdana&quot;,&q=
uot;sans-serif&quot;">Yes, If Virtual IP (including link local) is differen=
t for specific VRID then it will be DUAL Master State on DUT1 &amp; DUT2 ro=
uters.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-family:&quot;Verdana&quot;,&q=
uot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt">Thanks &amp; Regard=
s,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;color:#7030A0">Th=
irumavalavan
</span></b><b><span style=3D"font-size:10.0pt;color:#00B050">Periyannan<o:p=
></o:p></span></b></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt">Associate SQA En=
gineer, Extreme Networks
</span></b><span style=3D"font-size:10.0pt"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">-----Original Message-----<br>
From: vrrp-bounces@ietf.org [mailto:vrrp-bounces@ietf.org] On Behalf Of vrr=
p-request@ietf.org<br>
Sent: Saturday, October 19, 2013 12:31 AM<br>
To: vrrp@ietf.org<br>
Subject: vrrp Digest, Vol 88, Issue 1</p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">If you have received this digest without all the =
individual message attachments you will need to update your digest options =
in your list subscription.&nbsp; To do so, go to
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><a href=3D"https://www.ietf.org/mailman/listinfo/=
vrrp"><span style=3D"color:black;text-decoration:none">https://www.ietf.org=
/mailman/listinfo/vrrp</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Click the 'Unsubscribe or edit options' button, l=
og in, and set &quot;Get MIME or Plain Text Digests?&quot; to MIME.&nbsp; Y=
ou can set this option globally for all the list digests you receive at thi=
s point.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Send vrrp mailing list submissions to<o:p></o:p><=
/p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; <a href=3D"mailto:vrrp@ietf.org"><span style=3D"color:bla=
ck;text-decoration:none">vrrp@ietf.org</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">To subscribe or unsubscribe via the World Wide We=
b, visit<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; <a href=3D"https://www.ietf.org/mailman/listinfo/vrrp">
<span style=3D"color:black;text-decoration:none">https://www.ietf.org/mailm=
an/listinfo/vrrp</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText">or, via email, send a message with subject or bod=
y 'help' to<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; <a href=3D"mailto:vrrp-request@ietf.org"><span style=3D"c=
olor:black;text-decoration:none">vrrp-request@ietf.org</span></a><o:p></o:p=
></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">You can reach the person managing the list at<o:p=
></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; <a href=3D"mailto:vrrp-owner@ietf.org"><span style=3D"col=
or:black;text-decoration:none">vrrp-owner@ietf.org</span></a><o:p></o:p></p=
>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">When replying, please edit your Subject line so i=
t is more specific than &quot;Re: Contents of vrrp digest...&quot;<o:p></o:=
p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Today's Topics:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; 1. VRRP IPV6 Session Configuration w=
ith different link local<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; addresses (as VIP)=
 (Sandhya Puppala)<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">-------------------------------------------------=
---------------------<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Message: 1<o:p></o:p></p>
<p class=3D"MsoPlainText">Date: Thu, 17 Oct 2013 22:27:21 -0700 (PDT)<o:p><=
/o:p></p>
<p class=3D"MsoPlainText">From: Sandhya Puppala &lt;psandhya81@yahoo.com&gt=
;<o:p></o:p></p>
<p class=3D"MsoPlainText">To: &quot;vrrp@ietf.org&quot; &lt;vrrp@ietf.org&g=
t;<o:p></o:p></p>
<p class=3D"MsoPlainText">Subject: [VRRP] VRRP IPV6 Session Configuration w=
ith different link<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; local&nbsp;&nbsp;&nbsp;&nbsp; addresses (as VIP)<o:p></o:=
p></p>
<p class=3D"MsoPlainText">Message-ID:<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; &lt;1382074041.37205.YahooMailNeo@web160103.mail.bf1.yaho=
o.com&gt;<o:p></o:p></p>
<p class=3D"MsoPlainText">Content-Type: text/plain; charset=3D&quot;iso-885=
9-1&quot;<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Hi,<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Consider the below topology,<o:p></o:p></p>
<p class=3D"MsoPlainText">DUT1 ----- DUT2<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Configured DUT1 as owner with vip as fe80::ca35:b=
8ff:fea8:82fd.<o:p></o:p></p>
<p class=3D"MsoPlainText">And configured DUT2 as not-owner with vip as fe80=
::ca35:b8ff:fea8:8212<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">VIP on DUT1 and DUT2 are different.<o:p></o:p></p=
>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">What should be the states of DUT1 &amp; DUT2?<o:p=
></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">According to draft <a href=3D"http://tools.ietf.o=
rg/html/draft-ietf-vrrp-ipv6-spec-07">
<span style=3D"color:black;text-decoration:none">http://tools.ietf.org/html=
/draft-ietf-vrrp-ipv6-spec-07</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText">section 7.1, <o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">If the packet was not generated by the address ow=
ner (Priority does not equal 255 (decimal)), the receiver MUST drop the pac=
ket, otherwise continue processing.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">1. Does it need to compare the vip address of rec=
eived packet and its vip address?<o:p></o:p></p>
<p class=3D"MsoPlainText">??? If there are different what need to be done?<=
o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">As per RFC &quot;DUT2 should accept the packet fr=
om DUT1&quot;.<o:p></o:p></p>
<p class=3D"MsoPlainText">Does this mean DUT2 state should become backup?<o=
:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Thanks,<o:p></o:p></p>
<p class=3D"MsoPlainText">Sandhya<o:p></o:p></p>
<p class=3D"MsoPlainText">-------------- next part --------------<o:p></o:p=
></p>
<p class=3D"MsoPlainText">An HTML attachment was scrubbed...<o:p></o:p></p>
<p class=3D"MsoPlainText">URL: &lt;<a href=3D"http://www.ietf.org/mail-arch=
ive/web/vrrp/attachments/20131017/5babdb8d/attachment.htm"><span style=3D"c=
olor:black;text-decoration:none">http://www.ietf.org/mail-archive/web/vrrp/=
attachments/20131017/5babdb8d/attachment.htm</span></a>&gt;<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">------------------------------<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">_______________________________________________<o=
:p></o:p></p>
<p class=3D"MsoPlainText">vrrp mailing list<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"mailto:vrrp@ietf.org"><span style=3D"c=
olor:black;text-decoration:none">vrrp@ietf.org</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"https://www.ietf.org/mailman/listinfo/=
vrrp"><span style=3D"color:black;text-decoration:none">https://www.ietf.org=
/mailman/listinfo/vrrp</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">End of vrrp Digest, Vol 88, Issue 1<o:p></o:p></p=
>
<p class=3D"MsoPlainText">***********************************<o:p></o:p></p=
>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"2">DISCLAIMER:<br>
This e-mail and any attachments to it may contain confidential and propriet=
ary material and is solely for the use of the intended recipient. Any revie=
w, use, disclosure, distribution or copying of this transmittal is prohibit=
ed except by or on behalf of the
 intended recipient. If you have received this transmittal in error, please=
 notify the sender and destroy this e-mail and any attachments and all copi=
es, whether electronic or printed.<br>
</font>
</body>
</html>

--_000_617438426768D648ABBC00E677AA0149028C9A0DF814INEXCHANGEc_--

From sreenatha.setty@ibtechnology.com  Sat Oct 19 00:07:14 2013
Return-Path: <sreenatha.setty@ibtechnology.com>
X-Original-To: vrrp@ietfa.amsl.com
Delivered-To: vrrp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA7EF11E8136 for <vrrp@ietfa.amsl.com>; Sat, 19 Oct 2013 00:07:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_33=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TmepjX8Q0QTf for <vrrp@ietfa.amsl.com>; Sat, 19 Oct 2013 00:07:10 -0700 (PDT)
Received: from ipinternal.indiabulls.com (ipinternal.indiabulls.com [202.54.119.192]) by ietfa.amsl.com (Postfix) with ESMTP id C760721F9E01 for <vrrp@ietf.org>; Sat, 19 Oct 2013 00:07:08 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqQEADUuYlKsEMj1/2dsb2JhbABagz+sHZIaS4E7dIIlAQEBAQMBAQEtCjQLEgEIDQQDAQILBg4KByYeCgkBBAsDBQgBh2sDG7YwA4l1jGaBHhmBCDENgxmBCgOJPYxngxSLIYhjgWk
X-IronPort-AV: E=Sophos;i="4.93,527,1378837800"; d="scan'208";a="34354464"
Received: from GRGHEXCHANGE.grgh.indiabulls.com (172.16.200.21) by GGN-ICAS.grgh.indiabulls.com (172.16.200.245) with Microsoft SMTP Server id 14.3.123.3; Sat, 19 Oct 2013 12:36:49 +0530
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"
Date: Sat, 19 Oct 2013 12:36:50 +0530
Message-ID: <DB36B077CF387C4989BCC57D685FA30102F2BF4D@GRGHEXCHANGE.grgh.indiabulls.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: : [VRRP] VRRP IPV6 Session Configuration with different link
Thread-Index: Ac7MltKzg5YQLaPoTeWzV0zMIQzcvA==
From: Sreenatha Setty <sreenatha.setty@ibtechnology.com>
To: <vrrp@ietf.org>
Content-Transfer-Encoding: quoted-printable
Cc: psandhya81@yahoo.com
Subject: Re: [VRRP] :  VRRP IPV6 Session Configuration with different link
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vrrp>, <mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vrrp>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vrrp>, <mailto:vrrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Oct 2013 07:07:14 -0000

Hi Sandhya,
     Normally Vendors will implement based on the standard RFC not on
the draft version, since drafts can undergo changes very frequently. I
am not sure for what reason you are referring that particular draft. =

I suggest you to refer latest VRRP v3 RFC: 5798 for better
understanding.

Coming to your query,  according to latest RFC 5798( section 7.1), " 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" condition is removed.  So router can accept vrrp
packets even if it is generated by other than the address owner if all
other conditions are met. (Mentioned in the above sections 7.1 of RFC
5798)

In your case, you mentioned different VIPs are configured. In the same
section only,  RFC tells, =

      - MAY verify that "Count IPvX Addrs" and the list of IPvX
      address(es) match the IPvX Address(es) configured for the VRID.

So according to this logic, both DUTs will discard the vrrp packets
since VIP address are different and both DUTs will become VRRP Masters.

And standard VRRP MIB(RFC 6527) specifies one statistics object to
represent these kind of address list errors:

vrrpv3StatisticsAddressListErrors OBJECT-TYPE
           SYNTAX       Counter64
           MAX-ACCESS   read-only
           STATUS       current
           DESCRIPTION
               "The total number of packets received for which the
               address list does not match the locally configured
               list for the virtual router.

               Discontinuities in the value of this counter can occur
               at re-initialization of the management system, and at
               other times as indicated by the value of
               vrrpv3StatisticsRowDiscontinuityTime."
           ::=3D { vrrpv3StatisticsEntry 10 }

Summary to your query:
    1. Both DUTs will detects VIP address error, discards the packets
and becomes the Masters.
    2. DUTs  increment the statistics variable
vrrpv3StatisticsAddressListErrors.


Additionally, if you configure different VRIDs, packets will be
discarded before checking the VIPs only. Both DUTs will become masters
and will increment vrrpv3RouterVrIdErrors statistics variable (RFC
6527).

vrrpv3RouterVrIdErrors OBJECT-TYPE
           SYNTAX       Counter64
           MAX-ACCESS   read-only
          STATUS       current
           DESCRIPTION
               "The total number of VRRP packets received with a
                VRID that is not valid for any virtual router on this
                router.

               Discontinuities in the value of this counter can occur
               at re-initialization of the management system, and at
               other times as indicated by the value of
               vrrpv3GlobalStatisticsDiscontinuityTime."

           REFERENCE "RFC 5798, Section 5.2.3"
           ::=3D { vrrpv3Statistics 3 }

Thanks & Regards,
B Sreenatha Setty
Senior Software Engineer
IB Technology

------------------------------------------------------------------------
--------------------------------------
Message: 1
Date: Thu, 17 Oct 2013 22:27:21 -0700 (PDT)
From: Sandhya Puppala <psandhya81@yahoo.com>
To: "vrrp@ietf.org" <vrrp@ietf.org>
Subject: [VRRP] VRRP IPV6 Session Configuration with different link
	local	addresses (as VIP)
Message-ID:
	<1382074041.37205.YahooMailNeo@web160103.mail.bf1.yahoo.com>
Content-Type: text/plain; charset=3D"iso-8859-1"



Hi,


Consider the below topology,
DUT1 ----- DUT2

Configured DUT1 as owner with vip as fe80::ca35:b8ff:fea8:82fd.
And configured DUT2 as not-owner with vip as fe80::ca35:b8ff:fea8:8212

VIP on DUT1 and DUT2 are different.

What should be the states of DUT1 & DUT2?

According to draft
http://tools.ietf.org/html/draft-ietf-vrrp-ipv6-spec-07
section 7.1, =


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.

1. Does it need to compare the vip address of received packet and its
vip address?
??? If there are different what need to be done?

As per RFC "DUT2 should accept the packet from DUT1".
Does this mean DUT2 state should become backup?



Thanks,
Sandhya
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.ietf.org/mail-archive/web/vrrp/attachments/20131017/5babdb8d
/attachment.htm>

------------------------------

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


End of vrrp Digest, Vol 88, Issue 1
***********************************
Disclaimer : =

This email communication may contain privileged and confidential informatio=
n and is intended for the use of the addressee only.If you are not an inten=
ded recipient you are requested not to reproduce, copy disseminate or in an=
y manner distribute this email communication as the same is strictly prohib=
ited. If you have received this email in error, please notify the sender im=
mediately by return e-mail and delete the communication sent in error. Emai=
l communications cannot be guaranteed to be secure & error free and IB Tech=
nology is not liable for any errors in the email communication or for the p=
roper, timely and complete transmission thereof.


From psandhya81@yahoo.com  Tue Oct 22 03:42:06 2013
Return-Path: <psandhya81@yahoo.com>
X-Original-To: vrrp@ietfa.amsl.com
Delivered-To: vrrp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C89D711E8185 for <vrrp@ietfa.amsl.com>; Tue, 22 Oct 2013 03:42:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.998
X-Spam-Level: 
X-Spam-Status: No, score=-0.998 tagged_above=-999 required=5 tests=[AWL=-1.600, BAYES_50=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LT9vxqZpPAkM for <vrrp@ietfa.amsl.com>; Tue, 22 Oct 2013 03:42:01 -0700 (PDT)
Received: from nm33-vm5.bullet.mail.bf1.yahoo.com (nm33-vm5.bullet.mail.bf1.yahoo.com [72.30.239.205]) by ietfa.amsl.com (Postfix) with ESMTP id D995111E8354 for <vrrp@ietf.org>; Tue, 22 Oct 2013 03:41:24 -0700 (PDT)
Received: from [98.139.212.153] by nm33.bullet.mail.bf1.yahoo.com with NNFMP; 22 Oct 2013 10:41:24 -0000
Received: from [98.139.212.228] by tm10.bullet.mail.bf1.yahoo.com with NNFMP; 22 Oct 2013 10:41:24 -0000
Received: from [127.0.0.1] by omp1037.mail.bf1.yahoo.com with NNFMP; 22 Oct 2013 10:41:24 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 437735.80581.bm@omp1037.mail.bf1.yahoo.com
Received: (qmail 49125 invoked by uid 60001); 22 Oct 2013 10:41:24 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1382438484; bh=QlmkMuskZq6bMZRjSPtaJbQPahd9SbfvEaOCqMR0doU=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=vy4JKdfyDpeFwEXQjaJ2jqTRswwhpOgRTUbHpensjKtNOlCp/hH91quXdRudb0IQg4wlIBIzg0aWqyq/yaQAIIguDqR2jo+GhQggn4AKQrlV8AW+iM1/Z2+Ic6MwkUH42ED8CidNL/Szj+1oD2eFyfNtq7x9OKDpVlsqcyrLpRw=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=BS8rm9UXcTtp15IOP1jz8mXwMWQsOoHVs+9U8iHPIGy2xY06oBow2usLkBTAKPWslOf++l2LMIM7GgcQeloPcajQeqphvDdoK6w5KnGVtWm+2IoQBwiaQyRKuQiVu4DAPMSYNjPBm1jj9G5P5lg0BgQ8WKMDeSYISsCtjf7Q480=;
X-YMail-OSG: iUpZHa4VM1mFuJ8j3NBE7yYpYADGWGV6Bu2CfcF5Pgjfs2w vJOWQzgSCO6daPTsdFbaaJYofmqrmHKYpPolXd5i_FmE4t9VMdwDJWkdknjo LmVgf08S5PUFxIw2UJHBWhYB6WJEd8uKDx4tibWUc0UJ9sPeYjLMms5FzIsi Mtwmjrjq6KD0_2p7D7YiCy.UETJnyyZzPIQeSfbISErxPum8Ek03WohXPeIP 1mogceyUkwva5f10.BF3qUOIvQf_KK4HTNwpQK0IJ0.Y48ALSC_WOQlk60bg 9_eaXdutOz1zdFVGckZfzuShk1IsBCkWlMKV9n_IL40yJmWoYwHTiVQPsEXN FHGS9ZGPaMKjHeYv_4IbNVeDlmXKhAZT77S9hi76e2W1CVozOBoQjBAI1_Wc ZSc5Wq1QeOGb5bFk_.taiSQlqXrBDSYyFPTJLDJWmF0eUoPCP4Dj29kRt5jA vSzruN2Rsh0S9f1Ed6UZokVeCPwZbmwrtaP.LIB..lVO6dpcsap0jz1z2rKu pC3VXZnPcXJVcKhPHSPUP9OjazcvW6HgjOGgDjNx14zhsnee0KNM1iRyDsYe bzCG72GS7IcgFNS.cfuJgi46c2FAN31xuo0nouQgxayhzPUU5SkI-
Received: from [203.91.201.57] by web160102.mail.bf1.yahoo.com via HTTP; Tue, 22 Oct 2013 03:41:24 PDT
X-Rocket-MIMEInfo: 002.001, CgpIaSBTcmVlbmF0aGEsCgpUaGFuayB5b3UgZm9yIHlvdXIgcmVzcG9uc2UuCkkgYWdyZWUgd2l0aCB5b3UuIEkgYWxzbyBmZWVsLCBib3RoIHNob3VsZCBiZSBNYXN0ZXIsIGJ1dCBpbiBSRkMgNTc5OC4KSW4gc2VjdGlvbiA3LjEKSWYgYW55IG9uZSBvZiB0aGUgYWJvdmUgY2hlY2tzIGZhaWxzLCB0aGUgcmVjZWl2ZXIgTVVTVCBkaXNjYXJkIHRoZSBwYWNrZXQsIFNIT1VMRCBsb2cgdGhlIGV2ZW50LCBhbmQgTUFZIGluZGljYXRlIHZpYSBuZXR3b3JrIG1hbmFnZW1lbnQgdGhhdCBhbiBlcnJvciBvY2N1cnIBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.160.587
References: <mailman.41.1382209253.349.vrrp@ietf.org>
Message-ID: <1382438484.49051.YahooMailNeo@web160102.mail.bf1.yahoo.com>
Date: Tue, 22 Oct 2013 03:41:24 -0700 (PDT)
From: Sandhya Puppala <psandhya81@yahoo.com>
To: "vrrp@ietf.org" <vrrp@ietf.org>
In-Reply-To: <mailman.41.1382209253.349.vrrp@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="1775031368-1806675558-1382438484=:49051"
Subject: Re: [VRRP] vrrp Digest, Vol 88, Issue 2
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Sandhya Puppala <psandhya81@yahoo.com>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vrrp>, <mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vrrp>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vrrp>, <mailto:vrrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Oct 2013 10:42:07 -0000

--1775031368-1806675558-1382438484=:49051
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

=0A=0AHi Sreenatha,=0A=0AThank you for your response.=0AI agree with you. I=
 also feel, both should be Master, but in RFC 5798.=0AIn section 7.1=0AIf a=
ny one of the above checks fails, the receiver MUST discard the packet, SHO=
ULD log the event, and MAY indicate via network management that an error oc=
curred.=A0=0A=0A- MAY verify that "Count IPvX Addrs" and the list of IPvX a=
ddress(es) match the IPvX Address(es) configured for the VRID. If the above=
 check fails, the receiver SHOULD log the event and MAY indicate via networ=
k management that a misconfiguration was detected. =0A=0A=0AIt is not menti=
oned to drop the packet. In the same section for other failed cases it clea=
rly mentioned to drop the packet.=0APlease let me know your comments.=0A=0A=
=0AThanks,Sandhya=0A=0A=0A=0AOn Sunday, October 20, 2013 12:31 AM, "vrrp-re=
quest@ietf.org" <vrrp-request@ietf.org> wrote:=0A =0AIf you have received t=
his digest without all the individual message=0Aattachments you will need t=
o update your digest options in your list=0Asubscription.=A0 To do so, go t=
o =0A=0Ahttps://www.ietf.org/mailman/listinfo/vrrp=0A=0AClick the 'Unsubscr=
ibe or edit options' button, log in, and set "Get=0AMIME or Plain Text Dige=
sts?" to MIME.=A0 You can set this option=0Aglobally for all the list diges=
ts you receive at this point.=0A=0A=0A=0ASend vrrp mailing list submissions=
 to=0A=A0=A0=A0 vrrp@ietf.org=0A=0ATo subscribe or unsubscribe via the Worl=
d Wide Web, visit=0A=A0=A0=A0 https://www.ietf.org/mailman/listinfo/vrrp=0A=
or, via email, send a message with subject or body 'help' to=0A=A0=A0=A0 vr=
rp-request@ietf.org=0A=0AYou can reach the person managing the list at=0A=
=A0=A0=A0 vrrp-owner@ietf.org=0A=0AWhen replying, please edit your Subject =
line so it is more specific=0Athan "Re: Contents of vrrp digest..."=0A=0A=
=0AToday's Topics:=0A=0A=A0  1. Re: vrrp Digest, Vol 88, Issue 1 (Thirumava=
lavan Periyannan)=0A=A0  2. Re: :=A0 VRRP IPV6 Session Configuration with d=
ifferent link=0A=A0 =A0 =A0 (Sreenatha Setty)=0A=0A=0A---------------------=
-------------------------------------------------=0A=0AMessage: 1=0ADate: S=
at, 19 Oct 2013 01:02:02 +0530=0AFrom: Thirumavalavan Periyannan <tperiyann=
an@extremenetworks.com>=0ATo: "vrrp@ietf.org" <vrrp@ietf.org>=0ASubject: Re=
: [VRRP] vrrp Digest, Vol 88, Issue 1=0AMessage-ID:=0A=A0=A0=A0 <6174384267=
68D648ABBC00E677AA0149028C9A0DF814@INEXCHANGE.corp.extremenetworks.com>=0A=
=A0=A0=A0 =0AContent-Type: text/plain; charset=3D"us-ascii"=0A=0AHi,=0A=0A=
=0A=0AYes, If Virtual IP (including link local) is different for specific V=
RID then it will be DUAL Master State on DUT1 & DUT2 routers.=0A=0A=0AThank=
s & Regards,=0AThirumavalavan Periyannan=0AAssociate SQA Engineer, Extreme =
Networks=0A=0A=0A=0A-----Original Message-----=0AFrom: vrrp-bounces@ietf.or=
g [mailto:vrrp-bounces@ietf.org] On Behalf Of vrrp-request@ietf.org=0ASent:=
 Saturday, October 19, 2013 12:31 AM=0ATo: vrrp@ietf.org=0ASubject: vrrp Di=
gest, Vol 88, Issue 1=0A=0A=0A=0AIf you have received this digest without a=
ll the individual message attachments you will need to update your digest o=
ptions in your list subscription.=A0 To do so, go to=0A=0A=0A=0Ahttps://www=
.ietf.org/mailman/listinfo/vrrp=0A=0A=0A=0AClick the 'Unsubscribe or edit o=
ptions' button, log in, and set "Get MIME or Plain Text Digests?" to MIME.=
=A0 You can set this option globally for all the list digests you receive a=
t this point.=0A=0A=0A=0A=0A=0A=0A=0ASend vrrp mailing list submissions to=
=0A=0A=A0 =A0 =A0 =A0 =A0 =A0 vrrp@ietf.org<mailto:vrrp@ietf.org>=0A=0A=0A=
=0ATo subscribe or unsubscribe via the World Wide Web, visit=0A=0A=A0 =A0 =
=A0 =A0 =A0 =A0 https://www.ietf.org/mailman/listinfo/vrrp=0A=0Aor, via ema=
il, send a message with subject or body 'help' to=0A=0A=A0 =A0 =A0 =A0 =A0 =
=A0 vrrp-request@ietf.org<mailto:vrrp-request@ietf.org>=0A=0A=0A=0AYou can =
reach the person managing the list at=0A=0A=A0 =A0 =A0 =A0 =A0 =A0 vrrp-own=
er@ietf.org<mailto:vrrp-owner@ietf.org>=0A=0A=0A=0AWhen replying, please ed=
it your Subject line so it is more specific than "Re: Contents of vrrp dige=
st..."=0A=0A=0A=0A=0A=0AToday's Topics:=0A=0A=0A=0A=A0  1. VRRP IPV6 Sessio=
n Configuration with different link local=0A=0A=A0 =A0 =A0 addresses (as VI=
P) (Sandhya Puppala)=0A=0A=0A=0A=0A=0A-------------------------------------=
---------------------------------=0A=0A=0A=0AMessage: 1=0A=0ADate: Thu, 17 =
Oct 2013 22:27:21 -0700 (PDT)=0A=0AFrom: Sandhya Puppala <psandhya81@yahoo.=
com>=0A=0ATo: "vrrp@ietf.org" <vrrp@ietf.org>=0A=0ASubject: [VRRP] VRRP IPV=
6 Session Configuration with different link=0A=0A=A0 =A0 =A0 =A0 =A0 =A0 lo=
cal=A0 =A0  addresses (as VIP)=0A=0AMessage-ID:=0A=0A=A0 =A0 =A0 =A0 =A0 =
=A0 <1382074041.37205.YahooMailNeo@web160103.mail.bf1.yahoo.com>=0A=0AConte=
nt-Type: text/plain; charset=3D"iso-8859-1"=0A=0A=0A=0A=0A=0A=0A=0AHi,=0A=
=0A=0A=0A=0A=0AConsider the below topology,=0A=0ADUT1 ----- DUT2=0A=0A=0A=
=0AConfigured DUT1 as owner with vip as fe80::ca35:b8ff:fea8:82fd.=0A=0AAnd=
 configured DUT2 as not-owner with vip as fe80::ca35:b8ff:fea8:8212=0A=0A=
=0A=0AVIP on DUT1 and DUT2 are different.=0A=0A=0A=0AWhat should be the sta=
tes of DUT1 & DUT2?=0A=0A=0A=0AAccording to draft http://tools.ietf.org/htm=
l/draft-ietf-vrrp-ipv6-spec-07=0A=0Asection 7.1,=0A=0A=0A=0AIf the packet w=
as not generated by the address owner (Priority does not equal 255 (decimal=
)), the receiver MUST drop the packet, otherwise continue processing.=0A=0A=
=0A=0A1. Does it need to compare the vip address of received packet and its=
 vip address?=0A=0A??? If there are different what need to be done?=0A=0A=
=0A=0AAs per RFC "DUT2 should accept the packet from DUT1".=0A=0ADoes this =
mean DUT2 state should become backup?=0A=0A=0A=0A=0A=0A=0A=0AThanks,=0A=0AS=
andhya=0A=0A-------------- next part --------------=0A=0AAn HTML attachment=
 was scrubbed...=0A=0AURL: <http://www.ietf.org/mail-archive/web/vrrp/attac=
hments/20131017/5babdb8d/attachment.htm>=0A=0A=0A=0A-----------------------=
-------=0A=0A=0A=0A_______________________________________________=0A=0Avrr=
p mailing list=0A=0Avrrp@ietf.org<mailto:vrrp@ietf.org>=0A=0Ahttps://www.ie=
tf.org/mailman/listinfo/vrrp=0A=0A=0A=0A=0A=0AEnd of vrrp Digest, Vol 88, I=
ssue 1=0A=0A***********************************=0A=0A______________________=
__________=0ADISCLAIMER:=0AThis e-mail and any attachments to it may contai=
n confidential and proprietary material and is solely for the use of the in=
tended recipient. Any review, use, disclosure, distribution or copying of t=
his transmittal is prohibited except by or on behalf of the intended recipi=
ent. If you have received this transmittal in error, please notify the send=
er and destroy this e-mail and any attachments and all copies, whether elec=
tronic or printed.=0A-------------- next part --------------=0AAn HTML atta=
chment was scrubbed...=0AURL: <http://www.ietf.org/mail-archive/web/vrrp/at=
tachments/20131019/e1ee034d/attachment.htm>=0A=0A--------------------------=
----=0A=0AMessage: 2=0ADate: Sat, 19 Oct 2013 12:36:50 +0530=0AFrom: Sreena=
tha Setty <sreenatha.setty@ibtechnology.com>=0ATo: <vrrp@ietf.org>=0ACc: ps=
andhya81@yahoo.com=0ASubject: Re: [VRRP] :=A0 VRRP IPV6 Session Configurati=
on with different=0A=A0=A0=A0 link=0AMessage-ID:=0A=A0=A0=A0 <DB36B077CF387=
C4989BCC57D685FA30102F2BF4D@GRGHEXCHANGE.grgh.indiabulls.com>=0A=A0=A0=A0 =
=0AContent-Type: text/plain; charset=3D"us-ascii"=0A=0AHi Sandhya,=0A=A0 =
=A0  Normally Vendors will implement based on the standard RFC not on=0Athe=
 draft version, since drafts can undergo changes very frequently. I=0Aam no=
t sure for what reason you are referring that particular draft. =0AI sugges=
t you to refer latest VRRP v3 RFC: 5798 for better=0Aunderstanding.=0A=0ACo=
ming to your query,=A0 according to latest RFC 5798( section 7.1), " If=0At=
he packet was not generated by the address owner (Priority does not=0Aequal=
 255 (decimal)), the receiver MUST drop the packet, otherwise=0Acontinue pr=
ocessing" condition is removed.=A0 So router can accept vrrp=0Apackets even=
 if it is generated by other than the address owner if all=0Aother conditio=
ns are met. (Mentioned in the above sections 7.1 of RFC=0A5798)=0A=0AIn you=
r case, you mentioned different VIPs are configured. In the same=0Asection =
only,=A0 RFC tells, =0A=A0 =A0 =A0 - MAY verify that "Count IPvX Addrs" and=
 the list of IPvX=0A=A0 =A0 =A0 address(es) match the IPvX Address(es) conf=
igured for the VRID.=0A=0ASo according to this logic, both DUTs will discar=
d the vrrp packets=0Asince VIP address are different and both DUTs will bec=
ome VRRP Masters.=0A=0AAnd standard VRRP MIB(RFC 6527) specifies one statis=
tics object to=0Arepresent these kind of address list errors:=0A=0Avrrpv3St=
atisticsAddressListErrors OBJECT-TYPE=0A=A0 =A0 =A0 =A0 =A0  SYNTAX=A0 =A0 =
=A0  Counter64=0A=A0 =A0 =A0 =A0 =A0  MAX-ACCESS=A0  read-only=0A=A0 =A0 =
=A0 =A0 =A0  STATUS=A0 =A0 =A0  current=0A=A0 =A0 =A0 =A0 =A0  DESCRIPTION=
=0A=A0 =A0 =A0 =A0 =A0 =A0 =A0  "The total number of packets received for w=
hich the=0A=A0 =A0 =A0 =A0 =A0 =A0 =A0  address list does not match the loc=
ally configured=0A=A0 =A0 =A0 =A0 =A0 =A0 =A0  list for the virtual router.=
=0A=0A=A0 =A0 =A0 =A0 =A0 =A0 =A0  Discontinuities in the value of this cou=
nter can occur=0A=A0 =A0 =A0 =A0 =A0 =A0 =A0  at re-initialization of the m=
anagement system, and at=0A=A0 =A0 =A0 =A0 =A0 =A0 =A0  other times as indi=
cated by the value of=0A=A0 =A0 =A0 =A0 =A0 =A0 =A0  vrrpv3StatisticsRowDis=
continuityTime."=0A=A0 =A0 =A0 =A0 =A0  ::=3D { vrrpv3StatisticsEntry 10 }=
=0A=0ASummary to your query:=0A=A0 =A0 1. Both DUTs will detects VIP addres=
s error, discards the packets=0Aand becomes the Masters.=0A=A0 =A0 2. DUTs=
=A0 increment the statistics variable=0Avrrpv3StatisticsAddressListErrors.=
=0A=0A=0AAdditionally, if you configure different VRIDs, packets will be=0A=
discarded before checking the VIPs only. Both DUTs will become masters=0Aan=
d will increment vrrpv3RouterVrIdErrors statistics variable (RFC=0A6527).=
=0A=0Avrrpv3RouterVrIdErrors OBJECT-TYPE=0A=A0 =A0 =A0 =A0 =A0  SYNTAX=A0 =
=A0 =A0  Counter64=0A=A0 =A0 =A0 =A0 =A0  MAX-ACCESS=A0  read-only=0A=A0 =
=A0 =A0 =A0 =A0 STATUS=A0 =A0 =A0  current=0A=A0 =A0 =A0 =A0 =A0  DESCRIPTI=
ON=0A=A0 =A0 =A0 =A0 =A0 =A0 =A0  "The total number of VRRP packets receive=
d with a=0A=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 VRID that is not valid for any v=
irtual router on this=0A=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 router.=0A=0A=A0 =
=A0 =A0 =A0 =A0 =A0 =A0  Discontinuities in the value of this counter can o=
ccur=0A=A0 =A0 =A0 =A0 =A0 =A0 =A0  at re-initialization of the management =
system, and at=0A=A0 =A0 =A0 =A0 =A0 =A0 =A0  other times as indicated by t=
he value of=0A=A0 =A0 =A0 =A0 =A0 =A0 =A0  vrrpv3GlobalStatisticsDiscontinu=
ityTime."=0A=0A=A0 =A0 =A0 =A0 =A0  REFERENCE "RFC 5798, Section 5.2.3"=0A=
=A0 =A0 =A0 =A0 =A0  ::=3D { vrrpv3Statistics 3 }=0A=0AThanks & Regards,=0A=
B Sreenatha Setty=0ASenior Software Engineer=0AIB Technology=0A=0A---------=
---------------------------------------------------------------=0A---------=
-----------------------------=0AMessage: 1=0ADate: Thu, 17 Oct 2013 22:27:2=
1 -0700 (PDT)=0AFrom: Sandhya Puppala <psandhya81@yahoo.com>=0ATo: "vrrp@ie=
tf.org" <vrrp@ietf.org>=0ASubject: [VRRP] VRRP IPV6 Session Configuration w=
ith different link=0A=A0=A0=A0 local=A0=A0=A0 addresses (as VIP)=0AMessage-=
ID:=0A=A0=A0=A0 <1382074041.37205.YahooMailNeo@web160103.mail.bf1.yahoo.com=
>=0AContent-Type: text/plain; charset=3D"iso-8859-1"=0A=0A=0A=0AHi,=0A=0A=
=0AConsider the below topology,=0ADUT1 ----- DUT2=0A=0AConfigured DUT1 as o=
wner with vip as fe80::ca35:b8ff:fea8:82fd.=0AAnd configured DUT2 as not-ow=
ner with vip as fe80::ca35:b8ff:fea8:8212=0A=0AVIP on DUT1 and DUT2 are dif=
ferent.=0A=0AWhat should be the states of DUT1 & DUT2?=0A=0AAccording to dr=
aft=0Ahttp://tools.ietf.org/html/draft-ietf-vrrp-ipv6-spec-07=0Asection 7.1=
, =0A=0AIf the packet was not generated by the address owner (Priority does=
 not=0Aequal 255 (decimal)), the receiver MUST drop the packet, otherwise=
=0Acontinue processing.=0A=0A1. Does it need to compare the vip address of =
received packet and its=0Avip address?=0A??? If there are different what ne=
ed to be done?=0A=0AAs per RFC "DUT2 should accept the packet from DUT1".=
=0ADoes this mean DUT2 state should become backup?=0A=0A=0A=0AThanks,=0ASan=
dhya=0A-------------- next part --------------=0AAn HTML attachment was scr=
ubbed...=0AURL:=0A<http://www.ietf.org/mail-archive/web/vrrp/attachments/20=
131017/5babdb8d=0A/attachment.htm>=0A=0A------------------------------=0A=
=0A_______________________________________________=0Avrrp mailing list=0Avr=
rp@ietf.org=0Ahttps://www.ietf.org/mailman/listinfo/vrrp=0A=0A=0AEnd of vrr=
p Digest, Vol 88, Issue 1=0A***********************************=0ADisclaime=
r : =0AThis email communication may contain privileged and confidential inf=
ormation and is intended for the use of the addressee only.If you are not a=
n intended recipient you are requested not to reproduce, copy disseminate o=
r in any manner distribute this email communication as the same is strictly=
 prohibited. If you have received this email in error, please notify the se=
nder immediately by return e-mail and delete the communication sent in erro=
r. Email communications cannot be guaranteed to be secure & error free and =
IB Technology is not liable for any errors in the email communication or fo=
r the proper, timely and complete transmission thereof.=0A=0A=0A=0A--------=
----------------------=0A=0A_______________________________________________=
=0Avrrp mailing list=0Avrrp@ietf.org=0Ahttps://www.ietf.org/mailman/listinf=
o/vrrp=0A=0A=0AEnd of vrrp Digest, Vol 88, Issue 2=0A**********************=
*************
--1775031368-1806675558-1382438484=:49051
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:He=
lveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;fo=
nt-size:12pt"><div><br></div><div><span>Hi Sreenatha,</span></div><div styl=
e=3D"color:rgb(0, 0, 0);font-size:16px;font-family:HelveticaNeue, Helvetica=
 Neue, Helvetica, Arial, Lucida Grande, sans-serif;background-color:transpa=
rent;font-style:normal;"><br clear=3D"none"><span></span></div><div style=
=3D"color:rgb(0, 0, 0);font-size:16px;font-family:HelveticaNeue, Helvetica =
Neue, Helvetica, Arial, Lucida Grande, sans-serif;background-color:transpar=
ent;font-style:normal;"><span>Thank you for your response.</span></div><div=
 style=3D"color:rgb(0, 0, 0);font-size:16px;font-family:HelveticaNeue, Helv=
etica Neue, Helvetica, Arial, Lucida Grande, sans-serif;background-color:tr=
ansparent;font-style:normal;"><span>I agree with you. I also feel, both sho=
uld be Master, but in RFC 5798.</span></div><div style=3D"color:rgb(0, 0,
 0);font-size:16px;font-family:HelveticaNeue, Helvetica Neue, Helvetica, Ar=
ial, Lucida Grande, sans-serif;background-color:transparent;font-style:norm=
al;"><span style=3D"font-style: italic;"><span>In section 7.1</span></span>=
</div><div style=3D"color:rgb(0, 0, 0);font-size:16px;font-family:Helvetica=
Neue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;backgroun=
d-color:transparent;font-style:normal;"><span style=3D"font-style: italic;"=
>If any one of the above checks fails, the receiver MUST discard the=0A   p=
acket, SHOULD log the event, and MAY indicate via network management=0A   t=
hat an error occurred.&nbsp;</span></div><div style=3D"color:rgb(0, 0, 0);f=
ont-size:16px;font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, =
Lucida Grande, sans-serif;background-color:transparent;font-style:normal;">=
<span style=3D"font-style: italic;"><br clear=3D"none"></span></div><div st=
yle=3D"color:rgb(0, 0, 0);font-size:16px;font-family:HelveticaNeue, Helveti=
ca Neue, Helvetica, Arial, Lucida Grande, sans-serif;background-color:trans=
parent;font-style:normal;"><span style=3D"font-style: italic;"> - MAY verif=
y that "Count IPvX Addrs" and the list of IPvX=0A      address(es) match th=
e IPvX Address(es) configured for the VRID.=0A=0A   If the above check fail=
s, the receiver SHOULD log the event and MAY=0A   indicate via network mana=
gement that a misconfiguration was detected. </span><br clear=3D"none"></di=
v><div style=3D"color:rgb(0, 0, 0);font-size:16px;font-family:HelveticaNeue=
, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;background-co=
lor:transparent;font-style:normal;"><br clear=3D"none"></div><div style=3D"=
color:rgb(0, 0, 0);font-size:16px;font-family:HelveticaNeue, Helvetica Neue=
, Helvetica, Arial, Lucida Grande, sans-serif;background-color:transparent;=
font-style:normal;">It is not mentioned to drop the packet. In the same sec=
tion for other failed cases it clearly mentioned to drop the packet.</div><=
div style=3D"color:rgb(0, 0, 0);font-size:16px;font-family:HelveticaNeue, H=
elvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;background-color=
:transparent;font-style:normal;">Please let me know your comments.<br clear=
=3D"none"></div><div style=3D"color:rgb(0, 0, 0);font-size:16px;font-family=
:HelveticaNeue, Helvetica Neue, Helvetica, Arial,
 Lucida Grande, sans-serif;background-color:transparent;font-style:normal;"=
><br clear=3D"none"></div><div style=3D"color:rgb(0, 0, 0);font-size:16px;f=
ont-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, =
sans-serif;background-color:transparent;font-style:normal;">Thanks,</div>Sa=
ndhya<div style=3D"display: block;" class=3D"yahoo_quoted"> <br> <br> <div =
style=3D"font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Luci=
da Grande, sans-serif; font-size: 12pt;"> <div style=3D"font-family: Helvet=
icaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-=
size: 12pt;"> <div dir=3D"ltr"> <font size=3D"2" face=3D"Arial"> On Sunday,=
 October 20, 2013 12:31 AM, "vrrp-request@ietf.org" &lt;vrrp-request@ietf.o=
rg&gt; wrote:<br> </font> </div>  <div class=3D"y_msg_container">If you hav=
e received this digest without all the individual message<br>attachments yo=
u will need to update your digest options in your list<br>subscription.&nbs=
p; To do so,
 go to <br><br><a href=3D"https://www.ietf.org/mailman/listinfo/vrrp" targe=
t=3D"_blank">https://www.ietf.org/mailman/listinfo/vrrp</a><br><br>Click th=
e 'Unsubscribe or edit options' button, log in, and set "Get<br>MIME or Pla=
in Text Digests?" to MIME.&nbsp; You can set this option<br>globally for al=
l the list digests you receive at this point.<br><br><br><br>Send vrrp mail=
ing list submissions to<br>&nbsp;&nbsp;&nbsp; <a ymailto=3D"mailto:vrrp@iet=
f.org" href=3D"mailto:vrrp@ietf.org">vrrp@ietf.org</a><br><br>To subscribe =
or unsubscribe via the World Wide Web, visit<br>&nbsp;&nbsp;&nbsp; <a href=
=3D"https://www.ietf.org/mailman/listinfo/vrrp" target=3D"_blank">https://w=
ww.ietf.org/mailman/listinfo/vrrp</a><br>or, via email, send a message with=
 subject or body 'help' to<br>&nbsp;&nbsp;&nbsp; <a ymailto=3D"mailto:vrrp-=
request@ietf.org" href=3D"mailto:vrrp-request@ietf.org">vrrp-request@ietf.o=
rg</a><br><br>You can reach the person managing the list at<br>&nbsp;&nbsp;=
&nbsp; <a
 ymailto=3D"mailto:vrrp-owner@ietf.org" href=3D"mailto:vrrp-owner@ietf.org"=
>vrrp-owner@ietf.org</a><br><br>When replying, please edit your Subject lin=
e so it is more specific<br>than "Re: Contents of vrrp digest..."<br><br><b=
r>Today's Topics:<br><br>&nbsp;  1. Re: vrrp Digest, Vol 88, Issue 1 (Thiru=
mavalavan Periyannan)<br>&nbsp;  2. Re: :&nbsp; VRRP IPV6 Session Configura=
tion with different link<br>&nbsp; &nbsp; &nbsp; (Sreenatha Setty)<br><br><=
br>----------------------------------------------------------------------<b=
r><br>Message: 1<br>Date: Sat, 19 Oct 2013 01:02:02 +0530<br>From: Thirumav=
alavan Periyannan &lt;<a ymailto=3D"mailto:tperiyannan@extremenetworks.com"=
 href=3D"mailto:tperiyannan@extremenetworks.com">tperiyannan@extremenetwork=
s.com</a>&gt;<br>To: "<a ymailto=3D"mailto:vrrp@ietf.org" href=3D"mailto:vr=
rp@ietf.org">vrrp@ietf.org</a>" &lt;<a ymailto=3D"mailto:vrrp@ietf.org" hre=
f=3D"mailto:vrrp@ietf.org">vrrp@ietf.org</a>&gt;<br>Subject: Re: [VRRP] vrr=
p Digest,
 Vol 88, Issue 1<br>Message-ID:<br>&nbsp;&nbsp;&nbsp; &lt;<a ymailto=3D"mai=
lto:617438426768D648ABBC00E677AA0149028C9A0DF814@INEXCHANGE.corp.extremenet=
works.com" href=3D"mailto:617438426768D648ABBC00E677AA0149028C9A0DF814@INEX=
CHANGE.corp.extremenetworks.com">617438426768D648ABBC00E677AA0149028C9A0DF8=
14@INEXCHANGE.corp.extremenetworks.com</a>&gt;<br>&nbsp;&nbsp;&nbsp; <br>Co=
ntent-Type: text/plain; charset=3D"us-ascii"<br><br>Hi,<br><br><br><br>Yes,=
 If Virtual IP (including link local) is different for specific VRID then i=
t will be DUAL Master State on DUT1 &amp; DUT2 routers.<br><br><br>Thanks &=
amp; Regards,<br>Thirumavalavan Periyannan<br>Associate SQA Engineer, Extre=
me Networks<br><br><br><br>-----Original Message-----<br>From: <a ymailto=
=3D"mailto:vrrp-bounces@ietf.org" href=3D"mailto:vrrp-bounces@ietf.org">vrr=
p-bounces@ietf.org</a> [mailto:<a ymailto=3D"mailto:vrrp-bounces@ietf.org" =
href=3D"mailto:vrrp-bounces@ietf.org">vrrp-bounces@ietf.org</a>] On Behalf =
Of <a
 ymailto=3D"mailto:vrrp-request@ietf.org" href=3D"mailto:vrrp-request@ietf.=
org">vrrp-request@ietf.org</a><br>Sent: Saturday, October 19, 2013 12:31 AM=
<br>To: <a ymailto=3D"mailto:vrrp@ietf.org" href=3D"mailto:vrrp@ietf.org">v=
rrp@ietf.org</a><br>Subject: vrrp Digest, Vol 88, Issue 1<br><br><br><br>If=
 you have received this digest without all the individual message attachmen=
ts you will need to update your digest options in your list subscription.&n=
bsp; To do so, go to<br><br><br><br><a href=3D"https://www.ietf.org/mailman=
/listinfo/vrrp" target=3D"_blank">https://www.ietf.org/mailman/listinfo/vrr=
p</a><br><br><br><br>Click the 'Unsubscribe or edit options' button, log in=
, and set "Get MIME or Plain Text Digests?" to MIME.&nbsp; You can set this=
 option globally for all the list digests you receive at this point.<br><br=
><br><br><br><br><br><br>Send vrrp mailing list submissions to<br><br>&nbsp=
; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <a ymailto=3D"mailto:vrrp@ietf.org"
 href=3D"mailto:vrrp@ietf.org">vrrp@ietf.org</a>&lt;mailto:<a ymailto=3D"ma=
ilto:vrrp@ietf.org" href=3D"mailto:vrrp@ietf.org">vrrp@ietf.org</a>&gt;<br>=
<br><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br><b=
r>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <a href=3D"https://www.ietf.org=
/mailman/listinfo/vrrp" target=3D"_blank">https://www.ietf.org/mailman/list=
info/vrrp</a><br><br>or, via email, send a message with subject or body 'he=
lp' to<br><br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <a ymailto=3D"mailt=
o:vrrp-request@ietf.org" href=3D"mailto:vrrp-request@ietf.org">vrrp-request=
@ietf.org</a>&lt;mailto:<a ymailto=3D"mailto:vrrp-request@ietf.org" href=3D=
"mailto:vrrp-request@ietf.org">vrrp-request@ietf.org</a>&gt;<br><br><br><br=
>You can reach the person managing the list at<br><br>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; <a ymailto=3D"mailto:vrrp-owner@ietf.org" href=3D"mail=
to:vrrp-owner@ietf.org">vrrp-owner@ietf.org</a>&lt;mailto:<a
 ymailto=3D"mailto:vrrp-owner@ietf.org" href=3D"mailto:vrrp-owner@ietf.org"=
>vrrp-owner@ietf.org</a>&gt;<br><br><br><br>When replying, please edit your=
 Subject line so it is more specific than "Re: Contents of vrrp digest..."<=
br><br><br><br><br><br>Today's Topics:<br><br><br><br>&nbsp;  1. VRRP IPV6 =
Session Configuration with different link local<br><br>&nbsp; &nbsp; &nbsp;=
 addresses (as VIP) (Sandhya Puppala)<br><br><br><br><br><br>--------------=
--------------------------------------------------------<br><br><br><br>Mes=
sage: 1<br><br>Date: Thu, 17 Oct 2013 22:27:21 -0700 (PDT)<br><br>From: San=
dhya Puppala &lt;<a ymailto=3D"mailto:psandhya81@yahoo.com" href=3D"mailto:=
psandhya81@yahoo.com">psandhya81@yahoo.com</a>&gt;<br><br>To: "<a ymailto=
=3D"mailto:vrrp@ietf.org" href=3D"mailto:vrrp@ietf.org">vrrp@ietf.org</a>" =
&lt;<a ymailto=3D"mailto:vrrp@ietf.org" href=3D"mailto:vrrp@ietf.org">vrrp@=
ietf.org</a>&gt;<br><br>Subject: [VRRP] VRRP IPV6 Session Configuration wit=
h different
 link<br><br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; local&nbsp; &nbsp;  =
addresses (as VIP)<br><br>Message-ID:<br><br>&nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp; &nbsp; &lt;<a ymailto=3D"mailto:1382074041.37205.YahooMailNeo@web16010=
3.mail.bf1.yahoo.com" href=3D"mailto:1382074041.37205.YahooMailNeo@web16010=
3.mail.bf1.yahoo.com">1382074041.37205.YahooMailNeo@web160103.mail.bf1.yaho=
o.com</a>&gt;<br><br>Content-Type: text/plain; charset=3D"iso-8859-1"<br><b=
r><br><br><br><br><br><br>Hi,<br><br><br><br><br><br>Consider the below top=
ology,<br><br>DUT1 ----- DUT2<br><br><br><br>Configured DUT1 as owner with =
vip as fe80::ca35:b8ff:fea8:82fd.<br><br>And configured DUT2 as not-owner w=
ith vip as fe80::ca35:b8ff:fea8:8212<br><br><br><br>VIP on DUT1 and DUT2 ar=
e different.<br><br><br><br>What should be the states of DUT1 &amp; DUT2?<b=
r><br><br><br>According to draft <a href=3D"http://tools.ietf.org/html/draf=
t-ietf-vrrp-ipv6-spec-07"
 target=3D"_blank">http://tools.ietf.org/html/draft-ietf-vrrp-ipv6-spec-07<=
/a><br><br>section 7.1,<br><br><br><br>If the packet was not generated by t=
he address owner (Priority does not equal 255 (decimal)), the receiver MUST=
 drop the packet, otherwise continue processing.<br><br><br><br>1. Does it =
need to compare the vip address of received packet and its vip address?<br>=
<br>??? If there are different what need to be done?<br><br><br><br>As per =
RFC "DUT2 should accept the packet from DUT1".<br><br>Does this mean DUT2 s=
tate should become backup?<br><br><br><br><br><br><br><br>Thanks,<br><br>Sa=
ndhya<br><br>-------------- next part --------------<br><br>An HTML attachm=
ent was scrubbed...<br><br>URL: &lt;<a href=3D"http://www.ietf.org/mail-arc=
hive/web/vrrp/attachments/20131017/5babdb8d/attachment.htm"
 target=3D"_blank">http://www.ietf.org/mail-archive/web/vrrp/attachments/20=
131017/5babdb8d/attachment.htm</a>&gt;<br><br><br><br>---------------------=
---------<br><br><br><br>_______________________________________________<br=
><br>vrrp mailing list<br><br><a ymailto=3D"mailto:vrrp@ietf.org" href=3D"m=
ailto:vrrp@ietf.org">vrrp@ietf.org</a>&lt;mailto:<a ymailto=3D"mailto:vrrp@=
ietf.org" href=3D"mailto:vrrp@ietf.org">vrrp@ietf.org</a>&gt;<br><br><a hre=
f=3D"https://www.ietf.org/mailman/listinfo/vrrp" target=3D"_blank">https://=
www.ietf.org/mailman/listinfo/vrrp</a><br><br><br><br><br><br>End of vrrp D=
igest, Vol 88, Issue 1<br><br>***********************************<br><br>__=
______________________________<br>DISCLAIMER:<br>This e-mail and any attach=
ments to it may contain confidential and proprietary material and is solely=
 for the use of the intended recipient. Any review, use, disclosure, distri=
bution or copying of this transmittal is prohibited except by or on behalf =
of the
 intended recipient. If you have received this transmittal in error, please=
 notify the sender and destroy this e-mail and any attachments and all copi=
es, whether electronic or printed.<br>-------------- next part ------------=
--<br>An HTML attachment was scrubbed...<br>URL: &lt;<a href=3D"http://www.=
ietf.org/mail-archive/web/vrrp/attachments/20131019/e1ee034d/attachment.htm=
" target=3D"_blank">http://www.ietf.org/mail-archive/web/vrrp/attachments/2=
0131019/e1ee034d/attachment.htm</a>&gt;<br><br>----------------------------=
--<br><br>Message: 2<br>Date: Sat, 19 Oct 2013 12:36:50 +0530<br>From: Sree=
natha Setty &lt;<a ymailto=3D"mailto:sreenatha.setty@ibtechnology.com" href=
=3D"mailto:sreenatha.setty@ibtechnology.com">sreenatha.setty@ibtechnology.c=
om</a>&gt;<br>To: &lt;<a ymailto=3D"mailto:vrrp@ietf.org" href=3D"mailto:vr=
rp@ietf.org">vrrp@ietf.org</a>&gt;<br>Cc: <a ymailto=3D"mailto:psandhya81@y=
ahoo.com" href=3D"mailto:psandhya81@yahoo.com">psandhya81@yahoo.com</a><br>=
Subject:
 Re: [VRRP] :&nbsp; VRRP IPV6 Session Configuration with different<br>&nbsp=
;&nbsp;&nbsp; link<br>Message-ID:<br>&nbsp;&nbsp;&nbsp; &lt;<a ymailto=3D"m=
ailto:DB36B077CF387C4989BCC57D685FA30102F2BF4D@GRGHEXCHANGE.grgh.indiabulls=
.com" href=3D"mailto:DB36B077CF387C4989BCC57D685FA30102F2BF4D@GRGHEXCHANGE.=
grgh.indiabulls.com">DB36B077CF387C4989BCC57D685FA30102F2BF4D@GRGHEXCHANGE.=
grgh.indiabulls.com</a>&gt;<br>&nbsp;&nbsp;&nbsp; <br>Content-Type: text/pl=
ain; charset=3D"us-ascii"<br><br>Hi Sandhya,<br>&nbsp; &nbsp;  Normally Ven=
dors will implement based on the standard RFC not on<br>the draft version, =
since drafts can undergo changes very frequently. I<br>am not sure for what=
 reason you are referring that particular draft. <br>I suggest you to refer=
 latest VRRP v3 RFC: 5798 for better<br>understanding.<br><br>Coming to you=
r query,&nbsp; according to latest RFC 5798( section 7.1), " If<br>the pack=
et was not generated by the address owner (Priority does not<br>equal 255
 (decimal)), the receiver MUST drop the packet, otherwise<br>continue proce=
ssing" condition is removed.&nbsp; So router can accept vrrp<br>packets eve=
n if it is generated by other than the address owner if all<br>other condit=
ions are met. (Mentioned in the above sections 7.1 of RFC<br>5798)<br><br>I=
n your case, you mentioned different VIPs are configured. In the same<br>se=
ction only,&nbsp; RFC tells, <br>&nbsp; &nbsp; &nbsp; - MAY verify that "Co=
unt IPvX Addrs" and the list of IPvX<br>&nbsp; &nbsp; &nbsp; address(es) ma=
tch the IPvX Address(es) configured for the VRID.<br><br>So according to th=
is logic, both DUTs will discard the vrrp packets<br>since VIP address are =
different and both DUTs will become VRRP Masters.<br><br>And standard VRRP =
MIB(RFC 6527) specifies one statistics object to<br>represent these kind of=
 address list errors:<br><br>vrrpv3StatisticsAddressListErrors OBJECT-TYPE<=
br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  SYNTAX&nbsp; &nbsp; &nbsp;=20
 Counter64<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  MAX-ACCESS&nbsp;  read-on=
ly<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  STATUS&nbsp; &nbsp; &nbsp;  curre=
nt<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  DESCRIPTION<br>&nbsp; &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp;  "The total number of packets received for w=
hich the<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  address list =
does not match the locally configured<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp; &nbsp;  list for the virtual router.<br><br>&nbsp; &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp;  Discontinuities in the value of this counter can=
 occur<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  at re-initializ=
ation of the management system, and at<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp; &nbsp;  other times as indicated by the value of<br>&nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  vrrpv3StatisticsRowDiscontinuityTime."<=
br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  ::=3D { vrrpv3StatisticsEntry
 10 }<br><br>Summary to your query:<br>&nbsp; &nbsp; 1. Both DUTs will dete=
cts VIP address error, discards the packets<br>and becomes the Masters.<br>=
&nbsp; &nbsp; 2. DUTs&nbsp; increment the statistics variable<br>vrrpv3Stat=
isticsAddressListErrors.<br><br><br>Additionally, if you configure differen=
t VRIDs, packets will be<br>discarded before checking the VIPs only. Both D=
UTs will become masters<br>and will increment vrrpv3RouterVrIdErrors statis=
tics variable (RFC<br>6527).<br><br>vrrpv3RouterVrIdErrors OBJECT-TYPE<br>&=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  SYNTAX&nbsp; &nbsp; &nbsp;  Counter64<br=
>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  MAX-ACCESS&nbsp;  read-only<br>&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; STATUS&nbsp; &nbsp; &nbsp;  current<br>&nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp;  DESCRIPTION<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p; &nbsp; &nbsp;  "The total number of VRRP packets received with a<br>&nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; VRID that is not
 valid for any virtual router on this<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp; &nbsp; &nbsp; router.<br><br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp;  Discontinuities in the value of this counter can occur<br>&nbsp=
; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  at re-initialization of the ma=
nagement system, and at<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
  other times as indicated by the value of<br>&nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp;  vrrpv3GlobalStatisticsDiscontinuityTime."<br><br>&nbsp=
; &nbsp; &nbsp; &nbsp; &nbsp;  REFERENCE "RFC 5798, Section 5.2.3"<br>&nbsp=
; &nbsp; &nbsp; &nbsp; &nbsp;  ::=3D { vrrpv3Statistics 3 }<br><br>Thanks &=
amp; Regards,<br>B Sreenatha Setty<br>Senior Software Engineer<br>IB Techno=
logy<br><br>---------------------------------------------------------------=
---------<br>--------------------------------------<br>Message: 1<br>Date: =
Thu, 17 Oct 2013 22:27:21 -0700 (PDT)<br>From: Sandhya Puppala &lt;<a
 ymailto=3D"mailto:psandhya81@yahoo.com" href=3D"mailto:psandhya81@yahoo.co=
m">psandhya81@yahoo.com</a>&gt;<br>To: "<a ymailto=3D"mailto:vrrp@ietf.org"=
 href=3D"mailto:vrrp@ietf.org">vrrp@ietf.org</a>" &lt;<a ymailto=3D"mailto:=
vrrp@ietf.org" href=3D"mailto:vrrp@ietf.org">vrrp@ietf.org</a>&gt;<br>Subje=
ct: [VRRP] VRRP IPV6 Session Configuration with different link<br>&nbsp;&nb=
sp;&nbsp; local&nbsp;&nbsp;&nbsp; addresses (as VIP)<br>Message-ID:<br>&nbs=
p;&nbsp;&nbsp; &lt;<a ymailto=3D"mailto:1382074041.37205.YahooMailNeo@web16=
0103.mail.bf1.yahoo.com" href=3D"mailto:1382074041.37205.YahooMailNeo@web16=
0103.mail.bf1.yahoo.com">1382074041.37205.YahooMailNeo@web160103.mail.bf1.y=
ahoo.com</a>&gt;<br>Content-Type: text/plain; charset=3D"iso-8859-1"<br><br=
><br><br>Hi,<br><br><br>Consider the below topology,<br>DUT1 ----- DUT2<br>=
<br>Configured DUT1 as owner with vip as fe80::ca35:b8ff:fea8:82fd.<br>And =
configured DUT2 as not-owner with vip as fe80::ca35:b8ff:fea8:8212<br><br>V=
IP on DUT1
 and DUT2 are different.<br><br>What should be the states of DUT1 &amp; DUT=
2?<br><br>According to draft<br><a href=3D"http://tools.ietf.org/html/draft=
-ietf-vrrp-ipv6-spec-07" target=3D"_blank">http://tools.ietf.org/html/draft=
-ietf-vrrp-ipv6-spec-07</a><br>section 7.1, <br><br>If the packet was not g=
enerated by the address owner (Priority does not<br>equal 255 (decimal)), t=
he receiver MUST drop the packet, otherwise<br>continue processing.<br><br>=
1. Does it need to compare the vip address of received packet and its<br>vi=
p address?<br>??? If there are different what need to be done?<br><br>As pe=
r RFC "DUT2 should accept the packet from DUT1".<br>Does this mean DUT2 sta=
te should become backup?<br><br><br><br>Thanks,<br>Sandhya<br>-------------=
- next part --------------<br>An HTML attachment was scrubbed...<br>URL:<br=
>&lt;<a href=3D"http://www.ietf.org/mail-archive/web/vrrp/attachments/20131=
017/5babdb8d"
 target=3D"_blank">http://www.ietf.org/mail-archive/web/vrrp/attachments/20=
131017/5babdb8d</a><br>/attachment.htm&gt;<br><br>-------------------------=
-----<br><br>_______________________________________________<br>vrrp mailin=
g list<br><a ymailto=3D"mailto:vrrp@ietf.org" href=3D"mailto:vrrp@ietf.org"=
>vrrp@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/vrrp=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/vrrp</a><br><br><=
br>End of vrrp Digest, Vol 88, Issue 1<br>*********************************=
**<br>Disclaimer : <br>This email communication may contain privileged and =
confidential information and is intended for the use of the addressee only.=
If you are not an intended recipient you are requested not to reproduce, co=
py disseminate or in any manner distribute this email communication as the =
same is strictly prohibited. If you have received this email in error, plea=
se notify the sender immediately by return e-mail and delete the communicat=
ion
 sent in error. Email communications cannot be guaranteed to be secure &amp=
; error free and IB Technology is not liable for any errors in the email co=
mmunication or for the proper, timely and complete transmission thereof.<br=
><br><br><br>------------------------------<br><br>________________________=
_______________________<br>vrrp mailing list<br><a ymailto=3D"mailto:vrrp@i=
etf.org" href=3D"mailto:vrrp@ietf.org">vrrp@ietf.org</a><br><a href=3D"http=
s://www.ietf.org/mailman/listinfo/vrrp" target=3D"_blank">https://www.ietf.=
org/mailman/listinfo/vrrp</a><br><br><br>End of vrrp Digest, Vol 88, Issue =
2<br>***********************************<br><br><br></div>  </div> </div>  =
</div> </div></body></html>
--1775031368-1806675558-1382438484=:49051--

From sreenatha.setty@ibtechnology.com  Tue Oct 22 22:51:09 2013
Return-Path: <sreenatha.setty@ibtechnology.com>
X-Original-To: vrrp@ietfa.amsl.com
Delivered-To: vrrp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F6E511E82E6 for <vrrp@ietfa.amsl.com>; Tue, 22 Oct 2013 22:51:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ot9ukSwWi0E1 for <vrrp@ietfa.amsl.com>; Tue, 22 Oct 2013 22:51:04 -0700 (PDT)
Received: from ipinternal.indiabulls.com (ipinternal.indiabulls.com [202.54.119.192]) by ietfa.amsl.com (Postfix) with ESMTP id 8E13711E8149 for <vrrp@ietf.org>; Tue, 22 Oct 2013 22:51:02 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqEEACBjZ1KsEMj1/2dsb2JhbABZsAeSXoFDdIIlAQEBAQMwCj8SAQgNBAMBAgsGDgoHRAoJAQQLAwUIh2wDsQYDiXWMYIE1gQgxDRCDCYEKA4k9jGeONYhjgWk
X-IronPort-AV: E=Sophos;i="4.93,553,1378837800"; d="scan'208";a="34748187"
Received: from GRGHEXCHANGE.grgh.indiabulls.com (172.16.200.20) by GGN-ICAS.grgh.indiabulls.com (172.16.200.245) with Microsoft SMTP Server id 14.3.123.3; Wed, 23 Oct 2013 11:20:59 +0530
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"
Date: Wed, 23 Oct 2013 11:20:58 +0530
Message-ID: <DB36B077CF387C4989BCC57D685FA30102F2BFBE@GRGHEXCHANGE.grgh.indiabulls.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: : VRRP IPV6 Session Configuration with different link local local address
Thread-Index: Ac7PsS4iUzmMCVf6RHKz17m11Bzk6Q==
From: Sreenatha Setty <sreenatha.setty@ibtechnology.com>
To: <vrrp@ietf.org>
Content-Transfer-Encoding: quoted-printable
Cc: psandhya81@yahoo.com
Subject: Re: [VRRP] : VRRP IPV6 Session Configuration with different link local local address
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vrrp>, <mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vrrp>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vrrp>, <mailto:vrrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Oct 2013 05:51:09 -0000

Hi Sandhya,
    Good catch from the RFC.

    - MAY verify that "Count IPvX Addrs" and the list of IPvX
address(es) match the IPvX Address(es) configured for the VRID. If the
above check fails, the receiver SHOULD log the event and MAY indicate
via network management that a misconfiguration was detected.

      Here, "misconfiguration" word is used. We should not allow any
misconfiguration in the network. So we can discard the packet.  Then
both routers will start acting as Master and now it is up to network
administrator to resolve the misconfiguration.

Thanks,
Sreenatha    =


Message: 1
Date: Tue, 22 Oct 2013 03:41:24 -0700 (PDT)
From: Sandhya Puppala <psandhya81@yahoo.com>
To: "vrrp@ietf.org" <vrrp@ietf.org>
Subject: Re: [VRRP] vrrp Digest, Vol 88, Issue 2
Message-ID:
	<1382438484.49051.YahooMailNeo@web160102.mail.bf1.yahoo.com>
Content-Type: text/plain; charset=3D"iso-8859-1"



Hi Sreenatha,

Thank you for your response.
I agree with you. I also feel, both should be Master, but in RFC 5798.
In section 7.1
If any one of the above checks fails, the receiver MUST discard the
packet, SHOULD log the event, and MAY indicate via network management
that an error occurred.?

- MAY verify that "Count IPvX Addrs" and the list of IPvX address(es)
match the IPvX Address(es) configured for the VRID. If the above check
fails, the receiver SHOULD log the event and MAY indicate via network
management that a misconfiguration was detected. =



It is not mentioned to drop the packet. In the same section for other
failed cases it clearly mentioned to drop the packet.
Please let me know your comments.


Thanks,Sandhya



Disclaimer : =

This email communication may contain privileged and confidential informatio=
n and is intended for the use of the addressee only.If you are not an inten=
ded recipient you are requested not to reproduce, copy disseminate or in an=
y manner distribute this email communication as the same is strictly prohib=
ited. If you have received this email in error, please notify the sender im=
mediately by return e-mail and delete the communication sent in error. Emai=
l communications cannot be guaranteed to be secure & error free and IB Tech=
nology is not liable for any errors in the email communication or for the p=
roper, timely and complete transmission thereof.

