[Idr] Next hop encoding - IDR list poll

"Susan Hares" <shares@ndzh.com> Sun, 21 July 2019 21:02 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id ABC3F12006E; Sun, 21 Jul 2019 14:02:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.372
X-Spam-Level: *
X-Spam-Status: No, score=1.372 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_GREY=0.424] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id iDwfdK3-TniX; Sun, 21 Jul 2019 14:02:20 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-100-static.hfc.comcastbusiness.net []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CA61120045; Sun, 21 Jul 2019 14:02:20 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=;
From: Susan Hares <shares@ndzh.com>
To: idr@ietf.org, bess@ietf.org
Date: Sun, 21 Jul 2019 17:02:18 -0400
Message-ID: <002101d54007$95277f00$bf767d00$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0022_01D53FE6.0E1765A0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdVABvBwjgEHtW9wSo+Qm0F9bH6JGg==
Content-Language: en-us
X-Antivirus: AVG (VPS 190721-4, 07/21/2019), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/GNT2JHv4BCgmdoKdLxDT7SXtcWU>
Subject: [Idr] Next hop encoding - IDR list poll
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: Sun, 21 Jul 2019 21:02:22 -0000

Greetings iDR and BESS: 


Would people who are a BGP implementer or work with a 

BGP implementer send this information to the IDR chairs? 



Name of Implementation: 

Your name: 


1. Is your implementation capable of inferring next hop format from next

hop length included in MP_REACH attribute ?


2. If Yes for #1 does this apply to any AFI/SAFI or is this only for

selected AFI/SAFIs?  If it is for select AFI/SAFIs, please provide the list.


3. Do you support encoding of two IPv6 next hops (global and link local) in

the same next hop field and if so how do you use it once parsed correctly.



If it would help you to collect this to have this information in an

web format that could be clicked through in less than 5 minutes, 

please let me know. 


I can put up a snappy web form at www.surveymonkey.com. 


Cheerily, Susan Hares