peval issue
Jay Borkenhagen
jayb at braeburn.org
Wed Feb 29 11:44:09 UTC 2012
I've recently been using with peval for IPv6. I registered a route6
object for 2620:0:f00::/41, with origin in AS6431.
The issue I'm reporting is regarding the output format chosen by
peval:
$ peval 'afi ipv6.unicast 'as6431
({2620::F00:0:0:0:0:0/41})
$
$ peval -version
peval irrtoolset-5.0.0
$
It would be better to display this using the 2620:0:f00::/41 format.
Here is the relevant section of RFC 5952:
---------------------------------------------
4.2.3. Choice in Placement of "::"
When there is an alternative choice in the placement of a "::", the
longest run of consecutive 16-bit 0 fields MUST be shortened (i.e.,
the sequence with three consecutive zero fields is shortened in
2001:0:0:1:0:0:0:1). When the length of the consecutive 16-bit 0
fields are equal (i.e., 2001:db8:0:0:1:0:0:1), the first sequence
of zero bits MUST be shortened. For example, 2001:db8::1:0:0:1 is
correct representation.
---------------------------------------------
BTW, that same RFC also includes this text:
---------------------------------------------
4.3. Lowercase
The characters "a", "b", "c", "d", "e", and "f" in an IPv6 address
MUST be represented in lowercase.
---------------------------------------------
That one is easy enough to work around in a shell script, but it would
be simpler if peval used the [abcdef] notation.
Thanks!
Jay B.
More information about the irrtoolset
mailing list