Re: [Qirg] multiplexing?

Bruno Rijsman <brunorijsman@gmail.com> Tue, 27 April 2021 08:53 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 16FEA3A1B57 for <qirg@ietfa.amsl.com>; Tue, 27 Apr 2021 01:53:15 -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=ham 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 SD4tIhr8V5Kx for <qirg@ietfa.amsl.com>; Tue, 27 Apr 2021 01:53:10 -0700 (PDT)
Received: from mail-wr1-x431.google.com (mail-wr1-x431.google.com [IPv6:2a00:1450:4864:20::431]) (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 D08C73A1B54 for <qirg@irtf.org>; Tue, 27 Apr 2021 01:53:09 -0700 (PDT)
Received: by mail-wr1-x431.google.com with SMTP id l2so6270013wrm.9 for <qirg@irtf.org>; Tue, 27 Apr 2021 01:53:09 -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=sX6WB4jLu4UGZ9B1NfzxxrHaOFuiMV5aMdtBlF2RQPc=; b=BKr9o4pVMR4Sp20ACEJi57XGmNerwaySbpYs7mkVNcBFRx4oFZ+C1ED+0FwljqGytB LdyX2fG9usI9R3ecNnB0KTmRM6s5F0ZBHR3WRj95U/YP5Urhlp1D/arY0uoIvXGMHVoC 2mcgu1n0JU69AY4zsNNx0E5DFl7Zm9c3dT6BwuKpXFMMoHWqy880huAPqsp0/eUDO35Z xqc2iKq0t1LKyn6is4WJ9aCHTSnS1qqimKLFfrNF4PaD/IBYfcnwQVCgOO693uVcTyFZ 1uqf1n3RpxsJRcxEfnW6Li04POA2AlgBYU9HKIaHaTpWraUJWMqeg9ERuBXUHbxi/ukY sogw==
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=sX6WB4jLu4UGZ9B1NfzxxrHaOFuiMV5aMdtBlF2RQPc=; b=UlZwJdchppsd+e2B323TnShvv+PXW7UU6vQPDxAs9fbMhh7GTx+58Z5NsWYtC3sClD ZL58+cTGqepKGpd1c7dJqhjgX1sxsL5t/mT9PKhOTG3fANVJl371eTP0Ydk9TPVLSqeq imD6CSvu4/dy4U9SVcze/YJVW1WDh92HZylL4HiOp2c6YL+sXxL71hRuK92lMh9gFalE quxYTKWNXfr+N4WJahGRq4jXz8rACJL1TvbAEpZn7dvmJyehpXvHTBsGbbyGqA7aIMWE 6dDvZOiEJgRHLeiAzcWXQAmC9cWIBssVb6iK2ne3E89diXgq9k2mmF42CKvM2HV2er5P oCTQ==
X-Gm-Message-State: AOAM530tIKd0UxxhznElfKUwFLncwB7k2G0zPi4j1S0oi6O2vI4DHru6 hGBc/1CsJ7dDxRiZRov1TVIlmoUIUWHyNwzv
X-Google-Smtp-Source: ABdhPJxwb+6gynmzaUNmE7k0fjp6yU4470EJznqCSkC2iWLRicbrwgJ4jASP8zZSyhyzaU23SGn/mw==
X-Received: by 2002:a5d:53c9:: with SMTP id a9mr12996917wrw.108.1619513587347; Tue, 27 Apr 2021 01:53:07 -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 a22sm2991114wrc.59.2021.04.27.01.53.02 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 27 Apr 2021 01:53:07 -0700 (PDT)
From: Bruno Rijsman <brunorijsman@gmail.com>
Message-Id: <10CBC0C8-1F06-40CC-A7F6-884EE907661A@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0BB61FFF-9F47-4C40-90A9-7686D9AADBE0"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Tue, 27 Apr 2021 10:52:58 +0200
In-Reply-To: <5A703310-DF2E-4E29-BC00-FC54E7A133A6@sfc.wide.ad.jp>
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>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/qirg/dFfa7cVaguxi96TiJtvWCfMBY2g>
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 08:53:15 -0000

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> 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
> 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
>> 
>