IANA Considerations for Remote Procedure Call (RPC) Network Identifiers and Universal Address Formats
RFC 5665

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 06

Internet Engineering Task Force (IETF)                         M. Eisler
Request for Comments: 5665                                        NetApp
Updates: 1833                                               January 2010
Category: Standards Track
ISSN: 2070-1721

          IANA Considerations for Remote Procedure Call (RPC)
           Network Identifiers and Universal Address Formats

Abstract

   This document lists IANA Considerations for Remote Procedure Call
   (RPC) Network Identifiers (netids) and RPC Universal Network
   Addresses (uaddrs).  This document updates, but does not replace, RFC
   1833.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc5665.

Copyright Notice

   Copyright (c) 2010 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Eisler                       Standards Track                    [Page 1]
RFC 5665                       RPC Netids                   January 2010

Table of Contents

   1. Introduction and Motivation .....................................3
   2. Requirements Language ...........................................3
   3. Considerations for the Netid of the Stream Control
      Transmission Protocol ...........................................3
   4. Security Considerations .........................................3
   5. IANA Considerations .............................................3
      5.1. IANA Considerations for Netids .............................4
           5.1.1. Initial Registry ....................................6
           5.1.2. Updating Registrations ..............................8
      5.2. IANA Considerations for Uaddr Formats ......................8
           5.2.1. Initial Registry ....................................9
           5.2.2. Updating Registrations .............................10
           5.2.3. Uaddr Formats ......................................10
                  5.2.3.1. Uaddr Format for System V Release
                           4 Loopback Transports .....................10
                  5.2.3.2. Uaddr Format for Netid "-" ................10
                  5.2.3.3. Uaddr Format for Most IPv4 Transports .....11
                  5.2.3.4. Uaddr Format for Most IPv6 Transports .....11
                  5.2.3.5. Uaddr Format for ICMP over IPv4 and IPv6 ..11
      5.3. Cross Referencing between the Netid and Format Registry ...12
      5.4. Port Assignment for NFS over SCTP .........................12
   6. References .....................................................12
      6.1. Normative References ......................................12
      6.2. Informative References ....................................12
   Appendix A.  Acknowledgments ......................................14

Eisler                       Standards Track                    [Page 2]
RFC 5665                       RPC Netids                   January 2010

1.  Introduction and Motivation

   The concepts of an RPC (defined in RFC 5531 [4]) Network Identifier
   (netid) and an RPC Universal Address (uaddr) were introduced in RFC
   1833 [1] for distinguishing network addresses of multiple protocols
   and representing those addresses in a canonical form.  RFC 1833
   states that a netid "is defined by a system administrator based on
   local conventions, and cannot be depended on to have the same value
   on every system".  (The netid is contained in the field r_netid of
   the data type rpcb_entry, and the uaddr is contained in the field
   r_addr of the same data type, where rpcb_entry is defined in RFC
   1833.)  Since the publication of RFC 1833, it has been found that
   protocols like Network File System version 4 (NFSv4.0) [5] and RPC/
   RDMA (Remote Direct Memory Access) [6] depend on consistent values of
   netids and representations of uaddrs.  Current practices tend to
   ensure this consistency.  Thus, this document identifies the