[Qirg] updated I-D (-01) on connection setup

Rodney Van Meter <rdv@sfc.wide.ad.jp> Thu, 12 September 2019 04:43 UTC

Return-Path: <rdv@sfc.wide.ad.jp>
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 1E475120808 for <qirg@ietfa.amsl.com>; Wed, 11 Sep 2019 21:43:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sfc.wide.ad.jp
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 uo87tEg600cy for <qirg@ietfa.amsl.com>; Wed, 11 Sep 2019 21:43:47 -0700 (PDT)
Received: from mail1.sfc.wide.ad.jp (mail1.sfc.wide.ad.jp [IPv6:2001:200:0:8803:203:178:142:133]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEEC7120024 for <qirg@irtf.org>; Wed, 11 Sep 2019 21:43:46 -0700 (PDT)
Received: from vanmetedneysmbp.fletsphone (71.99.13.160.dy.iij4u.or.jp [160.13.99.71]) (Authenticated sender: rdv) by mail1.sfc.wide.ad.jp (Postfix) with ESMTPSA id 463717E4; Thu, 12 Sep 2019 13:43:44 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sfc.wide.ad.jp; s=mail1; t=1568263424; bh=weNy/EJ9titUTQKReS+FhxzY/c2Ps+WSGZ6Wvf1Y+N8=; h=From:Date:Subject:Cc:To:From; b=wMyvNQw6JYbcscGLaEjCxw4DsMr3yEakgIq90elvJC4BQxiGlBlocywiEn1eZQURJ osT7nMxFEOTiLsfkTpJL6eo0WhN3tPQQIDBKpkTqJtVdWSRHKYGOm5yIo0eJ8fizrR e1OyT7+/Y1nSgU1HpMyGtjx3nMFdVRF5XsZSUDkwPW4g0dni39tQGm+m65PZT1wvY8 UY8M0yX70tQ1xAEtksEE33CG35muhrmfYZaJ7jsSCfpzuGx1eu7x48qw9dgE6tz0TW 7M71MmQYwGQBeB654Lyp5CK8rufRv7jpx7l+I8C4KfUO2h/e1cRZNjJeFHmWSDnqPx iEjfiwHgOFcCg==
From: Rodney Van Meter <rdv@sfc.wide.ad.jp>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B2E85745-3D83-4EDE-99BD-717425D25881"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Date: Thu, 12 Sep 2019 13:43:43 +0900
Cc: Rodney Van Meter <rdv@sfc.wide.ad.jp>, Takaaki Matsuo <kaaki@sfc.wide.ad.jp>
To: qirg@irtf.org
Message-Id: <652C4922-7839-4700-8E64-3F57804671E2@sfc.wide.ad.jp>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/qirg/gIpCyRDrUZLOMX99-PltP4Qfv0o>
Subject: [Qirg] updated I-D (-01) on connection setup
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, 12 Sep 2019 04:43:50 -0000

If you’re on the drafts list, you probably saw about 19 hours ago that I posted an update to our draft on connection setup in quantum networks.
https://datatracker.ietf.org/doc/draft-van-meter-qirg-quantum-connection-setup/ <https://datatracker.ietf.org/doc/draft-van-meter-qirg-quantum-connection-setup/>
This is a minor update.

I went back and reread the email messages from when we posted the original in March. I think we covered most of the concerns here on the list, without needing much in the way of changes to the draft. But I clarified a few definitions in the new draft.

I think there are four things that I’d still like to do with this.  One is just writing:

1. Wojciech asked for an example of the process.  Agreed.

I think that’s an excellent idea, and would liked to have had it in the -01 draft, but didn’t get it done before -00 expired, so I went ahead and did the minor update.

There are three technical things that need to be done:

2. Align the terminology with Wojciech’s architecture document (*or vice versa*)
3. Our own thinking on where in the architecture *resource reservation* belongs is evolving; our simulator isn’t quite up to needing that yet, so we don’t have real experience with it yet, but this is an important discussion.
4. Wojciech asked if segment routing (SR) could figure into this, and I have only a dilettante’s understanding of SR, so I can’t say but would like to investigate.

Maybe we can revive the discussion of these here on the list, so that we can put out an -02 before Singapore?

—Rod

Rodney Van Meter
Professor, Faculty of Environment and Information Studies
Keio University, Japan
rdv@sfc.wide.ad.jp