From mailnull@www1.ietf.org Thu Jan 9 04:46:09 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05469 for ; Thu, 9 Jan 2003 04:46:09 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h099vlU10135 for vrrp-archive@odin.ietf.org; Thu, 9 Jan 2003 04:57:47 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h099vlJ10132 for ; Thu, 9 Jan 2003 04:57:47 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05461 for ; Thu, 9 Jan 2003 04:45:32 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h099tkJ10042; Thu, 9 Jan 2003 04:55:46 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h099qCJ09889 for ; Thu, 9 Jan 2003 04:52:12 -0500 Received: from mlry.radlan.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05379 for ; Thu, 9 Jan 2003 04:40:00 -0500 (EST) Received: from star.radlan.net ([176.192.111.5]) by mlry.radlan.net with Microsoft SMTPSVC(5.0.2195.5329); Thu, 9 Jan 2003 11:44:59 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2B7C3.C615AD96" Date: Thu, 9 Jan 2003 11:44:58 +0200 Message-ID: <1612A4FBCAA7434FB246A491ECF20EC30FCC1E@star.radlan.net> Thread-Topic: Question on Election Algorithm Thread-Index: AcK3w8W7dVr8Q8i5ThGoA3hfRvek8Q== From: "Lior Ronen" To: "Vrrp (E-mail)" X-OriginalArrivalTime: 09 Jan 2003 09:44:59.0188 (UTC) FILETIME=[C6384F40:01C2B7C3] Subject: [VRRP] Question on Election Algorithm Sender: vrrp-admin@ietf.org Errors-To: vrrp-admin@ietf.org X-BeenThere: vrrp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Virtual Router Redundancy Protocol List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------_=_NextPart_001_01C2B7C3.C615AD96 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Hello, =20 I'll appreciate an opinion on the following issue: =20 =20 To the same LAN 2 routers (R) are connected : R1 with ifIndex 2. R2 with ifIndex 2. =20 R1 has Primary IP address: 10.1.1.99 R2 has Primary IP address: 10.1.1.101 =20 R1 & R2 has same priority ( default priority =3D 100 ). =20 We configure one VR12: VR12 =3D {Non-Owner =3D R1, Non-Owner =3D R2, AssoIpAddr =3D = 10.1.1.100,vmac =3D Vmac1} =20 We start VRRP on router R1. Since it receive no advertisements it become = master. Then we start VRRP on R2. Since it is NON- Owner it transition to backup = state. It receive advertisement from R1. According to the RFC, R2 will not become master ( although it has a = higher Primary IP address than R1 and should have been the master ) = because it is in backup state and doesn't compare Primary IP address( = only in Master state Primary IP address are being compared in case of = equal priority). =20 =20 Am I correct ?=20 =20 Regards, Lior ______________________________ Lior Ronen RADLAN Computer Communications Ltd. ATIDIM Technological Park, Bldg #4, Tel-Aviv, Israel. Tel: 972-3-7658964 Fax: 972-3-6458544 Email: liorr@radlan.com =20 ------_=_NextPart_001_01C2B7C3.C615AD96 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable
Hello,
 
I'll = appreciate an=20 opinion on the following issue:
 
 
To = the same=20 LAN 2 routers (R) are = connected=20 :
R1 with ifIndex = 2.
R2 with ifIndex=20 2.
 
R1 has Primary IP address10.1.1.99
R2 has Primary IP address10.1.1.101
 
R1 & R2=20 has same priority ( default priority =3D 100 ).
 
We configure=20 one VR12:
VR12 =3D {Non-Owner =3D R1, Non-Owner =3D = R2, AssoIpAddr =3D  10.1.1.100,vmac = =3D=20 Vmac1}
 
We = start VRRP on=20 router R1. Since it receive no advertisements it become=20 master.
Then we start VRRP on R2. Since it is NON- Owner it transition to = backup=20 state. It receive advertisement from R1.
According to the RFC, R2 will not become master ( although it has a higher = Primary IP=20 address than R1 and should have been the = master ) because it is = in backup=20 state and doesn't compare Primary IP address( only in Master = state Primary=20 IP address are being compared in case of equal = priority).
 
 
Am I = correct=20 ? 
 
Regards,
Lior
______________________________
Lior=20 Ronen
RADLAN=20 Computer=20 Communications Ltd.
ATIDIM=20 Technological Park,
Bldg=20 #4,
Tel-Aviv,=20 Israel.
Tel: =20 972-3-7658964
Fax: =20 972-3-6458544
Email: liorr@radlan.com
 
------_=_NextPart_001_01C2B7C3.C615AD96-- _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From mailnull@www1.ietf.org Fri Jan 10 15:14:12 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14717 for ; Fri, 10 Jan 2003 15:14:12 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0AKQVQ26564 for vrrp-archive@odin.ietf.org; Fri, 10 Jan 2003 15:26:31 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AKQVJ26561 for ; Fri, 10 Jan 2003 15:26:31 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14703 for ; Fri, 10 Jan 2003 15:13:40 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AKOfJ26474; Fri, 10 Jan 2003 15:24:41 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0AKNhJ26436 for ; Fri, 10 Jan 2003 15:23:43 -0500 Received: from mgw-dax1.ext.nokia.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14652 for ; Fri, 10 Jan 2003 15:10:53 -0500 (EST) Received: from davir01nok.americas.nokia.com (davir01nok.americas.nokia.com [172.18.242.84]) by mgw-dax1.ext.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id h0AKECE03911 for ; Fri, 10 Jan 2003 14:14:12 -0600 (CST) Received: from daebh001.NOE.Nokia.com (unverified) by davir01nok.americas.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Fri, 10 Jan 2003 14:14:06 -0600 Received: from daebe008.NOE.Nokia.com ([172.18.242.238]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329); Fri, 10 Jan 2003 12:13:51 -0800 Received: from nokia.com ([172.19.66.59]) by daebe008.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329); Fri, 10 Jan 2003 14:13:50 -0600 Message-ID: <3E1F297E.98A9EAAC@nokia.com> Date: Fri, 10 Jan 2003 12:13:50 -0800 From: Mukesh Gupta Organization: Nokia Networks X-Mailer: Mozilla 4.75 [en]C-CCK-MCD {Nokia} (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: vrrp@ietf.org References: <018101c294bf$07877f20$8d18a8c0@corp.networkrobots.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 10 Jan 2003 20:13:50.0840 (UTC) FILETIME=[CA733F80:01C2B8E4] Content-Transfer-Encoding: 7bit Subject: [VRRP] 56th IETF VRRP WG Meeting Sender: vrrp-admin@ietf.org Errors-To: vrrp-admin@ietf.org X-BeenThere: vrrp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Virtual Router Redundancy Protocol List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit VRRP WG will be meeting in San Francisco. Please send me any potential agenda items that you might have. regards Mukesh _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From mailnull@www1.ietf.org Wed Jan 15 14:57:39 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08115 for ; Wed, 15 Jan 2003 14:57:39 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0FKCPM06083 for vrrp-archive@odin.ietf.org; Wed, 15 Jan 2003 15:12:25 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FKCPJ06080 for ; Wed, 15 Jan 2003 15:12:25 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08095 for ; Wed, 15 Jan 2003 14:57:08 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FKArJ06030; Wed, 15 Jan 2003 15:10:53 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FK9iJ05927 for ; Wed, 15 Jan 2003 15:09:44 -0500 Received: from presque.djinesys.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08045 for ; Wed, 15 Jan 2003 14:54:27 -0500 (EST) Received: (from root@localhost) by presque.djinesys.com (8.11.3/8.11.1) id h0FJvmd54022 for vrrp@ietf.org; Wed, 15 Jan 2003 14:57:48 -0500 (EST) (envelope-from jhaas@jhaas.nexthop.com) Received: from jhaas.nexthop.com (jhaas.nexthop.com [64.211.218.31]) by presque.djinesys.com (8.11.3/8.11.1) with ESMTP id h0FJvjC54015 for ; Wed, 15 Jan 2003 14:57:45 -0500 (EST) (envelope-from jhaas@jhaas.nexthop.com) Received: (from jhaas@localhost) by jhaas.nexthop.com (8.11.3nb1/8.11.3) id h0FJvjk28669 for vrrp@ietf.org; Wed, 15 Jan 2003 14:57:45 -0500 (EST) Date: Wed, 15 Jan 2003 14:57:45 -0500 From: Jeffrey Haas To: vrrp@ietf.org Message-ID: <20030115145745.E26136@nexthop.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Virus-Scanned: by AMaViS perl-11 Subject: [VRRP] very minor tweak suggested to draft-ietf-vrrp-spec-v2-06.txt Sender: vrrp-admin@ietf.org Errors-To: vrrp-admin@ietf.org X-BeenThere: vrrp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Virtual Router Redundancy Protocol List-Post: List-Help: List-Subscribe: , As I am reading through this specification as a new reader, the following stands out: : 7.1 Receiving VRRP Packets : [...] : - MAY verify that "Count IP Addrs" and the list of IP Address : matches the IP_Addresses 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. : 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. I believe that the bottom sentence is mandatory. Since it is in the same paragraph, one might consider the "MAY" and the "If the above check fails" to apply and thus you only MUST drop the packet if you are verifying the count and the list. I would suggest rewording the second sentence as a new paragraph: If the packet was not generated by the address owner (Priority does not equal 255 (decimal)), and either the "Count IP Addrs" or the list of IP Addresses fails to match the IP_Addresses configured for the VRID, then the receive MUST drop the packet. -- Jeff Haas NextHop Technologies _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From mailnull@www1.ietf.org Wed Jan 15 23:38:36 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA20567 for ; Wed, 15 Jan 2003 23:38:36 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0G4rV308723 for vrrp-archive@odin.ietf.org; Wed, 15 Jan 2003 23:53:31 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0G4rVJ08720 for ; Wed, 15 Jan 2003 23:53:31 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA20561 for ; Wed, 15 Jan 2003 23:38:05 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0G4qIJ08665; Wed, 15 Jan 2003 23:52:18 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0G4plJ08645 for ; Wed, 15 Jan 2003 23:51:47 -0500 Received: from rediffmail.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA20553 for ; Wed, 15 Jan 2003 23:36:20 -0500 (EST) Received: (qmail 374 invoked by uid 510); 16 Jan 2003 04:36:06 -0000 Date: 16 Jan 2003 04:36:06 -0000 Message-ID: <20030116043606.373.qmail@webmail17.rediffmail.com> Received: from unknown (203.197.138.201) by rediffmail.com via HTTP; 16 jan 2003 04:36:06 -0000 MIME-Version: 1.0 From: "ashish thakur" Reply-To: "ashish thakur" To: "Jeffrey Haas" Cc: vrrp@ietf.org Subject: Re: [VRRP] very minor tweak suggested to draft-ietf-vrrp-spec-v2-06.txt Content-type: text/plain; format=flowed Content-Disposition: inline Sender: vrrp-admin@ietf.org Errors-To: vrrp-admin@ietf.org X-BeenThere: vrrp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Virtual Router Redundancy Protocol List-Post: List-Help: List-Subscribe: , Jeff , as per rfc we are not dropping a non ip address owner generated packet if the IP address(es) associated with the VRID are not valid.Only we SHOULD log the event and MAY indicate via network management about the misconfiguration.Also we should further continue processing of the packet.Only in the case of address owner we MUST drop the packet. As far as what u have suggested , we should also drop the non ip address owner generated packets. cheer, ashish thakur On Thu, 16 Jan 2003 Jeffrey Haas wrote : >As I am reading through this specification as a new reader, the >following stands out: > >: 7.1 Receiving VRRP Packets >: [...] >: - MAY verify that "Count IP Addrs" and the list of IP >Address >: matches the IP_Addresses 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. >: 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. > >I believe that the bottom sentence is mandatory. >Since it is in the same paragraph, one might consider the "MAY" >and >the "If the above check fails" to apply and thus you only MUST >drop the packet if you are verifying the count and the list. > >I would suggest rewording the second sentence as a new >paragraph: > >If the packet was not generated by the address owner (Priority >does >not equal 255 (decimal)), and either the "Count IP Addrs" or >the list of IP Addresses fails to match the IP_Addresses >configured >for the VRID, then the receive MUST drop the packet. > > >-- >Jeff Haas >NextHop Technologies >_______________________________________________ >vrrp mailing list >vrrp@ietf.org >https://www1.ietf.org/mailman/listinfo/vrrp _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From mailnull@www1.ietf.org Thu Jan 16 12:53:42 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17977 for ; Thu, 16 Jan 2003 12:53:41 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0GI8rh10168 for vrrp-archive@odin.ietf.org; Thu, 16 Jan 2003 13:08:53 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GI8rJ10165 for ; Thu, 16 Jan 2003 13:08:53 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17939 for ; Thu, 16 Jan 2003 12:53:10 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GI7OJ09943; Thu, 16 Jan 2003 13:07:24 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GI6CJ09316 for ; Thu, 16 Jan 2003 13:06:12 -0500 Received: from presque.djinesys.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17792 for ; Thu, 16 Jan 2003 12:50:29 -0500 (EST) Received: (from root@localhost) by presque.djinesys.com (8.11.3/8.11.1) id h0GHrem78900; Thu, 16 Jan 2003 12:53:40 -0500 (EST) (envelope-from jhaas@jhaas.nexthop.com) Received: from jhaas.nexthop.com (jhaas.nexthop.com [64.211.218.31]) by presque.djinesys.com (8.11.3/8.11.1) with ESMTP id h0GHrbC78893; Thu, 16 Jan 2003 12:53:37 -0500 (EST) (envelope-from jhaas@jhaas.nexthop.com) Received: (from jhaas@localhost) by jhaas.nexthop.com (8.11.3nb1/8.11.3) id h0GHrbJ04009; Thu, 16 Jan 2003 12:53:37 -0500 (EST) Date: Thu, 16 Jan 2003 12:53:37 -0500 From: Jeffrey Haas To: ashish thakur Cc: vrrp@ietf.org Subject: Re: [VRRP] very minor tweak suggested to draft-ietf-vrrp-spec-v2-06.txt Message-ID: <20030116125337.B1982@nexthop.com> References: <20030116043606.373.qmail@webmail17.rediffmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20030116043606.373.qmail@webmail17.rediffmail.com>; from ash_thakur_@rediffmail.com on Thu, Jan 16, 2003 at 04:36:06AM -0000 X-Virus-Scanned: by AMaViS perl-11 Sender: vrrp-admin@ietf.org Errors-To: vrrp-admin@ietf.org X-BeenThere: vrrp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Virtual Router Redundancy Protocol List-Post: List-Help: List-Subscribe: , Ashish, On Thu, Jan 16, 2003 at 04:36:06AM -0000, ashish thakur wrote: > Jeff , as per rfc we are not dropping a non ip address owner > generated packet if the IP address(es) associated with the VRID > are not valid.Only we SHOULD log the event and MAY indicate via > network management about the misconfiguration.Also we should > further continue processing of the packet.Only in the case of > address owner we MUST drop the packet. This is opposite the way I read the spec. As I read the spec (cited below), we MUST drop the packet if the priority is not 255. If it *does* equal 255, we may continue processing. > ashish thakur > >: 7.1 Receiving VRRP Packets > >: [...] > >: - MAY verify that "Count IP Addrs" and the list of IP > >Address > >: matches the IP_Addresses 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. > >: 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. -- Jeff Haas NextHop Technologies _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From mailnull@www1.ietf.org Thu Jan 30 18:16:44 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13007 for ; Thu, 30 Jan 2003 18:16:44 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0UNJu804644 for vrrp-archive@odin.ietf.org; Thu, 30 Jan 2003 18:19:56 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UNJuJ04641 for ; Thu, 30 Jan 2003 18:19:56 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13002 for ; Thu, 30 Jan 2003 18:16:03 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UNEiJ04507; Thu, 30 Jan 2003 18:14:44 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UNB7J04425 for ; Thu, 30 Jan 2003 18:11:07 -0500 Received: from mel-rto2.wanadoo.fr (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12911 for ; Thu, 30 Jan 2003 18:07:22 -0500 (EST) Received: from mel-rta10.wanadoo.fr (193.252.19.193) by mel-rto2.wanadoo.fr (6.7.015) id 3E0C33700158ECA9; Fri, 31 Jan 2003 00:10:50 +0100 Received: from wanadoo.fr (81.49.28.193) by mel-rta10.wanadoo.fr (6.7.015) id 3E26DAA60088D86E; Fri, 31 Jan 2003 00:10:50 +0100 Message-ID: <3E39B0C8.9060207@wanadoo.fr> Date: Fri, 31 Jan 2003 00:10:00 +0100 From: Alexandre Cassen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mukesh Gupta CC: vrrp@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [VRRP] VRRP IPSEC-AH FSM extension Sender: vrrp-admin@ietf.org Errors-To: vrrp-admin@ietf.org X-BeenThere: vrrp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Virtual Router Redundancy Protocol List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Mukesh, I am currently writing the draft we discussed in a previous mail... In the discussion I need to offer an extended VRRP FSM design to expose all possible AH case. The FSM diagram I propose is the following : +---------------+ +----------------| |----------------+ | | Fault | | | +------------>| |<------------+ | | | +---------------+ | | | | ^ | | | | | | | | | +---------------+ | | | | +--------->| |<---------+ | | | | | | Initialize | | | | | | | +-------| |-------+ | | | | | | | +---------------+ | | | | | | | | | | | | V | | V V | | V +---------------+ +---------------+ | |---------------------->| | | Master | | Backup | | |<----------------------| | +---------------+ +---------------+ I just add a new STATE : the FAULT state. This state is reflecting an interface physical state : shut or no shut, due to hardware failure, media link detection failure, ... All layer1 related errors. Since VRRP is extremly interface state dependent, I really think this state must be considered. There is two point of view, integrating this state directly into Master and Backup state but creating a new dedicated state can be , IMHO, better for devel point of view, since FSM implementation is simplest. Especially for IPSEC-AH extension. What is your opinion ? Best regards, Alexandre _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From mailnull@www1.ietf.org Thu Jan 30 22:04:58 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA16941 for ; Thu, 30 Jan 2003 22:04:58 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0V38GG17220 for vrrp-archive@odin.ietf.org; Thu, 30 Jan 2003 22:08:16 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0V38GJ17217 for ; Thu, 30 Jan 2003 22:08:16 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA16935 for ; Thu, 30 Jan 2003 22:04:18 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0V36fJ16520; Thu, 30 Jan 2003 22:06:41 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0V31YJ16407 for ; Thu, 30 Jan 2003 22:01:34 -0500 Received: from mgw-dax1.ext.nokia.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16839 for ; Thu, 30 Jan 2003 21:57:45 -0500 (EST) Received: from davir01nok.americas.nokia.com (davir01nok.americas.nokia.com [172.18.242.84]) by mgw-dax1.ext.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id h0V31Gr00893 for ; Thu, 30 Jan 2003 21:01:16 -0600 (CST) Received: from daebh001.NOE.Nokia.com (unverified) by davir01nok.americas.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Thu, 30 Jan 2003 21:01:13 -0600 Received: from daebe008.NOE.Nokia.com ([172.18.242.238]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Thu, 30 Jan 2003 19:00:24 -0800 Received: from nokia.com ([10.241.50.20]) by daebe008.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Thu, 30 Jan 2003 21:00:23 -0600 Message-ID: <3E39E6C4.D916BBBA@nokia.com> Date: Thu, 30 Jan 2003 19:00:20 -0800 From: Mukesh Gupta Organization: Nokia Networks X-Mailer: Mozilla 4.75 [en]C-CCK-MCD {Nokia} (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: ext Alexandre Cassen CC: vrrp@ietf.org References: <3E39B0C8.9060207@wanadoo.fr> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 31 Jan 2003 03:00:23.0660 (UTC) FILETIME=[E5F732C0:01C2C8D4] Content-Transfer-Encoding: 7bit Subject: [VRRP] Re: VRRP IPSEC-AH FSM extension Sender: vrrp-admin@ietf.org Errors-To: vrrp-admin@ietf.org X-BeenThere: vrrp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Virtual Router Redundancy Protocol List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Alexandre, I am going to india for 15 days and will be back on 16th Feb. I will get back to you after that. In the meantime, I would appreciate if WG members could discuss the proposal in WG and express their opinion/comments. Thanks.. - Mukesh ext Alexandre Cassen wrote: > Hi Mukesh, > > I am currently writing the draft we discussed in a previous mail... In > the discussion I need to offer an extended VRRP FSM design to expose all > possible AH case. The FSM diagram I propose is the following : > > +---------------+ > +----------------| |----------------+ > | | Fault | | > | +------------>| |<------------+ | > | | +---------------+ | | > | | ^ | | > | | | | | > | | +---------------+ | | > | | +--------->| |<---------+ | | > | | | | Initialize | | | | > | | | +-------| |-------+ | | | > | | | | +---------------+ | | | | > | | | | | | | | > V | | V V | | V > +---------------+ +---------------+ > | |---------------------->| | > | Master | | Backup | > | |<----------------------| | > +---------------+ +---------------+ > > I just add a new STATE : the FAULT state. This state is reflecting an > interface physical state : shut or no shut, due to hardware failure, > media link detection failure, ... All layer1 related errors. Since VRRP > is extremly interface state dependent, I really think this state must be > considered. There is two point of view, integrating this state directly > into Master and Backup state but creating a new dedicated state can be > , IMHO, better for devel point of view, since FSM implementation is > simplest. Especially for IPSEC-AH extension. What is your opinion ? > > Best regards, > Alexandre _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp