From VRRP-owner@drcoffsite.com Tue Jan 4 21:59:13 2000 Received: from drcoffsite.com (dns1.drcoffsite.com [216.177.1.130]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13100 for ; Tue, 4 Jan 2000 21:59:11 -0500 (EST) Received: from perigee.net [216.189.61.120] by drcoffsite.com (SMTPD32-5.05) id A29C2B3A0212; Tue, 04 Jan 2000 21:55:24 -0500 From: tsmit10@perigeen.net Reply-To: tsmit10@perigeen.net To: tsmit10@perigeen.net Subject: need help? Message-Id: <200001042155375.SM00071@perigee.net> Precedence: bulk Sender: VRRP-owner@drcoffsite.com Date: Tue, 4 Jan 2000 21:57:13 -0500 ********************************************************** Your email address was collected from a list of Internet professionals. To be removed from this list and any future mailings, please reply with the subject "Remove". We will automatically block you from future mailings. ********************************************************** Need help finding the right place to host your web site? Tired of searching through thousands of companies all claiming to be the best? We personally believe your time should be spent doing what you do best...running your business! Visit our site today at http://www.amtinternet.com/webhosting We offer a complete guide for how to choose the right hosting service. We tell you what to look for, and what to avoid. In addition, we have compiled a list of services that consistently rank as the best! Be sure to check out the rest of our site for... *Your FREE search engine site ranking report! *The best resources for setting up merchant accounts to accept online credit card orders! *The most popular web site design and publishing tools! *E-Marketing reources *Much more... Visit our site today at http://www.amtinternet.com/webhosting.htm From VRRP-owner@drcoffsite.com Thu Jan 6 06:45:56 2000 Received: from drcoffsite.com (dns1.drcoffsite.com [216.177.1.130]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07207 for ; Thu, 6 Jan 2000 06:45:55 -0500 (EST) Received: from ietf.org [132.151.1.176] by drcoffsite.com with ESMTP (SMTPD32-5.05) id AEC842803F2; Thu, 06 Jan 2000 06:38:48 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07129; Thu, 6 Jan 2000 06:40:48 -0500 (EST) Message-Id: <200001061140.GAA07129@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: vrrp@drcoffsite.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-vrrp-spec-v2-05.txt Date: Thu, 06 Jan 2000 06:40:47 -0500 X-Sender: nsyracus@cnri.reston.va.us Precedence: bulk Sender: VRRP-owner@drcoffsite.com --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Virtual Router Redundancy Protocol Working Group of the IETF. Title : Virtual Router Redundancy Protocol Author(s) : S. Knight, D. Weaver, D. Whipple, B. Hinden, D. Mitzel, P. Hunt, P. Higginson, M. Shand, A. Lindem Filename : draft-ietf-vrrp-spec-v2-05.txt Pages : 32 Date : 05-Jan-00 This memo defines the Virtual Router Redundancy Protocol (VRRP). VRRP specifies an election protocol that dynamically assigns responsibility for a virtual router to one of the VRRP routers on a LAN. The VRRP router controlling the IP address(es) associated with a virtual router is called the Master, and forwards packets sent to these IP addresses. The election process provides dynamic fail over in the forwarding responsibility should the Master become unavailable. This allows any of the virtual router IP addresses on the LAN to be used as the default first hop router by end-hosts. The advantage gained from using VRRP is a higher availability default path without requiring configuration of dynamic routing or router discovery protocols on every end-host. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-vrrp-spec-v2-05.txt Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-vrrp-spec-v2-05.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-vrrp-spec-v2-05.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20000105150528.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-vrrp-spec-v2-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-vrrp-spec-v2-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20000105150528.I-D@ietf.org> --OtherAccess-- --NextPart-- From VRRP-owner@drcoffsite.com Thu Jan 6 13:26:16 2000 Received: from drcoffsite.com (dns1.drcoffsite.com [216.177.1.130]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18961 for ; Thu, 6 Jan 2000 13:26:14 -0500 (EST) Received: from sol.extremenetworks.com [216.52.8.2] by drcoffsite.com with ESMTP (SMTPD32-5.05) id AD45176404CC; Thu, 06 Jan 2000 13:21:57 -0500 Received: by SOL with Internet Mail Service (5.5.2650.21) id ; Thu, 6 Jan 2000 10:24:06 -0800 Message-ID: <808F64DDB492D3119D3C00508B5D8D733EC396@SOL> From: Andrew Smith To: vrrp@drcoffsite.com, "'hinden@iprg.nokia.com'" Subject: RE: I-D ACTION:draft-ietf-vrrp-spec-v2-05.txt Date: Thu, 6 Jan 2000 10:24:03 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Precedence: bulk Sender: VRRP-owner@drcoffsite.com Could someone please just clarify the current work items for this WG? Looking at this new draft it seems like these are just maintenance changes with no new functionality, right? If not, could someone please summarise the new functionality. I think the WG charter needs to be updated to cover this maintenance activity, regardless. Thanks, Andrew > -----Original Message----- > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > Sent: Thursday, January 06, 2000 3:41 AM > Cc: vrrp@drcoffsite.com > Subject: I-D ACTION:draft-ietf-vrrp-spec-v2-05.txt > > > A New Internet-Draft is available from the on-line > Internet-Drafts directories. > This draft is a work item of the Virtual Router Redundancy > Protocol Working Group of the IETF. > > Title : Virtual Router Redundancy Protocol > Author(s) : S. Knight, D. Weaver, D. Whipple, B. > Hinden, > D. Mitzel, P. Hunt, P. Higginson, M. Shand, > A. Lindem > Filename : draft-ietf-vrrp-spec-v2-05.txt > Pages : 32 > Date : 05-Jan-00 > > This memo defines the Virtual Router Redundancy Protocol (VRRP). > VRRP specifies an election protocol that dynamically assigns > responsibility for a virtual router to one of the VRRP routers on a > LAN. The VRRP router controlling the IP address(es) associated with > a virtual router is called the Master, and forwards packets sent to > these IP addresses. The election process provides dynamic fail over > in the forwarding responsibility should the Master become > unavailable. This allows any of the virtual router IP addresses on > the LAN to be used as the default first hop router by end-hosts. The > advantage gained from using VRRP is a higher availability default > path without requiring configuration of dynamic routing or router > discovery protocols on every end-host. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-vrrp-spec-v2-05.txt > > Internet-Drafts are also available by anonymous FTP. Login > with the username > "anonymous" and a password of your e-mail address. After logging in, > type "cd internet-drafts" and then > "get draft-ietf-vrrp-spec-v2-05.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-vrrp-spec-v2-05.txt". > > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant > mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > From VRRP-owner@drcoffsite.com Thu Jan 6 13:54:39 2000 Received: from drcoffsite.com (dns1.drcoffsite.com [216.177.1.130]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19675 for ; Thu, 6 Jan 2000 13:54:37 -0500 (EST) Received: from mailhost.iprg.nokia.com [205.226.5.12] by drcoffsite.com with ESMTP (SMTPD32-5.05) id A43E1B1804CC; Thu, 06 Jan 2000 13:51:42 -0500 Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69]) by mailhost.iprg.nokia.com (8.8.8/8.6.10) with ESMTP id KAA13801; Thu, 6 Jan 2000 10:53:38 -0800 (PST) Received: (from root@localhost) by darkstar.iprg.nokia.com (8.9.3/8.9.3-VIRSCAN) id KAA06135; Thu, 6 Jan 2000 10:53:33 -0800 X-Virus-Scanned: Thu, 6 Jan 2000 10:53:33 -0800 Nokia Silicon Valley AntiVirus Appliance Received: from (spruce.iprg.nokia.com [205.226.1.63]) by darkstar.iprg.nokia.com SMTP/WTS (12.69) xma005689; Thu, 6 Jan 00 10:53:20 -0800 Message-Id: <4.2.2.20000106104909.03e23950@mailhost.iprg.nokia.com> X-Sender: hinden@mailhost.iprg.nokia.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 06 Jan 2000 10:53:09 -0800 To: Andrew Smith From: Bob Hinden Subject: RE: I-D ACTION:draft-ietf-vrrp-spec-v2-05.txt Cc: vrrp@drcoffsite.com, "'hinden@iprg.nokia.com'" In-Reply-To: <808F64DDB492D3119D3C00508B5D8D733EC396@SOL> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Precedence: bulk Sender: VRRP-owner@drcoffsite.com Andrew, The recent updates to the VRRP spec are part of the process of moving it to Draft Standard. They are not protocol changes. The new draft updates the security considerations section per the suggestions in . Bob At 10:24 AM 1/6/00 -0800, Andrew Smith wrote: >Could someone please just clarify the current work items for this WG? >Looking at this new draft it seems like these are just maintenance changes >with no new functionality, right? If not, could someone please summarise the >new functionality. I think the WG charter needs to be updated to cover this >maintenance activity, regardless. From VRRP-owner@drcoffsite.com Fri Jan 7 15:38:48 2000 Received: from drcoffsite.com (dns1.drcoffsite.com [216.177.1.130]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26834 for ; Fri, 7 Jan 2000 15:38:47 -0500 (EST) Received: from rsvp.NE.3Com.COM [151.104.25.98] by drcoffsite.com with ESMTP (SMTPD32-5.05) id AE11BF0D004E; Fri, 07 Jan 2000 15:35:29 -0500 Received: from usboxmta.ne.3com.com (usboxmta.NE.3Com.COM [151.104.25.34]) by rsvp.NE.3Com.COM (Pro-8.9.3/Pro-8.9.3) with SMTP id PAA18715 for ; Fri, 7 Jan 2000 15:37:26 -0500 (EST) Received: by usboxmta.ne.3com.com(Lotus SMTP MTA v1.1 (385.6 5-6-1997)) id 8525685F.0073A804 ; Fri, 7 Jan 2000 16:03:16 -0500 X-Lotus-FromDomain: 3COM From: Richard_England@ne.3com.com To: vrrp@drcoffsite.com Message-ID: <8525685F.0070168A.00@usboxmta.ne.3com.com> Date: Fri, 7 Jan 2000 15:41:06 -0500 Mime-Version: 1.0 Content-type: text/plain; charset=US-ASCII Precedence: bulk Sender: VRRP-owner@drcoffsite.com The index for a VrrpOperEntry has two parts to it, the vrid and the ifIndex. If an "unsigned integer" ( 32 bits ) is used to store the index ( both the vrid and ifIndex), the ifIndex is limited to 24 bits, since the vrid can be (1-255). Can anybody tell me if this would be a proper implementation? Thanks, Rick England From VRRP-owner@drcoffsite.com Fri Jan 7 18:12:54 2000 Received: from drcoffsite.com (dns1.drcoffsite.com [216.177.1.130]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28898 for ; Fri, 7 Jan 2000 18:12:51 -0500 (EST) Received: from mailhost.iprg.nokia.com [205.226.5.12] by drcoffsite.com with ESMTP (SMTPD32-5.05) id A21E590512; Fri, 07 Jan 2000 18:09:18 -0500 Received: from mustang.iprg.nokia.com (mustang.iprg.nokia.com [205.226.1.196]) by mailhost.iprg.nokia.com (8.8.8/8.6.10) with ESMTP id PAA29148; Fri, 7 Jan 2000 15:11:14 -0800 (PST) Message-Id: <200001072311.PAA29148@mailhost.iprg.nokia.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Richard_England@ne.3com.com cc: vrrp@drcoffsite.com In-reply-to: Your message of "Fri, 07 Jan 2000 15:41:06 EST." <8525685F.0070168A.00@usboxmta.ne.3com.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 Jan 2000 15:11:13 -0800 From: "Danny J. Mitzel" Precedence: bulk Sender: VRRP-owner@drcoffsite.com On Friday, January 07, 2000 at 15:41 EST, Richard_England@ne.3com.com writes: >> The index for a VrrpOperEntry has two parts to it, the vrid and the >> ifIndex. If an "unsigned integer" ( 32 bits ) is used to store the index >> ( both the vrid and ifIndex), the ifIndex is limited to 24 bits, since the >> vrid can be (1-255). Can anybody tell me if this would be a proper >> implementation? internal to your router implementation, if 24 bits is sufficient to represent an interface index and you want to use a single 32 bit integer as key/index into your table then I think you're free to do that. however as the INDEX of an SNMP MIB table I believe these are treated and encoded as two objects. the SMI document [rfc2578] should discuss how to map each of the objects to form its portion of the instance identifier (both the ifIndex and VrId are underlying integer-valued). once the instance identifier is formed then things proceed as normal: assign OID as the name VarBind in some SNMP PDU [rfc1905] and encode/serialize for transmission [ISO ASN.1 BER]. danny From VRRP-owner@drcoffsite.com Sun Jan 9 16:20:20 2000 Received: from drcoffsite.com (dns1.drcoffsite.com [216.177.1.130]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10285 for ; Sun, 9 Jan 2000 16:20:20 -0500 (EST) Received: from sourcenet.org [209.214.98.110] by drcoffsite.com (SMTPD32-5.05) id AAE12AD03BA; Sun, 09 Jan 2000 16:17:21 -0500 From: Subject: Wishing you a Happy New Year Date: Sun, 9 Jan 2000 16:25:02 Message-Id: <244.807713.831693@sourcenet.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Precedence: bulk Sender: VRRP-owner@drcoffsite.com To be removed from this mailing list immediately press reply and enter REMOVE on the subject line. Would you like to be able to buy Computers and Software at wholesale? At below what the stores Pay? Reply with "MORE INFO" in the subject field If you are a reseller and would like information on paying what the distributors pay then Reply with Reseller in the subject field. If you have computer products you need to sell then email your details From VRRP-owner@drcoffsite.com Tue Jan 11 07:19:07 2000 Received: from drcoffsite.com (dns1.drcoffsite.com [216.177.1.130]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04819 for ; Tue, 11 Jan 2000 07:19:06 -0500 (EST) Received: from smtp1.cluster.oleane.net [195.25.12.16] by drcoffsite.com with ESMTP (SMTPD32-5.05) id AEB834602F4; Tue, 11 Jan 2000 07:14:48 -0500 Received: from oleane (dyn-1-1-205.Vin.dialup.oleane.fr [195.25.4.205]) by smtp1.cluster.oleane.net with SMTP id NAA46002; Tue, 11 Jan 2000 13:15:58 +0100 (CET) Message-ID: <001b01bf5c2d$41e873e0$0401a8c0@oleane.com> From: "Peter Lewis" To: Subject: Cellular Internet, Call for Paper Date: Tue, 11 Jan 2000 13:13:22 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0018_01BF5C35.A2B8B7E0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Precedence: bulk Sender: VRRP-owner@drcoffsite.com This is a multi-part message in MIME format. ------=_NextPart_000_0018_01BF5C35.A2B8B7E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Cellular Internet: The Micro-Mobility Approach The micro-mobility concept is the most recent and promising approach = proposed to add mobility to the Internet and packet data services to = third generation cellular systems. =20 A CFP is available at:=20 http://www.upperside.fr/baipcn.htm ------=_NextPart_000_0018_01BF5C35.A2B8B7E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Cellular Internet: The = Micro-Mobility=20 Approach

The micro-mobility concept is the most recent and = promising=20 approach proposed to add mobility to the Internet and packet data = services to=20 third generation cellular systems.
 
A CFP is available at:
http://www.upperside.fr/baipc= n.htm
------=_NextPart_000_0018_01BF5C35.A2B8B7E0-- From VRRP-owner@drcoffsite.com Tue Jan 11 11:30:04 2000 Received: from drcoffsite.com (dns1.drcoffsite.com [216.177.1.130]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14481 for ; Tue, 11 Jan 2000 11:30:03 -0500 (EST) Received: from seattle.3com.com [129.213.128.97] by drcoffsite.com with ESMTP (SMTPD32-5.05) id A9E04E50256; Tue, 11 Jan 2000 11:27:12 -0500 Received: from new-york.3com.com (new-york.3com.com [129.213.157.12]) by seattle.3com.com (8.8.8/8.8.8) with ESMTP id IAA00955; Tue, 11 Jan 2000 08:29:06 -0800 (PST) Received: from chicago.nsd.3com.com (chicago.nsd.3com.com [129.213.157.11]) by new-york.3com.com (8.8.8/8.8.8) with ESMTP id IAA29659; Tue, 11 Jan 2000 08:29:05 -0800 (PST) Received: from fubar.nsd.3com.com (fubar.nsd.3com.com [129.213.16.41]) by chicago.nsd.3com.com (8.8.8/8.8.8) with ESMTP id IAA12416; Tue, 11 Jan 2000 08:29:04 -0800 (PST) From: Brian Jewell Received: (from bjewell@localhost) by fubar.nsd.3com.com (8.8.2/8.8.5) id IAA11196; Tue, 11 Jan 2000 08:29:03 -0800 (PST) Date: Tue, 11 Jan 2000 08:29:03 -0800 (PST) Message-Id: <200001111629.IAA11196@fubar.nsd.3com.com> To: IfatG@radware.co.il Subject: Questions (and answers) about the VRRP MIB Cc: vrrp@drcoffsite.com, bjewell@ewd.3Com.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-MD5: +GbWZsrBEqQ3SWLRHPXEPA== Precedence: bulk Sender: VRRP-owner@drcoffsite.com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA14481 Hi Ifat, re: questions about the "vrrpOperAuthKey" object in the VRRP MIB: you wrote: > What I meant was that in the ADV. packet there are 4 octets reserved for authentication data. (Actualy 2 four octets for two authentication data.) > So how come that the authentication key in the MIB can be up to 16 octets? Aren't authentication key and authentication data the same thing? ============= I think the confusion arises from the fact that any AH data would be carried in the IP packet separate from the VRRP advertisement packet. Thus, if AH is used to provide security for VRRP, the mechanisms that make it work are the ones provided by IPSec - not anything provided by the VRRP implementation. So there would be no AH-related data in the advertisement packets - it would all be present in the IP packet carrying the advertisement packet and would be processed prior to reaching the VRRP router. So, in this area, the VRRP MIB mainly functions to allow configuration of AH security if a user chooses to do so. Also, check section 5.3.10 of the latest VRRP Spec. Draft. It indicates that the Authentication Data field is used for "simple text authentication" only. In reality, a user would probably use an IPSec MIB (when one becomes a standard) to configure AH security between to VRRP routers, and the vrrpOperAuthKey object provides a redundant means to set the key. The VRRP RFC does not provide much information in the area of security. I think efforts are underway to enhance this section of the RFC. -Brian > Hello again, > Concerning my former question: > 3) The definition of vrrpOperAuthKey ( page 19) states that the key length can > be up to 16 octets, but isn't it true that in the Adv. packet there's space only > for 4 octets( according to RFC 2338 section 5.1 )? > > What I meant was that in the ADV. packet there are 4 octets reserved for authentication data. (Actualy 2 four octets for two authentication data.) > So how come that the authentication key in the MIB can be up to 16 octets? Aren't authentication key and authentication data the same thing? > Thanks, > Ifat. > > > -----Original Message----- > > From: Brian Jewell [SMTP:bjewell@3com.com] > > Sent: > ו 07 ינואר 2000 17:37 > > To: DoronS@radware.com; IfatG@radware.co.il > > Cc: bjewell@ewd.3Com.com > > Subject: Re: vrrp mib definitaions > > > > Hi Ifat, > > > > Here's the answers to your questions: > > > > 1) and 2) Actually, VRID does not uniquely identify a VR. In Section > > 3.0, RFC 2338 indicates that a VRID can be re-used, as long as > > it is used on a different LAN - which essentially means a > > different IfIndex. So, to uniquely identify rows in the > > tables (or to uniquely identify a virtual router), both the VRID and > > the IfIndex is required. > > > > 3) vrrpOperAuthKey can be set via SNMP. It is never contained in a VRRP > > advertisement. I think this is your concern, but let me know if > > I'm wrong. > > > > 4) The "vrrpOperAuthKey" always returns a NULL octet string when read > > for security; Don't want SNMP managers to be able to read this key. > > > > Hope this answers your questions, but let me know if you need more information. > > I would appreciate maybe being able to use you as a reference as the MIB moves > > toward draft standard and there is a call for people who have implemented the > > MIB. > > > > -Brian > > > > > > > Hello, > > > > > > I'm about to implement the VRRP, and have some questions concerning the MIB > > definitaions in draft-ietf-vrrp-mib-09.txt: > > > > > > 1) Why is ifIndex a part of the index of vrrpOperEntry ( Doesn't vrrpOperVrId > > define the entry uniqly ) ? > > > > > > 2) Why is ifIndex a part of the index of vrrpAssoIpAddrEntry ( Don't > > vrrpOperVrId+vrrpAssoIpAddr define the entry uniqly ) ? > > > > > > 3) The definition of vrrpOperAuthKey ( page 19) states that the key length can > > be up to 16 octets, but isn't it true that in the Adv. packet there's space only > > for 4 octets( according to RFC 2338 section 5.1 )? > > > > > > 4) This same definition of vrrpOperAuthKey ( page 19) states that "When read, > > vrrpOperAuthKey always returns an Octet String of length zero." - Do you mean by > > that that in the returned Octet String the value in the length field will > > not match the real length of the string in the string field? > > > > > > Thanks a lot, > > > Ifat Gaabay. > > > > From VRRP-owner@drcoffsite.com Sun Jan 16 00:41:16 2000 Received: from drcoffsite.com (dns1.drcoffsite.com [216.177.1.130]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19023 for ; Sun, 16 Jan 2000 00:41:15 -0500 (EST) Received: from freepager [216.126.180.146] by drcoffsite.com (SMTPD32-5.05) id A82B24F03C2; Sun, 16 Jan 2000 00:33:31 -0500 From: sjgsjks@cljkwdsmx.heim.at Content-Type: text/plain; charset="iso-8859-1" Message-ID: To: vrrp@drcoffsite.com Date: Sun, 14 Nov 1999 21:36:05 -0800 Subject: Get A FREE Pager-No Hidden Costs -shhryrsab Precedence: bulk Sender: VRRP-owner@drcoffsite.com FREE PAGER Get a Brand New Satellite Pager for FREE! No long term contract No activation fee No big prepayment of airtime No credit check Put Free pagers on your kids Give one to your wife Paging America is going to give you a top of the line full featured pager in your choice of color for FREE. This top viewable display pager is one of the smallest and lightest pagers on the market today and holds up to 32 numeric messages, has 9 music alerts or silent vibration mode, flex technology which provides three times the battery life, message time and day stamping and smart alarm so you can set a daily or weekly reminder. This pager comes in black, teal (green) and blue. All we ask before we ship you your Free pager is for you to allow us to provide the airtime for you. There is no long term contract or credit check. Airtime is month to month and can be cancelled at any time. Airtime for this pager is only $9.95 per month billed monthly or only $8.95 per month if we bill your credit card or checking account each month. Just call the toll free number and we'll ship your Free pager to you immediately in your choice of color already programmed with a local telephone number for your town. For immediate delivery call Paging America 24 hours a day at 800-443-3122 From VRRP-owner@drcoffsite.com Tue Jan 18 08:30:44 2000 Received: from drcoffsite.com (dns1.drcoffsite.com [216.177.1.130]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29061 for ; Tue, 18 Jan 2000 08:30:42 -0500 (EST) Received: from sih-un49.unigate.co.uk [192.189.23.1] by drcoffsite.com with ESMTP (SMTPD32-5.05) id AA28D5D019C; Tue, 18 Jan 2000 08:27:04 -0500 Received: from 192.189.23.1 by sih-un49.unigate.co.uk (8.8.8/4.03) id NAA39894; Tue, 18 Jan 2000 13:19:20 GMT From: Publishing@mx-30.fsnet.co.uk Message-Id: <200001181319.NAA39894@sih-un49.unigate.co.uk> To: Publishing@yahoo.com Date: Tue, 18 Jan 00 03:55:30 EST Subject: Publishing Company for Sale! Reply-To: Remove-it-ok@bigfoot.com Precedence: bulk Sender: VRRP-owner@drcoffsite.com See information about Free Credit Application Below! My Multi-Million Dollar Publishing Company ONLY $149 Free Pre-Approved Merchant Account Application with Order!! To Start Your Business Out Right!! If you ever wanted "the easy way out" to make a lot of money with a business of your own.... Here is the EASIEST WAY TO START! I'm writing this letter to let you in on something that'll blow you away. What I'm about to present is something I've never done before...something that I'll never do again.... So PAY ATTENTION! For the past few years...I've have been running ads in newspapers & magazines, by direct mail, and throughout the internet. These ads were always small and very cheap... On these ads, we have been selling little manuals. These manuals have sold for anywhere between $10 to $99 each. We always ran different ads for each manual we were selling. I like selling information because NOBODY can put a price on it...ESPECIALLY when it is your own...The Sky is the Limit! Plus it is very cheap to reproduce How-To manuals. It costs between 40 cents and $3 to print the entire print manuals and around 35 cents to copy the manuals on disk. AND you can sell them for up to $99 each. That is one hell of a markup! These manuals tell you how to get a car with no money down and no credit...another one tells you how to avoid taxes by depositing income offshore...now you may not be interested in saving money by going offshore...but believe me....there are MILLIONS OF PEOPLE WHO DO...and they are willing to pay me to teach them!!! Well this is where the unbelievable offer comes in...I hope you are sitting down for this one...because this is a once in a lifetime chance for you. I do not know of an easier way to become financially independent...In fact THERE IS NO EASIER WAY!!! The next few paragraphs will reveal everything to you. I am willing to sell you my entire informational product line with FULL REPRINT RIGHTS and complete step-by-step instructions on how to start your mail order information business with very little money. Remember, these are PROVEN WINNERS. If you are stumped on something to sell or if you are having trouble writing a good ad, I have also included an entire book on disk to help you produce KILLER ads! This entire package which I call a Publishing Company in a Box will come on 1 CD containing over 2000 'Hot-Selling' Books, Reports And Manuals ready to print and sell, Sell, SELL! It also will come with a signed letter giving YOU FULL REPRINT RIGHTS allowing you to sell them for as much as you want and however you want. You Can even sell the entire kit to someone else to resale on their own! You also receive copies of KILLER ads which can fill your mailbox with cash! I am not even going to ask you for any of the money either... What you make is yours to keep . In fact...you get to make a ton of money on these manuals for as long as you wish...and you will never have to pay me another red cent in royalties! I am even going to print out and prepare our #1 selling report which contains the secrets of starting and operating your own million dollar mail order business on a shoestring budget so that you will be able to take it down to your local copy shop and be ready to sell it the same day you have received it. Watch out though - one individual is making $30,000 a month on this report alone! (Why - Because you can also include a special report On How to Write Order Pulling Ads that practically force people to whip out their checkbooks and order!) Note: THIS REPORT IS INCLUDED! All I ask for is...$149 and I will include FREE Priority Mail Shipping! Yes, I said $149. There are no zeros missing. Plus if you order before Jan 24, 2000 I will include 4 extra special bonuses... Bonus #1 - "Search Engine Magic" on disk. This report will shoot your web site up to the top of the search engine listings. Other web advertisers are selling this manual for $99 by itself - But I will give it to you for FREE with this package. Bonus #2 - The report "How to Make at least $1,600 a week online...Starting Now!" which is taking the internet by storm will be included absolutely FREE! Bonus #3 - I will include special details about a secret source for creating Your own direct mail leads and how you can get your own mail order business up and running for just a few bucks! Bonus #4 - I also will include a pre-approved application for a merchant account for your business benefit. Taking credit cards will increase your business up to 100%. The normal $195 application fee will be waved with this pre-approved application. But there is one drawback... I am sending this ad to 10,000 other people...and I will only allow 50 kits to be sold. It wouldn't make much sense if I sold this kit to 1,000 or 2,000 people...The market would be saturated with these same manuals... and I don't want to do that. To make sure that the people in this offer get the same results I have...ONLY 50 people can have it for $149.00! Chances are, I will get all 50 within a week's time. So if this is something you are interested in...RUSH me a check or money order for $149.00 TODAY to insure your future business. But, even if you decide to pass this up...Don't sweat it. It's not like I am going to be mad or anything like that. I know I will get my 50 order limit really fast. And anyone who gets their check into me late... I will simply send it back. For only $149.00, I am going to let you have the easiest money you will ever make. The manuals are written, the ads are presented, the advertising plan is laid out, and all you have to do is print them out for pennies and place the ads. Do it today! Rush me your payment of $149.00 right now...and get your very own MILLION DOLLAR publishing company going! You can start with one or two manuals...even the day you receive the package...and then expand to include ALL of them! For $149.00, you have everything you need to make a killing with your very own business. If you want to make real money - then this offer is for you! "I took the report "Search Engine Magic" and sold over 50 copies on disk within 2 weeks! They sold for $99 and I was able to copy them for under 50 cents each. Wait till I start marketing the other products included in this line!!!" Joe Fisher - Internet Marketer To rush order this "MILLION DOLLAR Publishing Company in a Box" simply fill out the order form below and fax it to our 24 hour order line at: FAX ORDER LINE: 1 (212) 504-8032 Regular Mail to: Financial Systems P.O. Box 301 Orange, Ma 01364 ORDER FORM -------------------------------------------------------------- Please send to: Your Name_____________________________________________ Your Address__________________________________________ Your City______________________________________________ State / Zip_____________________________________________ Your Country___________________________________________ Phone #: _____________________________________________ (For problems with your order only. No salesmen will call.) Email Address________________________________________ We Accept Checks or Money Orders along with all Major Credit Cards including Visa, MasterCard, American Express and Discover. (NOTE - We only ship to the address listed on the credit card) (Please Fill Out Below Section and Make sure that the above name and address are listed as it appears on the card) for $149.00 Credit Card Number:________________________________ Expiration Date:___________________________ Signature:_________________________ Date:____________________ [ ] YES! Please rush my Publishing Company in a Box. I understand I have FULL REPRINT Rights and can sell any of the items for whatever price I desire, even the entire kit. [ ] DOUBLE YES! I am ordering before Jan 24, 2000! Please include the extra special bonuses! * Please check one of the following payment options: [ ] I am faxing a check (Do not send original, we will make a draft from the faxed check) [ ] I am faxing or mailing my credit card number. (Note your card will be charged for $149.00 and we only ship to the address on the card) [ ] I am enclosing a check or money order for $149.00! Note - If ordering outside continental US, please add $5 to S&H P.S. Don't forget you will receive 2,000 Manuals, Books, and Reports (Some of which are up to 200 pages each)...all for $149...You have full reprint and resale rights to make as much money as you want without ever paying any royalties whatsoever! * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * You have been carefully selected to receive the following as a person obviously interested in this subject based upon your previous internet postings, or visits to one of our affiliate web sites. If you have received this message in error, hit Reply with the word unsubscribe in the subject. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * From VRRP-owner@drcoffsite.com Fri Jan 28 10:17:50 2000 Received: from drcoffsite.com (dns1.drcoffsite.com [216.177.1.130]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14692 for ; Fri, 28 Jan 2000 10:17:49 -0500 (EST) Received: from ietf.org [132.151.1.176] by drcoffsite.com with ESMTP (SMTPD32-5.05) id A250203805D4; Fri, 28 Jan 2000 10:14:24 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14594; Fri, 28 Jan 2000 10:15:55 -0500 (EST) Message-Id: <200001281515.KAA14594@ietf.org> To: IETF-Announce: ; Cc: RFC Editor Cc: Internet Architecture Board Cc: vrrp@drcoffsite.com From: The IESG Subject: Protocol Action: Definitions of Managed Objects for the Virtual Router Redundancy Protocol to Proposed Standard Date: Fri, 28 Jan 2000 10:15:55 -0500 X-Sender: scoya@cnri.reston.va.us Precedence: bulk Sender: VRRP-owner@drcoffsite.com The IESG has approved the Internet-Draft 'Definitions of Managed Objects for the Virtual Router Redundancy Protocol' as a Proposed Standard. This document is the product of the Virtual Router Redundancy Protocol Working Group. The IESG contact persons are David Oran and Rob Coltun. Technical Summary This specification defines an extension to the Management Information Base (MIB) for use with SNMP-based network management. In particular, it defines objects for configuring, monitoring, and controlling routers that employ the Virtual Router Redundancy Protocol (VRRP) specified in RFC 2338. Working Group Summary The working group supports advancement of this draft. There was no significant dissent. Protocol Quality This draft has been reviewed by Bert Wijnen and Rob Coltun for the IESG. There are a number of implementations. Note to RFC Editor: The IESG respectfully requests the following changes be made: - On page 19 OLD: vrrpOperAuthType OBJECT-TYPE SYNTAX INTEGER { noAuthentication(1), -- VRRP protocol exchanges are not -- authenticated. simpleTextPassword(2), -- Exchanges are authenticated by a -- clear text password. ipAuthenticationHeader(3) -- Exchanges are authenticated using -- the IP authentication header. } MAX-ACCESS read-create STATUS current DESCRIPTION "Authentication type used for VRRP protocol exchanges between virtual routers. This value of this object is the same for a given ifIndex." DEFVAL { noAuthentication } ::= { vrrpOperEntry 9 } NEW: vrrpOperAuthType OBJECT-TYPE SYNTAX INTEGER { noAuthentication(1), -- VRRP protocol exchanges are not -- authenticated. simpleTextPassword(2), -- Exchanges are authenticated by a -- clear text password. ipAuthenticationHeader(3) -- Exchanges are authenticated using -- the IP authentication header. } MAX-ACCESS read-create STATUS current DESCRIPTION "Authentication type used for VRRP protocol exchanges between virtual routers. This value of this object is the same for a given ifIndex. New enumerations to this list can only be added via a new RFC on the standards track." DEFVAL { noAuthentication } ::= { vrrpOperEntry 9 } - On page 20 OLD: vrrpOperProtocol OBJECT-TYPE SYNTAX INTEGER { ip (1), bridge (2), decnet (3), other (4) } MAX-ACCESS read-create STATUS current DESCRIPTION "The particular protocol being controlled by this Virtual Router." DEFVAL { ip } ::= { vrrpOperEntry 14 } NEW: vrrpOperProtocol OBJECT-TYPE SYNTAX INTEGER { ip (1), bridge (2), decnet (3), other (4) } MAX-ACCESS read-create STATUS current DESCRIPTION "The particular protocol being controlled by this Virtual Router. New enumerations to this list can only be added via a new RFC on the standards track." DEFVAL { ip } ::= { vrrpOperEntry 14 }