Blocks Extensible Exchange Protocol (BEEP) Parameters (last updated 2009-06-10) Registries included below: - BEEP Profiles - BEEP Features Registry Name: BEEP Profiles Reference: [RFC3080] Registration Procedures: Expert review 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&lists.beepcore.org may be used to solicit commentary. Registry: Standards-Track BEEP Profiles Reference -------------------------------------------- --------- http://iana.org/beep/TLS [RFC3080] http://iana.org/beep/SASL/mechanism [RFC3080] http://iana.org/beep/SYSLOG/RAW [RFC3195] http://iana.org/beep/SYSLOG/COOKED [RFC3195] http://iana.org/beep/APEX [RFC3340] http://iana.org/beep/soap [RFC4227] http://iana.org/beep/soap/1.1 [RFC4227] http://iana.org/beep/soap/1.2 [RFC4227] http://iana.org/beep/xmlrpc [RFC3529] http://iana.org/beep/TUNNEL [RFC3620] http://iana.org/beep/sacred [RFC3767] http://iana.org/beep/iris1 [RFC3983] http://iana.org/beep/iris1/dreg1 [RFC3982] http://iana.org/beep/cap/1.0 [RFC4324] http://iana.org/beep/iris1/ereg1 [RFC4414] http://iana.org/beep/netconf [RFC4744] http://iana.org/beep/iris1/dchk1 [RFC5144] Registry Name: BEEP Features Reference: [RFC3080] Registration Procedures: Expert review 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&lists.beepcore.org may be used to solicit commentary. Registry: Feature Reference ------------------------ --------- async [RFC5573] References ---------- [RFC3080] Rose, M., "The Blocks Extensible Exchange Protocol Core", RFC 3080, February 2001. [RFC3195] D. New and M. Rose, "Reliable Delivery for syslog", RFC 3195, November 2001. [RFC3288] E. O'Tuathail and M. Rose, "Using SOAP in BEEP", RFC 3288, June 2002. [RFC3340] M. Rose, G. Klyne, and D. Crocker, "The Application Exchange Core", RFC 3340, July 2002. [RFC3529] W. Harold, "Using XML-RPC in BEEP", RFC 3529, April 2003. [RFC3620] D. New, "The TUNNEL Profile", RFC 3620, October 2003. [RFC3767] S. Farrell, Ed., "Securely Available Credentials Protocol" RFC 3767, June 2004. [RFC3982] A. Newton and M. Sanz, "IRIS - A Domain Registry (dreg) Type for the Internet Registry Information Service", RFC 3982, January 2005. [RFC3983] A. Newton and M. Sanz, "IRIS - Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP)", RFC 3983, January 2005. [RFC4227] E. O'Tuathail and M. Rose, "Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP)", RFC 4227, January 2006. [RFC4324] D. Royer, G. Babics, P. Hill, and S. Mansour, "Calendar Access Protocol (CAP)", RFC 4324, December 2005. [RFC4414] A. Newton, "An ENUM Registry Type for the Internet Registry Information Service", RFC 4414, February 2006. [RFC4744] E. Lear and K. Crozier, "Using the NETCONF Protocol over Blocks Extensible Exchange Protocol (BEEP)", RFC 4744, December 2006. [RFC5144] A. Newton, M. Sanz, "A Domain Availability Check (DCHK) Registry Type for the Internet Registry Information Service (IRIS)", RFC 5144, February 2008. [RFC5573] M. Thomson, "Asynchronous Channels for the Blocks Extensible Exchange Protocol (BEEP)", RFC 5573, June 2009. (created 2000-01-30) []