From owner-nasreq@kull.rutgers.edu Fri Jul 28 20:03:32 2000 Received: from kull.rutgers.edu (kull.rutgers.edu [128.6.21.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28927 for ; Fri, 28 Jul 2000 20:03:31 -0400 (EDT) Received: (from majordom@localhost) by kull.rutgers.edu (8.8.8+Sun/8.8.8) id TAA23081 for nasreq-outgoing; Fri, 28 Jul 2000 19:29:44 -0400 (EDT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by kull.rutgers.edu (8.8.8+Sun/8.8.8) with ESMTP id TAA23070 for ; Fri, 28 Jul 2000 19:29:42 -0400 (EDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id QAA11069; Fri, 28 Jul 2000 16:29:39 -0700 (PDT) Message-Id: <200007282329.QAA11069@boreas.isi.edu> To: IETF-Announce: ; Subject: nasreq RFC 2881 on NASreq NAS Model Cc: rfc-ed@ISI.EDU, nasreq@tdmx.rutgers.edu Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 28 Jul 2000 16:29:39 -0700 From: RFC Editor Sender: owner-nasreq@tdmx.rutgers.edu Precedence: bulk --NextPart A new Request for Comments is now available in online RFC libraries. RFC 2881 Title: Network Access Server Requirements Next Generation (NASREQNG) NAS Model Author(s): D. Mitton, M. Beadles Status: Informational Date: July 2000 Mailbox: dmitton@nortelnetworks.com, mbeadles@smartpipes.com Pages: 20 Characters: 45024 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-nesreq-nasmodel-02.txt URL: ftp://ftp.isi.edu/in-notes/rfc2881.txt This document describes the terminology and gives a model of typical Network Access Server (NAS). The purpose of this effort is to set the reference space for describing and evaluating NAS service protocols, such as RADIUS (RFCs 2865, 2866) [1], [2] and follow-on efforts like AAA Working Group, and the Diameter protocol [3]. These are protocols for carrying user service information for authentication, authorization, accounting, and auditing, between a Network Access Server which desires to authenticate its incoming calls and a shared authentication server. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <000728162600.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2881 --OtherAccess Content-Type: Message/External-body; name="rfc2881.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <000728162600.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From owner-nasreq@kull.rutgers.edu Fri Jul 28 20:03:59 2000 Received: from kull.rutgers.edu (kull.rutgers.edu [128.6.21.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29044 for ; Fri, 28 Jul 2000 20:03:58 -0400 (EDT) Received: (from majordom@localhost) by kull.rutgers.edu (8.8.8+Sun/8.8.8) id TAA23866 for nasreq-outgoing; Fri, 28 Jul 2000 19:33:25 -0400 (EDT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by kull.rutgers.edu (8.8.8+Sun/8.8.8) with ESMTP id TAA23862 for ; Fri, 28 Jul 2000 19:33:24 -0400 (EDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id QAA11501; Fri, 28 Jul 2000 16:33:22 -0700 (PDT) Message-Id: <200007282333.QAA11501@boreas.isi.edu> To: IETF-Announce: ; Subject: nasreq RFC 2882 on Extended RADIUS Practices Cc: rfc-ed@ISI.EDU, nasreq@tdmx.rutgers.edu Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 28 Jul 2000 16:33:21 -0700 From: RFC Editor Sender: owner-nasreq@tdmx.rutgers.edu Precedence: bulk --NextPart A new Request for Comments is now available in online RFC libraries. RFC 2882 Title: Network Access Servers Requirements: Extended RADIUS Practices Author(s): D. Mitton Status: Informational Date: July 2000 Mailbox: dmitton@nortelnetworks.com Pages: 16 Characters: 31431 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-nesreq-ext-radiuspract-03.txt URL: ftp://ftp.isi.edu/in-notes/rfc2882.txt This document describes current practices implemented in NAS products that go beyond the scope of the RADIUS RFCs 2138, 2139. The purpose of this effort is to give examples that show the need for addressing and standardizing these types of ad-hoc functions. Since many of these features require a matching server support component, the ability to deploy and manage interoperable NAS and AAA server products is severely hindered. These practices are documented here to show functions that are obviously desired in developing future AAA protocols for NAS deployment. This document is a product of the Network Access Server Requirements Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <000728163050.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2882 --OtherAccess Content-Type: Message/External-body; name="rfc2882.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <000728163050.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart--