Jari Arkko wrote:
> how long do you think producing the general document
> to an RFC will take? What should we say in the
> meantime to folks who want to deploy IPv6 now?
What if we make some revision to "draft-ietf-ipv6-cellular-host",
and run that as Informational? Then we could have IPv6 Host
Requirements later on the standards track. We could even
have a later IPv6-over-3GPP standards track document which
would obsolete the Informational document, if desirable.
Or, would that be IPv6-over-3.75G?
> If there are decisions as to what to do with ND/DAD/whatever,
> should those be made by (a) IPv6 WG, (b) 3GPP, or (c)
> vendors?
Each of these groups will make decisions. However, I think that
the IPv6 working group should have the responsibility to
determine protocol behavior for a general IPv6 node.
Clearly, in general, an IPv6 node has to be able to run
these protocols. But there are times when the node should
be allowed to attach to a link without using them.
As an example, in the Mobile IPv6 working group, we have a
document that enables a mobile node to attach to a new link
without running DAD. This is done only after assurance is
received, that no other node at the new point of attachment
could possibly have a conflicting address with the mobile
node. A more general statement could be something like:
"An IPv6 node MUST run DAD unless it already has assurance
that there is no possible address conflict."
with some more wordsmithing. One way to satisfy this would
be to have DAD run by some proxy agent -- again, the Mobile
IPv6 home agent has this responsibility at times. Also,
note that in this case the mobile node is still presumed to
be able to run DAD, it just does not have always do DAD.
If all this has been said before, please just chalk it up
to my inability to keep up with enough mail lately.
Regards,
Charlie P.
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
