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

"Susan Hares" <shares@ndzh.com> Thu, 14 February 2019 00:00 UTC

Return-Path: <shares@ndzh.com>
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 0BF55130E9C for <idr@ietfa.amsl.com>; Wed, 13 Feb 2019 16:00:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Level:
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, URIBL_BLOCKED=0.001] autolearn=no 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 isYvVc8HRN0M for <idr@ietfa.amsl.com>; Wed, 13 Feb 2019 16:00:40 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-100-static.hfc.comcastbusiness.net [50.245.122.100]) (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 A926A128B01 for <idr@ietf.org>; Wed, 13 Feb 2019 16:00:39 -0800 (PST)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=166.176.248.72;
From: Susan Hares <shares@ndzh.com>
To: 'Robert Varga' <nite@hq.sk>, idr@ietf.org
References: <007b01d4b7c6$5b002210$11006630$@ndzh.com> <f4b36fe8-9245-14d6-61a9-cabd7eacf57d@hq.sk>
In-Reply-To: <f4b36fe8-9245-14d6-61a9-cabd7eacf57d@hq.sk>
Date: Wed, 13 Feb 2019 19:00:28 -0500
Message-ID: <001501d4c3f8$4bcc8f70$e365ae50$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJ3UJ5j1bTPsyO86K1JuAQ7q/LpfQKXKlI9pISVkTA=
Content-Language: en-us
X-Antivirus: AVG (VPS 190213-4, 02/13/2019), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/iWzkvxJBo_jJQnmhNSwMvuSRKNY>
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: Thu, 14 Feb 2019 00:00:42 -0000

Robert: 

The management section is option and standardization does not depend on that
portion of the implementation report.  It is extremely valuable information
that Opendaylight has yes or (n/a). 

Susan Hares 

-----Original Message-----
From: Robert Varga [mailto:nite@hq.sk] 
Sent: Wednesday, February 13, 2019 6:42 PM
To: Susan Hares; idr@ietf.org
Subject: Re: [Idr] WG Last Call on Extened Message Support

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-implem
> entations

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