{"id":264,"date":"2014-11-03T17:54:51","date_gmt":"2014-11-03T22:54:51","guid":{"rendered":"http:\/\/web.thinkingcat.com\/wordpress\/?page_id=264"},"modified":"2017-01-31T15:08:36","modified_gmt":"2017-01-31T20:08:36","slug":"technical-reports-rfcs","status":"publish","type":"page","link":"https:\/\/www.thinkingcat.com\/wordpress\/pubs\/technical-reports-rfcs\/","title":{"rendered":"RFCs and current Internet-Drafts"},"content":{"rendered":"<p>Daigle, L. (ed), &#8220;After the first decade: IASA Retrospective&#8221;, <a href=\"https:\/\/datatracker.ietf.org\/doc\/draft-daigle-iasa-retrospective\/\">draft-daigle-iasa-retrospective<\/a>, (-00 in October 2016).<\/p>\n<p>Daigle, L., and G. Deen, &#8220;Glass to Glass Internet Ecosystem URI and S-NAPTR Use&#8221;, <a href=\"https:\/\/datatracker.ietf.org\/doc\/draft-daigle-deen-ggie-uri-snaptr\/\">draft-daigle-deen-ggie-uri-snaptr<\/a>,\u00a0 (-00 in October 2016).<\/p>\n<p>Deen, G.,\u00a0 and L. Daigle, &#8220;Glass to Glass Internet Ecosystem Introduction&#8221;, <a href=\"https:\/\/datatracker.ietf.org\/doc\/draft-deen-daigle-ggie\/\">draft-deen-daigle-ggie<\/a>, (-02 in October 2016).<\/p>\n<p>Daigle, L. &#8220;Internet Application Identifier Architecture&#8221;, <a href=\"https:\/\/datatracker.ietf.org\/doc\/draft-daigle-appidarch\/\">draft-daigle-appidarch, <\/a>(-00 in September 2015).<\/p>\n<p>Daigle, L. (ed), O. Kolkman (ed), Internet Architecture Board (IAB), \u201cRFC Streams, Headers, and Boilerplates\u201d, <a href=\"http:\/\/www.ietf.org\/rfc\/rfc5741.txt\">RFC5741<\/a>, December 2009<\/p>\n<p>Daigle, L. (ed), Internet Architecture Board (IAB), \u201cThe RFC Series and RFC Editor\u201d, <a href=\"http:\/\/www.ietf.org\/rfc\/rfc4844.txt\">RFC4844<\/a>, July 2007.<\/p>\n<p>Daigle, L. (ed), Internet Architecture Board (IAB), \u201cProcess for Publication of IAB RFCs\u201d, <a href=\"http:\/\/www.ietf.org\/rfc\/rfc4845.txt\">RFC4845<\/a>, July 2007.<\/p>\n<p>Daigle, L., \u201cDomain-based Application Service Location Using URIs and the Dynamic Delegation Discovery Service (DDDS)\u201d, <a href=\"http:\/\/www.ietf.org\/rfc\/rfc4848.txt\">RFC4848<\/a>, April 2007.<\/p>\n<p>Daigle, L. (ed), Internet Architecture Board (IAB,\u00a0 \u201cIAB Processes for management of liaison relationships\u201d, <a href=\"http:\/\/www.ietf.org\/rfc\/rfc4052.txt\">RFC4052<\/a>, April 2005.<\/p>\n<p>Daigle, L. and A. Newton, \u201cDomain-based Application Service Location Using SRV RRs and the Dynamic Delegation Discovery Service (DDDS)\u201d, <a href=\"http:\/\/www.ietf.org\/rfc\/rfc3958.txt\">RFC3958<\/a>, January 2005.<\/p>\n<p>Daigle, L., \u201cWHOIS Protocol Specification\u201d, <a href=\"http:\/\/www.ietf.org\/rfc\/rfc3912.txt\">RFC3912<\/a>, September 2004.<\/p>\n<p>IAB Advisory Committee, \u201cThe IETF in the Large:\u00a0 Administration and Execution\u201d, <a href=\"http:\/\/www.ietf.org\/rfc\/rfc3716.txt\">RFC3716<\/a>, March 2004.<\/p>\n<p>Internet Architecture Board (IAB), L. Daigle (Ed), \u201cIETF ISOC Board of Trustee Appointment Procedures\u201d, <a href=\"http:\/\/www.ietf.org\/rfc\/rfc3677.txt\">RFC3677 (BCP77)<\/a>, December 2003.<\/p>\n<p>Internet Architecture Board (IAB), L. Daigle (Ed), \u201cIAB Considerations for UNilateral Self-Address Fixing (UNSAF)\u201d, <a href=\"http:\/\/www.ietf.org\/rfc\/rfc3424.txt\">RFC3424<\/a>, November 2002.<\/p>\n<p>Daigle, Leslie L., Dirk-Willem van Gulik, Renato Iannella, and Patrik F\u00e4ltstr\u00f6m, \u201cURN Namespace Definition Mechanisms\u201d, <a href=\"http:\/\/www.ietf.org\/rfc\/rfc3406.txt\">RFC3406<\/a>, October 2002.<\/p>\n<p>Internet Architecture Board (IAB), S. Floyd (Ed), L. Daigle (Ed), \u201cIAB Architectural and Policy Considerations for Open Pluggable Edge Services\u201d, <a href=\"http:\/\/www.ietf.org\/rfc\/rfc3238.txt\">RFC3238<\/a>, January 2002.<\/p>\n<p>Daigle, Leslie L. and Roland Hedberg, \u201cTISDAG &#8211; Technical Infrastructure for Swedish Directory Access Gateways\u201d, <a href=\"http:\/\/www.ietf.org\/rfc\/rfc2967.txt\">RFC2967<\/a>, October 2000.<\/p>\n<p>Daigle, Leslie L. and Thommy Ekl\u00f6f, \u201cMesh of Multiple DAG servers &#8211; Results from TISDAG\u201d, <a href=\"http:\/\/www.ietf.org\/rfc\/rfc2968.txt\">RFC2968<\/a>, October 2000.<\/p>\n<p>Daigle, Leslie L. and Thommy Ekl\u00f6f, \u201cArchitecture for Integrated Directory Services \u2013 Results from TISDAG\u201d, <a href=\"http:\/\/www.ietf.org\/rfc\/rfc2970.txt\">RFC2970<\/a>, October 2000.<\/p>\n<p>Ekl\u00f6f, Thommy and Leslie L. Daigle, \u201cWide Area Directory Deployment \u2013 Experiences from TISDAG\u201d, <a href=\"http:\/\/www.ietf.org\/rfc\/rfc2969.txt\">RFC2969<\/a>, October 2000.<\/p>\n<p>Daigle, Leslie L. and Patrik F\u00e4ltstr\u00f6m, \u201cThe application\/whoispp-query Content-Type\u201d, <a href=\"http:\/\/www.ietf.org\/rfc\/rfc2957.txt\">RFC2957<\/a>, October 2000.<\/p>\n<p>Daigle, Leslie L. and Patrik F\u00e4ltstr\u00f6m, \u201cThe application\/whoispp-response Content-Type\u201d, <a href=\"http:\/\/www.ietf.org\/rfc\/rfc2958.txt\">RFC2958<\/a>, October 2000.<\/p>\n<p>Daigle, L. (Ed), \u201cA Tangled Web: Issues of I18N, Domain Names, and the Other Internet protocols\u201d, <a href=\"http:\/\/www.ietf.org\/rfc\/rfc2825.txt\">RFC 2825<\/a>, May 2000.<\/p>\n<p>Daigle, Leslie L., Dirk-Willem van Gulik, Renato Iannella, and Patrik F\u00e4ltstr\u00f6m, \u201cURN Namespace Definition Mechanisms\u201d, <a href=\"http:\/\/www.ietf.org\/rfc\/rfc2611.txt\">RFC2611 (BCP 33)<\/a>, June 1999.<\/p>\n<p>Daigle, Leslie L., Peter Deutsch, Bill Heelan, Chris Alpaugh, and Mary Maclachlan, \u201cUniform Resource Agents (URAs)\u201d.\u00a0 <a href=\"http:\/\/www.ietf.org\/rfc\/rfc2016.txt\">RFC2016<\/a>, October 31, 1996.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Daigle, L. (ed), &#8220;After the first decade: IASA Retrospective&#8221;, draft-daigle-iasa-retrospective, (-00 in October 2016). Daigle, L., and G. Deen, &#8220;Glass to Glass Internet Ecosystem URI and S-NAPTR Use&#8221;, draft-daigle-deen-ggie-uri-snaptr,\u00a0 (-00 in October 2016). Deen, G.,\u00a0 and L. Daigle, &#8220;Glass to Glass Internet Ecosystem Introduction&#8221;, draft-deen-daigle-ggie, (-02 in October 2016). Daigle, L. &#8220;Internet Application Identifier Architecture&#8221;, [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"parent":46,"menu_order":3,"comment_status":"open","ping_status":"closed","template":"full-width-page.php","meta":{"jetpack_post_was_ever_published":false,"footnotes":""},"class_list":["post-264","page","type-page","status-publish","hentry"],"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/PbjRsG-4g","_links":{"self":[{"href":"https:\/\/www.thinkingcat.com\/wordpress\/wp-json\/wp\/v2\/pages\/264","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.thinkingcat.com\/wordpress\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.thinkingcat.com\/wordpress\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.thinkingcat.com\/wordpress\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.thinkingcat.com\/wordpress\/wp-json\/wp\/v2\/comments?post=264"}],"version-history":[{"count":6,"href":"https:\/\/www.thinkingcat.com\/wordpress\/wp-json\/wp\/v2\/pages\/264\/revisions"}],"predecessor-version":[{"id":480,"href":"https:\/\/www.thinkingcat.com\/wordpress\/wp-json\/wp\/v2\/pages\/264\/revisions\/480"}],"up":[{"embeddable":true,"href":"https:\/\/www.thinkingcat.com\/wordpress\/wp-json\/wp\/v2\/pages\/46"}],"wp:attachment":[{"href":"https:\/\/www.thinkingcat.com\/wordpress\/wp-json\/wp\/v2\/media?parent=264"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}