1.
RFC's
RFC1001: Protocol standard for a NetBIOS service on a TCP/UDP transport: ... RFC1095: Common Management Information Services and Protocol over TCP/IP (CMOT) ...
2.
Google talk: Conference bot
The google talk conference bot was written by me to address the lack of MUC server for google talk. Without s2s I couldn't run my own MUC server, ...
3.
RFC's
This document describes the format and use of RSVP's INTEGRITY object to provide hop-by-hop integrity and authentication of RSVP messages. ...
4.
RFC's
This document describes terminology for the benchmarking of devices that implement traffic control using packet classification based on defined criteria. ...
5.
RFC's
3892: The Session Initiation Protocol (SIP) Referred-By Mechanism. ... If that URI is a SIP URI, the referee will send a SIP request, often an INVITE, ...
6.
Google talk: Conference bot
The google talk conference bot was written by me to address the lack of MUC server for google talk. Without s2s I couldn't run my own MUC server, ...
7.
RFC's
0970: On packet switches with infinite storage. ... We find it illuminating to consider the case of a packet switch with infinite storage. ...
8.
RFC's
The Encapsulating Security Payload (ESP) header is designed to provide a mix of security services in IPv4 and IPv6. ESP may be applied alone, in combination ...
9.
Google talk: Conference bot
The google talk conference bot was written by me to address the lack of MUC server for google talk. Without s2s I couldn't run my own MUC server, ...
10.
Google talk: Conference bot
The google talk conference bot was written by me to address the lack of MUC .... Bug fix: When people remove the bot from their roster, remove them from the ...
