From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from NAM01-SN1-obe.outbound.protection.outlook.com (mail-sn1nam01on0729.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe40::729]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 46BC31A1DF4 for ; Tue, 16 Aug 2016 12:41:37 -0700 (PDT) Received: from AT5PR84MB0291.NAMPRD84.PROD.OUTLOOK.COM (10.162.138.25) by AT5PR84MB0290.NAMPRD84.PROD.OUTLOOK.COM (10.162.138.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.549.15; Tue, 16 Aug 2016 19:41:34 +0000 Received: from AT5PR84MB0291.NAMPRD84.PROD.OUTLOOK.COM ([10.162.138.25]) by AT5PR84MB0291.NAMPRD84.PROD.OUTLOOK.COM ([10.162.138.25]) with mapi id 15.01.0549.027; Tue, 16 Aug 2016 19:41:34 +0000 From: "Cohen, Eugene" To: "Wu, Jiaxin" , "Ye, Ting" , "edk2-devel@lists.01.org" , "Kinney, Michael D" Thread-Topic: DHCP Automatic Configure at Driver Connect Thread-Index: AdHzMrTK7bp7ndKxTJOq/Qc4XXghzQARlkIgAAQKA6AAE/Dm8AAV/5hgABh+18AAGhwegACBdhLAABj3DZAAI4TcYA== Date: Tue, 16 Aug 2016 19:41:34 +0000 Message-ID: References: <895558F6EA4E3B41AC93A00D163B7274137C5EA3@SHSMSX103.ccr.corp.intel.com> <895558F6EA4E3B41AC93A00D163B7274137C63EC@SHSMSX103.ccr.corp.intel.com> <895558F6EA4E3B41AC93A00D163B7274137C677D@SHSMSX103.ccr.corp.intel.com> <895558F6EA4E3B41AC93A00D163B7274137C7D82@SHSMSX103.ccr.corp.intel.com> In-Reply-To: <895558F6EA4E3B41AC93A00D163B7274137C7D82@SHSMSX103.ccr.corp.intel.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=eugene@hp.com; x-originating-ip: [15.65.254.4] x-ms-office365-filtering-correlation-id: e7f24145-b8f0-4e30-7e85-08d3c60d54b9 x-microsoft-exchange-diagnostics: 1; AT5PR84MB0290; 6:t/v1pgVwG67RymRPaSIVFz0CuWnFoLym/qcYSPHN2CYkQYKN4Wpqdqswrb817rxzYQh1sQYOyz+oGRzQ7gViKe+bI4/bzZEv2X9geS0Cyhb7+Stui4sSy5EIgywIGSD5mT7I3rXvnk9cUw5T0LBprxJ7imL4gitllckYNkaKFjG+Wc0TXrOp6WCj3oXi4NjBzUxsrMOYdAS6D18bL7+0TDSAy9RNA128rNAa2oI5FPg4jROloR2Vo7oj3f3JUr2s/NKHVkYKAhClndhEr6pkJjDLSpkb4zytDP2zGI3jMp0=; 5:uT5rAXN48PVZcGJ41oLT7W9WNjAWR4af211JLjnUExu76X0MLDA4cIhXvyVuuKS8NWa0udU2jgNPf3Pdf+sOwn0kAfaPDqDO2V6kub6jBvHmNz766te3pHNSW7/gfk9rnIYr0ULxnwnuvBaqqEvsOw==; 24:3ToRyJFmD7Z+/PzOj5Mg8YLavJ6brsEqNEl7IQFbjaBan2Pl+cOoZcMuYRmKAm5GqBC+LLvxhHiDLq1aPsrhj775ZIrBXm85KtQM3y/p/5s=; 7:QGyhh7AYNPrcZUny/qAXoWYrFJSUgSwdR3xRGboE1L4GHpp2fXgA6fDVrgfhlGFJZj4LEMdqWA5eftjsEBTGnz1gQoJwX+sBkSNS4GmIc39V/o7UTl28doGgBrnmtnFNkr5qnfyOMaPeBkaWmxVH8QQLMHg3reg4bnxWmgGTIHRMvedH+Mfn4NVU0K0mQnNfeLSDAt/bExjO/nnNwu55tRfcpumnZG48Afc6CxV2XHIKS5JebUBpMKNi0wo6z80+ x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AT5PR84MB0290; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(21532816269658); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046); SRVR:AT5PR84MB0290; BCL:0; PCL:0; RULEID:; SRVR:AT5PR84MB0290; x-forefront-prvs: 0036736630 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(189002)(6602003)(199003)(92566002)(8676002)(81156014)(81166006)(33656002)(2906002)(7846002)(54356999)(86362001)(5002640100001)(10400500002)(66066001)(87936001)(2900100001)(11100500001)(3280700002)(77096005)(2501003)(3660700001)(68736007)(50986999)(102836003)(99286002)(2950100001)(101416001)(8936002)(9686002)(76176999)(586003)(6116002)(3846002)(5001770100001)(93886004)(105586002)(189998001)(7736002)(122556002)(106356001)(7696003)(107886002)(305945005)(74316002)(97736004)(19627235001); DIR:OUT; SFP:1102; SCL:1; SRVR:AT5PR84MB0290; H:AT5PR84MB0291.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Aug 2016 19:41:34.5907 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: ca7981a2-785a-463d-b82a-3db87dfc3ce6 X-MS-Exchange-Transport-CrossTenantHeadersStamped: AT5PR84MB0290 Subject: Re: DHCP Automatic Configure at Driver Connect X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Aug 2016 19:41:37 -0000 Content-Language: en-US Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Jiaxin, =20 > 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 ".=20 I'm confused by this statement because I can see a distinct difference in b= ehavior from the past. I can see the new code which enables the new behavi= or 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(). =20 =20 > 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 pr= eserved but want a separate policy choice to delay the IP interface coming = "up" until a component calls Configure(). Eugene