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

[John E Drake <[e-mail]>]

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 <[e-mail]>
Sent: Thursday, December 20, 2018 9:55 AM
To: John E Drake <[e-mail]>; Andrew G. Malis <[e-mail]>; [e-mail] <[e-mail]>
Cc: TEAS WG Chairs <[e-mail]>; [e-mail]
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:[e-mail]] On Behalf Of John E Drake
Sent: Wednesday, December 19, 2018 11:46 AM
To: Andrew G. Malis; [e-mail]<mailto:[e-mail]>
Cc: TEAS WG Chairs; [e-mail]<mailto:[e-mail]>
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 <[e-mail]<mailto:[e-mail]>> On Behalf Of Andrew G. Malis
Sent: Tuesday, December 18, 2018 9:38 AM
To: [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>
Cc: TEAS WG Chairs <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>
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 <[e-mail]<mailto:[e-mail]>> 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
[e-mail]<mailto:[e-mail]>
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=>