Re: [Int-area] Some thoughts on draft-yong-intarea-inter-sites-over-tunnels

Joe Touch <touch@isi.edu> Sat, 10 December 2016 04:53 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 5B198129558 for <int-area@ietfa.amsl.com>; Fri, 9 Dec 2016 20:53:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.795
X-Spam-Level:
X-Spam-Status: No, score=-9.795 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 KkBcM-JWK7AN for <int-area@ietfa.amsl.com>; Fri, 9 Dec 2016 20:53:41 -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 E2EE612941E for <int-area@ietf.org>; Fri, 9 Dec 2016 20:53:41 -0800 (PST)
Received: from [192.168.1.189] (cpe-172-250-251-17.socal.res.rr.com [172.250.251.17]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id uBA4rBgl001319 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 9 Dec 2016 20:53:13 -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> <ceaf3563-ec86-8fe0-f67d-f50e9b9586ae@isi.edu> <05616d07ab3f420a8c0bd5556837d788@XCH15-06-08.nw.nos.boeing.com> <de82e183-f6dd-b872-eb21-981d57218a81@isi.edu> <a5713afee0f84c008e080f730350ed93@XCH15-06-08.nw.nos.boeing.com> <f69d6b1f-19fa-cb8d-f319-a18f7130bee6@isi.edu> <d9da3c70fcba42ddb6c7a60d8e80b6b4@XCH15-06-08.nw.nos.boeing.com> <622a5176-2b39-f08d-d31c-67aa076d52d6@isi.edu> <19fdababf617416ba19755fce7e2fcb7@XCH15-06-08.nw.nos.boeing.com> <c4cc5ab0-32b2-eff5-38de-803595263b21@isi.edu> <76d6861a032e444193553fe045a41eca@XCH15-06-08.nw.nos.boeing.com> <d6ef34df-3ff9-f989-1d5e-beafd512ff8a@isi.edu> <ef0bd101057340a5b82b1a49e028932c@XCH15-06-08.nw.nos.boeing.com> <5d9713ed-87be-d956-c813-a7ff995cc740@isi.edu> <c05d50bce73b467a9add53c95ec44100@XCH15-06-08.nw.nos.boeing.com> <75a147b0-86cf-04ae-188b-57d214865a50@isi.edu> <e4f67d41d1414819a17ca9439bce3133@XCH15-06-08.nw.nos.boeing.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <11918d0a-5110-d318-251e-9a8c9f984d44@isi.edu>
Date: Fri, 09 Dec 2016 20:53:10 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <e4f67d41d1414819a17ca9439bce3133@XCH15-06-08.nw.nos.boeing.com>
Content-Type: multipart/alternative; boundary="------------D67516602DE2FF2B4F182921"
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/cJfKfFLiPbRTzxIBq26pcDmTdvM>
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: Sat, 10 Dec 2016 04:53:43 -0000

Fred,


On 12/9/2016 4:25 PM, Templin, Fred L wrote:
>
> Hi Joe,
>
>  
>
> I read your document and, for the applications I am concerned with, I
> still
>
> think what I am doing is the better approach. One thing that you may not
>
> have gathered is that the AERO interface does not maintain a
> replicated copy
>
> of the entire IP forwarding table;
>
I wasn't assuming it did - therein lies the problem.

> it only keeps neighbor cache entries for its
>
> currently active sets of neighbors. For AERO Clients, this would
> include the
>
> default router(s) and any peers that it has recently received
> Redirects from.
>
> For AERO Servers, the neighbor cache would include entries for the current
>
> list of associated Clients. So, the AERO interface is not a full-blown
> IP router;
>
> it is a neighbor discovery engine for its active set of neighbors.
>

But it would need to have the full-blown IP forwarding capabilities to
determine which next IP address is intended for a given packet handed to
it by the master IP forwarding table.

>  So, unlike a dynamic routing protocol the AERO interface uses IPv6
> Neighbor
>
> Unreachability Detection (NUD) instead of routing protocol keepalives to
>
> maintain reachability. There is also no routing protocol control messaging
>
> going out over the underlying data links – it is simply data packets plus
>
> occasional NUD messages.
>
That only describes how the table is populated. There's the further
issue of how the table is indexed, which is a full-blown forwarding
lookup (with policy information as well).

>  I noticed that your document was from 1997, which is the same year I
>
> started with SRI International. I think that was right around the time
>
> you and I first met.
>

Not sure - it was presented in early 1997 at the GBN workshop at
Infocom, but also at a few DARPA PI meetings before.

FWIW, I didn't think we met until the IETF, which was in Dec in DC that
same year.

Joe