update documents

data/RFC9581.xml

@@ -0,0 +1,26 @@
+<reference anchor="RFC.9581" target="https://www.rfc-editor.org/info/rfc9581">
+  <front>
+    <title>Concise Binary Object Representation (CBOR) Tags for Time, Duration, and Period</title>
+    <author fullname="C. Bormann" initials="C." surname="Bormann">
+      <organization/>
+    </author>
+    <author fullname="B. Gamari" initials="B." surname="Gamari">
+      <organization/>
+    </author>
+    <author fullname="H. Birkholz" initials="H." surname="Birkholz">
+      <organization/>
+    </author>
+    <author>
+      <organization>RFC Series</organization>
+    </author>
+    <date year="2024" month="August"/>
+    <workgroup>cbor</workgroup>
+    <abstract>
+      <t>The Concise Binary Object Representation (CBOR, RFC 8949) is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation.</t>
+      <t>In CBOR, one point of extensibility is the definition of CBOR tags. RFC 8949 defines two tags for time: CBOR tag 0 (RFC 3339 time as a string) and tag 1 (POSIX time as int or float). Since then, additional requirements have become known. The present document defines a CBOR tag for time that allows a more elaborate representation of time, as well as related CBOR tags for duration and time period. This document is intended as the reference document for the IANA registration of the CBOR tags defined.</t>
+    </abstract>
+  </front>
+  <seriesInfo name="DOI" value="10.17487/RFC9581"/>
+  <seriesInfo name="RFC" value="9581"/>
+  <seriesInfo name="IETF"/>
+</reference>

data/RFC9604.xml

@@ -0,0 +1,31 @@
+<reference anchor="RFC.9604" target="https://www.rfc-editor.org/info/rfc9604">
+  <front>
+    <title>Carrying Binding Label/SID in PCE-Based Networks</title>
+    <author fullname="S. Sivabalan" initials="S." surname="Sivabalan">
+      <organization/>
+    </author>
+    <author fullname="C. Filsfils" initials="C." surname="Filsfils">
+      <organization/>
+    </author>
+    <author fullname="J. Tantsura" initials="J." surname="Tantsura">
+      <organization/>
+    </author>
+    <author fullname="S. Previdi" initials="S." surname="Previdi">
+      <organization/>
+    </author>
+    <author role="editor" fullname="C. Li" initials="C." surname="Li">
+      <organization/>
+    </author>
+    <author>
+      <organization>RFC Series</organization>
+    </author>
+    <date year="2024" month="August"/>
+    <workgroup>pce</workgroup>
+    <abstract>
+      <t>In order to provide greater scalability, network confidentiality, and service independence, Segment Routing (SR) utilizes a Binding Segment Identifier (BSID), as described in RFC 8402. It is possible to associate a BSID to an RSVP-TE-signaled Traffic Engineering (TE) Label Switched Path (LSP) or an SR TE path. The BSID can be used by an upstream node for steering traffic into the appropriate TE path to enforce SR policies. This document specifies the concept of binding value, which can be either an MPLS label or a Segment Identifier (SID). It further specifies an extension to Path Computation Element Communication Protocol (PCEP) for reporting the binding value by a Path Computation Client (PCC) to the Path Computation Element (PCE) to support PCE-based TE policies.</t>
+    </abstract>
+  </front>
+  <seriesInfo name="DOI" value="10.17487/RFC9604"/>
+  <seriesInfo name="RFC" value="9604"/>
+  <seriesInfo name="IETF"/>
+</reference>

flag.txt

@@ -1 +1 @@
-Fri Aug 16 15:14:52 UTC 2024
+Sat Aug 17 15:14:11 UTC 2024