com>; TIMONEY, DAN <dt5...@att.com>;
seshu.kuma...@huawei.com; KAPELUTO, ZAHI <zk0...@intl.att.com>;
onap-disc...@lists.onap.org; ROZIN, EDEN <er4...@intl.att.com>;
onap-tsc@lists.onap.org
Subject: RE: Re: [onap-tsc]答复: Re: ONAP VoLTE SDC call
The adaptor should define its
<bf1...@att.com>
Cc: SHADMI, DAVID <ds2...@att.com>; TIMONEY, DAN <dt5...@att.com>;
seshu.kuma...@huawei.com; KAPELUTO, ZAHI <zk0...@intl.att.com>;
onap-disc...@lists.onap.org; ROZIN, EDEN <er4...@intl.att.com>;
onap-tsc@lists.onap.org
Subject: 答复: Re: [onap-tsc]答复
: Monday, August 07, 2017 7:12 AM
To: SHADMI, DAVID <ds2...@att.com>; TIMONEY, DAN <dt5...@att.com>;
seshu.kuma...@huawei.com
Cc: onap-disc...@lists.onap.org; KAPELUTO, ZAHI <zk0...@intl.att.com>; ROZIN,
EDEN <er4...@intl.att.com>; onap-tsc@lists.onap.org
Subject: [onap-tsc
There are some issues about how WAN service descriptor works with SO and SDN-C
might need to be clarified. I suggest should we have a discussion on Monday
8:00 PM UTC on these issues first? If this time is not suitable for everyone,
please choose a better time for discussion.
Thank you all!
Hi, David, Dan and seshu
Some questions about how WAN service descriptor works with SO and SDN-C:
How does SDN-C import the YANG file describing NBI of 3rd controller? By Json
from SO? Or be placed manually according to specific apdator? Or by other ways?
What kind of infomation should
Congratulations! Great progress for ONAP R1.
@David: SO, SDNC, SDC team and WAN provider of Volte usecase(ZTE and CMCC)
might have further work on defining of WAN service descriptor which is not as
clear as NS descriptor.
@Zhuoyao Huang: please prepare and arrange discussion with related
