Re: [onap-tsc] ETSI NFV API Conventions, wiki page, and more available [modeling]

Hi Thinh I have created a page for recommended SPECs from SDOs. https://wiki.onap.org/display/DW/Recommended+specs+from+SDOs Please help to fill in the spread sheet. If other SDOs also have such intention, please follow that page as well Thanks a lot DENG Hui From:

Re: [onap-tsc] TSC VOTE on Repos for AAI, AAF, Modeling & MSB

+1 All From: Kenny Paul Date: Friday, 28 July 2017 at 1:08 AM To: Xinhui Li Cc: onap-tsc Subject: Re: [onap-tsc] TSC VOTE on Repos for AAI, AAF, Modeling & MSB Hi Xinhui, please verify that your response was intended as a

Re: [onap-tsc] Leadership Diversity Language

I agree that this topic would be more appropriate as a TSC policy than as text in the Charter. Chris From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Stephen Terrill Sent: Tuesday, August 01, 2017 12:22 AM To: Kenny Paul ;

Re: [onap-tsc] TSC VOTE on Repos for AAI, AAF, Modeling & MSB

These new repositories are all still unapproved. At least one more person needs to confirm that their vote it was intended to be a “+1 ALL” before these can be approved. Thank you. Best Regards, -kenny Kenny Paul, Technical Program Manager kp...@linuxfoundation.org 510.766.5945 >> >>

Re: [onap-tsc] Migration to *.onap.org

Adding this to the Aug 3 agenda. Best Regards, -kenny Kenny Paul, Technical Program Manager kp...@linuxfoundation.org 510.766.5945 > On Aug 1, 2017, at 5:07 AM, Lefevre, Catherine wrote: > > Dear ONAP TSC, > > I fully understand the request about the seed code to be

Re: [onap-tsc] Migration to *.onap.org

Could we put that on the TSC agenda on Thu? Thx Oliver > On Aug 1, 2017, at 8:07 AM EDT, LEFEVRE, CATHERINE > wrote: > > ***Security Advisory: This Message Originated Outside of AT *** > Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. > >

[onap-tsc] ONAP VoLTE SDC call

BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:China Standard Time BEGIN:STANDARD DTSTART:16010101T00 TZOFFSETFROM:+0800 TZOFFSETTO:+0800 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T00 TZOFFSETFROM:+0800 TZOFFSETTO:+0800 END:DAYLIGHT

[onap-tsc] [SDC][MODELING][SO][VFC][SDNC][A][MULTIVIM]ONAP VoLTE SDC call on wednesday

Please help to forward it, thanks a lot DENG Hui BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 15.0 MIMEDIR//EN VERSION:2.0 METHOD:PUBLISH X-MS-OLK-FORCEINSPECTOROPEN:TRUE BEGIN:VTIMEZONE TZID:China Standard Time BEGIN:STANDARD DTSTART:16010101T00 TZOFFSETFROM:+0800

[onap-tsc] Migration to *.onap.org

Dear ONAP TSC, I fully understand the request about the seed code to be migrated to *.onap.org. Nevertheless I want to bring to your attention that this request will require significant effort (development, testing and infrastructure changes) ·Coordinate and update Maven dependencies

Re: [onap-tsc] Leadership Diversity Language

Hi, Thanks Kenny for assembling this text and to the contributors for inputing. As a general question to all, given that these appear to read as guidelines, - do we want to include them in a charter; or create a TSC policy document where we can capture such things and others (i.e. information

Re: [onap-tsc] [MSB][OOM]The July Virtual Developers Event Topic :  OOM & MSB Interaction

Kenny, Yes this is fine with as defined in wiki. You can go ahead and request TSC’s approval. Thanks, Gildas ONAP Release Manager 1 415 238 6287 From: Kenny Paul [mailto:kp...@linuxfoundation.org] Sent: Monday, July 31, 2017 3:37 PM To: Gildas Lanilis Cc:

Re: [onap-tsc] Use case subcommittee meeting (31/07/2017): the summary

Hi Mazin, Definitely, one part of our plan is to review use cases proposals with Integration and Open lab tams to ensure commitment. Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:image001.png@01D30AA6.70E12AD0] From: GILBERT, MAZIN E (MAZIN E)

Re: [onap-tsc] Use case subcommittee meeting (31/07/2017): the summary

Thanks Alla for sharing. One of the requirement for any new use case should be the availability of a lab and integration support. We need to get that vetted upfront before committing to any use case for a release going forward. Regards Mazin Sent through AT's fastest network On Jul 31,