IETF Capacity Building and IPv6

IETF Capacity Building and IPv6

Talk at IoT/IPv6 Forum at CommunicAsia 2016. There is a companion IPv6 Excuses Bingo document as well.

75935a034e6c04dfd6f6946a299c3937?s=128

Harish Pillay

June 03, 2016
Tweet

Transcript

  1. How To Be An IETF Champion 1 Harish Pillay Member,

    Board of Trustees (2016-2019) ISOC (h.pillay@ieee.org) https://speakerdeck.com/harishpillay/ietf-capacity-building-and-ipv6 CC-BY-SA
  2. What is the IETF The IETF is the Internet’s premier

    technical standards body. It gathers a large community of network designers, operators, vendors, and researchers concerned with the evolution of the Internet architecture and the smooth operation of the Internet 2
  3. Mission The mission of the Internet Engineering Task Force (IETF)

    is to make the Internet work better by producing high quality, relevant technical documents that influence the way people design, use, and manage the Internet 3
  4. Some Tech accomplishments at IETF I • IPv6 • Fundamental

    to realizing the vision of an "Internet of Things” • The Domain Name System(DNS): a unified global address book • DNS now accommodates domain name in languages such as Arabic & Chinese making the Internet accessible to people who do not use Latin scripts • Protocols that advance the trustworthiness of the domain names that are key to the online presence of companies, organisations and individuals 4
  5. Some Tech accomplishments at IETF II • Strengthening Trust in

    the Internet •Best practices for existing application protocols such as instant messaging and email •Using encrypted connections more routinely •Creating a document to guide future application protocol developers • Making Collaboration Frictionless •The IETF in co-ordination with the World Wide Web Consortium (W3C) worked on the RTCWEB protocol which will allow any Web browser real-time collaboration with any other Web browser—with no need for a central server •OPUS audio codec was developed at the IETF - This is an alternative to proprietary approaches for encoding and decoding audio streams •Open video codec work is underway at the IETF - To develop an open video codec that promises to unlock the potential of video-based communications and collaboration 5
  6. IETF Participation/structure • There is no membership or voting at

    the IETF • The IETF is made of volunteers • The actual standards work takes place on mailing lists – attendance at f2f meetings is to resolve “big” issues and to get to know people 6
  7. IETF Work team • Document editors: edit individual documents •

    129ish working groups(WGs) • 7 Areas/Area Directors(AD) • Working group Chairs: Manage working group • IETF Chair • Internet Engineering Steering Group(IESG): Tech Review, Process Management, Adjudicates Appeals(AD+Chair) • Internet Architecture Board(IAB): Architectural Guidance & Liaison 7
  8. Working Groups •Primarily where IETF gets its work done •Working

    groups (WGs) •Generally proposed by IETF participants ie “bottoms up” • Announcement goes to other Standards Developing Organisations(SDO) to check for overlaps • IESG has final say on Charter • Working groups are closed when work is done • At least in theory 8
  9. IETF Areas 9

  10. Big Internet Trends Imp. for the IETF •Fast evolution in

    web technology •Security and Privacy •Tension between security and network management •Role of open source development 10
  11. Fast evolution in web technology •The web platform continues to

    support even more applications •High quality open codecs such as Internet Video Codec(NETVC) •The new HTTP protocol (HTTP/2) •Web tech for the Internet of Things •Innovative ideas in larger re-organisations of the protocol stack •Rapid evolution is driven by multiple reasons 11
  12. Security, Privacy and Network Mgmt • Communication security an aspect

    IETF is committed to improving its protocols • IETF since Snowden revelations • TLS 1.3, algorithms, UTA, DPRIVE… • RFC 7258-surveillance is just another security threat • Larger & larger fraction of all Internet traffic is encrypted & it affects network management 12
  13. Current Hot topics •YANG Modeling •Strengthening the Internet •Measurement Driven

    Protocol Engineering 13
  14. Tech dev is increasingly Code-based •Open source has a central

    role •Standard setting is a parallel activity •Waterfall development model will not suffice •“Rough consensus and running code” with hacking to programme cool new Internet tech at the IETF Hackathon 14
  15. How IETF work gets done 15 1. Tech development is

    done in Working Group (but can be individual effort) 2. Proposal published as a working document “Internet Draft” 3. Working document revised & re-published based on discussion 4.Working document submitted to IESG via AD 5.AD performs technical & process review of document & returns doc with comments if AD finds issues 6.When AD satisfied, IESG issues “Last call” for comments IETF wide 7.IESG performs interdisciplinary tech review of proposal & reviews Last Call comments 8.IESG returns documents to WG with comments if finds issues 9.When IESG is satisfied ,the document is sent to RFC Editor for publication as RFC
  16. Rough Consensus •Does not require unanimity •But ensures that everyone

    has their say •No formal voting •Show of hands or hum but no count •Disputes resolved by discussion •On mailing list & in face-to-face meetings •Final decisions must be verified on mailing list • But taking into account face-to-face discussion 16
  17. IETF Documents • All IETF documents are open •May be

    downloaded and copies made in full • Internet Drafts are IETF working documents • RFC •Archival publications which never changed once published •Update or correction gets new RFC number 17
  18. RFCs • Now over 7,000 RFCs • RFCs include Standards

    RFCs such as • Best Current Practices(BCP) •Policies or procedures(best way we know how) •2 stage standards track •Proposed standard(PS) •Good idea, no known problem •Internet Standard (STD) •PS + stable + ”benefit to Internet community” Multiple interoperable implementations to prove document clarity Note: interoperability, not conformance 18
  19. The Role & Scope of the IETF •Above the wire

    & below the application •IP, TCP, email, routing, IPsec, HTTP, FTP, ssh, LDAP, SIP, mobile, IP, ppp, RADIUS, Kerberos, secure email, streaming video & audio •But wires are getting fuzzy •MPLS, GMPLS, pwe3, VPN •Generally hard to clearly define IETF scope •IETF is constantly exploring the edges eg, IP telephony 19
  20. Scope of Other SDOs •The Internet is becoming the underpinnings

    of the entire world telecommunications business •Other SDOs trying to “fix” or “extend” IETF protocols •They may be trying to solve a different problem or are making different assumptions •Problem: What happens when extensions break underlying protocol assumptions or make non-interoperable versions? •SDO(including IETF) assumption: each SDO modifies its own protocols 20
  21. Internet Research Task Force(IRTF) Focuses on long term Internet problems

    •Crypto Forum Research Group(CFRG) •Delay-Tolerant Networking Research Group(DTNRG) •Global Access to the Internet for All Research Group (GAIA) •Internet Congestion Control Research Group(ICCRG) •Information Centric Networking Research Group(ICNRG) •Network Coding Research Group(NWCRG) •Network Management Research Group(NMRG) •Network Function Virtualization Research Group(NFVRG) •Software-Defined Network Research Group(SDNRG) 21
  22. IETF Trust •Holds Rights •Copyrights (on RFC etc) •Domain names

    •Trademarks •Software paid for by IETF •Databases etc •IPR created under the secretariat contract goes to Trust •The IETF Trust is not a patent pool 22
  23. IPR (Copyright) •ID author(s) need to give non-exclusive publication rights

    to IETF Trust if to be published at all • Also (normally) the right to make derivative works •This right required for standards track documents author(s) retain all other rights 23
  24. IPR(Patent) • Requires timely disclosure of your own IPR in

    your own submission & submission of others •“Reasonably & personally” known to the WG participant ie no patent search required •Disclosures published on IETF website • WG may take IPR into account when choosing solution •Many WGs tend to want IPR free(or at least assumed to be IPR free) update in the works 24
  25. Note Well • Note well defines “contribution” & requires obeying

    IETF rules • In effect a “contribution” is anything you say or write with the intent to effect the IETF standards process 25
  26. Why participate in standards •Enable your company to stay relevant

    •Gain influence over customers by being part of a team that develop a new standard •Help executive team gain valuable intelligence that could be useful to overall corporate strategy •Be knowledgeable about new mandatory standards used by customers in their RFPs 26
  27. Imp&Benefits of Open Standards(cos) •Less chance of being locked in

    by a specific technology and/or vendor •Easier for systems using different technologies to interoperate and communicate with one another •Open character coding standard makes it feasible for translation and localization of software and electronic office documents •It may be possible to mix and match solutions to provide best-of-breed solutions as far as possible •For an organization that possesses huge amounts of e-data, it will be easier to migrate or change information systems as it will be cheaper and possible to convert data files 27
  28. Additional IETF materials •https://www.ietf.org/newcomers.html •http://www.ietf.org/tao.html 28

  29. Upcoming events in Asia-Pacific •IETF97 Seoul November 13-18, ‘16 (30

    years) •IETF100 (a milestone) will be in Singapore 29
  30. IETFs in Asia-Pacific •IETF Yokohama 1486 participants (from 70 countries

    40% from Asia) •IETF Taipei 1051 participants •IETF Beijing 1337 participants •IETF Hiroshima 1249 participants •Major participating companies include Cisco,Huawei, Ericsson etc 30
  31. 31 Thank you CC-BY-SA Harish Pillay Member, Board of Trustees

    (2016-2019) ISOC (h.pillay@ieee.org) https://speakerdeck.com/harishpillay/ietf-capacity-building-and-ipv6
  32. None