Remote Account Maintenance Protocol (ramp)
------------------------------------------

 Charter
 Last Modified: 06/01/1994

 Current Status: Concluded Working Group

 Chair(s):
     Jeff Payne  <jpayne@interserv.net>

 Service Applications Area Director(s):
     Dave Crocker  <dcrocker@brandenburg.com>

 Service Applications Area Advisor:
     Dave Crocker  <dcrocker@brandenburg.com>

 Mailing Lists: 
     General Discussion:
     To Subscribe:      
     Archive:           

Description of Working Group:

Draft 3/16/94 mw

From the team that developed the Internet-in-a-box, there is interest
in pursuing IETF work in the realm of ``ato-registration''.  This BOF
will be held to discuss IETF interest in such an activity and how it 
should proceed.

The description of the work being submitted:

Before a client system and server can interact, they must be configured
to know about each other.  The Remote Account Maintenance Protocol (RAMP)
was designed to ease the process of account creation and machine 
registration on server systems.  RAMP clients create their own accounts
by populating pre-configured templates on RAMP servers.  This frees Server
Administrators from some mundane tasks, while providing users instant
access to certain server resources.

 Goals and Milestones:


 Internet-Drafts:

  No Current Internet-Drafts.

 Request For Comments:

  None to date.