Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-tunnel-01.txt

[Ole Trøan <[e-mail]>]

Ted,

>> I think we should do this too. let us make sure we get that into the RFC3315bis that I clearly remember you volunteered to write. ;-)
>> this draft proposes a solution that only affects the client implementation though (that is changing anyway), so I think we need this for a deployable solution.
> 
> The changes required to RFC3315 to do what you want are minor and don't require a spin of the full document—you can just issue a short document, about the length of your current one, that updates RFC3315.   This will get you what you want in the short term, and then we can fold your work into the RFC3315 update when the time comes.

there would be two client/server changes:
 - allow global unicast addresses as source address
 - allow a unicast address as destination address to reach the DHCPv6 server

there are a few MUSTs that must be changed. equally there might be security implications, and new text for how the server should deal with on or offlink clients.

> What you are doing here is proposing something completely different, that is unnecessarily complicated, and makes things worse, and that will not be compatible with the subsequent update to RFC3315.   IOW, two solutions, where one would have done better.

this isn't completely different. the draft describes how this can be achieved with existing DHCPv6 servers and within current RFC3315.
what is complicated and what is not compatible?

cheers,
Ole