Re: [icnrg] FLIC and error reporting

Marc Mosko <mmosko@parc.com> Tue, 04 August 2020 07:34 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 B346F3A0F61 for <icnrg@ietfa.amsl.com>; Tue, 4 Aug 2020 00:34:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 hN4I-VKZ4t4M for <icnrg@ietfa.amsl.com>; Tue, 4 Aug 2020 00:34:27 -0700 (PDT)
Received: from NAM10-DM6-obe.outbound.protection.outlook.com (mail-dm6nam10on2062.outbound.protection.outlook.com [40.107.93.62]) (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 D4C263A0F67 for <icnrg@irtf.org>; Tue, 4 Aug 2020 00:34:26 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=lwSWUBSpc5l+1rrqTr6tbMvBwUajuIrCOFSWI0h/w3NsqT5PMrGJLo3E0qas+Zw5h8zjxDgaEFsfX2675LYIvKV+2qbW5qLs1MSpM6BF3365gHwmv3mg9IOHBL00fsLid1PfzxXHLJRXQowVdR8wvVoUdhrrVKuXlt2b4LPtwShfoz3yOyVQja89yNnsW4PN6PMG9Oz2JVOcvob4pgAbOmxelGZlB8m9giY0a2EoNKCSLL8wKDfNrYBjwng97LEYvGrDZylMj9XVeuBe83cPXzV4du7Xm57rrbmoqRMrzrz9KxmiO72rh4mGgbD1xYJdh4sfGap4LTB2hfDBB8+8KQ==
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=Ilfybd3fTtLOaxNgsiLIbrrnB2JymLD0QM+uoaAzMM0=; b=bpI/gRcxRhpuwI3zgX1UAQuXmlBY7S9NloJyvu3BZh8vksZvXO2aZj/0hdG8N6ndDn0bL2LcVH4EXB167o7r55pZ2w1Z2GDXxwwnCeOKhWMk3nHIdYcFhJa164w0753x4ZtqO39VV2+2jpl8nAcTfBicIqxRjHXH1lXdlQmgf+HhELGNGTLQcXcQRMtWy3t9oNNHZ//BZ9vyQXIwiGc+4chVaSzBDllenL6TVoYV9omjtmL57qoY4AB0Oa6IhXpKXEbVaq0d9oCNf7mFmQju3WqioQGajoYo5OdUVkGagmCy9eV1USiTGxyd6V7XJ7tYUDC1pIGWBfm5We1RJDNyvA==
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=Ilfybd3fTtLOaxNgsiLIbrrnB2JymLD0QM+uoaAzMM0=; b=j/3V6kDMZDR5Hluv6jKfTlRlYcLS16YpbM8lpMaGxOAo+EjILeZv4/YBJxtbSDjKWpTY4lex0Vlw+VIp0eHjAL9v/mznOwwx01b8YfNiOaRclfyp7+xzibi8LbjiUZgCMH7d+gWKpW/E4Hqb6+AuQXHCutS3Tr07UpCMTiySNSU=
Received: from BYAPR15MB3238.namprd15.prod.outlook.com (2603:10b6:a03:106::29) by BY5PR15MB3537.namprd15.prod.outlook.com (2603:10b6:a03:1f5::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3239.19; Tue, 4 Aug 2020 07:34:19 +0000
Received: from BYAPR15MB3238.namprd15.prod.outlook.com ([fe80::1045:4aad:16d6:c0e6]) by BYAPR15MB3238.namprd15.prod.outlook.com ([fe80::1045:4aad:16d6:c0e6%7]) with mapi id 15.20.3239.022; Tue, 4 Aug 2020 07:34:19 +0000
From: Marc Mosko <mmosko@parc.com>
To: =?utf-8?B?Q2VuayBHw7xuZG/En2Fu?= <mail=2Bietf=40gundogan.net@dmarc.ietf.org>, "icnrg@irtf.org" <icnrg@irtf.org>
Thread-Topic: [icnrg] FLIC and error reporting
Thread-Index: AQHWaizHgO6NZbx4eUaRyY4DoYb67KknGaAA
Date: Tue, 4 Aug 2020 07:34:19 +0000
Message-ID: <8544E3E6-E5C4-4785-ABF2-8AC446711711@parc.com>
References: <87y2mu522u.fsf@gundogan.net>
In-Reply-To: <87y2mu522u.fsf@gundogan.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.39.20071300
authentication-results: dmarc.ietf.org; dkim=none (message not signed) header.d=none;dmarc.ietf.org; dmarc=none action=none header.from=parc.com;
x-originating-ip: [50.0.67.90]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 77492c58-95b3-4637-4c10-08d83848cc8d
x-ms-traffictypediagnostic: BY5PR15MB3537:
x-microsoft-antispam-prvs: <BY5PR15MB3537A979DC97BB2A68EEB181AD4A0@BY5PR15MB3537.namprd15.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: +gsGAkoIk7RPafKqrukIHZvrOfSRQBfWSAPEGbkT/Q96pWSYh76is5z6ZCgrmBjUWyC6dk22qR3YXP4E/IKlTedTFzv31NIFakGJOCmbFcwoMlPSoE1Zt/U4znhvyDTEFyez8R8K7DnT2GVuAVV8ZPXD4s19frMnLIUqKyUN72EuBjMH8v5WnnNHMpHdMVRPYvJEKFWtrG18tVICstGK/PkXjsmUo/Tk++HKNHJ28ka+ekmjPQ8Q9Ap0v1fPeR3W6MGttRcsw1C16dNWW0pqQ4MEPpX5UePxwoWjtoGZZq24b/uXAzcVRQ1xd1hW9a+u2nxZljlPmoRcbtW+i/xsBYDsjtWT5Em7vO3NMat2HTZ0hsEC2goIku7HPcMMux/ybBXJOa91pEI4LKEYvNuXhg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BYAPR15MB3238.namprd15.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(39850400004)(366004)(346002)(396003)(136003)(376002)(91956017)(966005)(478600001)(36756003)(71200400001)(8676002)(8936002)(186003)(26005)(33656002)(6506007)(316002)(5660300002)(86362001)(2906002)(110136005)(66476007)(64756008)(66446008)(6486002)(66556008)(66946007)(2616005)(83380400001)(6512007)(83080400001)(76116006)(66574015); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: A9qVvwpo/SRjGCnuqaGn58pN0kDH8NLopjNwPyRaoeQjAYC3tm+Xy/jFZ4wFAW+hEneCdpHIv/as7QWsxTzRJFe2tAmDacEqHKjvDen4xIm/z7cRyQw9O7396ucgfgAXgScfuFljE4cSEuFgUC2k93EIrEwbOEyRZa6eP/XtN+AKiM8p4sWIoD5QGVekGU48j8v69Rd7h8ccYe5eaM/KLn7JLqM2OEd2S3sFJ/ouFOOfzs6W6Kn26N2SQnve39fmTCs3lQ2vvDXLa252sphdE7sZCOI1RoFJdSWKgqcIDQRvSud4DA0p1wA4g0mMnBQNVKoDoMvaxCyd2FqLUnbQm6OF+guKsZvAj0OJKr64ayDJ2vP2smPX8m50errh8LItyqTFPm+C5yzgF0U6qgMJB9Fl11B2r7B3yh47t93Y+QIFRwTyPBsIdHcS1GnR2WykUJaDfiSTh5IvAP3MF2D1K4sMiW42V+lVaX5c/H/3l+U/+/871SObivb5oiOzbazSFNlLaMIHPf5AEhw5F3RvvhbOzfdT+BtJpxBVXK7z6LaY/cCsJHXbrxrj0xUvNwuWVQMXq9vcp+dCps3DiZIRVrpf/EwxKL1S+04/RrQZIv/Vx/EZqgtg2vFwBh69d2AccW03aBC4SqoQF4/Dr5MpUw==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <C8CB39B9FDF2EA4B878AB7AABF428EA1@namprd15.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: parc.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BYAPR15MB3238.namprd15.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 77492c58-95b3-4637-4c10-08d83848cc8d
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Aug 2020 07:34:19.2088 (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: lRJtTRb4Ep0DR1GDxhtJg8g4rTWfcS0F5E/5Qcp/6PmN0u4hgVAX0RkaYi7gZvHg
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR15MB3537
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/MFvLk7jnDabG83ypL7cZnfJxPDM>
Subject: Re: [icnrg] FLIC and error reporting
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: Tue, 04 Aug 2020 07:34:29 -0000

There are two types of errors (at least). One is a TLV structural error.  In those cases, you likely want to discard the object and maybe report it locally, but I would not send more network traffic due to it, apart from maybe re-requesting it.  Another type is some sort of traversal error like you mention.  That falls squarely in application space, I think, and should be handled by whatever error reporting mechanism a publisher has (if any).  I do not think InterestReturn is appropriate (you have an error in data, not interest, anyway).  I would not try to use a network control message to report application logic error.

If a particular application has a secure consumer back channel (not just interests), then there could be a protocol for a consumer to give feedback.  But I do not think plain, unsecured Interests are the way to do it.

Marc

On 8/3/20, 11:59 PM, "icnrg on behalf of Cenk Gündoğan" <icnrg-bounces@irtf.org on behalf of mail=2Bietf=40gundogan.net@dmarc.ietf.org> wrote:

    Hello,

    following yesterday's discussions and rereading the notes [1] and the
    -02 draft version, I noticed that there are no references to error
    reporting.

    Certain operations (like traversing or seeking the tree) may yield
    errors (pointer out-of-range [2] -EINVAL, denied access based on an ACL
    -EPERM, locked data structure, e.g., during re-publishing or
    deduplication -EAGAIN, ...). How does an error that concerns operations
    on a manifest tree propagate back to the source?

    One way would be to leverage the existing mechanism, which is

    1) for CCNx: InterestReturn (with an 8-bit return code),
    2) for NDN: AFAIK NDNLP provides the Interest NACK feature [3]

    Another way would be to come up with an orthogonal error reporting
    feature for manifests only, e.g., by using another PayloadType. The
    advantage would be a more fine-grained control over error codes and
    corrective actions. The disadvantage .. well, it can get more complex.

    FWIW, error handling (in either way) and how it is mapped to CCNx/NDN
    could probably be mentioned in the FLIC base draft.

    Just my 2 cents ..

    On a separate note, I wanted to thank the chairs and the FLIC experts
    for yesterday's interim. I liked the format of having a focused and
    technical discussion round.

    Cheers,
    Cenk

    [1] https://codimd.ietf.org/icnrg-interim-2020-08-03
    [2] https://tools.ietf.org/html/draft-irtf-icnrg-flic-02#section-4.2
    [3] https://redmine.named-data.net/projects/nfd/wiki/NDNLPv2#Network-NACK

    --
    Cenk Gündoğan

    Hamburg University of Applied Sciences
    Dept. of Computer Science / Internet Technologies Group
    Berliner Tor 7, 20099 Hamburg, Germany
    Fon: +49 40 42875 - 8426
    Mail: cenk.guendogan@haw-hamburg.de
    Web: https://www.inet.haw-hamburg.de/