On Fri, 2009-09-25 at 17:48 +0200, Daniel Veillard wrote:
On Thu, Sep 24, 2009 at 04:32:21PM -0700, David Lutterkort wrote:
Hum, this forces ipv4 protocol info before ipv6 ones, but I guess it's
fine, makes things easier to lookup manually though I guess the parsing
code doesn't care :-)
It doesn't really matter from a processing POV, so I could relax that
and allow ipv4/ipv6 in any order. How good's the implementation of the
interleave validation ;) ? Actually, interleave isn't allowed here since
you'd be interleaving two <protocol/> elements, and interleave doesn't
seem to be able to discriminate based on the family attribute. Ugh.
----------
> + <element name="dhcp">
> + <optional>
> + <attribute name="peerdns">
> + <ref name="yes-or-no"/>
> + </attribute>
> + </optional>
> + </element>
----------
identical to ipv4, so I would factor this out as a define.
Done.
David