update documents

data/RFC8947.xml

@@ -7,7 +7,7 @@
     <author fullname="T. Mrugalski" initials="T." surname="Mrugalski">
       <organization/>
     </author>
-    <author fullname="C. Bernardos" initials="C." surname="Bernardos">
+    <author fullname="CJ. Bernardos" initials="CJ." surname="Bernardos">
       <organization/>
     </author>
     <author>

data/RFC9706.xml

@@ -0,0 +1,25 @@
+<reference anchor="RFC.9706" target="https://www.rfc-editor.org/info/rfc9706">
+  <front>
+    <title>TreeDN: Tree-Based Content Delivery Network (CDN) for Live Streaming to Mass Audiences</title>
+    <author fullname="L. Giuliano" initials="L." surname="Giuliano">
+      <organization/>
+    </author>
+    <author fullname="C. Lenart" initials="C." surname="Lenart">
+      <organization/>
+    </author>
+    <author fullname="R. Adam" initials="R." surname="Adam">
+      <organization/>
+    </author>
+    <author>
+      <organization>RFC Series</organization>
+    </author>
+    <date year="2025" month="January"/>
+    <workgroup>mops</workgroup>
+    <abstract>
+      <t>As Internet audience sizes for high-interest live events reach unprecedented levels and bitrates climb to support formats and applications such as 4K, 8K, and Augmented Reality (AR), live streaming can place a unique type of stress upon network resources. TreeDN is a tree-based Content Delivery Network (CDN) architecture designed to address the distinctive scaling challenges of live streaming to mass audiences. TreeDN enables operators to offer Replication-as-a-Service (RaaS) at a fraction of the cost of traditional, unicast-based CDNs -- in some cases, at no additional cost to the infrastructure. In addition to efficiently utilizing network resources to deliver existing multi-destination traffic, this architecture also enables new types of content and use cases that previously were not possible or economically viable using traditional CDN approaches. Finally, TreeDN is a decentralized architecture and a democratizing technology that makes content distribution more accessible to more people by dramatically reducing the costs of replication.</t>
+    </abstract>
+  </front>
+  <seriesInfo name="DOI" value="10.17487/RFC9706"/>
+  <seriesInfo name="RFC" value="9706"/>
+  <seriesInfo name="IETF"/>
+</reference>

data/RFC9713.xml

@@ -0,0 +1,19 @@
+<reference anchor="RFC.9713" target="https://www.rfc-editor.org/info/rfc9713">
+  <front>
+    <title>Bundle Protocol Version 7 Administrative Record Types Registry</title>
+    <author fullname="B. Sipos" initials="B." surname="Sipos">
+      <organization/>
+    </author>
+    <author>
+      <organization>RFC Series</organization>
+    </author>
+    <date year="2025" month="January"/>
+    <workgroup>dtn</workgroup>
+    <abstract>
+      <t>This document updates RFC 9171 to clarify that Bundle Protocol Version 7 agents are expected to use the IANA "Bundle Administrative Record Types" registry to identify and document administrative record types. This document also designates code points for Private and Experimental Use.</t>
+    </abstract>
+  </front>
+  <seriesInfo name="DOI" value="10.17487/RFC9713"/>
+  <seriesInfo name="RFC" value="9713"/>
+  <seriesInfo name="IETF"/>
+</reference>

data/RFC9720.xml

@@ -0,0 +1,22 @@
+<reference anchor="RFC.9720" target="https://www.rfc-editor.org/info/rfc9720">
+  <front>
+    <title>RFC Formats and Versions</title>
+    <author fullname="P. Hoffman" initials="P." surname="Hoffman">
+      <organization/>
+    </author>
+    <author fullname="H. Flanagan" initials="H." surname="Flanagan">
+      <organization/>
+    </author>
+    <author>
+      <organization>RFC Series</organization>
+    </author>
+    <date year="2025" month="January"/>
+    <abstract>
+      <t>In order to improve the readability of RFCs while supporting their archivability, the definitive version of the RFC Series transitioned from plain-text ASCII to XML using the RFCXML vocabulary; different publication versions are rendered from that base document. This document describes how RFCs are published.</t>
+      <t>This document obsoletes RFC 7990. This document also updates the stability policy in RFC 9280.</t>
+    </abstract>
+  </front>
+  <seriesInfo name="DOI" value="10.17487/RFC9720"/>
+  <seriesInfo name="RFC" value="9720"/>
+  <seriesInfo name="Editorial"/>
+</reference>

flag.txt

@@ -1 +1 @@
-Fri Jan 17 15:16:45 UTC 2025
+Sat Jan 18 15:14:52 UTC 2025