RFC 5300–5399
93 RFCs von RFC 5300 bis RFC 5399, nach Nummer sortiert.
- RFC 5301Dynamic Hostname Exchange Mechanism for IS-IS
- RFC 5302Domain-Wide Prefix Distribution with Two-Level IS-IS
- RFC 5303Three-Way Handshake for IS-IS Point-to-Point Adjacencies
- RFC 5304IS-IS Cryptographic Authentication
- RFC 5305IS-IS Extensions for Traffic Engineering
- RFC 5306Restart Signaling for IS-IS
- RFC 5307IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)
- RFC 5308Routing IPv6 with IS-IS
- RFC 5309Alcatel-Lucent
- RFC 5310IP Infusion
- RFC 5311Simplified Extension of Link State PDU (LSP) Space for IS-IS
- RFC 5316ISIS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering
- RFC 5317Acreo AB
- RFC 5318December 2008
- RFC 5320The Subnetwork Encapsulation and Adaptation Layer (SEAL)
- RFC 5321Einfaches Mail-Übertragungsprotokoll
- RFC 5322Internet Message Format
- RFC 5323Mitrix
- RFC 5324Cisco Systems
- RFC 5325ISTRAC, ISRO
- RFC 5326NASA/Jet Propulsion Laboratory
- RFC 5327ISTRAC, ISRO
- RFC 5328DVB Project
- RFC 5329Traffic Engineering Extensions to OSPF Version 3
- RFC 5330BT
- RFC 5331Juniper Networks
- RFC 5332MPLS Multicast Encapsulations
- RFC 5333Swisscom
- RFC 5334Ogg Media Types
- RFC 5335Internationalized Email Headers
- RFC 5336SMTP Extension for Internationalized Email Addresses
- RFC 5337Internationalized Delivery Status and Disposition Notifications
- RFC 5338Ericsson Research NomadicLab
- RFC 5339Alcatel-Lucent
- RFC 5340OSPF für IPv6
- RFC 5341The Internet Assigned Number Authority (IANA) tel Uniform Resource Identifier (URI) Parameter Registry
- RFC 5342BCP: 141 September 2008
- RFC 5343Simple Network Management Protocol (SNMP) Context EngineID Discovery
- RFC 5344Presence and Instant Messaging Peering Use Cases
- RFC 5345Simple Network Management Protocol (SNMP)
- RFC 5346NIDA
- RFC 5347CableLabs
- RFC 5348TCP Friendly Rate Control (TFRC): Protocol Specification
- RFC 5349Microsoft Corporation
- RFC 5350IANA Considerations for the IPv4 and IPv6 Router Alert Options
- RFC 5351Ciena Corporation
- RFC 5352Aggregate Server Access Protocol (ASAP)
- RFC 5353Endpoint Handlespace Redundancy Protocol (ENRP)
- RFC 5354Aggregate Server Access Protocol (ASAP) and Endpoint Handlespace Redundancy Protocol (ENRP) Parameters
- RFC 5355Nokia Siemens Networks
- RFC 5356Muenster Univ. of Applied Sciences
- RFC 5357Verizon
- RFC 5358BCP: 140 F. Neves
- RFC 5359BCP: 144 R. Sparks
- RFC 5360Ericsson
- RFC 5361A Document Format for Requesting Consent
- RFC 5362The Session Initiation Protocol (SIP) Pending Additions Event Package
- RFC 5363Tekelec
- RFC 5364October 2008
- RFC 5365October 2008
- RFC 5366Avaya
- RFC 5367Subscriptions to Request-Contained Resource Lists in the Session Initiation Protocol (SIP)
- RFC 5368Referring to Multiple Resources in the Session Initiation Protocol (SIP)
- RFC 5369Framework for Transcoding with the Session Initiation Protocol (SIP)
- RFC 5370The Session Initiation Protocol (SIP)
- RFC 5371Sony
- RFC 5372Sony
- RFC 5373Research in Motion (RIM)
- RFC 5374Multicast Extensions to the Security Architecture for the Internet Protocol
- RFC 5375IPv6 Unicast Address Assignment Considerations
- RFC 5376BT
- RFC 5377Advice to the Trustees of the IETF Trust
- RFC 5378BCP: 78 J. Contreras, Ed.
- RFC 5379Guidelines for Using the Privacy Mechanism for SIP
- RFC 5380Hierarchical Mobile IPv6 (HMIPv6) Mobility Management
- RFC 5381Experience of Implementing NETCONF over SOAP
- RFC 5382BCP: 142 K. Biswas
- RFC 5383BCP: 143 October 2008
- RFC 5384The Protocol Independent Multicast (PIM) Join Attribute Format
- RFC 5385Version 2.0 Microsoft Word Template for Creating Internet Drafts and RFCs
- RFC 5386SSW
- RFC 5387EMC
- RFC 5388Information Model and XML Data Model for Traceroute Measurements
- RFC 5389Sitzungsdurchquerungstools für NAT (STUN)
- RFC 5390Requirements for Management of Overload in the
- RFC 5391RTP Payload Format for ITU-T Recommendation G.711.1
- RFC 5392OSPF Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering
- RFC 5393Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking Proxies
- RFC 5394Alcatel
- RFC 5395BCP: 42 November 2008
- RFC 5396Textuelle Darstellung von Autonomous-System- (AS-)Nummern
- RFC 5397December 2008
- RFC 5398Autonomous System (AS) Number Reservation for Documentation Use