RFC3080: The Blocks Extensible Exchange Protocol Core
Network Working Group M. Rose Request For Comments: 3080 Invisible Worlds, Inc. Category: Standards Track March 2001 The Blocks Extensible Exchange Protocol Core Status of thi...
RFC3081: Mapping the BEEP Core onto TCP
Network Working Group M. Rose Request for Comments: 3081 Invisible Worlds, Inc. Category: Standards Track March 2001 Mapping the BEEP Core onto TCP Status of this Memo ...
RFC3195: Reliable Delivery for syslog
Network Working Group D. New Request for Comments: 3195 M. Rose Category: Standards Track Dover Beach Consulting, Inc. November 2001 ...
RFC3288: Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP)
Network Working Group E. O'Tuathail Request for Comments: 3288 Clipcode.com Category: Standards Track M. Rose Dover Beach Consulting, Inc. ...
RFC3340: The Application Exchange Core
Network Working Group M. Rose Request for Comments: 3340 Dover Beach Consulting, Inc. Category: Standards Track G. Klyne Clearswift Corporation ...
RFC3349: A Transient Prefix for Identifying Profiles under Development by the Working Groups of the Internet Engineering Task Force
Network Working Group M. Rose Request for Comments: 3349 Dover Beach Consulting, Inc. BCP: 59 July 2002 Category: Best Current Practice A Transient Prefix for Identifying Prof...
RFC3620: The TUNNEL Profile
Network Working Group D. New Request for Comments: 3620 October 2003 Category: Standards Track The TUNNEL Profile Status of this Memo This document specifies an Internet standards trac...
RFC3529: Using Extensible Markup Language-Remote Procedure Calling (XML-RPC) in Blocks Extensible Exchange Protocol (BEEP)
Network Working Group W. Harold Request for Comments: 3529 IBM Category: Experimental April 2003 Using Extensible Markup Language-Remote Procedure Calling ...
RFC3767: Securely Available Credentials Protocol
Network Working Group S. Farrell, Ed. Request for Comments: 3767 Trinity College Dublin Category: Standards Track June 2004 Securely Available Credentials Protocol Status of this M...
RFC3983: Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP)
Network Working Group A. Newton Request for Comments: 3983 VeriSign, Inc. Category: Standards Track M. Sanz DENIC eG ...
RFC4227: Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP)
Network Working Group E. O'Tuathail Request for Comments: 4227 Clipcode.com Obsoletes: 3288 M. Rose Category: Standards Track Dover Beach Consulting, Inc. ...
RFC4324: Calendar Access Protocol (CAP)
Network Working Group D. Royer Request for Comments: 4324 IntelliCal, LLC Category: Experimental G. Babics Oracle ...
RFC4744: Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)
Network Working Group E. Lear Request for Comments: 4744 Cisco Systems Category: Standards Track K. Crozier December 2006 ...
RFC4767: The Intrusion Detection Exchange Protocol (IDXP)
Network Working Group B. Feinstein Request for Comments: 4767 SecureWorks, Inc. Category: Experimental G. Matthews CSC/NASA Ames Research Center ...
RFC5573: Asynchronous Channels for the Blocks Extensible Exchange Protocol (BEEP)
Network Working Group M. Thomson Request for Comments: 5573 Andrew Category: Experimental June 2009 Asynchronous Channels for the Blocks Extensible Exchange Protocol (BEEP) ...