Interesting point Bob raises.
Thomas,
Is the intention for the new text to relax the requirement for
auto-configuration? The new DHCPv6 text should be in addition to support
for stateless auto-configuration to ensure other deployment models are
supported.
John
Ralph, Thomas, John,
The attributes that come to mind are those that are DNS related via
RFC6106. In theory I suppose what John mentioned could be an issue,
however, in a broadband DOCSIS environment we only support stateful DHCPv6
for provisioning today as such I do not anticipate seeing these
Alex,
In DOCSIS deployments there are no issue with RAs and we do know how to
configure the default route. DHCPv6 is used mainly for address, prefix,
and configuration information.
John
=
John Jason Brzozowski
Comcast Cable
e)
Bert,
I sent some mail earlier on this topic. We do require it for provisioning
via the WAN interface. On the LAN we aim to ensure there is greater
flexibility. I just want to make sure it is clear that cable broadband
does not require the use of DHCPv6 in the premise. This is a local
On 2011-05-16 07:40, Timothy E. Enos wrote:
Hi Bob,
Thanks for your reply. I would say that partly because there are so many
different deployment models that MAY is precisely what is informed here.
That said, an acceptable alternative for me would be that it be SHOULD
for both DHCPv6 and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just read this thread. This is so great.
Thanks to Thomas and all for the new text.
Seiichi
(2011/05/14 8:32), Brian Haberman wrote:
All,
The chairs have determined that there is a strong consensus to
elevate DHCPv6 to SHOULD support in the
