PPT-1 IETF-79, Nov. 2010

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 InternetDraft 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. 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: . , 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:. 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. Marc Linsner. 5/11/10. ECRIT Charter (or a piece of it). ………The . group will show how the availability of location data and . call routing . information at different steps in session setup would . 1. Alert-Info URNs for the . Session Initiation Protocol . (SIP). draft-liess-dispatch-alert-info-urns-02. L. Liess, R. Jesske, D. Alexeitsev (Deutsche Telekom). A. Johnston, A. Siddiqui (Avaya). IETF 78 – Maastricht, Netherlands. 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>. . draft-asaeda-mboned-explicit-tracking-00. Hitoshi Asaeda. (Keio University). 78. th. IETF, Maastricht, Netherlands, July 2010 . 1. 78th IETF, July 2010, Maastricht. Objectives. Problem in bursty IGMP/MLD message transmission. IETF-78, Maastricht July 2010. Online Agenda and Slides at:. https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi. Co-chairs: JP Vasseur/David Culler. ADs: Adrian Farrel / Ross Callon. Note Well. 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). 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:. 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. ?. 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..