Re: [Int-area] New version of draft-bormann-intarea-alfi

"Templin, Fred L" <Fred.L.Templin@boeing.com> Mon, 09 September 2013 20:50 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69D9311E8116 for <int-area@ietfa.amsl.com>; Mon, 9 Sep 2013 13:50:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 J+WLcSf-B6qf for <int-area@ietfa.amsl.com>; Mon, 9 Sep 2013 13:50:20 -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 49B6821F9B07 for <int-area@ietf.org>; Mon, 9 Sep 2013 13:50:20 -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 r89KoF5m000724 for <int-area@ietf.org>; Mon, 9 Sep 2013 13:50:15 -0700
Received: from XCH-PHX-309.sw.nos.boeing.com (xch-phx-309.sw.nos.boeing.com [130.247.25.163]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r89KoEID000707 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Mon, 9 Sep 2013 13:50:14 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.29]) by XCH-PHX-309.sw.nos.boeing.com ([169.254.9.168]) with mapi id 14.02.0328.011; Mon, 9 Sep 2013 13:50:17 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Carsten Bormann <cabo@tzi.org>, "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: [Int-area] New version of draft-bormann-intarea-alfi
Thread-Index: AQHOrZpXwCwDmwuB/0aiEJA9DGnOIJm933Fw
Date: Mon, 09 Sep 2013 20:50:17 +0000
Message-ID: <2134F8430051B64F815C691A62D9831810456E@XCH-BLV-504.nw.nos.boeing.com>
References: <A1B43C2F-F80F-48DE-AF3A-0AA8C97496D0@tzi.org>
In-Reply-To: <A1B43C2F-F80F-48DE-AF3A-0AA8C97496D0@tzi.org>
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Subject: Re: [Int-area] New version of draft-bormann-intarea-alfi
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Sep 2013 20:50:25 -0000

Hi Carsten,

Here is a draft exploring a slightly different approach to
"link adaptation avoidance":

http://tools.ietf.org/html/draft-generic-6man-tunfrag-07

It mentions tunnels, but is applicable to any link type over
which IPv6 requires the assistance of a link-specific adaptation
scheme.

You might also want to have a look at SEAL, which accommodates
arbitrarily large MTU sizes over tunnels:

http://www.ietf.org/id/draft-templin-intarea-seal-62.txt

I think what you are proposing (and what the other draft I cited
is proposing) would be compatible with SEAL.

Thanks - Fred

> -----Original Message-----
> From: int-area-bounces@ietf.org [mailto:int-area-bounces@ietf.org] On
> Behalf Of Carsten Bormann
> Sent: Monday, September 09, 2013 1:22 PM
> To: int-area@ietf.org
> Subject: [Int-area] New version of draft-bormann-intarea-alfi
> 
> I just submitted a re-spin of draft-bormann-intarea-alfi.
> Apart from typos, the major difference is that the abstract now
> explicitly says:
> 
>   The present specification defines two alternative mechanisms [...]
> 
>   One design is based on the the IPv6 design and probably doesn't work
>   on the Internet.  The other design goes strictly against the IPv6
>   design and probably works well on the Internet.
> 
> Maybe we can find some time in Vancouver to discuss this aspect of the
> draft.
> 
> Htmlized:        http://tools.ietf.org/html/draft-bormann-intarea-alfi-
> 04
> Diff:            http://www.ietf.org/rfcdiff?url2=draft-bormann-
> intarea-alfi-04
> 
> Grüße, Carsten
> 
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area