From owner-nasreq@kull.rutgers.edu  Thu May 18 07:43:47 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 HAA03004
	for <nasreq-archive@odin.ietf.org>; Thu, 18 May 2000 07:43:44 -0400 (EDT)
Received: (from majordom@localhost)
	by kull.rutgers.edu (8.8.8+Sun/8.8.8) id GAA19756
	for nasreq-outgoing; Thu, 18 May 2000 06:54:44 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by kull.rutgers.edu (8.8.8+Sun/8.8.8) with ESMTP id GAA19745
	for <nasreq@tdmx.rutgers.edu>; Thu, 18 May 2000 06:54:43 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02183;
	Thu, 18 May 2000 06:54:42 -0400 (EDT)
Message-Id: <200005181054.GAA02183@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: nasreq@tdmx.rutgers.edu
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-nasreq-ext-radiuspract-03.txt
Date: Thu, 18 May 2000 06:54:41 -0400
Sender: owner-nasreq@tdmx.rutgers.edu
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Network Access Server Requirements Working Group of the IETF.

	Title		: Network Access Servers Requirements: Extended RADIUS 
                          Practices
	Author(s)	: D. Mitton
	Filename	: draft-ietf-nasreq-ext-radiuspract-03.txt
	Pages		: 18
	Date		: 17-May-00
	
This document describes current practices implemented in NAS products
that go beyond the scope of the RADIUS RFCs 2138, 2139 [1,2]. The pur-
pose of this effort is to give examples that show the need for address-
ing 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 draft submission of the Network Access Server
Requirements (NASREQ) Working Group of the Internet Engineering Task
Force (IETF).  Comments should be submitted to the mailing list
nasreq@tdmx.rutgers.edu.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-nasreq-ext-radiuspract-03.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-nasreq-ext-radiuspract-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-nasreq-ext-radiuspract-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20000517092327.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-nasreq-ext-radiuspract-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-nasreq-ext-radiuspract-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20000517092327.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-nasreq@kull.rutgers.edu  Thu May 18 07:49:10 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 HAA03090
	for <nasreq-archive@odin.ietf.org>; Thu, 18 May 2000 07:49:10 -0400 (EDT)
Received: (from majordom@localhost)
	by kull.rutgers.edu (8.8.8+Sun/8.8.8) id GAA19725
	for nasreq-outgoing; Thu, 18 May 2000 06:54:39 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by kull.rutgers.edu (8.8.8+Sun/8.8.8) with ESMTP id GAA19715
	for <nasreq@tdmx.rutgers.edu>; Thu, 18 May 2000 06:54:38 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02167;
	Thu, 18 May 2000 06:54:37 -0400 (EDT)
Message-Id: <200005181054.GAA02167@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: nasreq@tdmx.rutgers.edu
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-nasreq-nasmodel-02.txt
Date: Thu, 18 May 2000 06:54:37 -0400
Sender: owner-nasreq@tdmx.rutgers.edu
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Network Access Server Requirements Working Group of the IETF.

	Title		: Network Access Server Requirements Next Generation 
                          (NASREQNG)NAS Model
	Author(s)	: D. Mitton, M. Beadles
	Filename	: draft-ietf-nasreq-nasmodel-02.txt
	Pages		: 19
	Date		: 17-May-00
	
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 (RFC 2138, 2139)[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.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-nasreq-nasmodel-02.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-nasreq-nasmodel-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-nasreq-nasmodel-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20000517092317.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-nasreq-nasmodel-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-nasreq-nasmodel-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20000517092317.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-nasreq@kull.rutgers.edu  Thu May 18 13:28:44 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 NAA10831
	for <nasreq-archive@odin.ietf.org>; Thu, 18 May 2000 13:28:44 -0400 (EDT)
Received: (from majordom@localhost)
	by kull.rutgers.edu (8.8.8+Sun/8.8.8) id MAA06538
	for nasreq-outgoing; Thu, 18 May 2000 12:43:13 -0400 (EDT)
Received: from relay2.austria.eu.net (endjinn.austria.eu.net [193.81.13.2])
	by kull.rutgers.edu (8.8.8+Sun/8.8.8) with ESMTP id MAA06514
	for <nasreq@tdmx.rutgers.edu>; Thu, 18 May 2000 12:43:11 -0400 (EDT)
Received: from w1sfw21 (firew21.mobilkom.at [193.154.243.18])
	by relay2.austria.eu.net (8.10.1/8.10.1) with SMTP id e4IGh5101710
	for <nasreq@tdmx.rutgers.edu>; Thu, 18 May 2000 18:43:05 +0200 (MET DST)
Message-Id: <200005181643.e4IGh5101710@relay2.austria.eu.net>
Received: by mkabch08.mobilkom.at with Internet Mail Service (5.5.2650.21)
	id <LFR2C5K8>; Thu, 18 May 2000 16:38:51 +0200
Received: from w0ssec01 ([10.236.225.52]) by W1SXMS01.mobilkom.at with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id LFR2C5KT; Thu, 18 May 2000 16:38:44 +0200
From: postmaster@relay2.austria.eu.net
To: nasreq@tdmx.rutgers.edu
InterScan-Notification: yes
Subject: nasreq InterScan eManager Content Management Notification! (Attachment Removal)
Date: Thu, 18 May 2000 16:38:36 +0100
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_958660716_B78506032.R82506026"
Sender: owner-nasreq@tdmx.rutgers.edu
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_958660716_B78506032.R82506026
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

******Message from InterScan E-Mail VirusWall NT******

The following mail was blocked by InterScan eManager Content Management.

Source mailbox: <Internet-Drafts@ietf.org>
Destination mailbox(es): <nasreq@tdmx.rutgers.edu>
Policy: Attachment Removal
Attachment file name:  - text/plain, draft-ietf-nasreq-ext-radiuspract-03.txt - text/plain
Action: Replaced with text

eManager has removed a sensitive attachment file in the email.

******************* End of message *******************


------=_NextPart_000_958660716_B78506032.R82506026
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id HAA27171
	for ietf-123-outbound.01@ietf.org; Thu, 18 May 2000 07:25:00 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28])
	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id GAA26957
	for <all-ietf@loki.ietf.org>; Thu, 18 May 2000 06:54:41 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02183;
	Thu, 18 May 2000 06:54:42 -0400 (EDT)
Message-Id: <200005181054.GAA02183@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: nasreq@tdmx.rutgers.edu
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-nasreq-ext-radiuspract-03.txt
Date: Thu, 18 May 2000 06:54:41 -0400
Sender: nsyracus@cnri.reston.va.us

------=_NextPart_000_958660716_B78506032.R82506026--


From owner-nasreq@kull.rutgers.edu  Fri May 19 00:18:31 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 AAA18702
	for <nasreq-archive@odin.ietf.org>; Fri, 19 May 2000 00:18:30 -0400 (EDT)
Received: (from majordom@localhost)
	by kull.rutgers.edu (8.8.8+Sun/8.8.8) id XAA00441
	for nasreq-outgoing; Thu, 18 May 2000 23:44:27 -0400 (EDT)
Received: from mailrelay1.chek.com (gutmans.chek.com [208.197.227.23])
	by kull.rutgers.edu (8.8.8+Sun/8.8.8) with SMTP id XAA00434
	for <nasreq@tdmx.rutgers.edu>; Thu, 18 May 2000 23:44:27 -0400 (EDT)
Received: (qmail 30909 invoked from network); 19 May 2000 03:44:26 -0000
Received: from viebrock.chek.com (208.197.227.194)
  by mailrelay1.chek.com with SMTP; 19 May 2000 03:44:26 -0000
Received: (qmail 23188 invoked by uid 99); 19 May 2000 03:44:26 -0000
Date: 19 May 2000 03:44:26 -0000
Message-ID: <20000519034426.23187.qmail@viebrock.chek.com>
From: "Harish NK" <harish@c4.com>
To: nasreq@tdmx.rutgers.edu
X-Originating-IP: [209.21.27.82]
Subject: nasreq NAS package for MGCP ?
Sender: owner-nasreq@tdmx.rutgers.edu
Precedence: bulk

Hi,
 Is there any draft for implementing the NAS package for
the MGCP protocol?
  I know there is one for MEGACO 
i.e draft-ietf-megaco-naspkg-00.txt.

thanks
Harish

 

--------------------------------------------------
Totally Amazing Search Results - Just C4 Yourself!
http://www.C4.com - Total Search Technology


From owner-nasreq@kull.rutgers.edu  Fri May 19 23:48:15 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 XAA15338
	for <nasreq-archive@odin.ietf.org>; Fri, 19 May 2000 23:48:14 -0400 (EDT)
Received: (from majordom@localhost)
	by kull.rutgers.edu (8.8.8+Sun/8.8.8) id WAA08865
	for nasreq-outgoing; Fri, 19 May 2000 22:59:23 -0400 (EDT)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by kull.rutgers.edu (8.8.8+Sun/8.8.8) with ESMTP id WAA08855
	for <nasreq@tdmx.rutgers.edu>; Fri, 19 May 2000 22:59:21 -0400 (EDT)
Received: from chsharp-tecra.cisco.com (chsharp-isdn.cisco.com [171.68.116.221])
	by mailman.cisco.com (8.9.3/8.9.1) with ESMTP id TAA26334;
	Fri, 19 May 2000 19:59:18 -0700 (PDT)
Message-Id: <4.3.1.2.20000519225819.00b2ce20@dogwood.cisco.com>
X-Sender: chsharp@dogwood.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Fri, 19 May 2000 22:58:39 -0400
To: "Harish NK" <harish@c4.com>, nasreq@tdmx.rutgers.edu
From: Chip Sharp <chsharp@cisco.com>
Subject: Re: nasreq NAS package for MGCP ?
In-Reply-To: <20000519034426.23187.qmail@viebrock.chek.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-nasreq@tdmx.rutgers.edu
Precedence: bulk

See RFC2705 (MGCP).

Chip

At 03:44 AM 5/19/00 +0000, Harish NK wrote:
>Hi,
>  Is there any draft for implementing the NAS package for
>the MGCP protocol?
>   I know there is one for MEGACO
>i.e draft-ietf-megaco-naspkg-00.txt.
>
>thanks
>Harish
>
>
>
>--------------------------------------------------
>Totally Amazing Search Results - Just C4 Yourself!
>http://www.C4.com - Total Search Technology


-------------------------------------------------------------------
Chip Sharp                 CTO Consulting Engineering
Cisco Systems
Reality - Love it or Leave it.	
http://www.netaid.org		
-------------------------------------------------------------------



From owner-nasreq@kull.rutgers.edu  Sun May 21 02:55:43 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 CAA17782
	for <nasreq-archive@odin.ietf.org>; Sun, 21 May 2000 02:55:42 -0400 (EDT)
Received: (from majordom@localhost)
	by kull.rutgers.edu (8.8.8+Sun/8.8.8) id CAA03968
	for nasreq-outgoing; Sun, 21 May 2000 02:12:48 -0400 (EDT)
Received: from photon.idirect.com (photon.idirect.com [207.136.80.123])
	by kull.rutgers.edu (8.8.8+Sun/8.8.8) with ESMTP id CAA03957
	for <nasreq@tdmx.rutgers.edu>; Sun, 21 May 2000 02:12:46 -0400 (EDT)
From: offshore1444@yahoo.com
Received: from bc-vic-a53-01-92.look.ca ([216.66.129.92] helo=look.ca)
	by photon.idirect.com with smtp (Exim 3.12 #9)
	id 12rAZ5-0000Vu-00; Mon, 15 May 2000 07:25:03 +0500
Reply-To: offshore1444@yahoo.com
To: offshore1444@yahoo.com
Subject: nasreq Tired of the 9 to 5 Yet?
Message-Id: <E12rAZ5-0000Vu-00@photon.idirect.com>
Date: Mon, 15 May 2000 07:25:03 +0500
Sender: owner-nasreq@tdmx.rutgers.edu
Precedence: bulk

Ladies and Gentlemen,

     We thought this might be of interest to you because we received your commercial email, or you were referred to us as someone interested in business opportunities. WE PROMPTLY HONOR ALL REMOVE REQUESTS. To be removed from all future mailings, please reply with REMOVE in the subject heading

     Do you have the desire to make $2000 to $5000 PLUS PER WEEK, beginning almost immediately? How does $10,000 TO $20,000 PLUS PER MONTH, and a realistic STRONG SIX FIGURES this year sound? And, how about generating all of this by just sharing information?

     This is NOT, Lotions, Potions, Pills, Water Filters, Shopping Clubs, Long Distance Services. No Hype, No Meetings, No MLM! There Is No One Else Doing What We're Doing! 

    If you can bring desire and an honest effort to the table, we can show you how to NEVER WORRY ABOUT MONEY AGAIN! Opportunity is truly knocking! To find out more, call Toll Free.


                                                      1-800-636-6773 ext 3886
God bless




From owner-nasreq@kull.rutgers.edu  Fri May 26 06:56:14 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 GAA12306
	for <nasreq-archive@odin.ietf.org>; Fri, 26 May 2000 06:56:13 -0400 (EDT)
Received: (from majordom@localhost)
	by kull.rutgers.edu (8.8.8+Sun/8.8.8) id GAA02403
	for nasreq-outgoing; Fri, 26 May 2000 06:01:10 -0400 (EDT)
Received: from buffy.tpgi.com.au (buffy.tpgi.com.au [203.12.160.34])
	by kull.rutgers.edu (8.8.8+Sun/8.8.8) with ESMTP id GAA02393
	for <nasreq@tdmx.rutgers.edu>; Fri, 26 May 2000 06:01:06 -0400 (EDT)
From: info@animationallsorts.com
Received: (from smtpd@localhost)
	by buffy.tpgi.com.au (8.9.3/8.9.3) id UAA14233
	for <nasreq@tdmx.rutgers.edu.>; Fri, 26 May 2000 20:00:56 +1000
Date: Fri, 26 May 2000 20:00:56 +1000
Message-Id: <200005261000.UAA14233@buffy.tpgi.com.au>
Received: from syd3-56k-150.tpgi.com.au(203.29.148.150), claiming to be "home"
 via SMTP by buffy.tpgi.com.au, id smtpdlCHt1U; Fri May 26 20:00:46 2000
To: nasreq@tdmx.rutgers.edu
X-Mailer: 7A46E354.3786FEAA.c675ae82efdce36da3ab57fe8ff45c95
Subject: nasreq Open Mind
Organization: Animation Allsorts
Sender: owner-nasreq@tdmx.rutgers.edu
Precedence: bulk

I have discovered your webside on the Internet and find it
really interesting.I do believe that you or your clients may
benefit from the information we are offering. 

There are a lot of people trying to get rich quick, without 
any interest in another human being whatsoever. Well, I 
doubt that they will succeed. There is a law in success like 
there is a law in physics.

You may not believe in gravity or not know about it, but it still works.

The Law of Success says: 
If you help enough people to get what they want, 
You will get what You want.

Therefore, if you think, that you may gain and discover a benefit
for yourself, click on:

http://www.animationallsorts.com/00-Main-Journey.htm

or you can have a look at our Newsletter to find out if you can
benefit from it:

http://www.animationallsorts.com/NEWSLETER/April-00/NLetter-index.htm

Don't hesitate to forward a copy of this newsletter to friends
and associates, but please ask for permission before reproducing
the content in any form -- we would like to know who you are.

Pavel Kyral
Director

Animation Allsorts - Open Mind
105/3 Bruce Street, Crows Nest, NSW, 2065, Australia 
Phone: 612 9955 7990 | Fax: 612 9955 0076 
Copyright © 1990-2000 All Rights Reserved

If you think, that you will not benefit from this corespondence, send

an email to:

remove@animationallsorts.com	Subject:Remove gravity



From owner-nasreq@kull.rutgers.edu  Wed May 31 09:55: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 JAA09895
	for <nasreq-archive@odin.ietf.org>; Wed, 31 May 2000 09:55:58 -0400 (EDT)
Received: (from majordom@localhost)
	by kull.rutgers.edu (8.8.8+Sun/8.8.8) id JAA25338
	for nasreq-outgoing; Wed, 31 May 2000 09:16:03 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by kull.rutgers.edu (8.8.8+Sun/8.8.8) with ESMTP id JAA25321
	for <nasreq@tdmx.rutgers.edu>; Wed, 31 May 2000 09:16:01 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08301;
	Wed, 31 May 2000 09:15:50 -0400 (EDT)
Message-Id: <200005311315.JAA08301@ietf.org>
To: IETF-Announce: ;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
Cc: nasreq@tdmx.rutgers.edu
From: The IESG <iesg-secretary@ietf.org>
Subject: nasreq Document Action: Network Access Server Requirements Next
         Generation (NASREQNG)NAS Model to Informational
Date: Wed, 31 May 2000 09:15:50 -0400
Sender: owner-nasreq@tdmx.rutgers.edu
Precedence: bulk


The IESG has approved publication of the following Internet-Drafts as
Informational RFCs:


Network Access Server Requirements Next Generation (NASREQNG) NAS Model
<draft-ietf-nasreq-nasmodel-01.txt>

Network Access Servers Requirements: Extended RADIUS Practices
<draft-ietf-nasreq-ext-radiuspract-02.txt>

These documents are the product of the Network Access Server
Requirements Working Group.  The IESG contact persons are Bert Wijnen
and Randy Bush.


