Re: [Qirg] Link layer draft on GitHub

Axel Dahlberg <E.A.Dahlberg@tudelft.nl> Mon, 29 April 2019 08:28 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 D8D521200C3 for <qirg@ietfa.amsl.com>; Mon, 29 Apr 2019 01:28:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.178
X-Spam-Level:
X-Spam-Status: No, score=-3.178 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MISSING_HEADERS=1.021, 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 gKsglwA4D_bv for <qirg@ietfa.amsl.com>; Mon, 29 Apr 2019 01:28:19 -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 41A0D1202F0 for <qirg@irtf.org>; Mon, 29 Apr 2019 01:28:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by amavis (Postfix) with ESMTP id 85FCDCC0090 for <qirg@irtf.org>; Mon, 29 Apr 2019 10:28:17 +0200 (CEST)
X-Virus-Scanned: amavisd-new at tudelft.nl
Received: from mailservice.tudelft.nl ([130.161.131.74]) by localhost (tudelft.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id wPzKh8OHsMaX for <qirg@irtf.org>; Mon, 29 Apr 2019 10:28:16 +0200 (CEST)
Received: from SRV218.tudelft.net (mailboxcluster.tudelft.net [131.180.6.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mx3.tudelft.nl (Postfix) with ESMTPS id 218ABCC0082 for <qirg@irtf.org>; Mon, 29 Apr 2019 10:28:16 +0200 (CEST)
Received: from SRV221.tudelft.net (131.180.6.21) by SRV218.tudelft.net (131.180.6.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521) id 15.1.1713.5; Mon, 29 Apr 2019 10:28:09 +0200
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; Mon, 29 Apr 2019 10:28:09 +0200
From: Axel Dahlberg <E.A.Dahlberg@tudelft.nl>
CC: "qirg@irtf.org" <qirg@irtf.org>
Thread-Topic: Link layer draft on GitHub
Thread-Index: AQHU/SCZ3rjoHomhSUeEU9RiFaihuaZSqmaAgAAExYA=
Date: Mon, 29 Apr 2019 08:28:09 +0000
Message-ID: <98E09201-1DFE-4905-9ACB-8BA664B504F2@tudelft.nl>
References: <85CE9BC5-E238-4D03-A63F-6B8D3198FCFC@tudelft.nl> <F1E8EFF81FCF1B46AA7CCA3CC4D5E18CA05022CB@TW-MBX-P03.cnesnet.ad.cnes.fr>
In-Reply-To: <F1E8EFF81FCF1B46AA7CCA3CC4D5E18CA05022CB@TW-MBX-P03.cnesnet.ad.cnes.fr>
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_98E092011DFE49059ACB8BA664B504F2tudelftnl_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/qirg/X98LWETZeUt8yJ_kS4TJDN5iNg0>
Subject: Re: [Qirg] Link layer draft on GitHub
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: Mon, 29 Apr 2019 08:28:22 -0000

Hi Patrick!

With multi-link do you mean a multipartite entangled state? (Like a GHZ-state https://en.wikipedia.org/wiki/Greenberger%E2%80%93Horne%E2%80%93Zeilinger_state<https://en.wikipedia.org/wiki/Greenberger–Horne–Zeilinger_state>?).

I think I’m not fully understanding your question. Let me try to explain what we mean here and see if it clears up your question. Lets say that A and B share two entangled pairs, i.e. A has two qubits q_A, q_A' and B has two qubits q_B, q_B’, where q_A and q_B are entangled and similarly q_A’ and q_B’. Lets now say that A and B want to perform some action which requires one entangled pair. Clearly they should use the qubits (q_A and q_B) or (q_A’ and q_B’) and not for example (q_A and q_B’). Now this entanglement identifier simply gives them a way to relate an abstract entangled pair to a qubit. I.e. they might have two entanglement ids EntID and EntID’, together with a mapping:

Node A:
{EntID: q_A, EntID': q_A’}

Node B:
{EntID: q_B, EntID': q_B’}

/Axel Dahlberg

On 29 Apr 2019, at 10:11, Gelard Patrick <Patrick.Gelard@cnes.fr<mailto:Patrick.Gelard@cnes.fr>> wrote:

Hi Axel,

- "Once an entangled pair has been generated, the nodes need to be able to agree on which qubits are involved in which entangled pair in order to use it, thus another main task of the link
layer is to provide an entanglement identifier."
- "For a successful request, provide an entanglement identifier to allow higher layers to use identify the entangled pair in the network without the need for further communication."

In the case of multi-link, doesn't quantum indiscernibility lead to difficulties in identifying qubits ?

Thanks
/Patrick

De : Qirg <qirg-bounces@irtf.org<mailto:qirg-bounces@irtf.org>> De la part de Axel Dahlberg
Envoyé : samedi 27 avril 2019 19:43
À : qirg@irtf.org<mailto:qirg@irtf.org>
Objet : [Qirg] Link layer draft on GitHub

Dear Qirgers!

I just wanted to inform you that the draft defining the link layer service and interface in a quantum network is now also on GitHub such we can easily keep track of open issues, todos and changes.

Feel free to add issues or make pull requests.

You can find the repo here:
https://github.com/SoftwareQuTech/draft-dahlberg-qirg-ll-quantum

/Axel Dahlberg