From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id AE75F21B02B9C for ; Thu, 29 Jun 2017 23:49:59 -0700 (PDT) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Jun 2017 23:51:32 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.40,285,1496127600"; d="scan'208";a="280504658" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by fmsmga004.fm.intel.com with ESMTP; 29 Jun 2017 23:51:32 -0700 Received: from fmsmsx151.amr.corp.intel.com (10.18.125.4) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 29 Jun 2017 23:51:32 -0700 Received: from shsmsx104.ccr.corp.intel.com (10.239.4.70) by FMSMSX151.amr.corp.intel.com (10.18.125.4) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 29 Jun 2017 23:51:31 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.116]) by SHSMSX104.ccr.corp.intel.com ([10.239.4.70]) with mapi id 14.03.0319.002; Fri, 30 Jun 2017 14:51:30 +0800 From: "Ye, Ting" To: Santhapur Naveen , "edk2-devel@lists.01.org" Thread-Topic: IPv6 Stateless autoconfiguration Thread-Index: AdLxYhqT4FLpfKZ/T5iDvq6mU1Y1MQABVQZA Date: Fri, 30 Jun 2017 06:51:29 +0000 Message-ID: References: <625A2455CC232F40B0F38F05ACED6D97FA8D5BB8@VENUS1.in.megatrends.com> In-Reply-To: <625A2455CC232F40B0F38F05ACED6D97FA8D5BB8@VENUS1.in.megatrends.com> Accept-Language: zh-CN, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Subject: Re: IPv6 Stateless autoconfiguration X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jun 2017 06:49:59 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Naveen, Yes, EDKII supports IPv6 stateless address autoconfiguration defined in RFC= 4862. It includes two parts: - generating link-local address - generating global address via stateless address autoconfiguration. The later part requires an IPv6 router to send Router Advertisement with va= lid prefix information options periodically to UEFI client. In EDKII, we can't assume that the network environment has an IPv6 router c= orrectly configured and an IPv6 stateless address is available.=20 And both HTTP boot and PXE boot over IPv6 stack defined in UEFI spec includ= e a step that getting IPv6 address and other DHCP options from DHCP server. So, current implementation gets IPv6 address from DHCPv6 service. Thanks, Ting=20 -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Sant= hapur Naveen Sent: Friday, June 30, 2017 1:46 PM To: edk2-devel@lists.01.org Subject: [edk2] IPv6 Stateless autoconfiguration Hello all, I have some queries for which the answers are needed from the experts here.= Please help in answering them. Does edk2 support IPv6 stateless address autoconfiguration as mentioned in = RFC4862. If yes, then why do we have to configure the dhcpv6 service in such a way t= hat it provides IPv6 address also for HTTPv6/PXEv6 boot? Thank you Naveen _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel