The Subnetwork Encapsulation and Adaptation Layer (SEAL)
Metadata
- Publisher
- IETF
- Doc Type
- Experimental
- Pages
- 29
- Abstract
- For the purpose of this document, subnetworks are defined as virtual topologies that span connected network regions bounded by encapsulating border nodes. These virtual topologies may span multiple IP and/or sub-IP layer forwarding hops, and can introduce failure modes due to packet duplication and/or links with diverse Maximum Transmission Units (MTUs). This document specifies a Subnetwork Encapsulation and Adaptation Layer (SEAL) that accommodates such virtual topologies over diverse underlying link technologies. This document defines an Experimental Protocol for the Internet community.
- Publication Date
- 2010-02-01
- Status Note
- Experimental
- DOI
10.17487/RFC5320- Link
- https://doi.org/10.17487/RFC5320
- Author(s)
- Fred Templin
- Keyword(s)
- Virtual Topologies, MTU
Latest version of IETF RFC 5320
Document Versions — IETF RFC 5320
-
▶ IETF RFC 5320 (2010-02-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 791 [Active*]
- IETF RFC 792 [Active*]
- IETF RFC 2119 [Active*]
- IETF RFC 2460 [Superseded*]
Bibliographic Reference(s)
- "Archive/Hypermail of Early TCp-IP Mail List", http://www-mice.cs.ucl.ac.uk/multimedia/misc/tcp_ip/ , May 1987 - May 1990. EXTERNAL
- C, C., D, D., and k. k, "Beyond Folklore: Observations on Fragmented Traffic", December 2002. EXTERNAL
- "IETF MTU Discovery Working Group mailing list, gatekeeper.dec.com/pub/DEC/WRL/mogul/mtudwg-log, November 1989 - February 1995.". EXTERNAL
- Kent, C. and J. Mogul, "Fragmentation Considered Harmful", October 1987. EXTERNAL
- IETF RFC 1063 [Superseded*]
- IETF RFC 1191 [Active*]
- IETF RFC 1981 [Superseded*]
- IETF RFC 2003 [Active*]
- IETF RFC 2004 [Active*]
- IETF RFC 2764 [Active*]
- IETF RFC 2923 [Active*]
- IETF RFC 3692 [Active*]
- IETF RFC 3819 [Active*]
- IETF RFC 4213 [Active*]
- IETF RFC 4301 [Active, Amended*]
- IETF RFC 4380 [Active*]
- IETF RFC 4459 [Active*]
- IETF RFC 4727 [Active*]
- IETF RFC 4821 [Active*]
- IETF RFC 4963 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5320.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 5320, The Subnetwork Encapsulation and Adaptation Layer (SEAL). Available at https://doi.org/10.17487/RFC5320
Snippet:
IETF RFC 5320, The Subnetwork Encapsulation and Adaptation Layer (SEAL). Available at https://doi.org/10.17487/RFC5320
HTML (ISO 690 compliant)
Preview:
IETF RFC 5320, The Subnetwork Encapsulation and Adaptation Layer (SEAL). Available at https://doi.org/10.17487/RFC5320
Snippet:
<span class="citation"><cite>IETF RFC 5320</cite>, The Subnetwork Encapsulation and Adaptation Layer (SEAL). Available at <a href="https://doi.org/10.17487/RFC5320" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5320</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 5320, The Subnetwork Encapsulation and Adaptation Layer (SEAL)
doi: 10.17487/RFC5320
url: https://doi.org/10.17487/RFC5320
doi: 10.17487/RFC5320
url: https://doi.org/10.17487/RFC5320
Snippet:
<li> <cite id="bib-rfc5320">IETF RFC 5320</cite>, The Subnetwork Encapsulation and Adaptation Layer (SEAL) <span class="doi">10.17487/RFC5320</span> </li>
Referenced By
- IETF RFC 5558 [Active*]
- IETF RFC 5720 [Active*]
- IETF RFC 6333 [Active*]
- IETF RFC 6864 [Active*]