The Subnetwork Encapsulation and Adaptation Layer (SEAL)
draft-templin-intarea-seal-68
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Fred Templin | ||
Last updated | 2015-10-14 (Latest revision 2014-01-03) | ||
RFC stream | Independent Submission | ||
Intended RFC status | Experimental | ||
Formats | |||
Reviews | |||
Stream | ISE state | In ISE Review | |
Consensus boilerplate | Unknown | ||
Document shepherd | (None) | ||
IESG | IESG state | Expired (IESG: Dead) | |
Action Holders |
(None)
|
||
Telechat date | (None) | ||
Responsible AD | Ralph Droms | ||
IESG note | |||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document specifies a Subnetwork Encapsulation and Adaptation Layer (SEAL). SEAL operates over virtual topologies configured over connected IP network routing regions bounded by encapsulating border nodes. These virtual topologies are manifested by tunnels that may span multiple IP and/or sub-IP layer forwarding hops, where they may incur packet duplication, packet reordering, source address spoofing and traversal of links with diverse Maximum Transmission Units (MTUs). SEAL addresses these issues through the encapsulation and messaging mechanisms specified in this document.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)