[EMAIL PROTECTED] wrote:
> Hi Margaret,
> 
> As pointed out, the draft you have edited (draft-ietf-ipv6-3gpp-recommend-02.txt)
> states:
> 
>   7.1 Limitations of 3GPP Address Assignment
> 
>     The current 3GPP address assignment mechanism has the following
>     limitations:
> 
>          The GGSN only advertises a single /64 prefix, rather than a
>          set of prefixes.  This will prevent the participation of 3GPP
>          nodes (e.g. handsets or 3GPP-attached laptops) in IPv6 site
>          renumbering, or in other mechanisms that expect IPv6 hosts to
>          create addresses based on multiple advertised prefixes.
> 
>          A 3GPP node is assigned a single identifier and is not allowed
>          to generate additional identifiers.  This will prevent the use
>          of privacy addresses by 3GPP nodes.  This also makes 3GPP
>          mechanisms not fully compliant with the expected behavior of
>          IPv6 nodes, which will result in incompatibility with popular
>          laptop IPv6 stacks.  For example, a laptop that uses privacy
>          addresses for web browser connections could not currently not
>          currently establish a web browser connection over a 3GPP link.
> 
> As our draft is not meant to change either IETF nor 3GPP specifications,
> we cannot make any additional claims.
> 
> Is there something that you wish to see in our document to fully cover
> this?  One possiblility would be to add the following text to the end
> of 2.5.1:
> 
>   If Privacy Addresses are used [RFC-3041], then DupAddrDetectTransmits 
>   should not be set to zero.
> 
> John

As long as the GGSN does not configure any global scope addresses on its 
interface towards the 3G host, Privacy Addresses can be used with 
DupAddrDetectTransmits = 0. IMO there is no need for a global scope address on 
the interface towards the host, it's a point-to-point link and if the host needs 
to send packets with the GGSN as destination, it can just use the all-routers 
multicast address.

/Gerben

--------------------------------------------------------------------
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]
--------------------------------------------------------------------

Reply via email to