From owner-ietf-radius@livingston.com Tue Dec 1 10:48:40 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id KAA17671 for ; Tue, 1 Dec 1998 10:48:39 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id HAA27771; Tue, 1 Dec 1998 07:40:35 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id HAA29994 for ietf-radius-outgoing; Tue, 1 Dec 1998 07:37:39 -0800 (PST) Message-Id: <199812011541.KAA15367@beowulf.cryptocard.com> From: Alan DeKok To: ietf-radius@livingston.com Subject: Re: (radius) Vendor Specific Attributes In-reply-to: Your message of "Mon, 30 Nov 1998 17:07:41 CST." Date: Tue, 01 Dec 1998 10:41:08 -0500 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Alan DeKok "Varghese, Joe" wrote: > Our project needs to use attributes that are not defined in the Radius > specification for authentication, and apparantly the correct place for this > is under vendor-specific attributes. Yes. > However, I'm confused about *how* to place them here and still conform to > the specification. Namely, > > * For vendor-id, the RFC says to have the high-order byte be 0 and the low > order 3 bytes be the SMI code for the vendor. I looked at the Assigned > Numbers RFC, and the code with the highest value is less than 1100. Does > this mean you take the binary of the code value and pad the left with zeros? Take the SMI code, and write it as an integer in network byte order. As long as it's less than 0x00ffffff, you'll satisfy the RFC requirements. > *My understanding is that the vendor-id code is used only to make your > product/application be general purpose ... so, if our Radius client/server > is running in a controlled environment, this code is not that important. Is > this correct? Probably. For situations where you don't have an assigned SMI code, it's probably better to use '0', which is reserved. > * Surprisingly, I didn't see a code for Lucent Technologies. Did I miss it? > I made a request for a code, but was wondering if I did the right thing or > not ... ftp://ftp.isi.edu/in-notes/iana/assignments/enterprise-numbers 1751 Lucent Technologies Richard Bantel richard.bantel@lucent.com Alan DeKok. - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Fri Dec 4 14:19:24 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00759 for ; Fri, 4 Dec 1998 14:19:23 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id LAA06481; Fri, 4 Dec 1998 11:12:35 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id LAA21729 for ietf-radius-outgoing; Fri, 4 Dec 1998 11:13:50 -0800 (PST) From: Pat.Calhoun@eng.sun.com (Patrice Calhoun) Message-Id: <199812041910.LAA09681@hsmpka.eng.sun.com> Date: Fri, 4 Dec 1998 11:03:58 -0800 To: "Indranil Bagchi" , "'ietf-radius@livingston.com'" Subject: Re: (radius) TACACS X-Mailer: Sun NetMail 2.2.2 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Pat.Calhoun@eng.sun.com (Patrice Calhoun) Content-Transfer-Encoding: 7bit A best effort of XTACACS is specified in RFC 1492 while TACACS+ is specified in draft-grant-tacacs-02.txt. TACACS was specified in BBN Tech Memo CC-0045, and I doubt that you'll ever be able to get your hands on it :( PatC > >I am looking for specifications/source code for TACACS/XTACACS/TACACS+. >I would also like to find information on Kerberos and Kerberos CHAP >authentication. Any inputs would be appreciated. > >Thanks > > >- >To unsubscribe, email 'majordomo@livingston.com' with >'unsubscribe ietf-radius' in the body of the message. - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Fri Dec 4 14:54:57 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01453 for ; Fri, 4 Dec 1998 14:54:56 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id KAA05852; Fri, 4 Dec 1998 10:52:55 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id KAA18615 for ietf-radius-outgoing; Fri, 4 Dec 1998 10:48:14 -0800 (PST) Message-ID: From: Indranil Bagchi To: "'ietf-radius@livingston.com'" Subject: (radius) TACACS Date: Fri, 4 Dec 1998 10:47:00 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Indranil Bagchi I am looking for specifications/source code for TACACS/XTACACS/TACACS+. I would also like to find information on Kerberos and Kerberos CHAP authentication. Any inputs would be appreciated. Thanks - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Fri Dec 4 16:11:30 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02743 for ; Fri, 4 Dec 1998 16:11:29 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id NAA11659; Fri, 4 Dec 1998 13:03:43 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id NAA05618 for ietf-radius-outgoing; Fri, 4 Dec 1998 13:04:12 -0800 (PST) Date: Fri, 4 Dec 98 13:00:43 PST From: William "Chops" Westfield Cc: "Indranil Bagchi" , "'ietf-radius@livingston.com'" Subject: Re: (radius) TACACS In-Reply-To: Your message of Fri, 4 Dec 1998 11:03:58 -0800 Message-ID: Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: William "Chops" Westfield Note that cisco has put xtacacs and tacacs into "end of life" mode for all cisco products - I wouldn't design much around them if I were you. (something about keeping the number of supported authentication methods less than a dozen... ;-) BillW cisco - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Fri Dec 4 17:09:18 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03573 for ; Fri, 4 Dec 1998 17:09:17 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id NAA11842; Fri, 4 Dec 1998 13:07:03 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id NAA06074 for ietf-radius-outgoing; Fri, 4 Dec 1998 13:08:25 -0800 (PST) From: yyrte@singmail.com Message-Id: <199812042106.NAA11820@bast.livingston.com> Subject: (radius) PUT MONEY INTO YOUR POCKET! business opportunity ad Date: Fri, 4 Dec 1998 12:26:27 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: yyrte@singmail.com 5615404028 5615404028 E MAIL KING AND ASSOCIATES PUTS MONEY INTO YOUR POCKET!! OUR COMPANY HAS OVER 3 YEARS PROVEN E MAIL BLASTING EXPERIENCE! WORK SMARTER BY HAVING QUALIFIED PEOPLE PHONE YOU, ALREADY PREPARED TO BUY. PUT YOUR COLD CALLING DAYS TO AN END. CHECK OUT OUR INTRODUCTORY OFFER FOR 10,000 E MAILS TODAY! FOR ONLY $125.00 WE WILL INCLUDE A TARGETED SEARCH FOR CUSTOMERS WHO MAY BE INTERESTED IN YOUR PRODUCT OR SERVICE AND MAIL TO THEM ON THE INTERNET. FOR THOSE OF YOU WHO WOULD LIKE E MAILING CONTINOUSLY DONE, WHY NOT TRY OUR MONTHLY PROGRAM FOR ONLY $250.00. WE WILL E MAIL YOUR AD OUT TO 7500 ADDRESSES DAILY FIVE DAYS PER WEEK. Do you only market your product or service geographically? Not a problem with E Mail King and Associates. We can target your e-mail broadcastes into the city of your choosing! CALL US TODAY FOR DETAILS! IF YOU ALREADY HAVE YOUR OWN E MAIL SYSTEM, WHY NOT TRY OUR SUBCRIPTION SERVICE WHERE YOU WILL RECEIVE 50,000 FRESH GOOD E MAIL ADDRESSES EVERY week for only $25.00. CALL US FOR A QUOTE! ARE YOU INTERESTED IN BEING AN E MAIL KING RESELLER? PUT EVEN MORE MONEY INTO YOUR POCKET TODAY BY SIGNING UP WITH OUR PROGRAM TODAY!! IT DOES NOT COST ANYTHING TO JOIN!! We accept payment by Cheque by Fax. James phone 5615404028 _________________________________________________________________ TO BE REMOVED FROM OUR LIST, please call 18006366773 6834 or e mail yyrte@singmail.com type in "remove" in the subject header or our mailing address is EMAIL KING and Associates 1790 Bonhill Rd Mississauga Ontario Canada - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Fri Dec 4 19:42:32 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05245 for ; Fri, 4 Dec 1998 19:42:31 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id QAA18191; Fri, 4 Dec 1998 16:35:23 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id QAA28852 for ietf-radius-outgoing; Fri, 4 Dec 1998 16:35:42 -0800 (PST) Date: Fri, 4 Dec 98 16:32:20 PST From: William "Chops" Westfield To: ietf-radius@livingston.com Subject: (radius) Re: tacacs Message-ID: Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: William "Chops" Westfield >Note that cisco has put xtacacs and tacacs into "end of life" mode for >all cisco products - I wouldn't design much around them if I were you. A clarification: cisco is eliminating support for (old, BBN define) tacacs and (cisco-defined, old) xtacacs. Support for (cisco-defined, new) tacacs+ will continue for the forseen future... BillW cisco - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Sat Dec 5 00:00:45 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15211 for ; Sat, 5 Dec 1998 00:00:44 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id UAA23155; Fri, 4 Dec 1998 20:53:33 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id UAA13959 for ietf-radius-outgoing; Fri, 4 Dec 1998 20:53:14 -0800 (PST) From: asdla@msn.com Date: Fri, 4 Dec 1998 22:27:23 -0600 (CST) To: dsaflak@prodigy.net Subject: (radius) Home Based Travel Business!!!! X-PMFLAGS: 10322341.10 X-UIDL: 10293287_192832.222 Comments: Authenticated Sender is Message-Id: <31132597_35662529> Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: asdla@msn.com $100,000+ FIRST YEAR INCOME

* Earn $2000-$5000 weekly-Starting Within 1-4 weeks!
* 78% Profit Paid Daily
* No Selling
* No Risk Guarantee
* Work from home, No overhead, or employees.
* High Tech Training & Support
* Not MLM, 100x more profitable
* Multibillion Dollar Travel Industry

The most incredible part of our business is that
ALL MY CLIENTS CALL ME!

DO YOU QUALIFY FOR OUR MENTOR PROGRAM?
ACCEPTING ONLY 12 NEW ASSOCIATES.....

This is not a hobby! Serious Inquiries Only! No Obligation!

24 Hour Toll Free Message 1-800-417-6360 Ext. 5680

If you're an entrepreneur or have always wanted to be your own BOSS, read on. We supply state-of-the-art training and a support system that allows you to work your business from your home with just a phone-without cold calling. DO NOT CALL ME IF YOU'RE LOOKING FOR A "GET RICH QUICK" SCHEME or some extra cash or if you're lazy. We are only looking for FOCUSED, serious entrepreneurs. (PT/FT) with the DESIRE to improve their lifestyle immediately.


This is a one time mailing. If this has offended you please hit delete now!
Thanks
- To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Sat Dec 5 01:24:05 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17041 for ; Sat, 5 Dec 1998 01:24:05 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id WAA25014; Fri, 4 Dec 1998 22:17:13 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id WAA18048 for ietf-radius-outgoing; Fri, 4 Dec 1998 22:16:49 -0800 (PST) From: asdla@msn.com Date: Fri, 4 Dec 1998 22:12:58 -0800 (PST) To: dsaflak@prodigy.net Subject: (radius) Work from home in the Travel Industry! X-PMFLAGS: 10322341.10 X-UIDL: 10293287_192832.222 Comments: Authenticated Sender is Message-Id: <31055201_85695498> Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: asdla@msn.com $100,000+ FIRST YEAR INCOME

* Earn $2000-$5000 weekly-Starting Within 1-4 weeks!
* 78% Profit Paid Daily
* No Selling
* No Risk Guarantee
* Work from home, No overhead, or employees.
* High Tech Training & Support
* Not MLM, 100x more profitable
* Multibillion Dollar Travel Industry

The most incredible part of our business is that
ALL MY CLIENTS CALL ME!

DO YOU QUALIFY FOR OUR MENTOR PROGRAM?
ACCEPTING ONLY 12 NEW ASSOCIATES.....

This is not a hobby! Serious Inquiries Only! No Obligation!

24 Hour Toll Free Message 1-800-417-6360 Ext. 5680

If you're an entrepreneur or have always wanted to be your own BOSS, read on. We supply state-of-the-art training and a support system that allows you to work your business from your home with just a phone-without cold calling. DO NOT CALL ME IF YOU'RE LOOKING FOR A "GET RICH QUICK" SCHEME or some extra cash or if you're lazy. We are only looking for FOCUSED, serious entrepreneurs. (PT/FT) with the DESIRE to improve their lifestyle immediately.


This is a one time mailing. If this has offended you please hit delete now!
Thanks
- To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Sat Dec 5 21:44:22 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23870 for ; Sat, 5 Dec 1998 21:44:22 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id SAA06959; Sat, 5 Dec 1998 18:36:10 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id SAA12415 for ietf-radius-outgoing; Sat, 5 Dec 1998 18:32:54 -0800 (PST) From: Clark_Rudder@infonet.com X-Lotus-FromDomain: ISC@INFONET To: William "Chops" Westfield cc: ietf-radius@livingston.com Message-ID: <882566D2.000D5120.00@issmail1.infonet.com> Date: Sat, 5 Dec 1998 18:27:35 -0800 Subject: Re: (radius) TACACS Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Clark_Rudder@infonet.com Bill, What is the meaning of end of life mode? -Clark William "Chops" Westfield on 12/04/98 01:00:43 PM Please respond to William "Chops" Westfield To: cc: "Indranil Bagchi" , "'ietf-radius@livingston.com'" (bcc: Clark Rudder/HQ/ISC) Subject: Re: (radius) TACACS Note that cisco has put xtacacs and tacacs into "end of life" mode for all cisco products - I wouldn't design much around them if I were you. (something about keeping the number of supported authentication methods less than a dozen... ;-) BillW cisco - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Mon Dec 7 01:56:54 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15648 for ; Mon, 7 Dec 1998 01:56:54 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id WAA22552; Sun, 6 Dec 1998 22:48:51 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id WAA27006 for ietf-radius-outgoing; Sun, 6 Dec 1998 22:45:28 -0800 (PST) Message-Id: <199812070644.WAA01984@shell4.ba.best.com> Subject: Re: (radius) TACACS (fwd) To: ietf-radius@livingston.com Date: Sun, 6 Dec 1998 22:44:12 -0800 (PST) From: MegaZone Organization: WPI Discordian Society, Undocumented Cabal of the Accursed Saint Shiranto Joe X-Trade-Organization-1: Internet Service Providers' Consortium (ISP/C) X-Trade-Organization-2: Director At Large X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: MegaZone Content-Transfer-Encoding: 7bit Once upon a time Clark_Rudder@infonet.com shaped the electrons to say... >What is the meaning of end of life mode? No new development. Generally it means development is ended, and use is discouraged. In time it may be removed from the products that now use it due to being obsolete. When a product - HW or SW - is EOL'd nothing new is added. In some cases there is a period of time when bug fixes and security patches ae provided as needed, but no new features are added. And there is a death time set after which point NO work is done, and the product is considered totally dead. No support at all. The original TACACS has been obsolete for a rather long time now, XTACACS is out dated as well. Cisco moved to TACACS+ a while ago as their development focus, as have the others who support TACACS. And, of course, RADIUS has become nigh-universal. -MZ -- Gweep, Discordian, Author, Engineer, me.. Join ISP/C Internet Service Providers' Consortium "A little nonsense now and then, is relished by the wisest men" 781-788-0130 Hail Discordia! - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Mon Dec 7 02:48:37 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15877 for ; Mon, 7 Dec 1998 02:48:37 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id XAA23420; Sun, 6 Dec 1998 23:41:44 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id XAA29150 for ietf-radius-outgoing; Sun, 6 Dec 1998 23:43:01 -0800 (PST) Date: Sun, 6 Dec 98 23:39:10 PST From: William "Chops" Westfield To: MegaZone Cc: ietf-radius@livingston.com Subject: Re: (radius) TACACS (fwd) In-Reply-To: Your message of Sun, 6 Dec 1998 22:44:12 -0800 (PST) Message-ID: Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: William "Chops" Westfield >What is the meaning of end of life mode? No new development. Generally it means development is ended, and use is discouraged. In time it may be removed from the products that now use it due to being obsolete. Somewhere, cisco has carefully defined the "end of life" sequence for their products. First, "development" (new features) stops. Then "maintenance" stops as well (no bug fixes, no tech assistance.) Eventually, the feature is completely unsupported, and is (perhaps) removed from the software base. I think we've actually removed a couple things - chaosnet and pup, perhaps. I could tell you where on cisco's web site to find this info, but then I'd have to wear a suit more often... :-) BillW cisco - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Mon Dec 7 03:14:07 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16036 for ; Mon, 7 Dec 1998 03:14:06 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id AAA23745; Mon, 7 Dec 1998 00:06:23 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id AAA00108 for ietf-radius-outgoing; Mon, 7 Dec 1998 00:07:29 -0800 (PST) Message-Id: <199812070806.AAA11237@shell4.ba.best.com> Subject: Re: (radius) TACACS (fwd) To: ietf-radius@livingston.com Date: Mon, 7 Dec 1998 00:06:40 -0800 (PST) From: MegaZone Organization: WPI Discordian Society, Undocumented Cabal of the Accursed Saint Shiranto Joe X-Trade-Organization-1: Internet Service Providers' Consortium (ISP/C) X-Trade-Organization-2: Director At Large X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: MegaZone Content-Transfer-Encoding: 7bit Once upon a time William "Chops" Westfield shaped the electrons to say... >I could tell you where on cisco's web site to find this info, but then I'd >have to wear a suit more often... This one? Also of interest in context: -MZ -- Gweep, Discordian, Author, Engineer, me.. Join ISP/C Internet Service Providers' Consortium "A little nonsense now and then, is relished by the wisest men" 781-788-0130 Hail Discordia! - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Mon Dec 7 03:24:50 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16085 for ; Mon, 7 Dec 1998 03:24:49 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id AAA23958; Mon, 7 Dec 1998 00:17:33 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id AAA00974 for ietf-radius-outgoing; Mon, 7 Dec 1998 00:18:55 -0800 (PST) From: jill@msic.com Message-Id: <199812070817.JAA12223@mail.nexus.it> To: user@the.internet.nexus.it Date: Mon, 07 Dec 98 00:02:03 EST Subject: (radius) would like to purchase.. Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: jill@msic.com ll Ayers and I'm an account manager for MSI Communications. I'm interested in talking to you about surplus network equipment. We're a highly respected full-service integrator, but a significant part of our business is buying and selling used network equipment, including routers, switches and hubs. We concentrate on such top brands as Cisco, Ascend, Livingston/Lucent, Paradyne and USRobotics/3Com. The networking gear that you've taken out of service is probably collecting dust, but could still have significant value. If you have such a surplus, we may be interested in buying it. In addition to purchase, we can accept used equipment as trade-in if you're looking to replace it. Or, if you need equipment for low-cost network expansion, or for backup, our inventory of refurbished products will allow you to achieve your objectives for a cost savings of up to 40%. Unlike other suppliers who offer refurbished network equipment, we provide a full-service capability, including: Total product refurbishment and recertification, including firmware upgrades and documentation Product warranty Product repair service 24x7 tech support and problem resolution Optional overnight replacement service Warehousing and logistics management We also offer an unsurpassed reputation for quality and service, with such customers as EDS, Lockheed Martin, AOL, State Farm Insurance, CitiBank and IBM Business Recovery Services. We're an established (10 years) and highly respected organization, so our interest is serious - regardless of whether the opportunity is immediate or in the future. I urge you to check our credentials by viewing our web site... http://www.msic.com Please e-mail me to recommend when during the next week I should call you. Or, feel free to call me at your convenience at 973-347-3349. Thank you, Jill Ayers MSI Communications, Inc. 7 Waterloo Road, Stanhope NJ 07874 jill@msic.com V.) 973-347-3349 F.) 973-347-7176 - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Mon Dec 7 12:18:11 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19313 for ; Mon, 7 Dec 1998 12:18:10 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id JAA07056; Mon, 7 Dec 1998 09:08:27 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id JAA00725 for ietf-radius-outgoing; Mon, 7 Dec 1998 09:07:08 -0800 (PST) Message-Id: <199812071703.JAA17388@irp-view5.cisco.com> To: ietf-radius@livingston.com Subject: Re: (radius) TACACS (fwd) In-reply-to: Your message of "Sun, 06 Dec 1998 23:39:10 PST." Date: Mon, 07 Dec 1998 09:03:45 -0800 From: Lol Grant Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Lol Grant > Somewhere, cisco has carefully defined the "end of life" sequence for their > products. First, "development" (new features) stops. Then "maintenance" > stops as well (no bug fixes, no tech assistance.) Eventually, the feature > is completely unsupported, and is (perhaps) removed from the software base. > I think we've actually removed a couple things - chaosnet and pup, perhaps. > > I could tell you where on cisco's web site to find this info, but then I'd > have to wear a suit more often... At the risk of continuing this off-topic thread (though it's more relevant than most of the spam that seems to constitute this list nowadays) I'm told by marketing that end of life for x(tacacs) follows end of maintenance after two years. That means that (x)tacacs will effectively disappear, for all practical purposes, in May 1999. Tacacs_plus will, of course, be unaffected by any of this. Cheers, __ Lol - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Mon Dec 7 12:40:18 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19564 for ; Mon, 7 Dec 1998 12:40:17 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id JAA08238; Mon, 7 Dec 1998 09:31:09 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id JAA03607 for ietf-radius-outgoing; Mon, 7 Dec 1998 09:30:21 -0800 (PST) Date: Mon, 7 Dec 1998 11:26:54 -0600 (CST) From: Jim Thompson Message-Id: <199812071726.LAA10822@hosaka.smallworks.com> To: ietf-radius@livingston.com, lol@cisco.com Subject: Re: (radius) TACACS (fwd) Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Jim Thompson >Tacacs_plus will, of course, be unaffected by any of this. As much as TACACS+ is affected by anything in the RADIUS world... - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue Dec 8 00:50:35 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02063 for ; Tue, 8 Dec 1998 00:50:34 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id VAA06494; Mon, 7 Dec 1998 21:42:34 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id VAA18212 for ietf-radius-outgoing; Mon, 7 Dec 1998 21:42:32 -0800 (PST) Date: Tue, 08 Dec 1998 14:37:25 +0900 From: "ji choel park" Organization: Shinsegi Telecomm, Inc. To: "RADIUS" Subject: (radius) Framed IP-Address Attibute MIME-Version: 1.0 X-Mailer: HMail 1.0 Video Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <7718E765FBC.AAA30B9@mail.shinsegi.com> Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "ji choel park" Content-Transfer-Encoding: 7bit I have a few questions on Framed IP-Address Attribute in RADIUS. In section 5.8 in rfc2138, there's description on Address field. "The value 0xFFFFFFFF indicattes that the NAS should allow the user to select an address (e.g. Negotiated). The value 0xFFFFFE indicates that the NAS should select an address for the user (e.g. Assigned from a pool of addresses kept by the NAS). Other valid values indicate that the NAS should use that value as the user's IP address" If the value of the Address field is 0xFFFFFF, could the NAS allow the user to be assigned the address request by the user? For example, the user is a Mobile Host of Mobile IP, and it requests its Home Address to the NAS. If so, can the NAS assign the requested Home Address to the Mobile Node? Can the Frame-IP-Address Attribute be included in the Access-Accept packet, only when the previous Access-Request packet include the Attribute? If not, what is the reason? As more basical question, why is the Framed-IP-Address Attribute needed in RADIUS? Regards, Jicheol Park Shinsegi Telecomm, Inc. Korea - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue Dec 8 11:36:26 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07193 for ; Tue, 8 Dec 1998 11:36:25 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id IAA18021; Tue, 8 Dec 1998 08:28:24 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id IAA22892 for ietf-radius-outgoing; Tue, 8 Dec 1998 08:26:14 -0800 (PST) Message-ID: <004801be22c7$212f5920$c889e9cc@titanium.techapp.com> From: "Russell J. LeBar" To: "RADIUS" Subject: Re: (radius) Framed IP-Address Attibute Date: Tue, 8 Dec 1998 10:23:32 -0600 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 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "Russell J. LeBar" Content-Transfer-Encoding: 7bit If I am not mistaken, one example would be if a user has paid for a static IP Address. -----Original Message----- From: ji choel park >As more basical question, why is the Framed-IP-Address Attribute needed in RADIUS? - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue Dec 8 15:08:17 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09039 for ; Tue, 8 Dec 1998 15:08:17 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id MAA28905; Tue, 8 Dec 1998 12:00:27 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id LAA21417 for ietf-radius-outgoing; Tue, 8 Dec 1998 11:59:57 -0800 (PST) Message-Id: <2.2.32.19981208225324.0069753c@acc.com> X-Sender: koral@acc.com X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 08 Dec 1998 14:53:24 -0800 To: "Russell J. LeBar" From: Koral Ilgun Subject: Re: (radius) Framed IP-Address Attibute Cc: "RADIUS" Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Koral Ilgun Or if the RADIUS server is doing IP address assignments from a defined IP address pool. Steel-Belted-Radius does this for instance. Koral At 10:23 AM 12/8/98 -0600, Russell J. LeBar wrote: >If I am not mistaken, one example would be if a user has paid for a static >IP Address. > >-----Original Message----- >From: ji choel park > >>As more basical question, why is the Framed-IP-Address Attribute needed in >RADIUS? > > >- >To unsubscribe, email 'majordomo@livingston.com' with >'unsubscribe ietf-radius' in the body of the message. > > - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue Dec 8 18:33:30 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11051 for ; Tue, 8 Dec 1998 18:33:29 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id PAA09957; Tue, 8 Dec 1998 15:25:41 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id PAA21566 for ietf-radius-outgoing; Tue, 8 Dec 1998 15:26:09 -0800 (PST) Message-Id: <199812082324.PAA28660@shell4.ba.best.com> Subject: (radius) Framed IP-Address Attibute (fwd) To: ietf-radius@livingston.com Date: Tue, 8 Dec 1998 15:24:52 -0800 (PST) From: MegaZone Organization: WPI Discordian Society, Undocumented Cabal of the Accursed Saint Shiranto Joe X-Trade-Organization-1: Internet Service Providers' Consortium (ISP/C) X-Trade-Organization-2: Director At Large X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: MegaZone Content-Transfer-Encoding: 7bit Once upon a time ji choel park shaped the electrons to say... >In section 5.8 in rfc2138, there's description on Address field. > >"The value 0xFFFFFFFF indicattes that the NAS should allow the user to select an address (e.g. Negotiated). The value 0xFFFFFE indicates that the NAS should select an address for the user (e.g. Assigned from a pool of addresses kept by the NAS). Other valid values indicate that the NAS should use that value as the user's IP address" 0xFFFFFE is not valid - I presume you mean 0xFFFFFFFE Yes: 'Framed-IP-Address = 255.255.255.255' means 'let the user pick any IP' 'Framed-IP-Address = 255.255.255.254' means 'assign the user an IP from your pool' >If the value of the Address field is 0xFFFFFF, could the NAS allow the user to be assigned the address request by the user? For example, the user is a Mobile Host of Mobile IP, and it requests its Home Address to the NAS. If so, can the NAS assign the requested Home Address to the Mobile Node? 0xFFFFFF isn't valid - I presume you mean 0xFFFFFFFF? When the NAS gets this the user can request, and should be allowed to use, ANY IP address. Hence this is a very dangerous thing to use - and in practice is very rarely seen. >Can the Frame-IP-Address Attribute be included in the Access-Accept packet, only when the previous Access-Request packet include the Attribute? If not, what is the reason? The Framed-IP-Address AVP can be included in ANY Access-Accept packet. There is no need to have received it in the Access-Request packet - and in fact seeing it there is very rare in practice. >As more basical question, why is the Framed-IP-Address Attribute needed in RADIUS? 1. Telling the NAS what to do. By default most NASes will assign an IP from their pool. If you wish to allow the user to pick one you need to override that behavior. 2. Static IP addresses for dialin users. For example I have a static IP and subnet routed to a continuous ISDN dialup line at home. So my RADIUS entry has the appropriate IP and netmask for this connection. 3. RADIUS IP pools. Some RADIUS servers assign IP addresses from their own pools, or using some formula such as NAS-IP-Address+NAS-Port. -MZ -- Gweep, Discordian, Author, Engineer, me.. Join ISP/C Internet Service Providers' Consortium "A little nonsense now and then, is relished by the wisest men" 781-788-0130 Hail Discordia! - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue Dec 8 22:15:15 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12500 for ; Tue, 8 Dec 1998 22:15:14 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id TAA25068; Tue, 8 Dec 1998 19:07:10 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id TAA20333 for ietf-radius-outgoing; Tue, 8 Dec 1998 19:07:46 -0800 (PST) Message-ID: From: Indranil Bagchi To: "'ietf-radius@livingston.com'" Subject: (radius) radius v2 Date: Tue, 8 Dec 1998 19:07:04 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Indranil Bagchi I was going through the free source code available from Merit and found references to version 2. Is there a draft other than 2138 which describes the newer version of the protocol? Also the code has references to Merit specific extensions like huntgroups, binary filters and more. Is there any documentation available on these extensions. Thanks - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue Dec 8 22:29:01 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13394 for ; Tue, 8 Dec 1998 22:29:01 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id TAA26520; Tue, 8 Dec 1998 19:22:03 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id TAA22517 for ietf-radius-outgoing; Tue, 8 Dec 1998 19:23:21 -0800 (PST) Message-Id: <199812090322.TAA03523@shell4.ba.best.com> Subject: (radius) radius v2 (fwd) To: ietf-radius@livingston.com Date: Tue, 8 Dec 1998 19:22:07 -0800 (PST) From: MegaZone Organization: WPI Discordian Society, Undocumented Cabal of the Accursed Saint Shiranto Joe X-Trade-Organization-1: Internet Service Providers' Consortium (ISP/C) X-Trade-Organization-2: Director At Large X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: MegaZone Content-Transfer-Encoding: 7bit Once upon a time Indranil Bagchi shaped the electrons to say... >references to version 2. Is there a draft other than 2138 which describes >the newer version of the protocol? Also the code has references to Merit There is no newer version of the protocol. There is "RADIUS" - as defined in 2138, 2139, and the various drafts now in progress. I don't know what Merit was referring to. Some people were refer to RADIUS 2 when talking about the Lucent RADIUS server software versions 2.0 and higher, as these revisions marked the addtion of many new server-side features. >specific extensions like huntgroups, binary filters and more. Is there any >documentation available on these extensions. That is all server or vendor specific. Binary filters is an Ascend thing for example, *very* much outside of the RFCs. Every RADIUS server has its own features. The protocol definitions are only concerned with the communication across the network, not the decision making process in the server, or how it populates the AVPs it sends. -MZ -- Gweep, Discordian, Author, Engineer, me.. Join ISP/C Internet Service Providers' Consortium "A little nonsense now and then, is relished by the wisest men" 781-788-0130 Hail Discordia! - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue Dec 8 22:39:00 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14304 for ; Tue, 8 Dec 1998 22:38:59 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id TAA26795; Tue, 8 Dec 1998 19:32:06 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id TAA23344 for ietf-radius-outgoing; Tue, 8 Dec 1998 19:32:09 -0800 (PST) From: Aydin Edguer Message-Id: <199812090330.WAA20116@picu.morningstar.com> Subject: Re: (radius) radius v2 To: ibagchi@extremenetworks.com Date: Tue, 8 Dec 1998 22:30:44 -0500 (EST) Cc: ietf-radius@livingston.com In-Reply-To: from "Indranil Bagchi" at Dec 8, 98 07:07:04 pm X-Mailer: ELM [version 2.4 PL24 PGP2] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Aydin Edguer Content-Transfer-Encoding: 7bit > I was going through the free source code available from Merit This mailing list for discussions of the IETF RADIUS Working Group. If is not about any specific implementation of RADIUS. Questions regarding an implementation should be directed to the authors or companies supporting the software. > and found references to version 2. Is there a draft other than 2138 which > describes the newer version of the protocol? No. The "v2" in Merit are references to an earlier draft of what is now known as DIAMETER. However, the Merit version, although written by Pat Calhoun, no longer matches the current DIAMETER drafts. > Also the code has references to Merit specific extensions like huntgroups, > binary filters and more. Is there any documentation available on these > extensions. Documentation on Merit software should be available from the Merit web pages . Huntgroups are Merit specific. Binary filters are an Ascend Communications specific extension. Information on binary filters may be found in the Ascend documentation. - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Wed Dec 9 07:55:28 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24689 for ; Wed, 9 Dec 1998 07:55:27 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id EAA07610; Wed, 9 Dec 1998 04:47:56 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id EAA21102 for ietf-radius-outgoing; Wed, 9 Dec 1998 04:48:05 -0800 (PST) From: William Bulley Message-Id: <199812091248.HAA08796@ohm.merit.edu> Subject: Re: (radius) radius v2 To: ibagchi@extremenetworks.com Date: Wed, 9 Dec 1998 07:48:46 -0500 (EST) Cc: ietf-radius@livingston.com In-Reply-To: from "Indranil Bagchi" at Dec 8, 98 07:07:04 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: William Bulley Content-Transfer-Encoding: 7bit According to Indranil Bagchi: > > I was going through the free source code available from Merit and found > references to version 2. Is there a draft other than 2138 which describes > the newer version of the protocol? Also the code has references to Merit > specific extensions like huntgroups, binary filters and more. Is there any > documentation available on these extensions. Questions about the Merit AAA Server should be sent to aaa-support@merit.edu This is an experimental feature which is buggy and should not be used. Regards, web... -- William Bulley Senior Systems Research Programmer Merit Network, Inc. Email: web@merit.edu 4251 Plymouth Road, Suite C Phone: (734) 764-9993 Ann Arbor, Michigan 48105-2785 Fax: (734) 647-3185 If entropy is increasing, where is it coming from? - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Mon Dec 14 05:06:32 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17384 for ; Mon, 14 Dec 1998 05:06:31 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id BAA00719; Mon, 14 Dec 1998 01:59:10 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id BAA12543 for ietf-radius-outgoing; Mon, 14 Dec 1998 01:54:53 -0800 (PST) From: RLJ@mail.sartissohn.de Message-Id: <199812141053.LAA26551@mail.sartissohn.de> To: user@the_internet.com Date: Mon, 14 Dec 98 01:26:13 EST Subject: (radius) LEARN AND EARN Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: RLJ@mail.sartissohn.de How would you like to take home more money from your pay check "yes" let us show you how. How to purchase a home and pay from 0 to 3% interest. Drive a new car $40,000 to $100,000 without purchasing it. Reduce your taxes from $5,000 to $15,000 a year. You can earn extra income by teaching others. No products to sell. This is not Multi-Level Marketing, it is Network Marketing. As a independent representative for RCC Communications, Inc. we will help you build a downline. To learn how you can get started e-mail roncrutchfield@worldnet.att.net for more information or mail your name and address and phone number. HOW TO BECOME A DISTRIBUTOR OF WEBSITES. Give away FREE websites and earn a commission. CONTACT: RCC Communications, Inc. 3863 Union Deposit Rd Box 243 Harrisburg, Pa 17109 ---- - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Mon Dec 14 14:38:13 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27219 for ; Mon, 14 Dec 1998 14:38:12 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id LAA16678; Mon, 14 Dec 1998 11:29:43 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id LAA27166 for ietf-radius-outgoing; Mon, 14 Dec 1998 11:27:32 -0800 (PST) Message-ID: From: Indranil Bagchi To: "'ietf-radius@livingston.com'" Subject: (radius) Radius client passwd change Date: Mon, 14 Dec 1998 11:26:44 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Indranil Bagchi Is there a way (a radius attribute) by which a radius client can request the radius server to change its passwd. Or does this feature need to be implemented as a vendor-specific attribute. Thanks - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Mon Dec 14 15:05:50 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27945 for ; Mon, 14 Dec 1998 15:05:49 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id LAA18595; Mon, 14 Dec 1998 11:58:13 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id LAA02241 for ietf-radius-outgoing; Mon, 14 Dec 1998 11:58:18 -0800 (PST) Message-ID: From: "Nelson, David" To: "'ietf-radius@livingston.com'" Subject: FW: (radius) Radius client passwd change Date: Mon, 14 Dec 1998 14:54:27 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "Nelson, David" Indranil Bagchi writes... > Is there a way (a radius attribute) by which a radius client can > request the radius server to change its passwd. > No. > Or does this feature need to be implemented as a vendor-specific > attribute. > One could contemplate doing that. The RADIUS WG had a long debate on password change. You may wish to search the archives. The consensus reached was that password change was outside the scope of RADIUS, and that the security mechanisms needed to do this "correctly" were possibly incompatible with the RADIUS model. Having said that, one vendor (Digital, now Cabletron) has implemented a password change feature in its RADIUS Server product. This feature is implementation specific to the RADIUS server code, and does not use a vendor-specific attribute. While there is some obvious utility in this feature, you are not going to find a standardized way to implement it, and you should be aware of the potential security risks of doing this in a "simplistic" fashion. Caveat emptor. Regards, Dave David B. Nelson Cabletron Systems, Inc. Software Engineer V 50 Minuteman Road (978) 684-1330 Andover, MA 01810 - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue Dec 15 09:16:10 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16213 for ; Tue, 15 Dec 1998 09:16:10 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id GAA17039; Tue, 15 Dec 1998 06:07:13 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id GAA17863 for ietf-radius-outgoing; Tue, 15 Dec 1998 06:05:19 -0800 (PST) From: verygud@pusan.ac.kr Date: Tue, 15 Dec 1998 06:03:19 -0800 (PST) Message-Id: <199812151403.GAA16986@bast.livingston.com> To: ghghjj@ludwigsburg.netsurf.de Subject: (radius) $150K+ Per Year / Home-Based / NOT MLM Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: verygud@pusan.ac.kr Look, we don't want to waste your time....or ours. If you are 100% SERIOUS about earning a solid, six-figure income from home, and you're not afraid to work for it WE CAN HELP YOU! * NOT MLM or GLOBAL * Completely Legitimate Home-Based Business * Registered with D&B and BBB * Professional Training and Fantastic Support * Work Entirely From Home (no personal selling) Grab your share of the 3.4 Trillion Dollar Travel Industry NOW! CALL TOLL FREE 888-474-4721 (24 Hour Recorded Message) - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Wed Dec 16 08:54:14 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12186 for ; Wed, 16 Dec 1998 08:54:14 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id FAA15061; Wed, 16 Dec 1998 05:46:14 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id FAA06316 for ietf-radius-outgoing; Wed, 16 Dec 1998 05:44:35 -0800 (PST) From: tyrtggdfg@OMNIGRP.COM Date: Mon, 14 Dec 1998 03:22:26 -0600 Message-Id: <199812140922.DAA28593@dagon.host4u.net> To: hjkhjkh@ludwigsburg.netsurf.de Subject: (radius) $150K+ Per Year / Home-Based / NOT MLM Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: tyrtggdfg@OMNIGRP.COM Look, we don't want to waste your time....or ours. If you are 100% SERIOUS about earning a solid, six-figure income from home, and you're not afraid to work for it WE CAN HELP YOU! * NOT MLM or GLOBAL * Completely Legitimate Home-Based Business * Registered with D&B and BBB * Professional Training and Fantastic Support * Work Entirely From Home (no personal selling) Grab your share of the 3.4 Trillion Dollar Travel Industry NOW! CALL TOLL FREE 888-474-4721 (24 Hour Recorded Message) - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Thu Dec 17 18:06:58 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16214 for ; Thu, 17 Dec 1998 18:06:57 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id OAA22453; Thu, 17 Dec 1998 14:58:39 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id OAA25752 for ietf-radius-outgoing; Thu, 17 Dec 1998 14:56:57 -0800 (PST) From: cellular@webcre8tive.com Message-Id: <199812172255.OAA22280@bast.livingston.com> To: Subject: (radius) Cellphone Batteries @ Half Price! Date: Thu, 17 Dec 1998 11:23:22 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: cellular@webcre8tive.com Cellphone Batteries @ Half Price! Cellphone Owners and Mobile Professionals, SAVE BIG! – BUY DIRECT! - Get your Cellphone Batteries quick and easy online at CELLPHONE BATTERY WAREHOUSE Highest Quality, Lowest Prices, Giant Selection – Guaranteed! Click-on and Bookmark this site - http://members.tripod.com/~cellbattery ********************************************************** We believe in responsible targeted mailing. Your name was given to us as somebody who might be interested in this offer. This message is sent in compliance of the new e-mail bill: SECTION 301. Sender: CELLPHONE BATTERY WAREHOUSE, 7810 Topanga cyn Blvd, Canoga Park, Ca 91304 ph: 818 207-9600 E-Mail Address:Cellular@webcre8tive.com Per Section 301, Paragraph (a)(2)(C) of S.1618, further transmissions to you by the sender of this email may be stopped at no cost to you by ending a reply to this email address with the word "remove" in the subject line. For additional information see: ********************************************************** - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue Dec 22 06:03:16 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27086 for ; Tue, 22 Dec 1998 06:03:15 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id CAA09044; Tue, 22 Dec 1998 02:54:59 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id CAA26879 for ietf-radius-outgoing; Tue, 22 Dec 1998 02:52:21 -0800 (PST) Message-ID: From: Jonathan Garini To: ietf-radius@livingston.com Subject: (radius) Proxy state - String or Octets? Date: Tue, 22 Dec 1998 12:48:25 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="windows-1255" Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Jonathan Garini Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id GAA27086 The RFC states the the proxy state SHOULD be treated as undistinguished octets. Merit and Livingstom implementations treat it as an NULL terminated ASCII string field. If we try to send the field as undistinguished octets it does not work with Merit\Livingston.   My thoughts are that:   1. SHOULD is not good here as it does not allow interoperability between different Radius Servers. 2. The Merit\Livingston ASCII implementation should not be the preferred method as it is less flexible.   Regards, Jonathan. -- Jonathan  Garini - CEO mailto:jonathan@extent.com -- Extent Technologies Ltd. 3, Habonim St. Ramat Gan  52462 Israel Phone: +972-3-7513333    Fax: +972-3-7515858 mailto:info@extent.com         http://www.extent.com (US)   - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue Dec 22 06:35:02 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27261 for ; Tue, 22 Dec 1998 06:35:02 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id DAA09472; Tue, 22 Dec 1998 03:27:56 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id DAA28221 for ietf-radius-outgoing; Tue, 22 Dec 1998 03:28:45 -0800 (PST) Message-ID: <367F8064.9106375F@iea-software.com> Date: Tue, 22 Dec 1998 03:20:04 -0800 From: "Dale E. Reed Jr." Organization: IEA Software, Inc. X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Jonathan Garini CC: ietf-radius@livingston.com Subject: Re: (radius) Proxy state - String or Octets? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "Dale E. Reed Jr." Content-Transfer-Encoding: 7bit Jonathan Garini wrote: > > The RFC states the the proxy state SHOULD be treated as undistinguished > octets. > Merit and Livingstom implementations treat it as an NULL terminated ASCII > string field. First of all, strings are NOT null terminated in the RADIUS protocol, since we have a length specifier. Any implementation relying on NULL terminated strings is broken. IMHO. This has nothing to do with how they are stored by the server, just how they are tranmitted over the wire. However, with undistringuied octets it is possible to include a 0 byte at the end as as NULL (which should not cause a problem, since its not a string and you shouldn't be using string functions on the data portion). > If we try to send the field as undistinguished octets it does not work with > Merit\Livingston. Can you expand on this? What doesn't work? > My thoughts are that: > > 1. SHOULD is not good here as it does not allow interoperability between > different Radius Servers. I agree. > 2. The Merit\Livingston ASCII implementation should not be the preferred > method as it is less flexible. AFAIK, it isn't. Since the RFC says "should be supported as undistinguished octets" that means that is the "preferred method". -- Dale E. Reed Jr. (daler@iea-software.com) _________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue Dec 22 07:45:32 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27520 for ; Tue, 22 Dec 1998 07:45:31 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id EAA10228; Tue, 22 Dec 1998 04:37:52 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id EAA00875 for ietf-radius-outgoing; Tue, 22 Dec 1998 04:37:44 -0800 (PST) Message-ID: From: Jonathan Garini To: ietf-radius@livingston.com Cc: "'Dale E. Reed Jr.'" Subject: RE: (radius) Proxy state - String or Octets? Date: Tue, 22 Dec 1998 14:33:49 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Jonathan Garini > > First of all, strings are NOT null terminated in the RADIUS protocol, > since we have a length specifier. Any implementation relying on NULL > terminated strings is broken. IMHO. This has nothing to do > with how they > are stored by the server, just how they are tranmitted over the wire. > However, with undistringuied octets it is possible to include a 0 byte > at the end as as NULL (which should not cause a problem, since its not > a string and you shouldn't be using string functions on the data > portion). > Exactly. Apparently Livingston\Merit does not work this way. > > If we try to send the field as undistinguished octets it > does not work with > > Merit\Livingston. > > Can you expand on this? What doesn't work? What happens in Livingston\Merit is that they do not accept this attribute as octets but rather as a string, and since the octets sent by us contain \0 (line terminator when used as a string), they (Livingston\Merit) truncate this attribute, and the user can not be authenticated. > > > My thoughts are that: > > > > 1. SHOULD is not good here as it does not allow > interoperability between > > different Radius Servers. > > I agree. > > > 2. The Merit\Livingston ASCII implementation should not be > the preferred > > method as it is less flexible. > > AFAIK, it isn't. Since the RFC says "should be supported as > undistinguished > octets" that means that is the "preferred method". > > -- > Dale E. Reed Jr. (daler@iea-software.com) > _________________________________________________________________ > IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs > Internet Solutions for Today | http://www.iea-software.com > - > To unsubscribe, email 'majordomo@livingston.com' with > 'unsubscribe ietf-radius' in the body of the message. > - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue Dec 22 09:53:40 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29035 for ; Tue, 22 Dec 1998 09:53:39 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id GAA12295; Tue, 22 Dec 1998 06:45:21 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id GAA06779 for ietf-radius-outgoing; Tue, 22 Dec 1998 06:45:39 -0800 (PST) Message-Id: <199812221450.JAA21493@cryptocard.ott.igs.net> From: Alan DeKok To: ietf-radius@livingston.com Subject: Re: (radius) Proxy state - String or Octets? In-reply-to: Your message of "Tue, 22 Dec 1998 03:20:04 PST." <367F8064.9106375F@iea-software.com> Date: Tue, 22 Dec 1998 09:50:44 -0500 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Alan DeKok "Dale E. Reed Jr." writes: > > First of all, strings are NOT null terminated in the RADIUS protocol, > since we have a length specifier. Any implementation relying on NULL > terminated strings is broken. IMHO. Like Ascend? Their NAS boxes send strings with a trailing '\0', a zero-length STATE on an initial Access-Request (i.e. 0x18 0x02), and password attributes which are *not* 18+16n octets long. It's simple to work around these problems, but quite frustrating. Will there be a bakeoff and/or a suite of verification tests for Radius in the coming year? I'm uncomfortable with the idea of approving a standard when it's ambiguous enough to support multiple incompatible implementations. Alan DeKok. - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue Dec 22 10:04:31 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29282 for ; Tue, 22 Dec 1998 10:04:31 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id GAA12640; Tue, 22 Dec 1998 06:56:29 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id GAA07629 for ietf-radius-outgoing; Tue, 22 Dec 1998 06:57:03 -0800 (PST) Message-ID: From: Jonathan Garini To: ietf-radius@livingston.com Subject: RE: (radius) Proxy state - String or Octets? Date: Tue, 22 Dec 1998 16:53:08 +0200 Reply-By: Tue, 29 Dec 1998 16:57:00 +0200 X-Message-Flag: Follow up MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Jonathan Garini After Dale's comments in this matter we can now see that this not only a problem in the RFC but actually in the fact that Merit and Livingston do not comfort with the specification. I would appreciate if someone from Merit and Lucent will comment on this issue and notify whether they plan to fix this problem, as this is not theoretical but a real life problem we are facing. Regards, Jonathan. > -----Original Message----- > From: Dale E. Reed Jr. [mailto:daler@iea-software.com] > Sent: Tuesday, December 22, 1998 1:20 PM > To: Jonathan Garini > Cc: ietf-radius@livingston.com > Subject: Re: (radius) Proxy state - String or Octets? > > > Jonathan Garini wrote: > > > > The RFC states the the proxy state SHOULD be treated as > undistinguished > > octets. > > Merit and Livingstom implementations treat it as an NULL > terminated ASCII > > string field. > > First of all, strings are NOT null terminated in the RADIUS protocol, > since we have a length specifier. Any implementation relying on NULL > terminated strings is broken. IMHO. This has nothing to do > with how they > are stored by the server, just how they are tranmitted over the wire. > However, with undistringuied octets it is possible to include a 0 byte > at the end as as NULL (which should not cause a problem, since its not > a string and you shouldn't be using string functions on the data > portion). > > > If we try to send the field as undistinguished octets it > does not work with > > Merit\Livingston. > > Can you expand on this? What doesn't work? > > > My thoughts are that: > > > > 1. SHOULD is not good here as it does not allow > interoperability between > > different Radius Servers. > > I agree. > > > 2. The Merit\Livingston ASCII implementation should not be > the preferred > > method as it is less flexible. > > AFAIK, it isn't. Since the RFC says "should be supported as > undistinguished > octets" that means that is the "preferred method". > > -- > Dale E. Reed Jr. (daler@iea-software.com) > _________________________________________________________________ > IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs > Internet Solutions for Today | http://www.iea-software.com > - > To unsubscribe, email 'majordomo@livingston.com' with > 'unsubscribe ietf-radius' in the body of the message. > - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue Dec 22 10:29:40 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29791 for ; Tue, 22 Dec 1998 10:29:39 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id HAA13296; Tue, 22 Dec 1998 07:22:28 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id HAA09468 for ietf-radius-outgoing; Tue, 22 Dec 1998 07:23:08 -0800 (PST) Date: Tue, 22 Dec 98 10:19:39 EST From: David Bolen To: Jonathan Garini Cc: ietf-radius@livingston.com Subject: RE: (radius) Proxy state - String or Octets? In-Reply-To: Your message of Tue, 22 Dec 1998 14:33:49 +0200 Message-ID: Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: David Bolen Jonathan Garini writes: > Exactly. Apparently Livingston\Merit does not work this way. Yup - from what I could tell all String attributes are treated as NUL terminated information internally. I ran into this when trying to interoperate with a customer that was using one of the publically available Merit releases a while back. > What happens in Livingston\Merit is that they do not accept this attribute > as octets but rather as a string, and since the octets sent by us contain \0 > (line terminator when used as a string), they (Livingston\Merit) truncate > this attribute, and the user can not be authenticated. What I did in my server is add a server based flag for proxying such that if enabled for a given server, I "encoded" any Proxy-State attributes to remove any NULs (just simple byte prefixing with 0xFF). There's no other way that I know of to avoid the problem without changing the code (throughout it I thought at the time if you want to cover all String attributes) unless you can guarantee that your state will never have an octet of 0 in it (mine represented an internal state pointer, so it clearly could at times). > > > 1. SHOULD is not good here as it does not allow > > interoperability between > > > different Radius Servers. > > > > I agree. Well, except that I think the phrase about treating it as undistinguished octets is more of a server implementation issue than an interoperability one. Earlier in the section is the phrase: This Attribute is available to be sent by a proxy server to another server when forwarding an Access-Request and MUST be returned unmodified in the Access-Accept, Access-Reject or Access-Challenge. which it seems to me is enough of a statement to enforce interoperability. If a server wants to internally re-encode the value in some way which isn't using undistinguished octets I don't care as long as it gives it back to me unchanged as required by the above phrase. It's this MUST which the older Livingston/Merit code (I can't speak for any of the later, non-PD versions) breaks. -- David /-----------------------------------------------------------------------\ \ David Bolen \ Internet: db3l@ans.net / | ANS Communications, Inc. \ Phone: (914) 701-5327 | / 100 Manhattanville Rd, Purchase, NY 10577 \ Fax: (914) 701-5310 \ \-----------------------------------------------------------------------/ - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue Dec 22 11:02:24 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00522 for ; Tue, 22 Dec 1998 11:02:24 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id HAA14330; Tue, 22 Dec 1998 07:54:29 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id HAA12556 for ietf-radius-outgoing; Tue, 22 Dec 1998 07:54:42 -0800 (PST) From: William Bulley Message-Id: <199812221555.KAA14779@ohm.merit.edu> Subject: Re: (radius) Proxy state - String or Octets? To: jonathan@mail.extent.com Date: Tue, 22 Dec 1998 10:55:32 -0500 (EST) Cc: ietf-radius@livingston.com In-Reply-To: from "Jonathan Garini" at Dec 22, 98 04:53:08 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: William Bulley Content-Transfer-Encoding: 7bit According to Jonathan Garini: > > After Dale's comments in this matter we can now see that this not only a > problem in the RFC but actually in the fact that Merit and Livingston do not > comfort with the specification. > > I would appreciate if someone from Merit and Lucent will comment on this > issue and notify whether they plan to fix this problem, as this is not > theoretical but a real life problem we are facing. We are a little short staffed due to the holidays, etc. I have not looked at this part of the code now or in the recent past. Can you give me a version number where this is a "real life problem"? We have an upcoming release (due out early next year) and it would be easy to repair this in that version if it is a real problem and one which we still have. Regards, web... -- William Bulley Senior Systems Research Programmer Merit Network, Inc. Email: web@merit.edu 4251 Plymouth Road, Suite C Phone: (734) 764-9993 Ann Arbor, Michigan 48105-2785 Fax: (734) 647-3185 If entropy is increasing, where is it coming from? - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue Dec 22 13:51:40 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id NAA03484 for ; Tue, 22 Dec 1998 13:51:39 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id KAA22523; Tue, 22 Dec 1998 10:43:59 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id KAA04424 for ietf-radius-outgoing; Tue, 22 Dec 1998 10:44:57 -0800 (PST) Message-ID: From: Jonathan Garini To: "'William Bulley'" Cc: ietf-radius@livingston.com Subject: RE: (radius) Proxy state - String or Octets? Date: Tue, 22 Dec 1998 20:41:03 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Jonathan Garini > > We are a little short staffed due to the holidays, etc. > > I have not looked at this part of the code now or in the > recent past. Can you give me a version number where this > is a "real life problem"? > 2.4.23C running on Digital Unix. Regards, Jonathan. > We have an upcoming release (due out early next year) and > it would be easy to repair this in that version if it is > a real problem and one which we still have. > > Regards, > > web... > > -- > William Bulley Senior Systems Research Programmer > Merit Network, Inc. Email: web@merit.edu > 4251 Plymouth Road, Suite C Phone: (734) 764-9993 > Ann Arbor, Michigan 48105-2785 Fax: (734) 647-3185 > > If entropy is increasing, where is it coming from? > - > To unsubscribe, email 'majordomo@livingston.com' with > 'unsubscribe ietf-radius' in the body of the message. > - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue Dec 22 14:04:58 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id OAA03655 for ; Tue, 22 Dec 1998 14:04:56 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id KAA23161; Tue, 22 Dec 1998 10:57:44 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id KAA06351 for ietf-radius-outgoing; Tue, 22 Dec 1998 10:59:27 -0800 (PST) Message-ID: <367FEA01.AA8D53CA@iea-software.com> Date: Tue, 22 Dec 1998 10:50:41 -0800 From: "Dale E. Reed Jr." Organization: IEA Software, Inc. X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Alan DeKok CC: ietf-radius@livingston.com Subject: Re: (radius) Proxy state - String or Octets? References: <199812221450.JAA21493@cryptocard.ott.igs.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "Dale E. Reed Jr." Alan DeKok wrote: > > > First of all, strings are NOT null terminated in the RADIUS protocol, > > since we have a length specifier. Any implementation relying on NULL > > terminated strings is broken. IMHO. > > Like Ascend? Their NAS boxes send strings with a trailing '\0', a > zero-length STATE on an initial Access-Request (i.e. 0x18 0x02), and > password attributes which are *not* 18+16n octets long. > > It's simple to work around these problems, but quite frustrating. > > Will there be a bakeoff and/or a suite of verification tests for > Radius in the coming year? I'm uncomfortable with the idea of > approving a standard when it's ambiguous enough to support multiple > incompatible implementations. I still have a lot of the testing stuff from the previous bakeoff. We don't have a problem supporting a site to test RADIUS over the internet. We use to have an open site that anyone could use to test with RadiusNT. If there is interest in it, I can put the testing site back up after the first of the year, that would allow the vendors to register thier information on where to test and who is testing. It would all be a closed site that you would have to pre-register for and you could only see your results. -- Dale E. Reed Jr. (daler@iea-software.com) _________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue Dec 22 15:47:31 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id PAA06737 for ; Tue, 22 Dec 1998 15:47:30 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id MAA26664; Tue, 22 Dec 1998 12:37:24 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id MAA16465 for ietf-radius-outgoing; Tue, 22 Dec 1998 12:38:42 -0800 (PST) Message-ID: <368002ED.9E174C5E@uol.com.br> Date: Tue, 22 Dec 1998 18:37:01 -0200 From: Alberto Ferreira Delgado X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Lista Radius Subject: (radius) Total Control Hiper Arc Content-Type: multipart/mixed; boundary="------------76E98F44FBD9DBABEC81DDE7" Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Alberto Ferreira Delgado This is a multi-part message in MIME format. --------------76E98F44FBD9DBABEC81DDE7 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I changed radius to send the attribute Filter-Id with the filter to be aplied for each user, i am using Merit Radius 2.4.23C , with Portmaster 4 this works well , but with Total Control Hiper Arc , we had some problems. In Portmaster i created to filters on NAS like "filter.in" and "filter.out" , and i perform the attribute Filter-Id with the string "filter". The attribute Filter_Id is the correct parameter to set filter in Total Control Hiper Arc or there is another ? There is something diferent to do for Total Control Hiper Arc in this attribute ? Regards, -- ---------------------------------------------------------------------- Live for Love, for without Love you don't live. ---------------------------------------------------------------------- --------------76E98F44FBD9DBABEC81DDE7 Content-Type: text/x-vcard; charset=us-ascii; name="afdelgado.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Alberto Ferreira Delgado Content-Disposition: attachment; filename="afdelgado.vcf" begin:vcard n:Delgado;Alberto Ferreira tel;cell:9155-7263 tel;home:4799-0470 tel;work:224-7596 x-mozilla-html:TRUE org:Universo Online;Tecnologia adr:;;Al. Barão de limeira, 425;São Paulo;São Paulo;01202-000;Brasil version:2.1 email;internet:afdelgado@uol.com.br title:Analista de Sistemas fn:Alberto Ferreira Delgado end:vcard --------------76E98F44FBD9DBABEC81DDE7-- - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue Dec 22 20:21:22 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id UAA22980 for ; Tue, 22 Dec 1998 20:21:21 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id RAA02760; Tue, 22 Dec 1998 17:13:52 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id RAA12715 for ietf-radius-outgoing; Tue, 22 Dec 1998 17:14:15 -0800 (PST) Message-ID: From: "Nair, Shibu (MED, Wipro Systems, Inc)" To: ietf-radius@livingston.com Subject: (radius) Radius with 3Com Total Control Date: Tue, 22 Dec 1998 11:24:35 -0600 X-Mailer: Internet Mail Service (5.5.2232.9) Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "Nair, Shibu (MED, Wipro Systems, Inc)" Hi Iam using Livingston Radius (version 2.0) to authenticate the users who need dialin access. I have 3 Com's Total Control setupfor dial in access which is configured for the same radius server to authenticate the users. All clients are able to login to our network after authenticating with Radius server. But in the radius log file iam able to see "Request-Authenticator = Unverified" Any idea ? Pls help me to solve this error mesg... TIA Regards Shibu Complete log file for dialin PPP event is given below, Tue Dec 22 10:03:18 1998 User-Name = "msa3515p" NAS-IP-Address = 3.87.88.252 Acct-Status-Type = Stop Acct-Session-Id = "17367118" Acct-Delay-Time = 0 Acct-Authentic = RADIUS Service-Type = Framed-User NAS-Port-Type = Async NAS-Port = 1 Calling-Station-Id = "" Called-Station-Id = "" Framed-Protocol = PPP Framed-IP-Address = 3.87.90.10 Acct-Session-Time = 827 Acct-Terminate-Cause = User-Request Acct-Input-Octets = 10703 Acct-Output-Octets = 624 Timestamp = 914342598 Request-Authenticator = Unverified - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue Dec 22 21:25:23 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id VAA26954 for ; Tue, 22 Dec 1998 21:25:22 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id SAA03782; Tue, 22 Dec 1998 18:17:45 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id SAA15770 for ietf-radius-outgoing; Tue, 22 Dec 1998 18:18:00 -0800 (PST) From: Sctgdjk@worldnet.att.net Date: Tue, 22 Dec 1998 20:01:08 -0600 Message-ID: To: people3@aol.com Subject: (radius) Home Based Travel Biz! Free Cruise! Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Sctgdjk@worldnet.att.net $100,000+ FIRST YEAR INCOME * Earn $2000-$5000 weekly-Starting Within 1-4 weeks! * 78% Profit Paid Daily * No Selling * No Risk Guarantee * Work from home, No overhead, or employees. * High Tech Training & Support * Not MLM, 100x more profitable * Multibillion Dollar Travel Industry The most incredible part of our business is that ALL MY CLIENTS CALL ME! DO YOU QUALIFY FOR OUR MENTOR PROGRAM? ACCEPTING ONLY 12 NEW ASSOCIATES..... This is not a hobby! Serious Inquiries Only! 24 Hour Toll Free Message No obligation! 1-800-320-9895 If you're an entrepreneur or have always wanted to be your own BOSS, read on. We supply state-of-the-art training and a support system that allows you to work your business from your home with just a phone-without cold calling. DO NOT CALL ME IF YOU'RE LOOKING FOR A "GET RICH QUICK" SCHEME or some extra cash or if you're lazy. We are only looking for FOCUSED, serious entrepreneurs. (PT/FT) with the DESIRE to improve their lifestyle immediately. To be removed from out mailing list, please reply to: Movingman54@hotmail.com Any vulgarity will be blocked and your request to be removed will automatically be deleted. - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Wed Dec 23 08:04:34 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id IAA27185 for ; Wed, 23 Dec 1998 08:04:33 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id EAA10923; Wed, 23 Dec 1998 04:54:38 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id EAA10049 for ietf-radius-outgoing; Wed, 23 Dec 1998 04:53:44 -0800 (PST) From: William Bulley Message-Id: <199812231254.HAA16386@ohm.merit.edu> Subject: Re: (radius) Proxy state - String or Octets? To: jonathan@mail.extent.com (Jonathan Garini) Date: Wed, 23 Dec 1998 07:54:34 -0500 (EST) Cc: ietf-radius@livingston.com In-Reply-To: from "Jonathan Garini" at Dec 22, 98 08:41:03 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: William Bulley According to Jonathan Garini: > > 2.4.23C running on Digital Unix. You do realize (don't you?) that this version is old/buggy/obsolete and very non-RFC conformant. This version dates from mid-1996 and has been superceded by our 3.6B version. http://www.merit.edu/aaa/basicsvr.html Regards, web... -- William Bulley Senior Systems Research Programmer Merit Network, Inc. Email: web@merit.edu 4251 Plymouth Road, Suite C Phone: (734) 764-9993 Ann Arbor, Michigan 48105-2785 Fax: (734) 647-3185 If entropy is increasing, where is it coming from? - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Wed Dec 23 08:08:21 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id IAA27243 for ; Wed, 23 Dec 1998 08:08:20 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id FAA11099; Wed, 23 Dec 1998 05:00:44 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id FAA10417 for ietf-radius-outgoing; Wed, 23 Dec 1998 05:02:36 -0800 (PST) From: William Bulley Message-Id: <199812231303.IAA16493@ohm.merit.edu> Subject: Re: (radius) Total Control Hiper Arc To: afdelgado@uol.com.br Date: Wed, 23 Dec 1998 08:03:21 -0500 (EST) Cc: ietf-radius@livingston.com In-Reply-To: <368002ED.9E174C5E@uol.com.br> from "Alberto Ferreira Delgado" at Dec 22, 98 06:37:01 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: William Bulley According to Alberto Ferreira Delgado: > > I changed radius to send the attribute Filter-Id with the filter to > be aplied for each user, i am using Merit Radius 2.4.23C , with > Portmaster 4 this works well , but with Total Control Hiper Arc , we had > some problems. > In Portmaster i created to filters on NAS like "filter.in" and > "filter.out" , and i perform the attribute Filter-Id with the string > "filter". > The attribute Filter_Id is the correct parameter to set filter in > Total Control Hiper Arc or there is another ? > There is something diferent to do for Total Control Hiper Arc in > this attribute ? This should be a question asked of aaa-support@merit.edu But first you should replace version 2.4.23C with our 3.6B version The older version does not support USR/3COM NAS units, the newer version does. Regards, web... -- William Bulley Senior Systems Research Programmer Merit Network, Inc. Email: web@merit.edu 4251 Plymouth Road, Suite C Phone: (734) 764-9993 Ann Arbor, Michigan 48105-2785 Fax: (734) 647-3185 If entropy is increasing, where is it coming from? - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Wed Dec 23 08:26:12 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id IAA27558 for ; Wed, 23 Dec 1998 08:26:11 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id FAA11360; Wed, 23 Dec 1998 05:18:49 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id FAA11163 for ietf-radius-outgoing; Wed, 23 Dec 1998 05:20:32 -0800 (PST) Message-ID: From: Jonathan Garini To: "'William Bulley'" Cc: ietf-radius@livingston.com Subject: RE: (radius) Proxy state - String or Octets? Date: Wed, 23 Dec 1998 15:16:25 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Jonathan Garini > > > > 2.4.23C running on Digital Unix. > > You do realize (don't you?) that this version is old/buggy/obsolete > and very non-RFC conformant. This version dates from mid-1996 and > has been superceded by our 3.6B version. > > http://www.merit.edu/aaa/basicsvr.html > I do now. Please mind that we are not the ones with the problem but a customer of us who is trying to use Extent RBS Radius Server in proxy environment with Merit. So, I understand from your response that this problem is solved in the latest version? Regards, Jonathan. > Regards, > > web... > > -- > William Bulley Senior Systems Research Programmer > Merit Network, Inc. Email: web@merit.edu > 4251 Plymouth Road, Suite C Phone: (734) 764-9993 > Ann Arbor, Michigan 48105-2785 Fax: (734) 647-3185 > > If entropy is increasing, where is it coming from? > - > To unsubscribe, email 'majordomo@livingston.com' with > 'unsubscribe ietf-radius' in the body of the message. > - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Wed Dec 23 08:49:48 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id IAA28325 for ; Wed, 23 Dec 1998 08:49:47 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id FAA11724; Wed, 23 Dec 1998 05:39:51 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id FAA11971 for ietf-radius-outgoing; Wed, 23 Dec 1998 05:41:40 -0800 (PST) From: William Bulley Message-Id: <199812231342.IAA16942@ohm.merit.edu> Subject: Re: (radius) Proxy state - String or Octets? To: jonathan@mail.extent.com (Jonathan Garini) Date: Wed, 23 Dec 1998 08:42:30 -0500 (EST) Cc: ietf-radius@livingston.com In-Reply-To: from "Jonathan Garini" at Dec 23, 98 03:16:25 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: William Bulley According to Jonathan Garini: > > I do now. Please mind that we are not the ones with the problem but a > customer of us who is trying to use Extent RBS Radius Server in proxy > environment with Merit. > > So, I understand from your response that this problem is solved in the > latest version? I didn't say that. But the older version is a certain cause of user problems. Most of us are doing family things this time of year. I have noted the question for investigation when we get back to the office next year. Regards, web... -- William Bulley Senior Systems Research Programmer Merit Network, Inc. Email: web@merit.edu 4251 Plymouth Road, Suite C Phone: (734) 764-9993 Ann Arbor, Michigan 48105-2785 Fax: (734) 647-3185 If entropy is increasing, where is it coming from? - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Wed Dec 23 15:11:02 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id PAA06811 for ; Wed, 23 Dec 1998 15:11:01 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id MAA23185; Wed, 23 Dec 1998 12:03:03 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id MAA18655 for ietf-radius-outgoing; Wed, 23 Dec 1998 12:03:18 -0800 (PST) Date: Wed, 23 Dec 1998 13:59:28 -0600 (CST) From: "Russell J. LeBar" To: "Nair, Shibu (MED, Wipro Systems, Inc)" cc: ietf-radius@livingston.com Subject: Re: (radius) Radius with 3Com Total Control In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "Russell J. LeBar" On Tue, 22 Dec 1998, Nair, Shibu (MED, Wipro Systems, Inc) wrote: > Iam using Livingston Radius (version 2.0) to authenticate the users who > need dialin access. I have 3 Com's Total Control setupfor dial in > access which is configured for the same radius server to authenticate > the users. > > All clients are able to login to our network after authenticating with > Radius server. But in > the radius log file iam able to see "Request-Authenticator = Unverified" > Any idea ? > Pls help me to solve this error mesg... USR's do not send the secret key/authenticator in accounting packets which is presumably your problem. Anyone know if they have released newer firmware to correct this?/ - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Wed Dec 23 15:55:42 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id PAA08989 for ; Wed, 23 Dec 1998 15:55:42 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id MAA25825; Wed, 23 Dec 1998 12:47:47 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id MAA24938 for ietf-radius-outgoing; Wed, 23 Dec 1998 12:49:24 -0800 (PST) From: Pat.Calhoun@eng.sun.com (Patrice Calhoun) Message-Id: <199812232045.MAA00713@hsmpka.eng.sun.com> Date: Wed, 23 Dec 1998 12:43:41 -0800 To: "Russell J. LeBar" , "Nair, Shibu (MED, Wipro Systems, Inc)" Cc: Subject: Re: (radius) Radius with 3Com Total Control X-Mailer: Sun NetMail 2.2.3 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Pat.Calhoun@eng.sun.com (Patrice Calhoun) >On Tue, 22 Dec 1998, Nair, Shibu (MED, Wipro Systems, Inc) wrote: > >> Iam using Livingston Radius (version 2.0) to authenticate the users who >> need dialin access. I have 3 Com's Total Control setupfor dial in >> access which is configured for the same radius server to authenticate >> the users. >> >> All clients are able to login to our network after authenticating with >> Radius server. But in >> the radius log file iam able to see "Request-Authenticator = Unverified" >> Any idea ? >> Pls help me to solve this error mesg... > > >USR's do not send the secret key/authenticator in accounting packets which >is presumably your problem. Anyone know if they have released newer >firmware to correct this?/ I believe this was added a long time ago. It could be that it is disabled for backward compatibility. PatC > >- >To unsubscribe, email 'majordomo@livingston.com' with >'unsubscribe ietf-radius' in the body of the message. - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Wed Dec 23 23:14:50 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id XAA24167 for ; Wed, 23 Dec 1998 23:14:49 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id UAA15528; Wed, 23 Dec 1998 20:07:15 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id UAA07782 for ietf-radius-outgoing; Wed, 23 Dec 1998 20:07:16 -0800 (PST) Message-ID: <3681BE30.8BA5E29D@eproperties.com> Date: Wed, 23 Dec 1998 23:08:16 -0500 From: E-PROPERTIES X-Mailer: Mozilla 4.5 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: post@eproperties.com Subject: (radius) Real Estate Internet Solutions References: Content-Type: multipart/alternative; boundary="------------9F648039F5D08C5466DF82F5" Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: E-PROPERTIES --------------9F648039F5D08C5466DF82F5 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Please accept this invitation to to visit E-PROPERTIES web site. E-PROPERTIES is a Real Estate & Travel Guide Online where you can post and/or search any kind of property in USA and in the World. Contact us for more information. http://www.eproperties.com We hope you will find E-PROPERTIES helpful for your research and that you could come back to visit us many times after. E-PROPERTIES 201 Ascan Ave. Forest Hills, NY 11375, USA Tel.: 718 268-7623 info@eproperties.com --------------9F648039F5D08C5466DF82F5 Content-Type: text/html; charset=iso-8859-2 Content-Transfer-Encoding: 7bit
Please accept this invitation to to visit E-PROPERTIES web site.
E-PROPERTIES is a Real Estate & Travel Guide Online
where you can post and/or search any kind of property in USA and in the World.
Contact us for more information.
http://www.eproperties.com
We hope you will  find E-PROPERTIES helpful for your research and that  you could come back to visit us many times after.

E-PROPERTIES
201 Ascan Ave.
Forest Hills, NY 11375, USA
Tel.: 718 268-7623
info@eproperties.com




--------------9F648039F5D08C5466DF82F5--

-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe ietf-radius' in the body of the message.


From owner-ietf-radius@livingston.com  Thu Dec 31 10:00:52 1998
Received: from bast.livingston.com (bast.livingston.com [149.198.247.2])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id KAB20889
	for ; Thu, 31 Dec 1998 10:00:51 -0500 (EST)
Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id GAA13529; Thu, 31 Dec 1998 06:53:01 -0800 (PST)
Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id GAA22793 for ietf-radius-outgoing; Thu, 31 Dec 1998 06:50:13 -0800 (PST)
From: KatQV11@aol.com
Message-ID: 
Date: Thu, 31 Dec 1998 09:27:04 EST
Mime-Version: 1.0
Subject: (radius) Increase Business by ACCEPTING  CREDIT CARDS!!!
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
X-Mailer: AOL 3.0 for Windows 95 sub 18
Sender: owner-ietf-radius@livingston.com
Precedence: bulk
Reply-To: KatQV11@aol.com

ACCEPT CREDIT CARDS!!
PRE-APPROVED APPLICATION
Good Credit/Bad Credit/No Credit

NO APPLICATION FEES 
For a Limited Time Only!
Regular $195.00 Application Fee Waived For This Offer!

Increase Your Business Up To 100% Or More, 
Just By Accepting Credit Cards!
This Means More Customers...More Orders...More Money!
We Specialize in Home Based Businesses - Apply Today!
Accept Visa, Mastercard, American Express, and Discover!

Apply Now by visiting our Online Application Site!
We are overwhelmed with Responses...

http://www.systemwave.com/merchant/


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
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, please 
email system@systemwave.com with the word unsubscribe in 
the subject.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe ietf-radius' in the body of the message.