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

<philip.eardley@bt.com> Tue, 12 November 2019 10:21 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 83A5612003E for <coin@ietfa.amsl.com>; Tue, 12 Nov 2019 02:21:56 -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 bKVJeFCrTv2e for <coin@ietfa.amsl.com>; Tue, 12 Nov 2019 02:21:53 -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 20551120013 for <coin@irtf.org>; Tue, 12 Nov 2019 02:21:52 -0800 (PST)
Received: from tpw09926dag10h.domain1.systemhost.net (10.9.202.49) 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; Tue, 12 Nov 2019 10:21:49 +0000
Received: from tpw09926dag13g.domain1.systemhost.net (10.9.212.29) by tpw09926dag10h.domain1.systemhost.net (10.9.202.49) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 12 Nov 2019 10:21:49 +0000
Received: from bwp09926080.bt.com (10.36.82.111) by tpw09926dag13g.domain1.systemhost.net (10.9.212.29) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Tue, 12 Nov 2019 10:21:49 +0000
Received: from GBR01-CWL-obe.outbound.protection.outlook.com (104.47.20.59) by smtpe1.intersmtp.com (10.36.82.111) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1713.5; Tue, 12 Nov 2019 10:21:34 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=VeyM7rFzIKrmTiet2wVoEOwb+P/NBXMn/bDAFZ+UCGYxXaEqJeaHJuA/5MkXG0USaEp24D38ZIsO+fSUmd7G/sl8fl34iB8sbOnZ4uhNf3pmjFgUBFkPlekV8Hbxh3cjJSfmoPkL8Z1Htky9qDp+PlvxdyLvIxtQEGRZA7Vgf16aDE7GlXBfPHuPY4BVCzQCh/smEoOHCxEi4qcIJIh8bMUI7641+4zSrJIJWTVE929oxw9kYHwzuQXGt/vo4CNOrfyxDBzUuVRzHiKHKMRCMpNv4+AGpwteameYbWYtfw7QOcrKNIgJ9BuhbZmDGQE9vgKs6OJ2w4Wz3lG6DbCB3A==
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=yPh3RfcU/zZxHRWL3O8xD/sly6ChlpYBgIhZE3qnhYw=; b=Ox9NPX9ldk6id8YItuckqLPFvJ1FWCYLNP04UQHHJc+c8T3bY3Mw6mPsXSUm+3oFwIA/GKBR0tyuDO2JJRA5X8NOuOELqfbhBBQnUJmyiXFPbsUP9WBhOIEl5keFvdTBUwvJLki3+5aL8j/cSqYjafAJEiwbkQUNoXoZZPS6xgcriIs/woWrxuS1SmDnVkyRl3t/9P7a8l+38I4poEE21rs2ESJLj/fFbP1VRWWM2uANqeWonInKQZOW1x+omD0Y+xXd40BDY+kINGyLaErtrG6urhG7mUkH/7h8XWGYwn+ejd/rIk38vvGU8WEguPXEg20eek6tGY9Zt60R8mKTmQ==
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=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=yPh3RfcU/zZxHRWL3O8xD/sly6ChlpYBgIhZE3qnhYw=; b=EqH2hQh8B5IEdU6Q+i6YeiFI83KmnF2OtsivzT0+zLbSZEr3hlkQeBo3P7SawCRwehv9y+toxtdFg2Xd6Wo23vfpZnfA8der32aUCuWv1aU9YTJxmsSO+B4WN3Db9+OMkrkeTLcgwptHhJTtwHkRPhsB8HnpQ5GZba+XL00+Zyk=
Received: from LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM (20.179.128.78) by LNXP123MB2123.GBRP123.PROD.OUTLOOK.COM (20.176.159.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2430.24; Tue, 12 Nov 2019 10:21:44 +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.2430.027; Tue, 12 Nov 2019 10:21:44 +0000
From: <philip.eardley@bt.com>
To: <liupengyjy@outlook.com>, <coin@irtf.org>
Thread-Topic: RE: Draft-liu-coinrg-requirement-00 for discussion and comments
Thread-Index: AQHVNy13jQseX+U+yUKUHPhmTuOrJKeIFNUA
Date: Tue, 12 Nov 2019 10:21:44 +0000
Message-ID: <LNXP123MB2587EABCC1F2ECD38373E378EB770@LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM>
References: <TYAPR06MB2318F351A7840A558D77C648DAF00@TYAPR06MB2318.apcprd06.prod.outlook.com>, <LNXP123MB258736FB6E413F55C81BA122EB7F0@LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM> <PU1PR06MB2215BA135D7BD16A6AC523C5DA7A0@PU1PR06MB2215.apcprd06.prod.outlook.com>
In-Reply-To: <PU1PR06MB2215BA135D7BD16A6AC523C5DA7A0@PU1PR06MB2215.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: 3c00b69a-31cf-4f12-5e63-08d7675a1e49
x-ms-traffictypediagnostic: LNXP123MB2123:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <LNXP123MB212340E33FFE6526984E59F1EB770@LNXP123MB2123.GBRP123.PROD.OUTLOOK.COM>
x-antispam-2: 1
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 021975AE46
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(346002)(366004)(39860400002)(396003)(136003)(189003)(199004)(51914003)(2906002)(14454004)(76176011)(966005)(7736002)(74316002)(25786009)(11346002)(81166006)(81156014)(8676002)(606006)(86362001)(229853002)(7696005)(476003)(486006)(446003)(33656002)(8936002)(53546011)(316002)(6506007)(54896002)(110136005)(26005)(64756008)(66946007)(99286004)(55016002)(66556008)(66476007)(76116006)(66446008)(236005)(6246003)(71190400001)(71200400001)(66066001)(6436002)(9686003)(45080400002)(790700001)(6116002)(3846002)(6306002)(478600001)(256004)(14444005)(186003)(5660300002)(102836004)(52536014); DIR:OUT; SFP:1101; SCL:1; SRVR:LNXP123MB2123; 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: p3/1Mb6vj010rdVuaXQEKPxlXh3G/o7EANQgvkmh8uVlVRO+9aTxxfTonLNlwijLt4yFdrjoOLv1ijAtZRg9V0K8b5isc0ByBUTBsGx8qwHy8ZgLRLkdvjG6ow29GBZjWx4CLtulKByKZwqQ16/PV1tnBbwxNI3cGN0cE9ULqQkebIVVMDpA80vQR4XMlIcinGZgCmqZ1yQalNCEAOWuVxwClCvC6FEWZXGZbVE3qJjMXS8xH0bzaR19hD/vMhlgk5xJ3V540OUymKohjvBp4RdjjJFfLglz0DAe4WKqCYia7z5WNsk32EfjMUdx5Y79rcgcRGfK5xsDipHpNOE+o7/TMWscg5IO1GxHQhIP9lPRQ3vK06y/HEPm9K4CpSdpeJEkZHorjmtyhkm/LatFB62uGLQqwXYyvixCUhHdbvM+QGqfstQTIuLQipf/AImv4T1B5hUwb9mqfg0pR7uhQP/EXuYp8JYzc90vtBK3Zp0=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_LNXP123MB2587EABCC1F2ECD38373E378EB770LNXP123MB2587GBRP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 3c00b69a-31cf-4f12-5e63-08d7675a1e49
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Nov 2019 10:21:44.7267 (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: a3w+Tv1AZR6Ya8r8rFrQjd9NKosnrUr4/HtkOXvwOjWPOTqsPtEAQxEiwKcngOMGX2piSCj+J4XXDtfiXP/Biw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LNXP123MB2123
X-OriginatorOrg: bt.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/coin/QnTsoIztih0eEAlXt30rUZg1kn8>
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: Tue, 12 Nov 2019 10:21:57 -0000

Peng,

Can you explain a bit more about the problems with existing techniques for low /deterministic latency and packet loss? It would also be interesting to hear if there are specific issues of network computing that make the requirements more strict than for ‘ordinary’ applications.

I think it’s important to get the interface between the user & network correct.

The joint optimisation topic is discussed a bit in https://tools.ietf.org/html/draft-kutscher-coinrg-dir-01#section-5 – but I’m not sure how much we need to say in a requirements document.

Best wishes,
phil

From: 刘 鹏 <liupengyjy@outlook.com>
Sent: 09 November 2019 07:52
To: Eardley,PL,Philip,TUD1 R <philip.eardley@bt.com>; coin <coin@irtf.org>
Subject: Re: RE: Draft-liu-coinrg-requirement-00 for discussion and comments

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<mailto: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<mailto:coin-bounces@irtf.org>> On Behalf Of liupengyjy@outlook.com<mailto:liupengyjy@outlook.com>
Sent: 10 July 2019 15:48
To: coin@irtf.org<mailto: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