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

刘 鹏 <liupengyjy@outlook.com> Sat, 09 November 2019 07:51 UTC

Return-Path: <liupengyjy@outlook.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 4F19012084C for <coin@ietfa.amsl.com>; Fri, 8 Nov 2019 23:51:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level:
X-Spam-Status: No, score=-1.989 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outlook.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 QwDvLcamASB1 for <coin@ietfa.amsl.com>; Fri, 8 Nov 2019 23:51:47 -0800 (PST)
Received: from APC01-HK2-obe.outbound.protection.outlook.com (mail-oln040092255108.outbound.protection.outlook.com [40.92.255.108]) (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 26B9D120827 for <coin@irtf.org>; Fri, 8 Nov 2019 23:51:46 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=bhBDFbs1BWITlyv3sUiAb6ymYEivgX1O9PbCtI3plSfdQQCB9eNgT4r1Rv4Ho275E8XGf+IBi75oftY2qTVnEqmFDefX5Qrsg4VCwyn1/J43UCcs/ApmPS3OZYUpYoKKwhYKS4WPyUJ4mJefUMDVmFuUU7VyJI/51aS6Ptl4SUQ0ZFMPqNH2tDd2qjLWn9XNK/Z3l5qVUSPAooanz2EbyRwX0Fzg+miUhHjItmLJdHy/m7ciYI4+1ms+7NapKyTNNELHo7nS0CiBw+yhL5i+v17V2tNhtmLq8OHrxMCpHMnOjC9TJpQ5mbAhxS8s5KP7YMdAfDhi7eepH2POMta1XQ==
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=ZExakE28VDdIXv/a3UCrgKU0WQcvuNTeSP3dnH24cAI=; b=RpRD/ykVL65UhCbOcOTAlIqVIiwfufDCIf5Ud3zO59zpbrmiz5qm2Aw7HDmWzN7qYI82w+6S4BaI7oxMQ/LtpsMlWzx/ly3lLhPiZXa2FCvsyEc4sj8hK98iJEhJj9b+xYjYO3Uko+uZUBnn0FB3BMOVJPCZSL7Bk5/DPVqCnoLZFHZ7ymT1J6jjFMLA8ZRok/buNma+SEhq3GfSszA/fwRXM4VjyquNQOk+Tn0wDrzwJvVTlClvZ2+okniqrN2IMhr2OWKsAAhWdgly5QL3GrnemkFA0aLVyyyDJn9cFBPqljBugox/J+OSSaqDNtW9NPMsdy0aGjO6/e9pfeVnUw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ZExakE28VDdIXv/a3UCrgKU0WQcvuNTeSP3dnH24cAI=; b=gfBDKIu0qkXmP7J45+46RsSiLyrV9K4meO/e/xYd0G6FCMAqk/8VP2vJAoCqGof0+RbQ+ILMPuM134SccVVYx/yVyaTS+49rA34hlA4bJElooUPr3zzhju9CA9E5q8qOHtONTtUp1tpHwLoRxabjPjqG0md+y83YGx+psRQUVKssG+Gqu64CSsnmfXX4COgN88rSqsCR8TaS8PG5CsxpxLshCuuaf6c54EjFnybdhX263nb3Ok/XQ8CCDbp/AZ2uE8WbKft6aR2UqZvVb+WPjWxn8HNmAmZvedDCkMCUYitgB7Rd5MrZb4ZCdrT0QDeYlmuvdw6Mn8fpNznp6gk5uQ==
Received: from PU1APC01FT029.eop-APC01.prod.protection.outlook.com (10.152.252.52) by PU1APC01HT176.eop-APC01.prod.protection.outlook.com (10.152.253.182) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2430.22; Sat, 9 Nov 2019 07:51:43 +0000
Received: from PU1PR06MB2215.apcprd06.prod.outlook.com (10.152.252.52) by PU1APC01FT029.mail.protection.outlook.com (10.152.252.209) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2430.22 via Frontend Transport; Sat, 9 Nov 2019 07:51:43 +0000
Received: from PU1PR06MB2215.apcprd06.prod.outlook.com ([fe80::c13e:445a:35ce:e24a]) by PU1PR06MB2215.apcprd06.prod.outlook.com ([fe80::c13e:445a:35ce:e24a%6]) with mapi id 15.20.2430.023; Sat, 9 Nov 2019 07:51:43 +0000
From: =?utf-8?B?5YiYIOm5jw==?= <liupengyjy@outlook.com>
To: "philip.eardley@bt.com" <philip.eardley@bt.com>, coin <coin@irtf.org>
Thread-Topic: RE: Draft-liu-coinrg-requirement-00 for discussion and comments
Thread-Index: AQHVNy13jQseX+U+yUKUHPhmTuOrJA==
Date: Sat, 9 Nov 2019 07:51:43 +0000
Message-ID: <PU1PR06MB2215BA135D7BD16A6AC523C5DA7A0@PU1PR06MB2215.apcprd06.prod.outlook.com>
References: <TYAPR06MB2318F351A7840A558D77C648DAF00@TYAPR06MB2318.apcprd06.prod.outlook.com>, <LNXP123MB258736FB6E413F55C81BA122EB7F0@LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: HK0PR03CA0120.apcprd03.prod.outlook.com (2603:1096:203:b0::36) To PU1PR06MB2215.apcprd06.prod.outlook.com (2603:1096:803:38::11)
x-incomingtopheadermarker: OriginalChecksum:C041FDC2E0C5A0C3D2037190AC73299359F5817681190291BE4F616E7924D006; UpperCasedChecksum:0E7B4634093414924F2134CC47B02CD04279CFD0A68AA44A8690972D639B321A; SizeAsReceived:7405; Count:51
x-ms-exchange-messagesentrepresentingtype: 1
x-guid: 4710D759-42CC-4FA8-BE0A-28D57FA4E5DE
x-has-attach: no
x-mailer: Foxmail 7.2.9.115[cn]
x-tmn: [WHGuRkHc/0XNkn1U+raMqpr7H4kHoIZ/]
x-microsoft-original-message-id: <2019110915513829197222@outlook.com>
x-ms-publictraffictype: Email
x-incomingheadercount: 51
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: c9ed1b67-382f-4bcb-4616-08d764e9a954
x-ms-traffictypediagnostic: PU1APC01HT176:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: ty8YIz2sOPcksVb/R6hTR6ePQ2uuZIPj/mPq5gNrM99eivxOn/xHENwIyTMLgPkFVKuTg+4yPmbEQ6m9K1zneMEcrd+7Cp6l1N/n77Tmgma28Ecqnr/ILvkCLARDQBMBQQhEu3yOsAo7kqaL/bs9lhvk/mUGRA4FqXVwv2syDlVO6oMKKO2NBSeLH3jUVmy7
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_PU1PR06MB2215BA135D7BD16A6AC523C5DA7A0PU1PR06MB2215apcp_"
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: c9ed1b67-382f-4bcb-4616-08d764e9a954
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Nov 2019 07:51:43.4750 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PU1APC01HT176
Archived-At: <https://mailarchive.ietf.org/arch/msg/coin/DBPkFwSWSKCsMxoBYX5NEmMTGfk>
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: Sat, 09 Nov 2019 07:51:51 -0000

Hi philip,

Thank you for comments.

I agree with you that not all scenarios require low latency and packet loss rate. There might be some basic applications just need some computing capabilities of network. What I thought about was that for new applications, there might be high requirements for the network, especially based on the new architecture of computing in the network. There are some existing techniques for deterministic latency and packet loss rate. But I am not sure if there would be some problems of adaptability in network computing.

Section 2.3 wanted to express exposing each other's requirements and capabilities of user and network , maybe it was a little terse.

For the joint optimisation over the distributed resources, I think it's a interesting topic, do you have any more ideas about it? More discussion is welcome!

Thanks again.

Regards,
Peng
________________________________
liupengyjy@outlook.com

From: philip.eardley@bt.com<mailto:philip.eardley@bt.com>
Date: 2019-11-05 01:45
To: liupengyjy@outlook.com<mailto:liupengyjy@outlook.com>; coin@irtf.org<mailto:coin@irtf.org>
Subject: RE: Draft-liu-coinrg-requirement-00 for discussion and comments
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