Re: [Int-area] draft-ietf-intarea-tunnels

Joe Touch <touch@isi.edu> Mon, 02 November 2015 02:10 UTC

Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 405361B4165 for <int-area@ietfa.amsl.com>; Sun, 1 Nov 2015 18:10:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Mh1_NgOOraG1 for <int-area@ietfa.amsl.com>; Sun, 1 Nov 2015 18:10:41 -0800 (PST)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 662861B417B for <int-area@ietf.org>; Sun, 1 Nov 2015 18:10:35 -0800 (PST)
Received: from [128.9.176.28] (c1-vpn2.isi.edu [128.9.176.28]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id tA229m55029167 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 1 Nov 2015 18:09:48 -0800 (PST)
To: Lucy yong <lucy.yong@huawei.com>, "int-area@ietf.org" <int-area@ietf.org>
References: <2691CE0099834E4A9C5044EEC662BB9D571FF224@dfweml701-chm> <56282A02.5000408@isi.edu> <2691CE0099834E4A9C5044EEC662BB9D572034A0@dfweml701-chm>
From: Joe Touch <touch@isi.edu>
Message-ID: <5636C5EC.9040808@isi.edu>
Date: Sun, 01 Nov 2015 18:09:48 -0800
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <2691CE0099834E4A9C5044EEC662BB9D572034A0@dfweml701-chm>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: tA229m55029167
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/int-area/-yP2ppMSTpM4O_l32IchhaRmTkA>
Subject: Re: [Int-area] draft-ietf-intarea-tunnels
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 02 Nov 2015 02:10:51 -0000

Hi, Lucy,

On 10/31/2015 5:56 PM, Lucy yong wrote:
> Hi Joe,
> 
> Your tunnel draft addresses IP tunnel in the Internet, i.e. both M
> network and N network (in the draft) are on the Internet.

Yes, that's an area already identified for update for clarity.

> The draft describes the arch and req. for use portion of the
> Internet providing a link to other portion of the Internet.
> 
> There are also applications that using portion of the Internet
> provides many links to individual private IP networks, i.e. one link to
> one private IP network. e.g. network virtualization.

Network virtualization has many - often inconsistent and mutually
conflicting - definitions. E.g., IMO, any network that includes tunnels
as links includes network virtualization. A truly virtual network is one
composed entirely of tunnels, IMO.

> It would be useful for your draft to explicitly distinct two cases
> and point out the requirements for both cases. For example, ICMP usage.

I don't see them as distinct. Whether a network is connected to the
public Internet or not is less important than whether IPv4 or IPv6 is
used as the network layer.

Can you clarify how the second case might be distinct from the first
regarding ICMP use or any other aspect?

Joe


> Regards,
> Lucy
> 
> 
>  
>