{"id":2103,"date":"2020-06-15T18:03:02","date_gmt":"2020-06-16T01:03:02","guid":{"rendered":"https:\/\/self-issued.info\/?p=2103"},"modified":"2020-06-15T18:03:02","modified_gmt":"2020-06-16T01:03:02","slug":"secevent-delivery-specs-now-unambiguously-require-tls","status":"publish","type":"post","link":"https:\/\/self-issued.info\/?p=2103","title":{"rendered":"SecEvent Delivery specs now unambiguously require TLS"},"content":{"rendered":"<p><span class=\"plain\"><img decoding=\"async\" align=\"right\" src=\"https:\/\/self-issued.info\/images\/ietf-logo.png\" alt=\"IETF logo\"><\/span>The SecEvent delivery specifications have been revised to unambiguously require the use of TLS, while preserving descriptions of precautions needed for non-TLS use in non-normative appendices.  Thanks to the <a href=\"https:\/\/datatracker.ietf.org\/group\/secevent\/charter\/\">Security Events<\/a> and <a href=\"https:\/\/openid.net\/wg\/sse\/\">Shared Signals and Events<\/a> working group members who weighed in on this decision.  I believe these drafts are now ready to be scheduled for an IESG telechat.<\/p>\n<p>The updated specifications are available at:<\/p>\n<ul>\n<li><a href=\"https:\/\/tools.ietf.org\/html\/draft-ietf-secevent-http-push-12\">https:\/\/tools.ietf.org\/html\/draft-ietf-secevent-http-push-12<\/a><\/li>\n<li><a href=\"https:\/\/tools.ietf.org\/html\/draft-ietf-secevent-http-poll-11\">https:\/\/tools.ietf.org\/html\/draft-ietf-secevent-http-poll-11<\/a><\/li>\n<\/ul>\n<p>HTML-formatted versions are also available at:<\/p>\n<ul>\n<li><a href=\"https:\/\/self-issued.info\/docs\/draft-ietf-secevent-http-push-12.html\">https:\/\/self-issued.info\/docs\/draft-ietf-secevent-http-push-12.html<\/a><\/li>\n<li><a href=\"https:\/\/self-issued.info\/docs\/draft-ietf-secevent-http-poll-11.html\">https:\/\/self-issued.info\/docs\/draft-ietf-secevent-http-poll-11.html<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>The SecEvent delivery specifications have been revised to unambiguously require the use of TLS, while preserving descriptions of precautions needed for non-TLS use in non-normative appendices. Thanks to the Security Events and Shared Signals and Events working group members who weighed in on this decision. I believe these drafts are now ready to be scheduled [&hellip;]<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[32,23,25],"tags":[],"class_list":["post-2103","post","type-post","status-publish","format-standard","hentry","category-ietf","category-security","category-specifications"],"_links":{"self":[{"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/posts\/2103","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/self-issued.info\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2103"}],"version-history":[{"count":1,"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/posts\/2103\/revisions"}],"predecessor-version":[{"id":2104,"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/posts\/2103\/revisions\/2104"}],"wp:attachment":[{"href":"https:\/\/self-issued.info\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2103"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/self-issued.info\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2103"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/self-issued.info\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2103"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}