Re: DHCP Automatic Configure at Driver Connect

["Cohen, Eugene" <eugene@hp.com>]

Jiaxin,
 
> I mean I didn't know whether the *un-configured* status you want
> contain *no policy setting * or not. But it doesn't matter now, from
> your statement here, I know you don't care the policy setting.

Correct the static vs dhcp is irrelevant - it's the fact that the IP layer comes up that is the issue.

> As I said in previous email, " The current behavior of Ip4Config2: DHCP
> policy together with D.O.R.A process, which is the same case as the old
> Ip4Config behavior ". 

I'm confused by this statement because I can see a distinct difference in behavior from the past.  I can see the new code which enables the new behavior as well Ip4Config2OnDhcp4SbInstalled- when the DHCP SB is installed you do a configure automatically - this code simply did not exist before -- see Ip4Config2OnDhcp4SbInstalled.

> From the case you described here, are you want
> to separate the DHCP policy setting and D.O.R.A process? We don't
> know.

Yes, You could say I want to separate the DHCP vs static policy from D.O.R.A. but I don't think that's a good way to state it - I would state that we don't want the IP protocol (whether it be DHCP or statically configured) to be "up" until a piece of UEFI calls Configure().    
 
> The provided solution for you (such a DXE Driver) is only based on you
> want an *un-configured* status at each boot time until the third part
> configuration. I think it does an approach for this. But I think Ting is
> right, "we need fully understand your usage case before analyzing the
> problem". Perhaps you have more detailed requirements we don't
> know clearly.

We want the IP config information stored in NVRAM (dhcp or static) to be preserved but want a separate policy choice to delay the IP interface coming "up" until a component calls Configure().

Eugene