Re: [Idr] WG Last Call on Extened Message Support

Robert Varga <nite@hq.sk> Wed, 13 February 2019 23:41 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 7C6B1130E57 for <idr@ietfa.amsl.com>; Wed, 13 Feb 2019 15:41:57 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=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 zhCgR_zFAJsK for <idr@ietfa.amsl.com>; Wed, 13 Feb 2019 15:41:55 -0800 (PST)
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 B7C19128B01 for <idr@ietf.org>; Wed, 13 Feb 2019 15:41:54 -0800 (PST)
Received: from nitebug.nitenet.local (chello085216197060.chello.sk [85.216.197.60]) by mail.hq.sk (Postfix) with ESMTPSA id D5A0D242575; Thu, 14 Feb 2019 00:41:51 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hq.sk; s=mail; t=1550101311; bh=74DRdo24XjnxooLBHDybQwh/kKJjvRlE/w2MSVIg1GE=; h=Subject:To:References:From:Date:In-Reply-To; b=regMGwfy6ZuCN56X0CqObh0LdZhrJybpv5+HAmXpxP6j2d4oFoTbcAFivshjq02uq 2G6GOEz37e2QAs6Vs5TlSEq44nVHyo+8N+1rTuiZokdSD7vrmVdV2Y20wX08ZMM2a4 gUfy5NWw3cqhUWRf7grjVMgr8+ThTNbVl41qHixI=
To: Susan Hares <shares@ndzh.com>, idr@ietf.org
References: <007b01d4b7c6$5b002210$11006630$@ndzh.com>
From: Robert Varga <nite@hq.sk>
Openpgp: preference=signencrypt
Message-ID: <f4b36fe8-9245-14d6-61a9-cabd7eacf57d@hq.sk>
Date: Thu, 14 Feb 2019 00:41:45 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <007b01d4b7c6$5b002210$11006630$@ndzh.com>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="GCQwdBk57nSzjhMdf9uocmtD16wT0QkEE"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/qJBwQVoTkCxByZBM0xb10eM8Pvc>
Subject: Re: [Idr] WG Last Call on Extened Message Support
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, 13 Feb 2019 23:41:58 -0000

Hello everyone,

On 29/01/2019 12:32, Susan Hares wrote:
>  
> 
> This begins a 2 week WG LC on Extended Message Support for BGP
> (draft-ietf-idr-bgp-extended-messages-27).  You can access the draft at:
> 
>  
> 
> https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-extended-messages/
> 
>  
> 
> The authors should indicate whether they know of any IPR.   Implementers
> are encouraged to update the  implementation data at:
> 
>  
> 
> https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-bgp-extended-implementations

I have updated the report with the behavior of OpenDaylight
implementation to the extent I could quickly ascertain. I suspect all 12
answers in the Management Information are either Yes, or N/A (in case of
CLI), but I currently do not have the cycles to make a definitive
answer, sorry :(

[snip]

> As you comment on the draft, please consider if: a) the technology is
> mature, b) the additional space in a BGP message would be helpful for
> those deploying BGP-LS or SR, and c) if the specification is ready for
> publication. 

As an implementer: we have implemented this extension many moons ago
based on a request from a real-life deployment. I believe the answer to
all three questions is yes.

Regards,
Robert