RPC Numbering Authority Transfer to IANA
draft-ietf-nfsv4-rpc-iana-03

Document Type Expired Internet-Draft (nfsv4 WG)
Last updated 2005-02-04
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-nfsv4-rpc-iana-03.txt

Abstract

Network services based on RPC [RFC1831] use program numbers rather than well known transport ports to permit clients to find them, and use authentication flavor numbers to define the format of the authentication data passed. The assignment of RPC program numbers and authentication flavor numbers is still performed by Sun Microsystems, Inc. This is inappropriate for an IETF standard protocol, as such work is done well by the Internet Assigned Numbers Authority (IANA). This document defines how IANA will maintain and assign RPC program numbers and authentication flavor numbers.

Authors

Robert Thurlow (robert.thurlow@sun.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)