how to explain RFC 3315 sec 17.2.2 (together with CPE router requirements) ?

[Marco Hogewoning <marcoh@marcoh.net>]

Hi Folks.

I have a bit of a discussion with one of our vendors regarding the DHCPv6 implementation we use on our DSL platform. Hopefully one of you can shed some light on this to understand what the intentions are.

'IPv6 CE router requirements' requirement W-5 states:

"DHCPv6 address assignment (IA_NA) and DHCPv6 prefix delegation (IA_PD) SHOULD be done as a single DHCPv6 session."

And something further down gives some hints on how the responses should be handled, including WPD-7:

"If the IPv6 CE router requests both an IA_NA and an IA_PD in DHCPv6, it MUST accept an IA_PD in DHCPv6 Advertise/Reply messages, even if the message does not contain any addresses (IA_NA options with status code equal to NoAddrsAvail)."

They (the vendor) have implemented this and are requesting IA_NA and IA_PD, our platform (JUNOSe built-in) server responds with a message only containing an IA_PD. This is on purpose as we don't intend to assign addresses to the PPP link itself (other then link-local).

The discussion now is on the way we currently handle the IA_NA, by simply ignoring it. Which is based on rfc 3315, sec 17.2.2:

   If the server will not assign any addresses to any IAs in a
   subsequent Request from the client, the server MUST send an Advertise
   message to the client that includes only a Status Code option with
   code NoAddrsAvail and a status message for the user, a Server
   Identifier option with the server's DUID, and a Client Identifier
   option with the client's DUID.

I think we are correct in our response, we at least respond with one IA (IA_PD) and thus follow the paragraph before this:

   If the Solicit message from the client included one or more IA
   options, the server MUST include IA options in the Advertise message
   containing any addresses that would be assigned to IAs contained in
   the Solicit message from the client.

WPD-7 seems to exist specifically to handle this situation ?

Any opnions on who is right here ? Do I need to file a bug with Juniper or is our CPE vendor wrong ? (They already implemented a fix and are now accepting this, so it's just to assure they are still RFC compliant). 

TIA,

MarcoH