PPT-IETF Security Tutorial

Radia Perlman Intel Labs August 2012 radiaalummitedu Why an IETF Security Tutorial Security is important in all protocols not just protocols in the security area IETF specs mandated to have a security considerations section. , Nov. 2010. MEXT WG. 2. Administrativia. We need:. Two . n. ote takers. At least one jabber scribe. Blue Sheets. 3. Note Well. Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to:. ?. Internet Standards and How to Get . Involved. Chris Grundemann. Internet Society. MENOG 15 – Dubai – 2 April 2015. The Internet Engineering Task Force (IETF). First, one important point:. No one really speaks FOR the IETF.. Report . Allison . Mankin, Verisign Labs. Nomcom Chair 2013. Nomcom Process . Nomcom is the process by which we select the IETF leadership: IESG, IAB, part of the IAOC. Nomcom consists of 10 voting members randomly selected from a pool of volunteers. server-model-01. NETCONF Server Configuration Model. Updates since . IETF 89. From . I-D. to -00. Changed title to "NETCONF Server Configuration . Model”. Mapped . inbound/outbound to listen/call-. IETF . na. . América. Latina. Alvaro Retana (. aretana@cisco.com. ). Distinguished Engineer, Cisco Services. Routing Area Director, IETF. RFC 3935. A Mission Statement for the . IETF. “The . mission of the IETF is to produce high quality, relevant technical and engineering documents that influence the way people design, use, and manage the Internet in such a way as to . 1. MPLS-TP Control Plane Framework. . draft-ietf-ccamp-mpls-tp-cp-framework-02.txt . Contributors:. Loa Andersson <loa. @ericsson.com. >. Lou Berger <lberger@labn.net>. Luyuan Fang <lufang@cisco.com>. Real-time Communications. SIPNOC 2016. Herndon, Virginia. Russ Housley. My Background. Became active in the IRTF, and then IETF to work on security for Email and PKI. IETF S/MIME WG Chair. IETF Security Area Director – 4 years. Dave Thaler. November 6, 2013. Perpass BoF - IETF 88. 1. Potential Threats. We do not know what exactly has been done. Some might be real. Some might be pure speculation. Some might be research about what could be done in the future. (29 July – 3 Aug. 2012). Cloud . Computing, . N. etworking, and Service (CCNS) . Update for . GISFI-10, New . Delhi, . India . 10-12 Sept. 2012. Monday-10-September-2012 . 1. IETF84 update for GISFI-10, New Delhi . 1. Martini Working Group. IETF 79 Beijing. Chairs:. Bernard Aboba:bernard_aboba@hotmail.com. Spencer Dawkins:spencer@wonderhamster.org. IETF 79 - Beijing, China. 2. Logistics. Jabber room:  . martini at jabber.ietf.org (Please join). (TLS). IETF-76. Chairs. Joe Salowey (. jsalowey@cisco.com. ). Eric Rescorla (. ekr@rtfm.com. ). Note Well. Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to:. 88, . Vancouver. , . Ca. 2013. -. 11. -07 . 0900-. 1130. Plaza C. LISP Working Group. LISP Working Group. 2. Agenda and slides:. http://. tools.ietf.org. /. wg. /lisp/. agenda?item. =agenda-. 88-. lisp.html. Chairs:. Alan . DeKok. Joe . Salowey. . Note Well. Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". . March 29, 2011. Mar 29, 2011. IETF NEA Meeting. 1. Note Well. Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to:.