Guest User

Hackathon Stolen Emails

a guest
Dec 4th, 2015
126
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 13.92 KB | None | 0 0
  1.  
  2. From nobody Thu May 7 08:08:56 2015
  3. Return-Path: <eckelcu@cisco.com>
  4. X-Original-To: 92hackathon@ietfa.amsl.com
  5. Delivered-To: 92hackathon@ietfa.amsl.com
  6. Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9597D1A0027 for <92hackathon@ietfa.amsl.com>; Thu, 7 May 2015 08:08:54 -0700 (PDT)
  7. X-Virus-Scanned: amavisd-new at amsl.com
  8. X-Spam-Flag: NO
  9. X-Spam-Score: -14.51
  10. X-Spam-Level:
  11.  
  12.  
  13. --_004_D170CCBA4919Aeckelcuciscocom_
  14. Content-Type: multipart/alternative;
  15. boundary="_000_D170CCBA4919Aeckelcuciscocom_"
  16.  
  17. --_000_D170CCBA4919Aeckelcuciscocom_
  18. Content-Type: text/plain; charset="iso-8859-1"
  19. Content-Transfer-Encoding: quoted-printable
  20.  
  21. Just an FYI for any stragglers who subscribed to 92hackathon and have not y=
  22. et had a chance to subscribe to hackathon@ietf.org. If you want to remain i=
  23. nvolved in the hackathons going forward, please subscribe to the new list: =
  24. https://www.ietf.org/mailman/listinfo/hackathon
  25.  
  26. My apologies to those who receive this message twice.
  27.  
  28. Cheers,
  29. Charles
  30.  
  31. From: Charles Eckel <eckelcu@cisco.com<mailto:eckelcu@cisco.com>>
  32. Date: Thursday, May 7, 2015 at 8:01 AM
  33. To: "hackathon@ietf.org<mailto:hackathon@ietf.org>" <hackathon@ietf.org<mai=
  34. lto:hackathon@ietf.org>>
  35. Subject: [hackathon] update on Hackathon
  36.  
  37. Hi Everyone,
  38.  
  39. We are close to launching the event page and registration site for the hack=
  40. athon at IETF 93 in Prague. We are working out a few remaining issues. In t=
  41. he meantime, here is a preview of the info for your considering and plannin=
  42. g purposes. Comments, suggestions, and additional technologies/champions ar=
  43. e all welcome.
  44.  
  45.  
  46. IETF 93 Hackathon
  47.  
  48. The Internet Engineering Task Force (IETF) is holding a Hackathon to encour=
  49. age developers to discuss, collaborate and develop utilities, ideas, sample=
  50. code and solutions that show practical implementations of IETF standards.
  51.  
  52. When: Saturday July 18 and Sunday July 19
  53. Where: Hilton Prague, Room TBD
  54.  
  55. Keep up to date by subscribing to https://www.ietf.org/mailman/listinfo/hac=
  56. kathon
  57.  
  58. The Hackathon is free to attend but limited to 100 attendees.
  59.  
  60. ________________________________
  61. Technologies and Champions*
  62.  
  63. * Champions are individuals familiar with a given technology who have volun=
  64. teered to help get others get up and running with that technology
  65.  
  66. Champions should:
  67.  
  68. * Plan to arrive Friday, for any setup, and attend Saturday and Sund=
  69. ay
  70. * Prepare a brief overview presentation to introduce the technology =
  71. and suggest potential projects
  72. * Make themselves available to answer questions and help others
  73. * Hack on things themselves in their copious free time
  74. * Additional champions for new or existing technologies are welcome =
  75. at any time, send to hackathon@ietf.org<mailto:hackathon@ietf.org>
  76.  
  77. Current Technologies Include:
  78.  
  79. * BIER (Bit Index Explicit Replication)
  80.  
  81. * An alternative method of multicast forwarding
  82. * Status: confirmed
  83. * Champions:
  84. Greg Shepherd (shep) <shep@cisco.com<mailto:shep@cisco.com>>
  85. IJsbrand Wijnands (iwijnand) <ice@cisco.com<mailto:ice@cisco.com>>
  86. * IETF working group charter: https://datatracker.ietf.org/wg/bier/c=
  87. harter/
  88.  
  89. * HTTP/2.0
  90. * IETF Charter Hypertext Transfer Protocol (httpbis)<https://datatra=
  91. cker.ietf.org/wg/httpbis/charter/>
  92. * Champions:
  93. Mark Nottingham <mnot@mnot.net<mailto:mnot@mnot.net>>
  94.  
  95. * NETCONF/YANG, I2RS, OpenDaylight
  96. * Working with NETCONF/YANG devices and models in I2RS and OpenDayli=
  97. ght
  98. * Champions:
  99. Benoit Claise <bclaise@cisco.com<mailto:bclaise@cisco.com>>
  100. Jan Medved (jmedved) <jmedved@cisco.com<mailto:jmedved@cisco.com>>
  101. Ignas Bagdonas <ibagdona.ietf@gmail.com<mailto:ibagdona.ietf@gmail.com>>
  102.  
  103. * NETVC and Daala
  104. * Open source, royalty free video codec, video compression
  105. * Daala Project: https://xiph.org/daala/
  106. * Proposed IETF working group: Internet Video Codec (netvc)<https://=
  107. datatracker.ietf.org/wg/netvc/charter/>
  108. * Champions:
  109. Timothy B. Terriberry <tterriberry@mozilla.com<mailto:tterriberry@mozilla.c=
  110. om>>
  111. Jack Moffitt <jmoffitt@mozilla.com<mailto:jmoffitt@mozilla.com>>
  112.  
  113. * RIOT (OS for internet of things)
  114. * http://www.riot-os.org/
  115. * Information centric networking for IoT: Experiments with NDN in th=
  116. e Wild: http://conferences2.sigcomm.org/acm-icn/2014/papers/p77.pdf
  117. * Champions:
  118. Matthias Waehlisch <m.waehlisch@fu-berlin.de<mailto:m.waehlisch@fu-berlin.d=
  119. e>>
  120. Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr<mailto:Emmanuel.Baccelli@inri=
  121. a.fr>>
  122. Oliver Hahm <oliver.hahm@inria.fr<mailto:oliver.hahm@inria.fr>>, a.k.a. Ole=
  123. g
  124.  
  125. * SFC in OpenDaylight
  126. * Service function chaining with OpenDaylight
  127. * Champions:
  128. Reinaldo Penno <rapenno@gmail.com<mailto:rapenno@gmail.com>>
  129.  
  130. * SPUD (Substrate Protocol Underneath Datagrams)
  131. * Provide mechanism for applications at the end and boxes along the =
  132. path to explicitly declare their assumptions and intentions
  133. * Drafts: https://tools.ietf.org/id/spud
  134. * Open source library: iptube/SPUDlib =B7 GitHub<https://github.com/=
  135. iptube/SPUDlib>
  136. * Champions:
  137. Joe Hildebrand <jhildebr@cisco.com<mailto:jhildebr@cisco.com>>
  138. Pal Martinsen <palmarti@cisco.com<mailto:palmarti@cisco.com>>
  139.  
  140. Cheers,
  141. Charles
  142.  
  143. --_000_D170CCBA4919Aeckelcuciscocom_
  144. Content-Type: text/html; charset="iso-8859-1"
  145. Content-ID: <45DFE820090F50418369C628C2B0FF83@emea.cisco.com>
  146. Content-Transfer-Encoding: quoted-printable
  147.  
  148. <html>
  149. <head>
  150. <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
  151. 1">
  152. </head>
  153. <body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
  154. e-break: after-white-space; color: rgb(0, 0, 0); font-size: 16px; font-fami=
  155. ly: Calibri, sans-serif;">
  156. <div>Just an FYI for any stragglers who subscribed to 92hackathon and have =
  157. not yet had a chance to subscribe to hackathon@ietf.org. If you want to rem=
  158. ain involved in the hackathons going forward, please subscribe to the new l=
  159. ist:
  160. <a href=3D"https://www.ietf.org/mailman/listinfo/hackathon">https://www.iet=
  161. f.org/mailman/listinfo/hackathon</a></div>
  162. <div><br>
  163. </div>
  164. <div>My apologies to those who receive this message twice.</div>
  165. <div><br>
  166. </div>
  167. <div>Cheers,</div>
  168. <div>Charles</div>
  169. <div><br>
  170. </div>
  171. <span id=3D"OLK_SRC_BODY_SECTION">
  172. <div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
  173. lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
  174. 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
  175. BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
  176. <span style=3D"font-weight:bold">From: </span>Charles Eckel &lt;<a href=3D"=
  177. mailto:eckelcu@cisco.com">eckelcu@cisco.com</a>&gt;<br>
  178. <span style=3D"font-weight:bold">Date: </span>Thursday, May 7, 2015 at 8:01=
  179. AM<br>
  180. <span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:hackath=
  181. on@ietf.org">hackathon@ietf.org</a>&quot; &lt;<a href=3D"mailto:hackathon@i=
  182. etf.org">hackathon@ietf.org</a>&gt;<br>
  183. <span style=3D"font-weight:bold">Subject: </span>[hackathon] update on Hack=
  184. athon<br>
  185. </div>
  186. <div><br>
  187. </div>
  188. <blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT:=
  189. #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
  190. <div>
  191. <div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
  192. -break: after-white-space; font-family: Calibri, sans-serif; font-size: 16p=
  193. x; color: rgb(0, 0, 0);">
  194. <div>Hi Everyone,</div>
  195. <div><br>
  196. </div>
  197. <div>We are close to launching the event page and registration site for the=
  198. hackathon at IETF 93 in Prague. We are working out a few remaining issues.=
  199. In the meantime, here is a preview of the info for your considering and pl=
  200. anning purposes. Comments, suggestions,
  201. and additional technologies/champions are all welcome.</div>
  202. <div><br>
  203. </div>
  204. <div>
  205. <p class=3D"ptitle"><b style=3D"font-size: 20px;">IETF 93 Hackathon&nbsp;</=
  206. b></p>
  207. <p>The Internet Engineering Task Force (IETF) is holding a Hackathon to enc=
  208. ourage developers to discuss, collaborate and develop utilities, ideas, sam=
  209. ple code and solutions that show practical implementations of IETF standard=
  210. s.<br>
  211. <br>
  212. <strong>When:</strong>&nbsp;Saturday July 18 and Sunday July 19<br>
  213. <strong>Where:</strong>&nbsp;Hilton Prague, Room TBD<br>
  214. <br>
  215. Keep up to date by subscribing to&nbsp;<a href=3D"https://www.ietf.org/mail=
  216. man/listinfo/hackathon" style=3D"color: purple;">https://www.ietf.org/mailm=
  217. an/listinfo/hackathon</a></p>
  218. <p>The Hackathon is free to attend but limited to 100 attendees.</p>
  219. <hr>
  220. <h3 style=3D"font-size: 16px;">Technologies and Champions*</h3>
  221. <p>* Champions are individuals familiar with a given technology who have vo=
  222. lunteered to help get others get up and running with that technology</p>
  223. <ul>
  224. <blockquote>
  225. <p><strong>Champions should:</strong></p>
  226. </blockquote>
  227. <ul>
  228. <li>Plan to arrive Friday, for any setup, and attend Saturday and Sunday</l=
  229. i><li>Prepare a brief overview presentation to introduce the technology and=
  230. suggest potential projects</li><li>Make themselves available to answer que=
  231. stions and help others</li><li>Hack on things themselves in their copious f=
  232. ree time</li><li>Additional champions for new or existing technologies are =
  233. welcome at any time, send to&nbsp;<a href=3D"mailto:hackathon@ietf.org" sty=
  234. le=3D"color: purple;">hackathon@ietf.org</a></li></ul>
  235. </ul>
  236. <p><strong>Current Technologies Include:</strong><strong><br>
  237. </strong></p>
  238. <ul>
  239. <li><strong>BIER (Bit Index Explicit Replication)</strong></li></ul>
  240. <ul>
  241. <ul>
  242. <li>An alternative method of multicast forwarding</li><li>Status: confirmed=
  243. </li><li>Champions:<br>
  244. Greg Shepherd (shep) &lt;<a href=3D"mailto:shep@cisco.com">shep@cisco.com</=
  245. a>&gt;<br>
  246. IJsbrand Wijnands (iwijnand) &lt;<a href=3D"mailto:ice@cisco.com">ice@cisco=
  247. .com</a>&gt;</li><li>IETF working group charter:&nbsp;<a href=3D"https://da=
  248. tatracker.ietf.org/wg/bier/charter/" style=3D"color: purple;">https://datat=
  249. racker.ietf.org/wg/bier/charter/</a><br>
  250. <br>
  251. </li></ul>
  252. <li><strong>HTTP/2.0</strong>
  253. <ul>
  254. <li><a href=3D"https://datatracker.ietf.org/wg/httpbis/charter/" style=3D"c=
  255. olor: purple;">IETF Charter Hypertext Transfer Protocol (httpbis)</a></li><=
  256. li>Champions:<br>
  257. Mark Nottingham &lt;<a href=3D"mailto:mnot@mnot.net">mnot@mnot.net</a>&gt;&=
  258. nbsp;&nbsp;<br>
  259. <br>
  260. </li></ul>
  261. </li><li><strong>NETCONF/YANG, I2RS, OpenDaylight</strong>
  262. <ul>
  263. <li>Working with NETCONF/YANG devices and models in I2RS and OpenDaylight</=
  264. li><li>Champions:<br>
  265. Benoit Claise &lt;<a href=3D"mailto:bclaise@cisco.com">bclaise@cisco.com</a=
  266. >&gt;<br>
  267. Jan Medved (jmedved) &lt;<a href=3D"mailto:jmedved@cisco.com">jmedved@cisco=
  268. .com</a>&gt;<br>
  269. Ignas Bagdonas &lt;<a href=3D"mailto:ibagdona.ietf@gmail.com">ibagdona.ietf=
  270. @gmail.com</a>&gt;<br>
  271. <br>
  272. </li></ul>
  273. </li><li><strong>NETVC and Daala</strong>
  274. <ul>
  275. <li>Open source, royalty free video codec, video compression</li><li>Daala =
  276. Project:&nbsp;<a href=3D"https://xiph.org/daala/" style=3D"color: purple;">=
  277. https://xiph.org/daala/</a></li><li>Proposed IETF working group:&nbsp;<a hr=
  278. ef=3D"https://datatracker.ietf.org/wg/netvc/charter/" style=3D"color: purpl=
  279. e;">Internet Video Codec (netvc)</a></li><li>Champions:<br>
  280. Timothy B. Terriberry &lt;<a href=3D"mailto:tterriberry@mozilla.com">tterri=
  281. berry@mozilla.com</a>&gt;<br>
  282. Jack Moffitt &lt;<a href=3D"mailto:jmoffitt@mozilla.com">jmoffitt@mozilla.c=
  283. om</a>&gt;<br>
  284. <br>
  285. </li></ul>
  286. </li><li><strong>RIOT (OS for internet of things)&nbsp;</strong>
  287. <ul>
  288. <li><a href=3D"http://www.riot-os.org/" style=3D"color: purple;">http://www=
  289. .riot-os.org/</a></li><li>Information centric networking for IoT: Experimen=
  290. ts with NDN in the Wild:&nbsp;<a href=3D"http://conferences2.sigcomm.org/ac=
  291. m-icn/2014/papers/p77.pdf" style=3D"color: purple;">http://conferences2.sig=
  292. comm.org/acm-icn/2014/papers/p77.pdf</a></li><li>Champions:<br>
  293. Matthias Waehlisch &lt;<a href=3D"mailto:m.waehlisch@fu-berlin.de">m.waehli=
  294. sch@fu-berlin.de</a>&gt;<br>
  295. Emmanuel Baccelli &lt;<a href=3D"mailto:Emmanuel.Baccelli@inria.fr">Emmanue=
  296. l.Baccelli@inria.fr</a>&gt;<br>
  297. Oliver Hahm &lt;<a href=3D"mailto:oliver.hahm@inria.fr">oliver.hahm@inria.f=
  298. r</a>&gt;, a.k.a. Oleg<br>
  299. <br>
  300. </li></ul>
  301. </li><li><strong>SFC in OpenDaylight&nbsp;</strong>
  302. <ul>
  303. <li>Service function chaining with OpenDaylight</li><li>Champions:<br>
  304. Reinaldo Penno &lt;<a href=3D"mailto:rapenno@gmail.com">rapenno@gmail.com</=
  305. a>&gt;<br>
  306. <br>
  307. </li></ul>
  308. </li><li><strong>SPUD (Substrate Protocol Underneath Datagrams)&nbsp;</stro=
  309. ng>
  310. <ul>
  311. <li>Provide mechanism for applications at the end and boxes along the path =
  312. to explicitly declare their assumptions and intentions</li><li>Drafts:&nbsp=
  313. ;<a href=3D"https://tools.ietf.org/id/spud" style=3D"color: purple;">https:=
  314. //tools.ietf.org/id/spud</a></li><li>Open source library:&nbsp;<a href=3D"h=
  315. ttps://github.com/iptube/SPUDlib" style=3D"color: purple;">iptube/SPUDlib =
  316. =B7 GitHub</a></li><li>Champions:<br>
  317. Joe Hildebrand &lt;<a href=3D"mailto:jhildebr@cisco.com">jhildebr@cisco.com=
  318. </a>&gt;<br>
  319. Pal Martinsen &lt;<a href=3D"mailto:palmarti@cisco.com">palmarti@cisco.com<=
  320. /a>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;</li></ul>
  321. </li></ul>
  322. <div>Cheers,</div>
  323. </div>
  324. <div>Charles</div>
  325. </div>
  326. </div>
  327. </blockquote>
  328. </span>
  329. </body>
  330. </html>
  331.  
  332. --_000_D170CCBA4919Aeckelcuciscocom_--
  333.  
  334. --_004_D170CCBA4919Aeckelcuciscocom_
  335. Content-Type: text/plain; name="ATT00001.txt"
  336. Content-Description: ATT00001.txt
  337. Content-Disposition: attachment; filename="ATT00001.txt"; size=142;
  338. creation-date="Thu, 07 May 2015 15:06:44 GMT";
  339. modification-date="Thu, 07 May 2015 15:06:44 GMT"
  340. Content-ID: <FF14B9F699D9394AAA0C71A3812B5BF5@emea.cisco.com>
  341. Content-Transfer-Encoding: base64
  342.  
  343. X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCmhhY2thdGhv
  344. biBtYWlsaW5nIGxpc3QNCmhhY2thdGhvbkBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
  345. bWFpbG1hbi9saXN0aW5mby9oYWNrYXRob24NCg==
  346.  
  347. --_004_D170CCBA4919Aeckelcuciscocom_--
Add Comment
Please, Sign In to add comment