[core] TR: New Version Notification for draft-boucadair-core-hop-limit-00.txt
<mohamed.boucadair@orange.com> Thu, 16 August 2018 11:35 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 A63F5130E6C; Thu, 16 Aug 2018 04:35:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 DlJes0Xhbvtz; Thu, 16 Aug 2018 04:35:00 -0700 (PDT)
Received: from orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CACDE12D7F8; Thu, 16 Aug 2018 04:34:59 -0700 (PDT)
Received: from opfednr03.francetelecom.fr (unknown [xx.xx.xx.67]) by opfednr25.francetelecom.fr (ESMTP service) with ESMTP id 41rklQ3DGQzCrHF; Thu, 16 Aug 2018 13:34:58 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.31]) by opfednr03.francetelecom.fr (ESMTP service) with ESMTP id 41rklQ2DHkzDq7W; Thu, 16 Aug 2018 13:34:58 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM22.corporate.adroot.infra.ftgroup ([fe80::8c90:f4e9:be28:2a1%19]) with mapi id 14.03.0408.000; Thu, 16 Aug 2018 13:34:58 +0200
From: mohamed.boucadair@orange.com
To: "dots@ietf.org" <dots@ietf.org>, "core@ietf.org" <core@ietf.org>, "core-chairs@ietf.org" <core-chairs@ietf.org>
Thread-Topic: New Version Notification for draft-boucadair-core-hop-limit-00.txt
Thread-Index: AQHUNVQAFI7aKbVrj02KVBJq3RQg7KTCPW3w
Date: Thu, 16 Aug 2018 11:34:58 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302DFAAC00@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <153441879828.7958.7190170310076258819.idtracker@ietfa.amsl.com>
In-Reply-To: <153441879828.7958.7190170310076258819.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/klTQ51S76HqDB2wByvXDkNc7P30>
Subject: [core] TR: New Version Notification for draft-boucadair-core-hop-limit-00.txt
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.27
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: Thu, 16 Aug 2018 11:35:02 -0000
Hi all, We submitted a separate draft to specify the hop-limit option (used to be in the DOTS signal channel I-D) as per the outcome of the core interim meeting discussion in CORE. https://tools.ietf.org/html/draft-ietf-dots-signal-channel-22 will be updated to refer to this one. FWIW, draft-ietf-dots-signal-channel has already passed the WGLC. We would appreciate if the CORE WG can consider adoption of hop-limit I-D and process it in a timely manner. Thank you. Cheers, Med > -----Message d'origine----- > De : internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] > Envoyé : jeudi 16 août 2018 13:27 > À : Tirumaleswar Reddy; BOUCADAIR Mohamed IMT/OLN; Jon Shallow > Objet : New Version Notification for draft-boucadair-core-hop-limit-00.txt > > > A new version of I-D, draft-boucadair-core-hop-limit-00.txt > has been successfully submitted by Mohamed Boucadair and posted to the > IETF repository. > > Name: draft-boucadair-core-hop-limit > Revision: 00 > Title: Constrained Application Protocol (CoAP) Hop Limit Option > Document date: 2018-08-16 > Group: Individual Submission > Pages: 5 > URL: https://www.ietf.org/internet-drafts/draft-boucadair-core- > hop-limit-00.txt > Status: https://datatracker.ietf.org/doc/draft-boucadair-core-hop- > limit/ > Htmlized: https://tools.ietf.org/html/draft-boucadair-core-hop-limit-00 > Htmlized: https://datatracker.ietf.org/doc/html/draft-boucadair-core- > hop-limit > > > Abstract: > The presence of Constrained Application Protocol (CoAP) proxies may > lead to infinite forwarding loops, which is undesirable. To prevent > and detect such loops, this document specifies the Hop-Limit CoAP > option. > > > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > The IETF Secretariat
- [core] TR: New Version Notification for draft-bou… mohamed.boucadair