Re: [L2tpext] comments about draft-mkonstan-l2tpext-keyed-ipv6-tunnel

"Henderickx, Wim (Wim)" <wim.henderickx@alcatel-lucent.com> Tue, 17 December 2013 06:19 UTC

Return-Path: <wim.henderickx@alcatel-lucent.com>
X-Original-To: l2tpext@ietfa.amsl.com
Delivered-To: l2tpext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A54601AE088 for <l2tpext@ietfa.amsl.com>; Mon, 16 Dec 2013 22:19:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5] 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 E5lsEnqmM9xg for <l2tpext@ietfa.amsl.com>; Mon, 16 Dec 2013 22:19:02 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id CAC7C1AE024 for <l2tpext@ietf.org>; Mon, 16 Dec 2013 22:19:02 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id rBH6IpMh006102 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 17 Dec 2013 00:18:53 -0600 (CST)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id rBH6IpWL032255 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 17 Dec 2013 07:18:51 +0100
Received: from FR711WXCHMBA07.zeu.alcatel-lucent.com ([169.254.3.62]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Tue, 17 Dec 2013 07:18:51 +0100
From: "Henderickx, Wim (Wim)" <wim.henderickx@alcatel-lucent.com>
To: "Xialiang (Frank)" <frank.xialiang@huawei.com>, "maciek@cisco.com" <maciek@cisco.com>, "Giles Heron (giheron)" <giheron@cisco.com>, "rainer.schatzmayr@telekom.de" <rainer.schatzmayr@telekom.de>
Thread-Topic: comments about draft-mkonstan-l2tpext-keyed-ipv6-tunnel
Thread-Index: Ac7yVZwTFri13v8WQ2CW22pVy1gYCQIgHFeQAAZyqoA=
Date: Tue, 17 Dec 2013 06:18:50 +0000
Message-ID: <CED5AAA9.9BA13%wim.henderickx@alcatel-lucent.com>
References: <C02846B1344F344EB4FAA6FA7AF481F10F3BE891@SZXEMA502-MBS.china.huawei.com>
In-Reply-To: <C02846B1344F344EB4FAA6FA7AF481F10F3BE891@SZXEMA502-MBS.china.huawei.com>
Accept-Language: nl-BE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [135.239.27.41]
Content-Type: multipart/alternative; boundary="_000_CED5AAA99BA13wimhenderickxalcatellucentcom_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Cc: "l2tpext@ietf.org" <l2tpext@ietf.org>
Subject: Re: [L2tpext] comments about draft-mkonstan-l2tpext-keyed-ipv6-tunnel
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2tpext/>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Dec 2013 06:19:05 -0000

Frank, in-line and sorry for the late reply

From: "Xialiang (Frank)" <frank.xialiang@huawei.com<mailto:frank.xialiang@huawei.com>>
Date: Tuesday 17 December 2013 04:19
To: "maciek@cisco.com<mailto:maciek@cisco.com>" <maciek@cisco.com<mailto:maciek@cisco.com>>, "Giles Heron (giheron)" <giheron@cisco.com<mailto:giheron@cisco.com>>, "rainer. schatzmayr" <rainer.schatzmayr@telekom.de<mailto:rainer.schatzmayr@telekom.de>>, Wim Henderickx <wim.henderickx@alcatel-lucent.com<mailto:wim.henderickx@alcatel-lucent.com>>
Cc: "l2tpext@ietf.org<mailto:l2tpext@ietf.org>" <l2tpext@ietf.org<mailto:l2tpext@ietf.org>>
Subject: FW: comments about draft-mkonstan-l2tpext-keyed-ipv6-tunnel

Hi authors,
I have sent this email of comments for a period of time, but don’t get response.
So I try to send it again and hope for getting your kindly feedback.
Thanks!

B.R.
Frank

From: L2tpext [mailto:l2tpext-bounces@ietf.org] On Behalf Of Xialiang (Frank)
Sent: Friday, December 06, 2013 3:35 PM
To: maciek@cisco.com<mailto:maciek@cisco.com>; Giles Heron (giheron); rainer.schatzmayr@telekom.de<mailto:rainer.schatzmayr@telekom.de>; wim.henderickx@alcatel-lucent.com<mailto:wim.henderickx@alcatel-lucent.com>
Cc: l2tpext@ietf.org<mailto:l2tpext@ietf.org>
Subject: [L2tpext] comments about draft-mkonstan-l2tpext-keyed-ipv6-tunnel

Hi authors,
I have reviewed this draft, and consider it a useful draft for giving a concrete use case of using mature L2TPv3 protocol as a data plane overlay technology. I also have several comments below:

1.       You use a source+des IP pair to identify a L2TP tunnel without tenant id carried on the wire. It increases the complexity when identifying tenant network’s traffic using the mapping between tenant network and a large number of source+des IP pairs, especially when tenant network are highly distributed in the real network. While, using tenant id carried on the wire can reduce the complexity largely;

WH> given that we have enough bits in IPv6 addresses, this draft provides the tenant information based on the IPv6 addressing.


2.       Would you consider more general use cases, e.g., supporting IPv4 underlay network, and different types of services overlaid on it (e.g., Ethernet, PPP, IPv4, IPv6 ,etc)?

WH> the draft is focussed on IPv6 only, since the assumption on point 1 is no longer valid.


3.       I cannot find contents in the draft describing how to implement the multipoint VPN in detail. If you don’t use control plane, then data plane flooding or manage plane provision should be supported. Do you follow this way?

WH> I am not sure I understand the point but the draft allows to provision the endpoints through a management plane.

B.R.
Frank