Re: [Teas] WG adoption poll - draft-dong-teas-enhanced-vpn-03

"Andrew G. Malis" <agmalis@gmail.com> Mon, 24 December 2018 14:34 UTC

Return-Path: <agmalis@gmail.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD5A71271FF; Mon, 24 Dec 2018 06:34:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.991
X-Spam-Level:
X-Spam-Status: No, score=0.991 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 9bvYCVOI2hAr; Mon, 24 Dec 2018 06:34:01 -0800 (PST)
Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (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 94FD3130EFC; Mon, 24 Dec 2018 06:34:01 -0800 (PST)
Received: by mail-qt1-x82e.google.com with SMTP id l11so13164258qtp.0; Mon, 24 Dec 2018 06:34:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+E8e01k0qsWHZ5D/gg0cze07IEbZGvS/GxzdT1UKs+g=; b=e0QAVtPHziQw2SSQxBF5wwGYLpqe3I5e67xFlsQXUysaa+Jhw+PFHGu3kXSFtGuvzW crPgec+wiDQK4drkZ7VvnA70wjyrsyvksTuRezPOC6UHlcKhC7epN9uh23MXEEJxzyed EcZJp+45sVGy3sy2z6Wt0JJOu5zMrDImB5M9AbTZWHuYNg9vBL2rrMTTtIrc74bZyuv5 r8Wwt6M4BhtumLkMjfUCi3O3hn8ib6QY6ovJjtRw0kuskLIKgRZ+j7zeSx6HumFFEaAn sYmUjoRYksGlSnma1YNzIrh6IrvfgQoSm/ssz0uDD0ZycsZNQdSaLzsDNAFru1HeXsX0 zf5g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+E8e01k0qsWHZ5D/gg0cze07IEbZGvS/GxzdT1UKs+g=; b=OKUgaZKSCrgx4LdZQyg4ytbVt8t05V+z3SJi/7s3LBcnsscIkY5HMlZK1SJuC/N9qD 7aKYctX3hvMhHtODpfBJvoCSjmqc639cW5TODGj6RW53zfdKP0NLoHeHpOy90PPtK8da ohbt42XMsGQ+e0cGhpE5cJOC3dHF9/7lA6XW7lf2KwhW5qZzzcLjPYko7/AMFZ+Cs91c T5S32e88funP6xeNT8ycrL2dUQmcC45eGGOf0X+GjqyISDXA1EfMWAd9GI5XpwdB/mcN ++ATbMY98E80ELF0cATTY36gSt8wyUBfDbdbD82iVNoe2HOZ+BnI0ckvHFusBhHU7zu1 RM/Q==
X-Gm-Message-State: AA+aEWacOH865wVvkHUNoywtqaLucizfrcyoFCIqnZjj5R1Oe/q8fngI jf/1ouvvcOKKg1jEnqIYznPgC1AscOmd4P1Jdfc=
X-Google-Smtp-Source: AFSGD/Vj8s4GKUr40LgRLpIGvidgACOoBu4AXCC0gIfgV7nyj4LOxC+bkVdbnKrt3GADwuM5sB6XUpdJV5icgvkQ1KU=
X-Received: by 2002:ac8:2eb8:: with SMTP id h53mr12146878qta.18.1545662040528; Mon, 24 Dec 2018 06:34:00 -0800 (PST)
MIME-Version: 1.0
References: <CA+YzgTuYgfTNEX9s4XPAOOA_X2+uqxf7sSWBDtq32SuE4FjTKQ@mail.gmail.com> <CAA=duU2DGZzxuzPexyPzCf2AJWC5cZYXZSKzGcE15JpuPT3hdw@mail.gmail.com> <BYAPR05MB50299F47DD4D75210DD39A63C7BE0@BYAPR05MB5029.namprd05.prod.outlook.com> <0C72C38E7EBC34499E8A9E7DD00786391C5ED4B0@sjceml521-mbx.china.huawei.com> <BYAPR05MB50295366A9F676E156A0FADDC7BF0@BYAPR05MB5029.namprd05.prod.outlook.com> <76CD132C3ADEF848BD84D028D243C927C2FFD82B@NKGEML515-MBX.china.huawei.com> <BYAPR05MB50299F82613D934562D8724AC7B80@BYAPR05MB5029.namprd05.prod.outlook.com> <76CD132C3ADEF848BD84D028D243C927C3017E56@NKGEML515-MBX.china.huawei.com> <BB0583FD-C8E9-4A64-8C5E-068D5FBC5E2A@juniper.net>
In-Reply-To: <BB0583FD-C8E9-4A64-8C5E-068D5FBC5E2A@juniper.net>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Mon, 24 Dec 2018 09:33:49 -0500
Message-ID: <CAA=duU1BiEL2sY3gbNY2CuiPB7qA_fPK4V6NQWe7A9JU-354ww@mail.gmail.com>
To: John E Drake <jdrake@juniper.net>
Cc: "Dongjie (Jimmy)" <jie.dong@huawei.com>, Igor Bryskin <Igor.Bryskin@huawei.com>, "EXT-vishnupavan@gmail.com" <vishnupavan@gmail.com>, TEAS WG Chairs <teas-chairs@ietf.org>, "teas@ietf.org" <teas@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000de5bfe057dc57cf5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/ZObinDfIE-qfPSdIMfWbjcpp_C8>
Subject: Re: [Teas] WG adoption poll - draft-dong-teas-enhanced-vpn-03
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Dec 2018 14:34:04 -0000

John,

Does RFC 3209 have any guidance on how many RSVP-TE sessions you can run
simultaneously in a network, or a node? It's obviously both implementation
and deployment dependent. Why is this draft any different?

Cheers,
Andy


On Mon, Dec 24, 2018 at 7:49 AM John E Drake <jdrake@juniper.net> wrote:

> Comments inline
>
> Sent from my iPhone
>
> On Dec 24, 2018, at 5:46 AM, Dongjie (Jimmy) <jie.dong@huawei.com> wrote:
>
> Hi John,
>
>
>
> Please see inline.
>
>
>
> Best regards,
>
> Jie
>
>
>
> *From:* John E Drake [mailto:jdrake@juniper.net <jdrake@juniper.net>]
> *Sent:* Friday, December 21, 2018 9:15 PM
> *To:* Dongjie (Jimmy) <jie.dong@huawei.com>; Igor Bryskin <
> Igor.Bryskin@huawei.com>; Andrew G. Malis <agmalis@gmail.com>;
> EXT-vishnupavan@gmail.com <vishnupavan@gmail.com>
> *Cc:* TEAS WG Chairs <teas-chairs@ietf.org>; teas@ietf.org
> *Subject:* RE: [Teas] WG adoption poll - draft-dong-teas-enhanced-vpn-03
>
>
>
> Hi,
>
>
>
> Comment inline
>
>
>
> Yours Irrespectively,
>
>
>
> John
>
>
>
> *From:* Dongjie (Jimmy) <jie.dong@huawei.com>
> *Sent:* Thursday, December 20, 2018 9:47 PM
> *To:* John E Drake <jdrake@juniper.net>; Igor Bryskin <
> Igor.Bryskin@huawei.com>; Andrew G. Malis <agmalis@gmail.com>;
> EXT-vishnupavan@gmail.com <vishnupavan@gmail.com>
> *Cc:* TEAS WG Chairs <teas-chairs@ietf.org>; teas@ietf.org
> *Subject:* RE: [Teas] WG adoption poll - draft-dong-teas-enhanced-vpn-03
>
>
>
> Hi John,
>
>
>
> This draft does not suggest to allocate network resources to each
> individual VPN, only the VPNs which require particular level of SLA need to
> be integrated with underlay network resources, thus the number of enhanced
> VPN would be much less than the number of traditional overlay VPNs. Also it
> is possible that several VPNs with similar characteristics could be
> assigned with a set of aggregated resources,  and would share the same
> logical network.
>
>
>
> *[JD]  I don’t recall any such discussion in the draft.  Further, what is
> the maximum # of VPN+ instances supported in a given network such that that
> network does not implode?*
>
>
>
> [Jie] Such discussion happened during the presentation on previous IETF
> meetings, the current draft doesn't mandate the mapping of each individual
> VPN to dedicated logical network with resources allocated.
>
>
> JD. I am going to compile a list of statements
> that the draft makes that would lead one to a
> different conclusion
>
> That said, we could add some clarification in future version. The number
> of enhanced VPNs would depend on the number of services and customers which
> have such level of SLA requirement.
>
>
>
>
> JD  So, you have no guidance to offer?
>
>
>
> Best regards,
>
> Jie
>
>
>
> *From:* Teas [mailto:teas-bounces@ietf.org <teas-bounces@ietf.org>] *On
> Behalf Of *John E Drake
> *Sent:* Thursday, December 20, 2018 11:14 PM
> *To:* Igor Bryskin <Igor.Bryskin@huawei.com>; Andrew G. Malis <
> agmalis@gmail.com>; EXT-vishnupavan@gmail.com <vishnupavan@gmail.com>
> *Cc:* TEAS WG Chairs <teas-chairs@ietf.org>; teas@ietf.org
> *Subject:* Re: [Teas] WG adoption poll - draft-dong-teas-enhanced-vpn-03
>
>
>
> Igor,
>
>
>
> I am not convinced that network slicing is a good idea because it assumes
> that logical networks w/ vastly different characteristics can be built out
> of a set of common network resources.  I am convinced that allocating
> network resources on a per-VPN basis is a bad idea because of the scaling
> issues.
>
>
>
> Yours Irrespectively,
>
>
>
> John
>
>
>
> *From:* Igor Bryskin <Igor.Bryskin@huawei.com>
> *Sent:* Thursday, December 20, 2018 9:55 AM
> *To:* John E Drake <jdrake@juniper.net>; Andrew G. Malis <
> agmalis@gmail.com>; EXT-vishnupavan@gmail.com <vishnupavan@gmail.com>
> *Cc:* TEAS WG Chairs <teas-chairs@ietf.org>; teas@ietf.org
> *Subject:* RE: [Teas] WG adoption poll - draft-dong-teas-enhanced-vpn-03
>
>
>
> Hi John,
>
>
>
> Do you see any differences between a logical network and a network
> topology? Specifically, would you define network slices as produced by the
> same physical network sufficiently separated network topologies, each of
> which designed for specific class(es) of clients/overlays, with network
> resources available for the overlays limited by the resource pools
> allocated to the corresponding topologies? Another question: could network
> slices in your opinion be built hierarchically, i.e. higher level slices
> comprised of lower level ones?
>
>
>
> Thanks,
>
> Igor
>
>
>
> *From:* Teas [mailto:teas-bounces@ietf.org <teas-bounces@ietf.org>] *On
> Behalf Of *John E Drake
> *Sent:* Wednesday, December 19, 2018 11:46 AM
> *To:* Andrew G. Malis; EXT-vishnupavan@gmail.com
> *Cc:* TEAS WG Chairs; teas@ietf.org
> *Subject:* Re: [Teas] WG adoption poll - draft-dong-teas-enhanced-vpn-03
>
>
>
> Andy,
>
>
>
> Network slicing is very different from what is described in this draft.
> Network slicing envisions a small number of logical networks built using
> the same physical network, each of which is designed for a specific type of
> overlay network and a given VPN, depending upon its requirements, would be
> assigned to one or more of these network slices.  This draft, in contrast,
> is describing assignment of resources from the physical network to
> individual VPNs.
>
>
>
> This is clearly absurd, and its characterization as a ‘scalable approach’
> seems ill-considered.
>
>
>
> This draft is also not a framework draft in any of the normally used
> definitions of that word (
> https://www.merriam-webster.com/dictionary/framework
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.merriam-2Dwebster.com_dictionary_framework&d=DwMGaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=CRB2tJiQePk0cT-h5LGhEWH-s_xXXup3HzvBSMRj5VE&m=n9sCWh1x8RH083BAlFMqUZfK0blyu7AEqTYj5kopZ1I&s=o2aQfkCcHYaq6v8_OptqlhDqzYAgs1OiHS3JnOcuXtY&e=>).
> Rather, I would characterize it as a set of semi-random musings.
>
>
>
> Yours Irrespectively,
>
>
>
> John
>
>
>
> *From:* Teas <teas-bounces@ietf.org> *On Behalf Of *Andrew G. Malis
> *Sent:* Tuesday, December 18, 2018 9:38 AM
> *To:* EXT-vishnupavan@gmail.com <vishnupavan@gmail.com>
> *Cc:* TEAS WG Chairs <teas-chairs@ietf.org>; teas@ietf.org
> *Subject:* Re: [Teas] WG adoption poll - draft-dong-teas-enhanced-vpn-03
>
>
>
> Yes/support. This is a scalable approach for network slicing and enhanced
> VPNs that builds on a body of existing work.
>
>
>
> Cheers,
>
> Andy
>
>
>
>
>
> On Mon, Dec 17, 2018 at 2:27 AM Vishnu Pavan Beeram <vishnupavan@gmail.com>
> wrote:
>
> All,
>
> This is start of a *three* week poll on making
> draft-dong-teas-enhanced-vpn a TEAS working group document.
> Please send email to the list indicating "yes/support" or "no/do not
> support". If indicating no, please state your reservations with the
> document. If yes, please also feel free to provide comments you'd
> like to see addressed once the document is a WG document.
>
> The poll ends Jan 7th 2019 (extra week to account for the holidays).
>
> Thanks,
> Pavan and Lou
>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_teas&d=DwMFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=CRB2tJiQePk0cT-h5LGhEWH-s_xXXup3HzvBSMRj5VE&m=jfPzAk6KYMTzEcjux7ADyZR5qPrxoPYBDdzWSlkedyw&s=uXdPvThk8MvzKASbv-H0_ekBtni_GK-xqPKnIbJ6ek4&e=>
>
>