From exim@www1.ietf.org Tue Jul 1 09:17:41 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 JAA22563 for ; Tue, 1 Jul 2003 09:17:41 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h61DHEo28484 for vrrp-archive@odin.ietf.org; Tue, 1 Jul 2003 09:17:14 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XL0T-0007PL-Rs for vrrp-web-archive@optimus.ietf.org; Tue, 01 Jul 2003 09:17:13 -0400 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22382 for ; Tue, 1 Jul 2003 09:17:11 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XKzz-00079O-HO for vrrp-web-archive@ietf.org; Tue, 01 Jul 2003 09:16:43 -0400 Date: Tue, 01 Jul 2003 09:16:43 -0400 Message-ID: <20030701131643.18162.66076.Mailman@www1.ietf.org> Subject: ietf.org mailing list memberships reminder From: mailman-owner@www1.ietf.org To: vrrp-web-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: sip-admin@ietf.org Errors-To: sip-admin@ietf.org X-BeenThere: sip@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, vrrp-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner@www1.ietf.org. Thanks! Passwords for vrrp-web-archive@ietf.org: List Password // URL ---- -------- vrrp@ietf.org mPhD https://www1.ietf.org/mailman/options/vrrp/vrrp-web-archive%40ietf.org From exim@www1.ietf.org Tue Jul 1 15:12:56 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12606 for ; Tue, 1 Jul 2003 15:12:56 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XQYD-0002Y6-Kq for vrrp-archive@odin.ietf.org; Tue, 01 Jul 2003 15:12:26 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h61JCOXc009792 for vrrp-archive@odin.ietf.org; Tue, 1 Jul 2003 15:12:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XQYC-0002Xr-Pv for vrrp-web-archive@optimus.ietf.org; Tue, 01 Jul 2003 15:12:24 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12533 for ; Tue, 1 Jul 2003 15:12:22 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XQYA-0007Ez-00 for vrrp-web-archive@ietf.org; Tue, 01 Jul 2003 15:12:22 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19XQY6-0007Ep-00 for vrrp-web-archive@ietf.org; Tue, 01 Jul 2003 15:12:18 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XQX0-0002Sx-5V; Tue, 01 Jul 2003 15:11:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VuTV-0002NW-To for vrrp@optimus.ietf.org; Fri, 27 Jun 2003 10:45:17 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22424; Fri, 27 Jun 2003 07:33:18 -0400 (EDT) Message-Id: <200306271133.HAA22424@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: vrrp@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Fri, 27 Jun 2003 07:33:18 -0400 Subject: [VRRP] I-D ACTION:draft-ietf-vrrp-ipv6-mib-00.txt Sender: vrrp-admin@ietf.org Errors-To: vrrp-admin@ietf.org X-BeenThere: vrrp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Virtual Router Redundancy Protocol List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Virtual Router Redundancy Protocol Working Group of the IETF. Title : Definitions of Managed Objects for the VRRP IPv6 Author(s) : K. Tata Filename : draft-ietf-vrrp-ipv6-mib-00.txt Pages : 25 Date : 2003-6-26 This specification defines an extension to the Management Information Base (MIB) for use with SNMP-based network management. In particular, it defines objects for configuring, monitoring, and controlling routers that employ the Virtual Router Redundancy Protocol for IPv6 as defined in draft-ietf-vrrp-ipv6-spec-04.txt [19]. This memo specifies a MIB module in a manner that is compliant with SMIv2 [5], and semantically identical to the SMIv1 definitions [2]. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-vrrp-ipv6-mib-00.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-vrrp-ipv6-mib-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-vrrp-ipv6-mib-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-6-26162856.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-vrrp-ipv6-mib-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-vrrp-ipv6-mib-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-6-26162856.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Tue Jul 1 15:13:13 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12650 for ; Tue, 1 Jul 2003 15:13:13 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XQYO-0002YO-V2 for vrrp-archive@odin.ietf.org; Tue, 01 Jul 2003 15:12:43 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h61JCaa5009812 for vrrp-archive@odin.ietf.org; Tue, 1 Jul 2003 15:12:36 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XQYO-0002YB-9K for vrrp-web-archive@optimus.ietf.org; Tue, 01 Jul 2003 15:12:36 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12530 for ; Tue, 1 Jul 2003 15:12:21 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XQYA-0007F0-00 for vrrp-web-archive@ietf.org; Tue, 01 Jul 2003 15:12:22 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19XQY6-0007Eq-00 for vrrp-web-archive@ietf.org; Tue, 01 Jul 2003 15:12:18 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XQWw-0002S1-FO; Tue, 01 Jul 2003 15:11:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VfIh-000081-49 for vrrp@optimus.ietf.org; Thu, 26 Jun 2003 18:33:22 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25609 for ; Thu, 26 Jun 2003 18:32:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VfIP-0006cq-00 for vrrp@ietf.org; Thu, 26 Jun 2003 18:32:49 -0400 Received: from athena.nswc.navy.mil ([198.91.70.29]) by ietf-mx with esmtp (Exim 4.12) id 19VfIE-0006cP-00 for vrrp@ietf.org; Thu, 26 Jun 2003 18:32:38 -0400 Received: from relay.nswc.navy.mil (relay.nswc.navy.mil [128.38.1.41]) by athena.nswc.navy.mil (8.11.6p2/8.11.6) with ESMTP id h5QMWDP24677 for ; Thu, 26 Jun 2003 18:32:13 -0400 (PDT) Received: from relay.nswc.navy.mil (localhost [127.0.0.1]) by relay.nswc.navy.mil (8.11.6p2/8.11.6) with ESMTP id h5QMWDt09281 for ; Thu, 26 Jun 2003 18:32:13 -0400 (EDT) Received: from titanic.nswc.navy.mil (titanic.nswc.navy.mil [128.38.42.115]) by relay.nswc.navy.mil (8.11.6p2/8.11.6) with ESMTP id h5QMWBC09274; Thu, 26 Jun 2003 18:32:11 -0400 (EDT) Received: from nswc.navy.mil (localhost [127.0.0.1]) by titanic.nswc.navy.mil (8.11.6+Sun/8.9.3) with ESMTP id h5QMWA707725; Thu, 26 Jun 2003 18:32:10 -0400 (EDT) Message-ID: <3EFB74AE.EDA6B010@nswc.navy.mil> Date: Thu, 26 Jun 2003 18:33:18 -0400 From: "Robert (Bob) W. Hott" X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Radia Perlman - Boston Center for Networking , vrrp@ietf.org CC: kodonog@titanic.nswc.navy.mil, dmarlow@titanic.nswc.navy.mil, bchappe@nswc.navy.mil, tplunke@titanic.nswc.navy.mil, Lee S Carmichael Subject: Re: [VRRP] Need agenda items for the IETF meeting References: <200306231943.h5NJhMs00369@sydney.East.Sun.COM> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: vrrp-admin@ietf.org Errors-To: vrrp-admin@ietf.org X-BeenThere: vrrp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Virtual Router Redundancy Protocol List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Radia, About a month ago, there was a brief discussion about the granularity of the timers and proprietary solutions that use sub-second timers. Survivability solutions, such as VRRP are of interest to the US Navy. Selecting proprietary implementations of VRRP, or similar technologies, are desirable only when open standard solutions are not available. It would be nice to hear about proposals that would introduce sub-second timers to VRRP. Knowing that they may not scale for Internet-wide solutions, such an interoperable, open standard could be used for specific, controlled, networks with high reliability/availability requirements. While I will not be in attendance, several co-workers will. We could briefly discuss our needs, from a high level perspective, if needed. We would be the end-user of such a capability. We would certainly like to see this pursued with IPv6, if it is not looked at for IPv4. We would interested in hearing about the potential adding such a capability into VRRP, or the reasons why it should be avoided. Please consider this a request for such a discussion at the upcoming IETF. Thank you. Bob Hott Radia Perlman - Boston Center for Networking wrote: > Please send ideas for things to talk about at the > next IETF meeting. I'd prefer you "multicast" > it to the vrrp list rather than unicasting to me > and Mukesh, but if you're shy, feel free to > just send it to us. > > Thanks, > > Radia > > _______________________________________________ > vrrp mailing list > vrrp@ietf.org > https://www1.ietf.org/mailman/listinfo/vrrp -- Robert (Bob) W. Hott Naval Surface Warfare Center Dahlgren Division Code B35, Bldg. 1500/A110 17320 Dahlgren Road Dahlgren, VA 22448-5100 Voice: (540) 653-1497 FAX: (540) 653-8673 _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Tue Jul 1 18:35:34 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19469 for ; Tue, 1 Jul 2003 18:35:34 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XTiO-0002Ut-Lr for vrrp-archive@odin.ietf.org; Tue, 01 Jul 2003 18:35:08 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h61MZ8mQ009598 for vrrp-archive@odin.ietf.org; Tue, 1 Jul 2003 18:35:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XTiO-0002Uj-IZ for vrrp-web-archive@optimus.ietf.org; Tue, 01 Jul 2003 18:35:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19458 for ; Tue, 1 Jul 2003 18:35:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XTiL-0001bV-00 for vrrp-web-archive@ietf.org; Tue, 01 Jul 2003 18:35:05 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19XTiL-0001bS-00 for vrrp-web-archive@ietf.org; Tue, 01 Jul 2003 18:35:05 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XTiH-0002Tv-6B; Tue, 01 Jul 2003 18:35:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XThw-0002TP-9J for vrrp@optimus.ietf.org; Tue, 01 Jul 2003 18:34:40 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19438 for ; Tue, 1 Jul 2003 18:34:35 -0400 (EDT) From: Mukesh.Gupta@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XTht-0001b5-00 for vrrp@ietf.org; Tue, 01 Jul 2003 18:34:37 -0400 Received: from [63.78.179.216] (helo=mgw-dax1.ext.nokia.com) by ietf-mx with esmtp (Exim 4.12) id 19XThs-0001b1-00 for vrrp@ietf.org; Tue, 01 Jul 2003 18:34:36 -0400 Received: from davir01nok.americas.nokia.com (davir01nok.americas.nokia.com [172.18.242.84]) by mgw-dax1.ext.nokia.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h61MYZ118818 for ; Tue, 1 Jul 2003 17:34:35 -0500 (CDT) Received: from daebh002.NOE.Nokia.com (unverified) by davir01nok.americas.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Tue, 1 Jul 2003 17:34:32 -0500 Received: from daebe009.NOE.Nokia.com ([172.18.242.190]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Tue, 1 Jul 2003 17:34:31 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [VRRP] Need agenda items for the IETF meeting Date: Tue, 1 Jul 2003 17:34:30 -0500 Message-ID: <8D260779A766FB4A9C1739A476F84FA42ABD0A@daebe009.americas.nokia.com> Thread-Topic: [VRRP] Need agenda items for the IETF meeting Thread-Index: AcNABPYQMwHb0W5qTUWxpZaa6K8+hwAG2TcQ To: , , Cc: , , , , X-OriginalArrivalTime: 01 Jul 2003 22:34:31.0161 (UTC) FILETIME=[F0530690:01C34020] Content-Transfer-Encoding: quoted-printable Sender: vrrp-admin@ietf.org Errors-To: vrrp-admin@ietf.org X-BeenThere: vrrp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Virtual Router Redundancy Protocol List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Hi Bob, Sorry that your email had to wait for a while in the pending mail queue = because it was probably not sent from the email address that is = subscribed to vrrp wg mailing list. Would it be possible for any of your co-workers to prepare a small = presentation on this and talk about it in the meeting ?? We can = certainly reserve a slot for this presentation. Is it possible for you = to give us the name of the person who is ready to talk about it in the = meeting ? regards Mukesh > -----Original Message----- > From: ext Robert (Bob) W. Hott [mailto:hottrw@nswc.navy.mil] > Sent: Thursday, June 26, 2003 3:33 PM > To: Radia Perlman - Boston Center for Networking; vrrp@ietf.org > Cc: kodonog@titanic.nswc.navy.mil; dmarlow@titanic.nswc.navy.mil; > bchappe@nswc.navy.mil; tplunke@titanic.nswc.navy.mil; Lee S Carmichael > Subject: Re: [VRRP] Need agenda items for the IETF meeting >=20 >=20 > Radia, > About a month ago, there was a brief discussion about the > granularity of the timers and proprietary solutions that use=20 > sub-second > timers. Survivability solutions, such as VRRP are of interest=20 > to the US > Navy. Selecting proprietary implementations of VRRP, or similar > technologies, are desirable only when open standard solutions are not > available. It would be nice to hear about proposals that=20 > would introduce > sub-second timers to VRRP. Knowing that they may not scale for > Internet-wide solutions, such an interoperable, open standard could be > used for specific, controlled, networks with high > reliability/availability requirements. >=20 > While I will not be in attendance, several co-workers=20 > will. We could > briefly discuss our needs, from a high level perspective, if=20 > needed. We > would be the end-user of such a capability. We would certainly like to > see this pursued with IPv6, if it is not looked at for IPv4. We would > interested in hearing about the potential adding such a=20 > capability into > VRRP, or the reasons why it should be avoided. >=20 > Please consider this a request for such a discussion at=20 > the upcoming > IETF. Thank you. >=20 > Bob Hott >=20 > Radia Perlman - Boston Center for Networking wrote: >=20 > > Please send ideas for things to talk about at the > > next IETF meeting. I'd prefer you "multicast" > > it to the vrrp list rather than unicasting to me > > and Mukesh, but if you're shy, feel free to > > just send it to us. > > > > Thanks, > > > > Radia > > > > _______________________________________________ > > vrrp mailing list > > vrrp@ietf.org > > https://www1.ietf.org/mailman/listinfo/vrrp >=20 > -- > Robert (Bob) W. Hott > Naval Surface Warfare Center Dahlgren Division > Code B35, Bldg. 1500/A110 > 17320 Dahlgren Road > Dahlgren, VA 22448-5100 >=20 > Voice: (540) 653-1497 > FAX: (540) 653-8673 >=20 >=20 >=20 > _______________________________________________ > vrrp mailing list > vrrp@ietf.org > https://www1.ietf.org/mailman/listinfo/vrrp >=20 _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Tue Jul 1 19:09:29 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20171 for ; Tue, 1 Jul 2003 19:09:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XUFD-0003jL-GT for vrrp-archive@odin.ietf.org; Tue, 01 Jul 2003 19:09:03 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h61N93F7014338 for vrrp-archive@odin.ietf.org; Tue, 1 Jul 2003 19:09:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XUFD-0003jB-Ct for vrrp-web-archive@optimus.ietf.org; Tue, 01 Jul 2003 19:09:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20159 for ; Tue, 1 Jul 2003 19:08:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XUFA-0001zd-00 for vrrp-web-archive@ietf.org; Tue, 01 Jul 2003 19:09:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19XUF9-0001za-00 for vrrp-web-archive@ietf.org; Tue, 01 Jul 2003 19:08:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XUFB-0003iZ-2W; Tue, 01 Jul 2003 19:09:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XUEc-0003i0-Ox for vrrp@optimus.ietf.org; Tue, 01 Jul 2003 19:08:26 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20155 for ; Tue, 1 Jul 2003 19:08:21 -0400 (EDT) From: Mukesh.Gupta@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XUEZ-0001zS-00 for vrrp@ietf.org; Tue, 01 Jul 2003 19:08:23 -0400 Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 19XUEY-0001zO-00 for vrrp@ietf.org; Tue, 01 Jul 2003 19:08:22 -0400 Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33]) by mgw-x1.nokia.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h61N8Ma14003 for ; Wed, 2 Jul 2003 02:08:22 +0300 (EET DST) Received: from esebh004.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Wed, 2 Jul 2003 02:08:22 +0300 Received: from daebh001.NOE.Nokia.com ([172.18.242.231]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Wed, 2 Jul 2003 02:08:22 +0300 Received: from daebe009.NOE.Nokia.com ([172.18.242.190]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Tue, 1 Jul 2003 16:08:01 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Tue, 1 Jul 2003 18:08:01 -0500 Message-ID: <8D260779A766FB4A9C1739A476F84FA42ABD0B@daebe009.americas.nokia.com> Thread-Topic: [VRRP] Need agenda items for the IETF meeting Thread-Index: AcNABPYQMwHb0W5qTUWxpZaa6K8+hwAH4CWQ To: Cc: X-OriginalArrivalTime: 01 Jul 2003 23:08:02.0133 (UTC) FILETIME=[9EF50050:01C34025] Content-Transfer-Encoding: quoted-printable Subject: [VRRP] Draft Agenda for VRRP WG meeting in IETF57th. 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: quoted-printable Content-Transfer-Encoding: quoted-printable Folks, Here is the draft agenda for the meeting. Please send a mail to Me or = Radia in oder to add items to the agenda. ************ Virtual Router Redundancy Protocol WG (vrrp) WEDNESDAY, July 16, 2003 at 0900-1130 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D CHAIRS: Mukesh Gupta Radia Perlman AGENDA: Agenda Bashing Chairs 5 mins Milestones/Plans Chairs 5 mins Current Drafts's status Chairs 5 minutes Review current VRRP Bob Hinden 20 mins Drafts VRRPv3 MIB Chairs 10 minutes Sub-second Timers ???? 15 minutes ************ regards Mukesh _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Thu Jul 3 19:24:27 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22840 for ; Thu, 3 Jul 2003 19:24:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YDQi-0008Va-Ph for vrrp-archive@odin.ietf.org; Thu, 03 Jul 2003 19:23:56 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h63NNumZ032700 for vrrp-archive@odin.ietf.org; Thu, 3 Jul 2003 19:23:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YDQi-0008VL-LQ for vrrp-web-archive@optimus.ietf.org; Thu, 03 Jul 2003 19:23:56 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22312 for ; Thu, 3 Jul 2003 19:23:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YDHk-0003EJ-00 for vrrp-web-archive@ietf.org; Thu, 03 Jul 2003 19:14:40 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19YCru-00071p-00 for vrrp-web-archive@ietf.org; Thu, 03 Jul 2003 18:47:58 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YCg8-0000Sw-4k for vrrp-web-archive@ietf.org; Thu, 03 Jul 2003 18:35:48 -0400 Date: Thu, 03 Jul 2003 18:35:48 -0400 Message-ID: <20030703223548.4508.98909.Mailman@www1.ietf.org> Subject: ietf.org mailing list memberships reminder From: mailman-owner@www1.ietf.org To: vrrp-web-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: mailman-admin@ietf.org Errors-To: mailman-admin@ietf.org X-BeenThere: mailman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk There was an error in the last monthly reminder, in that the NOTE WELL statement (below) was not included. Therefore, the reminder is being sent out again. This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, vrrp-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. *************************************************************************** Note Well All statements related to the activities of the IETF and addressed to the IETF are subject to all provisions of Section 10 of RFC 2026, which grants to the IETF and its participants certain licenses and rights in such statements. Such statements include verbal statements in IETF meetings, as well as written and electronic communications made at any time or place, which are addressed to * the IETF plenary session, * any IETF working group or portion thereof, * the IESG, or any member thereof on behalf of the IESG, * the IAB or any member thereof on behalf of the IAB, * any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, * the RFC Editor or the Internet-Drafts function Statements made outside of an IETF meeting, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not subject to these provisions. *************************************************************************** If you have questions, problems, comments, etc, send them to mailman-owner@www1.ietf.org. Thanks! Passwords for vrrp-web-archive@ietf.org: List Password // URL ---- -------- vrrp@ietf.org mPhD https://www1.ietf.org/mailman/options/vrrp/vrrp-web-archive%40ietf.org From exim@www1.ietf.org Mon Jul 7 13:31:34 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04618 for ; Mon, 7 Jul 2003 13:31:33 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZZpR-0007IV-Ue for vrrp-archive@odin.ietf.org; Mon, 07 Jul 2003 13:31:05 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h67HV5Qj028050 for vrrp-archive@odin.ietf.org; Mon, 7 Jul 2003 13:31:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZZpR-0007IL-RL for vrrp-web-archive@optimus.ietf.org; Mon, 07 Jul 2003 13:31:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04603 for ; Mon, 7 Jul 2003 13:31:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZZpP-0007DX-00 for vrrp-web-archive@ietf.org; Mon, 07 Jul 2003 13:31:03 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ZZpP-0007DR-00 for vrrp-web-archive@ietf.org; Mon, 07 Jul 2003 13:31:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZZpO-0007HP-AI; Mon, 07 Jul 2003 13:31:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XoJJ-00038X-EG for vrrp@optimus.ietf.org; Wed, 02 Jul 2003 16:34:37 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13453; Wed, 2 Jul 2003 16:34:32 -0400 (EDT) Message-Id: <200307022034.QAA13453@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: vrrp@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Wed, 02 Jul 2003 16:34:31 -0400 Subject: [VRRP] I-D ACTION:draft-ietf-vrrp-ipv6-spec-05.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: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Virtual Router Redundancy Protocol Working Group of the IETF. Title : Virtual Router Redundancy Protocol for IPv6 Author(s) : R. Hinden Filename : draft-ietf-vrrp-ipv6-spec-05.txt Pages : 27 Date : 2003-7-2 This memo defines the Virtual Router Redundancy Protocol (VRRP) for IPv6. It is version three (3) of the protocol. It is based on the original version of VRRP (version 2) for IPv4 that is defined in RFC2338. VRRP specifies an election protocol that dynamically assigns responsibility for a virtual router to one of the VRRP routers on a LAN. The VRRP router controlling the IP address associated with a virtual router is called the Master, and forwards packets sent to this IP address. The election process provides dynamic fail over in the forwarding responsibility should the Master become unavailable. The advantage gained from using VRRP for IPv6 is a quicker switch over to back up routers than can be obtained with standard IPv6 Neighbor Discovery [ND] mechanisms. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-vrrp-ipv6-spec-05.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-vrrp-ipv6-spec-05.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-vrrp-ipv6-spec-05.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-7-2162041.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-vrrp-ipv6-spec-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-vrrp-ipv6-spec-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-7-2162041.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Mon Jul 7 13:31:34 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04630 for ; Mon, 7 Jul 2003 13:31:34 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZZpS-0007Iq-F7 for vrrp-archive@odin.ietf.org; Mon, 07 Jul 2003 13:31:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h67HV6p8028068 for vrrp-archive@odin.ietf.org; Mon, 7 Jul 2003 13:31:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZZpS-0007Id-CD for vrrp-web-archive@optimus.ietf.org; Mon, 07 Jul 2003 13:31:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04606 for ; Mon, 7 Jul 2003 13:31:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZZpQ-0007Db-00 for vrrp-web-archive@ietf.org; Mon, 07 Jul 2003 13:31:04 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ZZpP-0007DS-00 for vrrp-web-archive@ietf.org; Mon, 07 Jul 2003 13:31:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZZpO-0007HD-1R; Mon, 07 Jul 2003 13:31:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XoJF-00037r-Nz for vrrp@optimus.ietf.org; Wed, 02 Jul 2003 16:34:33 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13419; Wed, 2 Jul 2003 16:34:28 -0400 (EDT) Message-Id: <200307022034.QAA13419@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: vrrp@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Wed, 02 Jul 2003 16:34:27 -0400 Subject: [VRRP] I-D ACTION:draft-ietf-vrrp-spec-v2-08.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: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Virtual Router Redundancy Protocol Working Group of the IETF. Title : Virtual Router Redundancy Protocol Author(s) : R. Hinden et al. Filename : draft-ietf-vrrp-spec-v2-08.txt Pages : 31 Date : 2003-7-2 This memo defines the Virtual Router Redundancy Protocol (VRRP). VRRP specifies an election protocol that dynamically assigns responsibility for a virtual router to one of the VRRP routers on a LAN. The VRRP router controlling the IP address(es) associated with a virtual router is called the Master, and forwards packets sent to these IP addresses. The election process provides dynamic fail over in the forwarding responsibility should the Master become unavailable. This allows any of the virtual router IP addresses on the LAN to be used as the default first hop router by end-hosts. The advantage gained from using VRRP is a higher availability default path without requiring configuration of dynamic routing or router discovery protocols on every end-host. This document replaces RFC2338 'Virtual Router Redundancy Protocol'. RFC2338 will become historic. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-vrrp-spec-v2-08.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-vrrp-spec-v2-08.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-vrrp-spec-v2-08.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-7-2162031.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-vrrp-spec-v2-08.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-vrrp-spec-v2-08.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-7-2162031.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Mon Jul 7 15:17:36 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10023 for ; Mon, 7 Jul 2003 15:17:36 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZbU3-0006HR-R9 for vrrp-archive@odin.ietf.org; Mon, 07 Jul 2003 15:17:08 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h67JH78o024137 for vrrp-archive@odin.ietf.org; Mon, 7 Jul 2003 15:17:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZbU3-0006HE-Lm for vrrp-web-archive@optimus.ietf.org; Mon, 07 Jul 2003 15:17:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09992 for ; Mon, 7 Jul 2003 15:17:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZbU2-0001HH-00 for vrrp-web-archive@ietf.org; Mon, 07 Jul 2003 15:17:06 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ZbU1-0001HE-00 for vrrp-web-archive@ietf.org; Mon, 07 Jul 2003 15:17:05 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZbTx-0006Gk-92; Mon, 07 Jul 2003 15:17:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZbTt-0006GZ-O7 for vrrp@optimus.ietf.org; Mon, 07 Jul 2003 15:16:57 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09965 for ; Mon, 7 Jul 2003 15:16:55 -0400 (EDT) From: Mukesh.Gupta@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZbTs-0001H8-00 for vrrp@ietf.org; Mon, 07 Jul 2003 15:16:56 -0400 Received: from [63.78.179.216] (helo=mgw-dax1.ext.nokia.com) by ietf-mx with esmtp (Exim 4.12) id 19ZbTr-0001H1-00 for vrrp@ietf.org; Mon, 07 Jul 2003 15:16:55 -0400 Received: from davir01nok.americas.nokia.com (davir01nok.americas.nokia.com [172.18.242.84]) by mgw-dax1.ext.nokia.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h67JGr112950 for ; Mon, 7 Jul 2003 14:16:53 -0500 (CDT) Received: from daebh002.NOE.Nokia.com (unverified) by davir01nok.americas.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Mon, 7 Jul 2003 14:16:53 -0500 Received: from daebe009.NOE.Nokia.com ([172.18.242.190]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Mon, 7 Jul 2003 14:15:52 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 7 Jul 2003 14:15:51 -0500 Message-ID: <8D260779A766FB4A9C1739A476F84FA476C31B@daebe009.americas.nokia.com> Thread-Topic: Preparing WGs for the upcoming meeting in Vienna Thread-Index: AcMw9JwvWqA7NbNORFaZk+0GAPBjEgTx4Wvw To: X-OriginalArrivalTime: 07 Jul 2003 19:15:52.0148 (UTC) FILETIME=[2E847940:01C344BC] Content-Transfer-Encoding: quoted-printable Subject: [VRRP] FW: Preparing WGs for the upcoming meeting in Vienna 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: quoted-printable Content-Transfer-Encoding: quoted-printable FYI.. -----Original Message----- From: ext Paul Hoffman / VPNC [mailto:paul.hoffman@vpnc.org] Sent: Wednesday, June 11, 2003 9:56 AM To: wgchairs@ietf.org Subject: Preparing WGs for the upcoming meeting in Vienna Greetings again. The meeting in Vienna in a few weeks will probably be the first for many of the people in your WGs. A little WG-wide nudge a few weeks before the face-to-face meeting might get more effective results. This might be a good time to send a message to the WG mailing list, wearing your WG hat, reminding folks: - Newcomers can learn a lot ahead of time by reading the Tao of the IETF at . The newcomer orientation on Sunday (this year, at 1PM) is useful, but it is even more useful if they have read the Tao first. - It is a good idea to at least skim the WG archives for the past four months before the meeting to help prevent rehashing items that have already been decided and to help focus on items that need more review. - Similarly, it is a good idea to re-read the WG's charter before the meeting. Heck, many WG chairs could get value from this... - Many IETF areas have area-wide meetings. People who are interested in more than just one WG can get a feel for what is happening in other areas by going to these meetings. - The "Note Well" notice is serious. It can be found at , and will be given on paper in the registration packets. --Paul Hoffman, Director --VPN Consortium _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Mon Jul 7 15:37:32 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10939 for ; Mon, 7 Jul 2003 15:37:32 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZbnL-0007I4-UC for vrrp-archive@odin.ietf.org; Mon, 07 Jul 2003 15:37:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h67Jb3RF028024 for vrrp-archive@odin.ietf.org; Mon, 7 Jul 2003 15:37:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZbnL-0007Hv-PY for vrrp-web-archive@optimus.ietf.org; Mon, 07 Jul 2003 15:37:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10916 for ; Mon, 7 Jul 2003 15:37:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZbnK-0001Ww-00 for vrrp-web-archive@ietf.org; Mon, 07 Jul 2003 15:37:02 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ZbnJ-0001Wt-00 for vrrp-web-archive@ietf.org; Mon, 07 Jul 2003 15:37:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZbnJ-0007GN-8R; Mon, 07 Jul 2003 15:37:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZbmX-0007Ez-IL for vrrp@optimus.ietf.org; Mon, 07 Jul 2003 15:36:13 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10877; Mon, 7 Jul 2003 15:36:10 -0400 (EDT) From: Mukesh.Gupta@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZbmV-0001WP-00; Mon, 07 Jul 2003 15:36:11 -0400 Received: from [63.78.179.217] (helo=mgw-dax2.ext.nokia.com) by ietf-mx with esmtp (Exim 4.12) id 19ZbmV-0001WM-00; Mon, 07 Jul 2003 15:36:11 -0400 Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85]) by mgw-dax2.ext.nokia.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h67JaAG08021; Mon, 7 Jul 2003 14:36:10 -0500 (CDT) Received: from daebh001.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Mon, 7 Jul 2003 14:36:06 -0500 Received: from daebe009.NOE.Nokia.com ([172.18.242.190]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Mon, 7 Jul 2003 12:35:34 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 7 Jul 2003 14:35:34 -0500 Message-ID: <8D260779A766FB4A9C1739A476F84FA476C31C@daebe009.americas.nokia.com> Thread-Topic: VRRP WG meeting agenda. Thread-Index: AcNEvu7KbvHRRyigR9yGmabaw8j+lg== To: Cc: , , , X-OriginalArrivalTime: 07 Jul 2003 19:35:34.0924 (UTC) FILETIME=[EF81C4C0:01C344BE] Content-Transfer-Encoding: quoted-printable Subject: [VRRP] VRRP WG meeting agenda. 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: quoted-printable Content-Transfer-Encoding: quoted-printable Virtual Router Redundancy Protocol WG (vrrp) WEDNESDAY, July 16, 2003 at 0900-1130 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D CHAIRS: Mukesh Gupta Radia Perlman AGENDA: Agenda Bashing Chairs 5 mins Milestones/Plans Chairs 5 mins Current Drafts' status Chairs 5 minutes Review VRRP Drafts Bob Hinden 20 mins http://ietf.org/internet-drafts/draft-ietf-vrrp-spec-v2-08.txt http://ietf.org/internet-drafts/draft-ietf-vrrp-ipv6-spec-05.txt VRRPv3 MIB Chairs 10 minutes http://ietf.org/internet-drafts/draft-ietf-vrrp-ipv6-mib-00.txt Sub-second Timers Karen O'Donoghue 15 minutes _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Mon Jul 7 18:26:30 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19951 for ; Mon, 7 Jul 2003 18:26:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZeQu-0002O6-D5 for vrrp-archive@odin.ietf.org; Mon, 07 Jul 2003 18:26:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h67MQ4Of009174 for vrrp-archive@odin.ietf.org; Mon, 7 Jul 2003 18:26:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZeQu-0002Nt-9f for vrrp-web-archive@optimus.ietf.org; Mon, 07 Jul 2003 18:26:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19943 for ; Mon, 7 Jul 2003 18:25:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZeQr-0003iK-00 for vrrp-web-archive@ietf.org; Mon, 07 Jul 2003 18:26:01 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ZeQq-0003iH-00 for vrrp-web-archive@ietf.org; Mon, 07 Jul 2003 18:26:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZeQq-0002N6-VV; Mon, 07 Jul 2003 18:26:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZeQR-0002JP-IY for vrrp@optimus.ietf.org; Mon, 07 Jul 2003 18:25:35 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19911 for ; Mon, 7 Jul 2003 18:25:31 -0400 (EDT) From: Mukesh.Gupta@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZeQO-0003ht-00 for vrrp@ietf.org; Mon, 07 Jul 2003 18:25:32 -0400 Received: from [63.78.179.217] (helo=mgw-dax2.ext.nokia.com) by ietf-mx with esmtp (Exim 4.12) id 19ZeQO-0003hq-00 for vrrp@ietf.org; Mon, 07 Jul 2003 18:25:32 -0400 Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85]) by mgw-dax2.ext.nokia.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h67MPVG17152 for ; Mon, 7 Jul 2003 17:25:31 -0500 (CDT) Received: from daebh002.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Mon, 7 Jul 2003 17:24:49 -0500 Received: from daebe009.NOE.Nokia.com ([172.18.242.190]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Mon, 7 Jul 2003 17:24:14 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 7 Jul 2003 17:24:13 -0500 Message-ID: <8D260779A766FB4A9C1739A476F84FA476C31E@daebe009.americas.nokia.com> Thread-Topic: text conferencing at ietf57 Thread-Index: AcNEzQzDpqYgVU5uRoahXgDBlenh6QACSlZg To: X-OriginalArrivalTime: 07 Jul 2003 22:24:14.0471 (UTC) FILETIME=[7F3A1970:01C344D6] Content-Transfer-Encoding: quoted-printable Subject: [VRRP] Volunteer scribe ?? 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: quoted-printable Content-Transfer-Encoding: quoted-printable Do we have any volunteer scribe for IETF57 in the WG ?? -----Original Message----- From: ext Marshall Rose [mailto:mrose+mtr.ietf@dbc.mtview.ca.us] Sent: Monday, July 07, 2003 2:09 PM To: wgchairs@ietf.org Subject: text conferencing at ietf57 Remote Access for the 57th IETF meeting in Vienna: Text Conferencing At each IETF meeting, two of the working group meeting rooms are = equipped for video multicast and remote participation. That is, for every IETF meeting slot, two of the working groups can see and hear the meeting. For the 57th IETF, in *addition* to the usual network A/V, text conferencing will be provided for every working group that meets. All of the conference rooms will be hosted on ietf.jabber.at and each is named using the official IETF abbreviation found in the agenda (e.g., "apparea", "dhc", "forces", and so on -- for all the examples that follow, we'll use "foobar" as the abbreviation). Each conference room also has a 'bot which records everything that gets sent. So, the minute taker can review this information right after the meeting. In addition to the conference rooms for each wg that is meeting, there are three others of general interest: bar, hallway, and plenary. =20 1. Before the meeting: 1.1. If you want to participate =20 If you don't already have one, get yourself a Jabber client, here are = some suggestions: platform suggestion -------- ---------- win32 http://exodus.jabberstudio.org 'nix http://gabber.sf.net macos http://jabberfox.sf.net When you start the client for the first time, it will eventually ask if you want to register on a public server. Go ahead and do that.=20 =20 If you want to find out more, instead of choosing these defaults, here are pointers to some additional information: =20 list of clients: http://www.jabber.org/user/clientlist.php howto: http://www.jabber.org/user/userguide/ server list: http://www.jabber.org/user/publicservers.php To make sure everything is running ok, do a "Join Group Chat" with your Jabber client: =20 Group/Room: testing Server: conference.ietf.jabber.com This conference room is up and running right now (although probably no one will be in it when you connect). =20 1.2. What the Chair does =20 If you want to make text conferencing available, you'll need to have a volunteer scribe in the meeting room. The scribe will be typing in a running commentary as to what's going on in the room (who's presenting, what question is being asked, etc.) =20 So, why not send an email out on the mailing list now, before the meeting, to ask for volunteers? =20 =20 2. At the meeting 2.1. What the Chair does When a session starts, the chair asks if someone in the room is willing to act as "scribe". If no one volunteers, read no further, we're done! Otherwise, the scribe should do a "Join Group Chat" with their Jabber client, e.g., Group/Room: foobar Server: conference.ietf.jabber.com 2.2. What the Scribe does The scribe types in a running commentary as to what's going on in the room. For example, if a speaker makes a presentation, the scribe types in the URL for the presentation (more on this in a bit). Simlarly, during question time, a remote participant can type a question into the room and the scribe can pass it on to the speaker. 2.3. What each Presenter does Each presenter should put a copy of their presentation on a web server somewhere, so remote participants can follow along.=20 =20 2.4. Where to find the conference log =20 [ tbd: i'm still working on this one... ] =20 ####### _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Mon Jul 14 20:21:36 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09783 for ; Mon, 14 Jul 2003 20:21:36 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cDZ6-00075V-M8 for vrrp-archive@odin.ietf.org; Mon, 14 Jul 2003 20:21:08 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6F0L8b6027241 for vrrp-archive@odin.ietf.org; Mon, 14 Jul 2003 20:21:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cDZ6-00075I-Ho for vrrp-web-archive@optimus.ietf.org; Mon, 14 Jul 2003 20:21:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09730 for ; Mon, 14 Jul 2003 20:21:06 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cDZ4-0003Os-00 for vrrp-web-archive@ietf.org; Mon, 14 Jul 2003 20:21:06 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19cDZ3-0003Oo-00 for vrrp-web-archive@ietf.org; Mon, 14 Jul 2003 20:21:05 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cDYy-00074c-Mz; Mon, 14 Jul 2003 20:21:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cDY2-00071k-UR for vrrp@optimus.ietf.org; Mon, 14 Jul 2003 20:20:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09614 for ; Mon, 14 Jul 2003 20:20:00 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cDY0-0003Mj-00 for vrrp@ietf.org; Mon, 14 Jul 2003 20:20:00 -0400 Received: from [216.142.75.231] (helo=exmail.bivio.net) by ietf-mx with smtp (Exim 4.12) id 19cDXy-0003Ma-00 for vrrp@ietf.org; Mon, 14 Jul 2003 20:19:58 -0400 Received: from dprovan1 ([192.168.24.137]) by exmail.bivio.net with Microsoft SMTPSVC(5.0.2195.2966); Mon, 14 Jul 2003 17:19:52 -0700 From: "Don Provan" To: Subject: RE: [VRRP] I-D ACTION:draft-ietf-vrrp-spec-v2-08.txt Date: Mon, 14 Jul 2003 17:19:52 -0700 Message-ID: <004d01c34a66$cfb4fb50$8918a8c0@corp.networkrobots.com> X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Importance: Normal In-Reply-To: <200307022034.QAA13419@ietf.org> X-OriginalArrivalTime: 15 Jul 2003 00:19:52.0939 (UTC) FILETIME=[CFC48BB0:01C34A66] 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: , Sorry, nothing technical, but I couldn't help but notice that the Author's Addresses in section 15 refer to at least two companies that no longer exist. Perhaps it's time to refresh? -don > -----Original Message----- > From: vrrp-admin@ietf.org [mailto:vrrp-admin@ietf.org]On Behalf Of > Internet-Drafts@ietf.org > Sent: Wednesday, July 02, 2003 1:34 PM > To: IETF-Announce: > Cc: vrrp@ietf.org > Subject: [VRRP] I-D ACTION:draft-ietf-vrrp-spec-v2-08.txt > > > A New Internet-Draft is available from the on-line > Internet-Drafts directories. > This draft is a work item of the Virtual Router Redundancy > Protocol Working Group of the IETF. > > Title : Virtual Router Redundancy Protocol > Author(s) : R. Hinden et al. > Filename : draft-ietf-vrrp-spec-v2-08.txt > Pages : 31 > Date : 2003-7-2 > > This memo defines the Virtual Router Redundancy Protocol (VRRP). > VRRP specifies an election protocol that dynamically assigns > responsibility for a virtual router to one of the VRRP routers on a > LAN. The VRRP router controlling the IP address(es) associated with > a virtual router is called the Master, and forwards packets sent to > these IP addresses. The election process provides dynamic fail over > in the forwarding responsibility should the Master become > unavailable. This allows any of the virtual router IP addresses on > the LAN to be used as the default first hop router by end-hosts. The > advantage gained from using VRRP is a higher availability default > path without requiring configuration of dynamic routing or router > discovery protocols on every end-host. > This document replaces RFC2338 'Virtual Router Redundancy Protocol'. > RFC2338 will become historic. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-vrrp-spec-v2-08.txt > > To remove yourself from the IETF Announcement list, send a message to > ietf-announce-request with the word unsubscribe in the body > of the message. > > Internet-Drafts are also available by anonymous FTP. Login > with the username > "anonymous" and a password of your e-mail address. After logging in, > type "cd internet-drafts" and then > "get draft-ietf-vrrp-spec-v2-08.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-vrrp-spec-v2-08.txt". > > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant > mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Tue Jul 15 10:01:42 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18863 for ; Tue, 15 Jul 2003 10:01:42 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cQMn-0007GP-2K for vrrp-archive@odin.ietf.org; Tue, 15 Jul 2003 10:01:17 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6FE1HU9027915 for vrrp-archive@odin.ietf.org; Tue, 15 Jul 2003 10:01:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cQMm-0007GA-QC for vrrp-web-archive@optimus.ietf.org; Tue, 15 Jul 2003 10:01:16 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18852 for ; Tue, 15 Jul 2003 10:01:11 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cQMk-00029c-00 for vrrp-web-archive@ietf.org; Tue, 15 Jul 2003 10:01:14 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19cQMf-00029Z-00 for vrrp-web-archive@ietf.org; Tue, 15 Jul 2003 10:01:09 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cQMY-0007Et-52; Tue, 15 Jul 2003 10:01:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cQLi-0007E2-RN for vrrp@optimus.ietf.org; Tue, 15 Jul 2003 10:00:10 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18797 for ; Tue, 15 Jul 2003 10:00:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cQLc-000294-00 for vrrp@ietf.org; Tue, 15 Jul 2003 10:00:04 -0400 Received: from mailout.zma.compaq.com ([161.114.64.105] helo=zmamail05.zma.compaq.com) by ietf-mx with esmtp (Exim 4.12) id 19cQLR-00028u-00 for vrrp@ietf.org; Tue, 15 Jul 2003 09:59:54 -0400 Received: from taynzmail03.nz-tay.cpqcorp.net (taynzmail03.nz-tay.cpqcorp.net [16.47.4.103]) by zmamail05.zma.compaq.com (Postfix) with ESMTP id 40DCCBBBE for ; Tue, 15 Jul 2003 09:59:27 -0400 (EDT) Received: from lassie.ucx.lkg.dec.com (lassie.ucx.lkg.dec.com [16.20.208.100]) by taynzmail03.nz-tay.cpqcorp.net (Postfix) with SMTP id F205B1E70 for ; Tue, 15 Jul 2003 09:59:26 -0400 (EDT) Received: from unknown.hostname (16.115.195.118) by lassie.ucx.lkg.dec.com (T5.4-11E, OpenVMS V7.2-2 Alpha); Tue, 15 Jul 2003 10:00:36 -0400 (EDT) Message-ID: <0b1101c34ad8$64aac390$51501410@PORTABRAIN> From: "M. T. Hollinger" To: References: <8D260779A766FB4A9C1739A476F84FA476C31E@daebe009.americas.nokia.com> Date: Tue, 15 Jul 2003 09:52:26 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Transfer-Encoding: 7bit Subject: [VRRP] Virtual MAC for IPv6 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 The vrrp-ipv6-spec-05 draft still specifies the use of virtual MAC addresses, even with IPv6. I have long disliked the use of duplicate MAC addresses for v4, which was justified with the argument that some older ARP implementations did not properly receive and parse gratuitous ARP messages. That argument does not apply to IPv6. I oppose moving this document forward until the use of virtual MAC is removed. (Alternatively, if there is a strong justification, then text could be added to the document explaining why this architecturally awful design was believed to be the best choice for the IPv6 environment.) - Mark _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Tue Jul 15 11:06:39 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23291 for ; Tue, 15 Jul 2003 11:06:39 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cRNe-0002MS-GU for vrrp-archive@odin.ietf.org; Tue, 15 Jul 2003 11:06:14 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6FF6ElK009072 for vrrp-archive@odin.ietf.org; Tue, 15 Jul 2003 11:06:14 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cRNe-0002MF-DB for vrrp-web-archive@optimus.ietf.org; Tue, 15 Jul 2003 11:06:14 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23248 for ; Tue, 15 Jul 2003 11:06:08 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cRNb-0002kw-00 for vrrp-web-archive@ietf.org; Tue, 15 Jul 2003 11:06:11 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19cRNW-0002kt-00 for vrrp-web-archive@ietf.org; Tue, 15 Jul 2003 11:06:06 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cRNQ-0002L2-P5; Tue, 15 Jul 2003 11:06:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cRMZ-0002Ke-8n for vrrp@optimus.ietf.org; Tue, 15 Jul 2003 11:05:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23221 for ; Tue, 15 Jul 2003 11:05:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cRMW-0002kc-00 for vrrp@ietf.org; Tue, 15 Jul 2003 11:05:04 -0400 Received: from mailhost.iprg.nokia.com ([205.226.5.12]) by ietf-mx with esmtp (Exim 4.12) id 19cRMG-0002kD-00 for vrrp@ietf.org; Tue, 15 Jul 2003 11:04:48 -0400 Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69]) by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id IAA17901; Tue, 15 Jul 2003 08:03:21 -0700 (PDT) Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h6FF3K006715; Tue, 15 Jul 2003 08:03:20 -0700 X-mProtect: <200307151503> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (81.160.151.202, claiming to be "spruce.iprg.nokia.com") by darkstar.iprg.nokia.com smtpdfXA7LU; Tue, 15 Jul 2003 08:03:18 PDT Message-Id: <4.3.2.7.2.20030715074329.03553840@mailhost.iprg.nokia.com> X-Sender: hinden@mailhost.iprg.nokia.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 15 Jul 2003 08:02:37 -0700 To: "M. T. Hollinger" From: Bob Hinden Subject: Re: [VRRP] Virtual MAC for IPv6 Cc: In-Reply-To: <0b1101c34ad8$64aac390$51501410@PORTABRAIN> References: <8D260779A766FB4A9C1739A476F84FA476C31E@daebe009.americas.nokia.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed 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: , Mark, At 06:52 AM 7/15/2003, M. T. Hollinger wrote: >The vrrp-ipv6-spec-05 draft still specifies the use of virtual MAC >addresses, even with IPv6. > >I have long disliked the use of duplicate MAC addresses for v4, which was >justified with the argument that some older ARP implementations did not >properly receive and parse gratuitous ARP messages. > >That argument does not apply to IPv6. I oppose moving this document forward >until the use of virtual MAC is removed. (Alternatively, if there is a >strong justification, then text could be added to the document explaining >why this architecturally awful design was believed to be the best choice for >the IPv6 environment.) I don't agree that it is so bad or as you say an "architecturally awful design". I have thought about it as one of the great MAC address hacks :-) The advantage of this approach is that it works without the hosts having to do anything (e.g., receive and process an ND message, update tables, etc.). The switch over is transparent to the hosts. This approach is well proven in the IPv4 version of VRRP. It is running operationally in many places and I am not aware of any problems. Are you aware of any technical problems with the virtual MAC address approach? Thanks, Bob _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Thu Jul 17 09:29:45 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05827 for ; Thu, 17 Jul 2003 09:29:45 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19d8ox-0001Il-03 for vrrp-archive@odin.ietf.org; Thu, 17 Jul 2003 09:29:19 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6HDTI03005002 for vrrp-archive@odin.ietf.org; Thu, 17 Jul 2003 09:29:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19d8ow-0001Ib-Dr for vrrp-web-archive@optimus.ietf.org; Thu, 17 Jul 2003 09:29:18 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05816 for ; Thu, 17 Jul 2003 09:29:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19d8ou-0006TM-00 for vrrp-web-archive@ietf.org; Thu, 17 Jul 2003 09:29:16 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19d8op-0006TI-00 for vrrp-web-archive@ietf.org; Thu, 17 Jul 2003 09:29:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19d8oe-0001HH-QA; Thu, 17 Jul 2003 09:29:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19d8nu-0001Gp-CZ for vrrp@optimus.ietf.org; Thu, 17 Jul 2003 09:28:14 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05797 for ; Thu, 17 Jul 2003 09:28:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19d8nr-0006TC-00 for vrrp@ietf.org; Thu, 17 Jul 2003 09:28:11 -0400 Received: from [203.197.140.35] (helo=fsnt.future.futsoft.com) by ietf-mx with esmtp (Exim 4.12) id 19d8nf-0006Sh-00 for vrrp@ietf.org; Thu, 17 Jul 2003 09:28:00 -0400 Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com (Content Technologies SMTPRS 4.3.6) with ESMTP id for ; Thu , 17 Jul 2003 18:43:56 +0530 Received: from gunav (gunav.future.futsoft.com [10.6.4.36]) by kailash.future.futsoft.com (8.12.2/8.12.2) with SMTP id h6HD4x0r028628 for ; Thu, 17 Jul 2003 18:34:59 +0530 Reply-To: From: "Gunaseelan V" To: Date: Thu, 17 Jul 2003 18:42:50 +0530 Message-ID: <000901c34c65$205ed6c0$2404060a@future.futsoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Content-Transfer-Encoding: 7bit Subject: [VRRP] Query on Associated IP address and Primary IP address 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 VRRP Gurus I just started looking into VRRP protocol and am a beginner in this case, on browsing the RFC 2338 and other related docs, I am still not clear with the following points 1) What are the Associated IP addresses? is it the multiple IP addresses assigned to the same Physical Interface (means alias or multinetting) or doe sit belong to diff physical interfaces of a Virtual Router 2) What is Primary IP address? Is it one of the associated IP addresses within a router selected based on the some algorithm (say first one or least one etc) 3)I understood the concept of switchover from Master to Back up on Failure/Master Down timer event etc, but how the router which is on the other side (say WAN) knows about route to Hosts governed by VRRP? Here the Back up router once becomes the Master will forward the IP packets, if so does this router propagates on WAN Side thru any routing protocol about the Hosts reachability on the LAN side. If Yes When it should start propagating (only after becoming the Master or even during Back Up) Think will limit my doubts with this now, Thanks for your efforts and patience . Best Regards Gunaseelan V ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com ********************************************************************** _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Fri Jul 18 09:40:52 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29986 for ; Fri, 18 Jul 2003 09:40:52 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dVTE-0006zV-Jt for vrrp-archive@odin.ietf.org; Fri, 18 Jul 2003 09:40:25 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6IDeO2f026850 for vrrp-archive@odin.ietf.org; Fri, 18 Jul 2003 09:40:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dVTE-0006yz-2h for vrrp-web-archive@optimus.ietf.org; Fri, 18 Jul 2003 09:40:24 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29977 for ; Fri, 18 Jul 2003 09:40:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dVTC-00013O-00 for vrrp-web-archive@ietf.org; Fri, 18 Jul 2003 09:40:22 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19dVT6-00013K-00 for vrrp-web-archive@ietf.org; Fri, 18 Jul 2003 09:40:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dVSr-0006xh-FA; Fri, 18 Jul 2003 09:40:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dVRw-0006r6-2Q for vrrp@optimus.ietf.org; Fri, 18 Jul 2003 09:39:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29916 for ; Fri, 18 Jul 2003 09:39:00 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dVRu-00012k-00 for vrrp@ietf.org; Fri, 18 Jul 2003 09:39:02 -0400 Received: from [203.197.140.35] (helo=fsnt.future.futsoft.com) by ietf-mx with esmtp (Exim 4.12) id 19dVRi-00012V-00 for vrrp@ietf.org; Fri, 18 Jul 2003 09:38:51 -0400 Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com (Content Technologies SMTPRS 4.3.6) with ESMTP id ; Fri, 18 Jul 2003 18:50:38 +0530 Received: from gunav (gunav.future.futsoft.com [10.6.4.36]) by kailash.future.futsoft.com (8.12.2/8.12.2) with SMTP id h6IDBq0r021875; Fri, 18 Jul 2003 18:41:52 +0530 Reply-To: From: "Gunaseelan V" To: , Subject: RE: [VRRP] Query on Associated IP address and Primary IP address Date: Fri, 18 Jul 2003 18:49:49 +0530 Message-ID: <002e01c34d2f$44a3e820$2404060a@future.futsoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 In-Reply-To: Content-Transfer-Encoding: 7bit Sender: vrrp-admin@ietf.org Errors-To: vrrp-admin@ietf.org X-BeenThere: vrrp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Virtual Router Redundancy Protocol List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Thanks you very much for the answers and it cleared the basics for me, also I wish to put forth few more queries in the same line 1) Does the Back up router disable IP forwarding ? If Yes , is it totally on the i/f where VRRP is enabled or only Selectively like not forwarding the frames which has Virtual MAC Address . In the second case can Backup respond to Pings from hosts to its Primary IP address 2) In case of switch over from Master to Back up, how Backup will come to know about the IP address it should take care of (like how Backup will handle the IP packets not destined to its Primary IP address, here though it may be an implementation dependent, am wondering whether the new IP will ever be registered by VRRP module in its IP ,) Sorry for the disturbance caused Best Regards Gunaseelan V -----Original Message----- From: mitzel@tahoenetworks.com [mailto:mitzel@tahoenetworks.com]On Behalf Of mitzel@acm.org Sent: Friday, 18 July 2003 12:54 AM To: gunav@future.futsoft.com; vrrp@ietf.org Cc: mitzel@acm.org Subject: Re: [VRRP] Query on Associated IP address and Primary IP address --- Gunaseelan V wrote: > 1) What are the Associated IP addresses? > is it the multiple IP addresses assigned to the same > Physical Interface (means alias or multinetting) or doe > sit belong to diff physical interfaces of a Virtual Router it's all addresses on the interface running vrrp that are backed up using same vrid. typical deployments I've seen this is just a single address, but it becomes a set of addresses when alias/multinetting is deployed. > 2) What is Primary IP address? > Is it one of the associated IP addresses within a > router selected based on > the some algorithm (say first one or least one etc) you're correct that it's one of the associated ip addresses. the selection algorithm is vendor specific (explicitly tagged 'primary' address, first added, lowest numbered, etc.). the protocol specification just mandates whatever address is picked as the primary is also placed in the ip source address of any Advertisement. this ensures proper convergence if the master election tie breaker based on primary ip address comes into play. > 3)I understood the concept of switchover from Master > to Back up on Failure/Master Down timer event etc, but > how the router which is on the other side (say WAN) > knows about route to Hosts governed by VRRP? > > Here the Back up router once becomes the Master will > forward the IP packets, > if so does this router propagates on WAN Side thru > any routing protocol > about the Hosts reachability on the LAN side. > If Yes When it should start propagating (only after > becoming the Master or even during Back Up) the protocol specification makes no recommendations or requirements on the routing infrastructure when a dynamic routing protocol is used to advertise reachability to the vrrp backed up LAN. in the simplest case all of the vrrp routers advertise reachability. this may result in asymmetric forwarding, but that's not too uncommon in the current Internet routing architecture. if a vendor&customers desires to force symmetric forwarding path then they could tie reachability advertisement to vrrp master status, as you describe above, and market that as 'value added'/ differentiating feature of their product. danny ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com ********************************************************************** _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Fri Jul 18 19:03:41 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17345 for ; Fri, 18 Jul 2003 19:03:41 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19deFv-0000Jx-Fd for vrrp-archive@odin.ietf.org; Fri, 18 Jul 2003 19:03:16 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6IN3Fiq001232 for vrrp-archive@odin.ietf.org; Fri, 18 Jul 2003 19:03:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19deFv-0000Jn-Ct for vrrp-web-archive@optimus.ietf.org; Fri, 18 Jul 2003 19:03:15 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17338 for ; Fri, 18 Jul 2003 19:03:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19deFs-0004LT-00 for vrrp-web-archive@ietf.org; Fri, 18 Jul 2003 19:03:12 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19deFm-0004LO-00 for vrrp-web-archive@ietf.org; Fri, 18 Jul 2003 19:03:06 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19deFh-0000Ip-Do; Fri, 18 Jul 2003 19:03:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19deEi-0000HE-OZ for vrrp@optimus.ietf.org; Fri, 18 Jul 2003 19:02:01 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17303 for ; Fri, 18 Jul 2003 19:01:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19deEf-0004KX-00 for vrrp@ietf.org; Fri, 18 Jul 2003 19:01:57 -0400 Received: from web10604.mail.yahoo.com ([216.136.130.168]) by ietf-mx with smtp (Exim 4.12) id 19deEU-0004KI-00 for vrrp@ietf.org; Fri, 18 Jul 2003 19:01:46 -0400 Message-ID: <20030718230103.84838.qmail@web10604.mail.yahoo.com> Received: from [63.99.114.4] by web10604.mail.yahoo.com via HTTP; Fri, 18 Jul 2003 16:01:03 PDT Date: Fri, 18 Jul 2003 16:01:03 -0700 (PDT) From: danny mitzel Subject: RE: [VRRP] Query on Associated IP address and Primary IP address To: gunav@future.futsoft.com, vrrp@ietf.org In-Reply-To: <002e01c34d2f$44a3e820$2404060a@future.futsoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: vrrp-admin@ietf.org Errors-To: vrrp-admin@ietf.org X-BeenThere: vrrp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Virtual Router Redundancy Protocol List-Post: List-Help: List-Subscribe: , --- Gunaseelan V wrote: > 1) Does the Back up router disable IP forwarding ? > If Yes , is it totally on the i/f where VRRP > is enabled or only Selectively like not forwarding > the frames which has Virtual MAC Address . typically no need to disable any forwarding. if router is in vrrp backup role then it should not have the VMAC programmed into NIC so it won't see any of the packets destined to the vrrp master. if for some reason an implementation does have the NIC programmed to accept VMAC even while in vrrp backup then it would need to filter out those packets or else it would trigger duplicates. > In the second case can Backup respond to Pings from > hosts to its Primary IP address the 'primary ip address' of a router is always 'owned' by the router when it is up&running so it should definitely respond to pings or any other requests directed to that address. > 2) In case of switch over from Master to Back up, > how Backup will come to know about the IP address > it should take care of (like how Backup will > handle the IP packets not destined to its Primary IP > address, here though it may be an implementation > dependent, am wondering whether the new IP will > ever be registered by VRRP module in its IP ,) the router learns the list of ip address to backup as part of the VR configuration process. when a backup transitions to vrrp master state for a VR then it assumes arp response and data forwarding responsibilities for those 'adopted' address. however it will not respond to any pings or other requests directed to those 'adtoped' address. __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Mon Jul 21 08:49:53 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26072 for ; Mon, 21 Jul 2003 08:49:53 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ea6Y-0003Z4-DK for vrrp-archive@odin.ietf.org; Mon, 21 Jul 2003 08:49:27 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6LCnQhJ013698 for vrrp-archive@odin.ietf.org; Mon, 21 Jul 2003 08:49:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ea6X-0003Yr-TV for vrrp-web-archive@optimus.ietf.org; Mon, 21 Jul 2003 08:49:25 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26063 for ; Mon, 21 Jul 2003 08:49:21 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ea6W-0002ag-00 for vrrp-web-archive@ietf.org; Mon, 21 Jul 2003 08:49:24 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ea6R-0002ab-00 for vrrp-web-archive@ietf.org; Mon, 21 Jul 2003 08:49:19 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ea69-0003WJ-1t; Mon, 21 Jul 2003 08:49:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ea5M-0003T6-Aj for vrrp@optimus.ietf.org; Mon, 21 Jul 2003 08:48:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26058 for ; Mon, 21 Jul 2003 08:48:08 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ea5K-0002aR-00 for vrrp@ietf.org; Mon, 21 Jul 2003 08:48:11 -0400 Received: from [203.197.140.35] (helo=fsnt.future.futsoft.com) by ietf-mx with esmtp (Exim 4.12) id 19ea59-0002aG-00 for vrrp@ietf.org; Mon, 21 Jul 2003 08:47:59 -0400 Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Mon, 21 Jul 2003 18:28:01 +0530 Received: from gunav (gunav.future.futsoft.com [10.6.4.36]) by kailash.future.futsoft.com (8.12.2/8.12.2) with SMTP id h6LCdW0r020276; Mon, 21 Jul 2003 18:09:32 +0530 Reply-To: From: "Gunaseelan V" To: "'danny mitzel'" , Subject: RE: [VRRP] Query on Associated IP address and Primary IP address Date: Mon, 21 Jul 2003 18:17:47 +0530 Message-Id: <000801c34f86$4a567d60$2404060a@future.futsoft.com> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: <20030718230103.84838.qmail@web10604.mail.yahoo.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: vrrp-admin@ietf.org Errors-To: vrrp-admin@ietf.org X-BeenThere: vrrp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Virtual Router Redundancy Protocol List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Thanks for the response and the efforts, it gave a good concept of VRRP. Thanks Best Regards Gunaseelan V -----Original Message----- From: vrrp-admin@ietf.org [mailto:vrrp-admin@ietf.org]On Behalf Of danny mitzel Sent: Saturday, 19 July 2003 4:31 AM To: gunav@future.futsoft.com; vrrp@ietf.org Subject: RE: [VRRP] Query on Associated IP address and Primary IP address --- Gunaseelan V wrote: > 1) Does the Back up router disable IP forwarding ? > If Yes , is it totally on the i/f where VRRP > is enabled or only Selectively like not forwarding > the frames which has Virtual MAC Address . typically no need to disable any forwarding. if router is in vrrp backup role then it should not have the VMAC programmed into NIC so it won't see any of the packets destined to the vrrp master. if for some reason an implementation does have the NIC programmed to accept VMAC even while in vrrp backup then it would need to filter out those packets or else it would trigger duplicates. > In the second case can Backup respond to Pings from > hosts to its Primary IP address the 'primary ip address' of a router is always 'owned' by the router when it is up&running so it should definitely respond to pings or any other requests directed to that address. > 2) In case of switch over from Master to Back up, > how Backup will come to know about the IP address > it should take care of (like how Backup will > handle the IP packets not destined to its Primary IP > address, here though it may be an implementation > dependent, am wondering whether the new IP will > ever be registered by VRRP module in its IP ,) the router learns the list of ip address to backup as part of the VR configuration process. when a backup transitions to vrrp master state for a VR then it assumes arp response and data forwarding responsibilities for those 'adopted' address. however it will not respond to any pings or other requests directed to those 'adtoped' address. __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp *************************************************************************** This message is proprietary to Future Software Limited (FSL) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. FSL accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. *************************************************************************** _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Tue Jul 22 13:34:51 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20428 for ; Tue, 22 Jul 2003 13:34:51 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f11s-0008Lz-7E for vrrp-archive@odin.ietf.org; Tue, 22 Jul 2003 13:34:24 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6MHYO1f032110 for vrrp-archive@odin.ietf.org; Tue, 22 Jul 2003 13:34:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f11s-0008Lp-3o for vrrp-web-archive@optimus.ietf.org; Tue, 22 Jul 2003 13:34:24 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20409 for ; Tue, 22 Jul 2003 13:34:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19f11p-00068u-00 for vrrp-web-archive@ietf.org; Tue, 22 Jul 2003 13:34:22 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19f11k-00068p-00 for vrrp-web-archive@ietf.org; Tue, 22 Jul 2003 13:34:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f11V-0008JJ-NQ; Tue, 22 Jul 2003 13:34:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f10t-0008J2-Q9 for vrrp@optimus.ietf.org; Tue, 22 Jul 2003 13:33:23 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20374 for ; Tue, 22 Jul 2003 13:33:20 -0400 (EDT) From: Mukesh.Gupta@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19f10r-00068Y-00 for vrrp@ietf.org; Tue, 22 Jul 2003 13:33:21 -0400 Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx with esmtp (Exim 4.12) id 19f10g-00068N-00 for vrrp@ietf.org; Tue, 22 Jul 2003 13:33:10 -0400 Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36]) by mgw-x4.nokia.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h6MHWZJ02629 for ; Tue, 22 Jul 2003 20:32:36 +0300 (EET DST) Received: from esebh001.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Tue, 22 Jul 2003 20:32:35 +0300 Received: from daebh002.NOE.Nokia.com ([172.18.242.232]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Tue, 22 Jul 2003 20:32:35 +0300 Received: from daebe009.NOE.Nokia.com ([172.18.242.190]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Tue, 22 Jul 2003 12:32:30 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Tue, 22 Jul 2003 12:32:30 -0500 Message-ID: <8D260779A766FB4A9C1739A476F84FA42ABD1E@daebe009.americas.nokia.com> Thread-Topic: Working Group Last Call for draft-ietf-vrrp-spec-v2-08.txt thread-index: AcNQdzfFbMKvv2PORvqXv1GGLC5tTQ== To: X-OriginalArrivalTime: 22 Jul 2003 17:32:30.0749 (UTC) FILETIME=[3A6454D0:01C35077] Content-Transfer-Encoding: quoted-printable Subject: [VRRP] Working Group Last Call for draft-ietf-vrrp-spec-v2-08.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: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable This is a VRRP working group last call for comments on advancing the = following document as a Draft Standard: Title : Virtual Router Redundancy Protocol Author(s) : R. Hinden, P. Hunt, D. Mitzel, P. Higginson, M. Shand, A. Lindem, S. Knight, D. Weaver, D. Whipple Filename : draft-ietf-vrrp-spec-v2-08.txt Pages : 31 Please send substantive comments to the VRRP mailing list, and minor = editorial comments to the author(s). This last call period will end two = week from today on Tuesday, August 5th, 2003. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-vrrp-spec-v2-08.txt - Mukesh & Radia _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Tue Jul 22 15:25:48 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24366 for ; Tue, 22 Jul 2003 15:25:48 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f2lD-0005Gy-Os for vrrp-archive@odin.ietf.org; Tue, 22 Jul 2003 15:25:21 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6MJPJJQ020268 for vrrp-archive@odin.ietf.org; Tue, 22 Jul 2003 15:25:19 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f2lD-0005Gp-Kb for vrrp-web-archive@optimus.ietf.org; Tue, 22 Jul 2003 15:25:19 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24355 for ; Tue, 22 Jul 2003 15:25:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19f2lC-0006rG-00 for vrrp-web-archive@ietf.org; Tue, 22 Jul 2003 15:25:18 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19f2l6-0006r7-00 for vrrp-web-archive@ietf.org; Tue, 22 Jul 2003 15:25:12 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f2ku-0005EA-Lp; Tue, 22 Jul 2003 15:25:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dENl-00044U-QY for vrrp@optimus.ietf.org; Thu, 17 Jul 2003 15:25:38 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19626 for ; Thu, 17 Jul 2003 15:25:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dENk-0000rD-00 for vrrp@ietf.org; Thu, 17 Jul 2003 15:25:36 -0400 Received: from nat-63-99-114-4.tahoenetworks.com ([63.99.114.4] helo=TNEXVS01.tahoenetworks.com) by ietf-mx with esmtp (Exim 4.12) id 19dENZ-0000qq-00 for vrrp@ietf.org; Thu, 17 Jul 2003 15:25:26 -0400 Received: from tahoenetworks.com ([10.10.3.151]) by TNEXVS01.tahoenetworks.com with Microsoft SMTPSVC(5.0.2195.2966); Thu, 17 Jul 2003 12:23:51 -0700 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: gunav@future.futsoft.com, vrrp@ietf.org cc: mitzel@acm.org From: mitzel@acm.org Subject: Re: [VRRP] Query on Associated IP address and Primary IP address Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Jul 2003 12:23:50 -0700 Message-ID: X-OriginalArrivalTime: 17 Jul 2003 19:23:51.0223 (UTC) FILETIME=[F4330470:01C34C98] 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: , --- Gunaseelan V wrote: > 1) What are the Associated IP addresses? > is it the multiple IP addresses assigned to the same > Physical Interface (means alias or multinetting) or doe > sit belong to diff physical interfaces of a Virtual Router it's all addresses on the interface running vrrp that are backed up using same vrid. typical deployments I've seen this is just a single address, but it becomes a set of addresses when alias/multinetting is deployed. > 2) What is Primary IP address? > Is it one of the associated IP addresses within a > router selected based on > the some algorithm (say first one or least one etc) you're correct that it's one of the associated ip addresses. the selection algorithm is vendor specific (explicitly tagged 'primary' address, first added, lowest numbered, etc.). the protocol specification just mandates whatever address is picked as the primary is also placed in the ip source address of any Advertisement. this ensures proper convergence if the master election tie breaker based on primary ip address comes into play. > 3)I understood the concept of switchover from Master > to Back up on Failure/Master Down timer event etc, but > how the router which is on the other side (say WAN) > knows about route to Hosts governed by VRRP? > > Here the Back up router once becomes the Master will > forward the IP packets, > if so does this router propagates on WAN Side thru > any routing protocol > about the Hosts reachability on the LAN side. > If Yes When it should start propagating (only after > becoming the Master or even during Back Up) the protocol specification makes no recommendations or requirements on the routing infrastructure when a dynamic routing protocol is used to advertise reachability to the vrrp backed up LAN. in the simplest case all of the vrrp routers advertise reachability. this may result in asymmetric forwarding, but that's not too uncommon in the current Internet routing architecture. if a vendor&customers desires to force symmetric forwarding path then they could tie reachability advertisement to vrrp master status, as you describe above, and market that as 'value added'/ differentiating feature of their product. danny _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Tue Jul 22 16:37:39 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26096 for ; Tue, 22 Jul 2003 16:37:39 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f3sm-0008HO-E1 for vrrp-archive@odin.ietf.org; Tue, 22 Jul 2003 16:37:13 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6MKbC1O031820 for vrrp-archive@odin.ietf.org; Tue, 22 Jul 2003 16:37:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f3sm-0008H1-7F for vrrp-web-archive@optimus.ietf.org; Tue, 22 Jul 2003 16:37:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26077 for ; Tue, 22 Jul 2003 16:37:08 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19f3sk-0007Gr-00 for vrrp-web-archive@ietf.org; Tue, 22 Jul 2003 16:37:10 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19f3se-0007Go-00 for vrrp-web-archive@ietf.org; Tue, 22 Jul 2003 16:37:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f3sb-0008C3-Gl; Tue, 22 Jul 2003 16:37:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f3sL-0008Av-VO for vrrp@optimus.ietf.org; Tue, 22 Jul 2003 16:36:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26066 for ; Tue, 22 Jul 2003 16:36:41 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19f3sK-0007GZ-00 for vrrp@ietf.org; Tue, 22 Jul 2003 16:36:44 -0400 Received: from nwkea-mail-1.sun.com ([192.18.42.13]) by ietf-mx with esmtp (Exim 4.12) id 19f3s9-0007GQ-00 for vrrp@ietf.org; Tue, 22 Jul 2003 16:36:33 -0400 Received: from sydney.East.Sun.COM ([129.148.9.16]) by nwkea-mail-1.sun.com (8.12.9/8.12.9) with ESMTP id h6MKZQDZ029819; Tue, 22 Jul 2003 13:35:27 -0700 (PDT) Received: from sr1-ubur-01 (sr1-ubur-01 [129.148.9.80]) by sydney.East.Sun.COM (8.11.7+Sun/8.11.7/ENSMAIL,v2.2) with SMTP id h6MKZQs19346; Tue, 22 Jul 2003 16:35:26 -0400 (EDT) Message-Id: <200307222035.h6MKZQs19346@sydney.East.Sun.COM> Date: Tue, 22 Jul 2003 16:35:26 -0400 (EDT) From: Radia Perlman - Boston Center for Networking Reply-To: Radia Perlman - Boston Center for Networking Subject: Re: [VRRP] Query on Associated IP address and Primary IP address To: gunav@future.futsoft.com, vrrp@ietf.org, mitzel@acm.org Cc: mitzel@acm.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: dM5EWTsvPCWku2wR3WZwSQ== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.5.3_06 SunOS 5.9 sun4u sparc 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: , Multiple IP addresses is something that confuses me in VRRP. Danny says below that "in typical deployments it's just a single address, but it becomes a set of addresses when alias/multinetting is deployed". What functionality does "alias/multinetting" give over having a single IP address for the routers? I could imagine wanting two router IP addresses for path splitting, but then I'd think you'd want two VRIDs, so two different routers would be elected, one for each VRID (and each VRID would be a different IP address). But I can't think of an advantage of having multiple IP addresses for a single VRID. If there isn't any advantage, then perhaps it would be nice in the spec to strongly suggest that only a single IP address be used, and in the VRRP for IPv6 spec perhaps simplify the protocol by only allowing one? Thanks, Radia From: mitzel@acm.org --- Gunaseelan V wrote: > 1) What are the Associated IP addresses? > is it the multiple IP addresses assigned to the same > Physical Interface (means alias or multinetting) or doe > sit belong to diff physical interfaces of a Virtual Router it's all addresses on the interface running vrrp that are backed up using same vrid. typical deployments I've seen this is just a single address, but it becomes a set of addresses when alias/multinetting is deployed. > 2) What is Primary IP address? > Is it one of the associated IP addresses within a > router selected based on > the some algorithm (say first one or least one etc) you're correct that it's one of the associated ip addresses. the selection algorithm is vendor specific (explicitly tagged 'primary' address, first added, lowest numbered, etc.). the protocol specification just mandates whatever address is picked as the primary is also placed in the ip source address of any Advertisement. this ensures proper convergence if the master election tie breaker based on primary ip address comes into play. > 3)I understood the concept of switchover from Master > to Back up on Failure/Master Down timer event etc, but > how the router which is on the other side (say WAN) > knows about route to Hosts governed by VRRP? > > Here the Back up router once becomes the Master will > forward the IP packets, > if so does this router propagates on WAN Side thru > any routing protocol > about the Hosts reachability on the LAN side. > If Yes When it should start propagating (only after > becoming the Master or even during Back Up) the protocol specification makes no recommendations or requirements on the routing infrastructure when a dynamic routing protocol is used to advertise reachability to the vrrp backed up LAN. in the simplest case all of the vrrp routers advertise reachability. this may result in asymmetric forwarding, but that's not too uncommon in the current Internet routing architecture. if a vendor&customers desires to force symmetric forwarding path then they could tie reachability advertisement to vrrp master status, as you describe above, and market that as 'value added'/ differentiating feature of their product. danny _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Tue Jul 22 17:28:34 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27350 for ; Tue, 22 Jul 2003 17:28:33 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f4g4-0001m1-4K for vrrp-archive@odin.ietf.org; Tue, 22 Jul 2003 17:28:08 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6MLS8Zl006811 for vrrp-archive@odin.ietf.org; Tue, 22 Jul 2003 17:28:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f4g3-0001lm-WE for vrrp-web-archive@optimus.ietf.org; Tue, 22 Jul 2003 17:28:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27323 for ; Tue, 22 Jul 2003 17:28:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19f4g1-0007VF-00 for vrrp-web-archive@ietf.org; Tue, 22 Jul 2003 17:28:05 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19f4fv-0007VC-00 for vrrp-web-archive@ietf.org; Tue, 22 Jul 2003 17:27:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f4fx-0001kV-8U; Tue, 22 Jul 2003 17:28:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f4fr-0001kE-Hf for vrrp@optimus.ietf.org; Tue, 22 Jul 2003 17:27:55 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27296 for ; Tue, 22 Jul 2003 17:27:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19f4fp-0007V4-00 for vrrp@ietf.org; Tue, 22 Jul 2003 17:27:53 -0400 Received: from web10602.mail.yahoo.com ([216.136.130.166]) by ietf-mx with smtp (Exim 4.12) id 19f4fe-0007UR-00 for vrrp@ietf.org; Tue, 22 Jul 2003 17:27:42 -0400 Message-ID: <20030722212432.52511.qmail@web10602.mail.yahoo.com> Received: from [63.99.114.4] by web10602.mail.yahoo.com via HTTP; Tue, 22 Jul 2003 14:24:32 PDT Date: Tue, 22 Jul 2003 14:24:32 -0700 (PDT) From: danny mitzel Subject: Re: [VRRP] Query on Associated IP address and Primary IP address To: Radia Perlman - Boston Center for Networking , vrrp@ietf.org Cc: mitzel@acm.org In-Reply-To: <200307222035.h6MKZQs19346@sydney.East.Sun.COM> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: vrrp-admin@ietf.org Errors-To: vrrp-admin@ietf.org X-BeenThere: vrrp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Virtual Router Redundancy Protocol List-Post: List-Help: List-Subscribe: , --- Radia Perlman - Boston Center for Networking wrote: > What functionality does "alias/multinetting" give > over having a single IP address for the routers? I've never conducted any type of network manager survey on why anyone deploys alias/multinetting. maybe their network started as multiple segments each with different ip subnet and over time they collapsed it into one jumbo switched ethernet and didn't want to have to renumber hosts, OR they needed more than 255 hosts on a segment and only had some non-aggregatable/non-contiguous class C address ranges OR as you suggested maybe some type of traffic splitting based on ip subnet, OR ...? the one thing I do know is that products I've worked on seem to have alias/multinetting support in the list of requirements and pretty much every router product does support alias/multinetting. so I'm assuming someone out there is finding that feature of use for some purpose. then within the working group there was some desire expressed to support this alias/multinetting while minimizing number of virtual routers that must be configured and minimizing packet send/ receive and protocol processing overhead. which lead to the current design. danny __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Wed Jul 23 14:44:39 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23327 for ; Wed, 23 Jul 2003 14:44:39 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fOay-0008Pz-Iy for vrrp-archive@odin.ietf.org; Wed, 23 Jul 2003 14:44:12 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6NIiCNt032359 for vrrp-archive@odin.ietf.org; Wed, 23 Jul 2003 14:44:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fOay-0008Pq-EW for vrrp-web-archive@optimus.ietf.org; Wed, 23 Jul 2003 14:44:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23294 for ; Wed, 23 Jul 2003 14:44:08 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fOav-0006ud-00 for vrrp-web-archive@ietf.org; Wed, 23 Jul 2003 14:44:09 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19fOap-0006ua-00 for vrrp-web-archive@ietf.org; Wed, 23 Jul 2003 14:44:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fOam-0008Nx-Nh; Wed, 23 Jul 2003 14:44:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fOaa-0008Na-Od for vrrp@optimus.ietf.org; Wed, 23 Jul 2003 14:43:48 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23287 for ; Wed, 23 Jul 2003 14:43:45 -0400 (EDT) From: Mukesh.Gupta@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fOaX-0006uO-00 for vrrp@ietf.org; Wed, 23 Jul 2003 14:43:46 -0400 Received: from [63.78.179.216] (helo=mgw-dax1.ext.nokia.com) by ietf-mx with esmtp (Exim 4.12) id 19fOaN-0006uB-00 for vrrp@ietf.org; Wed, 23 Jul 2003 14:43:35 -0400 Received: from davir01nok.americas.nokia.com (davir01nok.americas.nokia.com [172.18.242.84]) by mgw-dax1.ext.nokia.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h6NIhF124232 for ; Wed, 23 Jul 2003 13:43:16 -0500 (CDT) Received: from daebh001.NOE.Nokia.com (unverified) by davir01nok.americas.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Wed, 23 Jul 2003 13:43:14 -0500 Received: from daebe009.NOE.Nokia.com ([172.18.242.190]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Wed, 23 Jul 2003 11:42:38 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Wed, 23 Jul 2003 13:42:38 -0500 Message-ID: <8D260779A766FB4A9C1739A476F84FA476C362@daebe009.americas.nokia.com> Thread-Topic: New Goals and Milestones thread-index: AcNRSjA/wlMQjVSHT1KOdCv13yJsbQ== To: X-OriginalArrivalTime: 23 Jul 2003 18:42:38.0655 (UTC) FILETIME=[30E994F0:01C3514A] Content-Transfer-Encoding: quoted-printable Subject: [VRRP] New Goals and Milestones 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: quoted-printable Content-Transfer-Encoding: quoted-printable Hi, I am planning to update the goals and milestones of the WG as the = following. There were no objections raised in the WG meeting in Vienna. = Please send your suggestions/comments to me or Radia by 25th July. =3D=3D=3D=3D=3D New Goals and Milestones: Mar 2003 - Resolve open issues with authentication methods [DONE MAR = 2003] Aug 2003 - Submit updated version of VRRP (IPv4) for Draft Standard Oct 2003 - Submit VRRP for IPv6 (VRRPv3) for Proposed Standard Dec 2003 - Submit MIB for VRRPv3 for Proposed Standard Dec 2003 - Review the WG goals and future potential =3D=3D=3D=3D=3D regards Mukesh _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Fri Jul 25 03:14:45 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26537 for ; Fri, 25 Jul 2003 03:14:44 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fwmP-0005cH-D0 for vrrp-archive@odin.ietf.org; Fri, 25 Jul 2003 03:14:18 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6P7EHct021586 for vrrp-archive@odin.ietf.org; Fri, 25 Jul 2003 03:14:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fwmP-0005c5-25 for vrrp-web-archive@optimus.ietf.org; Fri, 25 Jul 2003 03:14:17 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26522 for ; Fri, 25 Jul 2003 03:14:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fwmM-0005tS-00 for vrrp-web-archive@ietf.org; Fri, 25 Jul 2003 03:14:14 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19fwmH-0005tO-00 for vrrp-web-archive@ietf.org; Fri, 25 Jul 2003 03:14:09 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fwm9-0005bF-14; Fri, 25 Jul 2003 03:14:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fwlv-0005aq-P0 for vrrp@optimus.ietf.org; Fri, 25 Jul 2003 03:13:47 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26514 for ; Fri, 25 Jul 2003 03:13:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fwlt-0005tH-00 for vrrp@ietf.org; Fri, 25 Jul 2003 03:13:45 -0400 Received: from [203.197.140.35] (helo=fsnt.future.futsoft.com) by ietf-mx with esmtp (Exim 4.12) id 19fwli-0005t1-00 for vrrp@ietf.org; Fri, 25 Jul 2003 03:13:34 -0400 Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Fri, 25 Jul 2003 12:52:52 +0530 Received: from gunav (gunav.future.futsoft.com [10.6.4.36]) by kailash.future.futsoft.com (8.12.2/8.12.2) with SMTP id h6P74F0r031698; Fri, 25 Jul 2003 12:34:16 +0530 Reply-To: From: "Gunaseelan V" To: "'Radia Perlman - Boston Center for Networking'" , , Subject: RE: [VRRP] Query on Associated IP address and Primary IP address Date: Fri, 25 Jul 2003 12:42:53 +0530 Message-Id: <001401c3527c$2b225b00$2404060a@future.futsoft.com> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 In-Reply-To: <200307222035.h6MKZQs19346@sydney.East.Sun.COM> Importance: Normal Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: vrrp-admin@ietf.org Errors-To: vrrp-admin@ietf.org X-BeenThere: vrrp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Virtual Router Redundancy Protocol List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Radia and Danny In the same thread I wish to bring up my findings, like I found an implementation where the Associated IP addresses are configured with the values of IP address pertaining to the Back up routers' interface IP addresses. Though the Alias or multinetting are not getting supported in that implementation . Am not sure whether this is what being globally followed, Also I find there is a Specific Configuration for Primary IP address and this is used to determine the Master, is this a config parameter or an learned one. In the former case , the need of IP address info of Back up routers ,I feel for an election process of Master form pool of Backup routers, if Priority happens to be same on all then the tie breaker with IP address should take place. For this to happen the back up routers should know about the Ip address of others, is this need Justified or commonly followed . If you can throw some light on this that would be helpful. Wish to Thank you very much for all your efforts in clarifying my doubts earlier Best Regards Gunaseelan V -----Original Message----- From: vrrp-admin@ietf.org [mailto:vrrp-admin@ietf.org]On Behalf Of Radia Perlman - Boston Center for Networking Sent: Wednesday, 23 July 2003 2:05 AM To: gunav@future.futsoft.com; vrrp@ietf.org; mitzel@acm.org Cc: mitzel@acm.org Subject: Re: [VRRP] Query on Associated IP address and Primary IP address Multiple IP addresses is something that confuses me in VRRP. Danny says below that "in typical deployments it's just a single address, but it becomes a set of addresses when alias/multinetting is deployed". What functionality does "alias/multinetting" give over having a single IP address for the routers? I could imagine wanting two router IP addresses for path splitting, but then I'd think you'd want two VRIDs, so two different routers would be elected, one for each VRID (and each VRID would be a different IP address). But I can't think of an advantage of having multiple IP addresses for a single VRID. If there isn't any advantage, then perhaps it would be nice in the spec to strongly suggest that only a single IP address be used, and in the VRRP for IPv6 spec perhaps simplify the protocol by only allowing one? Thanks, Radia From: mitzel@acm.org --- Gunaseelan V wrote: > 1) What are the Associated IP addresses? > is it the multiple IP addresses assigned to the same > Physical Interface (means alias or multinetting) or doe > sit belong to diff physical interfaces of a Virtual Router it's all addresses on the interface running vrrp that are backed up using same vrid. typical deployments I've seen this is just a single address, but it becomes a set of addresses when alias/multinetting is deployed. > 2) What is Primary IP address? > Is it one of the associated IP addresses within a > router selected based on > the some algorithm (say first one or least one etc) you're correct that it's one of the associated ip addresses. the selection algorithm is vendor specific (explicitly tagged 'primary' address, first added, lowest numbered, etc.). the protocol specification just mandates whatever address is picked as the primary is also placed in the ip source address of any Advertisement. this ensures proper convergence if the master election tie breaker based on primary ip address comes into play. > 3)I understood the concept of switchover from Master > to Back up on Failure/Master Down timer event etc, but > how the router which is on the other side (say WAN) > knows about route to Hosts governed by VRRP? > > Here the Back up router once becomes the Master will > forward the IP packets, > if so does this router propagates on WAN Side thru > any routing protocol > about the Hosts reachability on the LAN side. > If Yes When it should start propagating (only after > becoming the Master or even during Back Up) the protocol specification makes no recommendations or requirements on the routing infrastructure when a dynamic routing protocol is used to advertise reachability to the vrrp backed up LAN. in the simplest case all of the vrrp routers advertise reachability. this may result in asymmetric forwarding, but that's not too uncommon in the current Internet routing architecture. if a vendor&customers desires to force symmetric forwarding path then they could tie reachability advertisement to vrrp master status, as you describe above, and market that as 'value added'/ differentiating feature of their product. danny _______________________________________________ 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 *************************************************************************** This message is proprietary to Future Software Limited (FSL) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. FSL accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. *************************************************************************** _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Mon Jul 28 18:33:44 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23697 for ; Mon, 28 Jul 2003 18:33:43 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hGYQ-0007hM-0T for vrrp-archive@odin.ietf.org; Mon, 28 Jul 2003 18:33:19 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6SMXHjw029590 for vrrp-archive@odin.ietf.org; Mon, 28 Jul 2003 18:33:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hGYP-0007hB-RI for vrrp-web-archive@optimus.ietf.org; Mon, 28 Jul 2003 18:33:17 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23694 for ; Mon, 28 Jul 2003 18:33:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hGYM-0000cc-00 for vrrp-web-archive@ietf.org; Mon, 28 Jul 2003 18:33:14 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19hGYM-0000cY-00 for vrrp-web-archive@ietf.org; Mon, 28 Jul 2003 18:33:14 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hGY8-0007df-HU; Mon, 28 Jul 2003 18:33:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hGXv-0007dT-Mo for vrrp@optimus.ietf.org; Mon, 28 Jul 2003 18:32:49 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23689 for ; Mon, 28 Jul 2003 18:32:41 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hGXs-0000cV-00 for vrrp@ietf.org; Mon, 28 Jul 2003 18:32:44 -0400 Received: from nat-63-99-114-4.tahoenetworks.com ([63.99.114.4] helo=TNEXVS01.tahoenetworks.com) by ietf-mx with esmtp (Exim 4.12) id 19hGXr-0000cS-00 for vrrp@ietf.org; Mon, 28 Jul 2003 18:32:43 -0400 Received: from tahoenetworks.com ([10.10.3.151]) by TNEXVS01.tahoenetworks.com with Microsoft SMTPSVC(5.0.2195.2966); Mon, 28 Jul 2003 15:32:03 -0700 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 X-Exmh-Isig-CompType: comp X-Exmh-Isig-Folder: inbox To: gunav@future.futsoft.com, vrrp@ietf.org cc: mitzel@acm.org From: danny_j_mitzel@yahoo.com Subject: RE: [VRRP] Query on Associated IP address and Primary IP address Mime-Version: 1.0 Content-Type: text/plain Date: Mon, 28 Jul 2003 15:32:03 -0700 Message-ID: X-OriginalArrivalTime: 28 Jul 2003 22:32:03.0879 (UTC) FILETIME=[11B0D370:01C35558] 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: , I had some difficulty understanding your description of findings and questions. if my comments don't cover your questions you might try restating or maybe someone else will chime in... > I found an implementation where the Associated IP > addresses are configured with the values of IP address > pertaining to the Back up routers' interface IP > addresses. Though the Alias or multinetting are not > getting supported in that implementation . Am not sure > whether this is what being globally followed a router backing up ip addresses 'owned' by some other router does need to be configured with the vrrp vrid and the list of addresses to be backed up. as we've discussed before this 'list of associated ip addresses' may typically be a single ip address. > Also I find there is a Specific Configuration for > Primary IP address and this is used to determine the > Master, is this a config parameter or an learned one. I think I mentioned one other time that no specific algorithm for selection of primary ip address is mandated in the protocol specification. this is vendor specific. as you mention it could be explicitly configured by administrator. other options may be first address configured on an interface, lowest numerically, etc. the rfc only mandates that each router selects its primary address and consistently uses that address as ip source address in any vrrp Advertisement sent and also uses it whenever performing master election tie breaker comparison. a general comment on your last question of 'is this a config parameter or an learned one'... if you look at the rfc section 6.1 all of the per-vr configurable parameters (marked as 'configured item') must be explicitly specified. then if you read the section 7.1 vrrp packet processing you'll see there is no auto-learning and any mismatch in configuration is typically treated as an error triggering a notification to alert administrator. > In the former case , the need of IP address info of > Back up routers ,I feel > for an election process of Master form pool of > Backup routers, if Priority > happens to be same on all then the tie breaker with > IP address should take > place. For this to happen the back up routers should > know about the Ip > address of others, is this need Justified or > commonly followed . a router only needs to know is its own primary ip address. when/if another backup at the same priority sends an Advertisement the source ip address will be that other router's primary ip address. that's all that's needed to make the tie breaker comparison. I guess you could sorta call that a form of auto-learning the other backup's primary ip address. danny _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Tue Jul 29 14:24:34 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03748 for ; Tue, 29 Jul 2003 14:24:34 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hZ8r-0006nZ-EB for vrrp-archive@odin.ietf.org; Tue, 29 Jul 2003 14:24:09 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6TIO9Pq026133 for vrrp-archive@odin.ietf.org; Tue, 29 Jul 2003 14:24:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hZ8r-0006nQ-A1 for vrrp-web-archive@optimus.ietf.org; Tue, 29 Jul 2003 14:24:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03714 for ; Tue, 29 Jul 2003 14:24:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hZ8o-0000mC-00 for vrrp-web-archive@ietf.org; Tue, 29 Jul 2003 14:24:06 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19hZ8o-0000m9-00 for vrrp-web-archive@ietf.org; Tue, 29 Jul 2003 14:24:06 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hZ8j-0006mW-C5; Tue, 29 Jul 2003 14:24:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hZ8f-0006mJ-FA for vrrp@optimus.ietf.org; Tue, 29 Jul 2003 14:23:57 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03702; Tue, 29 Jul 2003 14:23:51 -0400 (EDT) From: Radia.Perlman@sun.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hZ8c-0000lu-00; Tue, 29 Jul 2003 14:23:54 -0400 Received: from brmea-mail-2.sun.com ([192.18.98.43]) by ietf-mx with esmtp (Exim 4.12) id 19hZ8b-0000lq-00; Tue, 29 Jul 2003 14:23:53 -0400 Received: from sydney.East.Sun.COM ([129.148.9.16]) by brmea-mail-2.sun.com (8.12.9/8.12.9) with ESMTP id h6TINlIJ011484; Tue, 29 Jul 2003 12:23:47 -0600 (MDT) Received: from esun1as-be21 (esun1as-be21-ge0.Central.Sun.COM [129.147.60.148]) by sydney.East.Sun.COM (8.11.7+Sun/8.11.7/ENSMAIL,v2.2) with ESMTP id h6TINis05504; Tue, 29 Jul 2003 14:23:44 -0400 (EDT) Message-ID: <3607545.1059503023890.JavaMail.radia@sydney.East.Sun.COM> Date: Tue, 29 Jul 2003 12:23:43 -0600 (MDT) To: minutes@ietf.org, vrrp@ietf.org Cc: radia.perlman@sun.com, Mukesh.Gupta@nokia.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailer: Sun(TM) Web Access 1.0 Content-Transfer-Encoding: 7bit Subject: [VRRP] (re)post of minutes of VRRP WG, 7/16/2003, (this time without slides attached) 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 7/16/2003 Milestone review New milestones were proposed. === Mar 2003 - Resolve open issues with authentication methods [DONE MAR 2003] Aug 2003 - Submit updated version of VRRP (IPv4) for Draft Standard Oct 2003 - Submit VRRP for IPv6 (VRRPv3) for Proposed Standard Dec 2003 - Submit MIB for VRRPv3 for Proposed Standard Dec 2003 - Review the WG goals and future potential === VRRPv3 MIB There was a discussion about whether there should just be a single combined MIB for IPv4 and IPv6, or whether there should be two, and if there were two, one should be IPv4-only, but should the other be combined IPv4 and IPv6, or IPv6-only. The current draft is assuming IPv4-only plus IPv6-only. The conclusion was that it might be good to try to do a strawman IPv4+IPv6 and see if that works well. One argument for why there couldn't be a single MIB was that VRRPv2 is stable while VRRPv3 is still evolving, and there ought to be a stable MIB to go along with the stable protocol. Another is that VRRPv2 and VRRPv3 might be sufficiently different protocols that it would be confusing to try to combine them. VRRPv2 spec update Bob Hinden presented the changes to VRRPv2, which were mostly editorial other than removing the authentication methods, and adding to the security considerations section an explanation for having done so. An issue was raised about having too many listed authors, and some obsolete addresses for them. The conclusion was that Bob Hinden should be listed as "editor", and a "contributors" section should be added acknowledging the others. There was an issue that had been raised on the mailing list about possible pathological behavior when multiple backup routers had equal priorities, and on the mailing list a suggestion had been made for adding a tie-breaker based on IP address. After discussion during the meeting, it was concluded that the particular section of code involving backup router ties would not be invoked, because a router, once it sends a VRRP message, has already decided it is master, and the master portion has the IP-address tie-breaker. So the conclusion was that the election logic was fine as is. The sense of the room was that VRRPv2 is ready for wg last call. Sub-second Timers Karen O'Donoghue gave a presentation explaining the need for faster convergence (less than one second) than could be done using timers in units of seconds. The sense of the room was that they were convinced of the need, at least for IPv6. It would be difficult to do it for IPv4 because it would be an incompatible change, and it would be undesirable to delay the specification. Various encoding techniques were described, the most straightforward being making the size of the timer field longer and the units smaller (perhaps 100 ms), and other suggestions involving exponential encoding so as to fit into the same sized field. The conclusion was to pursue this on the mailing list for v6, and if it is desired for IPv4, to have a new draft for a new version of VRRP for IPv4 (perhaps version number 4). A quick check was made to ensure that VRRPv2 does indeed say that a VRRPv2 router should drop VRRP messages with unknown version numbers, which is required in order to safely roll out a new version of VRRP. VRRPv3 As with v2, removed authentication types and added explanation in security considerations section. An issue from the mailing list was discussed, which is that using VMACs causes layer 2 addresses to change locations, which is somewhat dangerous in a bridged LAN. For IPv4, VMACs are necessary because there are implementations of hosts (e.g., Win 95) that do not update their ARP caches when they receive gratuitous ARP messages. But the question was raised as to whether VMACs, and perhaps even VRRP, could be avoided for IPv6. The conclusion about whether VRRP for IPv6 could be avoided was that it could not. VRRP for IPv6 could not be avoided because the neighbor discovery mechanism in IPv6 would not be able to react to changes as quickly as a mechanism such as VRRP, confined to a community of a few routers. And even if IPv6 neighbor discovery could in theory be modified to be as responsive as VRRP, the VRRP WG could not impose changes to a different WG. The second issue was whether VMACs could be avoided for IPv6, i.e., have VRRPv3 still elect one router to represent the IP address, but not move MAC addresses. The elected router would use its own MAC address. The reasoning was that in IPv6, nodes are required to update their ARP caches if they see a gratuitous ARP, so as long as the newly elected router did a gratuitous ARP, the ARP caches would all get updated, and this approach would avoid having a MAC address move within the topology. Some objected to this because the endnodes would then be aware that the router had switched, but others liked this proposal specifically because the endnode would know that something had happened. There was also concern that if the gratuitous ARP got lost, it might take a long time for ARP caches to get fixed to the MAC adress of the new router. Another argument was that doing things very differently for VRRPv3 than VRRPv2 is out of the charter of the WG. So the conclusion is that we will assume for now that VRRPv3 will continue to use VMACs, but that the issue can be discussed on the mailing list, and if there is a lot of interest and a concrete proposal, we can revive this issue. _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp