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

Dino Farinacci <farinacci@gmail.com> Wed, 20 November 2019 14:29 UTC

Return-Path: <farinacci@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 14D8212085D for <qirg@ietfa.amsl.com>; Wed, 20 Nov 2019 06:29:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FKdIkcjoA6iL for <qirg@ietfa.amsl.com>; Wed, 20 Nov 2019 06:29:48 -0800 (PST)
Received: from mail-pl1-x62f.google.com (mail-pl1-x62f.google.com [IPv6:2607:f8b0:4864:20::62f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 457431200F8 for <qirg@irtf.org>; Wed, 20 Nov 2019 06:29:48 -0800 (PST)
Received: by mail-pl1-x62f.google.com with SMTP id ay6so13912581plb.0 for <qirg@irtf.org>; Wed, 20 Nov 2019 06:29:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=MCuDd7YJLrXiZSfGJr/2O8IZ7RjlR8inrYI/4tFwO9U=; b=TZ9kDoQVd5kcX0zIxgVaU7dgepJGPTlFaj5ppmZB0TzvNaDFGllDXemqjKpGsXVK6a 6xA8dg4oZR70/H08ZaOsQNyE6xiw39i25ysdwQ7fEkBosAIID7fQXg/UTM0fZE9AiZX/ tCFomSwbO3RYeZ4BedmMUCL8GE2LSjD7UgT2FWT9BsSEUxF7h0cy9UECyGTeLxpYUehO OB0HeJi7SLABywP9O34cnS0qlry2DSxlUQEaQRnahO1ef3u1vJFk+V0WmMWWhnnEaNGM fuR8NV12df49Om6UMPfGCpVoajDnn4q/xh8giX3soTzJyWz18yxbwRuSgelK03glVncy GOJg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=MCuDd7YJLrXiZSfGJr/2O8IZ7RjlR8inrYI/4tFwO9U=; b=aeQM6ofiPPleYnAgEIijn8jVdnECwWWKZu4CkYwj/w/9SEvU6QMC+yqg94qqk1CL3x WiWIm95Usn4sjKkgqWVQvHRIGxN0VxfFIUiVAMiVHyhf/BnVgtlMP/oVtZbUjxSvhDRF yWemj1tne72nfo7Vj7DfidLJM33f3/iEpkqQahb8+bQMQwxgsQEi4U8Om0eI7++eHvlj 9NLKBBiu2tUQ6sBZS5CeF6GaWaJTVmKZ4SsLRV0++GAhnPEp4Jt56vQzaaCoje+Qk+jz CABFEVrunvKBDI14/jQ7oRsR2yQ40lOkL1fV38+xM6GQHV1OEA+MzhQPQaIOOrOC72So KEGw==
X-Gm-Message-State: APjAAAXAnoLOhl0LAUKnJh7hQCikWF08Zh6QD3C1BK4Q05geHBq1VBx3 ev/omw3fV/iQkO0QURMnAuQ=
X-Google-Smtp-Source: APXvYqyCTwTUAJnpeu225kLlSN2tiWdGYRarbbykpVNk8RIqAPZ6Iq3wha8a8Brbeho/LTA9IAVvcQ==
X-Received: by 2002:a17:902:7c8c:: with SMTP id y12mr3293795pll.260.1574260187711; Wed, 20 Nov 2019 06:29:47 -0800 (PST)
Received: from dhcp-9dad.meeting.ietf.org (dhcp-9dad.meeting.ietf.org. [31.133.157.173]) by smtp.gmail.com with ESMTPSA id r4sm29747254pfl.61.2019.11.20.06.29.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Nov 2019 06:29:46 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <9751D214-0D25-48FB-A2EE-58647E4C27C8@gmail.com>
Date: Wed, 20 Nov 2019 22:29:44 +0800
Cc: "qirg@irtf.org" <qirg@irtf.org>, Gelard Patrick <Patrick.Gelard@cnes.fr>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B9A77D1C-00F5-45DF-9FAD-D1B3D7E93079@gmail.com>
References: <F1E8EFF81FCF1B46AA7CCA3CC4D5E18CA0592812@TW-MBX-P03.cnesnet.ad.cnes.fr> <249DECDC-7CBF-4209-B0D7-4C1AE6BC2813@gmail.com> <F1E8EFF81FCF1B46AA7CCA3CC4D5E18CA0592A68@TW-MBX-P03.cnesnet.ad.cnes.fr> <B64F6ED3-2373-4DDF-8F1E-A65CEC22767B@gmail.com> <A55452C0-0FE8-4457-A70F-E885684F7251@gmail.com> <2CB31F68-E13E-4A4E-9D73-D62274D4BDD6@gmail.com> <8F1998DE-B04E-460C-9E5E-799505149491@gmail.com> <893249F1-038C-40BB-8503-670F554AD2BC@gmail.com> <9751D214-0D25-48FB-A2EE-58647E4C27C8@gmail.com>
To: Bruno Rijsman <brunorijsman@gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/qirg/-IvQIVRfizefPKeNNP9mf-soTtk>
Subject: Re: [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: Wed, 20 Nov 2019 14:29:50 -0000

> One minor answer >>> below.
> 
> But before I address the main comment, can I ask you a clarifying question to fully understand the scenario that you have in mind?
> 
> In your scenario, are the service providers ATT and VZ only providing classical connectivity for the classical channel ([A] below) or are they also offering quantum connectivity for the quantum channel ([B] below)?

Classic connectivity. The QRs can be at their customer sites. And if ISPs provide QRs that sites need to pair with (good luck with that), then you will have to know the IP addresses of the ISP QRs (good luck with that).

> In everything I have described until now, I was actually only considering intra-domain quantum routing and not yet inter-domain quantum routing, which is even further away into the future IMHO.

I don’t see why. 

> 
> [A] Service provider provides only classical channel (CC):
>                    
>  CC      CC     CC     CC     CC     CC   CC    CC
>  +----CR----CR---+     +---CR----CR---+   +--CR--+
>  |   |........|  |     |  |.........| |   | |..| |
>  |      ATT      |     |     VZ       |   | Lab  |
>  |                \   /               \   /      \
> QR1----------------QR2-----------------QR4--------QR5
>           QC                 QC              QC
> 
> [B] Service provider provides both classical channel (CC) and quantum channel (QC):
>        
>     CC+   CC+   CC+    CC+   CC+   CC+    CC+   CC+
>     QC    QC    QC     QC    QC    QC     QC    QC
> QR1----QR----QR----QR2----QR----QR----QR4----QR----QR5
>       |........|         |........|         |..|
>        ATT                VZ                Lab
> 
> — Bruno
> 
>>> This is similar to not representing optical repeaters or Ethernet hubs in the classical layer 3 network topology.
>> 
>> Optical repeaters and ethernet hubs if SNMP managed would be hosts with accessible IP addresses on the layer-3 network.
> 
> >>> Exactly, they are represented as hosts (not routers) on the network. So, they do not appear as nodes in the layer-3 topology flooded by OSPF / ISIS / etc. In fact, they do not appear at all in the routing protocol (which only advertises subnets, not individual hosts).

Right, they are not routers. Just like your laptop right now is not pariticaping in OSPF/IS-IS.

Dino