
Hi all, The default range went through several changes during the lifetime of the project - from being small and constant until 3.2, to small and random in 3.3 until 3.5, back to fixed and small in 3.6, slightly enlarged (to 1024 addresses) in current master. In all cases, the address range was taken from the IANA-assigned range 001A4A of Qumranet (now Red Hat) [1]. I suggest to: 1. Default to a random range again - So that two or (a few) more setups using the same network segment are less likely to use the same range 2. One in the locally-administered address range [2] - So that we have a larger address range 3. Make it a bit larger, say 65000 addresses - So that admins do not have to handle this manually, even for large setups, unless they have specific needs If there is objection to (2.), we can still have the others - among the 24 bits in the 001A4A prefix range, choose among the first 8 a random value during engine-setup, and have the pool of size 16 bits. Comments/ideas/etc. are welcome. Best regards, [1] https://regauth.standards.ieee.org/standards-ra-web/pub/view.html [2] https://en.wikipedia.org/wiki/MAC_address#Universal_vs._local -- Didi

Can you please open an RFE for us to review? YANIV LAVI SENIOR TECHNICAL PRODUCT MANAGER Red Hat Israel Ltd. <https://www.redhat.com/> 34 Jerusalem Road, Building A, 1st floor Ra'anana, Israel 4350109 ylavi@redhat.com T: +972-9-7692306/8272306 F: +972-9-7692223 IM: ylavi <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> @redhatnews <https://twitter.com/redhatnews> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> On Sun, Nov 19, 2017 at 12:37 PM, Yedidyah Bar David <didi@redhat.com> wrote:
Hi all,
The default range went through several changes during the lifetime of the project - from being small and constant until 3.2, to small and random in 3.3 until 3.5, back to fixed and small in 3.6, slightly enlarged (to 1024 addresses) in current master.
In all cases, the address range was taken from the IANA-assigned range 001A4A of Qumranet (now Red Hat) [1].
I suggest to:
1. Default to a random range again - So that two or (a few) more setups using the same network segment are less likely to use the same range
2. One in the locally-administered address range [2] - So that we have a larger address range
3. Make it a bit larger, say 65000 addresses - So that admins do not have to handle this manually, even for large setups, unless they have specific needs
If there is objection to (2.), we can still have the others - among the 24 bits in the 001A4A prefix range, choose among the first 8 a random value during engine-setup, and have the pool of size 16 bits.
Comments/ideas/etc. are welcome.
Best regards,
[1] https://regauth.standards.ieee.org/standards-ra-web/pub/view.html [2] https://en.wikipedia.org/wiki/MAC_address#Universal_vs._local -- Didi _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel

https://bugzilla.redhat.com/show_bug.cgi?id=1516445 On Wed, Nov 22, 2017 at 5:48 PM, Yaniv Lavi <ylavi@redhat.com> wrote:
Can you please open an RFE for us to review?
YANIV LAVI
SENIOR TECHNICAL PRODUCT MANAGER
Red Hat Israel Ltd. <https://www.redhat.com/>
34 Jerusalem Road, Building A, 1st floor
Ra'anana, Israel 4350109
ylavi@redhat.com T: +972-9-7692306/8272306 F: +972-9-7692223 IM: ylavi <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> @redhatnews <https://twitter.com/redhatnews> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc>
On Sun, Nov 19, 2017 at 12:37 PM, Yedidyah Bar David <didi@redhat.com> wrote:
Hi all,
The default range went through several changes during the lifetime of the project - from being small and constant until 3.2, to small and random in 3.3 until 3.5, back to fixed and small in 3.6, slightly enlarged (to 1024 addresses) in current master.
In all cases, the address range was taken from the IANA-assigned range 001A4A of Qumranet (now Red Hat) [1].
I suggest to:
1. Default to a random range again - So that two or (a few) more setups using the same network segment are less likely to use the same range
2. One in the locally-administered address range [2] - So that we have a larger address range
3. Make it a bit larger, say 65000 addresses - So that admins do not have to handle this manually, even for large setups, unless they have specific needs
If there is objection to (2.), we can still have the others - among the 24 bits in the 001A4A prefix range, choose among the first 8 a random value during engine-setup, and have the pool of size 16 bits.
Comments/ideas/etc. are welcome.
Best regards,
[1] https://regauth.standards.ieee.org/standards-ra-web/pub/view.html [2] https://en.wikipedia.org/wiki/MAC_address#Universal_vs._local -- Didi _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Didi
participants (2)
-
Yaniv Lavi
-
Yedidyah Bar David