Re: [RTG-DIR] [L2tpext] RTG-DIR review: draft-ietf-l2tpext-keyed-ipv6-tunnel-05

"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Mon, 21 March 2016 19:28 UTC

Return-Path: <cpignata@cisco.com>
X-Original-To: rtg-dir@ietfa.amsl.com
Delivered-To: rtg-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BF6112D851; Mon, 21 Mar 2016 12:28:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 YB8-31KO5LFr; Mon, 21 Mar 2016 12:28:20 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED4D612DAB0; Mon, 21 Mar 2016 12:28:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13495; q=dns/txt; s=iport; t=1458588499; x=1459798099; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=1L2X7FI0N0FkN8j/tbz8QTDHYJR5C/qAu50IO3C2QtA=; b=K0xjUbyFm8X97VLsSg6ae+q6+e9Y6nJ3mP4Fd4Tppmb3EM23IPIXNjew jcCJ0VukyEY2oA6PMLfEPqzVzUyrJfU1ldhpLoO2033z+IJb2lQtGGelB GqX/hKFLn929xo/ZHwflFlqz5UbECsEDTRiMOlPfXUnZolxZ9B/PrAa4a c=;
X-Files: signature.asc : 841
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DtAgBnSvBW/5FdJa1egmdMgTYPBq5Rhl+Ebg6BcIYNAoEtOBQBAQEBAQEBZCeEQQEBAQMBI1YFBwQCAQgRAwECAScDAgIhERQJCAIEDgUOiAQDCgivN4pXDYRUAQEBAQEBAQEBAQEBAQEBAQEBAQEBDQiGHoFzCIJJgj6CBBqCYCuCKwWTBIQiMQGDHYFmhwuBdYFlh3GFMYcxh1QBHgFDggMZgUlqAYkHfgEBAQ
X-IronPort-AV: E=Sophos;i="5.24,373,1454976000"; d="asc'?scan'208,217";a="88719401"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Mar 2016 19:28:18 +0000
Received: from XCH-RTP-017.cisco.com (xch-rtp-017.cisco.com [64.101.220.157]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id u2LJSIfm027748 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 21 Mar 2016 19:28:18 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-017.cisco.com (64.101.220.157) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 21 Mar 2016 15:28:17 -0400
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1104.009; Mon, 21 Mar 2016 15:28:17 -0400
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: "Giles Heron (giheron)" <giheron@cisco.com>
Thread-Topic: [L2tpext] RTG-DIR review: draft-ietf-l2tpext-keyed-ipv6-tunnel-05
Thread-Index: AQHRIiH8oIv5vLabXk6tkiwcXDwZCp7Bf+EA//+vpFeAAIhJAICjfVGAgAATSwCAAAIJgIAAA/sA
Date: Mon, 21 Mar 2016 19:28:17 +0000
Message-ID: <62398ACE-576D-47B9-9114-8DF2B2054F0A@cisco.com>
References: <DB3PR03MB07802A1F72B4B0E8459E60779D590@DB3PR03MB0780.eurprd03.prod.outlook.com> <8FEFEEB2-0AC5-4C81-9727-AB9D49DB1913@cisco.com> <743196D6-DD0E-44C7-916B-E70824FE2A15@cisco.com> <D8223CD8-6049-49ED-A4C1-0B0F68F6E0B8@cisco.com> <904C8E01-D07F-4376-8AAD-38F3A42D3F01@cisco.com> <DB3PR03MB07803677839A7B4D48ADA2CA9D080@DB3PR03MB0780.eurprd03.prod.outlook.com> <BF350ECA-D4D4-42CB-9AA5-BD1F1AA5EF4B@cisco.com> <uka1pb7vqcp2lxr29npvgt87.1458587097958@email.android.com> <EA2F606D-D75C-4008-889D-7DE817E8D673@cisco.com>
In-Reply-To: <EA2F606D-D75C-4008-889D-7DE817E8D673@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.150.54.101]
Content-Type: multipart/signed; boundary="Apple-Mail=_FA9CEB04-AB94-43B1-BE5C-BFAE01F4C194"; protocol="application/pgp-signature"; micalg="pgp-sha256"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-dir/gJHlfZoVRPGWa1l3JFae8-qFxyY>
Cc: "draft-ietf-l2tpext-keyed-ipv6-tunnel.all@tools.ietf.org" <draft-ietf-l2tpext-keyed-ipv6-tunnel.all@tools.ietf.org>, Maciek Konstantynowicz <maciek@cisco.com>, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "rtg-ads@ietf.org" <rtg-ads@ietf.org>, Rainer Schatzmayr <rainer.schatzmayr@telekom.de>, "l2tpext-chairs@ietf.org" <l2tpext-chairs@ietf.org>, Stewart Bryant <stewart.bryant@gmail.com>, "Mark Townsley (townsley)" <townsley@cisco.com>, Wim Henderickx <wim.henderickx@alcatel-lucent.com>
Subject: Re: [RTG-DIR] [L2tpext] RTG-DIR review: draft-ietf-l2tpext-keyed-ipv6-tunnel-05
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-dir/>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Mar 2016 19:28:32 -0000

Thanks Giles and Sasha!

My AR$ 0.02 inline.

> On Mar 21, 2016, at 3:14 PM, Giles Heron (giheron) <giheron@cisco.com> wrote:
> 
> Hi Sasha,
> 
>> On 21 Mar 2016, at 19:06, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com <mailto:Alexander.Vainshtein@ecitele.com>> wrote:
>> 
>> Giles,
>> I will read the draft and provide detailed comments tomorrow. If you want to post it earlier, it is also OK.
> I’ll have to post today due to the cut-off.  I’m sure we can figure out a next rev once the window opens again.

Exactly — that sounds good. Posting will also make it easier to track state, diffs, etc.

Let’s also continue the conversation in this thread.
>> With regard to circular references - it is simple to resolve if the reference to the YANG draft in this one is Informational. To me it maked sense due to the imortant role management plays in this draft, but I do not insist on it.
> I'm not sure if the tip revisions of 2 drafts can refer to each other as one has to be published before the other (even if by a few minutes)?

I’d leave it as-is.
>> Your claim that the techniques  draft allows for better ECMP looks very interesting. I must admit that I have completely missed this consideration in my original analysis.
> yes - that’s the main benefit.  But there others (the route advertisement granularity benefit I alluded to, but also potentially implementation advantages in being able to do a simpler lookup).
> 
> Giles

Thanks!

— Carlos.
>> Thumb typed on my cellphone
>> Regards,
>> Sasha
>> 
>> -------- Original Message --------
>> From: "Giles Heron (giheron)" <giheron@cisco.com <mailto:giheron@cisco.com>>
>> Date: Mon, March 21, 2016 7:57 PM +0200
>> To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com <mailto:Alexander.Vainshtein@ecitele.com>>
>> CC: Maciek Konstantynowicz <maciek@cisco.com <mailto:maciek@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>>, rtg-dir@ietf.org <mailto:rtg-dir@ietf.org>, draft-ietf-l2tpext-keyed-ipv6-tunnel.all@tools.ietf.org <mailto:draft-ietf-l2tpext-keyed-ipv6-tunnel.all@tools.ietf.org>, "Mark Townsley (townsley)" <townsley@cisco.com <mailto:townsley@cisco.com>>, Stewart Bryant <stewart.bryant@gmail.com <mailto:stewart.bryant@gmail.com>>, l2tpext-chairs@ietf.org <mailto:l2tpext-chairs@ietf.org>, rtg-ads@ietf.org <mailto:rtg-ads@ietf.org>, "Carlos Pignataro (cpignata)" <cpignata@cisco.com <mailto:cpignata@cisco.com>>
>> Subject: Re: [L2tpext] RTG-DIR review:	draft-ietf-l2tpext-keyed-ipv6-tunnel-05
>> 
>> Updated draft attached (sorry for the delay).  will post this in an hour or two unless anyone objects.
>> 
>> changes:
>> 
>> 1) updated the wording to make it clear that the management plane is now in charge instead of the control plane (to address your comment re re-configuration to change cookies etc.)  I didn’t go as far as putting the word “orchestrator” in the draft as that may change by next week ;)   But I did use the phrase “matching configurations” - which should take care of concerns re e.g. MTU mismatches.
>> 
>> 2) updated the draft to allow the L2-specific sublayer (for VCCV and frame sequencing)
>> 
>> 3) added a paragraph to section 2 explaining the benefits of this approach (better ECMP and finer-grained route advertisements)
>> 
>> we can debate the other comments at a later point, but for now I wanted to get the draft published again - partly because there’s a dependency on this draft from the keyed IP tunnel YANG draft.  Speaking of which I’m not sure I want to put a ref here to that draft as that would all get a bit circular.
>> 
>> Giles
>> 
>