Re: [Qirg] multiplexing?

Bruno Rijsman <brunorijsman@gmail.com> Tue, 27 April 2021 09:19 UTC

Return-Path: <brunorijsman@gmail.com>
X-Original-To: qirg@ietfa.amsl.com
Delivered-To: qirg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD71C3A1C6D for <qirg@ietfa.amsl.com>; Tue, 27 Apr 2021 02:19:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1ETZpf_jQy2B for <qirg@ietfa.amsl.com>; Tue, 27 Apr 2021 02:19:04 -0700 (PDT)
Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF5B33A1C6F for <qirg@irtf.org>; Tue, 27 Apr 2021 02:19:03 -0700 (PDT)
Received: by mail-wr1-x432.google.com with SMTP id a4so58708505wrr.2 for <qirg@irtf.org>; Tue, 27 Apr 2021 02:19:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=7fQ5rVQzb7QyKDq125Kvat1FvcsNIa2JNpkdrdodyzQ=; b=KBYdL/Z8myKyzFGSvkcKGPVbWy3KvUzHl/3Ekzn9JgfCP1mEzmDKPjH9R7L1KamDAX C2htHBLd58S5RDWOPrLKC4MGdBImxu4mtMIDHqsL9o0TSqADwhvydrBjI6/PfCNgGwOR Jux8HV1DW0NxaA5qHNlv5Cmp3iFBu25PWNJQEhm0cau3B6T9iz4tmviekVsMsDTMtfs5 DYXYhaIB/EnCrUI775BCVu508Tk34xMOc44zMlHNcfniUtLz36iAxjW1HYcxQO/w+6NK TuDVv5sdmvT6dag9TrW/EK/+BSOUxmHJ94htgyIkugpo7PvaHGy8HDyy6D0926KvhUcm fZ6A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=7fQ5rVQzb7QyKDq125Kvat1FvcsNIa2JNpkdrdodyzQ=; b=EW+D2/YFGyVFJMIwlu9lZu9lYW9L+XUxSrfjsc4QKmBpKCkczX+O7Url10ecib5ZrN 7vscBXHC9h3fgXB7hYBbzbEvME10RNXLe/x7h90D2Fc6MQEuRG25wwjTUBMU+WFM4vjZ c3x8OYi076GzI/+KfgT/rvntNuPOnp6p8PNp+JfBzitExBudVOKbJlSxQtI4uOjRJSCd BlYLZA4ZnNiDpPTPbbteeFCDmGvVWCXN9z8DqnGrsZEFvIqRC1w2qbHdFfmGlIT9EGzS G2OQQjSGBa+Xhm9dIckzTZKRjxjKtC+fRQ3psiwS2Bn4HkbnAOreYGP0jjXZiUjHISFa R/lQ==
X-Gm-Message-State: AOAM533pc4SeXOZK9OSlF8cx2RbLhQwtdZD/5bkNK0CZYFbQArYG7Ji4 MQj8r7pc6pN7AJZkza8APqQ=
X-Google-Smtp-Source: ABdhPJxzczSwUerPbMIjNb2oydVbC116cQbPJNiVTlzP4Vnz2VEZ2pUgKzcNd49k6qIpvuCmsd1IRQ==
X-Received: by 2002:adf:fb87:: with SMTP id a7mr28430025wrr.58.1619515137249; Tue, 27 Apr 2021 02:18:57 -0700 (PDT)
Received: from [192.168.1.53] (168.15.19.109.rev.sfr.net. [109.19.15.168]) by smtp.gmail.com with ESMTPSA id e38sm324438wmp.21.2021.04.27.02.18.52 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 27 Apr 2021 02:18:56 -0700 (PDT)
From: Bruno Rijsman <brunorijsman@gmail.com>
Message-Id: <73821F62-0068-478B-86E2-63045ACC7D93@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_491F21B2-C7BF-4A1E-A8EA-68279E2CCF61"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Tue, 27 Apr 2021 11:18:48 +0200
In-Reply-To: <10CBC0C8-1F06-40CC-A7F6-884EE907661A@gmail.com>
Cc: Rodney Van Meter <rdv=40sfc.wide.ad.jp@dmarc.ietf.org>, qirg@irtf.org
To: Rodney Van Meter <rdv@sfc.wide.ad.jp>
References: <05E19233-CE34-487B-BB1B-F37577F0954A@sfc.wide.ad.jp> <51886A1A-BE2B-4A31-BAFC-0917AE5A5C2F@gmail.com> <5A703310-DF2E-4E29-BC00-FC54E7A133A6@sfc.wide.ad.jp> <10CBC0C8-1F06-40CC-A7F6-884EE907661A@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/qirg/jvTQQaFm1RVZV_pVXMNfNz2v3Lw>
Subject: Re: [Qirg] multiplexing?
X-BeenThere: qirg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Quantum Internet RG <qirg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/qirg>, <mailto:qirg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/qirg/>
List-Post: <mailto:qirg@irtf.org>
List-Help: <mailto:qirg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/qirg>, <mailto:qirg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Apr 2021 09:19:09 -0000

Would you like me to propose some specific language for the draft in a pull request?  (Not much, just one or two paragraphs mentioning the different kinds of multiplexing and why they are relevant.)

— Bruno

> On Apr 27, 2021, at 10:52 AM, Bruno Rijsman <brunorijsman@gmail.com> wrote:
> 
> Ah, yes, I was thinking of a more quantum-specific flavor of multiplexing: having multiple entanglements attempts going in parallel.  
> 
> If you need to do attempts sequentially (waiting for a round-trip time to receive the heralding result before starting the next attempt) entanglement generation is going to be very slow for reasonable distances.
> 
> For example, this paper https://arxiv.org/abs/1309.3202 <https://arxiv.org/abs/1309.3202> discusses spectral multiplexing where parallelism is achieved spectrally.
> 
> Or in NV centers parallelism (multiplexing) can be achieved by moving the communication qubit to a storage qubit to free up the communication qubit for the next entanglement attempt before the previous attempt was finished, i.e. before the heralding result was received (there is a paper on this, but I can’t locate it just right now).
> 
> But you are right, statistical muxing vs TDM muxing vs WDM muxing are also important considerations in quantum networks.
> 
> You need some TDM-ish clock synchronization to achieve indistinguishable photon arrivals at the heralding midpoint.  If you are also doing “parallelism” multiplexing in the sense of the start of this e-mail, then this almost inevitably leads to some sort of “time slot” concept.
> 
> And it is also often highly desirable (but not always practical) to WDM-mux the classical control channel onto the same fiber as the quantum data channel (and possibly even other classical data channels) to avoid having to use multiple fibers.
> 
> — Bruno
> 
>> On Apr 27, 2021, at 10:39 AM, Rodney Van Meter <rdv@sfc.wide.ad.jp <mailto:rdv@sfc.wide.ad.jp>> wrote:
>> 
>> Mmm, one problem is that it is used at many levels, and perhaps you and I are using it in different ways here.  I’m thinking of stat mux v. circuit switching, a very networky thing, but it’s also used to refer to frequency allocation in WDM and the quantum folks also use it to mean being able to connect multiple qubit memories to a single optical channel.
>> 
>> Rodney Van Meter
>> rdv@sfc.wide.ad.jp <mailto:rdv@sfc.wide.ad.jp>
>> Professor, Faculty of Environment and Information Studies, Keio University, Japan
>> 
>>> On Apr 27, 2021, at 17:35, Bruno Rijsman <brunorijsman@gmail.com> wrote:
>>> 
>>> I vote for updating the draft to mention multiplexing.
>>> 
>>> It is too important of a concept for achieving practically usable entanglement rates.
>>> 
>>> — Bruno
>>> 
>>>> On Apr 27, 2021, at 9:35 AM, Rodney Van Meter <rdv=40sfc.wide.ad.jp@dmarc.ietf.org> wrote:
>>>> 
>>>> Wojtek,
>>>> 
>>>> Just dinking around I noticed that we never use the word “multiplexing” in our I-D.
>>>> https://datatracker.ietf.org/doc/draft-irtf-qirg-principles/
>>>> We do refer to “resource management”.
>>>> 
>>>> QIRGers, what do y’all think?  Should we use muxing in some form in this to discuss the problem of managing access to resources along the path?
>>>> 
>>>> —Rod
>>>> 
>>>> P.S. Yes, we said in IETF a few weeks ago that this would be sent to IRSG by now, but we haven’t gotten it sent. I do think it’s ready.
>>>> 
>>>> Rodney Van Meter
>>>> rdv@sfc.wide.ad.jp
>>>> Professor, Faculty of Environment and Information Studies, Keio University, Japan
>>>> 
>>>> _______________________________________________
>>>> Qirg mailing list
>>>> Qirg@irtf.org
>>>> https://www.irtf.org/mailman/listinfo/qirg
>>> 
>> 
>