Hi all,
One point of clarification:
> > Section 2.5.1:
> >
> > DAD is not an optional part of Stateless Address Autoconfiguration,
> > and it should not be considered optional for cellular hosts.
> > If you really believe that DAD should be optional for some link
> > types, we need to re-visit the Stateless Autoconfiguration spec.
> > We should not just declare DAD to be optional here.
>
> I think we (the authors) need to do some thinking on this, as there
> is the feeling that 2462 does not apply to the 3GPP network, but
> I guess you feel strongly that it does.
I think a possible resolution to this is to state something like the
following:
2.5.1 Stateless Address Autoconfiguration in 3GPP
A 3GPP cellular host must process a Router Advertisement as stated
in chapter 5.5.3 of [RFC-2462].
These cellular hosts can set DupAddrDetectTransmits equal to zero,
as each delegated prefix is unique within its scope when allocated
using the 3GPP IPv6 Stateless Address Autoconfiguration.
See appendix B for more details on 3GPP IPv6 Stateless Address
Autoconfiguration.
I base my reasoning on the following text:
>From IPv6 Stateless Address Autoconfiguration (RFC2462)
DupAddrDetectTransmits
The number of consecutive Neighbor Solicitation
messages sent while performing Duplicate Address
Detection on a tentative address. A value of zero
indicates that Duplicate Address Detection is not
performed on tentative addresses. A value of one
indicates a single transmission with no follow up
retransmissions.
Default: 1, but may be overridden by a link-type
specific value in the document that covers issues
related to the transmission of IP over a particular
link type (e.g., [IPv6-ETHER]).
>From IPv6 over PPP (RFC2472):
5. Stateless Autoconfiguration and Link-Local Addresses
The Interface Identifier of IPv6 unicast addresses [6] of a PPP
interface, SHOULD be negotiated in the IPV6CP phase of the PPP
connection setup (see section 4.1). If no valid Interface Identifier
has been successfully negotiated, procedures for recovering from such
a case are unspecified. One approach is to manually configure the
Interface Identifier of the interface.
As long as the Interface Identifier is negotiated in the IPV6CP phase
of the PPP connection setup, it is redundant to perform duplicate
address detection as a part of the IPv6 Stateless Autoconfiguration
protocol [3]. Therefore it is recommended that for PPP links with
the IPV6CP Interface-Identifier option enabled the default value of
the DupAddrDetectTransmits autoconfiguration variable [3] be zero.
Does this sound reasonable?
John
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
