Hosnieh,
"an application layer lifetime".
1) The problem that this is a solution for.
I've looked through the draft multiple times, and what I see is a generic
abstract and then a very specific dive-in into the details.
What I think is very much missing is - what is the application you see in
m
On Jul 31, 2013, at 14:03 , Brian E Carpenter
wrote:
>
> I suppose, if the MAC layer actually delivers the clashing packet to the ND
> layer.
Alas, the presence of Neighbor Discovery proxy can disrupt that mechanism.
--
james woodyatt
core os networking
Ole,
On 31/07/2013 20:22, Ole Troan wrote:
> Brian,
>
> (participant hat)
>
>>> I found the last statements in section 4 slightly confusing:
>>> There is no algorithm
>>> for determining whether this case has arisen, rather than a genuine
>>> MAC address collision. Implementers should car
Let's first start the discussion about the lifetime of an IID. There are
some sections in RFC 4941 that explains the lifetime of an IID
The maximum lifetime is 1 week and preferred lifetime is 1 day. The address
cannot exceed the maximum lifetime value. When it reaches to this maximum
value, th
https://tools.ietf.org/html/draft-nachum-sarp-06 proposes a Proxy Gateway
mechanism to limit switches' FDB (MAC table) sizes in an environment where
hosts (or VMs) within one subnet (or VLAN) can spread over many access domains
(or shelves or sites) and each access domain has hosts (VMs) belongi
There was consensus to adopt draft-droms-6man-multicast-scopes-02 as a 6MAN
working group item at the IETF87 working group meeting. This is a call to
confirm that consensus on the mailing list.
If you object to adopting this document please state so and your reasons.
This call will end on 2013-
There was consensus to adopt
draft-cooper-6man-ipv6-address-generation-privacy-00 as a 6MAN working group
item at the IETF87 working group meeting. This is a call to confirm that
consensus on the mailing list.
If you object to adopting this document please state so and your reasons.
This call
Brian,
(participant hat)
>> I found the last statements in section 4 slightly confusing:
>> There is no algorithm
>> for determining whether this case has arisen, rather than a genuine
>> MAC address collision. Implementers should carefully consider the
>> consequences of continuing IPv6
