If we get the 4.3.0 to 4.3.1 in then there is no need for my previous comment. I was concerned it would not happen.
On Wed, Jun 4, 2014 at 9:20 AM, Daan Hoogland <daan.hoogl...@gmail.com> wrote: > On Wed, Jun 4, 2014 at 4:27 PM, Marcus <shadow...@gmail.com> wrote: > > Regarding 5e80e5d33d9a295b91cdba9377f52d9d963d802a, we should probably do > > that for IpAssocCommand as well. > > > I am feeling like in a spiral down. If the user input is fixed up > coming in it should probably be fixed down going out. when we save a > uri in the db we could still present the user with an id. Not when the > id can actually be an non vlan uri, however. This is going to take a > lot of work to get right. I doubt ipAssocCommand is going to be the > last one. > > -- > Daan >
