RPC
Click on the red underlined text to get to the source
... the use of ONC Remote Procedure Call (RPC) primitives built on top of
an eXternal Data Representation (XDR ...
... RFC2203].
This new flavor allows application protocols built on top of RPC to
access security mechanisms that adhere to the GSS-API ...
... Overview of RPC Security Architecture ...
... security parameters (referred to
as an authentication flavor in the RPC specification [RFC1831]) on
every call. The contents of the security parameters ...
... NFS server checks permissions by taking the credentials from the
RPC security information in each remote request. Each flavor packages
credentials ...
... reject the request with an error (either an NFS error or an RPC
level authentication error), or
...
...
When one develops a new RPC security flavor, iana@iana.org MUST be
contacted to get a unique flavor assignment. To simplify NFS ...
... bit integers that are allocated out of the same
number space as regular RPC security flavors like AUTH_NONE,
...
... file
systems to see if the triple was allowed. Moreover, by the time the
NFS server's dispatch routine was reached, the typical RPC subsystem
would already have performed the appropriate GSS-API operation,
...
... Pseudo flavor numbers MUST be registered via same method as regular
RPC security flavor numbers via iana@iana.org.
...
... Version 2 and Version 3 work over
RPC's RPCSEC_GSS security flavor. This memorandum requires that
...
... RPCSEC_GSS security service } be mapped to a unique RPC security
flavor number, which is a pseudo ...
... flavor number, which is a pseudo flavor that does not appear in an
RPC protocol header. This memorandum also encourages that an ASCII
string name be registered with the triple.
...
... pseudo flavor numbers are no different than that the considerations
for RPC security flavors, as both are assigned from the same number
space. IANA ...
... security flavors, as both are assigned from the same number
space. IANA is already responsible for the assigned of RPC security
flavors, and because this memorandum does not specify the RPC ...
... RPC security
flavors, and because this memorandum does not specify the RPC
protocol [RFC1831], it is beyond the scope of this memorandum to
...
...
This memorandum introduces the concept of a string name to be
associated with the RPC pseudo flavor number, and so it is within the
scope of this memorandum to provide guidance to IANA ...
... The simplest way to handle delegation is to delegate portions of the
RPC security flavor number space with the RPC ...
... RPC security flavor number space with the RPC flavor name space. The
guidelines for delegation ...