-lepape-6man-prefix-metadata-00#appendix-A.1.5 has the details.
Suggesting three different userspace/kernel methods isn't going to help
get
applications written. APIs matter here. Being able to set a default
colour
for a process (and it's children!!) is probably the initial killer
interface
I think that this draft is useful land should be adopted.
I think that application writers will be much happier asking for prefix
colours than properties, if there is a clear set of default colours.
I am concerned that there is an attempt to be too indirect, the way that
DiffServ tried with
On 22 Jul 2013, at 10:01, Shwetha Bhandari (shwethab) shwet...@cisco.com
wrote:
Hello,
A new draft draft-lepape-6man-prefix-metadata-00 describing
a method for applications to learn and influence source address selection by
associating
IPv6 prefixes with meta-data when configured
Hello,
A new draft
draft-lepape-6man-prefix-metadata-00http://tools.ietf.org/html/draft-lepape-6man-prefix-metadata-00
describing a method for applications to learn and influence source address
selection by associating IPv6 prefixes with meta-data when configured by the
network is submitted
