On 9/Apr/20 13:26, adamv0...@netconsultings.com wrote:
> Well one could take a view as: let's say LSO is baked into ONAP which is
> based on ECOMP therefore at is making some use of LSO in one way or the
> other (or anyone using ONAP for that matter).
> Obviously the reality is much more
> From: Mark Tinka
> Sent: Thursday, April 9, 2020 11:10 AM
>
> On 9/Apr/20 11:35, adamv0...@netconsultings.com wrote:
>
> > It's not an on/off switch, but more like a gradual evolution towards LSO (as
> it's being standardized at the same time).
> > It's never a green field deployment, there's
On 9/Apr/20 11:35, adamv0...@netconsultings.com wrote:
> It's not an on/off switch, but more like a gradual evolution towards LSO (as
> it's being standardized at the same time).
> It's never a green field deployment, there's a whole host of existing
> automation infrastructure & OSS/BSS
> From: Mark Tinka
> Sent: Thursday, April 9, 2020 9:45 AM
>
> On 9/Apr/20 10:40, adamv0...@netconsultings.com wrote:
>
> > In big carriers and smaller folks supporting big carriers or in other
> > words or more generally in folks that want to have a common dictionary
> > with each other.
>
>
On 9/Apr/20 10:40, adamv0...@netconsultings.com wrote:
> In big carriers and smaller folks supporting big carriers or in other words
> or more generally in folks that want to have a common dictionary with each
> other.
Yes, that's the goal.
But what I'm asking is anyone we know of publicly
> Mark Tinka
> Sent: Wednesday, April 8, 2020 12:23 PM
>
> On 26/Mar/20 18:59, adamv0...@netconsultings.com wrote:
>
> > How I view MEF is in their role of facilitator/mediator for
> > inter-operator standards.
> > Their original work on Metro Ethernet standards and network
> > certification
On 26/Mar/20 19:41, Aaron Gould wrote:
> Perhaps that, and also, I think they may be substituting that term "mef" for
> "ce" more recently. perhaps to imply that its capabilities are now
> beyond the "metro" and extend into "carrier" space and beyond. Trying to
> make some educated
On 26/Mar/20 18:59, adamv0...@netconsultings.com wrote:
> How I view MEF is in their role of facilitator/mediator for inter-operator
> standards.
> Their original work on Metro Ethernet standards and network certification
> was very helpful for the industry (certainly some ~8 years back when
On 26/Mar/20 17:41, sth...@nethelp.no wrote:
> No idea. But it sure *sounds* like rather significant scope creep.
Well, at some point, it became clear that the world was interested in
generalized Internet access, regardless of how it was carried :-).
Mark.
> From: Aaron Gould
> Sent: Thursday, March 26, 2020 5:48 PM
>
> Yeah, while certifying for mef-cecp, you gain an appreciation for
> their purpose in that space at least. (they do have other
> certifications). Lots of focus on functions and standards that exists
> at UNI's, ENNI's, services
] On Behalf Of
adamv0...@netconsultings.com
Sent: Thursday, March 26, 2020 12:00 PM
To: sth...@nethelp.no; t...@pelican.org
Cc: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] [External] SDx open standard?
> sth...@nethelp.no
> Sent: Thursday, March 26, 2020 3:42 PM
>
> >>> I spen
lections.
-Aaron
-Original Message-
From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of
t...@pelican.org
Sent: Thursday, March 26, 2020 10:25 AM
To: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] [External] SDx open standard?
On Thursday, 26 March, 2020 15:15, sth...@neth
> On Mar 26, 2020, at 8:28 AM, "t...@pelican.org" wrote:
>
> On Thursday, 26 March, 2020 15:15, sth...@nethelp.no said:
>
>>> I spent 10 min browsing MEF web site and still do not know what "MEF"
>>> stands for ... Looks to me like yet one more commercial entity to drain a
>>> little bit of
> sth...@nethelp.no
> Sent: Thursday, March 26, 2020 3:42 PM
>
> >>> I spent 10 min browsing MEF web site and still do not know what "MEF"
> >>> stands for ... Looks to me like yet one more commercial entity to
> >>> drain a little bit of cash out of the vendors while perhaps help
> >>> with
>>> I spent 10 min browsing MEF web site and still do not know what "MEF"
>>> stands for ... Looks to me like yet one more commercial entity to drain a
>>> little bit of cash out of the vendors while perhaps help with marketing and
>>> sales a bit.
>>
>> Metro Ethernet Forum. They've been around
On Thursday, 26 March, 2020 15:15, sth...@nethelp.no said:
>> I spent 10 min browsing MEF web site and still do not know what "MEF"
>> stands for ... Looks to me like yet one more commercial entity to drain a
>> little bit of cash out of the vendors while perhaps help with marketing and
>> sales
>> The standardization is coming, check out
> https://www.mef.net/mef-3-0-sd-wan
>
> I spent 10 min browsing MEF web site and still do not know what "MEF"
> stands for ... Looks to me like yet one more commercial entity to drain a
> little bit of cash out of the vendors while perhaps help with
Metro Ethernet Forum - https://www.mef.net/
On Thu, 26 Mar 2020 at 15:03, Robert Raszuk wrote:
> > The standardization is coming, check out
> https://www.mef.net/mef-3-0-sd-wan
>
> I spent 10 min browsing MEF web site and still do not know what "MEF"
> stands for ... Looks to me like yet one
> The standardization is coming, check out
https://www.mef.net/mef-3-0-sd-wan
I spent 10 min browsing MEF web site and still do not know what "MEF"
stands for ... Looks to me like yet one more commercial entity to drain a
little bit of cash out of the vendors while perhaps help with marketing
> Sent: Sunday, March 15, 2020 6:04 PM
> To: Hunter Fuller
>
> That's what I'm asking about.
>
> While the thread Mark referenced, deals (in my humble opinion) primarily
> with automation side of things, my question is how the whole SDN thing
> became vendor-specific-closed-protocol?
>
> I'm
On 15/Mar/20 20:04, Alex K. wrote:
> That's what I'm asking about.
>
> While the thread Mark referenced, deals (in my humble opinion) primarily
> with automation side of things, my question is how the whole SDN thing
> became vendor-specific-closed-protocol?
So the thread I shared is little to
That's what I'm asking about.
While the thread Mark referenced, deals (in my humble opinion) primarily
with automation side of things, my question is how the whole SDN thing
became vendor-specific-closed-protocol?
I'm not talking specifically about any particular facet of SDN, such as
automation
Well, the "software-defined thing" which started it all, would be
"software-defined networking." And this was widely implemented in
OpenFlow.
One could use OpenFlow to implement SDWAN or SDAccess, and in fact, we
did the latter, for a while (just in the lab/internal, not suitable
for release).
23 matches
Mail list logo
