IETF Logo Mail Archive

[Qirg] Similarities between RSVP IETF (RFC 2205) protocol and connection Setup in a Quantum Network

Gelard Patrick <Patrick.Gelard@cnes.fr> Tue, 19 November 2019 12:40 UTC

Return-Path: <Patrick.Gelard@cnes.fr>
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 C2E741208A4 for <qirg@ietfa.amsl.com>; Tue, 19 Nov 2019 04:40:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Level:
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_RATIO_04=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 Yidld1jbMuiN for <qirg@ietfa.amsl.com>; Tue, 19 Nov 2019 04:40:20 -0800 (PST)
Received: from mx2.cnes.fr (mx2.cnes.fr [194.199.174.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09312120891 for <qirg@irtf.org>; Tue, 19 Nov 2019 04:40:18 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.68,322,1569283200"; d="jpg'145?scan'145,208,145,217";a="30954968"
X-IPAS-Result: A2HpAQAM4dNd/wUBeAplHAEBAQEBBwEBEQEEBAEBgW0EAQELAYEbDXdZE3USKgqVPIc5gh+JRogHBAIHAQEBAQEBAQEBAwEcAQwGAQECAQGEQAKCJSQ3Bg4CEAEBAQQBAQEBAQUCAQECAmmEa0wBC4YoAQECAgEDAQYZCAFACwUNAQUQBQsBAQECCBEECQUQCgMCAQsUAw8BBA4EAQgGgxWCRgMOIA+vWIInGoQfAQMCg0UNghsKBoE2AYFkjEeBV4QOgRdHAQECAYFgBQcJgyuCLASVVoEEDo9lA1OGGC1BB4E8coI3g0sBgRcviW6CDYImdYlFhBMDi0GKcIIjgTWIOIITkRA9JIFYMxonTIJsUBGRCjAXFYhPhT9EMAGBHwiMfwGBDgEB
X-URL-LookUp-ScanningError: 1
From: Gelard Patrick <Patrick.Gelard@cnes.fr>
To: "qirg@irtf.org" <qirg@irtf.org>
CC: Rodney Van Meter <rdv=40sfc.wide.ad.jp@dmarc.ietf.org>, Frédéric Grosshans <frederic.grosshans@lip6.fr>
Thread-Topic: [Qirg] Similarities between RSVP IETF (RFC 2205) protocol and connection Setup in a Quantum Network
Thread-Index: AdWe1nZx1O+1wBKESW6pTEGonuuFnw==
Date: Tue, 19 Nov 2019 12:40:16 +0000
Message-ID: <F1E8EFF81FCF1B46AA7CCA3CC4D5E18CA0592812@TW-MBX-P03.cnesnet.ad.cnes.fr>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-tm-as-product-ver: SMEX-11.0.0.4255-8.100.1062-25052.005
x-tm-as-result: No--36.204000-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: multipart/related; boundary="_005_F1E8EFF81FCF1B46AA7CCA3CC4D5E18CA0592812TWMBXP03cnesnet_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/qirg/tkWL-9tCZfIUn9WJcKlDiRKUFYM>
Subject: [Qirg] Similarities between RSVP IETF (RFC 2205) protocol and connection Setup 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: Tue, 19 Nov 2019 12:40:23 -0000

Hi all,



There are similarities between  RSVP  IETF (RFC 2205) protocol and connection Setup in a Quantum Network ( https://tools.ietf.org/html/draft-van-meter-qirg-quantum-connection-setup-00 ) even if the goal isn't the same.



- RSVP was designed independently of any network architecture offering a QoS such as IntServ for example. It is RFC 2210 that defines how to implement the Qos of the IntServ architecture using the RSVP protocol / the setup connection must also be independent of any quantum network architecture

- Reservation at the request of the receiver like setup connection which use the recipient to establish rules and Bell pairs distribution

- RSVP is not a routing protocol. It must be integrated with routing and admission control functions. Connection Setup also needs the support of a routing protocol to reach the receiver.





[cid:image001.jpg@01D59EDE.DF96D4B0]



Messages :



Path: setting the path (logical state).

Resv: reservation request.

ResvTear: deletes the reservation status

PathTear: clears the path state.

ResvErr: reservation error,

PathErr: path error.

ResvConf: reservation confirmation.



[cid:image004.jpg@01D59EDE.DF96D4B0]



/Patrick



-----Message d'origine-----
De : Qirg <qirg-bounces@irtf.org> De la part de Frédéric Grosshans
Envoyé : mardi 12 novembre 2019 12:50
À : Patrick Gelard <patrick.gelard.59@gmail.com>; qirg@irtf.org; Gelard Patrick <Patrick.Gelard@cnes.fr>
Objet : Re: [Qirg] Multipatite entanglement



Hi Patrick,



Le 11/11/2019 à 09:04, Patrick Gelard a écrit :

> Now regarding the control plan for deploying such a service, he seems

> to me that one of the questions is: should we develop a new control

> plan or adapt some traditional network control plans (e.g Resource

> Reservation Protocol (RSVP) Mulicast ; SDN ; etc.) that could do the job?

>

My problem with this is that I'm a physicist with a really elementary knowledge (if any!) of network protocols. For example, in the theoretician's protocol we designed with Clément Meignant and Damian Markham, [arXiv:1811.05445 https://arxiv.org/abs/1811.05445],a<https://arxiv.org/abs/1811.05445%5d,a> key ingredient of GHZ state generation (which is a primitive for the following) is to find a subtree of the network linking the end-nodes.

The operation on nodes of the tree are then local, and look a bit like entanglement-swapping for a repeater line, bit on a tree.



I guess the control plan would look a lot like the one for multicast, but it's pure speculation from me.





Cheers,



        Frédéric



_______________________________________________

Qirg mailing list

Qirg@irtf.org<mailto:Qirg@irtf.org>

https://www.irtf.org/mailman/listinfo/qirg

v2.23.0 | Report a Bug | By Email