IETF Logo Mail Archive

Re: [Idr] Status of draft-ietf-idr-ext-opt-param?

Robert Varga <nite@hq.sk> Mon, 15 July 2019 20:07 UTC

Return-Path: <nite@hq.sk>
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 CC60F12016C for <idr@ietfa.amsl.com>; Mon, 15 Jul 2019 13:07:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hq.sk
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 MGVcGg8O3fX1 for <idr@ietfa.amsl.com>; Mon, 15 Jul 2019 13:07:29 -0700 (PDT)
Received: from mail.hq.sk (hq.sk [81.89.59.181]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A03401200F9 for <idr@ietf.org>; Mon, 15 Jul 2019 13:07:29 -0700 (PDT)
Received: from nitebug.nitenet.local (chello085216197060.chello.sk [85.216.197.60]) by mail.hq.sk (Postfix) with ESMTPSA id C7D08243551; Mon, 15 Jul 2019 22:07:27 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hq.sk; s=mail; t=1563221247; bh=fpNzHB0fPSHDlmfSxmFYKTyv7u3Cfx7cveVGrgGJlZo=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=FZIk37IJ5eYYaipP4MZ6SVaa/0u0UmGRdmvq3LY8aLIOLOku9JM9HOR2+iI9DsqZ5 hVbHYI0/Jx02Rla/e8TRrGGS5CHIgjcng2k1nFLVQiTAHRLaZoDv8ZDEq5zRAR1d3y mZ0xewzqSxaJj9CiaV81w8aBVPW31iQtd3IT4oC0=
To: Jeffrey Haas <jhaas@pfrc.org>
Cc: idr@ietf.org
References: <c28cbce0-2033-1224-eb73-be81fc436390@hq.sk> <20190711141919.GC4922@pfrc.org>
From: Robert Varga <nite@hq.sk>
Openpgp: preference=signencrypt
Message-ID: <a9a76ce4-924c-a834-6571-5ad396ed8bce@hq.sk>
Date: Mon, 15 Jul 2019 22:07:27 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <20190711141919.GC4922@pfrc.org>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="scoLPchuv7vbPZPvcATMmBvwhzsLoGFBe"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/4Ix-Na002M7JmWJkJu0v2sBl5aM>
Subject: Re: [Idr] Status of draft-ietf-idr-ext-opt-param?
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: Mon, 15 Jul 2019 20:07:31 -0000

On 11/07/2019 16:19, Jeffrey Haas wrote:
> Followup, since this also popped up on my TODO:
> 
> Juniper and Nokia have implementations.

FWIW, OpenDaylight will ship an implementation of
draft-ietf-idr-ext-opt-param-05 in the next major release (Sep 2019).

> I requested in 2016 an early allocation on the BGP optional parameter code
> point.  This has not been done.

Yes. If there is rough consensus, we need to get at least this done.

Regards,
Robert

v2.23.0 | Report a Bug | By Email