[{"author": "David Oran", "text": "My Safari decided to go CPU bond - i had to kill it, switch to Chrome, and rejoin.<br/>", "time": "2022-03-25T11:41:58Z"}, {"author": "Dirk Kutscher", "text": "Slides: <a href=\"https://datatracker.ietf.org/meeting/113/materials/slides-113-icnrg-ndn-for-data-intensive-science-experiments-n-dise-edmund-yeh-00\" rel=\"nofollow\">https://datatracker.ietf.org/meeting/113/materials/slides-113-icnrg-ndn-for-data-intensive-science-experiments-n-dise-edmund-yeh-00</a><br/>", "time": "2022-03-25T12:03:16Z"}, {"author": "Edmund Yeh", "text": "Need to go teach.&nbsp;&nbsp;Thanks for opportunity to present.&nbsp;&nbsp;Happy to answer questions offline.&nbsp;&nbsp;Edmund<br/>", "time": "2022-03-25T12:31:37Z"}, {"author": "Dirk Kutscher", "text": "Thanks Edmund!<br/>", "time": "2022-03-25T12:31:50Z"}, {"author": "Marie-Jose Montpetit", "text": "Edmund what is the name of your students<br/>", "time": "2022-03-25T12:43:48Z"}, {"author": "Colin Perkins", "text": "okay \u2013 makes sense<br/>", "time": "2022-03-25T12:43:57Z"}, {"author": "Matthias W\u00e4hlisch", "text": "@Marie-Jose, i suppose Yuanhao Wu<br/>", "time": "2022-03-25T12:45:49Z"}, {"author": "Dirk Kutscher", "text": "yes<br/>", "time": "2022-03-25T12:46:00Z"}, {"author": "Colin Perkins", "text": "Do the ICN ping and traceroute mechanisms require this?<br/>", "time": "2022-03-25T12:48:50Z"}, {"author": "Dirk Kutscher", "text": "no<br/>", "time": "2022-03-25T12:49:00Z"}, {"author": "Dirk Kutscher", "text": "MIIRC (what Dave was talking about)<br/>", "time": "2022-03-25T12:49:16Z"}, {"author": "Dirk Kutscher", "text": "the multipath congestion control work<br/>", "time": "2022-03-25T12:49:27Z"}, {"author": "Colin Perkins", "text": "ok<br/>", "time": "2022-03-25T12:50:04Z"}, {"author": "Dirk Kutscher", "text": "path steering is a little more invasive in terms of changing forwarder behavior<br/>", "time": "2022-03-25T12:51:15Z"}, {"author": "Colin Perkins", "text": "And I thought those words where \"but what about multicast?\"<br/>", "time": "2022-03-25T12:57:22Z"}, {"author": "Dirk Kutscher", "text": ";-)<br/>", "time": "2022-03-25T12:57:51Z"}, {"author": "David Oran", "text": "@thomas: this design is explicitly done to avoid reflection attacks - the Reflexive name prefix only identifies state at the consumer who issued the original interest, it isn't a regular name that can be forwarded anywhere else - it follows the breadcrumbs establishd by the initial interest<br/>", "time": "2022-03-25T13:12:03Z"}, {"author": "David Oran", "text": "@ken: There's still a new PIT entry created for the reflexive interest - it's just explicitly linked back to the PIT entry for the original interest, which is used to find the ingress face of that interest to use as the forwarding face for the reflexive interest.<br/>", "time": "2022-03-25T13:20:41Z"}, {"author": "David Oran", "text": "The tricky pat is ensuring that the OIt entry for the reflexive interest winds up in the same shard as the original interesrt, which is where the PIT token becomes critical.<br/>", "time": "2022-03-25T13:21:20Z"}, {"author": "David Oran", "text": "sorry for the typos: The tricky part is ensuring that the PIT entry for the reflexive interest winds up in the same shard as the original interest, which is where the PIT token becomes critical.<br/>", "time": "2022-03-25T13:22:23Z"}, {"author": "Colin Perkins", "text": "Thanks!<br/>", "time": "2022-03-25T13:32:39Z"}, {"author": "Kenneth Calvert", "text": "Thanks all!<br/>", "time": "2022-03-25T13:32:41Z"}, {"author": "Kazuaki Ueda", "text": "Thanks!<br/>", "time": "2022-03-25T13:32:41Z"}]