It's probably only funny if you're familiar with SIP, but it takes such great jabs at the protocol and the IETF. It sorta captures how SIP commonly [mis]implemented, instead of just being a complete gag.
Referring to SIP URIs:
"In the real world that's highly unlikely, and in fact Alice would have pressed buttons for a phone number, and simply set the domain portion to her service provider. But this is not the real world, this is the IETF."
On NAT:
"And we don't mean this as a knock on SIP, because the entire IETF refused to admit NATs exist."
And on removing some headers:
"Subject - this ain't email. "
5 comments
[ 85.1 ms ] story [ 283 ms ] threadhttp://www.rfc-editor.org/rfc-editor/instructions2authors.tx...
>This document was produced using the xml2rfc tool [RFC2629].
http://tools.ietf.org/id/draft-kaplan-sip-four-oh-00.txt
It's probably only funny if you're familiar with SIP, but it takes such great jabs at the protocol and the IETF. It sorta captures how SIP commonly [mis]implemented, instead of just being a complete gag.
Referring to SIP URIs: "In the real world that's highly unlikely, and in fact Alice would have pressed buttons for a phone number, and simply set the domain portion to her service provider. But this is not the real world, this is the IETF."
On NAT: "And we don't mean this as a knock on SIP, because the entire IETF refused to admit NATs exist."
And on removing some headers: "Subject - this ain't email. "