Re: [mpls] Working Group adoption call for draft-decraene-idr-next-hop-capability-03

<> Fri, 19 May 2017 06:54 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AAB93127775; Thu, 18 May 2017 23:54:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 4wY6xjAGO3gx; Thu, 18 May 2017 23:54:29 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2382B12EB9B; Thu, 18 May 2017 23:49:58 -0700 (PDT)
Received: from (unknown [xx.xx.xx.6]) by (ESMTP service) with ESMTP id 9159D1C03D8; Fri, 19 May 2017 08:49:56 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.10]) by (ESMTP service) with ESMTP id 6C9854004C; Fri, 19 May 2017 08:49:56 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM5C.corporate.adroot.infra.ftgroup ([fe80::4bd:9b2b:3651:6fba%19]) with mapi id 14.03.0339.000; Fri, 19 May 2017 08:49:56 +0200
From: <>
To: John G.Scudder <>, idr wg <>
CC: "" <>, "" <>
Thread-Topic: [mpls] Working Group adoption call for draft-decraene-idr-next-hop-capability-03
Thread-Index: AQHSz/XFR+Oe8TWL5EePssWVkm2tf6H7OE7A
Date: Fri, 19 May 2017 06:49:54 +0000
Message-ID: <30171_1495176596_591E9594_30171_3117_1_9E32478DFA9976438E7A22F69B08FF921DDBB1C0@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [mpls] Working Group adoption call for draft-decraene-idr-next-hop-capability-03
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multi-Protocol Label Switching WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 19 May 2017 06:54:31 -0000


-----Original Message-----
From: mpls [] On Behalf Of John G.Scudder
Sent: Thursday, May 18, 2017 18:35
To: idr wg
Subject: [mpls] Working Group adoption call for draft-decraene-idr-next-hop-capability-03

[resending, correcting draft@ietf address]

Hi All,

IDR working group adoption has been requested for draft-decraene-idr-next-hop-capability-03. Please send your comments to the IDR mailing list before June 2, 2017. Please remember that we need affirmative support in order to adopt the draft, so don't be shy.

draft datatracker page:
slides from IETF-98:

Since in part this draft specifies a replacement for the Entropy Label Capability Attribute (ELCA) that was defined by the MPLS WG in RFC 6790 and deprecated by RFC 7447, I have cc'd the MPLS WG mailing list. Since the proposed new attribute is a generic container with the ELCA replacement just the first application, the current draft is targeted to IDR and not MPLS (this was discussed during IETF-93). 


mpls mailing list


Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.