959: suggested subprefixes should be limited to nibble boundary

ID	Project	Category	View Status	Date Submitted	Last Update

959	RackTables	IPv4/IPv6/SLB	public	2013-07-24 18:46	2014-02-10 15:35

Reporter	jsn007	Assigned To	andriyanov
Priority	normal	Severity	feature	Reproducibility	always
Status	closed	Resolution	fixed
Product Version	0.20.5
Target Version	0.20.7	Fixed in Version	0.20.7

Summary	959: suggested subprefixes should be limited to nibble boundary
Description	After creating a new IPv6 prefix and then the first subprefix for that overall new prefix, racktables presents a list of other possible subprefixes available. The list is a regression of prefix lengths available. However IETF suggests that IPv6 prefixes be based upon nibble boundary to make life easier on admins. Thus racktables should only suggest subprefixes that are on nibble boundary. For example with current code: Starting prefix: 2001:db8::/32 First manually created prefix: 2001:db8::/36 The list of suggested prefixes available from racktables is: 2001:db8:1000::/36 [Here be dragons.] [create network here] 0 in 256M nets 2001:db8:2000::/35 [Here be dragons.] [create network here] 0 in 512M nets 2001:db8:4000::/34 [Here be dragons.] [create network here] 0 in 1G nets 2001:db8:8000::/33 [Here be dragons.] [create network here] 0 in 2G nets Ideally racktables should only offer /36 prefixes. Like wise if a new prefix was created as a /40 all the other prefixes suggested should be /40.
Tags	No tags attached.

Date Modified	Username	Field	Change
2013-07-24 18:46	jsn007	New Issue
2013-07-24 18:46	jsn007	Status	new => assigned
2013-07-24 18:46	jsn007	Assigned To	=> andriyanov
2013-07-24 19:15	andriyanov	Target Version	=> 0.20.6
2013-11-25 15:28	infrastation	Target Version	0.20.6 => 0.20.7
2014-02-10 15:35	andriyanov	Status	assigned => closed
2014-02-10 15:35	andriyanov	Resolution	open => fixed
2014-02-10 15:35	andriyanov	Fixed in Version	=> 0.20.7