From: Claudio Jeker <cjeker@diehard.n-r-g.com>
Subject: Re: bgpd.conf: document `announce EVPN`
To: Denis Fondras <denis@openbsd.org>
Cc: tech@openbsd.org
Date: Sun, 23 Feb 2025 07:28:48 +0100

On Sat, Feb 22, 2025 at 01:15:05PM +0100, Denis Fondras wrote:
> Just mention the existence of `announce EVPN` option.
> 
> Denis
> 
> Index: bgpd.conf.5
> ===================================================================
> RCS file: /cvs/src/usr.sbin/bgpd/bgpd.conf.5,v
> diff -u -p -r1.249 bgpd.conf.5
> --- bgpd.conf.5	27 Jan 2025 15:22:11 -0000	1.249
> +++ bgpd.conf.5	22 Feb 2025 12:12:50 -0000
> @@ -979,7 +979,7 @@ The neighbor properties are as follows:
>  .Bl -tag -width Ds -compact
>  .It Xo
>  .Ic announce
> -.Pq Ic IPv4 Ns | Ns Ic IPv6
> +.Pq Ic IPv4 Ns | Ns Ic IPv6 | Ns Ic EVPN
>  .Pq Ic none Ns | Ns Ic unicast Ns | Ns Ic vpn Ns | Ns Ic flowspec
>  .Op Ic enforce
>  .Xc

Would it make sense to add a second line here:

.It Xo
.Ic announce
.Ic EVPN
.Op Ic enforce
.Xc

To make it clear that EVPN is alone?

> @@ -987,7 +987,11 @@ For the given address family, control wh
>  .Em subsequent address families
>  are announced during the capabilities negotiation.
>  Only routes for that address family and subsequent address families will be
> -announced and processed.
> +announced and processed. Exception is
> +.Ic EVPN
> +does not accept
> +.Em subsequent address familiy
> +parameter.
>  .Pp
>  At the moment, only
>  .Ic none ,
> 

I'm fine with this otherwise.

-- 
:wq Claudio