Re: [Qirg] New Version Notification for draft-irtf-qirg-quantum-internet-use-cases-11.txt

Chonggang Wang <Chonggang.Wang@InterDigital.com> Fri, 10 June 2022 14:12 UTC

Return-Path: <chonggang.wang@interdigital.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 AF8A6C159490 for <qirg@ietfa.amsl.com>; Fri, 10 Jun 2022 07:12:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.007
X-Spam-Level:
X-Spam-Status: No, score=-2.007 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=interdigital.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B9kyugrMCFPz for <qirg@ietfa.amsl.com>; Fri, 10 Jun 2022 07:11:59 -0700 (PDT)
Received: from us-smtp-delivery-139.mimecast.com (us-smtp-delivery-139.mimecast.com [170.10.129.139]) (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 36244C15B26D for <qirg@irtf.org>; Fri, 10 Jun 2022 07:11:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=interdigital.com; s=mimecast20220303; t=1654870317; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=IeREWKanQAt4rL3sPFpeFUYCgniHLnmAwBc7k8a8ymQ=; b=JXN0qgIfp9TViXWCnxLDR+bLAjf2DVkZsJyrvYDDyaUJKK73ygRn8NrDHvFsFvvTd+seV9 8gV+A5QGZTFrb6MABw5cxvHuYQCBpaZfwR1vf/bGaEaEZ/e+8yU/NwgSE7k55wIQR33AGM ZDGbd5flurrEV8XgMhDOAos8tK97Pm1zLaKhwkqKFf3gZzNJcClfAlrs7ZAa8VBlCxzzob 3J+VRVHHpmG7hxjrUTmnxfC8nqROB2Ln5BkLh94pgOC9VsPXZJkvQTTd8OEs23C7MzxUUH oE2Oa1b+MVuHr8TeSrkZh7wNTr1X53SfrZVnRm63e6v6MfckScszrZYHqNtNXA==
Received: from NAM11-CO1-obe.outbound.protection.outlook.com (mail-co1nam11lp2173.outbound.protection.outlook.com [104.47.56.173]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-651-aPUEd41rMj6Lac7gPasBuQ-1; Fri, 10 Jun 2022 10:11:49 -0400
X-MC-Unique: aPUEd41rMj6Lac7gPasBuQ-1
Received: from BN0PR10MB5096.namprd10.prod.outlook.com (2603:10b6:408:117::23) by BYAPR10MB3541.namprd10.prod.outlook.com (2603:10b6:a03:11d::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5314.15; Fri, 10 Jun 2022 14:11:43 +0000
Received: from BN0PR10MB5096.namprd10.prod.outlook.com ([fe80::a8d4:5817:93a7:b19f]) by BN0PR10MB5096.namprd10.prod.outlook.com ([fe80::a8d4:5817:93a7:b19f%6]) with mapi id 15.20.5332.013; Fri, 10 Jun 2022 14:11:42 +0000
From: Chonggang Wang <Chonggang.Wang@InterDigital.com>
To: Rodney Van Meter <rdv=40sfc.wide.ad.jp@dmarc.ietf.org>, Chonggang Wang <Chonggang.Wang=40InterDigital.com@dmarc.ietf.org>
CC: Rodney Van Meter <rdv@sfc.wide.ad.jp>, Wojciech Kozlowski <W.Kozlowski@tudelft.nl>, Akbar Rahman <rahmansakbar@yahoo.com>, Ruidong Li <lrd@se.kanazawa-u.ac.jp>, "melchior@aelmans.eu" <melchior@aelmans.eu>, CHAKRABORTY Kaushik <kchakrab@exseed.ed.ac.uk>, "qirg@irtf.org" <qirg@irtf.org>
Thread-Topic: [Qirg] New Version Notification for draft-irtf-qirg-quantum-internet-use-cases-11.txt
Thread-Index: AQHYUzH/XvfDzGYHVkeFYNIgt3DS/Kz1wURQgAyjmYCAC0amYIAO3WIAgAQdNPCAI1EKAIAFB45A
Date: Fri, 10 Jun 2022 14:11:42 +0000
Message-ID: <BN0PR10MB50961D0DC81670A4FE3B163FF8A69@BN0PR10MB5096.namprd10.prod.outlook.com>
References: <165029271227.2600.5024441954198858019@ietfa.amsl.com> <BN0PR10MB50962AD80610A90ED5CA400EF8F39@BN0PR10MB5096.namprd10.prod.outlook.com> <66192772ec9449d8a8407a09ef1fc7d2@tudelft.nl> <BN0PR10MB50961EE4D6E6F41EF2DBF129F8C09@BN0PR10MB5096.namprd10.prod.outlook.com> <9F803336-97F1-4A0B-A0EA-6FA72A73EC8C@sfc.wide.ad.jp> <BN0PR10MB50967A921E244968FBE1FEC1F8CC9@BN0PR10MB5096.namprd10.prod.outlook.com> <2613CD40-3815-4434-A9C0-592CFD0F2041@sfc.wide.ad.jp>
In-Reply-To: <2613CD40-3815-4434-A9C0-592CFD0F2041@sfc.wide.ad.jp>
Accept-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3855acc4-9ec1-4dcc-c3ed-08da4aeb2541
x-ms-traffictypediagnostic: BYAPR10MB3541:EE_
x-microsoft-antispam-prvs: <BYAPR10MB3541785307A160D7F423C2C9F8A69@BYAPR10MB3541.namprd10.prod.outlook.com>
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0
x-microsoft-antispam-message-info: 3INR005e8GLuRnJ9SkOq9JL54UWdazEGmLZcX5X5ZPj69ogFY2+3F7R8LZr91xybM5waQgih4FDgesPAxvErrqWQH6xx3uXx+aidi7cIWmzd9+L1+BltFTx/BqmNlY4HIRlpTLSGmEkVjS+mXh8y9ResY/wjXV1cw/TB04XVuEdNwecdS91d8td2yJb7CUBJ/d6g07Z4v8e5FgkPLSc36N5CYfuKTZbB0BcJw5W1Vq9w4U3/fEWxuowsqFvobzcOJrwZ0T1EMyMWulYYGTFzT0gdqn7I2apeCupSrlCrUPSyg4iRIUlE0ulBYmn9EHiEyVCwQDVYNwRyixL4iH13k1khgrILr+y5w1/6UnVxRlpS27M8UTfWznmcVFKlMNVRJ82GGbx4zfrYTzoo5PzPblWhxChvJ29EU0S52tOaB0iOvETm6o0i7znJ8fHI8p9hQFOG4Ro42yTvi6z+u/sIH8k3OLvqfPzgD/d/lQ6hHlLDLZFFnUAeLfp6+wvTLaMv4RxhI9vPotvwUuHC5EHyB8ybK7TPatSzlpwSrUbveQ1PQ/UhyqCdS9qyLwPgDJUiIXqpMBXyfL0nDBRPzk07hb/fBKmBu4QN1v+mkp1Ox3KlCylbfMm963oA7DryhWwo7qACMMZ9tL34IQru9G+hGjfMmkP3Ro+cPG/IBpIbpAsLc9WvqZ4+dkmqGvxtKyAaPH4k7irdn+6HZLKl3/+3uwZOQ68b45VJnl2ivW8Gb9KMJ1nQRSlubj4XSK1kVI23+tzV+8Ug79tyibH5Ceze2ODRlVe6EdsKYHj5WMMmGax8hVG8aFTi6xAs7q1IMGBrSaBwAll75X97cCDzo3Oui7to8dulQBdD+esGNHSwhLM=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BN0PR10MB5096.namprd10.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230001)(4636009)(366004)(83380400001)(66556008)(4326008)(86362001)(186003)(33656002)(66446008)(66946007)(9326002)(66476007)(53546011)(38100700002)(122000001)(76116006)(2906002)(64756008)(8676002)(316002)(66574015)(30864003)(71200400001)(54906003)(55016003)(76236003)(966005)(52536014)(15650500001)(5660300002)(6506007)(9686003)(8936002)(26005)(508600001)(110136005)(19627405001)(38070700005)(166002)(7696005)(85282002)(579004); DIR:OUT; SFP:1102
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: gwxMdNbzSpzsy3KvNil3nt1kYIzML/fCdUaKudg9RAIWL+6zgnMmpyvIc7KeoEgVKYPto5QVI/BD574nZO6xh213Fx2Ve7kuE++zZAIl9hROSA9JUfuI0sry9vFhznNlKO6e5HfS54cU8deKlhyuDehR/MQL8d2NDsDO5K/rtVXdFPHlFhkh5NwaueyUq9j5+dJH7J2TvPCnWzGwB6v6ej79ut5hMcPSsIsUC1W5tOvX0006bY1p9FNp2+gLbhtsN02yOxqDtDRxt7MnpRAyiGupneY8GdVcwkISVwgSwX/ZYPe6qdgYzHVqQm6C3QesoOI3caKXcB2j3xHaj9Uro+acaz8m+equSbcTvcQMHMXzB5ebLgxpVQctTWnK8C+oX13NeBe8MUauJqp8qHRrrimGa8XLhL9Mkdu2KhXthk/xqxYsYzy3E7jQlOYB0D0cibT0qjFzikgg9LTDOUWAkccrsi8VPTqH5pX9AE/WpNHgzb2jSO6BobxDz8vWOGLtS0iKTvPK642scabKUpUiaZVPkpII4CaXUqV5lWe/JIa/UcOzeNWaDnuNPCYeS1HsDM6lziCsMuAVrQOht/AwFve0zNfH45/ae6s84GcUf2G2I3zbiauX/RlsVq+H/YiatS/UmO6Tbs7OzB8BNwRKxRD7P+5WYBxTzzpcp1lZ+wNXJcvR4tAYYqZtuSxS1z5+dEd4or8s31VjZKAhQMerPqTlLb2D4mVZcrS1q2pC0sdg7sAMWh06sMK/By8DFbsGdHKRZlWnFQncb5eA63C7d9PMUnr8XsDsVYgrrVwMraBbZkUFEBwPTDK2aLcsyHOtfqqMQpwK0o7DUSVlgc6eHHjG7CuwEh+vZiDFUTDw4KkFh0h1KKCXn8lQB9ObB+ErTyIxHArOdN1Y9mwCn8sDBgAa0eucM1ZK3dC3qcWUwhSuYjz54MHgKwFFSp6RrqiEEC3MD5YsaUR8jBV1ipMzalvDsZEC3pZkukZz6w20aJESUGZkOHUu5GRmcEJlk5GIYWsWu0xmL0p3RN9pJXR5G76ODLZEg3b2UvY9w6xuoyVZF+Jmm89rbWFO6GMvxZKfa124mJd1nvC49HYZr+GTnMqgZb1i3w2tNEfrNJ226uCMf4i0h3khe52YfB5kKr37EsBwaDwg0D8HDS4axv7yEMLZ/QkxZDH9s/khGhQV5d5eRUC+IK7Lsw0ja+U9YeeJ4mFYRoak0ld3L8U8knfa4R0kzxaRhPOS0MM6affbm13y9KP1nTppQBOXyNS0fuUzN3vgHAmylBhLGt0briu45yF3bzusVLSr6gKJqMOOjvKe507+hfFX48W0mC4+epPl8ywGZFoIgF741oEfO7tDXTRQm3VNgtu3vxEIfTUA7bXybCG+rCLnCigfXpr60eJ7BzF/H8zQSSLyctdFIbK8/wfb3HKAaFU5NTvueLfA2204P+1wsoZkeZa60IJRizIfG7F73wRwECqrtA98yLZlRsfphSRFfJvGWns55NnLbCax0riC/fi0SpKDHd5a3K3CI4p8brfcE/0fQEf+z0fAf9Jlg7TdMQuruxTYu7PR4TMqa4jYdMcaSTH+zvClyxFs798JDmBM6QNkCGIrwTsrzNwDznHmjdpgS3FQXo1Qoc3g55jboVwfgLI8CMhpMep5MeSSlbGACY21XB98lHI4vPlEkzhVIPRJVyZM7QarFXmyGV8TaRR3fZKq4fmT0u+R4p4dOJZqo1deBbZ6JgWMnQye7/ZOyp4ffgFAEtVADW4=
MIME-Version: 1.0
X-OriginatorOrg: interdigital.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BN0PR10MB5096.namprd10.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 3855acc4-9ec1-4dcc-c3ed-08da4aeb2541
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Jun 2022 14:11:42.8871 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: e351b779-f6d5-4e50-8568-80e922d180ae
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: H3VTaeW78mqjuFrN+jpNqDDy/GuAIkH3Zlm04aqhU4SHZvzt4BeEpH3w1/mLv6xIS8oI7Fp9ZraXKR/4lQsNCtXVE8Z2wvZwlG9K5n/QcD0=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR10MB3541
Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA39A403 smtp.mailfrom=chonggang.wang@interdigital.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: interdigital.com
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_BN0PR10MB50961D0DC81670A4FE3B163FF8A69BN0PR10MB5096namp_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/qirg/AoAy-X3wcwQQ9kN8rgvR6_2IzNU>
Subject: Re: [Qirg] New Version Notification for draft-irtf-qirg-quantum-internet-use-cases-11.txt
X-BeenThere: qirg@irtf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Quantum Internet 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: Fri, 10 Jun 2022 14:12:03 -0000

Hi Rodney,

Thanks for your positive feedback and valuable new suggestions.

According to your new suggestions, a new version v13 of the use case document was just generated and uploaded (https://datatracker.ietf.org/doc/draft-irtf-qirg-quantum-internet-use-cases/13/).

I included inline below my responses to your new suggestions.

Best regards,
Chonggang

From: Qirg <qirg-bounces@irtf.org> On Behalf Of Rodney Van Meter
Sent: Tuesday, June 7, 2022 5:13 AM
To: Chonggang Wang <Chonggang.Wang=40InterDigital.com@dmarc.ietf.org>
Cc: Rodney Van Meter <rdv@sfc.wide.ad.jp>; Wojciech Kozlowski <W.Kozlowski@tudelft.nl>; Akbar Rahman <rahmansakbar@yahoo.com>; Ruidong Li <lrd@se.kanazawa-u.ac.jp>; melchior@aelmans.eu; CHAKRABORTY Kaushik <kchakrab@exseed.ed.ac.uk>; qirg@irtf.org
Subject: Re: [Qirg] New Version Notification for draft-irtf-qirg-quantum-internet-use-cases-11.txt

Hi Chonggang,That was actually very quick turnaround — so quick I missed it :-). Wojtek bugged me about it today.Overall, I’m pretty happy, I think it has now reached a reasonable level of both useful and accurate.A couple of minor things:You referred to “atomic clocks”, which is ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌

<https://us.report.cybergraph.mimecast.com/alert-details/?dep=X46NFZHw7zZ5BYSVlosfKw%3D%3Dz6OpGUM%2F76hkb6DsokVrISGf%2FEEXk2d%2BYarRQu1b48iHuMFWCk3%2FL5ZghZU9SKGdyVD0ah3EMTzspBzUFyHzzi2OnfqXd56bGOrRFRApDr9bwoX0P8UfhiOZVH9AvAtbeoqYm0llL0KJIfqi3QtfNba26dRRAwUcBO4hSBL6bUZiwYRheH8Voq27Jy3iiCPRovk7%2Bs4DlHiGPCvlFd33BotaEylzEOZcw%2BIcPN0u7d%2FtuMhTmU25i%2B7a1IfMHaYF%2BIv9EfFazG5547Q2oQWHeDoSqMiWlae%2BrmgUZaZFaw1AAQc4zink6uUEp1pUWeClwWm5sO%2Fv%2Fypi9XuSBbhgoURj%2FaR20hGWSWDxuk1ENWYHbVNqFcHrOm5Ij0Z%2BapItbbVETdbj2lOfDxrzlWa5XCrwK2MbMrKp%2FUyiLrzoqxCham%2Fbz3lpFZvoIyGoiEC79ndvLllZ%2B46tXwLT12FfEnVfPESkqY0WK8hAx2e3A4q0ROg1t8%2BSvS3tkonxTG36bXUtJg3HiuL3x%2BSHIG4or79FjNBpIYUqkV72LeFnyYytzajmLozL1v1dJ2dIVfpLMTSlhotlD2JHuxOksNHfoMVnD2ZDTicQTuIHnnAjvID0PJFeUiX6rRT6ZK18trlcnH2rlVXA1QOQyQ135IVen2Dfz7xRzUjwLCcRV5Pg%2F6M5zcNLZo0IRJNeCbi0IX9pZV1tgG7H9T5jS%2B%2B%2F1ZjXL84fZwThqy5vSMnHoz1lqpj53gVwg6oGvGlCXb9Cr8giOHovASDRpAUw%2FS608GMO21GrYp51pv2UA0vzCftNZAKu%2BkpOojF85sfYK1%2FT6vIBaLy4t86OAP%2F%2F7kljP0HwCw%3D%3D>
Hi Chonggang,

That was actually very quick turnaround — so quick I missed it :-). Wojtek bugged me about it today.

Overall, I’m pretty happy, I think it has now reached a reasonable level of both useful and accurate.

A couple of minor things:

You referred to “atomic clocks”, which is what we amateurs call a broad class of things, but the most precise clocks in existence today have nothing to do with the atomic clocks of the 1950s or 60s or whenever they were invented. I wonder if there is a broader term that incorporates high-precision time references in some fashion?
>>CW - Good point. Replaced “atomic clocks” with “high-precision clocks”. Hope it is more boarder than “atomic”.

Slightly more important, Figures 1 & 3 show a user of some sort connected via a “GUI”. It’s unclear in both figures how the user is actually connected there. It’s much more important at the IRTF level that nature of that communication be clear rather than whether the user is using a GUI or CLI interface to the service. I wonder if it’s clearer or more confusing to have those connected to one or both nodes via the Classical Internet that appears on both figures? Or in Fig. 1, maybe best to show that the user is connected via a local, secure interface, which might mean using the same physical hardware or might mean some locally secure network? In Fig. 3, I think I would refer to some control system that classically distributes execution requests to the multiple quantum nodes, rather than having “Scientist” in the figure. (Especially, we eventually want non-scientists to use this network and distributed quantum computing, too!)
>>CW - Very valid comments. For Fig. 1, replaced “GUI” with “Secure Local Interface (e.g., the same physical hardware or a local secure network)”. For Fig. 3, 1) replaced “GUI” with “Secure Local Interface (e.g., the same physical hardware or a local secure network)”; and 2) removed “scientists” and rephased the corresponding sentence to “In this case, qubits will be transmitted among connected quantum computers via quantum channels, while the user’s execution requests are transmitted to these quantum computers via classical channels for coordination and control purpose”

After that, I think it’s probably ready to go to IRSG…?
>>CW - Appreciate the positive feedback.

—Rod

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


On May 16, 2022, at 7:07, Chonggang Wang <Chonggang.Wang=40InterDigital.com@dmarc.ietf.org<mailto:Chonggang.Wang=40InterDigital.com@dmarc.ietf.org>> wrote:

Hi Rodney,

Many thanks for your valuable feedback and detailed comments.

Your suggestions have been incorporated into the new v12, which was just uploaded (draft-irtf-qirg-quantum-internet-use-cases-12<https://datatracker.ietf.org/doc/draft-irtf-qirg-quantum-internet-use-cases/>).

Our responses to your feedback/questions are also provided below starting with “>>”. Please kindly let us know if you are satisfied with the updates.

Best regards,
Chonggang

From: Rodney Van Meter rdv@sfc.wide.ad.jp<mailto:rdv@sfc.wide.ad.jp>
Sent: Friday, May 13, 2022 3:04 AM
To: Chonggang Wang Chonggang.Wang@InterDigital.com<mailto:Chonggang.Wang@InterDigital.com>
Cc: Rodney Van Meter rdv@sfc.wide.ad.jp<mailto:rdv@sfc.wide.ad.jp>; Wojciech Kozlowski W.Kozlowski@tudelft.nl<mailto:W.Kozlowski@tudelft.nl>; Akbar Rahman rahmansakbar@yahoo.com<mailto:rahmansakbar@yahoo.com>; Ruidong Li lrd@se.kanazawa-u.ac.jp<mailto:lrd@se.kanazawa-u.ac.jp>; Melchior Aelmans maelmans@juniper.net<mailto:maelmans@juniper.net>; CHAKRABORTY Kaushik kchakrab@exseed.ed.ac.uk<mailto:kchakrab@exseed.ed.ac.uk>; qirg@irtf.org<mailto:qirg@irtf.org>
Subject: Re: New Version Notification for draft-irtf-qirg-quantum-internet-use-cases-11.txt

Sorry to be a little slow on this. It’s getting a lot better, but there are still many smaller things that can be improved that will make the document clearer and better for an IETF/IRTF audience.

—Rod

Comments:

Abstract:

I don’t think it’s common practice to put “This document is a  product of the Quantum Internet Research Group (QIRG).“ in the abstract, is it?
>>CW: Removed that sentence.

Throughout:
When "end node" is used as a noun, no need for the hyphen.  Same for "end-user".
>>CW: Made the global changes.

Sec. 1: fiber is a common form of access link now.
>>CW: Added fiber as a type of access links

"Qubits are expected to be transferred across the Quantum Internet."
I think that's misleading; that is one thing the QI will do, but more importantly it will create E2E entanglement.  I whould just delete this sentence, it doesn't add anything anyway.
>>CW: This sentence has been deleted as suggested:

" For instance, quantum key distribution can improve the security of the Classical Internet; the powerful computation capability of quantum computing can expedite and optimize computation-intensive tasks (e.g., routing modelling) in the Classical Internet."
I don't think there's any need to justify computation-intensive tasks in the context of Internet operations.  It would be fine without the parenthetical comment.  Moreover, as phrased it just says "quantum computers are powerful", which doesn't connect the attractiveness of quantum computers to the need for the QI.
>>CW: That sentence has been reworded as below according to your comment:
>>“For instance, quantum key distribution can improve the security of the Classical Internet; quantum computing can expedite and optimize computation-intensive tasks in the Classical Internet.”


"Similar to, but has more profound implications, as the process" --> "Similar to, but has more profound implications than, the process"
>>CW: Changed as suggested.

"A special type of two-qubits quantum states." --> "state" doesn't need the 's'.
>>CW: Fixed it.

"must be able to generate/transfer and receive/process qubits" I still don't like this phrasing.
It still implies a send-receive model, which is a possible way to build or use a QI, but not the only way.
>>CW: Removed this sentence.

"basis state vector |0> or |1>" -- adding "using Dirac's ket notation" will help beginners find other explanations of the notation.
>>CW: Added as suggested. Thanks!

Transmit, teleport, transfer: I like that distinction.  Let's use it throughout.
>>CW: Thanks for your earlier suggestion on this.

" (e.g., quantum random number generator)" -- there are many standalone quantum computational applications, why single out just this one?
>>CW: Do not think there would be many.  So, removed “(e.g., quantum random number generator)”.

   *  Quantum cryptography applications - Refer to the use of quantum information technology for cryptographic tasks such as quantum key distribution and quantum commitment.

   *  Quantum sensors applications - Refer to the use of quantum information technology for supporting distributed sensors (e.g., clock synchronization [Jozsa2000] [Komar] [Guo] ).

   *  Quantum computing applications - Refer to the use of quantum information technology for supporting remote quantum computing facilities (e.g., distributed quantum computing).

Only one of those has citations. Either all or none should.
>>CW: Good point. Added a reference for the first and the third bullet.

"terminal node needs to run a more computation-intensive task" the "more" there is confusing.  Delete it.
>>CW: Fixed it.

Blind computation: I'm not familiar with a couple of those papers, so good job on finding them, I'm looking forward to reading them.

"In fact, the error rates of two-qubit quantum gates have decreased nearly in half every 1.5 years (for trapped ion gates) to 2 years (for superconducting gates).  The error rate also increases as the number of qubits increases.  For example, a current 20-physical-qubit machine has a total error rate which is close to the total error rate of a 7 year old two-qubit machine [Grumbling]."
Is such temporally relevant information a good thing to have in an RFC?
>>CW: Deleted that sentence.

  2.  Distribute quantum computing functions to distributed quantum computers.
“A quantum computing task or function (e.g., quantum gates) is split and distributed to multiple physically separate quantum computers.  And it may or may not need to transmit qubits (either inputs or outputs) among those distributed quantum computers.  Pre-shared entangled states may be needed to transmit quantum states among distributed quantum computers without using quantum communications, similar to quantum teleportation.  For example, [Gottesman1999] and [Eisert] have proved that a CNOT  gate can be realized jointly by and distributed to multiple quantum computers.  The rest of this section focuses on this type of distributed quantum computing.”
The physicists and CS theorists do it a lot, but I really don't like the "we use preshared entanglement but not quantum communications" way of explaining things.  It's confusing and ultimately unfair, I think.
*Creating* the entangled states that are needed *IS* quantum communication.  We need a clearer way of saying this.  One factor in it is that almost every application of a QI will consume *lots* of entangled states.  Those can be created beforehand and stored or buffered.  We need a way of explaining this that correctly accounts for the volume of entangled states needed, and emphasizes that while they may be buffered, in practice in many cases it is fair to assume that the rate of entanglement creation will limit the performance of applications.
>>CW: Revised that paragraph to the following
>>“A quantum computing task or function (e.g., quantum gates) is split and distributed to multiple physically separate quantum computers. And it may or may not need to transmit qubits (either inputs or outputs) among those distributed quantum computers. Entangled states will be needed and actually consumed to support such distributed quantum computing tasks. It is worth noting that: 1)Entangled states can be created beforehand and stored or buffered; 2) The rate of entanglement creation will limit the performance of practical quantum internet applications  including distributed quantum computing, although entangled states could be buffered. For example, [Gottesman1999] and [Eisert] have proved that a CNOT gate can be realized jointly by and distributed to multiple quantum computers. The rest of this section focuses on this type of distributed quantum computing.”

"In order to gain higher computation power before fully-fledged quantum computers become available, NISQ computers can be connected"
This is also misleadingly phrased.  A cluster of NISQ machines gains no advantage over a single NISQ machine in terms of error rate/computational failure rate; in fact, it's probably worse, because of the initially poor performance of the network or interconnect. Tying multiple NISQ computers together is only interesting and useful if the user has a *broad, shallow* circuit to run, one that uses a lot of qubits (more than fit in a single NISQ machine) but requires only a small number of operations on each node.
>>CW: Agreed with your comment. Deleted that sentence.

"qubits from one NISQ computer to another NISQ computer are very sensitive and should not be lost."
That needs a verb phrase of some sort -- "we want to move from one node to another"?
>>CW: Rephases that sentence to “we want to move qubits from one NISQ computer to another NISQ computer.”




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



On May 4, 2022, at 5:06, Chonggang Wang <Chonggang.Wang@InterDigital.com<mailto:Chonggang.Wang@InterDigital.com>> wrote:

Dear Wojtek,
Thank you for your positive feedback and support.

Dear Rod,
Could you let us know your feedback on the version v11.

Best regards,
Chonggang

From: Wojciech Kozlowski <W.Kozlowski@tudelft.nl<mailto:W.Kozlowski@tudelft.nl>>
Sent: Tuesday, April 26, 2022 11:52 AM
To: Chonggang Wang <Chonggang.Wang@InterDigital.com<mailto:Chonggang.Wang@InterDigital.com>>; Rodney Van Meter <rdv@sfc.wide.ad.jp<mailto:rdv@sfc.wide.ad.jp>>
Cc: Akbar Rahman <rahmansakbar@yahoo.com<mailto:rahmansakbar@yahoo.com>>; Ruidong Li <lrd@se.kanazawa-u.ac.jp<mailto:lrd@se.kanazawa-u.ac.jp>>; Melchior Aelmans <maelmans@juniper.net<mailto:maelmans@juniper.net>>; CHAKRABORTY Kaushik <kchakrab@exseed.ed.ac.uk<mailto:kchakrab@exseed.ed.ac.uk>>
Subject: RE: New Version Notification for draft-irtf-qirg-quantum-internet-use-cases-11.txt

Dear Chonggang,

Thanks for the update! My point of view as one of the co-chairs is that it’s ready assuming all of Rod’s comments have been addressed. Therefore, as soon as Rod also agrees, we can proceed.

Rod, any thoughts?

Thanks,
Wojtek

From: Chonggang Wang <Chonggang.Wang@InterDigital.com<mailto:Chonggang.Wang@InterDigital.com>>
Sent: maandag 18 april 2022 16:59
To: Rodney Van Meter <rdv@sfc.wide.ad.jp<mailto:rdv@sfc.wide.ad.jp>>; Wojciech Kozlowski <W.Kozlowski@tudelft.nl<mailto:W.Kozlowski@tudelft.nl>>
Cc: Akbar Rahman <rahmansakbar@yahoo.com<mailto:rahmansakbar@yahoo.com>>; Ruidong Li <lrd@se.kanazawa-u.ac.jp<mailto:lrd@se.kanazawa-u.ac.jp>>; Melchior Aelmans <maelmans@juniper.net<mailto:maelmans@juniper.net>>; CHAKRABORTY Kaushik <kchakrab@exseed.ed.ac.uk<mailto:kchakrab@exseed.ed.ac.uk>>
Subject: FW: New Version Notification for draft-irtf-qirg-quantum-internet-use-cases-11.txt

Dear Rodney and Wojciech,

Thank you very much for your valuable feedback for our quantum application document.

We made quite a few updates mainly based on Rodney’s feedback posted before and after IETF 113. We also took your suggestion to have proofread the document and corrected some typos.

Would you please kindly let us know if v11 is ready for RGLC?

Best regards,
Chonggang

From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Sent: Monday, April 18, 2022 10:39 AM
To: Akbar Rahman <rahmansakbar@yahoo.com<mailto:rahmansakbar@yahoo.com>>; Chonggang Wang <Chonggang.Wang@InterDigital.com<mailto:Chonggang.Wang@InterDigital.com>>; Chonggang Wang <Chonggang.Wang@InterDigital.com<mailto:Chonggang.Wang@InterDigital.com>>; Kaushik Chakraborty <kchakrab@exseed.edu.ac.uk<mailto:kchakrab@exseed.edu.ac.uk>>; Melchior Aelmans <maelmans@juniper.net<mailto:maelmans@juniper.net>>; Ruidong Li <lrd@se.kanazawa-u.ac.jp<mailto:lrd@se.kanazawa-u.ac.jp>>; irtf-chair@irtf.org<mailto:irtf-chair@irtf.org>; qirg-chairs@ietf.org<mailto:qirg-chairs@ietf.org>
Subject: New Version Notification for draft-irtf-qirg-quantum-internet-use-cases-11.txt


A new version of I-D, draft-irtf-qirg-quantum-internet-use-cases-11.txt
has been successfully submitted by Chonggang Wang and posted to the
IETF repository.

Name: draft-irtf-qirg-quantum-internet-use-cases
Revision: 11
Title: Application Scenarios for the Quantum Internet
Document date: 2022-04-18
Group: qirg
Pages: 33
URL: https://www.ietf.org/archive/id/draft-irtf-qirg-quantum-internet-use-cases-11.txt<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_archive_id_draft-2Dirtf-2Dqirg-2Dquantum-2Dinternet-2Duse-2Dcases-2D11.txt&d=DwMGaQ&c=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m=P9CsSvouGVXvkdS5V5CrNZqwkCJbQzzgcWbbUviBaTA&s=d-zSytwljCqCV5-hut_eOc5ZL_W5lktu1hgngK3VdKI&e=>
Status: https://datatracker.ietf.org/doc/draft-irtf-qirg-quantum-internet-use-cases/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dirtf-2Dqirg-2Dquantum-2Dinternet-2Duse-2Dcases&d=DwMGaQ&c=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m=P9CsSvouGVXvkdS5V5CrNZqwkCJbQzzgcWbbUviBaTA&s=oT5lXtpJWGCYcCM_xMGq3yymVg2-94HWmus0rABhDkY&e=>
Htmlized: https://datatracker.ietf.org/doc/html/draft-irtf-qirg-quantum-internet-use-cases<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_html_draft-2Dirtf-2Dqirg-2Dquantum-2Dinternet-2Duse-2Dcases&d=DwMGaQ&c=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m=P9CsSvouGVXvkdS5V5CrNZqwkCJbQzzgcWbbUviBaTA&s=4e8hDJrNeAd3X0JdgxO8NFwTXL84IxQaQSa6ErBjkFk&e=>
Diff: https://www.ietf.org/rfcdiff?url2=draft-irtf-qirg-quantum-internet-use-cases-11<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_rfcdiff-3Furl2-3Ddraft-2Dirtf-2Dqirg-2Dquantum-2Dinternet-2Duse-2Dcases-2D11&d=DwMGaQ&c=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m=P9CsSvouGVXvkdS5V5CrNZqwkCJbQzzgcWbbUviBaTA&s=uXi7oEtZ_b7X35-fWfbXWwsX_SXSsuWatb6b9rnB7qI&e=>

Abstract:
The Quantum Internet has the potential to improve application
functionality by incorporating quantum information technology into
the infrastructure of the overall Internet. This document provides
an overview of some applications expected to be used on the Quantum
Internet and categorizes them. Some general requirements for the
Quantum Internet are also discussed. The intent of this document is
to describe a framework for applications, and describe a few selected
application scenarios for the Quantum Internet. This document is a
product of the Quantum Internet Research Group (QIRG).




The IETF Secretariat
<image001.jpg>

<image002.jpg><https://urldefense.proofpoint.com/v2/url?u=https-3A__www.interdigital.com_features_sustainability-2Din-2Da-2Dwireless-2Dworld&d=DwMGaQ&c=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m=P9CsSvouGVXvkdS5V5CrNZqwkCJbQzzgcWbbUviBaTA&s=0aC5Taw8b7jXbPnQoRP6LcIOGoBRt7tVy5iW5Ik6LYw&e=>

Sustainability in a Wireless World: Research dedicated to understanding the impact of our technologies on the planet.<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.interdigital.com_features_sustainability-2Din-2Da-2Dwireless-2Dworld&d=DwMGaQ&c=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m=P9CsSvouGVXvkdS5V5CrNZqwkCJbQzzgcWbbUviBaTA&s=0aC5Taw8b7jXbPnQoRP6LcIOGoBRt7tVy5iW5Ik6LYw&e=>
This e-mail is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and/or otherwise protected from disclosure to anyone other than its intended recipient. Unintended transmission shall not constitute waiver of any privilege or confidentiality obligation. If you received this communication in error, please do not review, copy or distribute it, notify me immediately by email, and delete the original message and any attachments. Unless expressly stated in this e-mail, nothing in this message or any attachment should be construed as a digital or electronic signature.


_______________________________________________
Qirg mailing list
Qirg@irtf.org<mailto:Qirg@irtf.org>
https://www.irtf.org/mailman/listinfo/qirg<https://www.irtf.org/mailman/listinfo/qirg>