- RFC 5301 - Dynamic Hostname Exchange Mechanism for IS-IS
- RFC 5302 - Domain-Wide Prefix Distribution with Two-Level IS-IS
- RFC 5303 - Three-Way Handshake for IS-IS Point-to-Point Adjacencies
- RFC 5304 - IS-IS Cryptographic Authentication
- RFC 5305 - IS-IS Extensions for Traffic Engineering
- RFC 5306 - Restart Signaling for IS-IS
- RFC 5307 - IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)
- RFC 5308 - Routing IPv6 with IS-IS
- RFC 5309 - Point-to-Point Operation over LAN in Link State Routing Protocols
- RFC 5310 - IS-IS Generic Cryptographic Authentication
- RFC 5311 - Simplified Extension of Link State PDU (LSP) Space for IS-IS
- RFC 5316 - ISIS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering
- RFC 5317 - Joint Working Team (JWT) Report on MPLS Architectural Considerations for a Transport Profile
- RFC 5318 - The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header)
- RFC 5320 - The Subnetwork Encapsulation and Adaptation Layer (SEAL)
- RFC 5321 - Simple Mail Transfer Protocol
- RFC 5322 - Internet Message Format
- RFC 5323 - Web Distributed Authoring and Versioning (WebDAV) SEARCH
- RFC 5324 - MIB for Fibre-Channel Security Protocols (FC-SP)
- RFC 5325 - Licklider Transmission Protocol - Motivation
- RFC 5326 - Licklider Transmission Protocol - Specification
- RFC 5327 - Licklider Transmission Protocol - Security Extensions
- RFC 5328 - A Uniform Resource Name (URN) Namespace for the Digital Video Broadcasting Project (DVB)
- RFC 5329 - Traffic Engineering Extensions to OSPF Version 3
- RFC 5330 - A Link-Type sub-TLV to Convey the Number of Traffic Engineering Label Switched Paths Signalled with Zero Reserved Bandwidth across a Link
- RFC 5331 - MPLS Upstream Label Assignment and Context-Specific Label Space
- RFC 5332 - MPLS Multicast Encapsulations
- RFC 5333 - IANA Registration of Enumservices for Internet Calendaring
- RFC 5334 - Ogg Media Types
- RFC 5335 - Internationalized Email Headers
- RFC 5336 - SMTP Extension for Internationalized Email Addresses
- RFC 5337 - Internationalized Delivery Status and Disposition Notifications
- RFC 5338 - Using the Host Identity Protocol with Legacy Applications
- RFC 5339 - Evaluation of Existing GMPLS Protocols against Multi-Layer and Multi-Region Networks (MLN/MRN)
- RFC 5340 - OSPF for IPv6
- RFC 5341 - The Internet Assigned Number Authority (IANA) tel Uniform Resource Identifier (URI) Parameter Registry
- RFC 5342 - IANA Considerations and IETF Protocol Usage for IEEE 802 Parameters
- RFC 5343 - Simple Network Management Protocol (SNMP) Context EngineID Discovery
- RFC 5344 - Presence and Instant Messaging Peering Use Cases
- RFC 5345 - Simple Network Management Protocol (SNMP) Traffic Measurements and Trace Exchange Formats
- RFC 5346 - Operational Requirements for ENUM-Based Softswitch Use
- RFC 5347 - Media Gateway Control Protocol Fax Package
- RFC 5348 - TCP Friendly Rate Control (TFRC): Protocol Specification
- RFC 5349 - Elliptic Curve Cryptography (ECC) Support for Public Key Cryptography for Initial Authentication in Kerberos (PKINIT)
- RFC 5350 - IANA Considerations for the IPv4 and IPv6 Router Alert Options
- RFC 5351 - An Overview of Reliable Server Pooling Protocols
- RFC 5352 - Aggregate Server Access Protocol (ASAP)
- RFC 5353 - Endpoint Handlespace Redundancy Protocol (ENRP)
- RFC 5354 - Aggregate Server Access Protocol (ASAP) and Endpoint Handlespace Redundancy Protocol (ENRP) Parameters
- RFC 5355 - Threats Introduced by Reliable Server Pooling (RSerPool) and Requirements for Security in Response to Threats
- RFC 5356 - Reliable Server Pooling Policies
- RFC 5357 - A Two-Way Active Measurement Protocol (TWAMP)
- RFC 5358 - Preventing Use of Recursive Nameservers in Reflector Attacks
- RFC 5359 - Session Initiation Protocol Service Examples
- RFC 5360 - A Framework for Consent-Based Communications in the Session Initiation Protocol (SIP)
- RFC 5361 - A Document Format for Requesting Consent
- RFC 5362 - The Session Initiation Protocol (SIP) Pending Additions Event Package
- RFC 5363 - Framework and Security Considerations for Session Initiation Protocol (SIP) URI-List Services
- RFC 5364 - Extensible Markup Language (XML) Format Extension for Representing Copy Control Attributes in Resource Lists
- RFC 5365 - Multiple-Recipient MESSAGE Requests in the Session Initiation Protocol (SIP)
- RFC 5366 - Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP)
- RFC 5367 - Subscriptions to Request-Contained Resource Lists in the Session Initiation Protocol (SIP)
- RFC 5368 - Referring to Multiple Resources in the Session Initiation Protocol (SIP)
- RFC 5369 - Framework for Transcoding with the Session Initiation Protocol (SIP)
- RFC 5370 - The Session Initiation Protocol (SIP) Conference Bridge Transcoding Model
- RFC 5371 - RTP Payload Format for JPEG 2000 Video Streams
- RFC 5372 - Payload Format for JPEG 2000 Video: Extensions for Scalability and Main Header Recovery
- RFC 5373 - Requesting Answering Modes for the Session Initiation Protocol (SIP)
- RFC 5374 - Multicast Extensions to the Security Architecture for the Internet Protocol
- RFC 5375 - IPv6 Unicast Address Assignment Considerations
- RFC 5376 - Inter-AS Requirements for the Path Computation Element Communication Protocol (PCECP)
- RFC 5377 - Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF Documents
- RFC 5378 - Rights Contributors Provide to the IETF Trust
- RFC 5379 - Guidelines for Using the Privacy Mechanism for SIP
- RFC 5380 - Hierarchical Mobile IPv6 (HMIPv6) Mobility Management
- RFC 5381 - Experience of Implementing NETCONF over SOAP
- RFC 5382 - NAT Behavioral Requirements for TCP
- RFC 5383 - Deployment Considerations for Lemonade-Compliant Mobile Email
- RFC 5384 - The Protocol Independent Multicast (PIM) Join Attribute Format
- RFC 5385 - Version 2.0 Microsoft Word Template for Creating Internet Drafts and RFCs
- RFC 5386 - Better-Than-Nothing Security: An Unauthenticated Mode of IPsec
- RFC 5387 - Problem and Applicability Statement for Better-Than-Nothing Security (BTNS)
- RFC 5388 - Information Model and XML Data Model for Traceroute Measurements
- RFC 5389 - Session Traversal Utilities for NAT (STUN)
- RFC 5390 - Requirements for Management of Overload in the Session Initiation Protocol
- RFC 5391 - RTP Payload Format for ITU-T Recommendation G.711.1
- RFC 5392 - OSPF Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering
- RFC 5393 - Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking Proxies
- RFC 5394 - Policy-Enabled Path Computation Framework
- RFC 5395 - Domain Name System (DNS) IANA Considerations
- RFC 5396 - Textual Representation of Autonomous System (AS) Numbers
- RFC 5397 - WebDAV Current Principal Extension
- RFC 5398 - Autonomous System (AS) Number Reservation for Documentation Use
|
[ FAQS.ORG Home | RFC Index | Search | What's New | Help ]
