Re: [onap-tsc] Call for vCPE VNFs proposals

2017-06-08 Thread Zhou, Danny 
Before we answer the questions who is going to support the open source VNFs, we 
might need to figure out whether those VNFs can really support a complete vCPE 
use case. For vDHCP, vDNS and vAAT which have relatively simple and fixed 
simple functionalities, it is easy to package them as VNFs or containerized 
VNFs, but for the vBRG, vBNG, vGW there are lots of complicated 
features/functionalities are involved which need the vCPE use case to 
specifically list the required features in first release then volunteers could 
figure out the technical gaps of existing open source VNFs and then provide 
meaningful estimation about how much additional development work as well as 
integration work needed.

From: ROSE, DANIEL V [mailto:dr6...@att.com]
Sent: Thursday, June 1, 2017 10:35 PM
To: SULLIVAN, BRYAN L <bs3...@att.com>; SPATSCHECK, OLIVER 
<spat...@research.att.com>; Zhou, Danny <danny.z...@intel.com>
Cc: onap-discuss <onap-disc...@lists.onap.org>; onap-tsc@lists.onap.org
Subject: RE: [onap-tsc] Call for vCPE VNFs proposals

Viability to even be included is certainly an important point.

But I think oliver’s point is there is always some work to get a vnf to be onap 
ready, and then some more work to configure it to work in our use case. Someone 
in the ONAP project has to take ownership and agree to either do that work, or 
find someone (possibly the projects actual contributors) to do that work.  This 
is analogous to a vendor who agrees to support their vnf in the use cases we 
use them for.

Thanks,
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of SULLIVAN, BRYAN L
Sent: Thursday, June 01, 2017 10:31 AM
To: SPATSCHECK, OLIVER 
<spat...@research.att.com<mailto:spat...@research.att.com>>; Zhou, Danny 
<danny.z...@intel.com<mailto:danny.z...@intel.com>>
Cc: onap-discuss 
<onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: Re: [onap-discuss] [onap-tsc] Call for vCPE VNFs proposals

***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Having support info in the table of open source VNFs, as well as notes on 
functional limitations / fitness for a particular purpose, and some consensus 
assessment [limited, viable] or status [experimental, lab-ready, deployed] that 
can change over time, would be useful. There are various types/levels of 
purpose here, and for the community’s need, functionally complete / 
production-ready open source VNFs while clearly a desired goal, are a 
would-be-nice.

Viability would include the level of community support for maintaining or 
further developing the VNF. But some VNFs may be still be viable for particular 
purposes (e.g. in tests for performance or lifecycle automation) even if they 
are incomplete or there is no active community.

Thanks,
Bryan Sullivan | AT

From: SPATSCHECK, OLIVER
Sent: Thursday, June 01, 2017 6:07 AM
To: Zhou, Danny <danny.z...@intel.com<mailto:danny.z...@intel.com>>
Cc: SULLIVAN, BRYAN L <bs3...@att.com<mailto:bs3...@att.com>>; KLUGER, YOAV 
<yoav.klu...@amdocs.com<mailto:yoav.klu...@amdocs.com>>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; onap-discuss 
<onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>>
Subject: Re: [onap-tsc] Call for vCPE VNFs proposals


Could we also start listing who is supporting the open source VNFs? E.g. even 
the simple open source based VNFs we are using for the current ONAP demo  based 
on the seed code took a couple of people 2 months or so to get to work properly 
in the integration environment. I would assume that for commercial VNFs this 
support will be provided by the vendor. However, for open source VNFs we need 
volunteers to take on that role. I would track those on the Wiki or identify 
them as gaps. If we can’t find that support we can’t use that VNF.

Thx

Oliver

On May 31, 2017, at 11:36 PM, Zhou, Danny 
<danny.z...@intel.com<mailto:danny.z...@intel.com>> wrote:

The wiki 
page<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Use-2BCase-253A-2BResidential-2BBroadband-2BvCPE=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=2-FskNSRL5sc9nQutgafCDIk3JbYrtcUwMwT5Zs1Tnk=Y6oSqusd5waa24F38QbqX5Q7z4FxBvAQy3WAxeNdz2E=QPIvHP7_JFzDMiX8sdebViT7Y8GADNDb_lq2G0otif0=>
 already lists preferred and usable open source VNFs like below, but the ONOS 
vBNG as open source vBNG and OpenWRT as open source vHGW does not make sense to 
me. Specifically, the ONOS vBNG is essentially a L3 NAT without the 
capabilities to address requirement such as session management, traffic 
aggregation and routing, etc., and in addition to OpenWRT acting

Re: [onap-tsc] Call for vCPE VNFs proposals

2017-06-01 Thread ROSE, DANIEL V 
Viability to even be included is certainly an important point.

But I think oliver’s point is there is always some work to get a vnf to be onap 
ready, and then some more work to configure it to work in our use case. Someone 
in the ONAP project has to take ownership and agree to either do that work, or 
find someone (possibly the projects actual contributors) to do that work.  This 
is analogous to a vendor who agrees to support their vnf in the use cases we 
use them for.

Thanks,
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of SULLIVAN, BRYAN L
Sent: Thursday, June 01, 2017 10:31 AM
To: SPATSCHECK, OLIVER <spat...@research.att.com>; Zhou, Danny 
<danny.z...@intel.com>
Cc: onap-discuss <onap-disc...@lists.onap.org>; onap-tsc@lists.onap.org
Subject: Re: [onap-discuss] [onap-tsc] Call for vCPE VNFs proposals

***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Having support info in the table of open source VNFs, as well as notes on 
functional limitations / fitness for a particular purpose, and some consensus 
assessment [limited, viable] or status [experimental, lab-ready, deployed] that 
can change over time, would be useful. There are various types/levels of 
purpose here, and for the community’s need, functionally complete / 
production-ready open source VNFs while clearly a desired goal, are a 
would-be-nice.

Viability would include the level of community support for maintaining or 
further developing the VNF. But some VNFs may be still be viable for particular 
purposes (e.g. in tests for performance or lifecycle automation) even if they 
are incomplete or there is no active community.

Thanks,
Bryan Sullivan | AT

From: SPATSCHECK, OLIVER
Sent: Thursday, June 01, 2017 6:07 AM
To: Zhou, Danny <danny.z...@intel.com<mailto:danny.z...@intel.com>>
Cc: SULLIVAN, BRYAN L <bs3...@att.com<mailto:bs3...@att.com>>; KLUGER, YOAV 
<yoav.klu...@amdocs.com<mailto:yoav.klu...@amdocs.com>>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; onap-discuss 
<onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>>
Subject: Re: [onap-tsc] Call for vCPE VNFs proposals


Could we also start listing who is supporting the open source VNFs? E.g. even 
the simple open source based VNFs we are using for the current ONAP demo  based 
on the seed code took a couple of people 2 months or so to get to work properly 
in the integration environment. I would assume that for commercial VNFs this 
support will be provided by the vendor. However, for open source VNFs we need 
volunteers to take on that role. I would track those on the Wiki or identify 
them as gaps. If we can’t find that support we can’t use that VNF.

Thx

Oliver

On May 31, 2017, at 11:36 PM, Zhou, Danny 
<danny.z...@intel.com<mailto:danny.z...@intel.com>> wrote:

The wiki 
page<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Use-2BCase-253A-2BResidential-2BBroadband-2BvCPE=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=2-FskNSRL5sc9nQutgafCDIk3JbYrtcUwMwT5Zs1Tnk=Y6oSqusd5waa24F38QbqX5Q7z4FxBvAQy3WAxeNdz2E=QPIvHP7_JFzDMiX8sdebViT7Y8GADNDb_lq2G0otif0=>
 already lists preferred and usable open source VNFs like below, but the ONOS 
vBNG as open source vBNG and OpenWRT as open source vHGW does not make sense to 
me. Specifically, the ONOS vBNG is essentially a L3 NAT without the 
capabilities to address requirement such as session management, traffic 
aggregation and routing, etc., and in addition to OpenWRT acting as vHGW, VPP 
based high performance Home 
Gateway<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.fd.io_view_VPP_VPP-5FHome-5FGateway=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4=S8WnofRTLquCoooSWMs6VppfiPsKgSASeuqb2NassTM=nZY_T4pjVyyFucKeg0ijm68LJm5NaaF46RQY48VPSQM=>
 as well 
asvRouter<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.fd.io_view_VPP-5FSandbox_router=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4=S8WnofRTLquCoooSWMs6VppfiPsKgSASeuqb2NassTM=MPD8ZLXRaBDF8Nx2xexNTaR8uFKEDBJqPAABHk4TcAU=>
 should be better.

  *   vDHCP: ISC DHCP
  *   vDNS:   ISC Bind
  *   vAAA:   FreeRADIUS

-Danny Zhou
Intel

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of SULLIVAN, BRYAN L
Sent: Thursday, June 1, 2017 3:36 AM
To: KLUGER, YOAV <yoav.klu...@amdocs.com<mailto:yoav.klu...@amdocs.com>>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; onap-discuss 
<onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>>
Subject: Re: [onap-tsc] Call for vCPE VNFs proposals

I recommend that any available open source implementations of these VNFs

Re: [onap-tsc] Call for vCPE VNFs proposals

2017-06-01 Thread SPATSCHECK, OLIVER (OLIVER) 

Could we also start listing who is supporting the open source VNFs? E.g. even 
the simple open source based VNFs we are using for the current ONAP demo  based 
on the seed code took a couple of people 2 months or so to get to work properly 
in the integration environment. I would assume that for commercial VNFs this 
support will be provided by the vendor. However, for open source VNFs we need 
volunteers to take on that role. I would track those on the Wiki or identify 
them as gaps. If we can’t find that support we can’t use that VNF.

Thx

Oliver

On May 31, 2017, at 11:36 PM, Zhou, Danny 
<danny.z...@intel.com<mailto:danny.z...@intel.com>> wrote:

The wiki 
page<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Use-2BCase-253A-2BResidential-2BBroadband-2BvCPE=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=2-FskNSRL5sc9nQutgafCDIk3JbYrtcUwMwT5Zs1Tnk=Y6oSqusd5waa24F38QbqX5Q7z4FxBvAQy3WAxeNdz2E=QPIvHP7_JFzDMiX8sdebViT7Y8GADNDb_lq2G0otif0=>
 already lists preferred and usable open source VNFs like below, but the ONOS 
vBNG as open source vBNG and OpenWRT as open source vHGW does not make sense to 
me. Specifically, the ONOS vBNG is essentially a L3 NAT without the 
capabilities to address requirement such as session management, traffic 
aggregation and routing, etc., and in addition to OpenWRT acting as vHGW, VPP 
based high performance Home 
Gateway<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.fd.io_view_VPP_VPP-5FHome-5FGateway=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4=S8WnofRTLquCoooSWMs6VppfiPsKgSASeuqb2NassTM=nZY_T4pjVyyFucKeg0ijm68LJm5NaaF46RQY48VPSQM=>
 as well 
asvRouter<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.fd.io_view_VPP-5FSandbox_router=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4=S8WnofRTLquCoooSWMs6VppfiPsKgSASeuqb2NassTM=MPD8ZLXRaBDF8Nx2xexNTaR8uFKEDBJqPAABHk4TcAU=>
 should be better.

  *   vDHCP: ISC DHCP
  *   vDNS:   ISC Bind
  *   vAAA:   FreeRADIUS


-Danny Zhou
Intel

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of SULLIVAN, BRYAN L
Sent: Thursday, June 1, 2017 3:36 AM
To: KLUGER, YOAV <yoav.klu...@amdocs.com<mailto:yoav.klu...@amdocs.com>>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; onap-discuss 
<onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>>
Subject: Re: [onap-tsc] Call for vCPE VNFs proposals

I recommend that any available open source implementations of these VNFs also 
be included. I am aware of several potential VNFs as used in the R-CORD 
project, and as being collected through the similar ODL VCO (Virtualized 
Central Office) project. These are being collected and assessed for deployment 
on OPNFV reference platforms as part of the proposed “Edge” project: 
https://wiki.opnfv.org/display/PROJ/Multi-Access+Edge<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_display_PROJ_Multi-2DAccess-2BEdge=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4=S8WnofRTLquCoooSWMs6VppfiPsKgSASeuqb2NassTM=pMPlFX7WiLZPIsWgpgL_uX8D9TNoYhXk3zlKzR_Wbsw=>
 intended to expand reference VNF options for edge-focused service deployments 
such as residential broadband. As a part of this project we will also be 
building reference blueprints (TOSCA based) for these VNFs and orchestrating 
them using ONAP components as well as other projects we are currently using for 
this in OPNFV (Cloudify, and OpenStack Tacker).

OPNFV is acquiring the necessary hardware (e.g. OLT devices) to have a 
fully-functional edge-focused lab environment in which to complete this 
integration. I’ll add the related info to the ONAP wiki as the usability of the 
open source VNFs becomes clear.

Thanks,
Bryan Sullivan | AT

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of KLUGER, YOAV
Sent: Wednesday, May 31, 2017 12:23 PM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; onap-discuss 
<onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>>
Subject: [onap-discuss] Call for vCPE VNFs proposals

Dear ONAP community,

As we all know, the Residential Broadband vCPE use case is one of our two 
targeted use cases for R1.
Its wiki 
page<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Use-2BCase-253A-2BResidential-2BBroadband-2BvCPE=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=2-FskNSRL5sc9nQutgafCDIk3JbYrtcUwMwT5Zs1Tnk=Y6oSqusd5waa24F38QbqX5Q7z4FxBvAQy3WAxeNdz2E=QPIvHP7_JFzDMiX8sdebViT7Y8GADNDb_lq2G0otif0=>
 has been significantly enriched recently, and more details are added on a 
daily basis.
A general residential broadband solution can be much more complex than what 
would be reasonably achievable by R1. We have narrowed down the descrip

Re: [onap-tsc] Call for vCPE VNFs proposals

2017-05-31 Thread Zhou, Danny 
The wiki 
page<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Use-2BCase-253A-2BResidential-2BBroadband-2BvCPE=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=2-FskNSRL5sc9nQutgafCDIk3JbYrtcUwMwT5Zs1Tnk=Y6oSqusd5waa24F38QbqX5Q7z4FxBvAQy3WAxeNdz2E=QPIvHP7_JFzDMiX8sdebViT7Y8GADNDb_lq2G0otif0=>
 already lists preferred and usable open source VNFs like below, but the ONOS 
vBNG as open source vBNG and OpenWRT as open source vHGW does not make sense to 
me. Specifically, the ONOS vBNG is essentially a L3 NAT without the 
capabilities to address requirement such as session management, traffic 
aggregation and routing, etc., and in addition to OpenWRT acting as vHGW, VPP 
based high performance Home 
Gateway<https://wiki.fd.io/view/VPP/VPP_Home_Gateway> as well as 
vRouter<https://wiki.fd.io/view/VPP_Sandbox/router> should be better.

  *   vDHCP: ISC DHCP
  *   vDNS:   ISC Bind
  *   vAAA:   FreeRADIUS

-Danny Zhou
Intel

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of SULLIVAN, BRYAN L
Sent: Thursday, June 1, 2017 3:36 AM
To: KLUGER, YOAV <yoav.klu...@amdocs.com>; onap-tsc@lists.onap.org; 
onap-discuss <onap-disc...@lists.onap.org>
Subject: Re: [onap-tsc] Call for vCPE VNFs proposals

I recommend that any available open source implementations of these VNFs also 
be included. I am aware of several potential VNFs as used in the R-CORD 
project, and as being collected through the similar ODL VCO (Virtualized 
Central Office) project. These are being collected and assessed for deployment 
on OPNFV reference platforms as part of the proposed "Edge" project: 
https://wiki.opnfv.org/display/PROJ/Multi-Access+Edge intended to expand 
reference VNF options for edge-focused service deployments such as residential 
broadband. As a part of this project we will also be building reference 
blueprints (TOSCA based) for these VNFs and orchestrating them using ONAP 
components as well as other projects we are currently using for this in OPNFV 
(Cloudify, and OpenStack Tacker).

OPNFV is acquiring the necessary hardware (e.g. OLT devices) to have a 
fully-functional edge-focused lab environment in which to complete this 
integration. I'll add the related info to the ONAP wiki as the usability of the 
open source VNFs becomes clear.

Thanks,
Bryan Sullivan | AT

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of KLUGER, YOAV
Sent: Wednesday, May 31, 2017 12:23 PM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; onap-discuss 
<onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>>
Subject: [onap-discuss] Call for vCPE VNFs proposals

Dear ONAP community,

As we all know, the Residential Broadband vCPE use case is one of our two 
targeted use cases for R1.
Its wiki 
page<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Use-2BCase-253A-2BResidential-2BBroadband-2BvCPE=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=2-FskNSRL5sc9nQutgafCDIk3JbYrtcUwMwT5Zs1Tnk=Y6oSqusd5waa24F38QbqX5Q7z4FxBvAQy3WAxeNdz2E=QPIvHP7_JFzDMiX8sdebViT7Y8GADNDb_lq2G0otif0=>
 has been significantly enriched recently, and more details are added on a 
daily basis.
A general residential broadband solution can be much more complex than what 
would be reasonably achievable by R1. We have narrowed down the description of 
the use case for R1, to something that should be both achievable and usable.
For the use case to work the following VNFs will be needed:

  *   vBNG
  *   vHGW
  *   vDHCP
  *   vDNS
  *   vAAA


In addition a simple hardware box with 802.1ad capabilities will be needed.

This is a call for vendors of such VNFs and/or such a box to join the activity. 
Would be great if by Beijing time the wiki will have at least one vendor name 
alongside every VNF, and also at least one vendor for the box.

Thanks,
Yoav Kluger
Amdocs Technology
+1(201)912-7294
+972-54-4850278
[amdocs-a]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at 
https://www.amdocs.com/about/email-disclaimer<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=2-FskNSRL5sc9nQutgafCDIk3JbYrtcUwMwT5Zs1Tnk=Y6oSqusd5waa24F38QbqX5Q7z4FxBvAQy3WAxeNdz2E=4DsjLuum5-WDdGQllWAreUo_BzbuxLSg0nGK7t4a7Ls=>
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Call for vCPE VNFs proposals

2017-05-31 Thread SULLIVAN, BRYAN L 
I recommend that any available open source implementations of these VNFs also 
be included. I am aware of several potential VNFs as used in the R-CORD 
project, and as being collected through the similar ODL VCO (Virtualized 
Central Office) project. These are being collected and assessed for deployment 
on OPNFV reference platforms as part of the proposed "Edge" project: 
https://wiki.opnfv.org/display/PROJ/Multi-Access+Edge intended to expand 
reference VNF options for edge-focused service deployments such as residential 
broadband. As a part of this project we will also be building reference 
blueprints (TOSCA based) for these VNFs and orchestrating them using ONAP 
components as well as other projects we are currently using for this in OPNFV 
(Cloudify, and OpenStack Tacker).

OPNFV is acquiring the necessary hardware (e.g. OLT devices) to have a 
fully-functional edge-focused lab environment in which to complete this 
integration. I'll add the related info to the ONAP wiki as the usability of the 
open source VNFs becomes clear.

Thanks,
Bryan Sullivan | AT

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of KLUGER, YOAV
Sent: Wednesday, May 31, 2017 12:23 PM
To: onap-tsc@lists.onap.org; onap-discuss 
Subject: [onap-discuss] Call for vCPE VNFs proposals

Dear ONAP community,

As we all know, the Residential Broadband vCPE use case is one of our two 
targeted use cases for R1.
Its wiki 
page
 has been significantly enriched recently, and more details are added on a 
daily basis.
A general residential broadband solution can be much more complex than what 
would be reasonably achievable by R1. We have narrowed down the description of 
the use case for R1, to something that should be both achievable and usable.
For the use case to work the following VNFs will be needed:

  *   vBNG
  *   vHGW
  *   vDHCP
  *   vDNS
  *   vAAA


In addition a simple hardware box with 802.1ad capabilities will be needed.

This is a call for vendors of such VNFs and/or such a box to join the activity. 
Would be great if by Beijing time the wiki will have at least one vendor name 
alongside every VNF, and also at least one vendor for the box.

Thanks,
Yoav Kluger
Amdocs Technology
+1(201)912-7294
+972-54-4850278
[amdocs-a]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at 
https://www.amdocs.com/about/email-disclaimer
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc