-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 01/21/2013 08:57 PM, William Jordan wrote:
I've recent had to write a program to interface with a SIP lync server and
in doing so have had to code to several rfcs. After reading and dealing
with implementation of the various rfcs I have read I have come up with
what I consider "A modest proposal" to fix some of the problems I've seen
with implementing a rfc. I think anyone who writes a rfc should have to
provide a working ANSI/C or GNU/C implementation of the rfc in question.
Specifically, I have worked with the SIP rfc (rfc 3261) and have come to
the conclusion that whoever wrote the rfc has never coded a day in their
life. Whoever thought it was a good idea to allow multiple ways of doing
the same exact thing would hopefully be deterred by actually writing code
to do it. I think a suitable punishment for those people would be to write
each way of writing a from header on a blackboard 100 times... this would
actually be less of the pain they've cause by making each writer of a SIP
stack handle each possible way of doing things.
Anyways, that is my modest proposal, please respond or I will be forced to
reply every day to this mailing list on each and every way the SIP spec
sucks one email at a time. FYI I'm not sure if GNU/C is the correct
acronym, maybe its POSIX/C.
SIP is an RFC so there is nothing that can be done here. If you want to help,
choose one or more Internet-Drafts, *fully* implement them and report the
problems you find to the Working Group. I also went through the full 5 steps
of grief over the death of my hope of having a good time implementing IETF
protocols and that's the best way I found of ensuring that RFCs do not suck at
implementation time.
- --
Marc Petit-Huguenin
Email: marc(_at_)petit-huguenin(_dot_)org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJQ/rg2AAoJECnERZXWan7EDoAP/1R5eEvy+RRACs5FfQ6ZzS4y
33FuGscGOQn+1D3vftUPTrQA5CyyFBqHbahYIJ4xODVkgyRM4U2OExMxcAZJ/b5t
YB7M+rpMxxozcwhBUrP+OgTiMHqh0b8sVzcDrb3bQ7mdkgyYXXcEvwEd+hzeQm58
vyaivz7WW5U9Y4dXev1/nsEaN4Wm2gGCHsxtk4rZAT6IHouTF0gDTRSLGKZbiZ0q
0wuMg9WjnlEH8qIqOEIA+6cIUQLvC7tQD8TXVxEC9BsUs7kHFcs7jMpcrfxALnfc
pDg4KtoyCbKzWhxVNJm+6Rgu4goEkX3Gx/Piptjs6jG4gwzdRYVWzIu0MYSZ1EM3
87bSUaf4lKlcn6kedfYuCAwAlkvdQYzelciGgP/hekhi4UZ7uf7G3rMPqJPdqsU0
l1vT+9liE8I5F7KrKo7jrUiTnGL1poSgwBFme5CAZXp9Z4nDQeQSAB3RVYPYWxbV
3ndmycW5OSSqpmNqno1BKWXF2UdYPVgKl4i7yVz4GWQiyK+XIftm4mQm4UYmSNbW
pJGi44w5lU0Ky8sjatOr/c0pkwqw0v4s6vx8SuTUO5uhRCHUKAvXFg0SHPJgZvYY
IrMXBEz2vRN91YbjhEqtZm2XhGTHIn7ZtR1JaKxq8ZGT1Y2D0fvgd0DIYyjmMt0R
8zIycA3AnZIy+nM4gsfo
=1GcK
-----END PGP SIGNATURE-----