IETF Logo Mail Archive

Re: [icnrg] reference needed for Interest-Interest

"Mosko, Marc <mmosko@parc.com>" <mmosko@parc.com> Mon, 09 March 2020 17:23 UTC

Return-Path: <mmosko@parc.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E98C3A1375 for <icnrg@ietfa.amsl.com>; Mon, 9 Mar 2020 10:23:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=parc.onmicrosoft.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 Co_C1uHYqWrR for <icnrg@ietfa.amsl.com>; Mon, 9 Mar 2020 10:23:54 -0700 (PDT)
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (mail-bn8nam12on2077.outbound.protection.outlook.com [40.107.237.77]) (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 49FD33A0D93 for <icnrg@irtf.org>; Mon, 9 Mar 2020 10:23:54 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=SXThYoEfEhQww/i5MMJDlbsy2dNoc5Y29KvghuTVBK7pKlDwJTW+oZoNiJ/n9pPHP6R+ZEk7UwdEih6WOEus+bUkWT1sXOFBYUJ9SqvKRkouyNXTeEEBhCrcfJxAAFKLPEHf/gvnYvGrpf8OPRmlFDY1FzqYaiwCOpPZVOSEVM97N9UdZx1gkA5G3T8YQQFjX+z2g2CnmLeWen0a1uxeBGR/YPOZ2cKL04qhvLMGRpEfHTvPvSgbQpx9uKNDtqKHzcjFwcXyr5Fx1gApfAfokUyD+h1wGLQIMxG7i7GYtrE7z8jQjbs2R9Dl5G2i3QSciTCQ9yafPWusVd8W1s1ZSQ==
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=p8UlEXF0aYsV56Q4qfiD98gEF7zluc+zWHzSPSM1PyM=; b=Qb5Sv6aesLyNQf+IXGF5xx5yhWgNDXe5IITCYZO6++nE2HakY00cw89mKrY156Q527vF4hRtE7hgwQsHGl8F64gdfHGc+5pSX9ZAUTMNBkUYSKDMzzOa/GfkSwfDeznzH6YeUfM0SPNHZ+fGflJe5Sn2VxCsa0vZISbyg8SEhki9yn6+B4uRpRIVv841dk9gYIMzfVujVFah/hbSq5mykKfKn7mlpuaV4qad1bTIr1UXHU26algykLqUy2TyF2YPpayN7wc7nQgtpgmbihF42iMJ6od5IzVElyl9wCbUj81JiGTai45F88ZJuIJh9OucQdcvVkjaJBegsKGrfqX0Wg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=parc.com; dmarc=pass action=none header.from=parc.com; dkim=pass header.d=parc.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parc.onmicrosoft.com; s=selector2-parc-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=p8UlEXF0aYsV56Q4qfiD98gEF7zluc+zWHzSPSM1PyM=; b=FhUac70KpxbqjXHSn7E9uLiTqPzrhqcMFiUIsOMiLQZCZo5HhB+f7vd136gYUFeDPcUFrMkuTeBUi4dMu2fgNtEthUTYk5E7WAjrxiEuZXcFeK1R6wBn/eZksPTN6MQEzGnchqm0wgJI06TInhVYk5psW90/JRxAWRQQzSlQfyc=
Received: from BYAPR15MB3272.namprd15.prod.outlook.com (2603:10b6:a03:110::17) by BYAPR15MB3335.namprd15.prod.outlook.com (2603:10b6:a03:104::30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2793.17; Mon, 9 Mar 2020 17:23:52 +0000
Received: from BYAPR15MB3272.namprd15.prod.outlook.com ([fe80::507e:3768:eb66:1e91]) by BYAPR15MB3272.namprd15.prod.outlook.com ([fe80::507e:3768:eb66:1e91%5]) with mapi id 15.20.2793.013; Mon, 9 Mar 2020 17:23:52 +0000
From: "Mosko, Marc <mmosko@parc.com>" <mmosko@parc.com>
To: Dirk Kutscher <ietf@dkutscher.net>, ICNRG <icnrg@irtf.org>
Thread-Topic: [icnrg] reference needed for Interest-Interest
Thread-Index: AQHV9hW24MHw4TEXc02rFPNr5krgAahATQCA///AfIA=
Date: Mon, 09 Mar 2020 17:23:52 +0000
Message-ID: <93B5F74D-D85C-4C59-AC30-78134FB8B09C@parc.com>
References: <47B7BCBF-83A9-44DC-B52E-3CFCB1A285E9@dkutscher.net> <D746AE95-A8A9-4FCA-B36F-7716DE519FA0@dkutscher.net>
In-Reply-To: <D746AE95-A8A9-4FCA-B36F-7716DE519FA0@dkutscher.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.21.0.200113
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mmosko@parc.com;
x-originating-ip: [2620:0:2e80:a00b::b]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 08195e3f-325b-4dcc-1d6e-08d7c44ea376
x-ms-traffictypediagnostic: BYAPR15MB3335:
x-microsoft-antispam-prvs: <BYAPR15MB3335C402E2407AEF05D405F1ADFE0@BYAPR15MB3335.namprd15.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0337AFFE9A
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(366004)(346002)(376002)(39840400004)(396003)(189003)(199004)(316002)(36542004)(2906002)(110136005)(5660300002)(186003)(86362001)(478600001)(8936002)(966005)(71200400001)(6486002)(36756003)(33656002)(66946007)(53546011)(76116006)(2616005)(81156014)(66476007)(81166006)(66556008)(6512007)(64756008)(8676002)(3450700001)(66446008)(9686003); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR15MB3335; H:BYAPR15MB3272.namprd15.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: parc.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 8jch2RR+0zqQmPzVUhQYDI4DtsgRWuTadesC43nWHRnhamuJp6Fz/Bj30NPB32Ua3DLjnpJWZ9ljCtXxCrqHWgyscYHGW2QmTpb3ZfA3ZOAG1D3jtOckvZ3MljagAf4hqZRN9i+1cJQv0qX+qh/KpZJBDIkifxEMsNVEeIKyDu6wpNs295CVBAxBQVIKQP9Dw3Y64lqkWVFKgNntzIDxEu5lNX196K2JSQ4I9CjXo2aP7zHKVU7YueEzuVsPBeDpOzWbKIyj7UrFj1lerVGW7EyunVtqs7VgGUr37ft142cEYDsEC/nwmFYOQjhdonBMwdG9ShkdtKbRqhtV45zRC9vyfka4+iAlja4l2Rf1PsbfpE/QPTP+aVUaQKxY07n9+Qzb7f7Mm5DU34URX3XDnWv3dJjwla6g7jFefRQ/RJ9FYPbygBz+KItqvvalTVVtqRpZvxIEBJ4O/pZBSep8R+bWy33zTA8Y7IE7XQ0BF1Os135PwIh9/PSQmh24ua5Id3BF/8DY1kQiPh/tn/ce3g==
x-ms-exchange-antispam-messagedata: I58ANtcXRrFkptm2CRo1lKi1bzpGNEv9smhYRKEy19fGMIVl0AREYhp+jr0qK/DnYTqFr3GX7O0/BlQj04H8mlOwnUD15dn1lgG9Yy9z0OApg6Mb522kLdexPZ816kF4//9aq95u9mXKQ3oZJwETGeAG7ZUOMWPI3f7DirSYOYY=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <F0A0A2C078C275418EC3657478943CBF@namprd15.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: parc.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 08195e3f-325b-4dcc-1d6e-08d7c44ea376
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Mar 2020 17:23:52.2826 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 733d6903-c9f1-4a0f-b05b-d75eddb52d0d
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: sLrkRpv1k9pNCN+tgWjPnDifS7Et4LF9e4EP5WFe7aiTJNsdi6FRAtSlEEyKGnHU
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR15MB3335
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/_x4qBul7MpzsXnZ_UEEEp6zLmhE>
Subject: Re: [icnrg] reference needed for Interest-Interest
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/icnrg/>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2020 17:23:56 -0000

The interest-interest-data semantics have been around in CCNx since the very early days.  It is the CCNx 0.x repository StartWrite command (https://github.com/ProjectCCNx/ccnx/blob/master/doc/technical/RepoProtocol.txt).  A producer sends an Interest to the repo asking that it fetch data from the producer.  The Repo sends an acknowledgement ContentObject and also starts fetching the data via normal interest-data exchanges.

The main issue with this approach is (a) the producer cannot tell which interests are from the repo and which are from another consumer, and (b) there is no "finished" notification, so the client must poll the repo to see if it has everything.  Both (a) and (b) mean the producer cannot easily discard the content as it does not know when the repo is done saving it.  A client can check if a particular segment is in the repository via the CheckedStartWrite command, though this is done segment-by-segment so is not particularly efficient.

The early Voice over CCNx (2009) paper used an Interest-Data exchange to kickoff bi-directional Interest-Data/Interest-Data exchanges in a different namespace.

The paper "CCNx 1.0 Bidirectional Streams " [https://arxiv.org/abs/1707.04738] extends the VoCCNx approach to a more robust repository protocol.   The document was originally published in 2013 or so as a tech report with the early CCNx 1.0 papers.

Marc

On 3/9/20, 7:12 AM, "icnrg on behalf of Dirk Kutscher" <icnrg-bounces@irtf.org on behalf of ietf@dkutscher.net> wrote:

    https://conferences.sigcomm.org/sigcomm/2011/papers/icn/p56.pdf
    
    from ICN-2011 describes the approach and its potential problems.
    
    Let me know if you have a better (seminal) reference.
    
    Thanks,
    Dirk
    
    On 9 Mar 2020, at 14:21, Dirk Kutscher wrote:
    
    > Hello everyone,
    >
    > I’m looking for a reference for the “Interest-Interest-Data” 
    > scheme (that has been proposed as a PUSH surrogate).
    >
    > Thanks,
    > Dirk
    >
    > _______________________________________________
    > icnrg mailing list
    > icnrg@irtf.org
    > https://www.irtf.org/mailman/listinfo/icnrg
    
    _______________________________________________
    icnrg mailing list
    icnrg@irtf.org
    https://www.irtf.org/mailman/listinfo/icnrg

v2.23.0 | Report a Bug | By Email