<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet type="text/xsl" href="gssapi-service-names.xsl"?>
<?xml-model href="gssapi-service-names.rng" schematypens="http://relaxng.org/ns/structure/1.0" ?>
<registry xmlns="http://www.iana.org/assignments" id="gssapi-service-names">
  <title>Generic Security Service Application Program Interface (GSSAPI)/Kerberos/Simple Authentication and Security Layer (SASL) Service Names</title>
  <updated>2021-08-26</updated>
  <registry id="gssapi-service-names-1">
    <title>GSSAPI/Kerberos/SASL Service Names</title>
    <xref type="rfc" data="rfc2743"/>
    <registration_rule>Specification Required</registration_rule>
    <expert>Unassigned</expert>
    <note>A service is a resource provided to network clients; often provided by
more than one server and potentially by more than one protocol.
Service names are short alphanumeric textual strings.  Service names
are used in the GSSAPI <xref type="rfc" data="rfc2743"/> host-service name form, are specified
as part of a SASL profile <xref type="rfc" data="rfc4422"/> and are used by Kerberos
service-based tickets <xref type="rfc" data="rfc1510"/>. Registrations are restricted to
alphanumeric characters and the characters '+', '-' and '.'
    </note>
    <record updated="2014-10-14">
      <name>rcmd</name>
      <usage>remote command/rlogin/telnet</usage>
      
    </record>
    <record>
      <name>host</name>
      <usage>generic host-based service</usage>
      <xref type="rfc" data="rfc2743"/>
    </record>
    <record updated="2021-02-22">
      <name>imap</name>
      <usage>mailstore access/IMAP4</usage>
      <xref type="rfc" data="rfc3501"/>
	    <xref type="rfc" data="rfc9051"/>
    </record>
    <record>
      <name>pop</name>
      <usage>maildrop access/POP3</usage>
      <xref type="rfc" data="rfc5034"/>
    </record>
    <record>
      <name>acap</name>
      <usage>remote configuration access/ACAP</usage>
      <xref type="rfc" data="rfc2244"/>
    </record>
    <record>
      <name>nfs</name>
      <usage>distributed file system protocol</usage>
      <xref type="rfc" data="rfc2623"/>
      <xref type="rfc" data="rfc7530"/>
      <xref type="rfc" data="rfc8881"/>
    </record>
    <record>
      <name>ftp</name>
      <usage>file transfer/FTP/TFTP</usage>
      <xref type="rfc" data="rfc2228"/>
    </record>
    <record>
      <name>ldap</name>
      <usage>Lightweight Directory Access Protocol (LDAP)</usage>
      <xref type="rfc" data="rfc4510"/>
      <xref type="rfc" data="rfc4513"/>
    </record>
    <record>
      <name>smtp</name>
      <usage>message transfer/SMTP</usage>
      <xref type="rfc" data="rfc4954"/>
    </record>
    <record>
      <name>beep</name>
      <usage>Blocks Extensible Exchange Protocol</usage>
      <xref type="rfc" data="rfc3080"/>
    </record>
    <record>
      <name>mupdate</name>
      <usage>Mailbox Update (MUPDATE) Protocol</usage>
      <xref type="rfc" data="rfc3656"/>
    </record>
    <record>
      <name>sacred</name>
      <usage>Secure Available Credentials (SACRED) Protocol</usage>
      <xref type="rfc" data="rfc3767"/>
    </record>
    <record>
      <name>sieve</name>
      <usage>ManageSieve Protocol</usage>
      <xref type="rfc" data="rfc5804"/>
    </record>
    <record>
      <name>xmpp</name>
      <usage>Extensible Messaging and Presence Protocol (XMPP)</usage>
      <xref type="rfc" data="rfc6120"/>
    </record>
    <record>
      <name>nntp</name>
      <usage>Network News Transfer Protocol (NNTP)</usage>
      <xref type="rfc" data="rfc4643"/>
    </record>
  </registry>
  <people/>
</registry>
