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.
Tony Hansen
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
[cid:[email protected]] [cid:[email protected]]
From:
<[email protected]<mailto:[email protected]>>
on behalf of Phil Robb
<[email protected]<mailto:[email protected]>>
Date: Thursday, May 11, 2017 at 9:50 PM
To: onap-tsc <[email protected]<mailto:[email protected]>>,
"[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>
Subject: [onap-discuss] [ONAP STANDARDS/SDO COORDINATOR ELECTION] Kickoff of
the ONAP Standards/SDO Coordinator Election
Hello ONAP Community Members:
Please consider this email as the kickoff of the ONAP Standards/SDO Coordinator
Election process. A description of the role can be found on the ONAP Technical
Community Coordinator's page here:
https://wiki.onap.org/display/DW/Technical+Community+Coordinators<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Technical-2BCommunity-2BCoordinators&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=Kz8VdgPVctDNSNPJ6PsBaw&m=UqBezFFv4qQgi-QTvOqoz4z97ZvEmBpExza_jgVv9dI&s=Bl7KZG7Yx2MD7Ce3OoxVTq2xIS7EldRb6YdXu7bMRRk&e=>
Please recall, as stated in section 5.2.2.2 of the ONAP TSC Charter, any member
of the technical community is eligible to run for this position. It is not
exclusively reserved for TSC Members. However, only TSC members are eligible
to vote when choosing among the potential candidates. This position serves at
the pleasure of the TSC and TSC Chairperson.
There are two phases to the election process. The first is the Nomination
Phase where community members may nominate themselves for the position of "ONAP
Standards/SDO Coordinator". Once the Nomination Phase has concluded, we will
enter the Election Phase, where all ONAP TSC Members are invited and encouraged
to vote on the candidates whom have been nominated.
Timing:
§ Nominations open May 11th, 2017.
§ Nominations close May 17th at 9:00pm Pacific Time
§ Voting begins May 18th, 2017
§ Voting Ends May 24th, 2017 at 9:00pm Pacific Time
If you wish to nominate yourself for the position of "ONAP Standards/SDO
Coordinator", please respond-all to this email with your picture (headshot),
biography, and statement of interest on why you would wish to hold the
position. I wlll post this information to the wiki prior to the start of the
election so that everyone in the technical community is able to become familiar
with the candidates.
If you have any questions, please do not hesitate to contact me.
Best,
Phil.
--
Phil Robb
Executive Director, OpenDaylight Project
VP Operations - Networking & Orchestration, The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb
_______________________________________________
ONAP-TSC mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-tsc
