<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet type="text/xsl" href="beep-parameters.xsl"?>
<?xml-model href="beep-parameters.rng" schematypens="http://relaxng.org/ns/structure/1.0" ?>
<registry xmlns="http://www.iana.org/assignments" id="beep-parameters">
  <title>Blocks Extensible Exchange Protocol (BEEP) Parameters</title>
  <created>2000-01-30</created>
  <updated>2009-06-10</updated>
  <registry id="beep-parameters-1">
    <title>BEEP Profiles</title>
    <xref type="rfc" data="rfc3080"/>
    <registration_rule>Expert Review</registration_rule>
    <expert>Marshall T. Rose</expert>
    <note>The IANA maintains a registry of standards-track BEEP
profiles (as specified in Appendix B of RFC 3080).

To add a BEEP Profile:
Section 5.1 of RFC 3080 contains a registration template
that should be completed, approved by the IESG, and then
placed in this registry.

As a courtesy to developers of non-standards track BEEP
profiles, the mailing list beepwg&amp;lists.beepcore.org may be
used to solicit commentary.</note>
    <record>
      <profile>http://iana.org/beep/TLS</profile>
      <xref type="rfc" data="rfc3080"/>
    </record>
    <record>
      <profile>http://iana.org/beep/SASL/mechanism</profile>
      <xref type="rfc" data="rfc3080"/>
    </record>
    <record>
      <profile>http://iana.org/beep/SYSLOG/RAW</profile>
      <xref type="rfc" data="rfc3195"/>
    </record>
    <record>
      <profile>http://iana.org/beep/SYSLOG/COOKED</profile>
      <xref type="rfc" data="rfc3195"/>
    </record>
    <record>
      <profile>http://iana.org/beep/APEX</profile>
      <xref type="rfc" data="rfc3340"/>
    </record>
    <record>
      <profile>http://iana.org/beep/soap</profile>
      <xref type="rfc" data="rfc4227"/>
    </record>
    <record>
      <profile>http://iana.org/beep/soap/1.1</profile>
      <xref type="rfc" data="rfc4227"/>
    </record>
    <record>
      <profile>http://iana.org/beep/soap/1.2</profile>
      <xref type="rfc" data="rfc4227"/>
    </record>
    <record>
      <profile>http://iana.org/beep/xmlrpc</profile>
      <xref type="rfc" data="rfc3529"/>
    </record>
    <record>
      <profile>http://iana.org/beep/TUNNEL</profile>
      <xref type="rfc" data="rfc3620"/>
    </record>
    <record>
      <profile>http://iana.org/beep/sacred</profile>
      <xref type="rfc" data="rfc3767"/>
    </record>
    <record>
      <profile>http://iana.org/beep/iris1</profile>
      <xref type="rfc" data="rfc3983"/>
    </record>
    <record>
      <profile>http://iana.org/beep/iris1/dreg1</profile>
      <xref type="rfc" data="rfc3982"/>
    </record>
    <record>
      <profile>http://iana.org/beep/cap/1.0</profile>
      <xref type="rfc" data="rfc4324"/>
    </record>
    <record>
      <profile>http://iana.org/beep/iris1/ereg1</profile>
      <xref type="rfc" data="rfc4414"/>
    </record>
    <record>
      <profile>http://iana.org/beep/netconf</profile>
      <xref type="rfc" data="rfc4744"/>
    </record>
    <record>
      <profile>http://iana.org/beep/iris1/dchk1</profile>
      <xref type="rfc" data="rfc5144"/>
    </record>
  </registry>
  <registry id="beep-parameters-2">
    <title>BEEP Features</title>
    <xref type="rfc" data="rfc3080"/>
    <registration_rule>Expert Review</registration_rule>
    <expert>Marshall T. Rose</expert>
    <note>The IANA maintains a registry of standards-track BEEP
features (as specified in Appendix B of RFC 3080).

To add a BEEP Feature:
Section 5.2 of RFC 3080 contains a registration template
that should be completed, approved by the IESG, and then
placed in this registry.

As a courtesy to developers of non-standards track BEEP
features, the mailing list beepwg&amp;lists.beepcore.org may be
used to solicit commentary.</note>
    
    <record>
      <feature>async</feature>
      <xref type="rfc" data="rfc5573"/>
    </record>
    
  </registry>
  <people/>
</registry>
