Re: [Coin] Draft-liu-coinrg-requirement-00 for discussion and comments

<philip.eardley@bt.com> Mon, 04 November 2019 17:46 UTC

Return-Path: <philip.eardley@bt.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 D36BD12021C for <coin@ietfa.amsl.com>; Mon, 4 Nov 2019 09:46:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bt.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 RDxp084Hjmfq for <coin@ietfa.amsl.com>; Mon, 4 Nov 2019 09:45:59 -0800 (PST)
Received: from smtpe1.intersmtp.com (smtpe1.intersmtp.com [213.121.35.77]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8FBF4120B54 for <coin@irtf.org>; Mon, 4 Nov 2019 09:45:58 -0800 (PST)
Received: from tpw09926dag17h.domain1.systemhost.net (10.9.212.41) by BWP09926082.bt.com (10.36.82.113) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1713.5; Mon, 4 Nov 2019 17:45:56 +0000
Received: from tpw09926dag11g.domain1.systemhost.net (10.9.212.27) by tpw09926dag17h.domain1.systemhost.net (10.9.212.41) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 4 Nov 2019 17:45:50 +0000
Received: from bwp09926081.bt.com (10.36.82.112) by tpw09926dag11g.domain1.systemhost.net (10.9.212.27) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Mon, 4 Nov 2019 17:45:50 +0000
Received: from GBR01-CWL-obe.outbound.protection.outlook.com (104.47.20.55) by smtpe1.intersmtp.com (10.36.82.112) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1713.5; Mon, 4 Nov 2019 17:45:39 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=SCfugpKW4GO8USkEtEzwNnZ0SFoIvjnUb9Hq1tcrMxiO7IiBfVLR1djIcCjIQsdiaaPIsdB85uCJ4Ajg2aPHuKmBcFIkHBbX2oFU9KZ962pNHhKQUH9es+e7p/ruq9+G8Rjn4zJf7Z6fMjteSAmO49Xd7G+OzM7ofRsVYX9wTswYLiJYOixSFoyzURhqlSdc3Zet6ixWj4cWNpISDV8dNsFdAwCHTqIhXemLEeTniypXsIvmA4HaLw0y6QjmeHlcmUdzrUH3hzD3u43CUY4gLIoUkKq9T7pmOvlTeONexkrC9JRcfXQCjiOzl32+8TKo5BjKoZPu0tnDs7YGO6yQ8Q==
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=uXUQNIuRW5Ne6qvVSCk5d+tjAyUcj2TNPUdSeRgRG5I=; b=lclknmUl1mP9hp6kY7hjMzWG55hAfJ2fRkRJELK6T1u922qwYXeQpfrd7u5b7cn7EckAhD+rY57wcxlV83UMDOxZbQYBjlIrLg9Cc/B0bKxJPLVPkKcK/+vmjItdbK28eHYxfUI82RRasMTXSRhMzbO3GNvL0pcQjMroCkgoVx+aGJuw6Z6zKS8XPz+k2bAuK3P4RtC3cf3FK/sv8ugso9/r1o/WMiLA8GuytzS+2d2dZhx84kxhAvIWPiRByifLclJ8l7+QRjM6Tyr22IOWZDlGnrBl6BGWUrszUoMM0XAjbLyEKu5C+u6wL7YMoimzLU8gv1qU1UCLUDr5kRqm1Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=bt.com; dmarc=pass action=none header.from=bt.com; dkim=pass header.d=bt.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bt.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=uXUQNIuRW5Ne6qvVSCk5d+tjAyUcj2TNPUdSeRgRG5I=; b=exl7YoxDWvYQaOUidglNSnrJ4z8uYNRfKV35CCwoeC/7zjgPd7pMrOeh3IL2P/7ApegICDxsUFWJabap/GJEQo22VE1yxNpkaUNnGOUaSJdDulp84jb8WC/tAxT7U6X6CnUWrw7yPSH23oT54xKVVx8smuU/eC5ziUr5f3wcSyU=
Received: from LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM (20.179.128.78) by LNXSPR01MB0021.GBRP123.PROD.OUTLOOK.COM (20.176.129.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2408.24; Mon, 4 Nov 2019 17:45:49 +0000
Received: from LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM ([fe80::2511:b620:ed5d:189c]) by LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM ([fe80::2511:b620:ed5d:189c%7]) with mapi id 15.20.2408.024; Mon, 4 Nov 2019 17:45:49 +0000
From: <philip.eardley@bt.com>
To: <liupengyjy@outlook.com>, <coin@irtf.org>
Thread-Topic: Draft-liu-coinrg-requirement-00 for discussion and comments
Thread-Index: AQHVNy13jQseX+U+yUKUHPhmTuOrJKd7vQ2Q
Date: Mon, 4 Nov 2019 17:45:49 +0000
Message-ID: <LNXP123MB258736FB6E413F55C81BA122EB7F0@LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM>
References: <TYAPR06MB2318F351A7840A558D77C648DAF00@TYAPR06MB2318.apcprd06.prod.outlook.com>
In-Reply-To: <TYAPR06MB2318F351A7840A558D77C648DAF00@TYAPR06MB2318.apcprd06.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=philip.eardley@bt.com;
x-originating-ip: [193.113.37.9]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 77885a8b-8f32-4617-97e7-08d7614ed49d
x-ms-traffictypediagnostic: LNXSPR01MB0021:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <LNXSPR01MB00217911569FC89F1A4565B3EB7F0@LNXSPR01MB0021.GBRP123.PROD.OUTLOOK.COM>
x-antispam-2: 1
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0211965D06
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(376002)(39860400002)(346002)(396003)(136003)(51914003)(189003)(199004)(6246003)(7696005)(81166006)(66446008)(229853002)(76176011)(110136005)(5660300002)(2906002)(8936002)(316002)(52536014)(81156014)(14454004)(71200400001)(54896002)(6306002)(790700001)(6436002)(6116002)(45080400002)(55016002)(3846002)(236005)(2501003)(486006)(606006)(74316002)(476003)(33656002)(86362001)(9686003)(8676002)(66066001)(99286004)(53546011)(966005)(478600001)(26005)(102836004)(6506007)(186003)(66946007)(76116006)(11346002)(256004)(14444005)(66556008)(446003)(7736002)(66476007)(64756008)(25786009)(71190400001); DIR:OUT; SFP:1101; SCL:1; SRVR:LNXSPR01MB0021; H:LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: bt.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: A4d2BMlXmVh123HNfEbziQ6QeNFn29C2ZzMspc4vl7e0l/NttFJMqjXeTow2CkvCQdHbdLsF07k06bwP1cJUOqWGuyPDupugdhhWWOIkM7FUOoSqdFrHWTSk8E98RhWwEOlcFAkJFTwZ4m28f3Z0yNlzI7yMNI33NdundO+Uhj7sxBaajAPrSWlTVMBAzscAIADjbTPPIPljn+0g5VFUePuc6apMB51lZYsGytXllV9Tr3ffKAA6BfN2tAtSx+8pg0O5O5QKMuKiar/18eXr7KVh+peShMFZRVC7fR3qoYlBXqng4TDUtLdnsBoBQk7skQZOSg7TKDMFhOMg1Zbos+TO+HpRyENhq4MVIwrpFaVv/3qJCr/p5WnMqqWxNrS0RFSOOxOIvepOnvXu228Fra0k/sk7eaTU9L58Mjg6aWd7ES9Fya3HTsiQyUsTBpfurNrYr56x8pPtQftUDLum0YcsU2S3ohGhHvisk0HOzSs=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_LNXP123MB258736FB6E413F55C81BA122EB7F0LNXP123MB2587GBRP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 77885a8b-8f32-4617-97e7-08d7614ed49d
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Nov 2019 17:45:49.7056 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a7f35688-9c00-4d5e-ba41-29f146377ab0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: jONRKR21DkaNADvxpsRkvW5jZibzhajbYA34GYWXAxbgtseD6Ta7kFccfgQ3IQIfqk1yTmdv3V+wuxXQ8iNWUw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LNXSPR01MB0021
X-NAI-Spam-Flag: NO
X-NAI-Spam-Threshold: 5
X-NAI-Spam-Score: 0
X-NAI-Spam-Report: 3 Rules triggered * 0 -- EDT_SDHA_ADR_FRG * 0 -- EDT_SDHA_DMN_FRG * 0 -- RV6666
X-NAI-Spam-Version: 2.2.0.9309 : core <6666> : inlines <7157> : streams <1837623> : uri <2933150>
X-OriginatorOrg: bt.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/coin/1BGIsnMOR1ppiHRpX73qcTEbCmc>
Subject: Re: [Coin] Draft-liu-coinrg-requirement-00 for discussion and comments
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: Mon, 04 Nov 2019 17:46:03 -0000

Peng,

Thanks for the draft, a few comments.

I agree with your target in Section 2.1 about integrating computing into the network.

Section 2.2 gives me the impression that COIN is all about great quality of service (deterministic, very low latency & packet loss).  I don't think COIN should be about developing new QoS techniques. As you hint at in the last paragraph of this section, if deterministic QoS is required then there are existing /emerging techniques for doing that, at least for networking resources (how about for computing resources?). I also think there are many COIN scenarios where it won't be critical to have low latency and packet loss rate.

Section 2.3 you mention the requirement for a network interface for the user to express their needs to the network. I agree that the interface between the "users" and the "COIN" is an important topic. Personally I don't think this is only about the user expressing their requirements - also the COIN expressing its capabilities (ie the resources it can offer), as I think this is important for making the system scale.

I think there are some very interesting requirements around the computing-networking overlap - for example, to allow joint optimisation over the (distributed) resources.

Best wishes,
Phil



From: Coin <coin-bounces@irtf.org> On Behalf Of liupengyjy@outlook.com
Sent: 10 July 2019 15:48
To: coin@irtf.org
Subject: [Coin] Draft-liu-coinrg-requirement-00 for discussion and comments

Dear all,

A new draft draft-liu-coinrg-requirement-00 was uploaded and available online https://datatracker.ietf.org/doc/draft-liu-coinrg-requirement/.

This draft points out the requirements including the new architecture, precision and intelligence of computing in network.

Comments are welcome!

Best regards,
Peng