[Idr] Next hop encoding
Robert Raszuk <robert@raszuk.net> Thu, 27 June 2019 20:18 UTC
Return-Path: <robert@raszuk.net>
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 350721201C9 for <idr@ietfa.amsl.com>; Thu, 27 Jun 2019 13:18:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
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 wsocybnctES9 for <idr@ietfa.amsl.com>; Thu, 27 Jun 2019 13:18:27 -0700 (PDT)
Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) (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 24422120110 for <idr@ietf.org>; Thu, 27 Jun 2019 13:18:27 -0700 (PDT)
Received: by mail-qk1-x72f.google.com with SMTP id s22so2892631qkj.12 for <idr@ietf.org>; Thu, 27 Jun 2019 13:18:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:from:date:message-id:subject:to:cc; bh=YyoOuQjvp2vi/eZdcBHOK36ViHL20GZESCTMLPqZFzk=; b=DFU7QErURbjCF1hcb58rIv/2vjnutKDT1ym2+K0NDf6Da9JnIO7RoqyfyKXUUK+mtT 6eM+Ru2jTWZmfqwWLTQB0DGv1EporjVBGhI9hzyJg/4wUZeEVUHYSWK49ANiScf808FT 27q3F1FVEtFbyJIkf6zQa38wn4li3A8hXsKa2EU1QVHx9DWwdiynpd/VmLc8qJg4JApl iOGd+sFB3NxI9qabx31YyiJulsUYzxwSFlkWylUyqpBYh2n65hMft+AOzy7REZfgoJOW O91swqSbyjDnnKrfzX0+QPJyOZsKl5pdLh25fzvNXkQuOtK+Np0risa8ZO/ZGqlUeDkN 0F3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=YyoOuQjvp2vi/eZdcBHOK36ViHL20GZESCTMLPqZFzk=; b=AgxMUyCVA8Iw/QxO4RpO5fkMgeeAgsipvua91oeEg2epBwqmidYTgcCh8GOwDtyz6Z UKhc8TSHmVuMdo7nTVR7LPoRclsx72Xb0LllJ377lpBGvKPf0TCY1XxNE4wr+RTDifKp ma6oKGqdXBzEywVPNQsTe3ni85vaZTklpCawOk5QJqg2rfnGOI/Hg/WcMOLxQ4MpFdQ1 ebKixV6oLfLmIhBpIpnAPzuWozaXuOjOfTTB6KIOiqhgkzdcvS9SirRQ0BKJapraVJId /Gc5PwSiN1X/hA8Q+9bJoIu1L5YgvO3P5bMeiVNnHzepTSgl9GzcHMUtoM/4nmZD8Mm6 WZvg==
X-Gm-Message-State: APjAAAXPf5MroztdR+5E8dtsKWBux/+7lnLsaic8t9NzJUSnBNZ9fnGs +7fn7ZRZ25P5gKGD3WWSQ2vkRW3nMN9QGARB/A76HA==
X-Google-Smtp-Source: APXvYqy+2KuBcc5aKLNL9be9ZPeUb62mjOMcQfe1BvVoplbALLdiyOq16Q8ft8Fdes0pjXltknPiIo973eDVHYHotEs=
X-Received: by 2002:a05:620a:1286:: with SMTP id w6mr5092842qki.219.1561666706102; Thu, 27 Jun 2019 13:18:26 -0700 (PDT)
MIME-Version: 1.0
From: Robert Raszuk <robert@raszuk.net>
Date: Thu, 27 Jun 2019 22:18:16 +0200
Message-ID: <CAOj+MMEPgV-9RLkN39f0sVCyWUk2G-KaNEJVRG_s0kAsMAOG0w@mail.gmail.com>
To: Susan Hares <shares@ndzh.com>, John Scudder <jgs@juniper.net>
Cc: "idr@ietf. org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000466c1d058c53dd7c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/wwrNQegoY3L9jyG276mWmHC1800>
Subject: [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: Thu, 27 Jun 2019 20:18:29 -0000
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. I think the min set of questions could be as follows: Name/Implementation 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 so pls 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. I think getting this information at least from all major BGP implementations would be very useful for making some choices in regards to current specifications or proposed erratum(s). Kind regards, R.
- [Idr] Next hop encoding Robert Raszuk
- Re: [Idr] Next hop encoding Jeffrey Haas