PPT-Bundle Protocol Status IETF 99

Scott Burleigh Jet Propulsion Laboratory California Institute of Technology 17 July 2017 This research was carried out at the Jet Propulsion Laboratory California Institute of Technology under a contract with the National Aeronautics and Space Administration 2017 California Institute of Technology Government sponsorship acknowledged. How and when to extend an existing . protocol. Adrian Farrel. Old Dog Consulting. adrian@olddog.co.uk. Engineer (. ɛndʒɪˈnɪə). noun . A . person who designs, builds, or maintains engines, machines, or . draft-dharinigert-ccamp-g-698-2-lmp-02.txt. Dharini Hiremagalur . Juniper Networks. Gert Grammel . Juniper Networks. John E. Drake . Juniper Networks. Gabriele Galimberti . Jeffrey Haas, . jhaas@pfrc.org. Dave Ward, . dward@juniper.net. Where do we go from here. We have largely accomplished our original charter.. Our original charter prohibited taking on new working group items without re-chartering.. Network of Information. Dirk Kutscher – NEC Labs. SAIL Project Consortium. DTNRG Meeting @ IETF-78. 2010-07-30. DTN Community:. We have come a long way. Interplanetary Networking. Networking the orbit, solar system, universe. Yaakov (J) Stein. September 2011. Outline. MPLS-TP history. Fundamentals. The . GACh. OAM. APS. Control plane. MPLS-TP History. Background. IP is the most popular packet-switched. . protocol. MPLS and. Russ Housley, IETF Chair. 2. IETF Grey Beard Beer?. 3. IETF 78 Participants. 1153 people. 267 newcomers. IETF 75 was 1124 people. 53 countries. . IETF 75 was 51 countries. IETF 75 was held in . Stockholm. ?. 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.. IETF#91, Honolulu, USA.. Victor Pascual . <victor.pascual@quobis.com>. Christer Holmberg <christer.holmberg@ericsson.com>. (. 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:. IETF. -. 89. Mary Barnes (WG . co-chair. ). Paul . Kyzivat. (WG . co-chair. ). 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 . . WG Meeting. Berlin, IETF-87, 30. th. July 2013. Philip . Eardley. Yoshifumi Nishida. 1. Note taker. Jabber [IMPORTANT]. • Please include . “. -. mptcp. -. ”. in your draft names. • Please say your name at the mike. IETF 83, Paris. Gabor Bajko, Brian Rosen. 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:. 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:. ?. 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.. Les Ginsberg. . (. ginsberg@cisco.com. ). Ahmed Bashandy (. bashandy@cisco.com. ). Clarence Filsfils(. cfilsfils@cisco.com. ). Stefano Previdi (. sprevidi@cisco.com. ). Mohan . Nanduri. (. mnanduri@microsft.com.