From exim@www1.ietf.org Sun Feb 1 10:14:38 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24602 for ; Sun, 1 Feb 2004 10:14:38 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AnJIZ-00040I-2M for vrrp-archive@odin.ietf.org; Sun, 01 Feb 2004 10:14:11 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i11FEBRe015384 for vrrp-archive@odin.ietf.org; Sun, 1 Feb 2004 10:14:11 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AnJIY-000403-Tx for vrrp-web-archive@optimus.ietf.org; Sun, 01 Feb 2004 10:14:10 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24266 for ; Sun, 1 Feb 2004 10:14:07 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AnJIW-0004zz-00 for vrrp-web-archive@ietf.org; Sun, 01 Feb 2004 10:14:08 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AnInT-0004gw-00 for vrrp-web-archive@ietf.org; Sun, 01 Feb 2004 09:42:05 -0500 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1AnIPV-0006n3-00 for vrrp-web-archive@ietf.org; Sun, 01 Feb 2004 09:17:17 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1AnIBw-0003uJ-08 for vrrp-web-archive@ietf.org; Sun, 01 Feb 2004 09:03:16 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AnIBt-0003kw-58 for vrrp-web-archive@ietf.org; Sun, 01 Feb 2004 09:03:13 -0500 Date: Sun, 01 Feb 2004 09:03:13 -0500 Message-ID: <20040201140313.1364.77024.Mailman@www1.ietf.org> Subject: ietf.org mailing list memberships reminder From: mailman-owner@www1.ietf.org To: vrrp-web-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: mailman-admin@ietf.org Errors-To: mailman-admin@ietf.org X-BeenThere: mailman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no version=2.60 This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, vrrp-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. *************************************************************************** Note Well All statements related to the activities of the IETF and addressed to the IETF are subject to all provisions of Section 10 of RFC 2026, which grants to the IETF and its participants certain licenses and rights in such statements. Such statements include verbal statements in IETF meetings, as well as written and electronic communications made at any time or place, which are addressed to * the IETF plenary session, * any IETF working group or portion thereof, * the IESG, or any member thereof on behalf of the IESG, * the IAB or any member thereof on behalf of the IAB, * any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, * the RFC Editor or the Internet-Drafts function Statements made outside of an IETF meeting, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not subject to these provisions. *************************************************************************** If you have questions, problems, comments, etc, send them to mailman-owner@www1.ietf.org. Thanks! Passwords for vrrp-web-archive@ietf.org: List Password // URL ---- -------- vrrp@ietf.org mPhD https://www1.ietf.org/mailman/options/vrrp/vrrp-web-archive%40ietf.org From exim@www1.ietf.org Mon Feb 2 14:10:23 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03281 for ; Mon, 2 Feb 2004 14:10:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AnjSC-0006NT-BE for vrrp-archive@odin.ietf.org; Mon, 02 Feb 2004 14:09:55 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i12J9qY8024509 for vrrp-archive@odin.ietf.org; Mon, 2 Feb 2004 14:09:52 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AnjSC-0006NE-6I for vrrp-web-archive@optimus.ietf.org; Mon, 02 Feb 2004 14:09:52 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03262 for ; Mon, 2 Feb 2004 14:09:48 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AnjS9-000653-00 for vrrp-web-archive@ietf.org; Mon, 02 Feb 2004 14:09:49 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AnjRD-0005zm-00 for vrrp-web-archive@ietf.org; Mon, 02 Feb 2004 14:08:51 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AnjQa-0005u8-00 for vrrp-web-archive@ietf.org; Mon, 02 Feb 2004 14:08:12 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AnjQQ-00064q-7G; Mon, 02 Feb 2004 14:08:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AnjQC-00062X-Js for vrrp@optimus.ietf.org; Mon, 02 Feb 2004 14:07:48 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03175 for ; Mon, 2 Feb 2004 14:07:45 -0500 (EST) From: Mukesh.Gupta@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AnjQA-0005tA-00 for vrrp@ietf.org; Mon, 02 Feb 2004 14:07:46 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AnjPL-0005on-00 for vrrp@ietf.org; Mon, 02 Feb 2004 14:06:56 -0500 Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx with esmtp (Exim 4.12) id 1AnjP0-0005jI-00 for vrrp@ietf.org; Mon, 02 Feb 2004 14:06:35 -0500 Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36]) by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i12J6W223118 for ; Mon, 2 Feb 2004 21:06:32 +0200 (EET) Received: from daebh002.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Mon, 2 Feb 2004 21:06:31 +0200 Received: from daebe009.NOE.Nokia.com ([10.241.35.109]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Mon, 2 Feb 2004 13:05:31 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 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, 2 Feb 2004 13:05:31 -0600 Message-ID: <8D260779A766FB4A9C1739A476F84FA4015471C7@daebe009.americas.nokia.com> Thread-Topic: No WG meeting in Seoul Thread-Index: AcPpv4bA5zp2EPzXSaSCF/cz2BZaTQ== To: Cc: , X-OriginalArrivalTime: 02 Feb 2004 19:05:31.0617 (UTC) FILETIME=[87667510:01C3E9BF] Content-Transfer-Encoding: quoted-printable Subject: [VRRP] No WG meeting in Seoul 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable As we have not received anything for the agenda, VRRP WG will not be meeting in Seoul (IETF 59th). _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Thu Feb 5 08:57:33 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15312 for ; Thu, 5 Feb 2004 08:57:33 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aok08-00049K-6f for vrrp-archive@odin.ietf.org; Thu, 05 Feb 2004 08:57:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i15Dv4L8015944 for vrrp-archive@odin.ietf.org; Thu, 5 Feb 2004 08:57:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aok07-000495-U9 for vrrp-web-archive@optimus.ietf.org; Thu, 05 Feb 2004 08:57:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15293 for ; Thu, 5 Feb 2004 08:57:01 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aok06-00014C-00 for vrrp-web-archive@ietf.org; Thu, 05 Feb 2004 08:57:02 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AojzB-0000yE-00 for vrrp-web-archive@ietf.org; Thu, 05 Feb 2004 08:56:05 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AojyO-0000so-00 for vrrp-web-archive@ietf.org; Thu, 05 Feb 2004 08:55:16 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AojyG-00041j-D8; Thu, 05 Feb 2004 08:55:08 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aoh53-0001uP-7c for vrrp@optimus.ietf.org; Thu, 05 Feb 2004 05:49:57 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10697 for ; Thu, 5 Feb 2004 05:49:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aoh4z-0007VN-00 for vrrp@ietf.org; Thu, 05 Feb 2004 05:49:53 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aoh45-0007Q9-00 for vrrp@ietf.org; Thu, 05 Feb 2004 05:48:58 -0500 Received: from web40610.mail.yahoo.com ([66.218.78.147]) by ietf-mx with smtp (Exim 4.12) id 1Aoh3M-0007Fd-00 for vrrp@ietf.org; Thu, 05 Feb 2004 05:48:12 -0500 Message-ID: <20040205104743.23745.qmail@web40610.mail.yahoo.com> Received: from [203.200.20.226] by web40610.mail.yahoo.com via HTTP; Thu, 05 Feb 2004 02:47:43 PST Date: Thu, 5 Feb 2004 02:47:43 -0800 (PST) From: Nabendu To: vrrp@ietf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-911443253-1075978063=:21728" Subject: [VRRP] VRRP Questions 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=HTML_MESSAGE autolearn=no version=2.60 --0-911443253-1075978063=:21728 Content-Type: text/plain; charset=us-ascii HI all, Plz help me to understand the following concerns... 1) " Master MUST NOT accept packets addressed to the IP address(es) associated with the virtual router if it is not the IP address owner."" --> as far as my understanding by sailing through the list is that this is done so that alarms will start ringing as ping will not work out ... and the desirable "data packet from a host will not be disrupted"......... Now my question is Will the IP packets from a host not be dropped if Master does not accept packets addressed to the IP address(es) associated with the virtual router ( if it is not the IP address owner ). 2) 7.2 Receiving VRRP packets states that "If the packet was not generated by the address owner (Priority does not equal 255 (decimal)), the receiver MUST drop the packet, otherwise continue processing." --Why receiver MUST drop the packet...??? And if it is dropped, how advertisement will be received by other backup routers ??? --------------------------------- Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online --0-911443253-1075978063=:21728 Content-Type: text/html; charset=us-ascii
HI all,
 
Plz help me to understand the following concerns...
 
1) " Master MUST NOT accept packets addressed to the IP address(es) associated
      with the virtual router if it is not the IP address owner."" --> as far as my understanding by sailing through the list is that this is done so that alarms will start ringing as ping will not work out ... and the desirable "data packet from a host will not be disrupted".........
Now my question is
                       Will the IP packets from a host not be dropped if Master does not accept packets addressed to the IP address(es) associated with the virtual router ( if it is not the IP address owner ).
 
 
2) 7.2 Receiving VRRP packets states that "If the packet was not generated by the address owner (Priority does not equal 255 (decimal)), the receiver MUST drop the packet, otherwise continue processing."
 
--Why receiver MUST drop the packet...??? And if it is dropped, how advertisement will be received by other backup routers ???

Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online --0-911443253-1075978063=:21728-- _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Thu Feb 5 17:40:47 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16952 for ; Thu, 5 Feb 2004 17:40:47 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AosAW-0001A7-Jd for vrrp-archive@odin.ietf.org; Thu, 05 Feb 2004 17:40:20 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i15MeKNa004461 for vrrp-archive@odin.ietf.org; Thu, 5 Feb 2004 17:40:20 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AosAW-00019s-ED for vrrp-web-archive@optimus.ietf.org; Thu, 05 Feb 2004 17:40:20 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16946 for ; Thu, 5 Feb 2004 17:40:17 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AosAT-00032s-00 for vrrp-web-archive@ietf.org; Thu, 05 Feb 2004 17:40:17 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aos9f-000313-00 for vrrp-web-archive@ietf.org; Thu, 05 Feb 2004 17:39:28 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1Aos9I-0002zQ-00 for vrrp-web-archive@ietf.org; Thu, 05 Feb 2004 17:39:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aos9F-00011R-2d; Thu, 05 Feb 2004 17:39:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aos8U-0000xp-FZ for vrrp@optimus.ietf.org; Thu, 05 Feb 2004 17:38:14 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16928 for ; Thu, 5 Feb 2004 17:38:11 -0500 (EST) From: Mukesh.Gupta@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aos8R-0002yP-00 for vrrp@ietf.org; Thu, 05 Feb 2004 17:38:12 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aos7V-0002xT-00 for vrrp@ietf.org; Thu, 05 Feb 2004 17:37:13 -0500 Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx with esmtp (Exim 4.12) id 1Aos70-0002wZ-00 for vrrp@ietf.org; Thu, 05 Feb 2004 17:36:42 -0500 Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36]) by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i15Mafv16049 for ; Fri, 6 Feb 2004 00:36:41 +0200 (EET) Received: from daebh001.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Fri, 6 Feb 2004 00:36:41 +0200 Received: from daebe009.NOE.Nokia.com ([10.241.35.109]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Thu, 5 Feb 2004 14:36:41 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Thu, 5 Feb 2004 16:36:40 -0600 Message-ID: <8D260779A766FB4A9C1739A476F84FA4015471F7@daebe009.americas.nokia.com> Thread-Topic: draft-ietf-vrrp-spec-v2: ready for rfc-ed Thread-Index: AcPsN8GOqc1PKs6XRz+TcBArjd5vvwAAHkIQ To: X-OriginalArrivalTime: 05 Feb 2004 22:36:41.0530 (UTC) FILETIME=[867F01A0:01C3EC38] Content-Transfer-Encoding: quoted-printable Subject: [VRRP] FW: draft-ietf-vrrp-spec-v2: ready for rfc-ed 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Folks, The VRRPv2 draft has finally been approved by the IESG. This is a major milestone for VRRP WG. Thanks and=20 congratulations to everyone who has directly or=20 indirectly contributed to the draft. Regards Mukesh -----Original Message----- From: ext Alex Zinin [mailto:zinin@psg.com] Sent: Thursday, February 05, 2004 2:30 PM To: iesg-secretary@ietf.org Cc: Gupta Mukesh (Nokia-NET/MtView); Radia.Perlman@Sun.COM; Bill Fenner; Hinden Bob (Nokia-ES/MtView) Subject: draft-ietf-vrrp-spec-v2: ready for rfc-ed Secretariat- Version -10 of draft-ietf-vrrp-spec-v2 addresses the IESG comments and is ready to go to the RFC Editor. --=20 Alex http://www.psg.com/~zinin/ _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Fri Feb 6 10:59:14 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02268 for ; Fri, 6 Feb 2004 10:59:14 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ap8NU-0005BE-Gl for vrrp-archive@odin.ietf.org; Fri, 06 Feb 2004 10:58:48 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i16Fwm8W019908 for vrrp-archive@odin.ietf.org; Fri, 6 Feb 2004 10:58:48 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ap8NU-0005B1-7d for vrrp-web-archive@optimus.ietf.org; Fri, 06 Feb 2004 10:58:48 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02260 for ; Fri, 6 Feb 2004 10:58:43 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ap8NR-0006Xz-00 for vrrp-web-archive@ietf.org; Fri, 06 Feb 2004 10:58:45 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ap8MX-0006Vk-00 for vrrp-web-archive@ietf.org; Fri, 06 Feb 2004 10:57:50 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1Ap8Lt-0006TA-00 for vrrp-web-archive@ietf.org; Fri, 06 Feb 2004 10:57:09 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ap8Ll-00057J-65; Fri, 06 Feb 2004 10:57:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AoqMp-0006Ys-7d for vrrp@optimus.ietf.org; Thu, 05 Feb 2004 15:44:55 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05446; Thu, 5 Feb 2004 15:44:53 -0500 (EST) Message-Id: <200402052044.PAA05446@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: Thu, 05 Feb 2004 15:44:52 -0500 Subject: [VRRP] I-D ACTION:draft-ietf-vrrp-spec-v2-10.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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60 --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 Filename : draft-ietf-vrrp-spec-v2-10.txt Pages : 29 Date : 2004-2-5 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-10.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-10.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-10.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: <2004-2-5155402.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-vrrp-spec-v2-10.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-vrrp-spec-v2-10.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-2-5155402.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Fri Feb 6 15:17:26 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13922 for ; Fri, 6 Feb 2004 15:17:26 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApCPK-0002UA-4t for vrrp-archive@odin.ietf.org; Fri, 06 Feb 2004 15:16:58 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i16KGws0009549 for vrrp-archive@odin.ietf.org; Fri, 6 Feb 2004 15:16:58 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApCPK-0002Tw-01 for vrrp-web-archive@optimus.ietf.org; Fri, 06 Feb 2004 15:16:58 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13855 for ; Fri, 6 Feb 2004 15:16:55 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ApCPI-00010L-00 for vrrp-web-archive@ietf.org; Fri, 06 Feb 2004 15:16:56 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ApCOQ-0000wn-00 for vrrp-web-archive@ietf.org; Fri, 06 Feb 2004 15:16:03 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1ApCNT-0000sl-00 for vrrp-web-archive@ietf.org; Fri, 06 Feb 2004 15:15:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApCNS-0001zk-Gc; Fri, 06 Feb 2004 15:15:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApCNL-0001xY-JL for vrrp@optimus.ietf.org; Fri, 06 Feb 2004 15:14:55 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13604 for ; Fri, 6 Feb 2004 15:14:53 -0500 (EST) From: Kalyan.Tata@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ApCNK-0000rI-00 for vrrp@ietf.org; Fri, 06 Feb 2004 15:14:54 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ApCMQ-0000nk-00 for vrrp@ietf.org; Fri, 06 Feb 2004 15:13:59 -0500 Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx with esmtp (Exim 4.12) id 1ApCLV-0000kO-00 for vrrp@ietf.org; Fri, 06 Feb 2004 15:13:01 -0500 Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35]) by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i16KD0v00877 for ; Fri, 6 Feb 2004 22:13:00 +0200 (EET) Received: from daebh002.NOE.Nokia.com (unverified) by esvir03nok.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Fri, 6 Feb 2004 22:12:59 +0200 Received: from mvebe001.NOE.Nokia.com ([172.18.140.37]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Fri, 6 Feb 2004 14:12:57 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3ECED.9B1F24CB" Date: Fri, 6 Feb 2004 12:12:55 -0800 Message-ID: <4D7B558499107545BB45044C63822DDE03ADD4FB@mvebe001.americas.nokia.com> Thread-Topic: [VRRP] VRRP Questions Thread-Index: AcPr77vF3IZ4nQONTC+V528pDUN5rwAZUHIA To: Cc: , X-OriginalArrivalTime: 06 Feb 2004 20:12:57.0393 (UTC) FILETIME=[9C85E210:01C3ECED] Subject: [VRRP] VRRP MIB Question 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.6 required=5.0 tests=HTML_50_60,HTML_FONTCOLOR_BLUE, HTML_MESSAGE,NO_REAL_NAME autolearn=no version=2.60 This is a multi-part message in MIME format. ------_=_NextPart_001_01C3ECED.9B1F24CB Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, From a previous email thread, we found out that VRID is not unique = across VRRP versions in a multi=20 stack (Systems participating in both VRRPv2 and VRRPv3) environment. Thus ifIndex+VRID cannot be used as index to uniquely identify a VRRP = instance in the VRRP=20 MIB tables. =20 We are planning to introduce IP version into the index which will make = an entry in VRRP tables=20 uniquely identifiable. Another approach would be introduce VRRP version. = =20 We would like to know any views/comments on this. =20 Bert/Dave, I noted down your suggestion during the IETF meeting to = change the order of=20 indexing from ifIndex-VRID to VRID-ifIndex.=20 =20 With the introduction of IPversion, I would like to know your views on = the following order IPversion-VRID-ifIndex=20 or VRID- ------_=_NextPart_001_01C3ECED.9B1F24CB Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
    From a previous email = thread, we=20 found out that VRID is not unique across VRRP versions in a multi=20
stack=20 (Systems participating in both VRRPv2 and VRRPv3)=20 environment.
Thus=20 ifIndex+VRID cannot be used as index to uniquely identify a VRRP = instance in the=20 VRRP
 MIB tables.
 
We are=20 planning to introduce IP version into the index which will make an entry = in VRRP=20 tables
uniquely identifiable. Another approach would = be=20 introduce VRRP version.
 
We=20 would like to know any views/comments on this.
 
Bert/Dave, I noted down your suggestion = during the IETF=20 meeting to change the order of
indexing from ifIndex-VRID to VRID-ifIndex.=20
 
With=20 the introduction of IPversion, I would like to know your views on the = following=20 order
IPversion-VRID-ifIndex
or
VRID-
------_=_NextPart_001_01C3ECED.9B1F24CB-- _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Fri Feb 6 16:38:29 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21035 for ; Fri, 6 Feb 2004 16:38:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApDfl-0001Wd-TL for vrrp-archive@odin.ietf.org; Fri, 06 Feb 2004 16:38:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i16Lc1hB005849 for vrrp-archive@odin.ietf.org; Fri, 6 Feb 2004 16:38:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApDfl-0001W8-CT for vrrp-web-archive@optimus.ietf.org; Fri, 06 Feb 2004 16:38:01 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20978 for ; Fri, 6 Feb 2004 16:37:57 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ApDfj-0001To-00 for vrrp-web-archive@ietf.org; Fri, 06 Feb 2004 16:37:59 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ApDdt-00016v-00 for vrrp-web-archive@ietf.org; Fri, 06 Feb 2004 16:36:08 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1ApDci-0000qd-00 for vrrp-web-archive@ietf.org; Fri, 06 Feb 2004 16:34:52 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApDV6-0000Cq-Ha; Fri, 06 Feb 2004 16:27:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApDUI-0000AW-MQ for vrrp@optimus.ietf.org; Fri, 06 Feb 2004 16:26:11 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18749 for ; Fri, 6 Feb 2004 16:26:07 -0500 (EST) From: Kalyan.Tata@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ApDUG-0006mC-00 for vrrp@ietf.org; Fri, 06 Feb 2004 16:26:08 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ApDRr-0006Ei-00 for vrrp@ietf.org; Fri, 06 Feb 2004 16:23:43 -0500 Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 1ApDPG-0005h2-00 for vrrp@ietf.org; Fri, 06 Feb 2004 16:20:59 -0500 Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33]) by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i16LKuq27251 for ; Fri, 6 Feb 2004 23:20:56 +0200 (EET) Received: from daebh001.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Fri, 6 Feb 2004 23:20:53 +0200 Received: from mvebe001.NOE.Nokia.com ([172.18.140.37]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Fri, 6 Feb 2004 13:20:50 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3ECF7.1758A78B" Date: Fri, 6 Feb 2004 13:20:48 -0800 Message-ID: <4D7B558499107545BB45044C63822DDE03873C96@mvebe001.americas.nokia.com> Thread-Topic: VRRP MIB Question Thread-Index: AcPr77vF3IZ4nQONTC+V528pDUN5rwAZUHIAACe9RaAAAFJscA== To: , Cc: X-OriginalArrivalTime: 06 Feb 2004 21:20:50.0019 (UTC) FILETIME=[17FF4B30:01C3ECF7] Subject: [VRRP] RE: VRRP MIB Question 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,HTML_60_70, HTML_FONTCOLOR_BLUE,HTML_MESSAGE,NO_REAL_NAME autolearn=no version=2.60 This is a multi-part message in MIME format. ------_=_NextPart_001_01C3ECF7.1758A78B Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thanks Dave for the quick response. =20 It would be great if any one with experience managing VRRP routers can = share their thoughts on this. =20 Thanks kalyan =20 =20 -----Original Message----- From: ext Dave Thaler [mailto:dthaler@windows.microsoft.com] Sent: 06 February, 2004 13:04 To: Tata Kalyan (Nokia-ES/MtView); vrrp@ietf.org Cc: bwijnen@lucent.com Subject: RE: VRRP MIB Question The order should typically take into account a few things: 1) Is one order significantly easier to implement in a device then = another order?=20 2) What order would humans most typically want to see the rows = appear in? (grouped first by IPversion? Or VRID? Or interface?) 3) Do you expect common management operations to be partial = enumerations based on a particular attribute? ("show me all the IPv4 = entries" or "show me all the entries for interface X") If so, the most = important one should be first (otherwise the management station must = enumerating everything and then filtering itself) -Dave From: Kalyan.Tata@nokia.com [ mailto:Kalyan.Tata@nokia.com] Sent: Friday, February 06, 2004 12:13 PM To: vrrp@ietf.org Cc: Dave Thaler; bwijnen@lucent.com Subject: VRRP MIB Question Hi, From a previous email thread, we found out that VRID is not unique = across VRRP versions in a multi=20 stack (Systems participating in both VRRPv2 and VRRPv3) environment. Thus ifIndex+VRID cannot be used as index to uniquely identify a VRRP = instance in the VRRP=20 MIB tables. =20 We are planning to introduce IP version into the index which will make = an entry in VRRP tables=20 uniquely identifiable. Another approach would be introduce VRRP version. = =20 We would like to know any views/comments on this. =20 Bert/Dave, I noted down your suggestion during the IETF meeting to = change the order of=20 indexing from ifIndex-VRID to VRID-ifIndex.=20 =20 With the introduction of IPversion, I would like to know your views on = the following order IPversion-VRID-ifIndex=20 or VRID- ------_=_NextPart_001_01C3ECF7.1758A78B Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: VRRP MIB Question
Thanks=20 Dave for the quick response.
 
It=20 would be great if any one with experience managing VRRP routers can = share their=20 thoughts on this.
 
Thanks
kalyan
 
 
-----Original Message-----
From: ext Dave Thaler=20 [mailto:dthaler@windows.microsoft.com]
Sent: 06 February, 2004 = 13:04
To: Tata Kalyan (Nokia-ES/MtView); = vrrp@ietf.org
Cc:=20 bwijnen@lucent.com
Subject: RE: VRRP MIB = Question

The order=20 should typically take into account a = few=20 things:

1)      Is=20 one order=20 significantly easier to implement in a device then=20 another order?
2)      What=20 order would humans most typically want=20 to see the rows appear in?  = (grouped first by=20 IPversion? Or VRID? Or interface?)

3)      Do you expect common management operations to be partial = enumerations=20 based on a particular attribute? (“show me=20 all the IPv4 entries” = or “show me all the entries for interface = X”)  If so, the most important one should be = first (otherwise the management station must = enumerating=20 everything and then filtering itself)

-Dave


From: Kalyan.Tata@nokia.com [mailto:Kalyan.Tata@nokia.com]Sent: Friday, February 06, 2004 12:13 = PM
To: vrrp@ietf.org
Cc: Dave Thaler; = bwijnen@lucent.com
Subject: VRRP MIB Question

Hi,

    From a previous email thread, we found out = that VRID=20 is not unique across VRRP versions in a multi=20

stack=20 (Systems participating in both VRRPv2 and VRRPv3)=20 environment.

Thus=20 ifIndex+VRID cannot be used as index to uniquely identify a VRRP = instance in the=20 VRRP

 MIB=20 tables.

 

We are=20 planning to introduce IP version into the index which will make an entry = in VRRP=20 tables

uniquely=20 identifiable. Another approach would be introduce VRRP=20 version.

 

We would=20 like to know any views/comments on this.

 

Bert/Dave,=20 I noted down your suggestion during the IETF meeting to change the order = of

indexing=20 from ifIndex-VRID to VRID-ifIndex. =

 

With the=20 introduction of IPversion, I would like to know your views on the = following=20 order

IPversion-VRID-ifIndex =

or

VRID-

------_=_NextPart_001_01C3ECF7.1758A78B-- _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Fri Feb 6 17:37:31 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26580 for ; Fri, 6 Feb 2004 17:37:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApEau-0005wO-A5 for vrrp-archive@odin.ietf.org; Fri, 06 Feb 2004 17:37:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i16Mb4x1022830 for vrrp-archive@odin.ietf.org; Fri, 6 Feb 2004 17:37:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApEat-0005w9-Pn for vrrp-web-archive@optimus.ietf.org; Fri, 06 Feb 2004 17:37:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26562 for ; Fri, 6 Feb 2004 17:36:59 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ApEar-0000f4-00 for vrrp-web-archive@ietf.org; Fri, 06 Feb 2004 17:37:01 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ApEZs-0000a5-00 for vrrp-web-archive@ietf.org; Fri, 06 Feb 2004 17:36:02 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1ApEYy-0000XK-00 for vrrp-web-archive@ietf.org; Fri, 06 Feb 2004 17:35:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApEYw-0005jR-3v; Fri, 06 Feb 2004 17:35:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApEY4-0005eX-34 for vrrp@optimus.ietf.org; Fri, 06 Feb 2004 17:34:08 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26497 for ; Fri, 6 Feb 2004 17:34:03 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ApEY1-0000UU-00 for vrrp@ietf.org; Fri, 06 Feb 2004 17:34:05 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ApEXK-0000RT-00 for vrrp@ietf.org; Fri, 06 Feb 2004 17:33:23 -0500 Received: from hoemail1.lucent.com ([192.11.226.161] helo=hoemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1ApEWi-0000ND-00 for vrrp@ietf.org; Fri, 06 Feb 2004 17:32:44 -0500 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by hoemail1.firewall.lucent.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i16MWAo02158 for ; Fri, 6 Feb 2004 16:32:11 -0600 (CST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id ; Fri, 6 Feb 2004 23:32:09 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155028EC554@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "'Dave Thaler'" , Kalyan.Tata@nokia.com, vrrp@ietf.org Cc: "Wijnen, Bert (Bert)" Date: Fri, 6 Feb 2004 23:32:08 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3ED00.EB4A9A86" Subject: [VRRP] RE: VRRP MIB Question 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,HTML_50_60, HTML_FONTCOLOR_BLUE,HTML_MESSAGE autolearn=no version=2.60 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C3ED00.EB4A9A86 Content-Type: text/plain W.r.t. 2) below, pls do also take potential applications into account. And... if you need a different indexing because there are many sorts of applications, then you can do an other table that has the indexes mapped in another order. Thanks, Bert -----Original Message----- From: Dave Thaler [mailto:dthaler@windows.microsoft.com] Sent: vrijdag 6 februari 2004 22:04 To: Kalyan.Tata@nokia.com; vrrp@ietf.org Cc: bwijnen@lucent.com Subject: RE: VRRP MIB Question The order should typically take into account a few things: 1) Is one order significantly easier to implement in a device then another order? 2) What order would humans most typically want to see the rows appear in? (grouped first by IPversion? Or VRID? Or interface?) 3) Do you expect common management operations to be partial enumerations based on a particular attribute? ("show me all the IPv4 entries" or "show me all the entries for interface X") If so, the most important one should be first (otherwise the management station must enumerating everything and then filtering itself) -Dave From: Kalyan.Tata@nokia.com [ mailto:Kalyan.Tata@nokia.com ] Sent: Friday, February 06, 2004 12:13 PM To: vrrp@ietf.org Cc: Dave Thaler; bwijnen@lucent.com Subject: VRRP MIB Question Hi, From a previous email thread, we found out that VRID is not unique across VRRP versions in a multi stack (Systems participating in both VRRPv2 and VRRPv3) environment. Thus ifIndex+VRID cannot be used as index to uniquely identify a VRRP instance in the VRRP MIB tables. We are planning to introduce IP version into the index which will make an entry in VRRP tables uniquely identifiable. Another approach would be introduce VRRP version. We would like to know any views/comments on this. Bert/Dave, I noted down your suggestion during the IETF meeting to change the order of indexing from ifIndex-VRID to VRID-ifIndex. With the introduction of IPversion, I would like to know your views on the following order IPversion-VRID-ifIndex or VRID- ------_=_NextPart_001_01C3ED00.EB4A9A86 Content-Type: text/html RE: VRRP MIB Question
W.r.t. 2) below, pls do also take potential applications into account.
 
And... if you need a different indexing because there are many sorts of applications,
then you can do an other table that has the indexes mapped in another order.
 

Thanks,
Bert

-----Original Message-----
From: Dave Thaler [mailto:dthaler@windows.microsoft.com]
Sent: vrijdag 6 februari 2004 22:04
To: Kalyan.Tata@nokia.com; vrrp@ietf.org
Cc: bwijnen@lucent.com
Subject: RE: VRRP MIB Question

The order should typically take into account a few things:

1)      Is one order significantly easier to implement in a device then another order?
2)      What order would humans most typically want to see the rows appear in?  (grouped first by IPversion? Or VRID? Or interface?)

3)      Do you expect common management operations to be partial enumerations based on a particular attribute? (“show me all the IPv4 entries” or “show me all the entries for interface X”)  If so, the most important one should be first (otherwise the management station must enumerating everything and then filtering itself)

-Dave


From: Kalyan.Tata@nokia.com [mailto:Kalyan.Tata@nokia.com]
Sent: Friday, February 06, 2004 12:13 PM
To: vrrp@ietf.org
Cc: Dave Thaler; bwijnen@lucent.com
Subject: VRRP MIB Question

Hi,

    From a previous email thread, we found out that VRID is not unique across VRRP versions in a multi

stack (Systems participating in both VRRPv2 and VRRPv3) environment.

Thus ifIndex+VRID cannot be used as index to uniquely identify a VRRP instance in the VRRP

 MIB tables.

 

We are planning to introduce IP version into the index which will make an entry in VRRP tables

uniquely identifiable. Another approach would be introduce VRRP version.

 

We would like to know any views/comments on this.

 

Bert/Dave, I noted down your suggestion during the IETF meeting to change the order of

indexing from ifIndex-VRID to VRID-ifIndex.

 

With the introduction of IPversion, I would like to know your views on the following order

IPversion-VRID-ifIndex

or

VRID-

------_=_NextPart_001_01C3ED00.EB4A9A86-- _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Thu Feb 12 15:01:04 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10120 for ; Thu, 12 Feb 2004 15:01:04 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArN0n-0001xj-4g for vrrp-archive@odin.ietf.org; Thu, 12 Feb 2004 15:00:37 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1CK0bhi007536 for vrrp-archive@odin.ietf.org; Thu, 12 Feb 2004 15:00:37 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArN0m-0001xL-Sx for vrrp-web-archive@optimus.ietf.org; Thu, 12 Feb 2004 15:00:36 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10108 for ; Thu, 12 Feb 2004 15:00:33 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ArN0i-0004jc-00 for vrrp-web-archive@ietf.org; Thu, 12 Feb 2004 15:00:32 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ArMzk-0004dc-00 for vrrp-web-archive@ietf.org; Thu, 12 Feb 2004 14:59:33 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1ArMzJ-0004Xd-00 for vrrp-web-archive@ietf.org; Thu, 12 Feb 2004 14:59:05 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArMzE-0000Mw-U0; Thu, 12 Feb 2004 14:59:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArIpc-0001uB-0p for vrrp@optimus.ietf.org; Thu, 12 Feb 2004 10:32:48 -0500 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28370 for ; Thu, 12 Feb 2004 10:32:43 -0500 (EST) Received: from nobody by optimus.ietf.org with local (Exim 4.20) id 1ArIp7-0001rX-JY; Thu, 12 Feb 2004 10:32:17 -0500 X-test-idtracker: no From: The IESG To: IETF-Announce:; Cc: Internet Architecture Board , RFC Editor , Message-Id: Date: Thu, 12 Feb 2004 10:32:17 -0500 Subject: [VRRP] Protocol Action: 'Virtual Router Redundancy Protocol' to Draft Standard 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 The IESG has approved the following document: - 'Virtual Router Redundancy Protocol ' as a Draft Standard This document is the product of the Virtual Router Redundancy Protocol Working Group. The IESG contact persons are Alex Zinin and Bill Fenner. Technical Summary 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. Working Group Summary There was a consensus within the WG on this document Protocol Quality The specification has been reviewed for the IESG by Alex Zinin and Bill Fenner. The protocol has been widely implemented and deployed. _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Thu Feb 12 17:52:57 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21012 for ; Thu, 12 Feb 2004 17:52:57 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArPh8-0007M2-C3 for vrrp-archive@odin.ietf.org; Thu, 12 Feb 2004 17:52:30 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1CMqU1q028266 for vrrp-archive@odin.ietf.org; Thu, 12 Feb 2004 17:52:30 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArPh8-0007Lp-2B for vrrp-web-archive@optimus.ietf.org; Thu, 12 Feb 2004 17:52:30 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21006 for ; Thu, 12 Feb 2004 17:52:26 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ArPh3-00077P-00 for vrrp-web-archive@ietf.org; Thu, 12 Feb 2004 17:52:25 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ArPgB-00073J-00 for vrrp-web-archive@ietf.org; Thu, 12 Feb 2004 17:51:31 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1ArPfg-0006yg-00 for vrrp-web-archive@ietf.org; Thu, 12 Feb 2004 17:51:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArPfi-0007Fn-6J; Thu, 12 Feb 2004 17:51:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArPfE-0007Ea-AJ for vrrp@optimus.ietf.org; Thu, 12 Feb 2004 17:50:32 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20955 for ; Thu, 12 Feb 2004 17:50:29 -0500 (EST) From: John.Cruz@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ArPf9-0006wv-00 for vrrp@ietf.org; Thu, 12 Feb 2004 17:50:27 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ArPeK-0006rX-00 for vrrp@ietf.org; Thu, 12 Feb 2004 17:49:36 -0500 Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 1ArPdc-0006ld-00 for vrrp@ietf.org; Thu, 12 Feb 2004 17:48:52 -0500 Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33]) by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1CMms328326 for ; Fri, 13 Feb 2004 00:48:54 +0200 (EET) Received: from daebh002.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Fri, 13 Feb 2004 00:48:54 +0200 Received: from mvebe001.NOE.Nokia.com ([172.18.140.37]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Thu, 12 Feb 2004 16:48:32 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Thu, 12 Feb 2004 14:48:30 -0800 Message-ID: Thread-Topic: VRRP for IPv6 - addresses Thread-Index: AcPxulZCTEeMDomVR3icRAbricJcTQ== To: X-OriginalArrivalTime: 12 Feb 2004 22:48:33.0120 (UTC) FILETIME=[57874600:01C3F1BA] Content-Transfer-Encoding: quoted-printable Subject: [VRRP] VRRP for IPv6 - addresses 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Hi, In the current draft for VRRP for IPv6 = (draft-ietf-vrrp-ipv6-spec-05.txt), the virtual IP address is always a link local address. This is okay for a box performing only as a router. However, for applications running on a box, this may not be sufficient. For applications like VPN that would like to failover the VPN endpoint, the virtual IP address must be a globally reachable address. The current draft does not support it. Also, an interface may belong to multiple subnets and we may want more than one address belonging to that interface to be backed up by another router. This implies that we may need support in = the VRRP packet to carry multiple virtual IP addresses. Any comments? John _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Fri Feb 13 14:33:45 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27834 for ; Fri, 13 Feb 2004 14:33:45 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Arj3u-0001q0-8O for vrrp-archive@odin.ietf.org; Fri, 13 Feb 2004 14:33:18 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1DJXIvP007060 for vrrp-archive@odin.ietf.org; Fri, 13 Feb 2004 14:33:18 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Arj3u-0001pn-3w for vrrp-web-archive@optimus.ietf.org; Fri, 13 Feb 2004 14:33:18 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27826 for ; Fri, 13 Feb 2004 14:33:14 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Arj3r-0001nR-00 for vrrp-web-archive@ietf.org; Fri, 13 Feb 2004 14:33:15 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Arj31-0001j9-00 for vrrp-web-archive@ietf.org; Fri, 13 Feb 2004 14:32:24 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1Arj2f-0001dW-00 for vrrp-web-archive@ietf.org; Fri, 13 Feb 2004 14:32:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Arj2f-0001jz-2D; Fri, 13 Feb 2004 14:32:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Arj1p-0001im-2A for vrrp@optimus.ietf.org; Fri, 13 Feb 2004 14:31:09 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27658 for ; Fri, 13 Feb 2004 14:31:05 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Arj1m-0001aV-00 for vrrp@ietf.org; Fri, 13 Feb 2004 14:31:06 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Arj0o-0001W3-00 for vrrp@ietf.org; Fri, 13 Feb 2004 14:30:07 -0500 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1Arizq-0001Oh-00 for vrrp@ietf.org; Fri, 13 Feb 2004 14:29:06 -0500 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i1DJSXk04047; Fri, 13 Feb 2004 11:28:33 -0800 X-mProtect: <200402131928> Nokia Silicon Valley Messaging Protection Received: from walnut2.iprg.nokia.com (205.226.9.199, claiming to be "spruce.nokia.com") by darkstar.iprg.nokia.com smtpdlsOgpz; Fri, 13 Feb 2004 11:28:31 PST Message-Id: <4.3.2.7.2.20040213110619.03a5e760@mailhost.iprg.nokia.com> X-Sender: hinden@mailhost.iprg.nokia.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 13 Feb 2004 11:25:07 -0800 To: John.Cruz@nokia.com From: Bob Hinden Subject: Re: [VRRP] VRRP for IPv6 - addresses Cc: vrrp@ietf.org In-Reply-To: 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 John, >In the current draft for VRRP for IPv6 (draft-ietf-vrrp-ipv6-spec-05.txt), >the virtual IP address is always a link local address. This is okay >for a box performing only as a router. However, for applications >running on a box, this may not be sufficient. For applications like >VPN that would like to failover the VPN endpoint, the virtual IP >address must be a globally reachable address. The current draft does This seems like a reasonable change to me. It was a feature that was in VRRP (for IPv4). I didn't include it in VRRP for IPv6 because all host to router traffic used the routers link-local addresses. You point out that when using things like VPN it also useful to visualize the routers other addresses. The changes to the draft are fairly easy and I should be able to include them in the draft I am planning to submit later today. >not support it. Also, an interface may belong to multiple subnets >and we may want more than one address belonging to that interface to be >backed up by another router. This implies that we may need support in the >VRRP packet to carry multiple virtual IP addresses. This isn't quite right. In IPv6 the routers tell the hosts (via router advertisements) what prefixes are on the link and that they are the router. So while there may be multiple prefixes (i.e., subnets) on the link, hosts don't send their off-link traffic to the routers address on the prefix, they only send their off-link traffic to the routers link-local address. The result is that one router may back up another router independent of the number of subnets on the link. Nonetheless, I think that the change you suggest for supporting VPNs is a good idea and will plan to make the change in the draft. It won't require more than the link-local address to be carried, so it shouldn't impose any overhead, other than having to set a count field in the header to 1, on people who don't want to use this feature. Bob Bob _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Fri Feb 13 14:55:53 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29059 for ; Fri, 13 Feb 2004 14:55:53 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArjPK-0004uZ-8Z for vrrp-archive@odin.ietf.org; Fri, 13 Feb 2004 14:55:26 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1DJtQOZ018879 for vrrp-archive@odin.ietf.org; Fri, 13 Feb 2004 14:55:26 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArjPK-0004uQ-5i for vrrp-web-archive@optimus.ietf.org; Fri, 13 Feb 2004 14:55:26 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29029 for ; Fri, 13 Feb 2004 14:55:22 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ArjPH-0003rJ-00 for vrrp-web-archive@ietf.org; Fri, 13 Feb 2004 14:55:23 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ArjOQ-0003m2-00 for vrrp-web-archive@ietf.org; Fri, 13 Feb 2004 14:54:30 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1ArjNw-0003gB-00 for vrrp-web-archive@ietf.org; Fri, 13 Feb 2004 14:54:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArjNw-0004nh-VP; Fri, 13 Feb 2004 14:54:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArjN7-0004NI-Sd for vrrp@optimus.ietf.org; Fri, 13 Feb 2004 14:53:09 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28876 for ; Fri, 13 Feb 2004 14:53:06 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ArjN5-0003cL-00 for vrrp@ietf.org; Fri, 13 Feb 2004 14:53:07 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ArjM6-0003WL-00 for vrrp@ietf.org; Fri, 13 Feb 2004 14:52:07 -0500 Received: from brmea-mail-3.sun.com ([192.18.98.34]) by ietf-mx with esmtp (Exim 4.12) id 1ArjL9-0003RN-00 for vrrp@ietf.org; Fri, 13 Feb 2004 14:51:07 -0500 Received: from phys-bur1-1 ([129.148.13.15]) by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id i1DJp7i5013308 for ; Fri, 13 Feb 2004 12:51:07 -0700 (MST) Received: from bur-mail2.east.sun.com (bur-mail2 [129.148.13.31]) by bur-mail2.east.sun.com (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003)) with ESMTP id <0HT100JKPGH77U@bur-mail2.east.sun.com> for vrrp@ietf.org; Fri, 13 Feb 2004 14:51:07 -0500 (EST) Received: from [129.147.60.148] by bur-mail2.east.sun.com (mshttpd); Fri, 13 Feb 2004 14:51:07 -0500 Date: Fri, 13 Feb 2004 14:51:07 -0500 From: Radia Perlman Subject: Re: [VRRP] VRRP for IPv6 - addresses To: Bob Hinden Cc: John.Cruz@nokia.com, vrrp@ietf.org Message-id: <10071d880.d88010071@bur-mail2.east.sun.com> MIME-version: 1.0 X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.16 (built May 14 2003) Content-type: text/plain; charset=us-ascii Content-language: en Content-transfer-encoding: 7bit Content-disposition: inline X-Accept-Language: en Priority: normal 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Would it be reasonable for each router to have two layer 3 addresses, one is a real, "permanent" (i.e., not affected by VRRP) address used for talking to it when you really want to talk to *that* box, and the other being the virtual one being "the VRRP router"? Radia ----- Original Message ----- From: Bob Hinden Date: Friday, February 13, 2004 2:25 pm Subject: Re: [VRRP] VRRP for IPv6 - addresses > John, > > >In the current draft for VRRP for IPv6 (draft-ietf-vrrp-ipv6-spec- > 05.txt),>the virtual IP address is always a link local address. > This is okay > >for a box performing only as a router. However, for applications > >running on a box, this may not be sufficient. For applications like > >VPN that would like to failover the VPN endpoint, the virtual IP > >address must be a globally reachable address. The current draft does > > This seems like a reasonable change to me. It was a feature that > was in > VRRP (for IPv4). I didn't include it in VRRP for IPv6 because all > host to > router traffic used the routers link-local addresses. You point > out that > when using things like VPN it also useful to visualize the routers > other > addresses. > > The changes to the draft are fairly easy and I should be able to > include > them in the draft I am planning to submit later today. > > >not support it. Also, an interface may belong to multiple subnets > >and we may want more than one address belonging to that interface > to be > >backed up by another router. This implies that we may need > support in the > >VRRP packet to carry multiple virtual IP addresses. > > This isn't quite right. In IPv6 the routers tell the hosts (via > router > advertisements) what prefixes are on the link and that they are > the > router. So while there may be multiple prefixes (i.e., subnets) > on the > link, hosts don't send their off-link traffic to the routers > address on the > prefix, they only send their off-link traffic to the routers link- > local > address. The result is that one router may back up another router > independent of the number of subnets on the link. > > Nonetheless, I think that the change you suggest for supporting > VPNs is a > good idea and will plan to make the change in the draft. It won't > require > more than the link-local address to be carried, so it shouldn't > impose any > overhead, other than having to set a count field in the header to > 1, on > people who don't want to use this feature. > > Bob > > > Bob > > > _______________________________________________ > vrrp mailing list > vrrp@ietf.org > https://www1.ietf.org/mailman/listinfo/vrrp > _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Fri Feb 13 18:14:57 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14226 for ; Fri, 13 Feb 2004 18:14:57 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArmVw-0003a0-BZ for vrrp-archive@odin.ietf.org; Fri, 13 Feb 2004 18:14:31 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1DNESNQ013754 for vrrp-archive@odin.ietf.org; Fri, 13 Feb 2004 18:14:28 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArmVw-0003Ze-6J for vrrp-web-archive@optimus.ietf.org; Fri, 13 Feb 2004 18:14:28 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14176 for ; Fri, 13 Feb 2004 18:14:23 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ArmVt-00000b-00 for vrrp-web-archive@ietf.org; Fri, 13 Feb 2004 18:14:25 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ArmV8-0007js-00 for vrrp-web-archive@ietf.org; Fri, 13 Feb 2004 18:13:39 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1ArmUa-0007dh-00 for vrrp-web-archive@ietf.org; Fri, 13 Feb 2004 18:13:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArmUX-0002wr-NS; Fri, 13 Feb 2004 18:13:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArmTu-0002hs-QI for vrrp@optimus.ietf.org; Fri, 13 Feb 2004 18:12:22 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13779 for ; Fri, 13 Feb 2004 18:12:18 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ArmTr-0007Yi-00 for vrrp@ietf.org; Fri, 13 Feb 2004 18:12:19 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ArmSs-0007QW-00 for vrrp@ietf.org; Fri, 13 Feb 2004 18:11:18 -0500 Received: from usen-221x249x121x227.ap-us01.usen.ad.jp ([221.249.121.227] helo=coconut.itojun.org) by ietf-mx with esmtp (Exim 4.12) id 1ArmRu-0007GM-00 for vrrp@ietf.org; Fri, 13 Feb 2004 18:10:18 -0500 Received: by coconut.itojun.org (Postfix, from userid 1001) id A7558FC; Sat, 14 Feb 2004 08:10:10 +0900 (JST) To: bob.hinden@nokia.com Cc: John.Cruz@nokia.com, vrrp@ietf.org Subject: Re: [VRRP] VRRP for IPv6 - addresses In-Reply-To: Your message of "Fri, 13 Feb 2004 11:25:07 -0800" <4.3.2.7.2.20040213110619.03a5e760@mailhost.iprg.nokia.com> References: <4.3.2.7.2.20040213110619.03a5e760@mailhost.iprg.nokia.com> X-Mailer: Cue version 0.6 (040210-0635/itojun) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Message-Id: <20040213231010.A7558FC@coconut.itojun.org> Date: Sat, 14 Feb 2004 08:10:10 +0900 (JST) From: itojun@itojun.org (Jun-ichiro itojun Hagino) 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 > >In the current draft for VRRP for IPv6 (draft-ietf-vrrp-ipv6-spec-05.txt), > >the virtual IP address is always a link local address. This is okay > >for a box performing only as a router. However, for applications > >running on a box, this may not be sufficient. For applications like > >VPN that would like to failover the VPN endpoint, the virtual IP > >address must be a globally reachable address. The current draft does > > This seems like a reasonable change to me. It was a feature that was in > VRRP (for IPv4). I didn't include it in VRRP for IPv6 because all host to > router traffic used the routers link-local addresses. You point out that > when using things like VPN it also useful to visualize the routers other > addresses. vrrp = virtual "ROUTER" redundancy protocol. you at least need a new name... itojun _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Mon Feb 16 19:18:28 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15313 for ; Mon, 16 Feb 2004 19:18:28 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Assw5-0002PL-Lq for vrrp-archive@odin.ietf.org; Mon, 16 Feb 2004 19:18:01 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1H0I1Lw009251 for vrrp-archive@odin.ietf.org; Mon, 16 Feb 2004 19:18:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Assw5-0002P8-GX for vrrp-web-archive@optimus.ietf.org; Mon, 16 Feb 2004 19:18:01 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15290 for ; Mon, 16 Feb 2004 19:17:58 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Assw4-0000k1-00 for vrrp-web-archive@ietf.org; Mon, 16 Feb 2004 19:18:00 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Assv4-0000dQ-00 for vrrp-web-archive@ietf.org; Mon, 16 Feb 2004 19:16:58 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AssuG-0000Xo-00 for vrrp-web-archive@ietf.org; Mon, 16 Feb 2004 19:16:08 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AssuA-0002FX-07; Mon, 16 Feb 2004 19:16:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AspYx-0002zu-80 for vrrp@optimus.ietf.org; Mon, 16 Feb 2004 15:41:55 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20287; Mon, 16 Feb 2004 15:41:52 -0500 (EST) Message-Id: <200402162041.PAA20287@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: Mon, 16 Feb 2004 15:41:52 -0500 Subject: [VRRP] I-D ACTION:draft-ietf-vrrp-ipv6-spec-06.txt Sender: vrrp-admin@ietf.org Errors-To: vrrp-admin@ietf.org X-BeenThere: vrrp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Virtual Router Redundancy Protocol List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60 --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-06.txt Pages : 30 Date : 2004-2-16 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-06.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-06.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-06.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: <2004-2-16123429.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-vrrp-ipv6-spec-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-vrrp-ipv6-spec-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-2-16123429.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp