IETF Logo Mail Archive

[Qirg] Naming and addressing in a quantum network

Axel Dahlberg <E.A.Dahlberg@tudelft.nl> Thu, 28 March 2019 11:55 UTC

Return-Path: <E.A.Dahlberg@tudelft.nl>
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 532841202B2 for <qirg@ietfa.amsl.com>; Thu, 28 Mar 2019 04:55:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 fQg3uY6rvXxQ for <qirg@ietfa.amsl.com>; Thu, 28 Mar 2019 04:55:25 -0700 (PDT)
Received: from mailservice.tudelft.nl (mailservice.tudelft.nl [130.161.131.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 601DE120279 for <qirg@irtf.org>; Thu, 28 Mar 2019 04:55:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by amavis (Postfix) with ESMTP id 6501140093 for <qirg@irtf.org>; Thu, 28 Mar 2019 12:55:23 +0100 (CET)
X-Virus-Scanned: amavisd-new at tudelft.nl
Received: from mailservice.tudelft.nl ([130.161.131.69]) by localhost (tudelft.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id HzmM-deC8YiU for <qirg@irtf.org>; Thu, 28 Mar 2019 12:55:21 +0100 (CET)
Received: from SRV223.tudelft.net (srv223.tudelft.net [131.180.6.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mx1.tudelft.nl (Postfix) with ESMTPS id CDDBB4009D for <qirg@irtf.org>; Thu, 28 Mar 2019 12:55:21 +0100 (CET)
Received: from SRV221.tudelft.net (131.180.6.21) by SRV223.tudelft.net (131.180.6.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521) id 15.1.1713.5; Thu, 28 Mar 2019 12:55:15 +0100
Received: from SRV221.tudelft.net ([fe80::1db0:d95:8ac1:d760]) by SRV221.tudelft.net ([fe80::1db0:d95:8ac1:d760%13]) with mapi id 15.01.1713.004; Thu, 28 Mar 2019 12:55:15 +0100
From: Axel Dahlberg <E.A.Dahlberg@tudelft.nl>
To: "qirg@irtf.org" <qirg@irtf.org>
Thread-Topic: Naming and addressing in a quantum network
Thread-Index: AQHU5V0b9bRMiofLhUqMnI+iGmZ4rg==
Date: Thu, 28 Mar 2019 11:55:15 +0000
Message-ID: <65F6DAF7-0122-4F57-A5F5-C0EF0DEC04CB@tudelft.nl>
Accept-Language: en-GB, nl-NL, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3445.9.1)
Content-Type: multipart/alternative; boundary="_000_65F6DAF701224F57A5F5C0EF0DEC04CBtudelftnl_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/qirg/QhYfVvsc8G6m-I2cVk62Yh909-U>
Subject: [Qirg] Naming and addressing in a quantum network
X-BeenThere: qirg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Quantum Internet \(proposed\) 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: Thu, 28 Mar 2019 11:55:29 -0000

Hi qirgers!

In the QIRG meeting on Tuesday there was some questions regarding naming and addressing in a quantum network and in particular what the “Remote Node ID” refers to in the draft draft-dahlberg-ll-quantum-01 (https://tools.ietf.org/html/draft-dahlberg-ll-quantum-01) on the service of a link layer in a quantum network. I would like to continue the discussion here on the mailing list. Any feedback or thought are highly appreciated, especially from those of you who have experience on these topics. I have knowledge about the quantum but not so much about naming and addressing.

In the draft the Remote Node ID, used in the CREATE message for requesting entanglement generation, is needed to identify the remote node which the higher layer wants to create entanglement with. This is useful if there are multiple nodes connected to a single heralding station (automated repeater) where photons can be interfered, in a star-like topology. There is also another use for the identifiers of the nodes in the network, which concern identifying entanglement. The link layer provides a sequence number for the generated entanglement contained in the OK message. However, this sequence number SEQ is only unique with respect to the link (at least during the lifetime of the entangled pair). Together with IDs of the nodes holding the entanglement (ID_A and ID_B), the higher layer can construct an entanglement identifier as (ID_A, ID_B, SEQ) which is unique in the network and can be used by an entanglement manager. Note though that this assumes that the node IDs are unique in the network.

Looking forward to your thoughts and feedback!

/Axel Dahlberg

v2.23.0 | Report a Bug | By Email