Good Morning! To all local and remote participants!
", "time": "2023-11-07T08:32:12Z"}, {"author": "\ud835\uddb6\ud835\uddbe\ud835\uddc7\ud835\uddbd\ud835\uddd2 \ud835\udda5\ud835\uddcb\ud835\uddbe\ud835\uddd3\ud835\uddba\ud835\uddc1", "text": "good morning
", "time": "2023-11-07T08:33:59Z"}, {"author": "Rodney Van Meter", "text": "Good morning, all!
\n(Or, good evening or afternoon...)
For those not on the QIRG mailing list (you should be! It's not very high traffic, and it's good.), I posted the following questions on Sunday about this draft (speaking personally):
\nI know it's heavily informed by your QKD work, but can you say a
\n little (here on the list, no need put it in the document yet) on
\n your view of the relevance of this document to more general-purpose,
\n entangled quantum networks?
Likewise, what about the relationship with <whisper> ITU
\n </whisper>? You have cited (and probably worked on) a number of
\n those QKD-specific documents; how do you see the IETF role v. the
\n ITU role?
My _impression_ of the ITU work is that it is strongest at the
\n physical layer and above the application layer, at the key
\n management functionality. This leaves a big gap in the middle
\n layers -- L3-4 ish, give or take. Does that match your experience?
\"Quantum forwarding plane\" is probably the wrong name. For
\n entangled networks, there really is no forwarding; the service
\n provided by the network is creation of E2E entanglement to be
\n consumed by applications. That is very much a distributed process,
\n nothing at all like the Internet's store-and-forward of packets.
\n (Actually, I would expect this aspect to be true for multihop,
\n trusted intermediate node QKD, as well.)
Going back to point 1, how will this architecture support the
\n stages of evolution of a Quantum Internet as outlined by Wehner,
\n Hanson, Elkouss (Science)?
Questioner is Shota Nagayama (Shota, use the online tool to raise your hand!)
", "time": "2023-11-07T08:55:22Z"}, {"author": "Martin Stiemerling", "text": "thx
", "time": "2023-11-07T08:55:28Z"}, {"author": "Rodney Van Meter", "text": "", "time": "2023-11-07T09:05:20Z"}, {"author": "Rodney Van Meter", "text": "Questioner is Massimiliano Pala
", "time": "2023-11-07T09:09:37Z"}, {"author": "Rodney Van Meter", "text": "Questioner is Scott Fluhrer
", "time": "2023-11-07T09:14:21Z"}, {"author": "Rodney Van Meter", "text": "https://www.ce.cit.tum.de/en/lti/tqsd/
", "time": "2023-11-07T09:16:52Z"}, {"author": "Alexandr Railean", "text": "please speak closer to the mic
", "time": "2023-11-07T09:18:50Z"}, {"author": "Rodney Van Meter", "text": "https://arxiv.org/abs/0801.2840
", "time": "2023-11-07T09:33:00Z"}, {"author": "Rodney Van Meter", "text": "First questioner was Scott Fluhrer
", "time": "2023-11-07T09:33:19Z"}, {"author": "Rodney Van Meter", "text": "Current questioner is Diego Lopez
", "time": "2023-11-07T09:33:28Z"}, {"author": "Rodney Van Meter", "text": "COmmenter was ? Choi
", "time": "2023-11-07T09:34:55Z"}, {"author": "Rodney Van Meter", "text": "Questioner is Scott Fluhrer
", "time": "2023-11-07T09:47:53Z"}, {"author": "Rodney Van Meter", "text": "Questioner is Diego Lopez
", "time": "2023-11-07T09:48:56Z"}, {"author": "Rodney Van Meter", "text": "Questioner is JinHyeock Choi
", "time": "2023-11-07T09:53:11Z"}, {"author": "Rodney Van Meter", "text": "Questioner is Shota Nagayama
", "time": "2023-11-07T09:55:19Z"}, {"author": "Greg Choules", "text": "My question/comment was going to be (because i'll have forgotten it by the end), if it turns out that we need some new kind of network addressing, please consider how that will affect mapping of service names to addresses in DNS; if DNS is even relevant anymore.
", "time": "2023-11-07T10:00:43Z"}, {"author": "Rodney Van Meter", "text": "Excellent question
", "time": "2023-11-07T10:01:05Z"}, {"author": "Rodney Van Meter", "text": "@Marcello Caleffi isn't in this stream at the moment...
", "time": "2023-11-07T10:02:14Z"}, {"author": "Marcello Caleffi", "text": "here I am
", "time": "2023-11-07T10:09:50Z"}, {"author": "Rodney Van Meter", "text": "@Greg Choules posted his question here, if we don't get to it at the end of the session you can answer here.
", "time": "2023-11-07T10:10:44Z"}, {"author": "Joaquin Chung", "text": "I've a similar concern as Greg, I think a quantum control plane (with quantum address) must be motivated/driven by the applications it will support. I'm not sure how relevant this is, the discussion reminded me of this paper https://arxiv.org/abs/2207.14336
", "time": "2023-11-07T10:12:57Z"}, {"author": "Marcello Caleffi", "text": "Greg Choules ha scritto:
\n\n\nMy question/comment was going to be (because i'll have forgotten it by the end), if it turns out that we need some new kind of network addressing, please consider how that will affect mapping of service names to addresses in DNS; if DNS is even relevant anymore.
\n
no clear answer yet
\nbut my feeling is that for \"classical names\" (i.e., classical resources) you'll keep using DNS and classical IP... afterall any quantum node will likely have a classical channel and you'll reach it via classical packet switching
conversely, for quantum names we might need to think about (and maybe redefine) the same concept of name: what is that you seek in a quantum network? a quantum node? a quantum resource?
", "time": "2023-11-07T10:13:16Z"}, {"author": "Joaquin Chung", "text": "Now a comment why we're stuck with IPv4 for more than 40 years is more operational than technical. IPv6 has been around for more that 25 years, still not pervasive. Named Data networking is been around for more than 10 years and still not out of the labs
", "time": "2023-11-07T10:16:10Z"}, {"author": "Marcello Caleffi", "text": "Joaquin Chung ha scritto:
\n\n\nI've a similar concern as Greg, I think a quantum control plane (with quantum address) must be motivated/driven by the applications it will support. I'm not sure how relevant this is, the discussion reminded me of this paper https://arxiv.org/abs/2207.14336
\n
an application requiring quantum control plane will definitely be the \"killer\" application..
\nstill, IP addressing has been defined in a time period where applications were very vague, and researchers were investigating scalable routing addressing not because they had a global-scale network but because they though it was a good research topic
I have three (personal, not chair) announcements:
\nWorkshop for Quantum Repeaters and Networks 4
\nSeptember 11-13, 2024
\nMontreux, Switzerland
\nlimited to ~100 attendees
\nhttps://www.wqrn.org/
Undergraduate texbook on Quantum Communications
\nMichal Hajdusek, Rodney Van Meter
\nCreative Commons CC-BY-SA license
\nhttps://arxiv.org/abs/2311.02367
Shota Nagayama and I are considering writing a survey on routing for
\nquantum networks. If you are interested in collaborating on this,
\nplease contact one of us.
Joaquin Chung ha scritto:
\n\n\nNow a comment why we're stuck with IPv4 for more than 40 years is more operational than technical. IPv6 has been around for more that 25 years, still not pervasive. Named Data networking is been around for more than 10 years and still not out of the labs
\n
yes but the fundamental principles of IP addressing is the same since 50 years: give a look it and tell me the difference between IPv6 and Kleinrock scheme https://www.sciencedirect.com/science/article/pii/0376507577900022
", "time": "2023-11-07T10:17:56Z"}, {"author": "Joaquin Chung", "text": "Thanks, will take a look.
", "time": "2023-11-07T10:19:57Z"}, {"author": "Marcello Caleffi", "text": "Joaquin Chung ha scritto:
\n\n\nThanks, will take a look.
\n
sure, let's talk about offline in person
", "time": "2023-11-07T10:20:25Z"}]