IETF Logo Mail Archive

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

<mohamed.boucadair@orange.com> Wed, 16 October 2019 11:50 UTC

Return-Path: <mohamed.boucadair@orange.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 58A1D120914 for <core@ietfa.amsl.com>; Wed, 16 Oct 2019 04:50:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 zFd68_fDXzJM for <core@ietfa.amsl.com>; Wed, 16 Oct 2019 04:50:39 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB847120909 for <core@ietf.org>; Wed, 16 Oct 2019 04:50:39 -0700 (PDT)
Received: from opfedar03.francetelecom.fr (unknown [xx.xx.xx.5]) by opfedar23.francetelecom.fr (ESMTP service) with ESMTP id 46tVwt0b3TzBs1g; Wed, 16 Oct 2019 13:50:38 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.29]) by opfedar03.francetelecom.fr (ESMTP service) with ESMTP id 46tVws6p15zCqkT; Wed, 16 Oct 2019 13:50:37 +0200 (CEST)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM21.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0468.000; Wed, 16 Oct 2019 13:50:37 +0200
From: mohamed.boucadair@orange.com
To: Christer Holmberg <christer.holmberg@ericsson.com>, 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: AQHVhApYYBijvGsxFUafcFUkAAupTKdc/IYAgAAC34CAACK6MP//4ySAgAAhyCA=
Date: Wed, 16 Oct 2019 11:50:37 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93303133F5E5@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <9D131FD6-2CE8-4C23-8BF1-0641C3E65A46@ericsson.com> <D43A1E52-FF72-4A23-8D3F-BD6E62FDCEB6@tzi.org> <FF5FA0C8-B277-471F-8392-FCB87971DB7B@ericsson.com> <787AE7BB302AE849A7480A190F8B93303133F57F@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <D756AFB8-AEBF-4E20-852F-ECC5669EB12F@ericsson.com>
In-Reply-To: <D756AFB8-AEBF-4E20-852F-ECC5669EB12F@ericsson.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/IuLXDqSoWD_J7bTzkXNg4u5asXU>
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:50:42 -0000

Re-,

Great. 

FWIW, I take the point to double check the usage of "messages" to make it explicit it is about "requests". 

Thank you for the comments.

Cheers,
Med

> -----Message d'origine-----
> De : Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> Envoyé : mercredi 16 octobre 2019 13:47
> À : BOUCADAIR Mohamed TGI/OLN; Carsten Bormann
> Cc : core@ietf.org
> Objet : Re: [core] A couple of late comments on Hop-Limit
> 
> Hi,
> 
> ...
> 
>     >>  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.
>     >
>     > [Med] Even in that case, this is still a client error (not the
> original client, but the client component of the proxy that violated the
> following):
>     >
>     >   MUST NOT be forwarded if the Hop-Limit option is set to '0' after
> decrement.
>     >
>     > The node that receives such message does not know (necessarily) that
> the request is coming from the original client or whether it is relayed by
> a proxy.
> 
>     Correct. My mistake.
> 
>     Regards,
> 
>     Christer
>

v2.23.0 | Report a Bug | By Email