Hi,
Please look at these patches:
bytestring-hex-prefix.patch - syntax with "hex:" prefix
I allowed mixed colons with no-divider there, so hex:12:345678:90 is
allowed. As there is a distinguishing prefix here, this should not be
a problem.
Empty bytestrings are allowed too: "hex:"
bytestring-hex
On Tue, Jun 13, 2023 at 05:34:18PM +0200, Alexander Zubkov wrote:
> On Tue, Jun 13, 2023, 16:07 Ondrej Zajicek wrote:
>
> > We agreed on keeping existing format for suffiently long hex bytestrings,
> > using hex: prefix for bytestrings of any length, and adding hex("...") /
> > base64("...") as or
On Tue, Jun 13, 2023, 16:07 Ondrej Zajicek wrote:
> On Mon, Jun 12, 2023 at 05:55:34PM +0200, Alexander Zubkov wrote:
> > BTW, if we put a string literal inside the brackets, we can mimic a
> > function call without dirty lexer/parser hacks:
> > hex("...")
> >
> > Or maybe you have already agreed
On Sun, Jun 04, 2023 at 06:06:22PM +, Sunnat Samadov wrote:
> Dear Birds,
>
> I am reaching out to seek assistance and guidance from the community
> regarding an issue we are facing with BIRD, specifically version 2.0.11,
> which we have been using in our network configuration.
>
> Our setu
On Mon, Jun 12, 2023 at 05:55:34PM +0200, Alexander Zubkov wrote:
> BTW, if we put a string literal inside the brackets, we can mimic a
> function call without dirty lexer/parser hacks:
> hex("...")
>
> Or maybe you have already agreed on something?
Hi
We agreed on keeping existing format for su
On Tue, Jun 13, 2023 at 10:47:08AM +0530, Ramanathan Selvamani wrote:
> Hi Team,
>
> I configured l3vpn in BIRD and I was able to see the routes are learnt and
> advertised based on RT.
>
> All the routes in this VRF are advertised with RT (1:11) to neighbors.
Hi
I am glad you tried this MPLS L
