Talk:List of RFCs

From Wikipedia, the free encyclopedia

Contents 1 Suggestions 2 Deflate and such 3 RTP 4 Transclusion to other pages?

[edit] Suggestions

To the editors of this page, please take a look into MIME, SMTP, ESMTP, Bounce messages, SMTP AUTH (ESMTPA), CRAM MD5, and RFC if you want to list about twenty more RfCs with corresponding articles. -- Omniplex 07:04, 30 March 2006 (UTC)

Would you care to list the RFCs for each? :) Cburnett 02:12, 17 March 2007 (UTC)

Two simple cases are SMTP AUTH RFC 4954 obsoleting RFC 2554, and CRAM-MD5 RFC 2195. The Delivery Status Notification set consists of four draft standards, RFC 3461 obsoletes RFC 1891, RFC 3462 obsoletes RFC 1892, RFC 3463 obsoletes RFC 1893, RFC 3464 obsoletes RFC 1894. I think you don't need the old 189x numbers, the way how Wikipedia links RFCs is much better than it used to be back in 2006. --217.184.142.41 (talk) 02:03, 3 June 2008 (UTC)

Could consider adding RFC 1294 (obsolete), RFC 1490 (obsolete), and RFC 2427 with related article links to Frame Relay / ATM. fonetikli 02:34, 16 May 2006 (UTC)

Done, please review my additions. Cburnett 02:12, 17 March 2007 (UTC)

[edit] Deflate and such

Can RFC 1950, RFC 1951 and RFC 1952 be in this list? --134.58.253.131 21:06, 14 February 2007 (UTC)

Done, please review my additions. Cburnett 02:12, 17 March 2007 (UTC)

[edit] RTP

Any special reason why it refers to the obsolute rfc 1889 instead of rfc 3550

[edit] Transclusion to other pages?

Given that there are protocol specific pages referencing RFCs for that protocol (SMTP,LDAP,MIME, etc), does it make sense to re-format the topical list so that each protocol specific list of RFCs can be standardized and re-used? This may also make it easier to maintain the list of RFCs as editors interested in those specific protocols could then maintain the specific list. I've coded up an example of what I am talking abou at User:Crkey/Sandbox/List of RFCs and User:Crkey/Sandbox/RFCs for LDAP and User:Crkey/Sandbox/RFCs for IRC. Crkey (talk) 18:46, 16 May 2008 (UTC)

That's a nice idea! I wonder if they could become more proper navboxes (collapsable, with "e" or "edit" link, etc.), so that editors could get to the actual content more easily from whatever page transcludes it? The history of invidivual specs is convoluted sometimes (look at the last section listing them on LDAP!), so having it collapsed-by-default but actually including all relevant ones would make it more reader-friendly when transcluded into that page. DMacks (talk) 19:15, 16 May 2008 (UTC)

Navboxes might be a good idea. I like that you'd be able to collapse them, though for some of the topics, like BEEP, that only have a few RFCs it might be over kill. Then again that's the same argument against my original suggestion. For what it's worth, I've updated my example with a pieced together navbox for the LDAP example. It could probably do for some better styling, but I'll leave that up to others to decide. Crkey (talk) 23:54, 16 May 2008 (UTC)