Re: [core] A couple of late comments on Hop-Limit

Christer Holmberg <christer.holmberg@ericsson.com> Wed, 16 October 2019 11:26 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09C39120164 for <core@ietfa.amsl.com>; Wed, 16 Oct 2019 04:26:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 2S0dlBommDvn for <core@ietfa.amsl.com>; Wed, 16 Oct 2019 04:26:10 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-eopbgr150082.outbound.protection.outlook.com [40.107.15.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 070541200F1 for <core@ietf.org>; Wed, 16 Oct 2019 04:26:09 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=IssATXVAPpE0jDLvESvlboSNRGD5+OPAnV3EPQLhlKVo6NO8s2eiHl6jnYabA0vWc0Iylb56b1W+vJXSvAVrpj/8XS17vJ1fE1qmxVH8WjUf4sbksciawNuc2VPYrnKEOiYZi1xCBQg+4f6qDuzJlW6CSXk/oTEPWDysJMebniMkSZ19eCWCXYqspARnK4JBv5mCbhYf7C48zA1fFuboa2eYdgMYZ2P1MM6VpXUhX2e1k+Dav6FxvAI5nlz8LkKBRVbIL+3s2JOYsxqJqohtU4gVRr5TRteo6wKqNUUi/EicZLF+Q9JG/r5ReGH0LBoSRE8fbfbnaT/gC+FTVBSCpw==
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=1F82+qANQlLwJOxc6Yok8bQHfTBX4uAUDUoxIe/zvS8=; b=lfgSsDZtFREuQDHE5RH73luqa64AcVK3JdA6EltRDMRq8XwvQVXoh/178c+jLg9Nx05qnLMw/mlCrTak3i4FCbFtzfidxH/7T5hZJrlwx6WaxoLmMfgYEaZcRUFPBUzzFYipFXZZBnq1qm8CvJBQZNolbg8ga6vIWW65yRYX1ce3EhrprXcGKrZZKPaUaU3adcb/BKwb32jlISKNX/w/ktfe+sZhfPoCyTK3vuqc30wwu/kBF2GS+MabzXFRv1b8iea/dvLk5s5I/SLLp8EBqO6UqqYXmmwoiDhnhmf0kj2TWfXkq2ZJEc+0EsWBB3AmkIxWpxembDRbjIxEbCbiAA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=1F82+qANQlLwJOxc6Yok8bQHfTBX4uAUDUoxIe/zvS8=; b=Rm6TZdArcJRGX7m6wlGwr+LE4xRP3lD7tM508Vj1Yk2EYjqtmI8tSK4WDQ5r8v6RoGd8PQ0/l+ODzUeUaXEqElwiBq5B8FfvIlE3LCJEdU/fFk67klIHX6TzThxEJsm6NdvCH+lGWrxOjP5gjVgBmwwWDB69nATkJqjyO54Q+qg=
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com (10.170.245.23) by HE1PR07MB4220.eurprd07.prod.outlook.com (20.176.168.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2367.14; Wed, 16 Oct 2019 11:26:07 +0000
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::14d0:5c4f:26b7:b6e9]) by HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::14d0:5c4f:26b7:b6e9%3]) with mapi id 15.20.2347.023; Wed, 16 Oct 2019 11:26:07 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Carsten Bormann <cabo@tzi.org>
CC: "core@ietf.org" <core@ietf.org>
Thread-Topic: [core] A couple of late comments on Hop-Limit
Thread-Index: AQHVhApYYBijvGsxFUafcFUkAAupTKddHg0AgAA1KoA=
Date: Wed, 16 Oct 2019 11:26:07 +0000
Message-ID: <FF5FA0C8-B277-471F-8392-FCB87971DB7B@ericsson.com>
References: <9D131FD6-2CE8-4C23-8BF1-0641C3E65A46@ericsson.com> <D43A1E52-FF72-4A23-8D3F-BD6E62FDCEB6@tzi.org>
In-Reply-To: <D43A1E52-FF72-4A23-8D3F-BD6E62FDCEB6@tzi.org>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1d.0.190908
authentication-results: spf=none (sender IP is ) smtp.mailfrom=christer.holmberg@ericsson.com;
x-originating-ip: [89.166.49.243]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 7f9d3599-b010-4ec0-651a-08d7522ba396
x-ms-traffictypediagnostic: HE1PR07MB4220:
x-microsoft-antispam-prvs: <HE1PR07MB422077EF61DBCAED6B9D396693920@HE1PR07MB4220.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0192E812EC
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(346002)(376002)(39860400002)(136003)(396003)(199004)(189003)(2906002)(76176011)(66946007)(81166006)(256004)(81156014)(8936002)(6506007)(8676002)(99286004)(33656002)(71190400001)(71200400001)(102836004)(66066001)(36756003)(76116006)(66556008)(14444005)(66476007)(3846002)(6116002)(66446008)(64756008)(6916009)(11346002)(5660300002)(316002)(486006)(2616005)(44832011)(25786009)(4326008)(476003)(186003)(7736002)(6486002)(446003)(478600001)(229853002)(6512007)(26005)(58126008)(14454004)(305945005)(86362001)(6246003)(6436002); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB4220; H:HE1PR07MB3161.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: gOI+2bpD8K2KGlNYeRT9Y9UFEX2zcNgvX6qrmLVMoFVnE6/OZbZFp9lViD2vXBa70Fw6lEZ2H7Qk/uCdFr/n7Vw31MJl9gdGUlBfaBI7NIBwMRKHApY4ut8zTwEOhE1HPGTk3dAJCNG3Y+ki3wJ/QvNEtLpFV3Qh8a02xRIwySre/OLIc5nWVtIyJVA0eKBvO0qHn88QIN8xQK/V+jX1bhQgt3KKZ6a2TJb++ZuskUHsMo5XlQ5Zak4v30HJmT9R3/jN+lbREnPiMmYvILf3T1v7HBPC4rG4MEfqRs5IqzOfTiqOBr25okOL9IYYx83+tsGZEx0mv6i+RtjRmsr7dCGkINRz5dv93pVb/2VjtKfl/krFRd5VWbtJUxcrUNcUy3jey+VDN+BYasGH9Wnu/nqKFLm+G0a5aGm10xvg1Tc=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <FF327D563461F44DA39A1DBFE6CBE072@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 7f9d3599-b010-4ec0-651a-08d7522ba396
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Oct 2019 11:26:07.5399 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: M+lcOTWiApzRWuCJqokY9bNG6gMlt1xxaOi2c4s0LeZg9N/xw+18Lq7ZatWsYhuaJwUgx0YJ7Ii7wQuSHNu3JXXjpxZcDLD/yYEtvzTBlqQ=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB4220
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/MIz_6nvoZ6mjyZrzkfmAkaPHRis>
Subject: Re: [core] A couple of late comments on Hop-Limit
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Oct 2019 11:26:12 -0000

Hi,

    >> Q2:
    >>  
    >> The draft says that a CoAP message with the Hop-Limit option value set to 0 bigger than 255 must be rejected with a 4.00 Bad Request response.
    >
    > There are two cases here: 0, and > 255.  The latter would be a syntax error for this option; the option description clearly limits the value to 
    > a single byte (Table 1).  Zero is not a syntax error, but a value that the authors chose to disallow.
    >
    >> 	• Is 4.00 really an appropriate response code? When reading the HTTP definition for 400 Bad Request (CoAP inherits the semantics), it 
    >>       is about a client error (miss formed message, etc), which is not the case here.
    >
    > A syntax error or a disallowed value in a request is a client error, no?

    The client may have included a valid value, but due to too many hops it reached 0. That is not a client error in my opinion.

    Sure, if the value is larger than 255 I guess 4.00 would be ok, because that is a protocol violation.

    >> 	• Based on my experience in SIP, it is VERY useful to have a dedicated response code for this (SIP defines ‘483 Too Many Hops’).
    >
    > We do have one for this case: TBA1 | Hop Limit Reached
    > But this is different from a syntax error.

    Yes, I noticed that (and just sent a reply about it).

    But, again, if the value reaches 0, shouldn't TBA1 be used instead of 4.00? 

    >> Because, when this happens, it is often related to *network configuration and/or routing issues* – not to client implementation
    >> issues – so it is VERY useful information when trying to figure out why the message was rejected.
    >
    > Specific response codes are useful if you want specific state machine transitions to happen

    Specific response codes are also very useful for debugging - especially in this case where one probably should start by looking at the network/routing configurations instead of the endpoint implementations.

Regards,

Christer