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

Joe Touch <touch@isi.edu> Thu, 01 December 2016 18:22 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 4E848129861 for <int-area@ietfa.amsl.com>; Thu, 1 Dec 2016 10:22:34 -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 gjAr1nqm1XeV for <int-area@ietfa.amsl.com>; Thu, 1 Dec 2016 10:22:32 -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 1DB231297EF for <int-area@ietf.org>; Thu, 1 Dec 2016 10:22:22 -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 uB1ILVid016610 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 1 Dec 2016 10:21:31 -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> <d711f321-e8c9-8d69-33d6-4008789b4de9@isi.edu> <93f8d61c9b6343b9b70b887c43e3aaee@XCH15-06-08.nw.nos.boeing.com> <d4e08982-03f8-fe5e-0c67-aa5cd7f26275@isi.edu> <e4096f9729474e00915432aa5c3af300@XCH15-06-08.nw.nos.boeing.com> <b82247d0-5221-ad60-3c4f-6e3287ef1fa9@isi.edu> <f54cd95a4f974ca189e2b3fb24864b97@XCH15-06-08.nw.nos.boeing.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <a3f0ade1-2145-ee28-31cf-d5a4878b507c@isi.edu>
Date: Thu, 01 Dec 2016 10:21:29 -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: <f54cd95a4f974ca189e2b3fb24864b97@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/c2hUcAMmFwcctLRlkvihSTpUd_Q>
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: Thu, 01 Dec 2016 18:22:34 -0000

Hi, Fred,

To wrap up:

- Subnet Redirects appear to rely on AERO-specific mechanisms, so would
not be of more general relevance to a bis doc IMO

- multiple link addresses are already part of the Ethernet spec and
already handled by most IP over Ethernet implementations (and TOS
marking correlation is defined in 802.1p).  When you assign more than
one link address to a single physical interface, you're acting as if you
have multiple links. At that point, the forwarding table indicates not
only the next-hop IP but the outgoing link -- for multiple link
addresses these are treated as different virtual interfaces already.

- I agree that IPv6 ND was done in an INTAREA WG; the same might be true
for AERO, but the INTAREA WG should be a place where generic aspects of
all Internet layer issues should be addressed, not domain-specific
solutions (IMO).

AERO might be one doc, but it is 60+ pages with over 70 revisions. I don't think it would be useful to bog down INTAREA with something that large.

Joe