Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

What

Members of the ONAP Technical Steering Committee (TSC) elect an Standards/SDO Coordinator each year.

Who

This position may be held by anyone in the ONAP community  Only the TSC votes on the candidates.

How

The election process occurs in two phases; the Nomination phase, and the Election phase.

Nominations open May 11th, 2017.
Nominations close May 17th at 9:00pm Pacific Time
Voting begins May 19th, 2017
Voting Ends May 24, 2017 at 9:00pm Pacific Time

Nomination Phase

An email is sent from the Election Coordinator (Phil Robb) to the TSC distribution list for ONAP and the subject line is tagged with the keywords [STANDARDS/SDO COORDINATOR ELECTION].
Any member of the ONAP community may nominate themselves to stand for election. Note that no one can nominate another person to run for election.
To submit a nomination, the community member must reply-all to the original nomination email stating their interest to stand for the election.
All nominees are invited to provide their Picture, Biography, and Statement of Intent for the election wiki page so that members of the TSC, and the community, can learn more about the candidate and their intentions for the role of Standards/SDO Coordinator. The nominee ordering on the election wiki page will be in ascending alphabetical order by last name.
Nominees are asked to send their Bio, Picture, and Statement of Intent to the Election Coordinator (Phil Robb) prior to the commencement of voting. The Election Coordinator will post all Candidate information on the wiki just prior to beginning the election.
The length of the Nomination phase is 5 business days. This clock starts when the email described above is sent.

Election Phase

Immediately upon the close of the Nomination Phase, an email will be sent from the Election Coordinator (Phil Robb) via the Condorcet Internet Voting Service (CIVS) to each TSC member. This email will have the subject line: “Poll: ONAP STANDARDS/SDO COORDINATOR ELECTION”. This email acts as an invitation by the CIVS for each TCS Member to vote. This voting invitation is only sent to the TSC Members. The TSC mailing list is not cc-ed on this email as per the CIVS process. Included in this election invitation will be a pointer to the Election wiki page which contains the names, pictures, biographies, and statements-of-intent for each of the candidates. The email also has instructions and a private URL where each TSC Member is sent to vote.
At the CIVS-provided voting URL, each voter will rank the candidates, where a smaller-numbered rank means that the voter prefers that choice more. Once the ranking is complete, the voter will press the “Submit ranking” button to complete the voting process.
The Election Phase will remain open for at least 5 business days from the time the invitation-to-vote email is sent by the CIVS.
Once the Election Phase has completed, the results of the election, including the votes cast by all participating TSC members, will be made available to the TSC mailing list.

Information on the Candidates

Each Candidate, please provide the following:

  • Name
  • Photo
  • Biography
  • Statement of Intent in being a TSC Vice Chairperson

The Candidates (In ascending alphabetical order by family name)

Jamil Chawki


Biography

    • ·          Since 2012, Coordinating Orange delegates active in different standard organisations like ETSI NFV, IETF, ITU-T SG 13, DMTF, ISO /IEC, 3GPP.
    • ·          Since 2016, OPNFV Board director representing Service Provider Silver members.
    • ·          Since 2015, OpenDaylight Advisory group member representing Orange.  
    • ·          2012-2016 Chairman of the cloud computing Working Party, in ITU-T Study Group 13 ‘Future Networks, SDN and Cloud’
    • ·          2012-2014 Co-convener of the joint Collaborative Team (CT) between ITU-T SG13 and ISO IEC/ JTC1 SC38 on Cloud Computing Overview & Vocabulary (ISO 17788) and Cloud Computing architecture (ISO 17789).


https://www.linkedin.com/in/jamil-chawki-a57a5a3/

https://twitter.com/jchawki

Statement of Intent

In order to accelerate the adoption of ONAP as an industry standard, a strong collaboration between ONAP project and major SDOs and open source projects is needed. As I am leading cloud computing, NFV and SDN standards and open source activities at Orange, I have a solid experience to serve this role. I have contributed to the creation of OPNFV with an objective to deliver a carrier-grade platform for NFV. I am also involved in the development of ETSI NFV specifications as well as the publication of several standards on cloud computing, SDN and Big Data in ITU-T and ISO/IEC.

DENG Hui


Biography

Hui DENG obtained his Doctor degree from Dept. Computer Science and Technology at Tsinghua University in 2002. He worked as chief researcher in Hitachi (China) R&D Cooperation from 2002 to 2007, and worked as Principal staff between 2007 and 2016 in China Mobile. He joined Huawei and working on NFV related topic quite recently. He acted as the co-chair of IETF MIF working group. And he was the board of director of WBA(Wireless Broadband Alliance) between 2012-2014, acted as the board of director of OPNFV between 2014-2016 and 1st board of chairman of OPEN-O project in Linux Foundation.

Mar. 2015 Started to work on the proposal of OPEN-O
May 2015 Contacted with Linux Foundation 1st time
Mar. 2016 1st OPEN-O speech in the keynote of Open Network Summit 2016.

2016 – 2016 1st Board of Chairman, OPEN-O
2014 – 2016 Board of Director (officer), OPNFV
2012 – 2014 Board of Director, WBA(Wireless Broadband Alliance)
2009 – 2016 Co-chair, MIF(Multiple Interfaces) WG, IETF
2016 - ETSI NFV ISG coordinator of Huawei

Professional experience
2016 – Now Chief NFV Strategy Officer, Huawei
2007 – 2016 Principal Staff, China Mobile
2002 – 2007 Chief Researcher, Hitachi

Hosting conference
2015 Chair, NFV workshop Beijing (China Mobile)
2015 Chair, NFV workshop Shanghai (China Mobile)
2016 Chair, SDN/NFV Opensource Workshop Beijing (China Mobile)

IETF RFC Publications
https://www.ietf.org/rfc/rfc7445.txt
https://www.ietf.org/rfc/rfc7494.txt
https://www.ietf.org/rfc/rfc6535.txt
https://www.ietf.org/rfc/rfc6098.txt
https://www.ietf.org/rfc/rfc6630.txt
https://www.ietf.org/rfc/rfc5142.txt
https://www.ietf.org/id/draft-deng-chinese-names-05.txt

Statement Of Intent

I am interested in serving as the coordinator of standard based on my strong feeling of devotion to the ONAP project.
My past 13 years’ experience in both standard and open source could help me to do this job. Standard and opensource are complementary each other, most opensource interfaces are de-facto standard, but still some need the help of standard.

Uri Elzur


Biography

Uri Elzur is the CTO for the Data Center Network Solution Group (DNSG) of Intel’s Data Center Group. In this role, he is responsible for creating SDN/NFV technical strategy, open source top-to-bottom stack architectures (including MANO, OpenStack, ODL, vSwitch) and influence the server platforms.

Uri is a networking specialist with more than 25 years of industry experience and a proven track record of creating innovative product architectures, strategies and in Networking, Virtualization, Security etc. Currently represent Intel at ODL, Open-O (as a VC Architecture) and IETF.

Previously, Uri has held a position of a Sr. Director at Broadcom, managing a networking/NIC architecture team. In that role Uri led multiple innovations in the areas of Virtualization, TCP offload, RDMA, iSER, iSCSI/FCoE.

Uri holds many patents and BSc and MSc EE/CS from the Technion, Haifa, Israel

Statement of Intent

Working in open source communities and standard organizations for multiple years now and specifically in all layers pertinent to ONAP, is in my humble opinion, the background needed to be successful in this important role for the ONAP community. I’ve gathered lots of experience serving as the OPEN-O TSC Vice chair and Architecture chair. I’m proud of the initiatives I’ve led in that community including the initiation of the VNF SDK project that was adopted by the ONAP community too! The VNF SDK was the first open source proposed project to fully include VNFs in a MANO community!

The VNF SDK project is designed to address the painful on-boarding issue and it emphasized the importance of getting VNFs that are in tune with the MANO orchestration as part of the initial design vs. an afterthought. Specifically related to this standards and SDO coordinator position, I’ve also proposed the adoption of a unified, industry-agreed Data Models to enable higher levels of MANO automation and reduction of the VNF vendor’s labor. This has been done in collaboration with all community vendor and considering and integrating the opinions and inputs of multiple VNF vendors.

Positions on level of automation and cloud readiness, are one of the topics that may separate different candidates for this position. We firmly believe that working with relevant standard organizations to promote highest level of automation and agility, are essential to enable Telco to best compete with best cloud efficiencies, for long term NFV success. However, my unequivocal commit is to represent the TSC position whatever it may be!

The time left before the vote is short. So I hope this write up provides some idea of the motivation, proven capabilities and proposed directions

Additional relevant background
· OPEN-O - multiple contributions to the Membership agreement that was used to guide the ONAP’s membership agreement. Active participant in data modeling and standard interactions.
· ODL – serve on the board and was on the TSC in last 2 years. intitiated and drove the Multi Writer work to respolve the issue of multiple projects simultaneously intercting with a vSwitch. Inititiator of the S3P (Stability, Security, Scalabilitya and Perfomance) as a mesure of “readiness” for an open Source project – adopted by ONAP as well
· SFC – working with many of the industry and the community to look for a broad industry agreement for top to bottom SFC
· VNF Data Model – created the initiative for Data Model convergence and industry agreement including multi party public efforts open to all where interoprability and use of the VNF SDK tools created for OPEN-O was demonstrated (e.g. public demo at MWC and recently at L123 NFV World Congress)
· DMTF board member 2008-2010
· IETF – co editor of the NSH (SFC related) draft
· At Intel I lead the stack architrcture MANO through OpenStack, ODL, vSwitches and the server platform. This provides an opportunity

Beyond experience, have demonstraed an un biased handling of technical issues! It is important to note that, we at Intel, do not ship products competing with the key vendors in the ONAP community, we are positioned to handle any potential disagreement in an even handed way!

Tony Hansen


Biography

Standards work:
I have been involved in the Internet Engineering Task Force (IETF) for 25 years, attending a majority of the meetings for the past 20 years. Most of my efforts there have been involved in the Applications and Real Time area, the Security area, and the General area (layer 5 on up). I have 20 published Requests for Comment (RFCs), including full internet standards and best current practices. I have been a Working Group (WG) chair four times, for the Open Pluggable Edge Platform WG (OPES, 2005-2007), the Yet Another Mail WG (YAM, 2009-2011), the File Transfer Protocol Extensions (FTPext, 2010-2012), and the Javascript Object Signing and Encryption WG (JOSE, 2011-2012). I have been a member of the RFC Series Oversight Committee (an Internet Architecture Board [IAB] appointed position) for the past four years.

I have also been an adjunct liaison to the C++ Standards Committee since 1991.

RFCS:
RFC3798 Message Disposition Notification. T. Hansen, Ed., G. Vaudreuil, Ed.. May 2004. (draft standard) (DOI: 10.17487/RFC3798)
RFC3885 SMTP Service Extension for Message Tracking. E. Allman, T. Hansen. September 2004. (Proposed Standard) (DOI: 10.17487/RFC3885)
RFC3887 Message Tracking Query Protocol. T. Hansen. September 2004. (Proposed Standard) (DOI: 10.17487/RFC3887)
RFC3888 Message Tracking Model and Requirements. T. Hansen. September 2004. (Informational) (DOI: 10.17487/RFC3888)
RFC3938 Video-Message Message-Context. T. Hansen. October 2004. (Proposed Standard) (DOI: 10.17487/RFC3938)
RFC4395 / BCP35 Guidelines and Registration Procedures for New URI Schemes. T. Hansen, T. Hardie, L. Masinter. February 2006. (Best Current Practice) (DOI: 10.17487/RFC4395)
RFC4634 US Secure Hash Algorithms (SHA and HMAC-SHA). D. Eastlake 3rd, T. Hansen. July 2006. (Informational) (DOI: 10.17487/RFC4634)
RFC5248 / BCP138 A Registry for SMTP Enhanced Mail System Status Codes. T. Hansen, J. Klensin. June 2008. (Best Current Practice) (DOI: 10.17487/RFC5248)
RFC5585 DomainKeys Identified Mail (DKIM) Service Overview. T. Hansen, D. Crocker, P. Hallam-Baker. July 2009. (Informational) (DOI: 10.17487/RFC5585)
RFC5703 Sieve Email Filtering: MIME Part Tests, Iteration, Extraction, Replacement, and Enclosure. T. Hansen, C. Daboo. October 2009. (Proposed Standard) (DOI: 10.17487/RFC5703)
RFC5863 DomainKeys Identified Mail (DKIM) Development, Deployment, and Operations. T. Hansen, E. Siegel, P. Hallam-Baker, D. Crocker. May 2010. (Informational) (DOI: 10.17487/RFC5863)
RFC6234 US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF). D. Eastlake 3rd, T. Hansen. May 2011. (Informational) (DOI: 10.17487/RFC6234)
RFC6376 / STD76 DomainKeys Identified Mail (DKIM) Signatures. D. Crocker, Ed., T. Hansen, Ed., M. Kucherawy, Ed.. September 2011. (Internet Standard) (DOI: 10.17487/RFC6376)
RFC6533 Internationalized Delivery Status and Disposition Notifications. T. Hansen, Ed., C. Newman, A. Melnikov. February 2012. (Proposed Standard) (DOI: 10.17487/RFC6533)
RFC6838 / BCP13 Media Type Specifications and Registration Procedures. N. Freed, J. Klensin, T. Hansen. January 2013. (Best Current Practice) (DOI: 10.17487/RFC6838)
RFC6839 Additional Media Type Structured Syntax Suffixes. T. Hansen, A. Melnikov. January 2013. (Informational) (DOI: 10.17487/RFC6839)
RFC7595 / BCP35 Guidelines and Registration Procedures for URI Schemes. D. Thaler, Ed., T. Hansen, T. Hardie. June 2015. (Best Current Practice) (DOI: 10.17487/RFC7595)
RFC7677 SCRAM-SHA-256 and SCRAM-SHA-256-PLUS Simple Authentication and Security Layer (SASL) Mechanisms. T. Hansen. November 2015. (Proposed Standard) (DOI: 10.17487/RFC7677)
RFC7995 PDF Format for RFCs. T. Hansen, Ed., L. Masinter, M. Hardy. December 2016. (Informational) (DOI: 10.17487/RFC7995)
RFC8098 / STD85 Message Disposition Notification. T. Hansen, Ed., A. Melnikov, Ed.. February 2017. (Internet Standard) (DOI: 10.17487/RFC8098)

Open Source work:
I was an early adopter of open source 35 years ago. I have contributed to the IETF Open source tools for the past 10 years. I have contributed code to various other small open source projects. I have been working on OpenECOMP & now ONAP for the past two years.

Other major publications:
The C++ Answer Book, 1989

Professional Experience:
Bell Laboratories / AT&T 1980 – present
Member of Technical Staff, Distinguished Member of Technical Staff, Technology Consultant, Lead Member Technical Staff

Education:
Masters Computer Science / Computer Engineering, Stanford University, 1981
Bachelor of Science Electrical Engineering, SDSU, 1980
Bachelor of Arts Mathematics, SDSU, 1980

Statement of Intent

I am interested in the ONAP Standards / SDO Coordinator position. I feel that my involvement in the standards world for the past 25 years puts me in an excellent position to support ONAP in this role.



  • No labels