RFC 5320: The Subnetwork Encapsulation and Adaptation Layer (SEAL)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC5320
- Published
- February 2010
- Authors
- F. Templin
- Status
- EXPERIMENTAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 29
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3988Maximum Transmission Unit Signalling Extensions for the Label Distribution ProtocolCurrent
February 2005
- RFC 7180Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and UpdatesObsoleted
May 2014
- RFC 7588A Widely Deployed Solution to the Generic Routing Encapsulation (GRE) Fragmentation ProblemCurrent
July 2015
- RFC 7780Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and UpdatesUpdated
February 2016
- RFC 1393Traceroute Using an IP OptionObsoleted
January 1993
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?