One thing I'd wonder is if TCP/TLS/UDP are the right thing to key the specification on - what actually seems to be _relevant_ is "SP over transports with SOCK_STREAM semantics" and "SP over transports with SOCK_DGRAM semantics" - that then covers TCP, TCP+TLS, AF_UNIX SOCK_STREAM (IPC), IPC+TLS, UDP, UDP+DTLS, etc. Martin Sustrik wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi all, > > I've added first drafts of UDP and TLS RFCs into the rfc subdirectory. > Feel free to comment. > > Garrett, you'll probably want to make yourself the editor of the TLS > draft. I don't have enough experience in the area to make a sane > editor of that document. > > As for generating the txts from xmls I am at the moment using online > xml.resource.org tool. Later on we can add xml2rfc to the build process. > > Also note that I've added the RFCs to the nanomsg package. > > Martin > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQEcBAEBAgAGBQJTL8uaAAoJENTpVjxCNN9Y7j4H/0mfcV8UsKuJuCzitWoM8puH > RdQGvHJCaZCAlWcjogUQis+NTSEO5UlasCpqG9jsq57o0Rt5ZnDytvqHPDLfBXmB > DsBghtDyufr3GC7L6G/EApQKCjn/+LfmHETiGUhAT2mUX0yGFulP4oc5RWbawzB0 > AGEL3OdZELonOSV4G9QcPskbUaatD4jjhEcjG76LqXE3TC58B30yKxIKZrFRla/S > Zs9LMGAiBdMd8qJf5ymBsot0geu2Ej2K73P9/0pS9pa1roKcNLUOt0n8h/j4XdUz > HsXwV0u4mmc7aw1xmP8p8mrMvGGgeHUaXmKAsXPGE5qJDwBhp2tbTPtS2rsXxj4= > =xHyP > -----END PGP SIGNATURE-----