RE: "Deprecate"

"Templin, Fred L" <Fred.L.Templin@boeing.com> Fri, 02 August 2013 15:41 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA7D211E80EE for <ipv6@ietfa.amsl.com>; Fri, 2 Aug 2013 08:41:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.413
X-Spam-Level:
X-Spam-Status: No, score=-6.413 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FQ3onHoWEmyx for <ipv6@ietfa.amsl.com>; Fri, 2 Aug 2013 08:41:15 -0700 (PDT)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) by ietfa.amsl.com (Postfix) with ESMTP id 9114E11E80D3 for <ipv6@ietf.org>; Fri, 2 Aug 2013 08:41:15 -0700 (PDT)
Received: from blv-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r72FfCvX027607 for <ipv6@ietf.org>; Fri, 2 Aug 2013 08:41:12 -0700
Received: from XCH-PHX-109.sw.nos.boeing.com (xch-phx-109.sw.nos.boeing.com [130.247.25.36]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r72FfBnD027584 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK) for <ipv6@ietf.org>; Fri, 2 Aug 2013 08:41:11 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.29]) by XCH-PHX-109.sw.nos.boeing.com ([169.254.9.81]) with mapi id 14.02.0328.011; Fri, 2 Aug 2013 08:41:13 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: "Deprecate"
Thread-Topic: "Deprecate"
Thread-Index: AQHOj3igiYfnka6nOUeBop7mpmo4ZpmCA2zQgAAJCgA=
Date: Fri, 02 Aug 2013 15:41:13 +0000
Message-ID: <2134F8430051B64F815C691A62D983180DD972@XCH-BLV-504.nw.nos.boeing.com>
References: <FAD482FE-4583-472A-8B57-E789A942686E@gmail.com> <1DF7BDE3-1490-41FE-A959-EC8EC54B0A5F@tzi.org> <8B84E185-36AC-4F22-A88E-5A2F1200AE8B@gmail.com> <51DC77B1.9020206@gmail.com> <DEDA9E45-2839-4D7C-9D86-04360DDE9C1D@gmail.com> <2134F8430051B64F815C691A62D983180DCA04@XCH-BLV-504.nw.nos.boeing.com> <F47D3B2D-A883-4F24-9263-95F85F59E20A@gmail.com> <2134F8430051B64F815C691A62D983180DD8F5@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983180DD8F5@XCH-BLV-504.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 15:41:21 -0000

Hi,

Up to now, the SEAL spec has focused on "tunnel mode", and had the
singular statement:

  "(A transport-mode of operation is also possible, but out of scope
   for this document.)"

in the introduction. (Indeed, the first edition of SEAL (RFC5320)
did specify a transport mode of operation, but that document will
be obsolete by the second edition.) So, in light of these discussions
I decided that now might be a good time to bring transport mode back
into scope and as such have added the following new section to the
document. Please send comments and suggestions. I will post a new
draft version by the end of the day that will include both tunnel
and transport modes.

Thanks - Fred
fred.l.templin@boeing.com

6.  SEAL Transport Mode Specification

   SEAL is also used for transport-mode operation.  Transport mode
   refers to a SEAL encapsulation in which a layer-4 header appears
   immediately following the SEAL header.  The type of layer-4 header is
   indicated in the "NEXTHDR" field the same as for tunnel mode.  The
   SEAL header is identical to the version used for tunnel mode, except
   that the "LINK_ID" and "LEVEL" fields are omitted, and the transport
   layer port numbers are included in each non-initial segment (see:
   Figure 6).

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |    NEXTHDR    |VER|C|P|I|V|R|M|     Offset    |    Reserved   |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      | Source Port (when Offset!=0)  |   Dest Port (when Offset!=0)  |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                      Identification (optional)                |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                  Integrity Check Vector (optional)            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+   ...

                       Figure 6: SEAL Header Format

   The "Source Port" and "Dest Port" are taken from the corresponding
   fields in the transport layer next header that appears immediately
   following the SEAL header in the initial segment.  For example, for
   UDP [RFC0768] the transport layer source/dest ports are 16 bits in
   length and are copied from the transport layer header.  All
   segmentation is exactly as specified in SEAL tunnel mode, and the
   SEAL Control Message Protocol (SCMP) operates the same as for tunnel
   mode.  For example, the source node can probe the path MTU to the
   destination by setting the P bit in a probe packet and waiting for an
   acknowledgement from the destination.

   SEAL transport mode is useful for transport layer protocols that have
   no way to segment the large packets they send.  It is a universal
   format that can be applied to any such transport.