Re: [v6ops] draft-ietf-v6ops-6204bis WGLC

["Hemant Singh (shemant)" <[e-mail]>]

Chris,

 

-----Original Message-----
From: Chris Grundemann [mailto:[e-mail]] 
Sent: Tuesday, March 20, 2012 4:36 PM
To: Ole Trøan; Hemant Singh (shemant)
Cc: [e-mail]; [e-mail]; Ronald Bonica
Subject: Re: [v6ops] draft-ietf-v6ops-6204bis WGLC

 

 

>Yes, and the O flag is the "Other configuration" flag. PD is certainly

>other DHCPv6 configuration information. In fact, RFC 4861 is quite clear

>on this point, it states: "If neither M nor O flags are set, this

>indicates that no information is available via DHCPv6." (emphasis on 'NO

>information')

 

Not quite.  The O flag is to obtain information using stateless DHCPv6 - see http://tools.ietf.org/rfc/rfc3736.txt.

PD acquisition is a stateful DHCPv6 procedure or RFC 3633 has to also clarify if PD acquisition is supported via both stateful and stateless DHCPv6.  We have discussed such a clarification with Ralph Droms and Ole in the past - don't remember the outcome.  Further, a DHCPv6 client includes the IA_NA and the IA_PD option in the DHCPv6 SOLICIT.  IA_NA IA_Address acquisition is a stateful DHCPv6 operation and now if PD acquisition is a stateless operation, what if the DHCPv6 server the SOLICIT is going to is only stateless (and if rfc3633 supports stateless dhcpv6 operation?). The IA_NA is not obtained from such a server.   I hope it's clear now the kind of DHCPv6 client and server issues one has.  In the kind of network I develop products for, I so do prefer that 120,000 DHCPv6 clients on my router relay agent do issue SOLICIT with both IA_NA and the IA_PD so that I save upstream bandwidth or alleviate congestion.  The DHCPv6 server in our deployment also better support stateful and stateless services in one server.  

 

I keep hearing of new corner cases in the DHC WG related to DHCPv6 server for the PD being separate from the server that allocates IA_NA's.  It's fine to work out such corner cases, but a gentle reminder that the broadband networks, IMHO, need consolidated options in a DHCPv6 SOLICIT.

 

Hemant