This is a partial list of RFCs (request for comments memoranda). A Request for Comments (RFC) is a publication in a series from the principal technical development and standards-setting bodies for the Internet, most prominently the Internet Engineering Task Force (IETF).
While there are over 9,151 RFCs as of February 2022, this list consists of RFCs that have related articles. A complete list is available from the IETF website. [1]
# | Title | Date published | Related article | Made obsolete by | Notes |
---|---|---|---|---|---|
RFC 20 | ASCII format for Network Interchange | October 16, 1969 | ASCII | ||
RFC 42 | Message Data Types | 31 March 1970 | |||
RFC 768 | User Datagram Protocol | August 28, 1980 | UDP | ||
RFC 783 | THE TFTP PROTOCOL (REVISION 2) | June 1981 | TFTP | RFC 1350 | |
RFC 791 | Internet Protocol | September 1981 | IPv4 | ||
RFC 792 | INTERNET CONTROL MESSAGE PROTOCOL | September 1981 | ICMP | ||
RFC 793 | TRANSMISSION CONTROL PROTOCOL | September 1981 | TCP | RFC 9293 | |
RFC 826 | An Ethernet Address Resolution Protocol | November 1982 | ARP | ||
RFC 854 | TELNET PROTOCOL SPECIFICATION | May 1983 | Telnet | ||
RFC 855 | TELNET OPTION SPECIFICATIONS | May 1983 | |||
RFC 862 | Echo Protocol | May 1983 | Echo | ||
RFC 863 | Discard Protocol | May 1983 | DISCARD | ||
RFC 864 | Character Generator Protocol | May 1983 | CHARGEN | ||
RFC 868 | Time Protocol | May 1983 | TIME | ||
RFC 903 | A Reverse Address Resolution Protocol | June 1984 | RARP | ||
RFC 937 | POST OFFICE PROTOCOL - VERSION 2 | February 1985 | POP v 2 | ||
RFC 951 | BOOTSTRAP PROTOCOL (BOOTP) | September 1985 | BOOTP | ||
RFC 959 | FILE TRANSFER PROTOCOL (FTP) | October 1985 | FTP | ||
RFC 1034 | DOMAIN NAMES - CONCEPTS AND FACILITIES | November 1987 | DNS | ||
RFC 1035 | DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION | November 1987 | DNS | ||
RFC 1036 | Standard for Interchange of USENET Messages | December 1987 | Usenet | ||
RFC 1055 | A Non-Standard for Transmission of IP Datagrams Over Serial Lines: SLIP | June 1988 | SLIP | ||
RFC 1058 | Routing Information Protocol | June 1988 | RIP v 1 | ||
RFC 1059 | Network Time Protocol (version 1) specification and implementation | July 1988 | NTP v 1 | ||
RFC 1087 | Ethics and the Internet | January 1989 | Internet Ethics | ||
RFC 1118 | The Hitchhikers Guide to the Internet | September 1989 | The Hitchhikers Guide to the Internet | ||
RFC 1119 | Network Time Protocol (version 2) specification and implementation | September 1989 | NTP v 2 | ||
RFC 1149 | A Standard for the Transmission of IP Datagrams on Avian Carriers | April 1, 1990 | IP over Avian Carriers | ||
RFC 1157 | A Simple Network Management Protocol (SNMP) | May 1990 | SNMP v1 | ||
RFC 1176 | INTERACTIVE MAIL ACCESS PROTOCOL - VERSION 2 | August 1990 | IMAP v 2 | ||
RFC 1191 | Path MTU Discovery | November 1990 | PMTUD | Obsoletes RFC 1063 | |
RFC 1305 | Network Time Protocol (Version 3) Specification, Implementation and Analysis | March 1992 | NTP v 3 | RFC 5905 | Obsoletes RFC 1119, RFC 1059, RFC 958 |
RFC 1321 | The MD5 Message-Digest Algorithm | April 1992 | MD5 | ||
RFC 1350 | THE TFTP PROTOCOL (REVISION 2) | July 1992 | TFTP | Obsoletes RFC 783 | |
RFC 1436 | The Internet Gopher Protocol | March 1993 | Gopher | ||
RFC 1441 | Introduction to version 2 of the Internet-standard Network Management Framework | April 1993 | SNMP v 2 | ||
RFC 1459 | Internet Relay Chat Protocol | May 1993 | IRC | ||
RFC 1730 | INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4 | December 1994 | IMAP v 4 | ||
RFC 1777 | Lightweight Directory Access Protocol | March 1995 | LDAP | ||
RFC 1855 | Netiquette Guidelines | October 1995 | Netiquette | ||
RFC 1918 | Address Allocation for Private Internets | February 1996 | Private network | ||
RFC 1928 | SOCKS Protocol Version 5 | March 1996 | SOCKS5 | ||
RFC 1939 | Post Office Protocol - Version 3 | May 1996 | POP v 3 | ||
RFC 1945 | Hypertext Transfer Protocol—HTTP/1.0 | May 1996 | HTTP v 1.0 | ||
RFC 1948 | Defending Against Sequence Number Attacks | May 1996 | IP spoofing | ||
RFC 1950 | ZLIB Compressed Data Format Specification version 3.3 | May 1996 | Zlib v 3.3 | ||
RFC 1951 | DEFLATE Compressed Data Format Specification version 1.3 | May 1996 | DEFLATE v 1.3 | ||
RFC 1952 | GZIP file format specification version 4.3 | May 1996 | Gzip v 4.3 | ||
RFC 1964 | The Kerberos Version 5 GSS-API Mechanism | June 1996 | Kerberos; GSSAPI | ||
RFC 2080 | RIPng for IPv6 | January 1997 | RIP v ng | ||
RFC 2119 | Key words for use in RFCs to Indicate Requirement Levels | March 1997 | Request for Comments | Updated by RFC 8174 | |
RFC 2131 | Dynamic Host Configuration Protocol | March 1997 | DHCP | ||
RFC 2177 | IMAP4 IDLE command | June 1997 | IMAP IDLE | ||
RFC 2195 | IMAP/POP AUTHorize Extension for Simple Challenge/Response | September 1997 | CRAM-MD5 | ||
RFC 2228 | FTP Security Extensions | October 1997 | FTP | ||
RFC 2230 | Key Exchange Delegation Record for the DNS | November 1997 | Secure DNS | ||
RFC 2246 | The TLS Protocol Version 1.0 | January 1999 | TLS 1.0 | ||
RFC 2251 | Lightweight Directory Access Protocol (v3) | December 1997 | LDAP v 3 | ||
RFC 2252 | Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions | ||||
RFC 2253 | Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names | ||||
RFC 2254 | The String Representation of LDAP Search Filters | ||||
RFC 2255 | The LDAP URL Format | ||||
RFC 2256 | A Summary of the X.500(96) User Schema for use with LDAPv3 | ||||
RFC 2326 | Real Time Streaming Protocol (RTSP) | April 1998 | RTSP | ||
RFC 2327 | SDP: Session Description Protocol | April 1998 | SDP | ||
RFC 2328 | OSPF Version 2 | April 1998 | OSPF | ||
RFC 2351 | Mapping of Airline Reservation, Ticketing, and Messaging Traffic over IP | May 1998 | MATIP | ||
RFC 2362 | Protocol Independent Multicast-Sparse Mode (PIM-SM) | June 1998 | PIM | ||
RFC 2397 | The "data" URL scheme | August 1998 | Data: URI scheme | ||
RFC 2407 | Internet IP Security Domain of Interpretation for ISAKMP. | November 1998 | IKE | ||
RFC 2408 | Internet Security Association and Key Management Protocol (ISAKMP) | ||||
RFC 2409 | The Internet Key Exchange (IKE) | ||||
RFC 2427 | Multiprotocol Interconnect over Frame Relay | September 1998 | Frame Relay | 1294, 1490 | |
RFC 2453 | RIP Version 2 | November 1998 | RIP v 2 | ||
RFC 2460 | Internet Protocol, Version 6 (IPv6) Specification | December 1998 | IPv6 | RFC 8200 | |
RFC 2549 | IP over Avian Carriers with Quality of Service | April 1, 1999 | IP over Avian Carriers | ||
RFC 2555 | 30 Years of RFCs | April 7, 1999 | Retraces the history of RFCs | ||
RFC 2570 | Introduction to Version 3 of the Internet-standard Network Management Framework | April 1999 | SNMP v3 | ||
RFC 2595 | Using TLS with IMAP, POP3 and ACAP | June 1999 | STARTTLS for IMAP, POP3 and ACAP | ||
RFC 2606 | Reserved Top Level DNS Names | June 1999 | Fictitious domain name | example.com, .test, ... | |
RFC 2740 | OSPF for IPv6 | December 1999 | OSPF | ||
RFC 2743 | Generic Security Service Application Program Interface Version 2, Update 1 | January 2000 | GSSAPI v 2 | ||
RFC 2744 | Generic Security Service API Version 2 : C-bindings | ||||
RFC 2801 | Internet Open Trading Protocol - IOTP Version 1.0 | April 2000 | Internet Open Trading Protocol | ||
RFC 2802 | Digital Signatures for the v1.0 Internet Open Trading Protocol (IOTP) | April 2000 | Internet Open Trading Protocol | ||
RFC 2810 | Internet Relay Chat: Architecture | April 2000 | IRC | ||
RFC 2811 | Internet Relay Chat: Channel Management | ||||
RFC 2812 | Internet Relay Chat: Client Protocol | ||||
RFC 2813 | Internet Relay Chat: Server Protocol | ||||
RFC 2853 | Generic Security Service API Version 2 : Java Bindings | June 2000 | GSSAPI v 2 | ||
RFC 2865 | Remote Authentication Dial In User Service (RADIUS) | June 2000 | RADIUS | ||
RFC 2866 | RADIUS Accounting | June 2000 | |||
RFC 2935 | Internet Open Trading Protocol (IOTP) HTTP Supplement | September 2000 | Internet Open Trading Protocol | ||
RFC 2974 | Session Announcement Protocol | October 2000 | SAP | ||
RFC 3504 | Internet Open Trading Protocol (IOTP), Version 1, Errata | March 2003 | Internet Open Trading Protocol | ||
RFC 3022 | Traditional IP Network Address Translator (Traditional NAT) | January 2001 | NAT | ||
RFC 3031 | Multiprotocol Label Switching Architecture | January 2001 | MPLS | ||
RFC 3053 | IPv6 Tunnel Broker | January 2001 | Tunnel Broker | ||
RFC 3056 | Connection of IPv6 Domains via IPv4 Clouds | February 2001 | 6to4 | ||
RFC 3080 | The Blocks Extensible Exchange Protocol Core | March 2001 | BEEP | ||
RFC 3162 | RADIUS and IPv6 | August 2001 | RADIUS (IPv6) | ||
RFC 3207 | SMTP Service Extension for Secure SMTP over Transport Layer Security | February 2002 | STARTTLS for SMTP | ||
RFC 3261 | SIP: Session Initiation Protocol | June 2002 | SIP | ||
RFC 3284 | The VCDIFF Generic Differencing and Compression Data Format | June 2002 | VCDIFF | ||
RFC 3286 | An Introduction to the Stream Control Transmission Protocol (SCTP) | May 2002 | SCTP | ||
RFC 3315 | Dynamic Host Configuration Protocol for IPv6 (DHCPv6) | July 2003 | DHCP (IPv6) | ||
RFC 3339 | Date and Time on the Internet: Timestamps | July 2002 | Timestamp | ||
RFC 3376 | Internet Group Management Protocol, Version 3 | October 2002 | IGMP v 3 | ||
RFC 3401 | Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS | October 2002 | DDDS | ||
RFC 3402 | Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm | ||||
RFC 3403 | Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database | ||||
RFC 3404 | Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI) Resolution Application | ||||
RFC 3405 | Dynamic Delegation Discovery System (DDDS) Part Five: URI.ARPA Assignment Procedures | ||||
RFC 3492 | Punycode: A Bootstring encoding of Unicode for Internationalized Domain Names in Applications (IDNA) | March 2003 | Punycode | ||
RFC 3501 | INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1 | March 2003 | IMAP v 4r1 | ||
RFC 3530 | Network File System (NFS) version 4 Protocol | April 2003 | NFS v 4 | ||
RFC 3538 | Secure Electronic Transaction (SET) Supplement for the v1.0 Internet Open Trading Protocol (IOTP) | June 2003 | Internet Open Trading Protocol | ||
RFC 3550 | RTP: A Transport Protocol for Real-Time Applications | July 2003 | RTP | ||
RFC 3711 | The Secure Real-time Transport Protocol (SRTP) | March 2004 | SRTP | ||
RFC 3720 | Internet Small Computer Systems Interface (iSCSI) | April 2004 | ISCSI | ||
RFC 3730 | Extensible Provisioning Protocol (EPP) | March 2004 | Extensible Provisioning Protocol | ||
RFC 3783 | Small Computer Systems Interface (SCSI) Command Ordering Considerations with iSCSI | May 2004 | ISCSI | ||
RFC 3801 | Voice Profile for Internet Protocol | June 2004 | VPIM | ||
RFC 3830 | MIKEY: Multimedia Internet KEYing | August 2004 | MIKEY | ||
RFC 3867 | Payment Application Programmers Interface (API) for v1.0 | November 2004 | Internet Open Trading Protocol | ||
RFC 3977 | Network News Transfer Protocol | October 2006 | NNTP | ||
RFC 4121 | The Kerberos Version 5 - Generic Security Service Application Program Interface (GSS-API) | July 2005 | Kerberos | ||
RFC 4122 | A Universally Unique IDentifier (UUID) URN Namespace | July 2005 | UUID | ||
RFC 4151 | The 'tag' URI Scheme | October 2005 | Tag URI scheme | ||
RFC 4213 | Basic Transition Mechanisms for IPv6 Hosts and Routers | October 2005 | 6in4 | ||
RFC 4217 | Securing FTP with TLS | October 2005 | SSL FTP (FTPS) | ||
RFC 4271 | Border Gateway Protocol 4 | January 2006 | Border Gateway Protocol | ||
RFC 4287 | The Atom Syndication Format | December 2005 | Atom | ||
RFC 4251 | The Secure Shell (SSH) Protocol Architecture | January 2006 | SSH-2 | ||
RFC 4291 | IP Version 6 Addressing Architecture | February 2006 | IPv6 | ||
RFC 4353 | A Framework for Conferencing with the Session Initiation Protocol (SIP) | February 2006 | Conference call | ||
RFC 4408 | Sender Policy Framework (SPF) for Authorizing Use of Domains in E-Mail, Version 1 | January 2006 | SPF | ||
RFC 4422 | Simple Authentication and Security Layer (SASL) | June 2006 | SASL | ||
RFC 4541 | Considerations for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping Switches | May 2006 | IGMP snooping | ||
RFC 4575 | A Session Initiation Protocol (SIP) Event Package for Conference State | August 2006 | Conference call | ||
RFC 4579 | Session Initiation Protocol (SIP) Call Control - Conferencing for User Agents | August 2006 | |||
RFC 4634 | US Secure Hash Algorithms (SHA and HMAC-SHA) | July 2006 | SHA-1, SHA-2 | ||
RFC 4655 | A Path Computation Element (PCE)-Based Architecture | August 2008 | Path computation element | ||
RFC 4787 | Network Address Translation (NAT) Behavioral Requirements for Unicast UDP | January 2007 | NAT | ||
RFC 4960 | Stream Control Transmission Protocol | September 2007 | SCTP | ||
RFC 5023 | The Atom Publishing Protocol | October 2007 | Atom | ||
RFC 5228 | Sieve: An Email Filtering Language | January 2008 | Sieve | Obsoletes RFC 3028 | |
RFC 5321 | Simple Mail Transfer Protocol | October 2008 | SMTP, Internet Message Format | ||
RFC 5322 | Internet Message Format | October 2008 | |||
RFC 5533 | Shim6: Level 3 Multihoming Shim Protocol for IPv6 | June 2009 | Site Multihoming by IPv6 Intermediation | ||
RFC 5545 | iCalendar Specification | September 2009 | iCalendar | ||
RFC 5646 | Tags for Identifying Languages | September 2009 | language tags | ||
RFC 5849 | The OAuth 1.0 Protocol | April 2010 | OAuth | ||
RFC 5880 | Bidirectional Forwarding Detection | June 2010 | BFD | ||
RFC 5881 | BFD for IPv4 and IPv6 (Single Hop) | June 2010 | BFD | ||
RFC 5905 | Network Time Protocol Version 4: Protocol and Algorithms Specification | June 2010 | NTP v 4 | Obsoletes RFC 1305, RFC 4330 | |
RFC 5969 | IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) | January 2010 | IPv6 rapid deployment | ||
RFC 6238 | TOTP: Time-Based One-Time Password Algorithm | May 2011 | TOTP | ||
RFC 6265 | HTTP State Management Mechanism | April 2011 | HTTP cookie | ||
RFC 6409 | Message submission for mail | November 2011 | message submission agent | replaces 2476, 4409 | |
RFC 6455 | The WebSocket Protocol | December 2011 | WebSocket | ||
RFC 6508 | Sakai-Kasahara Key Encryption (SAKKE) | February 2012 | SAKKE | ||
RFC 6716 | Definition of the Opus Audio Codec | September 2012 | Opus (audio format) | Updated by RFC 8251 | |
RFC 6726 | File Delivery over Unidirectional Transport (FLUTE) | November 2012 | FLUTE | Obsoletes RFC 3926 | |
RFC 6749 | The OAuth 2.0 Authorization Framework | October 2012 | OAuth | ||
RFC 6797 | HTTP Strict Transport Security (HSTS) | November 2012 | HTTP Strict Transport Security | ||
RFC 6805 | The Application of the Path Computation Element Architecture to the Determination of a Sequence of Domains in MPLS and GMPLS | November 2012 | Path computation element | ||
RFC 7230 | Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing | June 2014 | HTTP v1.1 | Obsoletes 2616 | |
RFC 7231 | Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content | June 2014 | HTTP v1.1 | Obsoletes 2616 | |
RFC 7232 | Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests | June 2014 | HTTP v1.1 | Obsoletes 2616 | |
RFC 7233 | Hypertext Transfer Protocol (HTTP/1.1): Range Requests | June 2014 | HTTP v1.1, Byte serving | Obsoletes 2616 | |
RFC 7234 | Hypertext Transfer Protocol (HTTP/1.1): Caching | June 2014 | HTTP v1.1 | Obsoletes 2616 | |
RFC 7235 | Hypertext Transfer Protocol (HTTP/1.1): Authentication | June 2014 | HTTP v1.1 | Obsoletes 2616 | |
RFC 7252 | Constrained Application Protocol (CoAP) | June 2014 | Constrained Application Protocol | ||
RFC 7301 | Transport Layer Security (TLS): Application-Layer Protocol Negotiation Extension | July 2014 | Application-Layer Protocol Negotiation | ||
RFC 7348 | Virtual eXtensible Local Area Network (VXLAN): A Framework for Overlaying Virtualized Layer 2 Networks over Layer 3 Networks | August 2014 | VXLAN | ||
RFC 7469 | Public Key Pinning Extension for HTTP | April 2015 | HTTP Public Key Pinning | ||
RFC 7540 | Hypertext Transfer Protocol Version 2 (HTTP/2) | May 2015 | HTTP/2 | ||
RFC 7541 | HPACK: Header Compression for HTTP/2 | May 2015 | |||
RFC 7567 | IETF Recommendations Regarding Active Queue Management | July 2015 | Active Queue Management | ||
RFC 7725 | An HTTP Status Code to Report Legal Obstacles | December 2015 | HTTP 451 | ||
RFC 7871 | Client Subnet in DNS Queries | May 2016 | Domain Name System | ||
RFC 8391 | XMSS: eXtended Merkle Signature Scheme | May 2018 | Hash-based cryptography | ||
RFC 8392 | CBOR Web Token (CWT) | May 2018 | |||
RFC 9000 | QUIC: A UDP-Based Multiplexed and Secure Transport | May 2021 | QUIC | ||
RFC 9293 | Transmission Control Protocol (TCP) | August 2022 | TCP | Obsoletes RFC 793 | |
RFC 9338 | CBOR Object Signing and Encryption (COSE): Countersignatures | December 2022 | COSE | Updates RFC 9052 | |
RFC 9580 | OpenPGP | July 2024 | OpenPGP | Obsoletes RFC 4880, RFC 5581, RFC 6637 |
Obsolete RFCs are indicated with struck-through text.
In computer network engineering, an Internet Standard is a normative specification of a technology or methodology applicable to the Internet. Internet Standards are created and published by the Internet Engineering Task Force (IETF). They allow interoperation of hardware and software from different sources which allows internets to function. As the Internet became global, Internet Standards became the lingua franca of worldwide communications.
The Internet Engineering Task Force (IETF) is a standards organization for the Internet and is responsible for the technical standards that make up the Internet protocol suite (TCP/IP). It has no formal membership roster or requirements and all its participants are volunteers. Their work is usually funded by employers or other sponsors.
A Request for Comments (RFC) is a publication in a series from the principal technical development and standards-setting bodies for the Internet, most prominently the Internet Engineering Task Force (IETF). An RFC is authored by individuals or groups of engineers and computer scientists in the form of a memorandum describing methods, behaviors, research, or innovations applicable to the working of the Internet and Internet-connected systems. It is submitted either for peer review or to convey new concepts, information, or, occasionally, engineering humor.
A Uniform Resource Identifier (URI), formerly Universal Resource Identifier, is a unique sequence of characters that identifies an abstract or physical resource, such as resources on a webpage, mail address, phone number, books, real-world objects such as people and places, concepts. URIs are used to identify anything described using the Resource Description Framework (RDF), for example, concepts that are part of an ontology defined using the Web Ontology Language (OWL), and people who are described using the Friend of a Friend vocabulary would each have an individual URI.
Simple Network Management Protocol (SNMP) is an Internet Standard protocol for collecting and organizing information about managed devices on IP networks and for modifying that information to change device behavior. Devices that typically support SNMP include cable modems, routers, network switches, servers, workstations, printers, and more.
The Internet Architecture Board (IAB) is a committee of the Internet Engineering Task Force (IETF) and an advisory body of the Internet Society (ISOC). Its responsibilities include architectural oversight of IETF activities, Internet Standards Process oversight and appeal, and the appointment of the Request for Comments (RFC) Editor. The IAB is also responsible for the management of the IETF protocol parameter registries.
In computing, Internet Key Exchange is the protocol used to set up a security association (SA) in the IPsec protocol suite. IKE builds upon the Oakley protocol and ISAKMP. IKE uses X.509 certificates for authentication ‒ either pre-shared or distributed using DNS ‒ and a Diffie–Hellman key exchange to set up a shared session secret from which cryptographic keys are derived. In addition, a security policy for every peer which will connect must be manually maintained.
An email address identifies an email box to which messages are delivered. While early messaging systems used a variety of formats for addressing, today, email addresses follow a set of specific rules originally standardized by the Internet Engineering Task Force (IETF) in the 1980s, and updated by RFC 5322 and 6854. The term email address in this article refers to just the addr-spec in Section 3.4 of RFC 5322. The RFC defines address more broadly as either a mailbox or group. A mailbox value can be either a name-addr, which contains a display-name and addr-spec, or the more common addr-spec alone.
A Uniform Resource Name (URN) is a Uniform Resource Identifier (URI) that uses the urn
scheme. URNs are globally unique persistent identifiers assigned within defined namespaces so they will be available for a long period of time, even after the resource which they identify ceases to exist or becomes unavailable. URNs cannot be used to directly locate an item and need not be resolvable, as they are simply templates that another parser may use to find an item.
An Internet Draft (I-D) is a document published by the Internet Engineering Task Force (IETF) containing preliminary technical specifications, results of networking-related research, or other technical information. Often, Internet Drafts are intended to be work-in-progress documents for work that is eventually to be published as a Request for Comments (RFC) and potentially leading to an Internet Standard.
Robert Braden was an American computer scientist who played a role in the development of the Internet. His research interests included end-to-end network protocols, especially in the transport and network layers.
In the Internet addressing architecture, the Internet Engineering Task Force (IETF) and the Internet Assigned Numbers Authority (IANA) have reserved various Internet Protocol (IP) addresses for special purposes.
In information and communications technology, a media type, content type or MIME type is a two-part identifier for file formats and content formats. Their purpose is comparable to filename extensions and uniform type identifiers, in that they identify the intended data format. They are mainly used by technologies underpinning the Internet, and also used on Linux desktop systems.
Brian Edward Carpenter is a British Internet engineer and a former chair of the Internet Engineering Task Force (IETF), the Internet Architecture Board (IAB), and the Internet Society.
A best current practice, abbreviated as BCP, is a de facto level of performance in engineering and information technology. It is more flexible than a standard, since techniques and tools are continually evolving. The Internet Engineering Task Force publishes Best Current Practice documents in a numbered document series. Each document in this series is paired with the currently valid Request for Comments (RFC) document. BCP was introduced in RFC-1818.
An IPv6 transition mechanism is a technology that facilitates the transitioning of the Internet from the Internet Protocol version 4 (IPv4) infrastructure in use since 1983 to the successor addressing and routing system of Internet Protocol Version 6 (IPv6). As IPv4 and IPv6 networks are not directly interoperable, transition technologies are designed to permit hosts on either network type to communicate with any other host.
Mark James Handley is Professor of Networked Systems in the Department of Computer Science of University College London since 2003, where he leads the Networks Research Group.
An Internet Protocol version 6 address is a numeric label that is used to identify and locate a network interface of a computer or a network node participating in a computer network using IPv6. IP addresses are included in the packet header to indicate the source and the destination of each packet. The IP address of the destination is used to make decisions about routing IP packets to other networks.
A uniform resource locator (URL), colloquially known as an address on the Web, is a reference to a resource that specifies its location on a computer network and a mechanism for retrieving it. A URL is a specific type of Uniform Resource Identifier (URI), although many people use the two terms interchangeably. URLs occur most commonly to reference web pages (HTTP/HTTPS) but are also used for file transfer (FTP), email (mailto), database access (JDBC), and many other applications.