Peter Memishian wrote:
> I have suggested an alternative of using an "improved" version of the
> existing logical interface naming scheme which does not have the V4/V6
> namespace split and which would also accommodate address bundles in the
> same manner that address labels accommodate them (at least, to the degree
> which I understand how address labels accommodate them). Specifically,
> each address object for a particular IP interface (whether it's a single
> address, a point-to-point address, or an IPv6 address bundle) would have
> an associated numeric identifier. During create-addr, the administrator
> can either choose this identifier or have the system assign one for them.
> The address object is then identified by the interface/id tuple until it
> is eventually removed -- i.e., net0/0 or net0/86 or whatever.
Even if we use /n instead of :n to try to keep this separate from the
logical interface numbers I think we'd spend a year of our lives
explaining that the number in the label has nothing to do with the
number that ifconfig -a reports.
Stated differently, doing /n would be find if we excized all of ifconfig
and logical interface numbers from the kernel at the same time. Anything
else will cause confusion.
Thus I think it is better to either have free text labels. Or we could
do alphabetic instead numeric e.g net0/a and net0/b. With alphabetic we
could still auto-assign them.
As long as we stay away from numeric we reduce the source of confusion.
Erik
