IETF Logo Mail Archive

[Qirg] Entanglement path computation

Kireeti Kompella <kireeti.ietf@gmail.com> Wed, 20 March 2024 04:16 UTC

Return-Path: <kireeti.ietf@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 87A03C14F749 for <qirg@ietfa.amsl.com>; Tue, 19 Mar 2024 21:16:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.212
X-Spam-Level:
X-Spam-Status: No, score=-6.212 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, MIME_HTML_ONLY=0.1, MIME_HTML_ONLY_MULTI=0.001, MIME_QP_LONG_LINE=0.001, MPART_ALT_DIFF=0.79, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WQkWyhTSNi97 for <qirg@ietfa.amsl.com>; Tue, 19 Mar 2024 21:16:43 -0700 (PDT)
Received: from mail-oi1-x22a.google.com (mail-oi1-x22a.google.com [IPv6:2607:f8b0:4864:20::22a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4D59C14F74E for <qirg@irtf.org>; Tue, 19 Mar 2024 21:16:43 -0700 (PDT)
Received: by mail-oi1-x22a.google.com with SMTP id 5614622812f47-3c39579af51so1016278b6e.3 for <qirg@irtf.org>; Tue, 19 Mar 2024 21:16:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1710908202; x=1711513002; darn=irtf.org; h=to:message-id:subject:date:mime-version:from :content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=YHY9kDfL30agwM9DJOKVscXK58HOQmrNvzZhDn79yOY=; b=WCKsEBtK2dsLE9HvLJ9St2a3Dz07xfNjlb8gQnt12ZRyRmrKiYY4mQw8mBosn7kGEa LObEnH0BTkUeJdq+5rnUpd9GTlFFUftZtidyN2SsMZJond/S5UcCPsYak/pLR5PlydqO EDgQkJ4UiAON9vo72k78nckWEeCU9GlXJDuM6wM5Fecw3ElsqbfzC1hLkMoEACibe7s5 a0Iocm6+sRrEjtEVQq0I9T7FrfjKFYJdEphJVsUvldI3feotgXflA4XHDuIf2tUBZzXj nYS+DGZwnE2EBQNwiVW4qZiMRJXeGvYXVYUsAhSGl4GBPNmTvkIa8VW9ImtI92Hk/dAD JV+A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710908202; x=1711513002; h=to:message-id:subject:date:mime-version:from :content-transfer-encoding:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=YHY9kDfL30agwM9DJOKVscXK58HOQmrNvzZhDn79yOY=; b=ja3pA3D3PEnURmufSYqoPw504dCB0dk9b2vhAgKfuENnaFzhtVLBFt5JsMwlRaishm LDTJ5rNmKDS1Hi2PJxY+pf3b3y9XN9roSeO8gaTq+QI+pMSuCl8K6ba/H5zbOWCFC2RR eTxNm6YOdXg2PeCt6H8/uBl8DFbqAzaGuAqrE6q7YmOyn5T5AHAXc/l7r/zAt/K3kfIZ 7YateV6wddUwiy+R0GS3Xpe/FozlKeUrxx7eMTL+KX74dY3Qfw2GCczwIx0ClS+i1tBL pH0RVj7kZwrH7gvddRHjSHwMGjAQ/SFA+8zpNubznQMvDD3jct7GIpJWyjtUizbl/nEt dyDA==
X-Gm-Message-State: AOJu0YxZctcjeHHmeHX0kTZb4IVKQBQ1rIy7GoFrnxeTsRww2GvwSfEQ 1mG5hPuHQlJWl+PBC9WbHEV+y4CfTLRJnzSFMpve2hw6ahubx2FGbnkpwRtc4oY=
X-Google-Smtp-Source: AGHT+IEfsfWtmJFWj9AxiXdYWBB/pFSn57N/jWFoB8IDWT5p8d3OgViAvRb/6yEi18nRhWyGxP7WjQ==
X-Received: by 2002:a05:6358:6f9c:b0:17e:d8fe:be45 with SMTP id s28-20020a0563586f9c00b0017ed8febe45mr13841223rwn.8.1710908202048; Tue, 19 Mar 2024 21:16:42 -0700 (PDT)
Received: from smtpclient.apple ([2001:67c:370:128:75ce:c45e:7d0a:51af]) by smtp.gmail.com with ESMTPSA id m24-20020a63f618000000b005e43cb66a7asm9939582pgh.87.2024.03.19.21.16.41 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 19 Mar 2024 21:16:41 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-FF1C7A6E-9F35-4D85-AAB8-8EA7860C3E66"
Content-Transfer-Encoding: 7bit
From: Kireeti Kompella <kireeti.ietf@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Wed, 20 Mar 2024 14:16:28 +1000
Message-Id: <FBCA4AAD-269D-4F94-BE46-FBD809B6AE1F@gmail.com>
To: qirg@irtf.org
X-Mailer: iPhone Mail (21D61)
Archived-At: <https://mailarchive.ietf.org/arch/msg/qirg/jn1zr3Ig6HEM00efwzrwUe-G-tQ>
Subject: [Qirg] Entanglement path computation
X-BeenThere: qirg@irtf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Quantum Internet RG <qirg.irtf.org>
List-Unsubscribe: <https://mailman.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://mailman.irtf.org/mailman/listinfo/qirg>, <mailto:qirg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2024 04:16:47 -0000

Hi Michael,

Thanks for your talk on computing entanglement paths in quantum networks. The following draft (somewhat dormant for a while) is what I mentioned at the mike: 
“Advertising Entanglement Capabilities in Quantum Networks”
The basic idea is to advertise entanglement properties of nodes and links in a network so that computations such as those you talked about can be done. For example, a node’s distillation (purification) capabilities; a link’s time-fidelity tradeoff for entanglement operations. These properties are advertised via a link state protocol such as OSPF. There are no doubt more such properties that factor into effective entanglement computations. These properties should be useful for both distributed and centralized computations. 

Something like this draft could form the basis of future work; happy to help any way I can, as I’m sure my co-authors are as well. 

[Rod: please forward to Michael Cubeddu, in case he’s not on the QIRG mailing list. Thanks!]

Kireeti

v2.23.0 | Report a Bug | By Email