Re: [Coin] COINRG and QIR : interaction for generic architecture of quantum computation node ?

"Diego R. Lopez" <diego.r.lopez@telefonica.com> Wed, 25 December 2019 16:17 UTC

Return-Path: <diego.r.lopez@telefonica.com>
X-Original-To: coin@ietfa.amsl.com
Delivered-To: coin@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F386120025 for <coin@ietfa.amsl.com>; Wed, 25 Dec 2019 08:17:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=telefonica.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 PZqOPnVTlIFF for <coin@ietfa.amsl.com>; Wed, 25 Dec 2019 08:17:32 -0800 (PST)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-eopbgr40113.outbound.protection.outlook.com [40.107.4.113]) (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 2EAC0120018 for <coin@irtf.org>; Wed, 25 Dec 2019 08:17:31 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=mgC2nI8FWbNJnQMkTatvz2bHoU1QKrWibmwB80E014pF9X6xCtEkPuvds7nJBLXNYqeKWM6ZGB6eUdUqFUINBqd4l7L9th9XWr7eVoT0tfoKTziMnfwFgK5VbL1cLNt4f9bCe3etl6uR9cFwDulQ6l8wL+go3K3NQDJCV/KOKGDsSt7Qumwf2XVkZTkEo17/gzZ50uboWoLhQGk/jk9EjrQ9eELyI+Iz618BUR7dGvqKoFucOcM5OcB7B8vQboPOBfkbp/F1KRyc4Utb43m7ct7Zfjq9XsXViB0+a0bzco2eQZCopBXrIUEG00FikZlMa9s+5wF7btcVouHr5ZVWMw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=coE1D0F2CtQayARCRa6m7FYa8Zl/bn+BY4NWHXRs+uM=; b=i7oaCqZuI1WOCITRHBoeM9+RPgNjQSchBnovYYhWMetwcDRhErdkjr+Q0A1OcaD4jryZnPbLcoig2gtkUeFL64Ha4mWXSSnKwyUgARsG2y/8d6FAKrH9d1LGg7MZxILaEIt8DPo21ZhRg6cHQBoPaBlc9sKuWhlBZiHfHMfqgfh8V2A96remCtthnN7gRe7Rjyr8NaniubUnbJHrpMJ+lIi4O0E0lQ0yLBAN1df1yxyI8WRIeU262YzPQY2HqC0P4h3FeLk6ry2rCkFqfdvbyQ3SBQG/qK2ze40il1p8SEmiVwUY/kro2IJ1B0gg+o1vds5UYUVg9EiOBbiNM6ZQog==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=telefonica.com; dmarc=pass action=none header.from=telefonica.com; dkim=pass header.d=telefonica.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telefonica.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=coE1D0F2CtQayARCRa6m7FYa8Zl/bn+BY4NWHXRs+uM=; b=Bz0XO+7SXH3NO7vvTui4dq8YBzblDGh64k0PYd1HdO5V0PMCnbDuqoR3QdOUcuKwmWg//0TZOjdeGy3c3s6O0LZn2doTzbN2bh/Zr5/5wrZybTqmoMvAhzWgqjG3/+QloW+T2eyBGiI7W7t6wJVxqwVLBMRs2WDyek6Fc9KutNU=
Received: from DB3PR0602MB3788.eurprd06.prod.outlook.com (52.134.70.148) by DB3PR0602MB3786.eurprd06.prod.outlook.com (52.134.65.154) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2559.15; Wed, 25 Dec 2019 16:17:25 +0000
Received: from DB3PR0602MB3788.eurprd06.prod.outlook.com ([fe80::7d5f:6349:556d:b75f]) by DB3PR0602MB3788.eurprd06.prod.outlook.com ([fe80::7d5f:6349:556d:b75f%7]) with mapi id 15.20.2559.017; Wed, 25 Dec 2019 16:17:25 +0000
From: "Diego R. Lopez" <diego.r.lopez@telefonica.com>
To: Wojciech Kozlowski <W.Kozlowski@tudelft.nl>, "coin@irtf.org" <coin@irtf.org>
CC: Vicente Martin <vicente@fi.upm.es>
Thread-Topic: [Coin] COINRG and QIR : interaction for generic architecture of quantum computation node ?
Thread-Index: AdWjcb8gZ7jfOaskTf2Qmp25g6DuyAACt7oAAAUUIIAF5DLsgA==
Date: Wed, 25 Dec 2019 16:17:24 +0000
Message-ID: <1BEA3AC8-255A-4142-8CEE-64837A1EDAF3@telefonica.com>
References: <F3B0A07CFD358240926B78A680E166FF1ED066DC@TW-MBX-P03.cnesnet.ad.cnes.fr> <CAPjWiCQLZZMuPyop=-aPVCwc-0i7aOQqwMSt4+FeSGE0pRgr3A@mail.gmail.com> <c52b812819bae9c5473dbbc5afcf19dd3cfad51d.camel@tudelft.nl>
In-Reply-To: <c52b812819bae9c5473dbbc5afcf19dd3cfad51d.camel@tudelft.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.11.191208
authentication-results: spf=none (sender IP is ) smtp.mailfrom=diego.r.lopez@telefonica.com;
x-originating-ip: [81.35.16.140]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 23fb2518-b07f-4b2f-1943-08d78955edd8
x-ms-traffictypediagnostic: DB3PR0602MB3786:
x-microsoft-antispam-prvs: <DB3PR0602MB3786294A6E1C5D131B8EA752DF280@DB3PR0602MB3786.eurprd06.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 02622CEF0A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(346002)(366004)(376002)(396003)(136003)(39860400002)(469094003)(199004)(189003)(53754006)(40134004)(53484002)(478600001)(66946007)(966005)(6486002)(110136005)(5660300002)(86362001)(45080400002)(2616005)(66574012)(91956017)(76116006)(6512007)(8936002)(66476007)(64756008)(4001150100001)(66556008)(186003)(55236004)(66446008)(786003)(36756003)(26005)(81156014)(2906002)(6506007)(71200400001)(8676002)(316002)(33656002)(81166006)(4326008)(41533002); DIR:OUT; SFP:1102; SCL:1; SRVR:DB3PR0602MB3786; H:DB3PR0602MB3788.eurprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: telefonica.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: IlYGKEFs+KCkIIG1kF1wP6PaplOerfpByjfPWX5xkOaoUqT6w+NTp+K1D+iJlK9n0NkT+9xxGep0f6QXQlm3ievTb8IO/RaSWMgaqZiHceX63maIAXsQWZfn8tk8ZFlb2/mOM4Gk5nqsC7DeY1oMP8q7H4DBhRwQBBT+6tVB/EzD9yuwXCyprNGo2dcaVQ4FKS5FJYTPl3rIGNlqHEcP0ZLuu0AgfGbPg15O07/RnH9vmmHAGSshPL0phJoy4KkrYG52d2XGv0T9IdPpvlUUCxU/7oklr+YAmdwlpPLQMvJ5i24oqbEJ/44Pjimfi7PAcKp+BosruWYe4LA3cGV1h3e+2mF3XYMJ1M2pxvk+La1rC6nYd/je4xgyPoHkg8RPgolQjaHURRphWLOY/j+arTJ90hjn0ovQyXoFjjrpWT+jENSCkjSid80MEVk0X+Thl3Hjp0VJCxRNRthO7zdH3FQaPlKLZL6XyT56LIr3rnAsG1cVDVc8g/Q8+evMD4i+YwGhW855ELuoZ9tOi1kaP9LMj/c8DKI2u88IujPwOUlRAK7i7PHpyy9EWs1K1nV0/7hGVM+dPtf/sVNUZREAfbkCiiKv5ZzdMLEeTMJHcdmzOk/KUPrVKF2qg0iPCLRE
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_1BEA3AC8255A41428CEE64837A1EDAF3telefonicacom_"
MIME-Version: 1.0
X-OriginatorOrg: telefonica.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 23fb2518-b07f-4b2f-1943-08d78955edd8
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Dec 2019 16:17:25.0143 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9744600e-3e04-492e-baa1-25ec245c6f10
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: C1HU0wAZI+3UspwyHaFyw8rHZ+wRv/fAIZGcfKa38GXHQyVGNtUVPrHjMhTf0DyZwut60tM8HRO8abrTcwG2LO+lu4JmG+eY5qQE0eG9hMI=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB3PR0602MB3786
Archived-At: <https://mailarchive.ietf.org/arch/msg/coin/wcOHCHBmIJwHpsZvyk1ObRNN_pE>
Subject: Re: [Coin] COINRG and QIR : interaction for generic architecture of quantum computation node ?
X-BeenThere: coin@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "COIN: Computing in the Network" <coin.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/coin>, <mailto:coin-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/coin/>
List-Post: <mailto:coin@irtf.org>
List-Help: <mailto:coin-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/coin>, <mailto:coin-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Dec 2019 16:17:36 -0000

Hi Wojtek,

Coming to this with some delay as I have not been able to start dealing with this and related stuff till my turn-of-the-year survey of pending emails…

We (including Vicente in the loop, as the main perpetrator of the idea) are playing with the idea of considering network components rather than layers or planes in defining a quantum network, and some of these components are required to support the necessary bridging aspects between classical (path computation or routing, for example) and quantum aspects. I share your view that these components, and probably others, can be considered as applying in-network computing and it would be quite interesting to explore Rodney’s distributed computation paradigm. As you know, we are focusing our effort on QKD, but I think many of what is proposed there can be adapted to a general quantum network.

We are about to finish a project deliverable on this subject, and will be happy to share it and see whether we can take advantage of the model described there, and move from there on.

Be goode,

--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D
https://www.linkedin.com/in/dr2lopez/

e-mail: diego.r.lopez@telefonica.com<mailto:diego.r.lopez@telefonica.com>
Tel:         +34 913 129 041
Mobile:  +34 682 051 091
----------------------------------

On 25/11/2019, 14:05, "Coin on behalf of Wojciech Kozlowski" <coin-bounces@irtf.org<mailto:coin-bounces@irtf.org> on behalf of W.Kozlowski@tudelft.nl<mailto:W.Kozlowski@tudelft.nl>> wrote:

Following a mention of COIN at the QIRG meeting I attended the meeting on Friday and I do think there is definitely at least some scope for initial exploration. However, I am new to COIN so please forgive me any obvious blunders in the technical matters.

I picked up an interest in COIN, because one of the problems of developing an architectural model for a quantum network is that the stateless packet processing model just does not apply when you have to deal with certain quantum phenomena such as entanglement where you have a pair of qubits on two different physical devices yet they share state information which must be tracked by the network. Rodney Van Meter who is a co-chair of QIRG and published a lot of early work on this topic often suggests that quantum networking is a form of distributed computation. Furthermore, quantum networks (at least the near-term realisations) will be incredibly time-sensitive - latency will matter _a lot_ - so I was interested to see that one of the driving factors for COIN is reducing the latency.

Quantum networking will have a significant non-quantum processing component which will involve local processing and networked communication with other nodes. This has caused me some trouble in my own research when trying to apply the conventional notion of data and control planes to the problem. Perhaps computation in the network might end up being one way of looking at this problem. I have even been exploring using P4 for quantum "data planes" (but more from the SDN and central controller approach) which would open up a practical way of adding computation in the network to quantum nodes.

This is a line of thinking I would like to explore and I'm sure it would be of interest to some in the QIRG. If the people at COINRG are interested and think it's relevant there might be some scope to move forward on this topic.

Thanks,
Wojtek

PS For curious readers: we are currently working on a "Architectural Principles of a Quantum Internet" draft which will serve as an introduction for networking people with no quantum background to the subject of quantum networking (for a quick look into the challenges involved that might be addressed with COIN see sections 4.1 and 5.1).

On Mon, 2019-11-25 at 02:39 -0800, Marie-Jose Montpetit wrote:
Thanks.

At the QIRG meeting last week COIN was mentioned so maybe there is an opportunity to indeed start a dialogue.

mjm

Marie-José Montpetit, Ph.D.
Research Affiliate, MIT Media Laboratory
mariejose@mjmontpetit.com<mailto:mariejose@mjmontpetit.com>
mariejo@mit.edu<mailto:mariejo@mit.edu>


On November 25, 2019 at 10:44:55 AM, Kuhn Nicolas (nicolas.kuhn@cnes.fr<mailto:nicolas.kuhn@cnes.fr>) wrote:
Hi all,

Despite my interest in QIRG activity, I could not attend the meeting at last IETF106 for conflict with other meetings reasons.
However, I could attend COINRG.
I think there is an opportunity for interaction between QIRG and COINRG.

The draft “Directions for Computing in the Network” [https://datatracker.ietf.org/doc/draft-kutscher-coinrg-dir/] mentions a terminology towards a novel "computing in the network (COIN)" approach that revisits the function split between computing and networking.
The document takes one example: “Compute-First Networking with ICN”. To assess whether the proposed terminology is generic, it may be interesting to consider other use-cases where the computing is spread within the network.
Another example could then be “Interconnected Quantum Computers”.
Indeed, the charter of QIRG mentions an architectural framework to support a first step toward a quantum network architecture [https://datatracker.ietf.org/rg/qirg/about/].

I am not sure about the way towards an interaction between those activities, but starting email discussions may pull a trigger.

I hope this helps,
Kind regards,

Nicolas

--
Coin mailing list
Coin@irtf.org<mailto:Coin@irtf.org>
https://www.irtf..org/mailman/listinfo/coin<https://www.irtf.org/mailman/listinfo/coin>

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição