faqs.org - Internet FAQ Archives

RFC Title Index 8101 - 8200

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


Or Display the document by number



  • RFC 8101 - IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespace for Mission Critical Push To Talk Service
  • RFC 8102 - Remote-LFA Node Protection and Manageability
  • RFC 8103 - Using ChaCha20-Poly1305 Authenticated Encryption in the Cryptographic Message Syntax (CMS)
  • RFC 8104 - Pseudowire (PW) Endpoint Fast Failure Protection
  • RFC 8105 - Transmission of IPv6 Packets over Digital Enhanced Cordless Telecommunications (DECT) Ultra Low Energy (ULE)
  • RFC 8106 - IPv6 Router Advertisement Options for DNS Configuration
  • RFC 8107 - Advertising Digital Identifier (Ad-ID) URN Namespace Definition
  • RFC 8108 - Sending Multiple RTP Streams in a Single RTP Session
  • RFC 8109 - Initializing a DNS Resolver with Priming Queries
  • RFC 8110 - Opportunistic Wireless Encryption
  • RFC 8111 - Locator/ID Separation Protocol Delegated Database Tree (LISP-DDT)
  • RFC 8112 - Locator/ID Separation Protocol Delegated Database Tree (LISP-DDT) Referral Internet Groper (RIG)
  • RFC 8113 - Locator/ID Separation Protocol (LISP): Shared Extension Message & IANA Registry for Packet Type Allocations
  • RFC 8114 - Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast Network
  • RFC 8115 - DHCPv6 Option for IPv4-Embedded Multicast and Unicast IPv6 Prefixes
  • RFC 8116 - Security Threats to the Optimized Link State Routing Protocol Version 2 (OLSRv2)
  • RFC 8117 - Current Hostname Practice Considered Harmful
  • RFC 8118 - The application/pdf Media Type
  • RFC 8119 - SIP "cause" URI Parameter for Service Number Translation
  • RFC 8120 - Mutual Authentication Protocol for HTTP
  • RFC 8121 - Mutual Authentication Protocol for HTTP: Cryptographic Algorithms Based on the Key Agreement Mechanism 3 (KAM3)
  • RFC 8122 - Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP)
  • RFC 8123 - Requirements for Marking SIP Messages to be Logged
  • RFC 8124 - The Session Description Protocol (SDP) WebSocket Connection URI Attribute
  • RFC 8125 - Requirements for Password-Authenticated Key Agreement (PAKE) Schemes
  • RFC 8126 - Guidelines for Writing an IANA Considerations Section in RFCs
  • RFC 8128 - IETF Appointment Procedures for the ICANN Root Zone Evolution Review Committee
  • RFC 8129 - Authentication Indicator in Kerberos Tickets
  • RFC 8130 - RTP Payload Format for the Mixed Excitation Linear Prediction Enhanced (MELPe) Codec
  • RFC 8131 - RSVP-TE Signaling Procedure for End-to-End GMPLS Restoration and Resource Sharing
  • RFC 8132 - PATCH and FETCH Methods for the Constrained Application Protocol (CoAP)
  • RFC 8133 - The Security Evaluated Standardized Password-Authenticated Key Exchange (SESPAKE) Protocol
  • RFC 8134 - Management Incident Lightweight Exchange (MILE) Implementation Report
  • RFC 8135 - Complex Addressing in IPv6
  • RFC 8136 - Additional Transition Functionality for IPv6
  • RFC 8137 - IEEE 802.15.4 Information Element for the IETF
  • RFC 8138 - IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Routing Header
  • RFC 8139 - Transparent Interconnection of Lots of Links (TRILL): Appointed Forwarders
  • RFC 8140 - The Arte of ASCII: Or, An True and Accurate Representation of an Menagerie of Thynges Fabulous and Wonderful in Ye Forme of Character
  • RFC 8141 - Uniform Resource Names (URNs)
  • RFC 8142 - GeoJSON Text Sequences
  • RFC 8143 - Using Transport Layer Security (TLS) with Network News Transfer Protocol (NNTP)
  • RFC 8144 - Use of the Prefer Header Field in Web Distributed Authoring and Versioning (WebDAV)
  • RFC 8145 - Signaling Trust Anchor Knowledge in DNS Security Extensions (DNSSEC)
  • RFC 8146 - Adding Support for Salted Password Databases to EAP-pwd
  • RFC 8147 - Next-Generation Pan-European eCall
  • RFC 8148 - Next-Generation Vehicle-Initiated Emergency Calls
  • RFC 8149 - RSVP Extensions for Reoptimization of Loosely Routed Point-to-Multipoint Traffic Engineering Label Switched Paths (LSPs)
  • RFC 8150 - MPLS Transport Profile Linear Protection MIB
  • RFC 8151 - Use Cases for Data Center Network Virtualization Overlay Networks
  • RFC 8153 - Digital Preservation Considerations for the RFC Series
  • RFC 8154 - Parallel NFS (pNFS) Small Computer System Interface (SCSI) Layout
  • RFC 8155 - Traversal Using Relays around NAT (TURN) Server Auto Discovery
  • RFC 8156 - DHCPv6 Failover Protocol
  • RFC 8157 - Huawei's GRE Tunnel Bonding Protocol
  • RFC 8159 - Keyed IPv6 Tunnel
  • RFC 8160 - IUTF8 Terminal Mode in Secure Shell (SSH)
  • RFC 8161 - Benchmarking the Neighbor Discovery Protocol
  • RFC 8162 - Using Secure DNS to Associate Certificates with Domain Names for S/MIME
  • RFC 8163 - Transmission of IPv6 over Master-Slave/Token-Passing (MS/TP) Networks
  • RFC 8164 - Opportunistic Security for HTTP/2
  • RFC 8165 - Design Considerations for Metadata Insertion
  • RFC 8168 - DHCPv6 Prefix-Length Hint Issues
  • RFC 8169 - Residence Time Measurement in MPLS Networks
  • RFC 8170 - Planning for Protocol Adoption and Subsequent Transitions
  • RFC 8171 - Transparent Interconnection of Lots of Links (TRILL): Edge Directory Assistance Mechanisms
  • RFC 8173 - Precision Time Protocol Version 2 (PTPv2) Management Information Base
  • RFC 8174 - Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
  • RFC 8175 - Dynamic Link Exchange Protocol (DLEP)
  • RFC 8176 - Authentication Method Reference Values
  • RFC 8177 - YANG Data Model for Key Chains
  • RFC 8179 - Intellectual Property Rights in IETF Technology
  • RFC 8180 - Minimal IPv6 over the TSCH Mode of IEEE 802.15.4e (6TiSCH) Configuration
  • RFC 8186 - Support of the IEEE 1588 Timestamp Format in a Two-Way Active Measurement Protocol (TWAMP)
  • RFC 8188 - Encrypted Content-Encoding for HTTP


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