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

"Templin, Fred L" <Fred.L.Templin@boeing.com> Thu, 01 December 2016 18:36 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 DF6E612983F for <int-area@ietfa.amsl.com>; Thu, 1 Dec 2016 10:36:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 nUFOFjQu6Scc for <int-area@ietfa.amsl.com>; Thu, 1 Dec 2016 10:36:06 -0800 (PST)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B128B129859 for <int-area@ietf.org>; Thu, 1 Dec 2016 10:36:06 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id uB1Ia6Eo054264; Thu, 1 Dec 2016 11:36:06 -0700
Received: from XCH15-06-10.nw.nos.boeing.com (xch15-06-10.nw.nos.boeing.com [137.136.239.219]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id uB1IZx2V053731 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Thu, 1 Dec 2016 11:35:59 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-10.nw.nos.boeing.com (2002:8988:efdb::8988:efdb) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Thu, 1 Dec 2016 10:35:58 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1178.000; Thu, 1 Dec 2016 10:35:58 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joe Touch <touch@isi.edu>, Lucy yong <lucy.yong@huawei.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: [Int-area] Some thoughts on draft-yong-intarea-inter-sites-over-tunnels
Thread-Index: AQHSSfUTLZDjgwj4v06xdSRLJ7spf6DwdPtAgAFWbFCAAJuxAP//gxPAgACJCwD//3tEwIAAjWUA//+BhHAAFPoOgAAP0p/A//+omgD//4m84IABfSIAgACA9qD//51zgIAAhBJQ
Date: Thu, 01 Dec 2016 18:35:58 +0000
Message-ID: <1707aa63f4e4424e85a8933a79b43dfe@XCH15-06-08.nw.nos.boeing.com>
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> <a3f0ade1-2145-ee28-31cf-d5a4878b507c@isi.edu>
In-Reply-To: <a3f0ade1-2145-ee28-31cf-d5a4878b507c@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/xP-KDnq3yICEvbVZXpzpf7okY3E>
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:36:21 -0000

Hi Joe,

> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Thursday, December 01, 2016 10:21 AM
> 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
> Subject: Re: [Int-area] Some thoughts on draft-yong-intarea-inter-sites-over-tunnels
> 
> 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

RFC6706 already specifies how these Redirects work and is agnostic to the
link type. AERO(bis) tells how they work on AERO links through use of the
IPv6 ND protocol on a specific link type.

> - 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). 

I'd like to see what you are talking about so I can compare it to what
AERO is doing.

> When you assign more than
> one link address to a single physical interface, you're acting as if you
> have multiple links.

No, you are acting as if there are multiple link-layer addresses on the
same link.

> 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.

Going with what I just said above, the forwarding table indicates only
the next-hop IP. It is the neighbor cache entry for the next-hop IP
that includes the multiple link-layer addresses. But, it is all one link.

> - 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.

The document size and number of revisions are irrelevant. By making it
an intarea doc, it would revert back to a -00.

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

> Joe
>