PPT-IETF 94 Yokohama

Author : lindy-dunigan | Published Date : 2018-01-06

draft finn detnet problemstatement Norm Finn Pascal Thubert DetNet problem statement Doc charter This effort will establish the deployment environment and

Presentation Embed Code

Download Presentation

Download Presentation The PPT/PDF document "IETF 94 Yokohama" is the property of its rightful owner. Permission is granted to download and print the materials on this website for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.

IETF 94 Yokohama: Transcript


draft finn detnet problemstatement Norm Finn Pascal Thubert DetNet problem statement Doc charter This effort will establish the deployment environment and deterministic network requirements . 1. BEHAVE Working Group. IETF 77 – Anaheim. March, 2010. Chairs: . Dave Thaler, dthaler@microsoft.com. Dan Wing, dwing@cisco.com. BEHAVE – IETF 77. 2. 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: . Just Getting Started. NANOG 63. The . first ever IETF Help Desk was successfully held at . NANOG 63. in San Antonio . 2-4 February. . The help desk provided a common, known point for operators attending the NANOG meeting to bring their questions about the IETF. As expected, we received many very basic questions, the most popular being, ‘How do I get started?’. The booth was set up for all three days of the NANOG meeting and was staffed by experienced IETF volunteers most of the time, including during all breaks. Based on this success we will continue with our plan to facilitate hosting of the IETF Help Desk at NOG/NOF meetings around the world. ?. 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. MEXT WG. 2. Administrativia. We need:. Two note 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:. draft-. wilton. -. netmod. -. intf. -. vlan. -yang. Robert Wilton (Cisco). Presentation Objectives. To explain what this IETF model is trying to achieve. To justify why this is being standardized in IETF. (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). 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". . Hannes Tschofenig. Status. Finished various specifications, including . OAuth. Core: RFC 6749. Bearer Tokens: RFC 6750. Security Threats: RFC 6819. Discussion about an enhancement to Bearer Token security (now called “Proof-of-Possession”) since the early days of the working group. . draft-ietf-teas-fast-lsps-requirements. From: Brain Wilson, 10 Mar 2015. Open issues:. None known. Next steps:. Soliciting WG review and comments. . 92nd IETF TEAS Working Group. 2. draft-. ietf. -teas-. cja@daydream.com. ARIN . XXVII. April 2011. San Juan, Puerto Rico. Note. This . presentation is not an official IETF report. There is no official IETF Liaison to ARIN or any . RIR. This is all my opinion and my view and I am not covering everything just highlights. Update History. Version 00 presented at IETF 92. Provided introduction to an Information Model relevant to the data modeling work on Topology underway in the IETF, describing:. Relevant work under development outside of the IETF. draft-barguil-teas-network-slices-instantation-06. S. Barguil (. Nokia. ), . L.M. Contreras . (. Telefonica. ), V. Lopez (. Nokia. ), R. Rokui (. Ciena. ), O. Gonzalez de Dios (. Telefonica. ), D. King (.

Download Document

Here is the link to download the presentation.
"IETF 94 Yokohama"The content belongs to its owner. You may download and print it for personal use, without modification, and keep all copyright notices. By downloading, you agree to these terms.

Related Documents