From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from IMSVA.IN.MEGATRENDS.COM (Webmail.amiindia.co.in [203.199.198.232]) (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 7CD7B21951C92 for ; Tue, 2 May 2017 00:09:46 -0700 (PDT) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id C00E782047 for ; Tue, 2 May 2017 12:41:32 +0530 (IST) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id AA50C82046 for ; Tue, 2 May 2017 12:41:32 +0530 (IST) Received: from webmail.amiindia.co.in (venus1.in.megatrends.com [10.0.0.5]) by IMSVA.IN.MEGATRENDS.COM (Postfix) with ESMTPS for ; Tue, 2 May 2017 12:41:32 +0530 (IST) Received: from VENUS2.in.megatrends.com ([fe80::2002:4a07:4f17:c09b]) by VENUS1.in.megatrends.com ([fe80::951:7975:6ecf:eae5%14]) with mapi id 14.01.0438.000; Tue, 2 May 2017 12:39:41 +0530 From: Karunakar P To: "edk2-devel@lists.01.org" Thread-Topic: Does edk2 supports RFC standards 3132? Thread-Index: AdLDEvgF9AmvJv0xS2mY4m9ea4xMDg== Date: Tue, 2 May 2017 07:09:41 +0000 Message-ID: Accept-Language: en-GB, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.0.84.164] MIME-Version: 1.0 X-TM-AS-GCONF: 00 X-TM-AS-Product-Ver: IMSVA-9.1.0.1600-8.1.0.1062-23044.005 X-TM-AS-Result: No--17.745-5.0-31-10 X-imss-scan-details: No--17.745-5.0-31-10 X-TMASE-Version: IMSVA-9.1.0.1600-8.1.1062-23044.005 X-TMASE-Result: 10--17.744700-10.000000 X-TMASE-MatchedRID: ZX8kMFEwPc4C8/gH0ZUaB5VIEKhlTKpsguwtqyXlE6Gtj24Xqh0yXBvh 8HrJc28GRTCo3/ci8lIuWlWHXeK0FClMSnJkvXdeLTHwnYOikQ0n9092gsBYOWEORtrscnjUZqh J5ESvkX4E0NPV6hmv8uDmaeE7z2RkRF8J0whn5t39KXlxhBAZb4N12XKYbuJLStFk/81wIJKLOs WlYdMG9wR1ZtMYefFWPC7j/mzpDFrd4xdn1XD3c0OZWaJBszmqEsPHM6iHL3YUtdRZTmEaIV2pa +aJMbyan9fPWsL/WDQa89WSX1xM/otUkiO6jsmxEgwM8US/pTF9e88fgoklswwv1ZvdCH+FmPMv FiO40LCPL1kerA0y5HJijuKE1vE5L0W1btd8e54OsNNBnlgRWn0tCKdnhB58r10pknZXGJrPPeN 6HN6d7Ol37+ty9Rb2IAcCikR3vq+5kUW9V1dBtCtEn/qkiYf3o7+RwFmlCysgbXyRlq7dxn54nl Z0R9W5 X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0,39:0-0 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 Subject: Does edk2 supports RFC standards 3132? 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: Tue, 02 May 2017 07:09:47 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi all, Does edk2 supports RFC 3132? I can find DHCP RFCs supported info in Dhcp4Impl.h, it doesn't have RFC 313= 2. Does it mean edk2 don't support it yet? Do edk2 have plans to support it= ? /** @file EFI DHCP protocol implementation. RFCs supported are: RFC 2131: Dynamic Host Configuration Protocol RFC 2132: DHCP Options and BOOTP Vendor Extensions RFC 1534: Interoperation Between DHCP and BOOTP RFC 3396: Encoding Long Options in DHCP. Copyright (c) 2006 - 2016, Intel Corporation. All rights reserved.
This program and the accompanying materials are licensed and made available under the terms and conditions of the BSD L= icense which accompanies this distribution. The full text of the license may be f= ound at http://opensource.org/licenses/bsd-license.php THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIE= D. **/ Thanks, karunakar