From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124])
 by mx.groups.io with SMTP id smtpd.web12.676.1602087040266074040
 for <devel@edk2.groups.io>;
 Wed, 07 Oct 2020 09:10:40 -0700
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=IwAiJIJK;
 spf=pass (domain: redhat.com, ip: 216.205.24.124, mailfrom: lersek@redhat.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1602087039;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=yzHtlwd16I0/nEckqtoRkFCnSyw9BJhskboKBu62vK0=;
	b=IwAiJIJK/e8hTZNDWI5zgcoUGXXAVDFZq8+Yi3L/zdlPpoeSs4oHXhoKUD681puw+mc55F
	Km1y7vPZpXhWxNCR4/89DJcyN0yw9MURvgyXwoazvf/u/qMeWB82ubZBxruXBybJePN1r7
	gynm0MMNtsq/ZqR0t4KC2lZd1xtKN/M=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com
 [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id
 us-mta-437-BD5vBVYMMdaJUS7nj7j0Aw-1; Wed, 07 Oct 2020 12:10:37 -0400
X-MC-Unique: BD5vBVYMMdaJUS7nj7j0Aw-1
Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx01.redhat.com (Postfix) with ESMTPS id D386F80401A;
	Wed,  7 Oct 2020 16:10:35 +0000 (UTC)
Received: from lacos-laptop-7.usersys.redhat.com (ovpn-113-94.ams2.redhat.com [10.36.113.94])
	by smtp.corp.redhat.com (Postfix) with ESMTP id B274E6EF4B;
	Wed,  7 Oct 2020 16:10:33 +0000 (UTC)
Subject: Re: [edk2-devel] Server name Indication (SNI) support in CryptoPkg
To: devel@edk2.groups.io, prarthanasv@amiindia.co.in
References: <013B69FA8423AE4585E1D2D1AA16ACB101D81A7043@VENUS1.in.megatrends.com>
Cc: Maciej Rabeda <maciej.rabeda@linux.intel.com>,
 Jiaxin Wu <jiaxin.wu@intel.com>, Siyuan Fu <siyuan.fu@intel.com>,
 Jiewen Yao <jiewen.yao@intel.com>, Jian J Wang <jian.j.wang@intel.com>,
 Xiaoyu Lu <xiaoyux.lu@intel.com>, Guomin Jiang <guomin.jiang@intel.com>
From: "Laszlo Ersek" <lersek@redhat.com>
Message-ID: <ca348d7b-1fc3-b9ee-7846-a5cd07168aa3@redhat.com>
Date: Wed, 7 Oct 2020 18:10:32 +0200
MIME-Version: 1.0
In-Reply-To: <013B69FA8423AE4585E1D2D1AA16ACB101D81A7043@VENUS1.in.megatrends.com>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13
Authentication-Results: relay.mimecast.com;
	auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=lersek@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset=windows-1252
Content-Language: en-US
Content-Transfer-Encoding: 7bit

On 10/07/20 14:13, Prarthana Sagar V wrote:
> Hello,
> 
> CryptoPkg has no support to send SNI extension in ClientHello during Handshake.
> When multiple URLs are used in single server, then it is necessary to send host name as SNI in ClientHello to make the handshake successful.
> Does EDK2 have any plan to support it?

CC'ing NetworkPkg and CryptoPkg owners.

Thanks
Laszlo