Paul Durrant writes ("[PATCH v3 4/4] docs: Document xenstore paths for domain
network address information"):
> +#### ~/attr/vif/$DEVID/name = STRING [w]
You need to explicitly state what this information is to be used for.
This "name" is presumably useful for humans in the management UI ?
You need to say something about the toolstack not trusting it too
much.
> +A domain may write its internal 'friendly' name for a network device
> +using this path.
> +
> +#### ~/attr/vif/$DEVID/mac/$INDEX = MAC_ADDRESS [w]
> +
> +A domain may write the set of MAC addresses (unicast and multicast)
> +in use by the network frontend using paths of this form.
The primary (virtual hardware) VIF MAC address is already recorded by
the toolstack in the PV protocol backend directory.
What is this for ?
At the very least you need to state that this information MUST NOT be
used for packet routing, packet filtering, or for security purposes.
> +#### ~/attr/vif/$DEVID/ipv4/$INDEX = IPV4_ADDRESS [w]
> +#### ~/attr/vif/$DEVID/ipv6/$INDEX = IPV6_ADDRESS [w]
I can see that this would be easier to use than messing with querying
the DHCP server or whatever.
But you absolutely must state that this information MUST NOT be used
for packet routing etc. Examples of what it _is_ good for would be
good.
Thanks,
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
