From exim@www1.ietf.org Wed Oct 1 12:36:35 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 MAA22566 for ; Wed, 1 Oct 2003 12:36:35 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4jxV-0004PV-3n for vrrp-archive@odin.ietf.org; Wed, 01 Oct 2003 12:36:13 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h91GaD2t016947 for vrrp-archive@odin.ietf.org; Wed, 1 Oct 2003 12:36:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4jxU-0004PG-Uu for vrrp-web-archive@optimus.ietf.org; Wed, 01 Oct 2003 12:36: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 MAA22548 for ; Wed, 1 Oct 2003 12:36:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A4jxT-0001tF-00 for vrrp-web-archive@ietf.org; Wed, 01 Oct 2003 12:36:11 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A4jxS-0001tC-00 for vrrp-web-archive@ietf.org; Wed, 01 Oct 2003 12:36:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4jxJ-0004OP-LV; Wed, 01 Oct 2003 12:36:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4jwj-0004Np-40 for vrrp@optimus.ietf.org; Wed, 01 Oct 2003 12:35: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 MAA22518 for ; Wed, 1 Oct 2003 12:35:17 -0400 (EDT) From: Mukesh.Gupta@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A4jwh-0001sd-00 for vrrp@ietf.org; Wed, 01 Oct 2003 12:35:23 -0400 Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx with esmtp (Exim 4.12) id 1A4jwg-0001sZ-00 for vrrp@ietf.org; Wed, 01 Oct 2003 12:35:23 -0400 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.6) with ESMTP id h91GZHt15665 for ; Wed, 1 Oct 2003 19:35:18 +0300 (EET DST) Received: from daebh001.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Wed, 1 Oct 2003 19:35:17 +0300 Received: from daebe009.NOE.Nokia.com ([172.18.242.190]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Wed, 1 Oct 2003 09:35:15 -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, 1 Oct 2003 11:35:15 -0500 Message-ID: <8D260779A766FB4A9C1739A476F84FA476C5F8@daebe009.americas.nokia.com> Thread-Topic: [iesg-secretary #14033] VRRPv2 Implementation Report. Thread-Index: AcOIJwHkwqgVHJyxSfGBqCW62J1thQAEvQCg To: X-OriginalArrivalTime: 01 Oct 2003 16:35:16.0006 (UTC) FILETIME=[FE746460:01C38839] Content-Transfer-Encoding: quoted-printable Subject: [VRRP] FW: [iesg-secretary #14033] VRRPv2 Implementation Report. 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 Amy Katherine [mailto:amyk@foretec.com] Sent: Wednesday, October 01, 2003 7:19 AM To: Gupta Mukesh (IPRG/MtView) Subject: Re: [iesg-secretary #14033] VRRPv2 Implementation Report. Your request #14033 was updated by amyk: Dear Mukesh, The implementation report you sent for RFC 2338 has been posted to the IETF page for Protocol Implementation Reports (http://www.ietf.org/IESG/implementation.html). Thank you, The IETF Secretariat _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Sat Oct 11 17:49: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 RAA13912 for ; Sat, 11 Oct 2003 17:49:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8Rbq-00073W-Dl for vrrp-archive@odin.ietf.org; Sat, 11 Oct 2003 17:49:10 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9BLnAwV027116 for vrrp-archive@odin.ietf.org; Sat, 11 Oct 2003 17:49:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8Rbq-00073H-8U for vrrp-web-archive@optimus.ietf.org; Sat, 11 Oct 2003 17:49: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 RAA13891 for ; Sat, 11 Oct 2003 17:48:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A8Rbn-0000GV-00 for vrrp-web-archive@ietf.org; Sat, 11 Oct 2003 17:49:07 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A8Rbn-0000GR-00 for vrrp-web-archive@ietf.org; Sat, 11 Oct 2003 17:49:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8Rbg-00072j-TF; Sat, 11 Oct 2003 17:49:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A82Mv-00022o-AJ for vrrp@optimus.ietf.org; Fri, 10 Oct 2003 14:52:05 -0400 Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12143 for ; Fri, 10 Oct 2003 14:51:56 -0400 (EDT) Received: from apache by asgard.ietf.org with local (Exim 4.14) id 1A82M4-0002Tf-Qz; Fri, 10 Oct 2003 14:51:12 -0400 X-test-idtracker: no To: IETF-Announce :; Cc: vrrp@ietf.org From: The IESG Reply-to: iesg@ietf.org Message-Id: Date: Fri, 10 Oct 2003 14:51:12 -0400 Subject: [VRRP] Last Call: '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: , The IESG has received a request from the Virtual Router Redundancy Protocol WG to consider the following document: - 'Virtual Router Redundancy Protocol ' as a Draft Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2003-10-24. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-vrrp-spec-v2-09.txt _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Wed Oct 15 12:50: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 MAA08825 for ; Wed, 15 Oct 2003 12:50: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 1A9oqg-0003sz-85 for vrrp-archive@odin.ietf.org; Wed, 15 Oct 2003 12:50:11 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9FGoA9B014931 for vrrp-archive@odin.ietf.org; Wed, 15 Oct 2003 12:50:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9oqg-0003sk-4R for vrrp-web-archive@optimus.ietf.org; Wed, 15 Oct 2003 12:50: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 MAA08799 for ; Wed, 15 Oct 2003 12:49:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A9oqd-0007K8-00 for vrrp-web-archive@ietf.org; Wed, 15 Oct 2003 12:50:07 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A9oqd-0007K5-00 for vrrp-web-archive@ietf.org; Wed, 15 Oct 2003 12:50:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9oqY-0003s4-44; Wed, 15 Oct 2003 12:50:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9ahL-0002em-Qj for vrrp@optimus.ietf.org; Tue, 14 Oct 2003 21:43: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 VAA13038; Tue, 14 Oct 2003 21:43:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A9ahH-0004oU-00; Tue, 14 Oct 2003 21:43:31 -0400 Received: from coconut.itojun.org ([219.101.47.130]) by ietf-mx with esmtp (Exim 4.12) id 1A9ahG-0004oR-00; Tue, 14 Oct 2003 21:43:31 -0400 Received: from itojun.org (localhost [127.0.0.1]) by coconut.itojun.org (Postfix) with ESMTP id 308B890; Wed, 15 Oct 2003 10:43:22 +0900 (JST) To: hinden@iprg.nokia.com Cc: Radia Perlman , Mukesh Gupta Cc: vrrp@ietf.org Cc: ietf@ietf.org X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 From: itojun@iijlab.net Date: Wed, 15 Oct 2003 10:43:18 +0900 Message-Id: <20031015014322.308B890@coconut.itojun.org> Subject: [VRRP] draft-ietf-vrrp-ipv6-spec-05.txt lacks IPR clause 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: , draft-ietf-vrrp-ipv6-spec-05.txt does not have IPR clause on it, even though cisco claims to have patent related to it. http://www.ietf.org/ietf/IPR/cisco-ipr-draft-ietf-vrrp-ipv6-spec.txt itojun _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Wed Oct 15 12:56:23 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 MAA09101 for ; Wed, 15 Oct 2003 12:56:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9owM-0004F0-BY for vrrp-archive@odin.ietf.org; Wed, 15 Oct 2003 12:56:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9FGu2J1016296 for vrrp-archive@odin.ietf.org; Wed, 15 Oct 2003 12:56:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9owM-0004El-6Z for vrrp-web-archive@optimus.ietf.org; Wed, 15 Oct 2003 12:56: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 MAA09085 for ; Wed, 15 Oct 2003 12:55:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A9owK-0007PU-00 for vrrp-web-archive@ietf.org; Wed, 15 Oct 2003 12:56:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A9owJ-0007PR-00 for vrrp-web-archive@ietf.org; Wed, 15 Oct 2003 12:55:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9owK-0004Cs-Dr; Wed, 15 Oct 2003 12:56:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9owH-0004Ca-BP for vrrp@optimus.ietf.org; Wed, 15 Oct 2003 12:55: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 MAA09075; Wed, 15 Oct 2003 12:55:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A9owF-0007PB-00; Wed, 15 Oct 2003 12:55:55 -0400 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1A9owE-0007OT-00; Wed, 15 Oct 2003 12:55:54 -0400 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h9FGtHk23013; Wed, 15 Oct 2003 09:55:17 -0700 X-mProtect: <200310151655> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.9.199, claiming to be "spruce.iprg.nokia.com") by darkstar.iprg.nokia.com smtpdSWFExf; Wed, 15 Oct 2003 09:55:16 PDT Message-Id: <4.3.2.7.2.20031015094435.02488eb8@mailhost.iprg.nokia.com> X-Sender: hinden@mailhost.iprg.nokia.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 15 Oct 2003 09:52:18 -0700 To: itojun@iijlab.net From: Bob Hinden Cc: hinden@iprg.nokia.com, Radia Perlman , Mukesh Gupta , vrrp@ietf.org, ietf@ietf.org In-Reply-To: <20031015014322.308B890@coconut.itojun.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [VRRP] Re: draft-ietf-vrrp-ipv6-spec-05.txt lacks IPR clause 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: , Itojun, At 06:43 PM 10/14/2003, itojun@iijlab.net wrote: > draft-ietf-vrrp-ipv6-spec-05.txt does not have IPR clause on it, > even though cisco claims to have patent related to it. > http://www.ietf.org/ietf/IPR/cisco-ipr-draft-ietf-vrrp-ipv6-spec.txt I wasn't aware of this claim on VRRP for IPv6 when the current draft was submitted. I will add an IPR clause in the next version. Thanks, Bob _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Fri Oct 17 19:44: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 TAA00014 for ; Fri, 17 Oct 2003 19:44:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAeGN-0001EN-GW for vrrp-archive@odin.ietf.org; Fri, 17 Oct 2003 19:44:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9HNi7SP004728 for vrrp-archive@odin.ietf.org; Fri, 17 Oct 2003 19:44:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAeGN-0001EB-9Y for vrrp-web-archive@optimus.ietf.org; Fri, 17 Oct 2003 19:44: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 TAA29990 for ; Fri, 17 Oct 2003 19:43:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAeGL-00034D-00 for vrrp-web-archive@ietf.org; Fri, 17 Oct 2003 19:44:05 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AAeGK-000349-00 for vrrp-web-archive@ietf.org; Fri, 17 Oct 2003 19:44:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAeGH-0001DL-Kx; Fri, 17 Oct 2003 19:44:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAeFs-0001Cx-EW for vrrp@optimus.ietf.org; Fri, 17 Oct 2003 19:43: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 TAA29966 for ; Fri, 17 Oct 2003 19:43:27 -0400 (EDT) From: Kalyan.Tata@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAeFq-00032x-00 for vrrp@ietf.org; Fri, 17 Oct 2003 19:43:34 -0400 Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 1AAeFp-00032u-00 for vrrp@ietf.org; Fri, 17 Oct 2003 19:43:34 -0400 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 h9HNhXd27114 for ; Sat, 18 Oct 2003 02:43:33 +0300 (EET DST) Received: from daebh001.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Sat, 18 Oct 2003 02:43:33 +0300 Received: from mvebe001.NOE.Nokia.com ([172.18.140.37]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Fri, 17 Oct 2003 16:43:30 -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: Fri, 17 Oct 2003 16:43:30 -0700 Message-ID: <4D7B558499107545BB45044C63822DDE03873BB5@mvebe001.americas.nokia.com> Thread-Topic: [VRRP] Routing table in VRRP Thread-Index: AcOFYcSwKXrm7ZliSXm6xe3LJ6pkVwPpP1wA To: X-OriginalArrivalTime: 17 Oct 2003 23:43:31.0068 (UTC) FILETIME=[7883B3C0:01C39508] Content-Transfer-Encoding: quoted-printable Subject: [VRRP] Referring VRRP by version 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, We are submitting a draft for managed objects (MIB)=20 that can be used by both VRRPv2 and VRRPv3 protocols. We are using the word "VRRPv2" and "VRRP for IPv4" interchangeably in the draft. Similarly both "VRRPv3" and "VRRP for IPv6" are=20 being used in the draft. I want to know what is the correct way to identify these protocols? =09 I feel that referring as "VRRP for IPv4" and "VRRP for IPv6" would=20 be more explanatory and the MIB can be used in unlikely case of=20 more than one VRRP versions for IPv4 and IPv6. On the other hand the=20 MIB may have to be revised any way in the above scenario. VRRPv2 and VRRPv3 may be the best way to refer too. Please let me know your thoughts on this. thanks kalyan _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Sat Oct 18 11:20: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 LAA00979 for ; Sat, 18 Oct 2003 11:20: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 1AAssG-0004Lv-7z for vrrp-archive@odin.ietf.org; Sat, 18 Oct 2003 11:20:12 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9IFKCIm016729 for vrrp-archive@odin.ietf.org; Sat, 18 Oct 2003 11:20:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAssF-0004Lh-Rc for vrrp-web-archive@optimus.ietf.org; Sat, 18 Oct 2003 11:20:11 -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 LAA00962 for ; Sat, 18 Oct 2003 11:20:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAssE-0001vV-00 for vrrp-web-archive@ietf.org; Sat, 18 Oct 2003 11:20:10 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AAssE-0001vS-00 for vrrp-web-archive@ietf.org; Sat, 18 Oct 2003 11:20:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAss6-0004Hl-Ma; Sat, 18 Oct 2003 11:20:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAsrh-0004E7-IU for vrrp@optimus.ietf.org; Sat, 18 Oct 2003 11:19:37 -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 LAA00955 for ; Sat, 18 Oct 2003 11:19:27 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAsrg-0001vM-00 for vrrp@ietf.org; Sat, 18 Oct 2003 11:19:36 -0400 Received: from smtp02.mrf.mail.rcn.net ([207.172.4.61]) by ietf-mx with esmtp (Exim 4.12) id 1AAsrg-0001vI-00 for vrrp@ietf.org; Sat, 18 Oct 2003 11:19:36 -0400 Received: from 65-78-115-165.c3-0.tlg-ubr1.atw-tlg.pa.cable.rcn.com ([65.78.115.165] helo=61dhv01) by smtp02.mrf.mail.rcn.net with smtp (Exim 3.35 #4) id 1AAsrg-0005KB-00; Sat, 18 Oct 2003 11:19:36 -0400 Message-ID: <000901c3958b$39360460$0301a8c0@61dhv01> From: "Mark & Jeanne Zelios" To: Cc: References: <4D7B558499107545BB45044C63822DDE03873BB5@mvebe001.americas.nokia.com> Subject: Re: [VRRP] Referring VRRP by version Date: Sat, 18 Oct 2003 11:19:28 -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.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 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 VRRPv4 and VRRPv6 perhaps? ... unless all version numbers need to be accounted for. Just a thought. Mark ----- Original Message ----- From: To: Sent: Friday, October 17, 2003 7:43 PM Subject: [VRRP] Referring VRRP by version Hi, We are submitting a draft for managed objects (MIB) that can be used by both VRRPv2 and VRRPv3 protocols. We are using the word "VRRPv2" and "VRRP for IPv4" interchangeably in the draft. Similarly both "VRRPv3" and "VRRP for IPv6" are being used in the draft. I want to know what is the correct way to identify these protocols? I feel that referring as "VRRP for IPv4" and "VRRP for IPv6" would be more explanatory and the MIB can be used in unlikely case of more than one VRRP versions for IPv4 and IPv6. On the other hand the MIB may have to be revised any way in the above scenario. VRRPv2 and VRRPv3 may be the best way to refer too. Please let me know your thoughts on this. thanks kalyan _______________________________________________ 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 Sat Oct 18 13:35: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 NAA03269 for ; Sat, 18 Oct 2003 13:35: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 1AAuyn-0005Qk-Mh for vrrp-archive@odin.ietf.org; Sat, 18 Oct 2003 13:35:10 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9IHZ54o020868 for vrrp-archive@odin.ietf.org; Sat, 18 Oct 2003 13:35:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAuyn-0005QV-H0 for vrrp-web-archive@optimus.ietf.org; Sat, 18 Oct 2003 13:35: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 NAA03260 for ; Sat, 18 Oct 2003 13:34:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAuyl-0003Xx-00 for vrrp-web-archive@ietf.org; Sat, 18 Oct 2003 13:35:03 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AAuyk-0003Xu-00 for vrrp-web-archive@ietf.org; Sat, 18 Oct 2003 13:35:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAuyj-0005Py-3q; Sat, 18 Oct 2003 13: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 1AAuyV-0005Ni-On for vrrp@optimus.ietf.org; Sat, 18 Oct 2003 13:34: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 NAA03257 for ; Sat, 18 Oct 2003 13:34:37 -0400 (EDT) From: Mukesh.Gupta@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAuyT-0003Xr-00 for vrrp@ietf.org; Sat, 18 Oct 2003 13:34:45 -0400 Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx with esmtp (Exim 4.12) id 1AAuyS-0003Xo-00 for vrrp@ietf.org; Sat, 18 Oct 2003 13:34:45 -0400 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 h9IHYiX12559 for ; Sat, 18 Oct 2003 20:34:44 +0300 (EET DST) Received: from daebh002.NOE.Nokia.com (unverified) by esvir03nok.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Sat, 18 Oct 2003 20:34:43 +0300 Received: from daebe009.NOE.Nokia.com ([172.18.242.190]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Sat, 18 Oct 2003 12:34:42 -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] Referring VRRP by version Date: Sat, 18 Oct 2003 12:34:42 -0500 Message-ID: <8D260779A766FB4A9C1739A476F84FA42ABDC9@daebe009.americas.nokia.com> Thread-Topic: [VRRP] Routing table in VRRP Thread-Index: AcOFYcSwKXrm7ZliSXm6xe3LJ6pkVwPpP1wAACWOBvA= To: , X-OriginalArrivalTime: 18 Oct 2003 17:34:42.0786 (UTC) FILETIME=[1D719420:01C3959E] 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 Kalyan, Both the names have their own advantages but I think, "VRRP for IPv4" and "VRRP for IPv6" will be better because they could accomodate minor future upgrades to the VRRP versions. Regards Mukesh > -----Original Message----- > From: ext Kalyan.Tata@nokia.com [mailto:Kalyan.Tata@nokia.com] > Sent: Friday, October 17, 2003 4:44 PM > To: vrrp@ietf.org > Subject: [VRRP] Referring VRRP by version >=20 >=20 > Hi, > We are submitting a draft for managed objects (MIB)=20 > that can be used by both VRRPv2 and VRRPv3 protocols. >=20 > We are using the word "VRRPv2" and "VRRP for IPv4"=20 > interchangeably > in the draft. Similarly both "VRRPv3" and "VRRP for IPv6" are=20 > being used in the draft. >=20 > I want to know what is the correct way to identify=20 > these protocols? > =09 > I feel that referring as "VRRP for IPv4" and "VRRP for=20 > IPv6" would=20 > be more explanatory and the MIB can be used in unlikely case of=20 > more than one VRRP versions for IPv4 and IPv6. On the=20 > other hand the=20 > MIB may have to be revised any way in the above scenario. >=20 > VRRPv2 and VRRPv3 may be the best way to refer too. >=20 > Please let me know your thoughts on this. >=20 > thanks > kalyan >=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 Sat Oct 18 18:16: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 SAA11856 for ; Sat, 18 Oct 2003 18:16:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAzMi-0006wv-Tr for vrrp-archive@odin.ietf.org; Sat, 18 Oct 2003 18:16:10 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9IMG4wL026709 for vrrp-archive@odin.ietf.org; Sat, 18 Oct 2003 18:16:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAzMi-0006wi-Q7 for vrrp-web-archive@optimus.ietf.org; Sat, 18 Oct 2003 18:16: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 SAA11728 for ; Sat, 18 Oct 2003 18:15:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAzMf-0007RL-00 for vrrp-web-archive@ietf.org; Sat, 18 Oct 2003 18:16:01 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AAzMf-0007RI-00 for vrrp-web-archive@ietf.org; Sat, 18 Oct 2003 18:16:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAzMf-0006u3-DG; Sat, 18 Oct 2003 18:16:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAzMP-0006rz-Nq for vrrp@optimus.ietf.org; Sat, 18 Oct 2003 18:15:45 -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 SAA11687 for ; Sat, 18 Oct 2003 18:15:33 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAzMM-0007Qu-00 for vrrp@ietf.org; Sat, 18 Oct 2003 18:15:42 -0400 Received: from brmea-mail-3.sun.com ([192.18.98.34]) by ietf-mx with esmtp (Exim 4.12) id 1AAzML-0007Ql-00 for vrrp@ietf.org; Sat, 18 Oct 2003 18:15:42 -0400 Received: from sydney.East.Sun.COM ([129.148.9.16]) by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id h9IMFX5u010942; Sat, 18 Oct 2003 16:15:33 -0600 (MDT) Received: from sydney.East.Sun.COM (esun1as-be21-ge0.Central.Sun.COM [129.147.60.148]) by sydney.East.Sun.COM (8.11.7p1+Sun/8.11.7/ENSMAIL,v2.2) with ESMTP id h9IMFBB16820; Sat, 18 Oct 2003 18:15:20 -0400 (EDT) From: Radia Perlman - Boston Center for Networking Message-Id: <200310182215.h9IMFBB16820@sydney.East.Sun.COM> Date: Sat, 18 Oct 2003 18:16:32 -0400 To: "Mark & Jeanne Zelios" , Cc: Reply-To: Subject: Re: [VRRP] Referring VRRP by version X-Mailer: Sun NetMail 2.3 MIME-Version: 1.0 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 I always disliked the names "VRRPv2" and VRRPv3 to refer to IPv4 and IPv6, respectively. What happens if a new version of VRRP for IPv4 happens? What would it be called? So I like "VRRP for IPv4" and "VRRP for IPv6" as the names. But then what should be done about the version number? With a combined MIB, does that mean that what we've been calling VRRPv3 would really be for both IPv4 and IPv6? Should these be really two different "protocols", which I think means that they'd get different IP IANA-assigned protocol types? Or maybe in addition to a version number there should be a field that says what version(s) of IP are supported? Radia >VRRPv4 and VRRPv6 perhaps? >... unless all version numbers need to be accounted for. >Just a thought. >Mark >----- Original Message ----- >From: >To: >Sent: Friday, October 17, 2003 7:43 PM >Subject: [VRRP] Referring VRRP by version > > >Hi, >We are submitting a draft for managed objects (MIB) >that can be used by both VRRPv2 and VRRPv3 protocols. > >We are using the word "VRRPv2" and "VRRP for IPv4" interchangeably >in the draft. Similarly both "VRRPv3" and "VRRP for IPv6" are >being used in the draft. > >I want to know what is the correct way to identify these protocols? > >I feel that referring as "VRRP for IPv4" and "VRRP for IPv6" would >be more explanatory and the MIB can be used in unlikely case of >more than one VRRP versions for IPv4 and IPv6. On the other hand the >MIB may have to be revised any way in the above scenario. > >VRRPv2 and VRRPv3 may be the best way to refer too. > >Please let me know your thoughts on this. > >thanks >kalyan > >_______________________________________________ >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 _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Sat Oct 18 19:34: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 TAA13643 for ; Sat, 18 Oct 2003 19:34:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AB0aB-0003yl-4e for vrrp-archive@odin.ietf.org; Sat, 18 Oct 2003 19:34:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9INY3pi015289 for vrrp-archive@odin.ietf.org; Sat, 18 Oct 2003 19:34:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AB0aA-0003yW-VM for vrrp-web-archive@optimus.ietf.org; Sat, 18 Oct 2003 19:34: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 TAA13637 for ; Sat, 18 Oct 2003 19:33:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AB0a8-0000FW-00 for vrrp-web-archive@ietf.org; Sat, 18 Oct 2003 19:34:01 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AB0a8-0000FT-00 for vrrp-web-archive@ietf.org; Sat, 18 Oct 2003 19:34:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AB0a8-0003xZ-IY; Sat, 18 Oct 2003 19:34:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AB0Zv-0003vQ-GD for vrrp@optimus.ietf.org; Sat, 18 Oct 2003 19:33: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 TAA13634 for ; Sat, 18 Oct 2003 19:33:36 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AB0Zt-0000FQ-00 for vrrp@ietf.org; Sat, 18 Oct 2003 19:33:45 -0400 Received: from outbound0.sv.meer.net ([205.217.152.13]) by ietf-mx with esmtp (Exim 4.12) id 1AB0Zs-0000FN-00 for vrrp@ietf.org; Sat, 18 Oct 2003 19:33:44 -0400 Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by outbound0.sv.meer.net (8.12.10/8.12.6) with ESMTP id h9INXNhr015961; Sat, 18 Oct 2003 16:33:23 -0700 (PDT) (envelope-from rmh@alderaan.com) Received: from [209.157.142.169] ([209.157.142.169]) by mail.meer.net (8.12.1/8.12.2/meer) with ESMTP id h9INXGYW098373; Sat, 18 Oct 2003 16:33:17 -0700 (PDT) (envelope-from rmh@alderaan.com) Mime-Version: 1.0 X-Sender: rmh@mail.toaster.net Message-Id: In-Reply-To: <200310182215.h9IMFBB16820@sydney.East.Sun.COM> References: <200310182215.h9IMFBB16820@sydney.East.Sun.COM> Date: Sat, 18 Oct 2003 16:33:13 -0700 To: From: Bob Hinden Subject: Re: [VRRP] Referring VRRP by version Cc: "Mark & Jeanne Zelios" , , 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: , Radia, Such weighty issues :-) Seems to me that the MIB should deal in version numbers as it is the version number that defines the fields in the header, etc. If a new version is done, the MIB will need to be able to tell the difference (independent of if it is for IPv4 or IPv6). I agree that for the names of the protocol, "VRRP for IPv4" and "VRRP for IPv6" are best. We could agree to use even version number for "VRRP for IPv4" and odd versions numbers for "VRRP for IPv6". I don't think it is wise to get a new protocol number if the only reason is to make the MIB a little simpler. It's an 8 bit field and the values are shared for IPv4 and IPv6. Bob _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Mon Oct 20 02:36:38 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 CAA14723 for ; Mon, 20 Oct 2003 02:36:38 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABTeJ-00082Y-HJ for vrrp-archive@odin.ietf.org; Mon, 20 Oct 2003 02:36:17 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9K6aFq3030905 for vrrp-archive@odin.ietf.org; Mon, 20 Oct 2003 02:36:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABTeJ-00082O-5r for vrrp-web-archive@optimus.ietf.org; Mon, 20 Oct 2003 02:36: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 CAA14696 for ; Mon, 20 Oct 2003 02:36:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABTeF-0004js-00 for vrrp-web-archive@ietf.org; Mon, 20 Oct 2003 02:36:11 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ABTeE-0004jo-00 for vrrp-web-archive@ietf.org; Mon, 20 Oct 2003 02:36:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABTe5-0007zM-3x; Mon, 20 Oct 2003 02:36:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABTdi-0007sp-U6 for vrrp@optimus.ietf.org; Mon, 20 Oct 2003 02:35:39 -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 CAA14679 for ; Mon, 20 Oct 2003 02:35:29 -0400 (EDT) From: Kalyan.Tata@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABTdf-0004jY-00 for vrrp@ietf.org; Mon, 20 Oct 2003 02:35:35 -0400 Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 1ABTde-0004jU-00 for vrrp@ietf.org; Mon, 20 Oct 2003 02:35:34 -0400 Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37]) by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9K6ZYd02787 for ; Mon, 20 Oct 2003 09:35:34 +0300 (EET DST) Received: from daebh001.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Mon, 20 Oct 2003 09:35:33 +0300 Received: from mvebe001.NOE.Nokia.com ([172.18.140.37]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Sun, 19 Oct 2003 23:35:31 -0700 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] Referring VRRP by version X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 Date: Sun, 19 Oct 2003 23:35:31 -0700 Message-ID: <4D7B558499107545BB45044C63822DDE03873BBA@mvebe001.americas.nokia.com> Thread-Topic: [VRRP] Referring VRRP by version Thread-Index: AcOV0Idg26vqLpBeSdy1u4AfCQ5RsQBAJy2w To: , Cc: , X-OriginalArrivalTime: 20 Oct 2003 06:35:31.0851 (UTC) FILETIME=[5C1355B0:01C396D4] 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, My original question was regarding the text describing the two VRRP protocols. Right now the draft (for MIB) uses both VRRP v2 and VRRP for = IPv4. The MIB itself has a version field in the table entry that describes a = virtual=20 router (uniquely identified by interfaceIndex/VRID ) I need to reformat the doc if I have to change the draft to use "VRRP = for IPvx" every where, So I am going to submit it as it is and will correct this = once we reach a consensus on how best to describe these two protocols. Thanks -kalyan -----Original Message----- From: ext Bob Hinden [mailto:rmh@alderaan.com] Sent: Saturday, October 18, 2003 4:33 PM To: Radia.Perlman@Sun.COM Cc: Mark & Jeanne Zelios; Tata Kalyan (NES/MtView); vrrp@ietf.org Subject: Re: [VRRP] Referring VRRP by version Radia, Such weighty issues :-) Seems to me that the MIB should deal in version numbers as it is the=20 version number that defines the fields in the header, etc. If a new=20 version is done, the MIB will need to be able to tell the difference=20 (independent of if it is for IPv4 or IPv6). I agree that for the names of the protocol, "VRRP for IPv4" and "VRRP=20 for IPv6" are best. We could agree to use even version number for "VRRP for IPv4" and odd=20 versions numbers for "VRRP for IPv6". I don't think it is wise to get a new protocol number if the only=20 reason is to make the MIB a little simpler. It's an 8 bit field and=20 the values are shared for IPv4 and IPv6. Bob _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Mon Oct 20 19:40:58 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 TAA14618 for ; Mon, 20 Oct 2003 19:40:58 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABjde-00007j-69 for vrrp-archive@odin.ietf.org; Mon, 20 Oct 2003 19:40:38 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9KNecMI000471 for vrrp-archive@odin.ietf.org; Mon, 20 Oct 2003 19:40:38 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABjde-00007W-2q for vrrp-web-archive@optimus.ietf.org; Mon, 20 Oct 2003 19:40:38 -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 TAA14606 for ; Mon, 20 Oct 2003 19:40:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABjd4-0008O2-6x; Mon, 20 Oct 2003 19:40:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABfyw-000264-R5 for vrrp@optimus.ietf.org; Mon, 20 Oct 2003 15:46:22 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22498; Mon, 20 Oct 2003 15:46:13 -0400 (EDT) Message-Id: <200310201946.PAA22498@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, 20 Oct 2003 15:46:13 -0400 Subject: [VRRP] I-D ACTION:draft-ietf-vrrp-unified-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 VRRPv2 and VRRpv3 Author(s) : K. Tata, et. al. Filename : draft-ietf-vrrp-unified-mib-00.txt Pages : 31 Date : 2003-10-20 This specification defines a 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 both IPv4 and IPv6 as defined in draft-ietf-vrrp-spec-v2-09.txt [RFCxxxx] and draft- ietf-vrrp-ipv6-spec-04.txt [RFCyyyy]. This memo obsolates RFC 2787 [RFC2787] A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-vrrp-unified-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-unified-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-unified-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-10-20145425.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-vrrp-unified-mib-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-vrrp-unified-mib-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-10-20145425.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 Oct 21 13:29: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 NAA27213 for ; Tue, 21 Oct 2003 13:29: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 1AC0Jn-0001RT-VR for vrrp-archive@odin.ietf.org; Tue, 21 Oct 2003 13:29:16 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9LHTFul005539 for vrrp-archive@odin.ietf.org; Tue, 21 Oct 2003 13:29:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AC0Jn-0001RG-Ma for vrrp-web-archive@optimus.ietf.org; Tue, 21 Oct 2003 13:29: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 NAA27194 for ; Tue, 21 Oct 2003 13:29:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AC0Jl-0006Le-00 for vrrp-web-archive@ietf.org; Tue, 21 Oct 2003 13:29:13 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AC0Jl-0006La-00 for vrrp-web-archive@ietf.org; Tue, 21 Oct 2003 13:29:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AC0JY-0001K5-SD; Tue, 21 Oct 2003 13: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 1AC0In-00016I-N7 for vrrp@optimus.ietf.org; Tue, 21 Oct 2003 13:28: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 NAA27181 for ; Tue, 21 Oct 2003 13:28:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AC0Il-0006KX-00 for vrrp@ietf.org; Tue, 21 Oct 2003 13:28:11 -0400 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1AC0Ik-0006KE-00 for vrrp@ietf.org; Tue, 21 Oct 2003 13:28:11 -0400 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h9LHRQF22232; Tue, 21 Oct 2003 10:27:26 -0700 X-mProtect: <200310211727> 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 smtpdURDdOa; Tue, 21 Oct 2003 10:27:24 PDT Message-Id: <4.3.2.7.2.20031021100447.02fe09d8@mailhost.iprg.nokia.com> X-Sender: hinden@mailhost.iprg.nokia.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 21 Oct 2003 10:27:05 -0700 To: Kalyan.Tata@nokia.com From: Bob Hinden Subject: RE: [VRRP] Referring VRRP by version Cc: , mzelios@rcn.com, In-Reply-To: <4D7B558499107545BB45044C63822DDE03873BBA@mvebe001.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: , Kalyan, At 11:35 PM 10/19/2003, Kalyan.Tata@nokia.com wrote: >hi, My original question was regarding the text describing the two VRRP >protocols. Right now the draft (for MIB) uses both VRRP v2 and VRRP for IPv4. > >The MIB itself has a version field in the table entry that describes a >virtual >router (uniquely identified by interfaceIndex/VRID ) > >I need to reformat the doc if I have to change the draft to use "VRRP for >IPvx" >every where, So I am going to submit it as it is and will correct this once >we reach a consensus on how best to describe these two protocols. Sound to me like there is agreement to have the text describing the name of the two VRRP protocols as "VRRP for IPv4" and "VRRP for IPv6". Bob _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Tue Oct 21 17:47: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 RAA12277 for ; Tue, 21 Oct 2003 17:47: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 1AC4LR-0000QT-Q5 for vrrp-archive@odin.ietf.org; Tue, 21 Oct 2003 17:47:15 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9LLlDV0001633 for vrrp-archive@odin.ietf.org; Tue, 21 Oct 2003 17:47:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AC4LR-0000QG-Mh for vrrp-web-archive@optimus.ietf.org; Tue, 21 Oct 2003 17:47: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 RAA12236 for ; Tue, 21 Oct 2003 17:47:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AC4LO-00037U-00 for vrrp-web-archive@ietf.org; Tue, 21 Oct 2003 17:47:11 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AC4LO-00037R-00 for vrrp-web-archive@ietf.org; Tue, 21 Oct 2003 17:47:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AC4LF-0000Mz-0B; Tue, 21 Oct 2003 17:47:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AC4Kj-0000HM-I1 for vrrp@optimus.ietf.org; Tue, 21 Oct 2003 17:46:29 -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 RAA12212; Tue, 21 Oct 2003 17:46:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AC4Kg-00036p-00; Tue, 21 Oct 2003 17:46:26 -0400 Received: from coconut.itojun.org ([219.101.47.130]) by ietf-mx with esmtp (Exim 4.12) id 1AC4Ke-00036g-00; Tue, 21 Oct 2003 17:46:25 -0400 Received: by coconut.itojun.org (Postfix, from userid 1001) id CDE5D9C; Wed, 22 Oct 2003 06:46:23 +0900 (JST) To: hinden@iprg.nokia.com Cc: Radia Perlman , Mukesh Gupta , vrrp@ietf.org, ietf@ietf.org X-Mailer: Cue version 0.6 (031002-0709/itojun) Mime-Version: 1.0 References: <20031015014322.308B890@coconut.itojun.org> Cc: itojun@itojun.org Content-Type: Text/Plain; charset=us-ascii Message-Id: <20031021214623.CDE5D9C@coconut.itojun.org> Date: Wed, 22 Oct 2003 06:46:23 +0900 (JST) From: itojun@itojun.org (Jun-ichiro itojun Hagino) Subject: [VRRP] Re: draft-ietf-vrrp-ipv6-spec-05.txt lacks IPR clause 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: , btw, KAME have removed VRRP6 implementation from the distribution because of the IPR statement (it conflicts with our policy about IPR). there's ongoing work called "carp" which is specifically designed to avoid infringing cisco patent on HSRP by avoiding core details, so KAME would integrate that eventually. itojun --- KAME IPR policy 9. Policy on technology with intellectual property right restriction There are quite a few IETF documents/whatever which has intellectual property right (IPR) restriction. KAME's stance is stated below. The goal of KAME is to provide freely redistributable, BSD-licensed, implementation of Internet protocol technologies. For this purpose, we implement protocols that (1) do not need license contract with IPR holder, and (2) are royality-free. The reason for (1) is, even if KAME contracts with the IPR holder in question, the users of KAME stack (usually implementers of some other codebase) would need to make a license contract with the IPR holder. it would damage "freely redistributable" status of KAME codebase. By doing so KAME is (implicitly) trying to advocate no-license-contract, royality-free, release of IPRs. Note however, as documented in README, we do not guarantee that KAME code is free of IPR infringement, you MUST check it if you are to integrate KAME into your product (or whatever): READ CAREFULLY: Several countries have legal enforcement for export/import/use of cryptographic software. Check it before playing with the kit. We do not intend to be your legalease clearing house (NO WARRANTY). If you intend to include KAME stack into your product, you'll need to check if the licenses on each file fit your situations, and/or possible intellectual property right issues. _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Tue Oct 21 20:42:26 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 UAA21602 for ; Tue, 21 Oct 2003 20:42: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 1AC74g-0005Bm-8e for vrrp-archive@odin.ietf.org; Tue, 21 Oct 2003 20:42:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9M0g6Cj019942 for vrrp-archive@odin.ietf.org; Tue, 21 Oct 2003 20:42:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AC74g-0005BG-2N for vrrp-web-archive@optimus.ietf.org; Tue, 21 Oct 2003 20:42: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 UAA21594 for ; Tue, 21 Oct 2003 20:41:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AC74d-0005kR-00 for vrrp-web-archive@ietf.org; Tue, 21 Oct 2003 20:42:03 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AC74d-0005kO-00 for vrrp-web-archive@ietf.org; Tue, 21 Oct 2003 20:42:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AC74b-00058d-S6; Tue, 21 Oct 2003 20:42:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AC743-0004uI-4f for vrrp@optimus.ietf.org; Tue, 21 Oct 2003 20:41:27 -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 UAA21572 for ; Tue, 21 Oct 2003 20:41:16 -0400 (EDT) From: Kalyan.Tata@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AC740-0005jv-00 for vrrp@ietf.org; Tue, 21 Oct 2003 20:41:24 -0400 Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx with esmtp (Exim 4.12) id 1AC73z-0005js-00 for vrrp@ietf.org; Tue, 21 Oct 2003 20:41:24 -0400 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 h9M0fNq27076 for ; Wed, 22 Oct 2003 03:41:23 +0300 (EET DST) Received: from daebh002.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Wed, 22 Oct 2003 03:41:23 +0300 Received: from mvebe001.NOE.Nokia.com ([172.18.140.37]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Tue, 21 Oct 2003 19:41:21 -0500 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 Subject: RE: [VRRP] Referring VRRP by version Date: Tue, 21 Oct 2003 17:41:20 -0700 Message-ID: <4D7B558499107545BB45044C63822DDE03ADD25F@mvebe001.americas.nokia.com> Thread-Topic: [VRRP] Referring VRRP by version Thread-Index: AcOX+JvPMqdGeF6+SIyVMtmTJNrhagAPEVXA To: Cc: , , X-OriginalArrivalTime: 22 Oct 2003 00:41:21.0698 (UTC) FILETIME=[36D2D020:01C39835] 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, yes, I think we have a consensus. I will update our=20 draft with these text changes in the next revision. Thanks kalyan=20 -----Original Message----- From: Bob Hinden [mailto:bob.hinden@nokia.com] Sent: 21 October, 2003 10:27 To: Tata Kalyan (NES/MtView) Cc: Radia.Perlman@Sun.COM; mzelios@rcn.com; vrrp@ietf.org Subject: RE: [VRRP] Referring VRRP by version Kalyan, At 11:35 PM 10/19/2003, Kalyan.Tata@nokia.com wrote: >hi, My original question was regarding the text describing the two VRRP >protocols. Right now the draft (for MIB) uses both VRRP v2 and VRRP for = IPv4. > >The MIB itself has a version field in the table entry that describes a=20 >virtual >router (uniquely identified by interfaceIndex/VRID ) > >I need to reformat the doc if I have to change the draft to use "VRRP = for=20 >IPvx" >every where, So I am going to submit it as it is and will correct this = once >we reach a consensus on how best to describe these two protocols. Sound to me like there is agreement to have the text describing the name = of=20 the two VRRP protocols as "VRRP for IPv4" and "VRRP for IPv6". Bob _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Wed Oct 22 17:28: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 RAA28792 for ; Wed, 22 Oct 2003 17:28: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 1ACQWf-0004q2-Ov for vrrp-archive@odin.ietf.org; Wed, 22 Oct 2003 17:28:18 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9MLSHiw018594 for vrrp-archive@odin.ietf.org; Wed, 22 Oct 2003 17:28:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACQWf-0004pp-KN for vrrp-web-archive@optimus.ietf.org; Wed, 22 Oct 2003 17:28: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 RAA28781 for ; Wed, 22 Oct 2003 17:28:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACQWd-0002xd-00 for vrrp-web-archive@ietf.org; Wed, 22 Oct 2003 17:28:15 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACQWc-0002xZ-00 for vrrp-web-archive@ietf.org; Wed, 22 Oct 2003 17:28:14 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACQWP-0004lD-Nm; Wed, 22 Oct 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 1ACQW6-0004gy-9K for vrrp@optimus.ietf.org; Wed, 22 Oct 2003 17:27:42 -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 RAA28750 for ; Wed, 22 Oct 2003 17:27:30 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACQW3-0002x0-00 for vrrp@ietf.org; Wed, 22 Oct 2003 17:27:39 -0400 Received: from email.quarrytech.com ([4.17.144.4] helo=qtech1.quarrytech.com) by ietf-mx with esmtp (Exim 4.12) id 1ACQW3-0002wa-00 for vrrp@ietf.org; Wed, 22 Oct 2003 17:27:39 -0400 Received: from MDUFFY1.quarrytech.com (MDUFFY1 [10.1.3.166]) by qtech1.quarrytech.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id VJD9MMN0; Wed, 22 Oct 2003 17:27:07 -0400 Message-Id: <5.2.0.9.0.20031022165810.0212aae0@email> X-Sender: mduffy@email X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Wed, 22 Oct 2003 17:11:35 -0400 To: vrrp@ietf.org From: Mark Duffy Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [VRRP] newbie vrrp 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: , Hi, and apologies if this has been covered before. The latest draft (and RFC 2338) is quite clear that the router in Master state - MUST NOT accept packets addressed to the IP address(es) associated with the virtual router if it is not the IP address owner. What is the reason for this? Accepting packets for connection-oriented protocols might not fare too well if a reelection happened in the middle, but I don't see how it would "break" the vrrp protocol to accept these packets. And it seems as though having the virtual router respond to ping would be quite helpful for troubleshooting. I have noticed that a major-vendor router accepts ping, telnet, etc. on the virtual router IP address when it is master, even when it is not the address owner. Thanks, Mark _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Wed Oct 22 18:31: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 SAA02093 for ; Wed, 22 Oct 2003 18:31:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACRVX-0000Pu-2F for vrrp-archive@odin.ietf.org; Wed, 22 Oct 2003 18:31:11 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9MMVBqQ001601 for vrrp-archive@odin.ietf.org; Wed, 22 Oct 2003 18:31:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACRVW-0000Pk-VE for vrrp-web-archive@optimus.ietf.org; Wed, 22 Oct 2003 18:31: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 SAA02047 for ; Wed, 22 Oct 2003 18:30:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACRVT-0003TG-00 for vrrp-web-archive@ietf.org; Wed, 22 Oct 2003 18:31:07 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACRVT-0003TD-00 for vrrp-web-archive@ietf.org; Wed, 22 Oct 2003 18:31:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACRVO-0000Mk-Dv; Wed, 22 Oct 2003 18: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 1ACRUc-0000DV-72 for vrrp@optimus.ietf.org; Wed, 22 Oct 2003 18:30: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 SAA02007 for ; Wed, 22 Oct 2003 18:30:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACRUZ-0003S3-00 for vrrp@ietf.org; Wed, 22 Oct 2003 18:30:11 -0400 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1ACRUY-0003RU-00 for vrrp@ietf.org; Wed, 22 Oct 2003 18:30:10 -0400 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h9MMTdw01293; Wed, 22 Oct 2003 15:29:39 -0700 X-mProtect: <200310222229> 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 smtpdw9ZgMe; Wed, 22 Oct 2003 15:29:36 PDT Message-Id: <4.3.2.7.2.20031022152233.034d2270@mailhost.iprg.nokia.com> X-Sender: hinden@mailhost.iprg.nokia.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 22 Oct 2003 15:29:12 -0700 To: Mark Duffy From: Bob Hinden Subject: Re: [VRRP] newbie vrrp question Cc: vrrp@ietf.org In-Reply-To: <5.2.0.9.0.20031022165810.0212aae0@email> 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 02:11 PM 10/22/2003, Mark Duffy wrote: >Hi, and apologies if this has been covered before. Yes, it has. Someone should write a VRRP FAQ.... >The latest draft (and RFC 2338) is quite clear that the router in Master state > > - MUST NOT accept packets addressed to the IP address(es) associated > with the virtual router if it is not the IP address owner. > >What is the reason for this? The reason for not accepting packets addressed to the IP address of the owner, if not the owner, is to make it easier to detect that one of the routers is down. People have had problems with other redundancy protocols that did not have the behavior that their network management systems would not detect that one of the routers had failed because the IP address still responded to pings, SNMP queries, etc. It is also confusing for routing protocols. The desired behavior when one of the routers fails is to have user traffic keep flowing, but to have all network management bells start ringing. >Accepting packets for connection-oriented protocols might not fare too >well if a reelection happened in the middle, but I don't see how it would >"break" the vrrp protocol to accept these packets. And it seems as though >having the virtual router respond to ping would be quite helpful for >troubleshooting. I have noticed that a major-vendor router accepts ping, >telnet, etc. on the virtual router IP address when it is master, even when >it is not the address owner. Time to call the IETF protocol police :-) Bob _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Sun Oct 26 15:42: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 PAA27910 for ; Sun, 26 Oct 2003 15:42:27 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADriC-0002q8-Ds for vrrp-archive@odin.ietf.org; Sun, 26 Oct 2003 15:42:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9QKg8V2010910 for vrrp-archive@odin.ietf.org; Sun, 26 Oct 2003 15:42:08 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADriC-0002pt-9q for vrrp-web-archive@optimus.ietf.org; Sun, 26 Oct 2003 15:42: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 PAA27896 for ; Sun, 26 Oct 2003 15:41:56 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ADriA-0000Zz-00 for vrrp-web-archive@ietf.org; Sun, 26 Oct 2003 15:42:06 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ADriA-0000Zw-00 for vrrp-web-archive@ietf.org; Sun, 26 Oct 2003 15:42:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADri5-0002op-Jm; Sun, 26 Oct 2003 15:42:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADrhV-0002nJ-W4 for vrrp@optimus.ietf.org; Sun, 26 Oct 2003 15:41: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 PAA27893 for ; Sun, 26 Oct 2003 15:41:14 -0500 (EST) From: Mukesh.Gupta@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ADrhU-0000Zs-00 for vrrp@ietf.org; Sun, 26 Oct 2003 15:41:24 -0500 Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 1ADrhT-0000Zp-00 for vrrp@ietf.org; Sun, 26 Oct 2003 15:41:24 -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 h9QKfNI18336 for ; Sun, 26 Oct 2003 22:41:23 +0200 (EET) Received: from daebh002.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Sun, 26 Oct 2003 22:41:22 +0200 Received: from daebe009.NOE.Nokia.com ([172.18.242.190]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Sun, 26 Oct 2003 14:41:21 -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: Sun, 26 Oct 2003 14:41:21 -0600 Message-ID: <8D260779A766FB4A9C1739A476F84FA401546E62@daebe009.americas.nokia.com> Thread-Topic: Agenda for IETF58th Thread-Index: AcOcAYJPvcMg9ZzETViPJtWafIA1zg== To: Cc: X-OriginalArrivalTime: 26 Oct 2003 20:41:21.0640 (UTC) FILETIME=[83C91680:01C39C01] Content-Transfer-Encoding: quoted-printable Subject: [VRRP] Agenda for IETF58th 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 what we have currently. Please send us a mail if you want to add something. ****************************************************** Virtual Router Redundancy Protocol WG (vrrp) Thursday, November 13, 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=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 VRRPv3 MIB Kalyan Tata 20 minutes http://ietf.org/internet-drafts/draft-ietf-vrrp-unified-mib-00.txt http://ietf.org/internet-drafts/draft-ietf-vrrp-ipv6-mib-00.txt VMACs vs ND for VRRPv3 Chairs 15 minutes http://ietf.org/internet-drafts/draft-ietf-vrrp-ipv6-spec-05.txt _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp