Browse Prior Art Database

The Subnetwork Encapsulation and Adaptation Layer (SEAL) (RFC5320)

IP.com Disclosure Number: IPCOM000193194D
Original Publication Date: 2010-Feb-01
Included in the Prior Art Database: 2010-Feb-14
Document File: 58 page(s) / 68K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

F. Templin: AUTHOR [+2]

Abstract

As Internet technology and communication has grown and matured, many techniques have developed that use virtual topologies (including tunnels of one form or another) over an actual network that supports the Internet Protocol (IP) [RFC0791][RFC2460]. Those virtual topologies have elements that appear as one hop in the virtual topology, but are actually multiple IP or sub-IP layer hops. These multiple hops often have quite diverse properties that are often not even visible to the endpoints of the virtual hop. This introduces failure modes that are not dealt with well in current approaches.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 4% of the total text.

Independent Submission                                   F. Templin, Ed. Request for Comments: 5320                  Boeing Research & Technology Category: Experimental                                     February 2010 ISSN: 2070-1721

         The Subnetwork Encapsulation and Adaptation Layer (SEAL)

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.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for examination, experimental implementation, and    evaluation.

   This document defines an Experimental Protocol for the Internet    community.  This is a contribution to the RFC Series, independently    of any other RFC stream.  The RFC Editor has chosen to publish this    document at its discretion and makes no statement about its value for    implementation or deployment.  Documents approved for publication by    the RFC Editor are not a candidate for any level of Internet    Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc5320.

IESG Note

   This RFC is not a candidate for any level of Internet Standard.  The    IETF disclaims any knowledge of the fitness of this RFC for any    purpose and in particular notes that the decision to publish is not    based on IETF review for such things as security, congestion control,    or inappropriate interaction with deployed protocols.  The RFC Editor    has chosen to publish this document at its discretion.  Readers of    this document should exercise caution in evaluating its value for    implementation and deployment.  See RFC 3932 for more information.

Templin                       Experimental                      [Page 1]
 RFC 5320                          SEAL                     February 2010

 Copyright Notice

   Copyright (c) 2010 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of t...