[Steve Nahm: New charter; new co-chair]

["Theodore Y. Ts'o" <[e-mail]>]

The ONCRPC working group is starting a new phase of work, which involves
adding an authentication flavor which uses GSSAPI.  I invite all those
in the CAT wg who might be interested in this work area to join the
ONCRPC wg mailing list, download the internet drafts, and show up at the
upcoming San JOSE wg meeting!

						- Ted

------- Forwarded Message

Date: Wed, 20 Nov 1996 21:30:09 -0800
From: [e-mail] (Steve Nahm)
To: [e-mail]
Subject: New charter; new co-chair
Cc: [e-mail], [e-mail]
X-Sun-Charset: US-ASCII


There were no objections or discussions on the revised charter that
I posted on this alias a while back, so our area directors made a few
minor tweaks to it and agreed to the new charter.

I'm pleased to announce that Ted Ts'o has agreed to become co-chair
of this WG as we move into the "security mechanism" phase of work.
Ted's experience working with the RPC authentication flavors will
bring a practical perspective to the review of the RPCSEC_GSS proposal
that's currently on the table.

Note that the schedule listed below is moderately agressive, and will
require that all interested parties spend the time needed to review
the RPCSEC_GSS proposal and bring up any issues early.  To date, 
no one outside of Sun has committed to reviewing the draft by the
San Jose WG meeting.  We *must* do a critical review of the proposal
by this meeting if we are to meet the timetable below.  So this time
I'll ask those of you who think they *might* review the RPCSEC_GSS
proposal in time for discussion at the San Jose meeting, please email
me (or the WG list if you're willing to go public :-).

Thanks and see you in a few weeks,
Steve


ONC Remote Procedure Call (oncrpc)
-----------------------------------
 
 Charter 
 
 Current status: active working group
 
 Chair(s):
     Steve Nahm <[e-mail]>
     Ted Ts'o   <[e-mail]>
 
 Transport Area Director(s): 
     Allison Mankin  <[e-mail]>
     Allyn Romanow <[e-mail]>
 
 Mailing lists: 
     General Discussion:[e-mail]
     To Subscribe:      [e-mail]
     Archive:           ftp://playground.sun.com/pub/oncrpc

Description of Working Group:
 
The Open Network Computing Remote Procedure Call Working Group was
originally formed to update the RFCs that describe ONC RPC to reflect
the current state of the deployed and accepted technology, and submit
them for Internet standardization.  RFCs have been submitted for the
three core ONC technologies: RPC (RFC1831), RPC Binding (RFC 1833)
and XDR (RFC1832).

During this work, IESG identified the area of security as requiring
improvement prior to standardizing the core RPC technologies (RPC and
RPC Binding).  Therefore, the Working Group shall develop and define
a security mechanism for ONC RPC which shall, at the minimum, allow
for strong authentication of client and server principals.  The core
RPC technologies will be unblocked from the standards track once
such a mechanism is approved as a Proposed Standard, provided
that its design does not require changes to the core RPC technologies.

The basis for the work will be the RPCSEC_GSS Protocol Specification,
draft-ietf-oncrpc-rpcsec_gss.00.txt.

The document editor will be Michael Eisler.

Background:

ONC RPC is a Remote Procedure Call technology that originated in Sun
Microsystems in the early 1980s. ONC RPC was modelled on Xerox's
Courier RPC protocols. It has been widely deployed on platforms from
most major workstation vendors. It has been implemented on MS-DOS,
Microsoft Windows, Microsoft Windows NT, Mac, VMS, MVS, and
practically all flavors of UNIX, among others. Sun Microsystems has
delegated change control for the ONC RPC protocols for the purposes
of making an Internet Standard to the IETF (see RFC 1790).

 
 Goals and Milestones: 
 

     Done	Submit XDR document to IESG for consideration as a Draft
		Standard.

     Done	Submit a strong security mechanism for ONC RPC as an
		Internet Draft.

     Feb 97	Submit strong security mechanism for ONC RPC to IESG 
		for consideration as a Proposed Standard.

     Mar 97     Submit core RPC documents to IESG for consideration as 
		Draft Standards.   

     Mar 97     Conclude working group, leaving mailing list in place
                for pursuit of the subseqent standards stages.  The
                anticipated schedule for submissions is:

         	  Apr 97  XDR for consideration as Internet Standard

         	  Aug 97  Core RPC for consideration as Internet Standard   

                  Aug 97  Strong security mechanism for consideration
                          as Draft Standard

                  Jan 98  Strong security mechanism for consideration
                          as Internet Standard


------- End Forwarded Message