[{"author": "Oscar Garcia", "text": "Hello all!<br/>", "time": "2022-03-22T13:31:37Z"}, {"author": "BEHCET SARIKAYA", "text": "Hello Oscar<br/>", "time": "2022-03-22T13:32:11Z"}, {"author": "Jorge Amodio", "text": "I think the notes link is still pointing to CodiMD<br/>", "time": "2022-03-22T13:34:44Z"}, {"author": "Jorge Amodio", "text": "The link on the agenda works fine<br/>", "time": "2022-03-22T13:35:25Z"}, {"author": "Joerg Ott", "text": "yay!<br/>", "time": "2022-03-22T13:35:46Z"}, {"author": "Jorge Amodio", "text": "<a href=\"https://notes.ietf.org/notes-ietf-113-dtn\" rel=\"nofollow\">https://notes.ietf.org/notes-ietf-113-dtn</a><br/>", "time": "2022-03-22T13:36:08Z"}, {"author": "Joerg Ott", "text": "no audio<br/>", "time": "2022-03-22T13:37:15Z"}, {"author": "Hang Shi", "text": "No audio<br/>", "time": "2022-03-22T13:37:16Z"}, {"author": "Jorge Amodio", "text": "yes<br/>", "time": "2022-03-22T13:38:39Z"}, {"author": "Jorge Amodio", "text": "perfect<br/>", "time": "2022-03-22T13:38:46Z"}, {"author": "Marc Blanchet", "text": "I'm never tired to hear Vint<br/>", "time": "2022-03-22T13:53:16Z"}, {"author": "Jorge Amodio", "text": "Vint bring his own cheer leaders<br/>", "time": "2022-03-22T13:53:44Z"}, {"author": "Oscar Garcia", "text": "<a href=\"https://ipnsig.org/home/\" rel=\"nofollow\">https://ipnsig.org/home/</a><br/>", "time": "2022-03-22T13:55:04Z"}, {"author": "Oscar Garcia", "text": "<a href=\"https://ipnsig.org/projects/\" rel=\"nofollow\">https://ipnsig.org/projects/</a><br/>", "time": "2022-03-22T13:56:17Z"}, {"author": "Stuart Card", "text": "I'd rather not come to the mic to ask this as that takes valuable time, but if any of the chairs wants to relay this question: Would use of the \"DTN at home\" test net (or another instance using same protocols and code) for terrestrial disaster comms be welcomed?<br/>", "time": "2022-03-22T13:56:20Z"}, {"author": "Juliusz Chroboczek", "text": "I'd be interested about disaster comms too :-)<br/>", "time": "2022-03-22T13:56:41Z"}, {"author": "Rick Taylor", "text": "Disaster comms is really the \"other\" use-case.<br/>", "time": "2022-03-22T13:57:22Z"}, {"author": "Edward Birrane", "text": "Yes - DTN is being considered for disaster comms.<br/>", "time": "2022-03-22T13:57:23Z"}, {"author": "Juliusz Chroboczek", "text": "I'd be grateful for pointers to publications on the subject.<br/>", "time": "2022-03-22T13:57:48Z"}, {"author": "Jorge Amodio", "text": "One of the projects on IPNSIG address the application of DTN for disaster situations<br/>", "time": "2022-03-22T13:57:55Z"}, {"author": "Marc Blanchet", "text": "we demonstrated streaming video over DTN in a CCSDS session many years ago with our implementation ;-)<br/>", "time": "2022-03-22T13:58:38Z"}, {"author": "Jorge Amodio", "text": "Other applications are IoT, mobile comm with high disruption, battle field comm<br/>", "time": "2022-03-22T13:58:46Z"}, {"author": "BEHCET SARIKAYA", "text": "I would like to know if dtn tried QUIC as transport protocol?<br/>", "time": "2022-03-22T13:59:29Z"}, {"author": "Rick Taylor", "text": "Not yet - but it can fit...<br/>", "time": "2022-03-22T13:59:48Z"}, {"author": "Oscar Garcia", "text": "I shared links to IPNSIG home page where you can join and also contact the working groups.<br/>", "time": "2022-03-22T14:00:04Z"}, {"author": "BEHCET SARIKAYA", "text": "Thanks Rick<br/>", "time": "2022-03-22T14:00:21Z"}, {"author": "Jorge Amodio", "text": "Thanks Vinit<br/>", "time": "2022-03-22T14:00:35Z"}, {"author": "Brian Sipos", "text": "@Behcet an indirect way to leverage QUIC would be an HTTP3-based CL which would operate over QUIC transport. As a side effect this could be usable with HTTP1/2.<br/>", "time": "2022-03-22T14:01:49Z"}, {"author": "Ronald in 't Velt", "text": "Define a TAPS CL and be done with it :-)<br/>", "time": "2022-03-22T14:02:43Z"}, {"author": "Rick Taylor", "text": "Absolutely!<br/>", "time": "2022-03-22T14:03:13Z"}, {"author": "Rick Taylor", "text": "We have a TCP Convergance Layer (DTN 'adapter'), we have a UDP CL in progress, and a QUIC CL is an obvious next step<br/>", "time": "2022-03-22T14:04:09Z"}, {"author": "Juliusz Chroboczek", "text": "What's weird about source routing?<br/>", "time": "2022-03-22T14:18:52Z"}, {"author": "Jorge Amodio", "text": "The source may not be available<br/>", "time": "2022-03-22T14:19:51Z"}, {"author": "Rick Taylor", "text": "Source routing has always been seen as an oddball in the IETF as it sort defeats routing in some cases.&nbsp;&nbsp;It was popular for a while, became unpopular, but is coming back into vogue.&nbsp;&nbsp;Read into that what you wish ;)<br/>", "time": "2022-03-22T14:24:11Z"}, {"author": "Stuart Card", "text": "Although there were successful deployments of DiffServ -- we did one.<br/>", "time": "2022-03-22T14:36:42Z"}, {"author": "Edward Birrane", "text": "If there are published experiences detailing limitations with DiffServ please point me to them.<br/>", "time": "2022-03-22T14:38:13Z"}, {"author": "Rick Taylor", "text": "The problem with Differv (as I see it) isn't the implementation, it's that it's an honor system<br/>", "time": "2022-03-22T14:38:32Z"}, {"author": "Oscar Garcia", "text": "I need to jump to another meeting. Thank you to the Chairs for the opportunity to show IPNSIG progress with Vint's talk.<br/>", "time": "2022-03-22T14:38:54Z"}, {"author": "Rick Taylor", "text": "Within an administrative zone, it works excellently<br/>", "time": "2022-03-22T14:38:58Z"}, {"author": "Rick Taylor", "text": "@oscar - Please check my last slides - they are relevant to SANA/IPNSIG<br/>", "time": "2022-03-22T14:39:21Z"}, {"author": "Oscar Garcia", "text": "@rick I will email you to get the link. Thank You.<br/>", "time": "2022-03-22T14:40:33Z"}, {"author": "Rick Taylor", "text": "@oscar - <a href=\"https://datatracker.ietf.org/doc/slides-113-dtn-on-endpoint-id-schemas/\" rel=\"nofollow\">https://datatracker.ietf.org/doc/slides-113-dtn-on-endpoint-id-schemas/</a><br/>", "time": "2022-03-22T14:43:16Z"}, {"author": "Ronald in 't Velt", "text": "It isn't called that anymore, is it?<br/>", "time": "2022-03-22T14:59:11Z"}, {"author": "Ronald in 't Velt", "text": "Oops<br/>", "time": "2022-03-22T14:59:14Z"}, {"author": "Ronald in 't Velt", "text": "New name is too restrictive, though.<br/>", "time": "2022-03-22T15:00:34Z"}, {"author": "Edward Birrane", "text": "Thought is that DTNMA as the informational document is OK. The data models and protocols that implement that architecture may be more expansively named.<br/>", "time": "2022-03-22T15:02:25Z"}, {"author": "Edward Birrane", "text": "But we are open to naming suggestions.<br/>", "time": "2022-03-22T15:02:34Z"}, {"author": "Rick Taylor", "text": "Especially if there is cross-over with MANET for example<br/>", "time": "2022-03-22T15:03:04Z"}, {"author": "Edward Birrane", "text": "Saying \"asynchronous\" caused confusion - we mean \"transport-layer asynchronous requiring autonomy\" and others see asynchronous and think \"REST-ful interfaces over TCP\".<br/>", "time": "2022-03-22T15:03:11Z"}, {"author": "Edward Birrane", "text": "There is no need to make a special case for bulk reports in DTNMA - we would have the same issue with traffic other than reports.<br/>", "time": "2022-03-22T15:10:18Z"}, {"author": "Edward Birrane", "text": "Part of management should be able to set policy to handle these cases and reports queued in message should be treated just as other queued messages.<br/>", "time": "2022-03-22T15:10:44Z"}, {"author": "Jorge Amodio", "text": "Is there any ANMS code available we can play with at IPNSIG ?<br/>", "time": "2022-03-22T15:12:40Z"}, {"author": "Edward Birrane", "text": "The ANMS team if working to open-source an alpha release shortly. Perhaps April.<br/>", "time": "2022-03-22T15:13:37Z"}, {"author": "Jorge Amodio", "text": "Thanks Ed<br/>", "time": "2022-03-22T15:13:51Z"}, {"author": "Edward Birrane", "text": "The idea is to gather early users who can both test the system, propose features, and be part of the support community for this.<br/>", "time": "2022-03-22T15:14:02Z"}, {"author": "Edward Birrane", "text": "This would be release of spiral 1 of 5 planned development spirals over the next 2 years, so we would have time to gather experiences and react to them.<br/>", "time": "2022-03-22T15:14:26Z"}, {"author": "Jorge Amodio", "text": "Is there any doc that talks about what are the requirements to run the system?<br/>", "time": "2022-03-22T15:14:54Z"}, {"author": "Edward Birrane", "text": "There are a few, and we can answer specific questions. The system is deployed as a series of docker containers<br/>", "time": "2022-03-22T15:15:26Z"}, {"author": "Jorge Amodio", "text": "Got it<br/>", "time": "2022-03-22T15:15:37Z"}, {"author": "Jorge Amodio", "text": "DNS uggghhhh<br/>", "time": "2022-03-22T15:26:03Z"}, {"author": "Jorge Amodio", "text": "you can't rely on DNS on the North pole of Mars<br/>", "time": "2022-03-22T15:26:58Z"}, {"author": "Ronald in 't Velt", "text": "Non-starter for non-singleton EIDs<br/>", "time": "2022-03-22T15:27:56Z"}, {"author": "Jorge Amodio", "text": "isn't out there a \"space\" IANA ?<br/>", "time": "2022-03-22T15:29:03Z"}, {"author": "Joshua Deaton", "text": "Question was going to be for verification the name being proposed to resolve to DNS is dtn://address correct?<br/>", "time": "2022-03-22T15:29:44Z"}, {"author": "Emery Annis", "text": "Do you think the dtn:/ schema, could be extended to support things like named data networking? or would that need a new schema<br/>", "time": "2022-03-22T15:30:06Z"}, {"author": "Stuart Card", "text": "I have some thoughts involving HF-ALE ids and DRIP DETs / HIP HHITs (which are IPv6 address compatible IDs, not locators, based on public keys).<br/>", "time": "2022-03-22T15:30:37Z"}, {"author": "Jorge Amodio", "text": "Great meeting !!<br/>", "time": "2022-03-22T15:30:51Z"}, {"author": "Ronald in 't Velt", "text": "Previous charter said not to touch 4838<br/>", "time": "2022-03-22T15:31:05Z"}, {"author": "Stuart Card", "text": "+1 @emery<br/>", "time": "2022-03-22T15:31:10Z"}, {"author": "Edward Birrane", "text": "There has been discussion of using extension blocks to carry annotative naming for NDN<br/>", "time": "2022-03-22T15:31:40Z"}, {"author": "Ronald in 't Velt", "text": "4 people left in the room<br/>", "time": "2022-03-22T15:31:41Z"}, {"author": "Felix Flentge", "text": "Yes, <a href=\"https://sanaregistry.org/\" rel=\"nofollow\">https://sanaregistry.org/</a><br/>", "time": "2022-03-22T15:32:02Z"}, {"author": "Rick Taylor", "text": "@Joshua - yes - when used externally, the name component of the dtn: EID should be DNS resolvable<br/>", "time": "2022-03-22T15:32:09Z"}, {"author": "Jorge Amodio", "text": ":thumbsup:<br/>", "time": "2022-03-22T15:32:20Z"}, {"author": "Ronny Bull", "text": "have a great afternoon/evening everyone great meeting!<br/>", "time": "2022-03-22T15:32:20Z"}, {"author": "Rick Taylor", "text": "Definitely need 2 sessions next time<br/>", "time": "2022-03-22T15:33:09Z"}, {"author": "Abdussalam Baryun", "text": "thanks all<br/>", "time": "2022-03-22T15:33:11Z"}]