<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On 28 Mar 2013, at 00:58, Erik Kline <<a href="mailto:ek@google.com">ek@google.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
P.S. RFC 6866 touches on this issue. draft-chown-6man-tokenised-ipv6-identifiers<br>
touched on it too, but was not adopted so far.<br></blockquote><div><br></div><div style="">I don't recall seeing that draft go by. Over all it makes sense to me, though I think using the word "token" kind of confuses the issue as compared to just talking about IIDs. (What's wrong with just something like "ifconfig eth0 inet6 iid add ::dead:beef" or whatever?)</div>
<div style=""><br></div><div style="">Also: maybe something for v6ops, rather then 6man?</div></div></div></div></blockquote><br></div><div>I used 'token' as that was the term used in the original implementation in Solaris. Someone at our uni then did an implementation for Linux. That was maybe 10 years ago now though. It was the recent 6renum work that made me think it was worth documenting. There are various ways you could implement it. I'll nudge it on the 6man list, and see where it goes.</div><div><br></div><div>Tim</div></body></html>