[dhcwg] draft-chowdhury-dhc-bcmcv[46]-option-01.txt

The dhc WG has been asked to consider two drafts,
draft-chowdhury-dhc-bcmcv4-option-01.txt and
draft-chowdhury-dhc-bcmcv6-option-01.txt, for acceptance as WG work
items.  There has been some discussion of these two drafts, starting
at http://www1.ietf.org/mail-archive/web/dhcwg/current/msg04124.html.

There has been no objection to the primary purpose of these drafts,
and the discussion has focused on whether the options defined as in
the two drafts or should they be redefined to be carried as
vendor-identifying vendor-specific options.  As we have a fairly tight
deadline for moving forward on these drafts, I have decided to accept
the drafts as WG work items.

We still need to come to consensus as to the decision about how to
define the options.  Reiterating from my previous e-mail about the
options, here are some considerations for discussion:

3GPP2 has defined some vendor-specific sub-options, for example, to
identify a MIP home agent for the DHCP client.

A 3GPP2 client needs to specify to the DHCP server which parameters it
needs - specifically, whether it needs to receive the BCMCS servers.
If the current drafts are adopted, the client can simply use the
parameter request list option (option code 55) for the request.  If a
VIVSO sub-option is used, 3GPP2 would also define a parameter request
list sub-option.

There is a deployment issue, as some service providers already have
DHCP servers in place that must be updated for any new options.  Is it
the case that the options defined in the current drafts can be
supported without code changes to existing servers?  Use of a VIVSO
sub-option would require code changes to existing servers.  How long
would it take to deploy DHCP server that can support VIVSO.

BCMCS may be adopted across multiple technologies, so the options in
the current drafts would not be specific to 3GPP2.  However, the BCMCS
specification has not adopted by other standards, yet, so we may need
to define additional options for related services in the future if
those services are not interoperable with the 3GPP2 BCMCS service.

- Ralph

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg