On 05/19/2013 07:55 PM, Karl Auer wrote:
> On Sun, 2013-05-19 at 19:06 -0300, Fernando Gont wrote:
>> You're right. s/desirable/required/?
>>
>> (I don't think "REQUIRED" (caps) would be needed, since the bullests
>> contain RFC2119-anguage, already).
>
> LC or UC "required" would be OK.
Ok, done
On Sun, 2013-05-19 at 19:06 -0300, Fernando Gont wrote:
> You're right. s/desirable/required/?
>
> (I don't think "REQUIRED" (caps) would be needed, since the bullests
> contain RFC2119-anguage, already).
LC or UC "required" would be OK.
Regards,K.
--
~~
On 05/19/2013 07:03 PM, Karl Auer wrote:
> On Sun, 2013-05-19 at 16:55 +, 6man issue tracker wrote:
>> The following properties are desirable for the Net_Iface:
>> o it MUST be constant across system bootstrap sequences and other
>>network events (e.g., bringing another interface u
On Sun, 2013-05-19 at 16:55 +, 6man issue tracker wrote:
> The following properties are desirable for the Net_Iface:
> o it MUST be constant across system bootstrap sequences and other
>network events (e.g., bringing another interface up or down)
> o it MUST be different for e
#1: Proper source for an "Interface Identifier"
Changes (by fg...@si6networks.com):
* status: new => closed
* resolution: => fixed
Comment:
The "Interface Identifier" has now been replaced with a generic
"Net_Iface" parameter, and we describe what are the required properties
for this I
#1: Proper source for an "Interface Identifier"
Version -06 of the document includes the "interface index" in the
expression "F()" that generate the stable privacy IIDs. It has been noted
that interface indexes might not be stable, and that, in any case,
mandating a specific source for tan "in
