Re: [Idr] I-D Action: draft-ietf-idr-next-hop-capability-06.txt Tue, 06 October 2020 15:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4598A3A0A39 for <>; Tue, 6 Oct 2020 08:02:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ArgpI1s_8KhW for <>; Tue, 6 Oct 2020 08:02:20 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 776783A0A35 for <>; Tue, 6 Oct 2020 08:02:20 -0700 (PDT)
Received: from (unknown [xx.xx.xx.66]) by (ESMTP service) with ESMTP id 4C5LKl0WxNz4xXP for <>; Tue, 6 Oct 2020 17:02:19 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=ORANGE001; t=1601996539; bh=0S86drLsI5mj4Orp47AXrviuXuwizliaMGjRqzhfvCw=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=ns0IeXKBJ+9PE8hdhaUTXedeWro/Bptln4kx2wa2RNOHRG+i3PnwOiO7xpmui9etL DwbbGO049xljKesm1OisJkaNtY+HKrs7ZG5dZLx34jYKimzD2q1jdgyV8uqZFZAn2R OHQOWxwnqghod40WuQB8T1tAKgSUBGJEZduh0qJRLgxQYVCsO2k6I8TJf0o00/mvKe 8pXvYY5xC9ITNMQ7BBJJn81z0U7iEsp80hdF3H9H925IgymtuDrjY4DQvBQSmfppsZ YvCOmDGrN7bkTALAx5btaprW1qJ5T32iGgdZRDcIz/lu1ulplbfnK48kj/n1VMSr+N 0QQ0mBRAd29+Q==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.89]) by (ESMTP service) with ESMTP id 4C5LKk6s6lz8sYx for <>; Tue, 6 Oct 2020 17:02:18 +0200 (CEST)
To: "" <>
Thread-Topic: [Idr] I-D Action: draft-ietf-idr-next-hop-capability-06.txt
Thread-Index: AQHWm/DreACvQw8npEuR//6XwXpOh6mKqyHQ
Date: Tue, 06 Oct 2020 15:02:17 +0000
Message-ID: <3599_1601996539_5F7C86FA_3599_488_6_53C29892C857584299CBF5D05346208A48F97C4F@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
References: <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-next-hop-capability-06.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 06 Oct 2020 15:02:22 -0000

Hi all,

Just a refresh with no change.

> A diff from the previous version is available at:

-- Bruno

> -----Original Message-----
> From: Idr [] On Behalf Of internet-
> Sent: Tuesday, October 6, 2020 4:57 PM
> To:
> Cc:
> Subject: [Idr] I-D Action: draft-ietf-idr-next-hop-capability-06.txt
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Inter-Domain Routing WG of the IETF.
>         Title           : BGP Next-Hop dependent capabilities
>         Authors         : Bruno Decraene
>                           Kireeti Kompella
>                           Wim Henderickx
> 	Filename        : draft-ietf-idr-next-hop-capability-06.txt
> 	Pages           : 13
> 	Date            : 2020-10-06
> Abstract:
>    RFC 5492 advertises the capabilities of the BGP peer.  When the BGP
>    peer is not the same as the BGP Next-Hop, it is useful to also be
>    able to advertise the capability of the BGP Next-Hop, in particular
>    to advertise forwarding plane features.  This document defines a
>    mechanism to advertise such BGP Next Hop dependent Capabilities.
>    This document defines a new BGP non-transitive attribute to carry
>    Next-Hop Capabilities.  This attribute is guaranteed to be deleted or
>    updated when the BGP Next Hop is changed, in order to reflect the
>    capabilities of the new BGP Next-Hop.
>    This document also defines a Next-Hop capability to advertise the
>    ability to process the MPLS Entropy Label as an egress LSR for all
>    NLRI advertised in the BGP UPDATE.  It updates RFC 6790 with regard
>    to this BGP signaling.
> The IETF datatracker status page for this draft is:
> There are also htmlized versions available at:
> A diff from the previous version is available at:
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at
> Internet-Drafts are also available by anonymous FTP at:
> _______________________________________________
> Idr 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.