Re: [Int-area] Some thoughts on draft-yong-intarea-inter-sites-over-tunnels
Joe Touch <touch@isi.edu> Wed, 30 November 2016 22:32 UTC
Return-Path: <touch@isi.edu>
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 674B4129B4C for <int-area@ietfa.amsl.com>; Wed, 30 Nov 2016 14:32:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.796
X-Spam-Level:
X-Spam-Status: No, score=-9.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-2.896] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9FtiGPQlMuoq for <int-area@ietfa.amsl.com>; Wed, 30 Nov 2016 14:32:10 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0BF1129587 for <int-area@ietf.org>; Wed, 30 Nov 2016 14:32:09 -0800 (PST)
Received: from [128.9.184.245] ([128.9.184.245]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id uAUMVYIU020808 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 30 Nov 2016 14:31:34 -0800 (PST)
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Lucy yong <lucy.yong@huawei.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "int-area@ietf.org" <int-area@ietf.org>
References: <2a8ef418-91dc-b0c5-1384-203b4fde3830@gmail.com> <2691CE0099834E4A9C5044EEC662BB9D57B92F39@dfweml501-mbb> <bc9be2d15e2f46a68400c942b44951e1@XCH15-06-08.nw.nos.boeing.com> <743bc5a4-3582-d187-f817-bd32e626c4db@isi.edu> <be6721f90aa54216b30f7197c52ff0a5@XCH15-06-08.nw.nos.boeing.com> <c282e277-3257-a8e0-6256-e143c6d35752@isi.edu> <b1b6f51369864c2da290fba88117cb5f@XCH15-06-08.nw.nos.boeing.com> <950cf5fb-3c71-f428-cea1-ab44849147bb@isi.edu> <daf5035c7fad45eaa577c4e7e08a81cc@XCH15-06-08.nw.nos.boeing.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <d711f321-e8c9-8d69-33d6-4008789b4de9@isi.edu>
Date: Wed, 30 Nov 2016 14:31:33 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.0
MIME-Version: 1.0
In-Reply-To: <daf5035c7fad45eaa577c4e7e08a81cc@XCH15-06-08.nw.nos.boeing.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/n9WrHLtAiypOB4fSDOxZL7Nmet0>
Subject: Re: [Int-area] Some thoughts on draft-yong-intarea-inter-sites-over-tunnels
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 30 Nov 2016 22:32:12 -0000
Hi, Fred (et al.), On 11/30/2016 12:51 PM, Templin, Fred L wrote: > Hi Joe, > ... > I didn't mention route optimization. With AERO, route optimization is what happens > when the tunnel ingress switches from an egress that is on a suboptimal path to a > different egress that is on a better path. That's internal to the tunnel itself, related to the fact that your tunnel is multipoint and treats all egresses as valid. That's another feature, but again it's hard to see where that would be discussed. It's closest in spirit to egress determination in BGP or LISP, and has no clear relation (AFAICT) to INTAREA (expertise or purview). However... > Due to the link nature of the NBMA overlay, > that switching is accomplished through the use of IPv6 ND Redirect messages the > same as would occur on a physical link (and in the same spirit as published in RFC6706). I don't think I would call that routing either when it happens in a regular network or inside an NMBA tunnel. > That is why I ended up agreeing with you that fully embracing fragmentation is the > only way to truly handle tunnel MTU, because without fragmentation an MTU that > worked over the suboptimal path might fail over the new path once route > optimization is employed. >> And traffic engineering is easy >> in a tunnel *if* it's supported in the base network over which the >> tunnel operates, and impossible otherwise. > Traffic engineering as in allowing the Client to select both the outbound underlying > interface for outbound traffic and the inbound underlying interface for inbound > traffic. A tunnel ends at interfaces. Client determination of interfaces happens separate from a tunnel, IMO. > So, a device that has both cellular and WiFi can send and receive packets > with different TOS markings over both interfaces simultaneously (e.g., TOS '1' goes > out over cellular, TOS '2' goes out over WiFI, etc.) and respectively for the > inbound direction. That's the job of interface selection in the host, which is already specified in RFC1122 and extensions. Are you suggesting a change to that? If so, it seems like it's completely orthogonal to the use of tunnels as interfaces. > >> I'm not claiming this wouldn't be useful. I'm saying that we need to >> know what problem it solves to know where to home it. > I have identified two very important use cases relating to aviation. You've defined a customer, IMO - which is great, but short of taking this to an aerospace forum, it doesn't really help me understand where in the IETF it should be discussed. > So, the fortuitous > selection of the AERO acronym now seems quite appropriate. We are also using it for > mobile VPN management for corporate enterprise mobile device users (cellphones > and tablets), and we are planning to release source code soon. That's all good news, but I'm still left not quite understanding where in the IETF this should (or could) be handled. We don't really have a WG for creating tunnels and I'm not sure INTAREA should serve as a default. Joe
- [Int-area] Some thoughts on draft-yong-intarea-in… Brian E Carpenter
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Lucy yong
- Re: [Int-area] Some thoughts on draft-yong-intare… Brian E Carpenter
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Tom Herbert
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Tom Herbert
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Templin, Fred L
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Templin, Fred L
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Templin, Fred L
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Templin, Fred L
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Templin, Fred L
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Templin, Fred L
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Templin, Fred L
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Templin, Fred L
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Templin, Fred L
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Templin, Fred L
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Templin, Fred L
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Templin, Fred L
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Templin, Fred L
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Templin, Fred L
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Templin, Fred L
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Templin, Fred L
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- [Int-area] regarding subnet redirects Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Templin, Fred L
- Re: [Int-area] regarding subnet redirects Templin, Fred L
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] regarding subnet redirects Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Templin, Fred L
- Re: [Int-area] regarding subnet redirects Templin, Fred L
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Templin, Fred L
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Templin, Fred L
- Re: [Int-area] Some thoughts on draft-yong-intare… Templin, Fred L
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Templin, Fred L
- Re: [Int-area] Some thoughts on draft-yong-intare… Joe Touch
- Re: [Int-area] Some thoughts on draft-yong-intare… Templin, Fred L
- Re: [Int-area] Some thoughts on draft-yong-intare… Templin, Fred L