Re: [onap-tsc] [Onap-arc] ONAP Architecture presentation

2017-11-22 Thread Vladimir Yanover (vyanover)
+N
where N is the number of people in Cisco that keep asking me where the last 
approved version of the documentation can be found and what is the process in 
the ONAP documentation (submission - discussion - approval - implementation in 
the code / documentation?). They don't understand why ONAP is not working (even 
does not have timeline) on delivery of specifications to reach the level of the 
Linux Standard Base (ISO/IEC 23360-1) or ODL.
I understand difficulties of starting a new organization and appreciate people 
that worked hard to deliver the R1. The question is whether for R2 some level 
of maturity can be reached. To make it happen, we need to work on it.
Besides, clear procedure is absolutely necessary element of transparency.

Thanks
Vladimir

From: onap-arc-boun...@lists.onap.org [mailto:onap-arc-boun...@lists.onap.org] 
On Behalf Of Sabater, Susana, Vodafone Spain
Sent: Tuesday, November 21, 2017 11:47 PM
To: Alla Goldner ; Pasi Vaananen 
; Stephen Terrill ; 
onap-...@lists.onap.org; onap-tsc@lists.onap.org
Subject: Re: [Onap-arc] ONAP Architecture presentation

+1
Regards
/Susana

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Tuesday, November 21, 2017 6:32 PM
To: Pasi Vaananen >; Stephen 
Terrill >; 
onap-...@lists.onap.org; 
onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] [Onap-arc] ONAP Architecture presentation

+1 and including TSC list for a broader discussion of this issue.

One of the problems we face is that there are multiple locations where 
presentations are uploaded (f uploaded), e.g. under Usecase or Architecture 
subcommittee, in a dedicated project area etc.

In my view, the best way to support visibility of all submitted documents is to 
have a single placeholder as done by a different SDO e.g. 3GPP, ETSI NFV - and 
then it may be further distinguished there by subject, submitter, targeted 
subcommittee/project etc.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D36388.86E65360]

From: onap-arc-boun...@lists.onap.org 
[mailto:onap-arc-boun...@lists.onap.org] On Behalf Of Pasi Vaananen
Sent: Tuesday, November 21, 2017 7:06 PM
To: Stephen Terrill 
>; 
onap-...@lists.onap.org
Subject: Re: [Onap-arc] ONAP Architecture presentation


+1

... but this should not be limited only to architecture team presentations.

Pasi

On 11/21/2017 12:00 PM, Stephen Terrill wrote:
Hi Chris,

Can I make a suggestion regarding the presentations in the ONAP Architecture 
team. Sometimes the presentation cannot be found afterwards.  I think it's a 
common practice in a few foras that the documentation has to be uploaded before 
being presented, can we assume the same practice here ?

BR,

Steve


[Ericsson]


STEPHEN TERRILL
Technology Specialist
DUIC, Systems and Technology
Development Unit IP & Cloud
Business Unit, IT & Cloud Products

Ericsson
Ericsson R Center, via de los Poblados 13
28033, Madrid, Spain
Phone +34 339 3005
Mobile +34 609 168 515
stephen.terr...@ericsson.com
www.ericsson.com


[http://www.ericsson.com/current_campaign]

Legal entity: Ericsson España S.A, compay registration number ESA288568603. 
This Communication is Confidential. We only send and receive email on the basis 
of the terms set out at 
www.ericsson.com/email_disclaimer





___

Onap-arc mailing list

onap-...@lists.onap.org

https://lists.onap.org/mailman/listinfo/onap-arc

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


Re: [onap-tsc] ona-user mailing list?

2017-11-22 Thread Lingli Deng
+1

 

Lingli

 

From: onap-tsc-boun...@lists.onap.org
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Dhananjay Pavgi
Sent: 2017年11月22日 16:20
To: Kanagaraj Manickam ; onap-...@lists.onap.
org
Subject: Re: [onap-tsc] ona-user mailing list?

 

Good idea, Kanagaraj. +1. 

 

thanks & regards,

Dhananjay Pavgi

+91 98220 22264

 

From: onap-tsc-boun...@lists.onap.org

[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Kanagaraj Manickam
Sent: Wednesday, November 22, 2017 1:48 PM
To: onap-tsc@lists.onap.org  
Subject: [onap-tsc] ona-user mailing list?

 

Dear TSC team,

 

When user starts to use the ONAP Amsterdam version and they would need an
forum to discuss among the user communities to discuss about ONAP usage
related issues. So, shall we create new mailing list ‘onap-user’, to
address it?  

This would be similar to onap-discuss, used by developers community.

 

Thank you.

 

Regards

Kanagaraj M

 


***
本邮件及其附件含有华为公司的保密信息,仅限于发送给上面地址中列出的个人或群
组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散
发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本
邮件!

**


***
This e-mail and its attachments contain confidential information from
HUAWEI, which is intended only for the person  or entity whose address is
listed above. Any use of the information contained herein in any way
(including, but not   limited to, total or partial disclosure, reproduction,
or dissemination) by persons other than the intended recipient(s) is
prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!

***

 




Disclaimer:  This message and the information contained herein is
proprietary and confidential and subject to the Tech Mahindra policy
statement, you may review the policy at
http://www.techmahindra.com/Disclaimer.html externally
http://tim.techmahindra.com/tim/disclaimer.html internally within
TechMahindra.




___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc


Re: [onap-tsc] Usecase subcommittee 20/11/2017 meeting - the summary

2017-11-22 Thread BEGWANI, VIMAL
Hello All,
  5G use case requirements can be found at the following links.  Please feel to 
send your comments to us.

5G Use Case Summary:
https://wiki.onap.org/pages/viewpage.action?pageId=15992173
5G Subcases with illustration:
https://wiki.onap.org/pages/viewpage.action?pageId=15992187
https://wiki.onap.org/pages/viewpage.action?pageId=15992190
https://wiki.onap.org/pages/viewpage.action?pageId=15992192
https://wiki.onap.org/pages/viewpage.action?pageId=15992204
Summary of Functional Requirements arising from use case:
https://wiki.onap.org/display/DW/Summary+of+Functional+Platform+Requirements+arising+from+5G+Use+Case

Regards,
Vimal


From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Alla Goldner
Sent: Wednesday, November 22, 2017 12:50 PM
To: onap-usecase...@lists.onap.org; onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Usecase subcommittee 20/11/2017 meeting - the summary

Hi again,

I would like to remind about the AI from the summary below:

. General: What is currently missing in the requirements 
definition. Yuan has expressed his view that VNFs/PNFs source/description is 
missing from the use case as well as expressed concern of lacking of 5G 
standard to start with 5G related requirements. We decided that:

i.  Each requirements group/task force leader (5G, Change 
Management, VoLTE remaining requirements, E-vCPE, VNF Scaling;  Centralized 
Parser Distribution and External Controller, once ready) will issue separate 
email to the whole list describing what has already been defined in a different 
places related to his/her use case/requirements with the corresponding links
ii. Community members will provide comments what is missing (if 
something is missing), target date is next Monday, 27/11/2017

Guys, we must have all requirements completed, otherwise we will not be able to 
approve them for Beijing Release. Please try to proceed with the (i) above ASAP.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D36394.748354F0]

From: Alla Goldner
Sent: Tuesday, November 21, 2017 11:42 AM
To: 'onap-usecase...@lists.onap.org' 
>; 
onap-tsc@lists.onap.org; 
onap-disc...@lists.onap.org
Cc: 'Kenny Paul' >
Subject: Usecase subcommittee 20/11/2017 meeting - the summary

Hi all,

Thanks to all meeting's participants!

Here is the summary:


  1.  Alla thanked all Usecase subcommittee members and Integration team 
members greatly contributed to the success of Amsterdam Release!!!

 2.   R2 requirements
a.E-vCPE requirements were presented by Luman. This will follow by 
email discussion which Luman will initiate ASAP, describing the problem the 
requirements are resolving, and high level description, in addition to the 
presentation.

b.Centralized Parsers Distribution requirements were presented by  
Atul. Some questions were raised. The next step is to include the requirements 
into merged requirements table, including all needed information and also 
present it to Architecture subcommittee

c. General: What is currently missing in the requirements 
definition. Yuan has expressed his view that VNFs/PNFs source/description is 
missing from the use case as well as expressed concern of lacking of 5G 
standard to start with 5G related requirements. We decided that:


i.Each requirements group/task force leader (5G, Change 
Management, VoLTE remaining requirements, E-vCPE, VNF Scaling;  Centralized 
Parser Distribution and External Controller, once ready) will issue separate 
email to the whole list describing what has already been defined in a different 
places related to his/her use case/requirements with the corresponding links

ii.   Community members will provide comments what is missing 
(if something is missing), target date is next Monday, 27/11/2017

d.VNF Scaling - next level of details - this task force 
representatives didn't attend the call. Steve/team - please also issue email as 
described above for the VNF scaling related requirements to see if ONAP 
community is satisfied with the level of definition

e.External Controller - status of the discussions (Ramesh). There 
was no progress on the related discussions. Ramesh will update us next week on 
the progress achieved by then


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D36394.748354F0]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at 

Re: [onap-tsc] Usecase subcommittee 20/11/2017 meeting - the summary

2017-11-22 Thread Alla Goldner
Hi again,

I would like to remind about the AI from the summary below:

. General: What is currently missing in the requirements 
definition. Yuan has expressed his view that VNFs/PNFs source/description is 
missing from the use case as well as expressed concern of lacking of 5G 
standard to start with 5G related requirements. We decided that:

i.  Each requirements group/task force leader (5G, Change 
Management, VoLTE remaining requirements, E-vCPE, VNF Scaling;  Centralized 
Parser Distribution and External Controller, once ready) will issue separate 
email to the whole list describing what has already been defined in a different 
places related to his/her use case/requirements with the corresponding links
ii. Community members will provide comments what is missing (if 
something is missing), target date is next Monday, 27/11/2017

Guys, we must have all requirements completed, otherwise we will not be able to 
approve them for Beijing Release. Please try to proceed with the (i) above ASAP.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D363CB.225BD170]

From: Alla Goldner
Sent: Tuesday, November 21, 2017 11:42 AM
To: 'onap-usecase...@lists.onap.org' ; 
onap-tsc@lists.onap.org; onap-disc...@lists.onap.org
Cc: 'Kenny Paul' 
Subject: Usecase subcommittee 20/11/2017 meeting - the summary

Hi all,

Thanks to all meeting's participants!

Here is the summary:


1.   Alla thanked all Usecase subcommittee members and Integration team 
members greatly contributed to the success of Amsterdam Release!!!

 2.   R2 requirements
a.E-vCPE requirements were presented by Luman. This will follow by 
email discussion which Luman will initiate ASAP, describing the problem the 
requirements are resolving, and high level description, in addition to the 
presentation.

b.Centralized Parsers Distribution requirements were presented by  
Atul. Some questions were raised. The next step is to include the requirements 
into merged requirements table, including all needed information and also 
present it to Architecture subcommittee

c. General: What is currently missing in the requirements 
definition. Yuan has expressed his view that VNFs/PNFs source/description is 
missing from the use case as well as expressed concern of lacking of 5G 
standard to start with 5G related requirements. We decided that:


i.Each requirements group/task force leader (5G, Change 
Management, VoLTE remaining requirements, E-vCPE, VNF Scaling;  Centralized 
Parser Distribution and External Controller, once ready) will issue separate 
email to the whole list describing what has already been defined in a different 
places related to his/her use case/requirements with the corresponding links

ii.  Community members will provide comments what is missing 
(if something is missing), target date is next Monday, 27/11/2017

d.VNF Scaling - next level of details - this task force 
representatives didn't attend the call. Steve/team - please also issue email as 
described above for the VNF scaling related requirements to see if ONAP 
community is satisfied with the level of definition

e.External Controller - status of the discussions (Ramesh). There 
was no progress on the related discussions. Ramesh will update us next week on 
the progress achieved by then


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D363CB.225BD170]

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


[onap-tsc] 答复: Re: [Onap-arc] ONAP Architecture presentation

2017-11-22 Thread zhang.maopeng1
Hi Chris


   


 The work is done. The project proposel can be gotten in the following wiki 
pages:


  https://wiki.onap.org/display/DW/Run-Time+Catalog


  https://wiki.onap.org/display/DW/November+21


  https://wiki.onap.org/display/DW/Contributions










BR


Maopeng



原始邮件




发件人: ;
收件人: ; ; 
; ; 
; ;
日 期 :2017年11月22日 04:14
主 题 :Re: [onap-tsc] [Onap-arc] ONAP Architecture presentation








It’s available under the Architecture Subcommittee page on the wiki (with 
recording):


https://wiki.onap.org/display/DW/November+21


 


Some of the slides have already been uploaded, but I received two last-minute 
requests for slots and I haven’t seen those slides yet.  LiZi and Maopeng, 
would you please upload them to the Contributions page? 
https://wiki.onap.org/display/DW/Contributions


 


 


Chris


 



From: onap-arc-boun...@lists.onap.org [mailto:onap-arc-boun...@lists.onap.org] 
On Behalf Of jamil.cha...@orange.com
 Sent: Tuesday, November 21, 2017 9:40 AM
 To: Alla Goldner ; Pasi Vaananen 
; Stephen Terrill ; 
onap-...@lists.onap.org; onap-tsc@lists.onap.org
 Subject: Re: [Onap-arc] ONAP Architecture presentation




 


+1


And also a short summary of the meeting 


Best 


Jamil


 



De : onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
De la part de Alla Goldner
 Envoyé : mardi 21 novembre 2017 18:32
 À : Pasi Vaananen; Stephen Terrill; onap-...@lists.onap.org; 
onap-tsc@lists.onap.org
 Objet : Re: [onap-tsc] [Onap-arc] ONAP Architecture presentation




 


+1 and including TSC list for a broader discussion of this issue.


 


One of the problems we face is that there are multiple locations where 
presentations are uploaded (f uploaded), e.g. under Usecase or Architecture 
subcommittee, in a dedicated project area etc. 


 


In my view, the best way to support visibility of all submitted documents is to 
have a single placeholder as done by a different SDO e.g. 3GPP, ETSI NFV – and 
then it may be further distinguished there by subject,  submitter, targeted 
subcommittee/project etc.


 


Best regards, 


 


Alla Goldner


 


Open Network Division 


Amdocs Technology


 


 






 



From: onap-arc-boun...@lists.onap.org [mailto:onap-arc-boun...@lists.onap.org] 
On Behalf Of Pasi Vaananen
 Sent: Tuesday, November 21, 2017 7:06 PM
 To: Stephen Terrill ; onap-...@lists.onap.org
 Subject: Re: [Onap-arc] ONAP Architecture presentation




 

+1 

... but this should not be limited only to architecture team presentations.

Pasi


 


On 11/21/2017 12:00 PM, Stephen Terrill wrote:



Hi Chris,


 


Can I make a suggestion regarding the presentations in the ONAP Architecture 
team. Sometimes the presentation cannot be found afterwards.  I think it’s a 
common practice in a few  foras that the documentation has to be uploaded 
before being presented, can we assume the same practice here ?


 


BR,


 


Steve


 


 



 
 
 


STEPHEN TERRILL 
 Technology Specialist 
 DUIC, Systems and Technology 
 Development Unit IP & Cloud


Business Unit, IT & Cloud Products



 Ericsson
 Ericsson R Center, via de los Poblados 13
 28033, Madrid, Spain
 Phone +34 339 3005
 Mobile +34 609 168 515
 stephen.terr...@ericsson.com
 www.ericsson.com 



 
 


 


Legal entity: Ericsson España S.A, compay registration number ESA288568603. 
This Communication is Confidential. We only send and receive email on the basis 
of the  terms set out at www.ericsson.com/email_disclaimer 


 



 
 
 

___ Onap-arc mailing list 
onap-...@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-arc 
 


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



_
   Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites 
ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez 
le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les 
messages electroniques etant susceptibles d'alteration, Orange decline toute 
responsabilite si ce message a ete altere, deforme ou falsifie. Merci.   This 
message and its attachments may contain confidential or privileged information 
that may be protected by law; they should not be distributed, used or copied 
without authorisation. If you have received this email in error, please notify 
the sender and delete this message 

Re: [onap-tsc] ona-user mailing list?

2017-11-22 Thread Dhananjay Pavgi
Good idea, Kanagaraj. +1.

thanks & regards,
Dhananjay Pavgi
+91 98220 22264

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Kanagaraj Manickam
Sent: Wednesday, November 22, 2017 1:48 PM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] ona-user mailing list?

Dear TSC team,

When user starts to use the ONAP Amsterdam version and they would need an forum 
to discuss among the user communities to discuss about ONAP usage related 
issues. So, shall we create new mailing list ‘onap-user’, to address it?
This would be similar to onap-discuss, used by developers community.

Thank you.

Regards
Kanagaraj M

***
本邮件及其附件含有华为公司的保密信息,仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本邮件!**

***
This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not   
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is  prohibited. If you receive 
this e-mail in error, please notify the sender by phone or email immediately 
and delete it!
***



Disclaimer:  This message and the information contained herein is proprietary 
and confidential and subject to the Tech Mahindra policy statement, you may 
review the policy at http://www.techmahindra.com/Disclaimer.html 
 externally 
http://tim.techmahindra.com/tim/disclaimer.html 
 internally within 
TechMahindra.


___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc


[onap-tsc] ona-user mailing list?

2017-11-22 Thread Kanagaraj Manickam
Dear TSC team,

When user starts to use the ONAP Amsterdam version and they would need an forum 
to discuss among the user communities to discuss about ONAP usage related 
issues. So, shall we create new mailing list ‘onap-user’, to address it?
This would be similar to onap-discuss, used by developers community.

Thank you.

Regards
Kanagaraj M

***
本邮件及其附件含有华为公司的保密信息,仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本邮件!**

***
This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not   
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is  prohibited. If you receive 
this e-mail in error, please notify the sender by phone or email immediately 
and delete it!
***

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc


[onap-tsc] 答复: Re: [Onap-arc] ONAP Architecture presentation

2017-11-22 Thread li.zi30
Done.






Regards,


LiZi















原始邮件



发件人: ;
收件人: ; ; 
; ; 
; ;
日 期 :2017年11月22日 04:15
主 题 :Re: [onap-tsc] [Onap-arc] ONAP Architecture presentation




It’s available under the Architecture Subcommittee page on the wiki (with 
recording):


https://wiki.onap.org/display/DW/November+21


 


Some of the slides have already been uploaded, but I received two last-minute 
requests for slots and I haven’t seen those slides yet.  LiZi and Maopeng, 
would you please upload them to the Contributions page? 
https://wiki.onap.org/display/DW/Contributions


 


 


Chris


 



From: onap-arc-boun...@lists.onap.org [mailto:onap-arc-boun...@lists.onap.org] 
On Behalf Of jamil.cha...@orange.com
 Sent: Tuesday, November 21, 2017 9:40 AM
 To: Alla Goldner ; Pasi Vaananen 
; Stephen Terrill ; 
onap-...@lists.onap.org; onap-tsc@lists.onap.org
 Subject: Re: [Onap-arc] ONAP Architecture presentation




 


+1


And also a short summary of the meeting 


Best 


Jamil


 



De : onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
De la part de Alla Goldner
 Envoyé : mardi 21 novembre 2017 18:32
 À : Pasi Vaananen; Stephen Terrill; onap-...@lists.onap.org; 
onap-tsc@lists.onap.org
 Objet : Re: [onap-tsc] [Onap-arc] ONAP Architecture presentation




 


+1 and including TSC list for a broader discussion of this issue.


 


One of the problems we face is that there are multiple locations where 
presentations are uploaded (f uploaded), e.g. under Usecase or Architecture 
subcommittee, in a dedicated project area etc. 


 


In my view, the best way to support visibility of all submitted documents is to 
have a single placeholder as done by a different SDO e.g. 3GPP, ETSI NFV – and 
then it may be further distinguished there by subject,  submitter, targeted 
subcommittee/project etc.


 


Best regards, 


 


Alla Goldner


 


Open Network Division 


Amdocs Technology


 


 






 



From: onap-arc-boun...@lists.onap.org [mailto:onap-arc-boun...@lists.onap.org] 
On Behalf Of Pasi Vaananen
 Sent: Tuesday, November 21, 2017 7:06 PM
 To: Stephen Terrill ; onap-...@lists.onap.org
 Subject: Re: [Onap-arc] ONAP Architecture presentation




 

+1 

... but this should not be limited only to architecture team presentations.

Pasi


 


On 11/21/2017 12:00 PM, Stephen Terrill wrote:



Hi Chris,


 


Can I make a suggestion regarding the presentations in the ONAP Architecture 
team. Sometimes the presentation cannot be found afterwards.  I think it’s a 
common practice in a few  foras that the documentation has to be uploaded 
before being presented, can we assume the same practice here ?


 


BR,


 


Steve


 


 



 
 
 


STEPHEN TERRILL 
 Technology Specialist 
 DUIC, Systems and Technology 
 Development Unit IP & Cloud


Business Unit, IT & Cloud Products



 Ericsson
 Ericsson R Center, via de los Poblados 13
 28033, Madrid, Spain
 Phone +34 339 3005
 Mobile +34 609 168 515
 stephen.terr...@ericsson.com
 www.ericsson.com 



 
 


 


Legal entity: Ericsson España S.A, compay registration number ESA288568603. 
This Communication is Confidential. We only send and receive email on the basis 
of the  terms set out at www.ericsson.com/email_disclaimer 


 



 
 
 

___ Onap-arc mailing list 
onap-...@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-arc 
 


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



_
   Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites 
ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez 
le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les 
messages electroniques etant susceptibles d'alteration, Orange decline toute 
responsabilite si ce message a ete altere, deforme ou falsifie. Merci.   This 
message and its attachments may contain confidential or privileged information 
that may be protected by law; they should not be distributed, used or copied 
without authorisation. If you have received this email in error, please notify 
the sender and delete this message and its attachments. As emails may be 
altered, Orange is not liable for messages that have been modified, changed or 
falsified. Thank you.___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org