RFC 8507: Simple Internet Protocol (SIP) Specification
In plain English — editorial summary, not part of the RFC
This document is published for the historical record. The Simple Internet Protocol was the basis for one of the candidates for the IETF's Next Generation (IPng) work that became IPv6. The publication date of the original Internet-Draft was November 10, 1992. It is presented here substantially unchanged and is neither a complete document nor intended to be implementable. The paragraph that follows is the Abstract from the original draft. This document specifies a new version of IP called SIP, the Simple Internet Protocol. It also describes the changes needed to ICMP, IGMP, and transport protocols such as TCP and UDP, in order to work with SIP. A companion document [SIP-ADDR] describes the addressing and routing aspects of SIP, including issues of auto-configuration, host and subnet mobility, and multicast.
Document record
- Document ID
- RFC8507
- Published
- December 2018
- Authors
- S. Deering; R. Hinden
- Status
- HISTORIC
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 26
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8200Internet Protocol, Version 6 (IPv6) SpecificationUpdated
July 2017
- RFC 2460Internet Protocol, Version 6 (IPv6) SpecificationObsoleted
December 1998
- RFC 1752The Recommendation for the IP Next Generation ProtocolCurrent
January 1995
- RFC 8483Yeti DNS TestbedCurrent
October 2018
- RFC 7785Recommendations for Prefix Binding in the Context of Softwire Dual-Stack LiteCurrent
February 2016
- RFC 7021Assessing the Impact of Carrier-Grade NAT on Network ApplicationsCurrent
September 2013
- RFC 6964Operational Guidance for IPv6 Deployment in IPv4 Sites Using the Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)Current
May 2013
- RFC 6431Huawei Port Range Configuration Options for PPP IP Control Protocol (IPCP)Current
November 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?