> (1) The Duplicate address detection shouldn’t be recommended to be 
 > disabled, if the IPv6CP negotiates interface identifier with 
 > the peer.
 > *
 > *
 > 
 >     *Rationale:*
 > 
 >     (a) In the mobile (3GPP) networks the host isn't stationary. As
 >     such, the interface identifier uniqueness may not be ensured at
 >     different space points in the provider network (for 
 > instance, in the
 >     case of randomly generated Interface Identifier). This would then
 >     warrant the mobile host to trigger duplicate address detection as
 >     and when it changes it's position.

(a) doesn't seem correct to me. In terms of 3GPP nets the host is
stationary with respect to its default router. Also as recommended
in RFC 3314 an entire /64 is assigned to a mobile's connection so DAD
is not useful. Looks to me like the 3GPP case would actually be in
favour of disabling DAD.

/Karim

This communication is confidential and intended solely for the addressee(s). Any 
unauthorized review, use, disclosure or distribution is prohibited. If you believe 
this message has been sent to you in error, please notify the sender by replying to 
this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, 
unauthorized amendment, tampering and viruses, and we only send and receive e-mails on 
the basis that we are not liable for any such corruption, interception, amendment, 
tampering or viruses or any consequences thereof.


--------------------------------------------------------------------
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to