From owner-nasreq@tdmx.rutgers.edu Wed Aug 4 15:19:18 1999 Received: from the-dread-pirate-roberts.rutgers.edu (the-dread-pirate-roberts.rutgers.edu [128.6.21.44]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19243 for ; Wed, 4 Aug 1999 15:19:18 -0400 (EDT) Received: (from majordom@localhost) by the-dread-pirate-roberts.rutgers.edu (8.8.8/8.8.8) id PAA10858; Wed, 4 Aug 1999 15:19:20 -0400 (EDT) Date: Wed, 4 Aug 1999 15:19:20 -0400 (EDT) Message-Id: <199908041919.PAA10858@the-dread-pirate-roberts.rutgers.edu> X-Authentication-Warning: the-dread-pirate-roberts.rutgers.edu: majordom set sender to owner-nasreq@tdmx.rutgers.edu using -f To: nasreq-archive@ietf.org From: Majordomo@tdmx.rutgers.edu Subject: Welcome to nasreq Reply-To: Majordomo@tdmx.rutgers.edu -- Welcome to the nasreq mailing list! Please save this message for future reference. Thank you. If you ever want to remove yourself from this mailing list, you can send mail to with the following command in the body of your email message: unsubscribe nasreq or from another account, besides nasreq-archive@lists.ietf.org: unsubscribe nasreq nasreq-archive@lists.ietf.org If you ever need to get in contact with the owner of the list, (if you have trouble unsubscribing, or have questions about the list itself) send email to . This is the general rule for most mailing lists when you need to contact a human. Here's the general information for the list you've subscribed to, in case you don't already have it: network access server requirements From owner-nasreq@the-dread-pirate-roberts.rutgers.edu Mon Aug 30 06:02:54 1999 Received: from the-dread-pirate-roberts.rutgers.edu (the-dread-pirate-roberts.rutgers.edu [128.6.21.44]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19219; Mon, 30 Aug 1999 06:02:53 -0400 (EDT) Received: (from majordom@localhost) by the-dread-pirate-roberts.rutgers.edu (8.8.8/8.8.8) id FAA23026 for nasreq-outgoing; Mon, 30 Aug 1999 05:46:25 -0400 (EDT) X-Authentication-Warning: the-dread-pirate-roberts.rutgers.edu: majordom set sender to owner-nasreq@tdmx.rutgers.edu using -f Received: from btm4r4.alcatel.be (btm4r4.alcatel.be [195.207.101.110]) by the-dread-pirate-roberts.rutgers.edu (8.8.8/8.8.8) with ESMTP id FAA23022 for ; Mon, 30 Aug 1999 05:46:23 -0400 (EDT) Received: from btmq9s.rc.bel.alcatel.be (btmq9s.rc.bel.alcatel.be [138.203.65.182]) by btm4r4.alcatel.be (8.9.1a/8.9.1) with ESMTP id LAA02105 for ; Mon, 30 Aug 1999 11:45:52 +0200 (MET DST) Received: from rc.bel.alcatel.be ([138.203.66.115]) by btmq9s.rc.bel.alcatel.be (8.8.8+Sun/8.8.8) with ESMTP id LAA04301; Mon, 30 Aug 1999 11:45:59 +0200 (MET DST) Message-ID: <37CA52C2.D918B90C@rc.bel.alcatel.be> Date: Mon, 30 Aug 1999 11:45:38 +0200 From: Ronnie Ekstein X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: nasreq@tdmx.rutgers.edu Subject: nasreq draft-ekstein-roamops-protcomp-00.txt Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by the-dread-pirate-roberts.rutgers.edu id FAA23023 Sender: owner-nasreq@tdmx.rutgers.edu Precedence: bulk Content-Transfer-Encoding: 8bit hi *, we have recently submitted draft-ekstein-roamops-protcomp-00.txt. The draft gives a protocol comparison between the RADIUS, DIAMETER and COPS protocols. Although it has been submitted to the roamops group, we think it is of relevance too for nasreq and aaa WG. We would be happy to receive improvements/comments on this document. Abstract -------- Although RADIUS, DIAMETER and COPS all serve the purpose of distributing (some subfunctions of) the AAA service, there are many differences between these protocols. These differences (based on the protocol operation) are briefly compared with their possible implications on the functionality or applicability of the protocol. Comparison is based upon : - the relative support of authentication, authorization, accounting and transport of configuration information - the extensibility in terms of messages and attributes - the support of unsolicited messages - the reliability in operation - the scalability - the way they provide security, both on a hop-by-hop and end-to-end basis (in proxy situations) The draft further discusses the compliance of the RADIUS, DIAMETER and COPS protocols to the requirements for the provisioning of "roaming capability" for dialup Internet users outlined in RFC 2477.   This is at large 'work in progress' and we solicit any input that might help us to improve the quality of the draft. Kind regards, Ronnie Ekstein Yves T'Joens Bernard Sales From owner-nasreq@the-dread-pirate-roberts.rutgers.edu Tue Aug 31 11:40:12 1999 Received: from the-dread-pirate-roberts.rutgers.edu (the-dread-pirate-roberts.rutgers.edu [128.6.21.44]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22078; Tue, 31 Aug 1999 11:40:11 -0400 (EDT) Received: (from majordom@localhost) by the-dread-pirate-roberts.rutgers.edu (8.8.8/8.8.8) id KAA01663 for nasreq-outgoing; Tue, 31 Aug 1999 10:53:26 -0400 (EDT) X-Authentication-Warning: the-dread-pirate-roberts.rutgers.edu: majordom set sender to owner-nasreq@tdmx.rutgers.edu using -f Received: from btm4r4.alcatel.be (btm4r4.alcatel.be [195.207.101.110]) by the-dread-pirate-roberts.rutgers.edu (8.8.8/8.8.8) with ESMTP id KAA01659 for ; Tue, 31 Aug 1999 10:53:23 -0400 (EDT) Received: from btmq9s.rc.bel.alcatel.be (btmq9s.rc.bel.alcatel.be [138.203.65.182]) by btm4r4.alcatel.be (8.9.1a/8.9.1) with ESMTP id QAA25863 for ; Tue, 31 Aug 1999 16:52:52 +0200 (MET DST) Received: from rc.bel.alcatel.be ([138.203.66.115]) by btmq9s.rc.bel.alcatel.be (8.8.8+Sun/8.8.8) with ESMTP id QAA00162; Tue, 31 Aug 1999 16:52:58 +0200 (MET DST) Message-ID: <37CBEC33.39354E40@rc.bel.alcatel.be> Date: Tue, 31 Aug 1999 16:52:35 +0200 From: Ronnie Ekstein X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: nasreq@tdmx.rutgers.edu Subject: nasreq draft-ekstein-roamops-protcomp-00.txt Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by the-dread-pirate-roberts.rutgers.edu id KAA01660 Sender: owner-nasreq@tdmx.rutgers.edu Precedence: bulk Content-Transfer-Encoding: 8bit The I-D is now available at : ftp://ftp.ietf.org/internet-drafts/draft-ekstein-roamops-protcomp-00.txt or http://www.ietf.org/internet-drafts/draft-ekstein-roamops-protcomp-00.txt Kind regards, Ronnie Ekstein Ronnie Ekstein wrote: > hi *, > > we have recently submitted draft-ekstein-roamops-protcomp-00.txt. The > draft gives a protocol comparison between the RADIUS, DIAMETER and COPS > protocols. Although it has been submitted to the roamops group, we think > > it is of relevance too for nasreq and aaa WG. > > We would be happy to receive improvements/comments on this document. > > Abstract > -------- > > Although RADIUS, DIAMETER and COPS all serve the purpose of distributing > > (some subfunctions of) the AAA service, there are many differences > between these protocols. > > These differences (based on the protocol operation) are briefly compared > > with their possible implications on the functionality or applicability > of the protocol. > > Comparison is based upon : > - the relative support of authentication, authorization, accounting and > transport of configuration information > - the extensibility in terms of messages and attributes > - the support of unsolicited messages > - the reliability in operation > - the scalability > - the way they provide security, both on a hop-by-hop and end-to-end > basis (in proxy situations) > > The draft further discusses the compliance of the RADIUS, DIAMETER and > COPS protocols to the requirements for the provisioning of "roaming > capability" for dialup Internet users outlined in RFC 2477. >   > > This is at large 'work in progress' and we solicit any input that might > help us to improve the quality of the draft. > > Kind regards, > > Ronnie Ekstein > Yves T'Joens > Bernard Sales From owner-nasreq@the-dread-pirate-roberts.rutgers.edu Tue Aug 31 21:17:20 1999 Received: from the-dread-pirate-roberts.rutgers.edu (the-dread-pirate-roberts.rutgers.edu [128.6.21.44]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04881; Tue, 31 Aug 1999 21:17:20 -0400 (EDT) Received: (from majordom@localhost) by the-dread-pirate-roberts.rutgers.edu (8.8.8/8.8.8) id UAA04491 for nasreq-outgoing; Tue, 31 Aug 1999 20:35:53 -0400 (EDT) X-Authentication-Warning: the-dread-pirate-roberts.rutgers.edu: majordom set sender to owner-nasreq@tdmx.rutgers.edu using -f Received: from shell4.ba.best.com (root@shell4.ba.best.com [206.184.139.135]) by the-dread-pirate-roberts.rutgers.edu (8.8.8/8.8.8) with ESMTP id UAA04487 for ; Tue, 31 Aug 1999 20:35:51 -0400 (EDT) Received: (from megazone@localhost) by shell4.ba.best.com (8.9.3/8.9.2/best.sh) id RAA16826; Tue, 31 Aug 1999 17:35:22 -0700 (PDT) Message-Id: <199909010035.RAA16826@shell4.ba.best.com> Subject: Re: nasreq draft-ekstein-roamops-protcomp-00.txt In-Reply-To: <37CBEC33.39354E40@rc.bel.alcatel.be> from Ronnie Ekstein at "Aug 31, 99 04:52:35 pm" To: eksteinr@rc.bel.alcatel.be (Ronnie Ekstein) Date: Tue, 31 Aug 1999 17:35:22 -0700 (PDT) Cc: nasreq@tdmx.rutgers.edu 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-nasreq@tdmx.rutgers.edu Precedence: bulk Content-Transfer-Encoding: 7bit ---cut--- Neither RADIUS nor COPS support explicitly vendor specific extensibility. ---cut--- That is an error. RADIUS most certainly does - the attribute is called "Vendor-Specific". I think this document would be more effective if it took into account the drafts that enhance and extend RFCs 2138/2139 as there is a lot of capability not in those two RFCs but that does exist and is in common use today. ---cut--- A RADIUS client and server maintain between them a shared secret. A RADIUS server can authenticate the clients request only if the shared secret has been used in the context of password hiding. A User-Password attribute is the plain-text user password encoded with the MD5 digest of the octet stream consisting of the shared secret and the Authenticator. If the User-Password attribute is not available, no other explicit authentication information is available within the request. ---cut--- This is also no longer the case. The more recent revisions to RADIUS talk to this point and there are other items to use in place of the User-Password. You mention Signature later in your draft. ---cut--- RADIUS only provides for hiding of the User-Password attribute. Other attributes are send in cleartext ---cut--- ARAP-Password, CHAP-Password (this is off the top of my head, so I may be slightly off on the names), etc, are also protected if used. -MZ, CISSP #3762 -- 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!