IETF Logo Mail Archive

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

Christer Holmberg <christer.holmberg@ericsson.com> Wed, 16 October 2019 11:19 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 1942F120168 for <core@ietfa.amsl.com>; Wed, 16 Oct 2019 04:19:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 FynWF_0ba4tw for <core@ietfa.amsl.com>; Wed, 16 Oct 2019 04:19:13 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on061b.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe02::61b]) (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 AFA54120154 for <core@ietf.org>; Wed, 16 Oct 2019 04:19:12 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=a/89VVcL5o6hT2rRWNqk2uQqR+eX6cW3yBPkCn2qf0g78xczxNOCMn3wHzwMQsYaN6in8P4/rrBk5VatsOo6C9l6HqWSht1N0LwyOlnzZqrFYAM5nHbQzxKWxIsTDzLYb+xjsOR++3pvBV+OScuyGkfGyvN5Je55PVI5FtAGfsgcKIYkGzwzIRYgb3mo5El8HGAVZuhJgh0Bo2s43YQUnHhPukD/n4MA4wMxV/T1m3iM68XFWcv+aYdYoC/TwQyseilgtMHYYbWISkSDareDIGlSi/8UPRo1gmHYqwNPGHUUduHQE02QW0a/vlS7gM++ThPfp+xfI4/7MqK5/w/GHg==
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=PGs3huX1V3kboYKU9NejjA6+E6adpJwm5yAwbDrY6A0=; b=Zq6WiYlmURiplk76WRu+70cT6rDobUB3ooa538D9JZpcSocRBx08MpskkjkqipLwQF7+sRSSWDjj0J2uOTspo9z5ufPGirvxusaBZduBQ1SQRC9fxlr5sArDtGqGKL9a7DGRPGcLHbANuIC2VIcwSb4qqsmVTt6jR67uTH2+rbkWlrbe2hu3XJDC5vYCPxGwnLdaMNl6CCP/cvvP5bEDtbrtXqcFitAHgDAmtpE9Kpe+dMkRbfsAHSWupUipcqaQm8SjtflmujHhCCwIQZcV3ZL1RjiuyORB7WjTg6hbzc0ozGZy5Byy45B3q7Y6T7aS+O2oDjdIXqMRpS+OWiJ45Q==
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=PGs3huX1V3kboYKU9NejjA6+E6adpJwm5yAwbDrY6A0=; b=oaloCmsnP642B1xqnoz9aSE/64SD/g8TXgoluMpN/h6eWPGvCM9s7T5vW2nssEzxN+oZeigSeZrq36ICRsYmmJx/Zf9qyoAFZxVnF38/3VUtnO/UCdCNhDqBxVUVjnkItBC8AFyF0J0bqbx90n03/2pUAiiErXTjnZh3zMRekGY=
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:19:10 +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:19:10 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg=40ericsson.com@dmarc.ietf.org>, "core@ietf.org" <core@ietf.org>
Thread-Topic: [core] A couple of late comments on Hop-Limit
Thread-Index: AQHVhBOImxUqJiehEkST/oZlh6cTzA==
Date: Wed, 16 Oct 2019 11:19:09 +0000
Message-ID: <FAEC72BC-D475-4004-9F11-DCCE24EB1D55@ericsson.com>
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: 1bd5d5fb-5b82-40ec-64c8-08d7522aaaa7
x-ms-traffictypediagnostic: HE1PR07MB4220:
x-microsoft-antispam-prvs: <HE1PR07MB4220590F448B72F0C992FE7493920@HE1PR07MB4220.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0192E812EC
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(39860400002)(376002)(346002)(396003)(366004)(199004)(189003)(5660300002)(316002)(2616005)(44832011)(486006)(58126008)(110136005)(6246003)(6436002)(14454004)(86362001)(186003)(476003)(25786009)(478600001)(6306002)(26005)(54896002)(6512007)(229853002)(7736002)(6486002)(8676002)(6506007)(102836004)(71200400001)(71190400001)(33656002)(99286004)(81166006)(2906002)(66946007)(256004)(8936002)(81156014)(66446008)(6116002)(3846002)(66476007)(64756008)(14444005)(66556008)(76116006)(66066001)(2501003)(36756003); 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: 3vjKh9YEaLzKA14ckhgGkuo6M5X7/LW7Bl497PBuwTHYZ5LdHcIul3iBTHyKHbgEnLaLc/xTqDV7wBQ4FkoQO6rX+p5YrExEMwnjbff5P348G3emAZlZeFykcXMqHScsgTLcVGYr+luOXON1+u4LkAj0/+s92J8tRrVXNvsdv+MlQh/DUQgPHNBIoDQrWpywpkkQyEWEP2fyQYPDUJIO+IvVbA3ZMOWi33Nohtr1DQa2SBbv2RbNjQccE5Ppv1k8oKnE/TDkEFQaO43OmTgJjlIP3ruBqcTN21JbcreZN9nyLcVO9E68E1WHacxTGzpWxJGVp4zNyXgeL65e3uCaFdiQJtLxfQxYkJxpfynYjJpKmHNuJkUlt0i+BNORYBhjs/b4lxqamv1tD7yULqWJ5jhlJfDz/HLT17EpiNIyZBg=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_FAEC72BCD47540049F11DCCE24EB1D55ericssoncom_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 1bd5d5fb-5b82-40ec-64c8-08d7522aaaa7
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Oct 2019 11:19:09.9546 (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: +oYwgJCohi6//MdH5YL6dpbggkiSH14Hroqp8s/HsVXQdQcp1/ziLPQxJ5x7VenK+Qekc2aBa6q/BlGtBusWZihWjP3yX+1Vbu+HbjR7thQ=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB4220
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/u-0yMnMfilYSGu6FmW-ckYhkRFs>
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:19:16 -0000

Hi,

Regarding Q2, I note that the document actually does define a new response code,  Hop Limit Reached. So, it withdraw that part of my comment. Sorry for the confusion.

But, then my question is why the text says that a server/proxy must send 4.00 Bad Request? Should that be replaced with the new Hop Limit Reached response code?

Regards,

Christer



From: core <core-bounces@ietf.org> on behalf of Christer Holmberg <christer.holmberg=40ericsson.com@dmarc.ietf.org>
Date: Wednesday, 16 October 2019 at 13.13
To: "core@ietf.org" <core@ietf.org>
Subject: [core] A couple of late comments on Hop-Limit

Hi,

I haven’t followed the hop-limit discussions, so I apologize if the following has already been discussed. I also know that my comments come very late in the process, so sorry for that.

Adam may have an opinion regarding Q2.


Q1:

The draft talks about “CoAP messages”. But, if I understand correctly, it is only intended to be used for CoAP request messages, right?


  *   Since you use a CoAP option, the mechanism can’t be used in an empty message.
  *   I assume you don’t want to use the mechanism when sending a response, because then there is a risk that the client will not receive it.

Unless I’ve missed it, I think it should be more explicit what the applicability of the mechanism is.


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.


  *   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.
  *   Based on my experience in SIP, it is VERY useful to have a dedicated response code for this (SIP defines ‘483 Too Many Hops’). 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.

Regards,

Christer

v2.23.0 | Report a Bug | By Email