한국   대만   중국   일본 
페이지를 파싱하기 어렵습니다. Recent RFCs Recently published RFCs 2024-06-11T19:58:24-07:00 RFC Editor https://www.rfc-editor.org RFC 9584: RTP Payload Format for Essential Video Coding (EVC) https://www.rfc-editor.org/info/rfc9584 2024-06-11T00:00:00-07:00 This document describes an RTP payload format for the Essential Video Coding (EVC) standard, published as ISO/IEC International Standard 23094-1. EVC was developed by the MPEG. The RTP payload format allows for the packetization of one or more Network Abstraction Layer (NAL) units in each RTP packet payload and the fragmentation of a NAL unit into multiple RTP packets. The payload format has broad applicability in videoconferencing, Internet video streaming, and high-bitrate entertainment-quality video, among other applications. RFC 9596: CBOR Object Signing and Encryption (COSE) "typ" (type) Header Parameter https://www.rfc-editor.org/info/rfc9596 2024-06-11T00:00:00-07:00 This specification adds the equivalent of the JSON Object Signing and Encryption (JOSE) "typ" (type) header parameter to CBOR Object Signing and Encryption (COSE). This enables the benefits of explicit typing (as defined in RFC 8725, "JSON Web Token Best Current Practices") to be brought to COSE objects. The syntax of the COSE type header parameter value is the same as the existing COSE content type header parameter. RFC 9587: YANG Data Model for OSPFv3 Extended Link State Advertisements (LSAs) https://www.rfc-editor.org/info/rfc9587 2024-06-07T00:00:00-07:00 This document defines a YANG data model augmenting the IETF OSPF YANG data model (RFC 9129) to provide support for OSPFv3 Link State Advertisement (LSA) Extensibility as defined in RFC 8362. OSPFv3 Extended LSAs provide extensible TLV-based LSAs for the base LSA types defined in RFC 5340. RFC 9579: Use of Password-Based Message Authentication Code 1 (PBMAC1) in PKCS #12 Syntax https://www.rfc-editor.org/info/rfc9579 2024-05-31T00:00:00-07:00 This document specifies additions and amendments to RFCs 7292 and 8018. It defines a way to use the Password-Based Message Authentication Code 1 (PBMAC1), defined in RFC 8018, inside the PKCS #12 syntax. The purpose of this specification is to permit the use of more modern Password-Based Key Derivation Functions (PBKDFs) and allow for regulatory compliance. RFC 9590: IMAP Extension for Returning Mailbox METADATA in Extended LIS https://www.rfc-editor.org/info/rfc9590 2024-05-31T00:00:00-07:00 This document defines an extension to the Internet Message Access Protocol (IMAP) LIST command that allows the client to request mailbox annotations (metadata), along with other information typically returned by the LIST command. RFC 9585: IMAP Response Code for Command Progress Notifications https://www.rfc-editor.org/info/rfc9585 2024-05-31T00:00:00-07:00 This document defines a new IMAP untagged response code, "INPROGRESS", that provides progress notifications regarding the status of long-running commands. RFC 9586: IMAP Extension for Using and Returning Unique Identifiers (UIDs) Only https://www.rfc-editor.org/info/rfc9586 2024-05-30T00:00:00-07:00 The UIDONLY extension to the Internet Message Access Protocol (RFCs 3501 and 9051) allows clients to enable a mode in which information about mailbox changes is returned using only Unique Identifiers (UIDs). Message numbers are not returned in responses and cannot be used in requests once this extension is enabled. This helps both clients and servers to reduce resource usage required to maintain a map between message numbers and UIDs. This document defines an experimental IMAP extension. RFC 9571: Extension of RFC 6374-Based Performance Measurement Using Synonymous Flow Labels https://www.rfc-editor.org/info/rfc9571 2024-05-29T00:00:00-07:00 RFC 6374 describes methods of making loss and delay measurements on Label Switched Paths (LSPs) primarily as they are used in MPLS Transport Profile (MPLS-TP) networks. This document describes a method of extending the performance measurements (specified in RFC 6374) from flows carried over MPLS-TP to flows carried over generic MPLS LSPs. In particular, it extends the technique to allow loss and delay measurements to be made on multipoint-to-point LSPs and introduces some additional techniques to allow more sophisticated measurements to be made in both MPLS-TP and generic MPLS networks. RFC 9548: Generating Transport Key Containers (PFX) Using the GOST Algorithms https://www.rfc-editor.org/info/rfc9548 2024-05-29T00:00:00-07:00 This document specifies how to use "PKCS #12: Personal Information Exchange Syntax v1.1" (RFC 7292) to transport key containers (PFX) for storing keys and certificates in conjunction with the Russian national standard GOST algorithms. This specification has been developed outside the IETF. The purpose of publication is to facilitate interoperable implementations that wish to support the GOST algorithms. This document does not imply IETF endorsement of the cryptographic algorithms used here. RFC 9572: Updates to EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Procedures https://www.rfc-editor.org/info/rfc9572 2024-05-24T00:00:00-07:00 This document specifies updated procedures for handling Broadcast, Unknown Unicast, or Multicast (BUM) traffic in Ethernet VPNs (EVPNs), including selective multicast and segmentation of provider tunnels. This document updates RFC 7432. RFC 9574: Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs) https://www.rfc-editor.org/info/rfc9574 2024-05-24T00:00:00-07:00 Network Virtualization Overlay (NVO) networks using Ethernet VPNs (EVPNs) as their control plane may use trees based on ingress replication or Protocol Independent Multicast (PIM) to convey the overlay Broadcast, Unknown Unicast, or Multicast (BUM) traffic. PIM provides an efficient solution that prevents sending multiple copies of the same packet over the same physical link; however, it may not always be deployed in the NVO network core. Ingress replication avoids the dependency on PIM in the NVO network core. While ingress replication provides a simple multicast transport, some NVO networks with demanding multicast applications require a more efficient solution without PIM in the core. This document describes a solution to optimize the efficiency of ingress replication trees. RFC 9573: MVPN/EVPN Tunnel Aggregation with Common Labels https://www.rfc-editor.org/info/rfc9573 2024-05-24T00:00:00-07:00 The Multicast VPN (MVPN) specifications allow a single Point-to-Multipoint (P2MP) tunnel to carry traffic of multiple IP VPNs (referred to as VPNs in this document). The EVPN specifications allow a single P2MP tunnel to carry traffic of multiple Broadcast Domains (BDs). These features require the ingress router of the P2MP tunnel to allocate an upstream-assigned MPLS label for each VPN or for each BD. A packet sent on a P2MP tunnel then carries the label that is mapped to its VPN or BD (in some cases, a distinct upstream-assigned label is needed for each flow.) Since each ingress router allocates labels independently, with no coordination among the ingress routers, the egress routers may need to keep track of a large number of labels. The number of labels may need to be as large as, or larger than, the product of the number of ingress routers times the number of VPNs or BDs. However, the number of labels can be greatly reduced if the association between a label and a VPN or BD is made by provisioning, so that all ingress routers assign the same label to a particular VPN or BD. New procedures are needed in order to take advantage of such provisioned labels. These new procedures also apply to Multipoint-to-Multipoint (MP2MP) tunnels. This document updates RFCs 6514, 7432, and 7582 by specifying the necessary procedures. RFC 9582: A Profile for Route Origin Authorizations (ROAs) https://www.rfc-editor.org/info/rfc9582 2024-05-23T00:00:00-07:00 This document defines a standard profile for Route Origin Authorizations (ROAs). A ROA is a digitally signed object that provides a means of verifying that an IP address block holder has authorized an Autonomous System (AS) to originate routes to one or more prefixes within the address block. This document obsoletes RFC 6482. RFC 9598: Internationalized Email Addresses in X.509 Certificates https://www.rfc-editor.org/info/rfc9598 2024-05-23T00:00:00-07:00 This document defines a new name form for inclusion in the otherName field of an X.509 Subject Alternative Name and Issuer Alternative Name extension that allows a certificate subject to be associated with an internationalized email address. This document updates RFC 5280 and obsoletes RFC 8398. RFC 9589: On the Use of the Cryptographic Message Syntax (CMS) Signing-Time Attribute in Resource Public Key Infrastructure (RPKI) Signed Objects https://www.rfc-editor.org/info/rfc9589 2024-05-23T00:00:00-07:00 In the Resource Public Key Infrastructure (RPKI), Signed Objects are defined as Cryptographic Message Syntax (CMS) protected content types. A Signed Object contains a signing-time attribute, representing the purported time at which the object was signed by its issuer. RPKI repositories are accessible using the rsync and RPKI Repository Delta protocols, allowing Relying Parties (RPs) to synchronize a local copy of the RPKI repository used for validation with the remote repositories. This document describes how the CMS signing-time attribute can be used to avoid needless retransfers of data when switching between different synchronization protocols. This document updates RFC 6488 by mandating the presence of the CMS signing-time attribute and disallowing the use of the binary-signing-time attribute.