faqs.org - Internet FAQ Archives

RFC Title Index 8501 - 8600

[ FAQS.ORG Home | RFC Index | Search | What's New | Help ]


Or Display the document by number



  • RFC 8501 - Reverse DNS in IPv6 for Internet Service Providers
  • RFC 8502 - L2L3 VPN Multicast MIB
  • RFC 8503 - BGP/MPLS Layer 3 VPN Multicast Management Information Base
  • RFC 8504 - IPv6 Node Requirements
  • RFC 8505 - Registration Extensions for IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Neighbor Discovery
  • RFC 8506 - Diameter Credit-Control Application
  • RFC 8507 - Simple Internet Protocol (SIP) Specification
  • RFC 8508 - IMAP REPLACE Extension
  • RFC 8509 - A Root Key Trust Anchor Sentinel for DNSSEC
  • RFC 8510 - OSPF Link-Local Signaling (LLS) Extensions for Local Interface ID Advertisement
  • RFC 8511 - TCP Alternative Backoff with ECN (ABE)
  • RFC 8512 - A YANG Module for Network Address Translation (NAT) and Network Prefix Translation (NPT)
  • RFC 8513 - A YANG Data Model for Dual-Stack Lite (DS-Lite)
  • RFC 8514 - Internet Message Access Protocol (IMAP) - SAVEDATE Extension
  • RFC 8515 - URN Namespace for ETSI Documents
  • RFC 8516 - "Too Many Requests" Response Code for the Constrained Application Protocol
  • RFC 8517 - An Inventory of Transport-Centric Functions Provided by Middleboxes: An Operator Perspective
  • RFC 8518 - Selection of Loop-Free Alternates for Multi-Homed Prefixes
  • RFC 8519 - YANG Data Model for Network Access Control Lists (ACLs)
  • RFC 8520 - Manufacturer Usage Description Specification
  • RFC 8521 - Registration Data Access Protocol (RDAP) Object Tagging
  • RFC 8522 - Looking Glass Command Set
  • RFC 8525 - YANG Library
  • RFC 8526 - NETCONF Extensions to Support the Network Management Datastore Architecture
  • RFC 8527 - RESTCONF Extensions to Support the Network Management Datastore Architecture
  • RFC 8528 - YANG Schema Mount
  • RFC 8529 - YANG Data Model for Network Instances
  • RFC 8530 - YANG Model for Logical Network Elements
  • RFC 8531 - Generic YANG Data Model for Connection-Oriented Operations, Administration, and Maintenance (OAM) Protocols
  • RFC 8532 - Generic YANG Data Model for the Management of Operations, Administration, and Maintenance (OAM) Protocols That Use Connectionless Communications
  • RFC 8533 - A YANG Data Model for Retrieval Methods for the Management of Operations, Administration, and Maintenance (OAM) Protocols That Use Connectionless Communications
  • RFC 8534 - Explicit Tracking with Wildcard Routes in Multicast VPN
  • RFC 8536 - The Time Zone Information Format (TZif)
  • RFC 8537 - Updates to the Fast Reroute Procedures for Co-routed Associated Bidirectional Label Switched Paths (LSPs)
  • RFC 8538 - Notification Message Support for BGP Graceful Restart
  • RFC 8539 - Softwire Provisioning Using DHCPv4 over DHCPv6
  • RFC 8540 - Stream Control Transmission Protocol: Errata and Issues in RFC 4960
  • RFC 8541 - Impact of Shortest Path First (SPF) Trigger and Delay Strategies on IGP Micro-loops
  • RFC 8542 - A YANG Data Model for Fabric Topology in Data-Center Networks
  • RFC 8543 - Extensible Provisioning Protocol (EPP) Organization Mapping
  • RFC 8544 - Organization Extension for the Extensible Provisioning Protocol (EPP)
  • RFC 8545 - Well-Known Port Assignments for the One-Way Active Measurement Protocol (OWAMP) and the Two-Way Active Measurement Protocol (TWAMP)
  • RFC 8546 - The Wire Image of a Network Protocol
  • RFC 8549 - Export of BGP Community Information in IP Flow Information Export (IPFIX)
  • RFC 8550 - Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 4.0 Certificate Handling
  • RFC 8551 - Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 4.0 Message Specification
  • RFC 8552 - Scoped Interpretation of DNS Resource Records through "Underscored" Naming of Attribute Leaves
  • RFC 8553 - DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node Names
  • RFC 8554 - Leighton-Micali Hash-Based Signatures
  • RFC 8555 - Automatic Certificate Management Environment (ACME)
  • RFC 8556 - Multicast VPN Using Bit Index Explicit Replication (BIER)
  • RFC 8558 - Transport Protocol Path Signals
  • RFC 8559 - Dynamic Authorization Proxying in the Remote Authentication Dial-In User Service (RADIUS) Protocol
  • RFC 8560 - Seamless Integration of Ethernet VPN (EVPN) with Virtual Private LAN Service (VPLS) and Their Provider Backbone Bridge (PBB) Equivalents
  • RFC 8562 - Bidirectional Forwarding Detection (BFD) for Multipoint Networks
  • RFC 8563 - Bidirectional Forwarding Detection (BFD) Multipoint Active Tails
  • RFC 8564 - Support of Point-to-Multipoint Bidirectional Forwarding Detection (BFD) in Transparent Interconnection of Lots of Links (TRILL)
  • RFC 8565 - Hypertext Jeopardy Protocol (HTJP/1.0)
  • RFC 8567 - Customer Management DNS Resource Records
  • RFC 8568 - Network Virtualization Research Challenges
  • RFC 8570 - IS-IS Traffic Engineering (TE) Metric Extensions
  • RFC 8571 - BGP - Link State (BGP-LS) Advertisement of IGP Traffic Engineering Performance Metric Extensions
  • RFC 8572 - Secure Zero Touch Provisioning (SZTP)
  • RFC 8574 - cite-as: A Link Relation to Convey a Preferred URI for Referencing
  • RFC 8575 - YANG Data Model for the Precision Time Protocol (PTP)
  • RFC 8576 - Internet of Things (IoT) Security: State of the Art and Challenges
  • RFC 8577 - Signaling RSVP-TE Tunnels on a Shared MPLS Forwarding Plane
  • RFC 8578 - Deterministic Networking Use Cases
  • RFC 8579 - Sieve Email Filtering: Delivering to Special-Use Mailboxes
  • RFC 8580 - Sieve Extension: File Carbon Copy (FCC)
  • RFC 8584 - Framework for Ethernet VPN Designated Forwarder Election Extensibility
  • RFC 8585 - Requirements for IPv6 Customer Edge Routers to Support IPv4-as-a-Service
  • RFC 8586 - Loop Detection in Content Delivery Networks (CDNs)
  • RFC 8587 - NFS Version 4.0 Trunking Update
  • RFC 8588 - Personal Assertion Token (PaSSporT) Extension for Signature-based Handling of Asserted information using toKENs (SHAKEN)
  • RFC 8590 - Change Poll Extension for the Extensible Provisioning Protocol (EPP)
  • RFC 8591 - SIP-Based Messaging with S/MIME
  • RFC 8592 - Key Performance Indicator (KPI) Stamping for the Network Service Header (NSH)
  • RFC 8593 - Video Traffic Models for RTP Congestion Control Evaluations
  • RFC 8594 - The Sunset HTTP Header Field
  • RFC 8597 - Cooperating Layered Architecture for Software-Defined Networking (CLAS)


[ FAQS.ORG Home | RFC Index | Search | What's New | Help ]