<div dir="ltr">On 5 April 2013 13:01, Ted Lemon <span dir="ltr"><<a href="mailto:Ted.Lemon@nominum.com" target="_blank">Ted.Lemon@nominum.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div style="word-wrap:break-word">That's not compliant with RFC3315. That's not the criterion that's supposed to be used to decide whether or not the DUID-LL identifier is permissible.
</div></blockquote><div><br>I never claimed it was, I was simply replying on how you can tell the client which type of address to use.<br><br>I
guess the bigger question is why does the DUID-LLT keep changing, if
I'm to read RFC3315 correctly it states that DUID-LLT is generated once
and then written to non-volatile storage for future use. So does the
client have non-volatile storage? if so is dhclient writing the value to a
non-volatile location? <br></div></div></div></div>