From mailnull@www1.ietf.org Sun Jun 15 22:48:57 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA17415 for ; Sun, 15 Jun 2003 22:48:57 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5G2mUi14281 for vrrp-archive@odin.ietf.org; Sun, 15 Jun 2003 22:48:30 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5G2mUm14278 for ; Sun, 15 Jun 2003 22:48:30 -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 WAA17408 for ; Sun, 15 Jun 2003 22:48:27 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Rk0c-0006eF-00 for vrrp-web-archive@ietf.org; Sun, 15 Jun 2003 22:46:14 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Rk0b-0006eB-00 for vrrp-web-archive@ietf.org; Sun, 15 Jun 2003 22:46:13 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5G1R0a09295; Sun, 15 Jun 2003 21:27:00 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5G1Qkm09262 for ; Sun, 15 Jun 2003 21:26:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16221 for ; Sun, 15 Jun 2003 21:26:43 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19RijW-0006NH-00 for vrrp@ietf.org; Sun, 15 Jun 2003 21:24:30 -0400 Received: from nwkea-mail-1.sun.com ([192.18.42.13]) by ietf-mx with esmtp (Exim 4.12) id 19RijV-0006NA-00 for vrrp@ietf.org; Sun, 15 Jun 2003 21:24:30 -0400 Received: from sydney.East.Sun.COM ([129.148.9.16]) by nwkea-mail-1.sun.com (8.12.9/8.12.9) with ESMTP id h5G1QC4Z013095 for ; Sun, 15 Jun 2003 18:26:12 -0700 (PDT) Received: from sydney.East.Sun.COM (esun1as-be21-ge0.Central.Sun.COM [129.147.60.148]) by sydney.East.Sun.COM (8.11.7+Sun/8.11.7/ENSMAIL,v2.2) with ESMTP id h5G1Q5s10871 for ; Sun, 15 Jun 2003 21:26:07 -0400 (EDT) From: Radia Perlman - Boston Center for Networking Message-Id: <200306160126.h5G1Q5s10871@sydney.East.Sun.COM> Date: Sun, 15 Jun 2003 21:26:35 -0400 To: Reply-To: 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 Subject: [VRRP] OK. What's with the IPv6 mib draft? 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'm jumping in new here and I'm keeping up with the regular drafts, but I don't see any email about the IPv6 mib (And Mukesh is out of town). Apparently we are past due on the milestone for that draft (ipv6 mib). Who is working on it? What state is it in? Speaking of which...I'm not quite sure why WGs have two documents...one for IPv6 and one for IPv4. Wouldn't there be cases where IPv6 and IPv4 were coexisting on the same LAN, so therefore there might be routers performing VRRP for both IPv6 and IPv4 simultaneously? I'd think it would be easier for an implementer if there were one spec, that told you how to do both simultaneously, since there also might be some interactions that would have to be thought about when doing both IPv6 and IPv4 simultaneously. Thanks... Radia _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From mailnull@www1.ietf.org Mon Jun 16 19:55:04 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09182 for ; Mon, 16 Jun 2003 19:55:04 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5GNsZC16398 for vrrp-archive@odin.ietf.org; Mon, 16 Jun 2003 19:54:35 -0400 Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5GNsZm16395 for ; Mon, 16 Jun 2003 19:54: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 TAA09168 for ; Mon, 16 Jun 2003 19:54:33 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19S3lq-0000U9-00 for vrrp-web-archive@ietf.org; Mon, 16 Jun 2003 19:52:18 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19S3lp-0000U6-00 for vrrp-web-archive@ietf.org; Mon, 16 Jun 2003 19:52:17 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5GIF1a23907; Mon, 16 Jun 2003 14:15:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5GIEkm23888 for ; Mon, 16 Jun 2003 14:14:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23892 for ; Mon, 16 Jun 2003 14:14:43 -0400 (EDT) From: BJewell@coppermountain.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19RySz-0004n4-00 for vrrp@ietf.org; Mon, 16 Jun 2003 14:12:29 -0400 Received: from pamail.faststartdsl.com ([12.147.16.235] helo=fs-pa-exch1.coppermountain.com) by ietf-mx with esmtp (Exim 4.12) id 19RySy-0004mh-00 for vrrp@ietf.org; Mon, 16 Jun 2003 14:12:28 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [VRRP] OK. What's with the IPv6 mib draft? Date: Mon, 16 Jun 2003 11:13:23 -0700 Message-ID: Thread-Topic: [VRRP] OK. What's with the IPv6 mib draft? Thread-Index: AcMzr4eg1jJB63R3TLeAnTW8qlRK7QAgc5gw To: , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h5GIEkm23889 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: 8bit Content-Transfer-Encoding: 8bit There has been some work going on for the VRRP V6 MIB in background. The intention was to post it to the Mailing List soon. But, we've all been pretty busy, so I think the draft has fallen a little behind. Here's the list of authors: Kalyan.Tata@nokia.com; Kripakaran.Karlekar@nokia.com; bjewell@coppermountain.com; Thanks. -Brian -----Original Message----- From: Radia Perlman - Boston Center for Networking [mailto:Radia.Perlman@sun.com] Sent: Sunday, June 15, 2003 6:27 PM To: vrrp@ietf.org Subject: [VRRP] OK. What's with the IPv6 mib draft? I'm jumping in new here and I'm keeping up with the regular drafts, but I don't see any email about the IPv6 mib (And Mukesh is out of town). Apparently we are past due on the milestone for that draft (ipv6 mib). Who is working on it? What state is it in? Speaking of which...I'm not quite sure why WGs have two documents...one for IPv6 and one for IPv4. Wouldn't there be cases where IPv6 and IPv4 were coexisting on the same LAN, so therefore there might be routers performing VRRP for both IPv6 and IPv4 simultaneously? I'd think it would be easier for an implementer if there were one spec, that told you how to do both simultaneously, since there also might be some interactions that would have to be thought about when doing both IPv6 and IPv4 simultaneously. Thanks... Radia _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From mailnull@www1.ietf.org Tue Jun 17 00:06:51 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15756 for ; Tue, 17 Jun 2003 00:06:50 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5H46M201697 for vrrp-archive@odin.ietf.org; Tue, 17 Jun 2003 00:06:22 -0400 Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5H46Dm01692 for ; Tue, 17 Jun 2003 00:06: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 AAA15748 for ; Tue, 17 Jun 2003 00:06:08 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19S7hK-0002Jt-00 for vrrp-web-archive@ietf.org; Tue, 17 Jun 2003 00:03:54 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19S7hJ-0002Jp-00 for vrrp-web-archive@ietf.org; Tue, 17 Jun 2003 00:03:53 -0400 Received: from www1.ietf.org (a.mx.viagraonlinenow.biz [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5GJ90a28147; Mon, 16 Jun 2003 15:09:00 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5GJ8Gm28107 for ; Mon, 16 Jun 2003 15:08:16 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26154 for ; Mon, 16 Jun 2003 15:08:12 -0400 (EDT) From: Kalyan.Tata@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19RzIk-0005LA-00 for vrrp@ietf.org; Mon, 16 Jun 2003 15:05:58 -0400 Received: from [63.78.179.217] (helo=mgw-dax2.ext.nokia.com) by ietf-mx with esmtp (Exim 4.12) id 19RzIh-0005L5-00 for vrrp@ietf.org; Mon, 16 Jun 2003 15:05:55 -0400 Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87]) by mgw-dax2.ext.nokia.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h5GJ89G03815 for ; Mon, 16 Jun 2003 14:08:09 -0500 (CDT) Received: from daebh001.NOE.Nokia.com (unverified) by davir04nok.americas.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Mon, 16 Jun 2003 14:08:20 -0500 Received: from mvebe001.NOE.Nokia.com ([172.18.140.37]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Mon, 16 Jun 2003 12:07:07 -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" Subject: RE: [VRRP] OK. What's with the IPv6 mib draft? Date: Mon, 16 Jun 2003 12:07:06 -0700 Message-ID: <4D7B558499107545BB45044C63822DDE011A0B06@mvebe001.americas.nokia.com> Thread-Topic: [VRRP] OK. What's with the IPv6 mib draft? Thread-Index: AcMzrQ7XxAtIM9JLSxa8mjBrgQMWpgAhmgmQ To: , Cc: , X-OriginalArrivalTime: 16 Jun 2003 19:07:07.0693 (UTC) FILETIME=[7B3E3DD0:01C3343A] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h5GJ8Gm28108 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: 8bit Content-Transfer-Encoding: 8bit hi Radia, Brian Jewell, Karlekar Kripakaran and myself are working on this draft. The draft is almost ready except for some minor corrections and formatting issues. We are working on this and should be ready in a week. We are expected to submit this by june 26th (that is the date given by Mukesh). On the question of why we need two documents, We did investigate the possibility of having one VRRP MIB that would work with both VRRP over IPv4 and IPv6. From what we understood from RFC 3291, MIB modules that are inherently IP version specific should be separate documents. We verified this with Bob Hinden and he confirmed that VRRPv2 is dependant on IPv4 and VRRPv3 is dependant on IPv6 and that these are two separate (though similar) protocols. I also talked to some VRRP protocol developers regarding the implementation of VRRPv6, and they too seem to agree that VRRP over IPv6 and the corresponding MIB should be separate from the existing protocol/ MIB. So our agenda was: Defining a completely new MIB for VRRP-IPv6 (which is to a large extent similar to RFC 2787) - which uses inetAddress / inetAddressType, - Add any new objects that IPv6 specific, - Remove any objects that are not relevant to IPv6 (there are some) - Add more clarifications to the existing objects if needed. Thanks kalyan -----Original Message----- From: ext Radia Perlman - Boston Center for Networking [mailto:Radia.Perlman@sun.com] Sent: 15 June, 2003 18:27 To: vrrp@ietf.org Subject: [VRRP] OK. What's with the IPv6 mib draft? I'm jumping in new here and I'm keeping up with the regular drafts, but I don't see any email about the IPv6 mib (And Mukesh is out of town). Apparently we are past due on the milestone for that draft (ipv6 mib). Who is working on it? What state is it in? Speaking of which...I'm not quite sure why WGs have two documents...one for IPv6 and one for IPv4. Wouldn't there be cases where IPv6 and IPv4 were coexisting on the same LAN, so therefore there might be routers performing VRRP for both IPv6 and IPv4 simultaneously? I'd think it would be easier for an implementer if there were one spec, that told you how to do both simultaneously, since there also might be some interactions that would have to be thought about when doing both IPv6 and IPv4 simultaneously. Thanks... Radia _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From mailnull@www1.ietf.org Tue Jun 17 00:23:38 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16174 for ; Tue, 17 Jun 2003 00:23:38 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5H4N8f03483 for vrrp-archive@odin.ietf.org; Tue, 17 Jun 2003 00:23:08 -0400 Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5H4Mtm03480 for ; Tue, 17 Jun 2003 00:22:55 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16149 for ; Tue, 17 Jun 2003 00:22:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19S7xV-0002RS-00 for vrrp-web-archive@ietf.org; Tue, 17 Jun 2003 00:20:37 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19S7xU-0002RP-00 for vrrp-web-archive@ietf.org; Tue, 17 Jun 2003 00:20:36 -0400 Received: from www1.ietf.org (a.mx.viagraonlinenow.biz [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5GJI1a28512; Mon, 16 Jun 2003 15:18:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5GJHum28500 for ; Mon, 16 Jun 2003 15:17:56 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27245 for ; Mon, 16 Jun 2003 15:17:55 -0400 (EDT) From: Kalyan.Tata@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19RzS8-0005Te-00 for vrrp@ietf.org; Mon, 16 Jun 2003 15:15:40 -0400 Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx with esmtp (Exim 4.12) id 19RzS7-0005Tb-00 for vrrp@ietf.org; Mon, 16 Jun 2003 15:15:39 -0400 Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36]) by mgw-x4.nokia.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h5GJHq904367 for ; Mon, 16 Jun 2003 22:17:52 +0300 (EET DST) Received: from esebh002.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Mon, 16 Jun 2003 22:17:52 +0300 Received: from daebh002.NOE.Nokia.com ([172.18.242.232]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Mon, 16 Jun 2003 22:17:52 +0300 Received: from mvebe001.NOE.Nokia.com ([172.18.140.37]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Mon, 16 Jun 2003 14:17:40 -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" Subject: RE: [VRRP] OK. What's with the IPv6 mib draft? Date: Mon, 16 Jun 2003 12:17:39 -0700 Message-ID: <4D7B558499107545BB45044C63822DDE01CBC4FF@mvebe001.americas.nokia.com> Thread-Topic: [VRRP] OK. What's with the IPv6 mib draft? Thread-Index: AcMzrQ7XxAtIM9JLSxa8mjBrgQMWpgAhmgmQAAH5n1A= To: , , Cc: , X-OriginalArrivalTime: 16 Jun 2003 19:17:40.0199 (UTC) FILETIME=[F43EFF70:01C3343B] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h5GJHvm28501 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: 8bit Content-Transfer-Encoding: 8bit hi, the due date is June 23rd not 26 as I mentioned in my previous mail. thanks kalyan -----Original Message----- From: Tata Kalyan (NIC/MtView) Sent: 16 June, 2003 12:07 To: 'radia.perlman@sun.com'; vrrp@ietf.org Cc: Karlekar Kripakaran (NIC/MtView); 'bjewell@coppermountain.com' Subject: RE: [VRRP] OK. What's with the IPv6 mib draft? hi Radia, Brian Jewell, Karlekar Kripakaran and myself are working on this draft. The draft is almost ready except for some minor corrections and formatting issues. We are working on this and should be ready in a week. We are expected to submit this by june 26th (that is the date given by Mukesh). On the question of why we need two documents, We did investigate the possibility of having one VRRP MIB that would work with both VRRP over IPv4 and IPv6. From what we understood from RFC 3291, MIB modules that are inherently IP version specific should be separate documents. We verified this with Bob Hinden and he confirmed that VRRPv2 is dependant on IPv4 and VRRPv3 is dependant on IPv6 and that these are two separate (though similar) protocols. I also talked to some VRRP protocol developers regarding the implementation of VRRPv6, and they too seem to agree that VRRP over IPv6 and the corresponding MIB should be separate from the existing protocol/ MIB. So our agenda was: Defining a completely new MIB for VRRP-IPv6 (which is to a large extent similar to RFC 2787) - which uses inetAddress / inetAddressType, - Add any new objects that IPv6 specific, - Remove any objects that are not relevant to IPv6 (there are some) - Add more clarifications to the existing objects if needed. Thanks kalyan -----Original Message----- From: ext Radia Perlman - Boston Center for Networking [mailto:Radia.Perlman@sun.com] Sent: 15 June, 2003 18:27 To: vrrp@ietf.org Subject: [VRRP] OK. What's with the IPv6 mib draft? I'm jumping in new here and I'm keeping up with the regular drafts, but I don't see any email about the IPv6 mib (And Mukesh is out of town). Apparently we are past due on the milestone for that draft (ipv6 mib). Who is working on it? What state is it in? Speaking of which...I'm not quite sure why WGs have two documents...one for IPv6 and one for IPv4. Wouldn't there be cases where IPv6 and IPv4 were coexisting on the same LAN, so therefore there might be routers performing VRRP for both IPv6 and IPv4 simultaneously? I'd think it would be easier for an implementer if there were one spec, that told you how to do both simultaneously, since there also might be some interactions that would have to be thought about when doing both IPv6 and IPv4 simultaneously. Thanks... Radia _______________________________________________ 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 Mon Jun 23 15:45:56 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07511 for ; Mon, 23 Jun 2003 15:45:56 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5NJjSk06069 for vrrp-archive@odin.ietf.org; Mon, 23 Jun 2003 15:45:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UXFo-0001Zo-92 for vrrp-web-archive@optimus.ietf.org; Mon, 23 Jun 2003 15:45:28 -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 PAA07498 for ; Mon, 23 Jun 2003 15:45:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UXFm-0005EI-00 for vrrp-web-archive@ietf.org; Mon, 23 Jun 2003 15:45:26 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19UXFh-0005EB-00 for vrrp-web-archive@ietf.org; Mon, 23 Jun 2003 15:45:21 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UXFM-0001ZI-MQ; Mon, 23 Jun 2003 15:45:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UXER-0001Yt-Sx for vrrp@optimus.ietf.org; Mon, 23 Jun 2003 15:44:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07421 for ; Mon, 23 Jun 2003 15:44:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UXEQ-0005Dc-00 for vrrp@ietf.org; Mon, 23 Jun 2003 15:44:02 -0400 Received: from brmea-mail-2.sun.com ([192.18.98.43]) by ietf-mx with esmtp (Exim 4.12) id 19UXEE-0005DX-00 for vrrp@ietf.org; Mon, 23 Jun 2003 15:43:51 -0400 Received: from sydney.East.Sun.COM ([129.148.9.16]) by brmea-mail-2.sun.com (8.12.9/8.12.9) with ESMTP id h5NJhM7U021130 for ; Mon, 23 Jun 2003 13:43:22 -0600 (MDT) Received: from sr1-ubur-08 (sr1-ubur-08 [129.148.9.87]) by sydney.East.Sun.COM (8.11.7+Sun/8.11.7/ENSMAIL,v2.2) with SMTP id h5NJhMs00369 for ; Mon, 23 Jun 2003 15:43:22 -0400 (EDT) Message-Id: <200306231943.h5NJhMs00369@sydney.East.Sun.COM> Date: Mon, 23 Jun 2003 15:43:22 -0400 (EDT) From: Radia Perlman - Boston Center for Networking Reply-To: Radia Perlman - Boston Center for Networking To: vrrp@ietf.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: tW81A/9u/YMr79yeGsIW2g== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.5.3_06 SunOS 5.9 sun4u sparc Subject: [VRRP] Need agenda items for the IETF meeting Sender: vrrp-admin@ietf.org Errors-To: vrrp-admin@ietf.org X-BeenThere: vrrp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Virtual Router Redundancy Protocol List-Post: List-Help: List-Subscribe: , Please send ideas for things to talk about at the next IETF meeting. I'd prefer you "multicast" it to the vrrp list rather than unicasting to me and Mukesh, but if you're shy, feel free to just send it to us. Thanks, Radia _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Thu Jun 26 19:11:43 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26584 for ; Thu, 26 Jun 2003 19:11:43 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5QNBIV11734 for vrrp-archive@odin.ietf.org; Thu, 26 Jun 2003 19:11:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Vftd-00033B-UQ for vrrp-web-archive@optimus.ietf.org; Thu, 26 Jun 2003 19:11: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 TAA26571 for ; Thu, 26 Jun 2003 19:11:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Vfta-0006vA-00 for vrrp-web-archive@ietf.org; Thu, 26 Jun 2003 19:11:14 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19VftU-0006v5-00 for vrrp-web-archive@ietf.org; Thu, 26 Jun 2003 19:11:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VftN-00031u-6J; Thu, 26 Jun 2003 19:11:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VftE-00031Z-Bi for vrrp@optimus.ietf.org; Thu, 26 Jun 2003 19:10:52 -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 TAA26550 for ; Thu, 26 Jun 2003 19:10:32 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Vfsv-0006ur-00 for vrrp@ietf.org; Thu, 26 Jun 2003 19:10:34 -0400 Received: from brmea-mail-3.sun.com ([192.18.98.34]) by ietf-mx with esmtp (Exim 4.12) id 19Vfsk-0006uj-00 for vrrp@ietf.org; Thu, 26 Jun 2003 19:10:22 -0400 Received: from sydney.East.Sun.COM ([129.148.9.16]) by brmea-mail-3.sun.com (8.12.9/8.12.9) with ESMTP id h5QNA11J024041; Thu, 26 Jun 2003 17:10:01 -0600 (MDT) Received: from sr1-ubur-08 (sr1-ubur-08 [129.148.9.87]) by sydney.East.Sun.COM (8.11.7+Sun/8.11.7/ENSMAIL,v2.2) with SMTP id h5QNA0s02008; Thu, 26 Jun 2003 19:10:00 -0400 (EDT) Message-Id: <200306262310.h5QNA0s02008@sydney.East.Sun.COM> Date: Thu, 26 Jun 2003 19:10:00 -0400 (EDT) From: Radia Perlman - Boston Center for Networking Reply-To: Radia Perlman - Boston Center for Networking Subject: Re: [VRRP] Need agenda items for the IETF meeting To: Radia.Perlman@sun.com, vrrp@ietf.org, hottrw@nswc.navy.mil Cc: kodonog@titanic.nswc.navy.mil, dmarlow@titanic.nswc.navy.mil, bchappe@nswc.navy.mil, tplunke@titanic.nswc.navy.mil, CarmichaelLS@nswc.navy.mil MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: r11cAwwCQM1gk88SV0ujGg== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.5.3_06 SunOS 5.9 sun4u sparc Sender: vrrp-admin@ietf.org Errors-To: vrrp-admin@ietf.org X-BeenThere: vrrp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Virtual Router Redundancy Protocol List-Post: List-Help: List-Subscribe: , >>It would be nice to hear about proposals that would introduce >>sub-second timers to VRRP. Thank you for being the first to volunteer to be on the agenda. Can I put a name next to this topic, since you are not going to be there? Can that person do a presentation to lead off the discussion? How much time do you think would be appropriate? Thanks, Radia _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp From exim@www1.ietf.org Thu Jun 26 19:36:39 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27274 for ; Thu, 26 Jun 2003 19:36:38 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5QNaA920867 for vrrp-archive@odin.ietf.org; Thu, 26 Jun 2003 19:36:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VgHi-0005QU-OG for vrrp-web-archive@optimus.ietf.org; Thu, 26 Jun 2003 19:36: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 TAA27257 for ; Thu, 26 Jun 2003 19:36:06 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VgHg-00076g-00 for vrrp-web-archive@ietf.org; Thu, 26 Jun 2003 19:36:08 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19VgHb-00076d-00 for vrrp-web-archive@ietf.org; Thu, 26 Jun 2003 19:36:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VgHZ-0005HU-CG; Thu, 26 Jun 2003 19: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 19VgHY-0005HH-3T for vrrp@optimus.ietf.org; Thu, 26 Jun 2003 19:36:00 -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 TAA27254 for ; Thu, 26 Jun 2003 19:35:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VgHW-00076X-00 for vrrp@ietf.org; Thu, 26 Jun 2003 19:35:58 -0400 Received: from mailhost.iprg.nokia.com ([205.226.5.12]) by ietf-mx with esmtp (Exim 4.12) id 19VgHG-00076J-00 for vrrp@ietf.org; Thu, 26 Jun 2003 19:35:42 -0400 Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69]) by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id QAA04291; Thu, 26 Jun 2003 16:35:02 -0700 (PDT) Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h5QNZ1R11167; Thu, 26 Jun 2003 16:35:01 -0700 X-mProtect: <200306262335> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.12.76, claiming to be "spruce.iprg.nokia.com") by darkstar.iprg.nokia.com smtpdo4Xpt3; Thu, 26 Jun 2003 16:34:58 PDT Message-Id: <4.3.2.7.2.20030626163437.022bfb20@127.0.0.1> X-Sender: hinden@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 26 Jun 2003 16:34:52 -0700 To: Radia Perlman From: Bob Hinden Subject: Re: [VRRP] Need agenda items for the IETF meeting Cc: vrrp@ietf.org 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: , You can put me down to review the new VRRP drafts. I may get another update done, but if not we discuss the comments made on the list. Bob At 12:43 PM 6/23/2003, Radia Perlman - Boston Center for Networking wrote: >Please send ideas for things to talk about at the >next IETF meeting. I'd prefer you "multicast" >it to the vrrp list rather than unicasting to me >and Mukesh, but if you're shy, feel free to >just send it to us. > >Thanks, > >Radia > > >_______________________________________________ >vrrp mailing list >vrrp@ietf.org >https://www1.ietf.org/mailman/listinfo/vrrp _______________________________________________ vrrp mailing list vrrp@ietf.org https://www1.ietf.org/mailman/listinfo/vrrp