Re: [Idr] Next hop encoding
Jeffrey Haas <jhaas@pfrc.org> Wed, 03 July 2019 19:36 UTC
Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12FCA120447 for <idr@ietfa.amsl.com>; Wed, 3 Jul 2019 12:36:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 5ctmqh3BIcJD for <idr@ietfa.amsl.com>; Wed, 3 Jul 2019 12:36:45 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 185D41203F6 for <idr@ietf.org>; Wed, 3 Jul 2019 12:36:45 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 2A62E1E2F4; Wed, 3 Jul 2019 15:38:10 -0400 (EDT)
Date: Wed, 03 Jul 2019 15:38:09 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Robert Raszuk <robert@raszuk.net>
Cc: Susan Hares <shares@ndzh.com>, John Scudder <jgs@juniper.net>, "idr@ietf. org" <idr@ietf.org>
Message-ID: <20190703193809.GA21323@pfrc.org>
References: <CAOj+MMEPgV-9RLkN39f0sVCyWUk2G-KaNEJVRG_s0kAsMAOG0w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAOj+MMEPgV-9RLkN39f0sVCyWUk2G-KaNEJVRG_s0kAsMAOG0w@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/mdBJshMxCQPRAVVURprvW2rdWME>
Subject: Re: [Idr] Next hop encoding
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jul 2019 19:36:46 -0000
On Thu, Jun 27, 2019 at 10:18:16PM +0200, Robert Raszuk wrote: > Dear IDR chairs, > > If I may I would like to suggest some form of pool (doodle, email to the > list, IDR wiki etc ...) which could help all of us to get first hand > information on how various shipping BGP implementations are handling next > hop encoding parsing. FWIW, I'm supportive of an implementation poll being done. RFC 2545 nexthops have proven to be troublesome for most of my time doing BGP. I certainly wouldn't mind seeing them go away. -- Jeff
- [Idr] Next hop encoding Robert Raszuk
- Re: [Idr] Next hop encoding Jeffrey Haas