From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [14.98.235.2]) by mx.groups.io with SMTP id smtpd.web12.14910.1598971761836881472 for ; Tue, 01 Sep 2020 07:49:22 -0700 Authentication-Results: mx.groups.io; dkim=missing; spf=none, err=SPF record not found (domain: amiindia.co.in, ip: 14.98.235.2, mailfrom: sivaramann@amiindia.co.in) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 4485982058; Tue, 1 Sep 2020 20:28:10 +0530 (IST) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id DDF7E82047; Tue, 1 Sep 2020 20:28:09 +0530 (IST) Received: from webmail.amiindia.co.in (venus2.in.megatrends.com [10.0.0.7]) by IMSVA.IN.MEGATRENDS.COM (Postfix) with ESMTPS; Tue, 1 Sep 2020 20:28:09 +0530 (IST) Received: from VENUS1.in.megatrends.com ([fe80::951:7975:6ecf:eae5]) by Venus2.in.megatrends.com ([fe80::2002:4a07:4f17:c09b%14]) with mapi id 14.03.0248.002; Tue, 1 Sep 2020 20:19:17 +0530 From: "Sivaraman Nainar" To: "Rabeda, Maciej" , "devel@edk2.groups.io" Subject: Re: [edk2-devel] TCP Port for ISCSI Connection Thread-Topic: [edk2-devel] TCP Port for ISCSI Connection Thread-Index: AdZcMQrZhnonGfLbRHu342pRW6O7mQIeYm4wBrLOY4AAMSF5AAAMLfKg//+pt4D//6HGcA== Date: Tue, 1 Sep 2020 14:49:15 +0000 Message-ID: References: <16228C0E194D8DF1.2727@groups.io> <142a8a9f-fb6f-3bd1-2b8f-8e6888e09081@linux.intel.com> In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.0.0.181] MIME-Version: 1.0 X-TM-AS-GCONF: 00 X-TM-AS-Product-Ver: IMSVA-9.1.0.1817-8.6.0.1013-25638.007 X-TM-AS-Result: No--25.325-5.0-31-10 X-imss-scan-details: No--25.325-5.0-31-10 X-TMASE-Version: IMSVA-9.1.0.1817-8.6.1013-25638.007 X-TMASE-Result: 10--25.324600-10.000000 X-TMASE-MatchedRID: vWvnoyq7eMxbJCKOm3VRCUhcmj54ab4UJoKOQUqn/54mPFPgVMM3P9Br VWcP/4U9fPmUQQG69pxHQFjzAbvJEEFJjqTH4zXxGlbrk2ODhoOyyQInvLPk/BL5dheUDGATrpx Kw6iXQhawrpdl1VUSD8qtGqLtQ+lsGwKs3RUcsbiPiMW+3YzkgvchSLPSYNPJHJqAEQnJzjJ6Zx U6Cn9jnjwe897U/PjCtKV49RpAH3sZSo6PM4Lsil70lsqJNmceaSfKPLGWHubl3dqcxd4Oon6wP ec2/K0YePGAeSn124IdxBAG5/hkW0zzNX6FuGYDhgn72LMkncoRSB+McTz1ooQiFLyWqHtCOOco WEKA1AMqAObPkRRi5boBFlY6se+UzVE3gQTykCoohxHgu5jxflb9p6vyI+KCFXiEz+vIvVm/8J8 OKgGLVvy6nJnxadqoth8ie/2LVJXCRhoKDxcPh0Ev/8MqJVzOLT3TLaitHJ/7vFO+Ar9i5juhMQ JwyVlsOJQuSr/cFG6rhCEFTnVAD4VXe903O4U0M/fPG6YRJVHRGIcTaJXZtej9o0PMprXvyY+qc In8OnNAcBNjprrcipCB65RjRY3suxwruP+fgRTInKrwfonFC2kZ7sHaiCh7zubmDs6njS1BSbmJ D3drFROGhJ1r/lCClNomdZyIWKJ+tO36GYDlsvMqZZGHRQPVLSNJFDuOFuTficuMUwmy50mlX2s cVfePArfIDVjQDX7BtFDYGmaWKhrL4FDGAJ+FCwWRLqiC/UoSeB53z6WzWxk26uRmBZrWu9cQ6c 7hF6azhw/2vFDzln6Y5s54+e3K3kR1SkDo27+bKItl61J/yZUdXE/WGn0FHwAqApZ40aESsYwLh H7g0dbkrsq6X+UeRRgndEtDQrIUkaV0kwWnFo+Eus71oCNf3ZhB22pRt9s8TWuTuz9RZVgpWCbv a+Mm X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0 Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_B4DE137BDB63634BAC03BD9DE765F19702B4B466B5VENUS1inmegat_" --_000_B4DE137BDB63634BAC03BD9DE765F19702B4B466B5VENUS1inmegat_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Maciej, Thanks for the clarification. I agree with you. -Siva From: Rabeda, Maciej [mailto:maciej.rabeda@linux.intel.com] Sent: Tuesday, September 1, 2020 8:12 PM To: Sivaraman Nainar; devel@edk2.groups.io Subject: Re: [edk2-devel] TCP Port for ISCSI Connection Siva, iSCSI targets can be configured to listen on any TCP port. Changing the UEFI iSCSI Client's TargetPort min/max will effectively preve= nt the user from communicating with the targets configured to listen on por= ts outside that range (in your example: below 1024). I do not see a reason behind removing that flexibility. If user sets iSCSI= target and client ports to values shared by other services, it is that use= r's mistake. Thanks, Maciej On 01-Sep-20 16:31, Sivaraman Nainar wrote: Hello Maciej: The ports numbers from 0 to 1023 are having specific roles. Ex: 80 for HTTTP, 443 for HTTPS. In the case can we set Min as 1024 and Max as 65535. Thanks Siva From: devel@edk2.groups.io [mailto:devel@edk2= .groups.io] On Behalf Of Maciej Rabeda Sent: Tuesday, September 1, 2020 7:32 PM To: devel@edk2.groups.io; Sivaraman Nainar Subject: Re: [edk2-devel] TCP Port for ISCSI Connection Hi Siva, What seems to be the problem at hand? What kind of range of values for Tar= getPort do you propose? TARGET_PORT_MIN/MAX_NUM refer to a range of values (0-65535) that be set i= n TargetPort field in iSCSI HII. 3260 is a default TCP port for iSCSI. I see nothing wrong with that. Thanks, Maciej On 31-Aug-20 11:05, Sivaraman Nainar wrote: Rabeda: Could you please provide your comment on this. -Siva From: Sivaraman Nainar Sent: Tuesday, July 28, 2020 12:15 PM To: jiaxin.wu@intel.com Cc: devel@edk2.groups.io Subject: RE: TCP Port for ISCSI Connection Jiaxin: Can you please comment on the below query. -Siva From: devel@edk2.groups.io [mailto:devel@edk2= .groups.io] On Behalf Of Sivaraman Nainar Sent: Friday, July 17, 2020 5:39 PM To: devel@edk2.groups.io Cc: jiaxin.wu@intel.com Subject: [edk2-devel] Reg: TCP Port for ISCSI Connection Hello all: In the ISCSI driver, Target TCP Port Input shows the default port as 3260.= Which can be set from 0 to 65535 As per below RFC it talks about the Default Port only. Still it not clearl= y said if we can use the numbers 49152-65535 which is reserved. https://tools.ietf.org/html/rfc3720 13. IANA Considerations This section conforms to [RFC2434]. The well-known user TCP port number for iSCSI connections assigned by IANA is 3260 and this is the default iSCSI port. Implementations needing a system TCP port number may use port 860, the port assigned by IANA as the iSCSI system port; however in order to use port 860, it MUST be explicitly specified - implementations MUST NOT default to use of port 860, as 3260 is the only allowed default. with my understanding, it wouid be good if we can change the below Min and= MAX port number ranges with right ranges. #define TARGET_PORT_MIN_NUM 0 #define TARGET_PORT_MAX_NUM 65535 Thanks Siva This e-mail is intended for the use of the addressee only and may contain = privileged, confidential, or proprietary information that is exempt from di= sclosure under law. If you have received this message in error, please info= rm us promptly by reply e-mail, then delete the e-mail and destroy any prin= ted copy. Thank you. --_000_B4DE137BDB63634BAC03BD9DE765F19702B4B466B5VENUS1inmegat_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Maciej,

 

Thanks for the clarification. I agree with you.

 

-Siva

From: Rabeda, Maciej [mailto:maciej.rabeda@l= inux.intel.com]
Sent: Tuesday, September 1, 2020 8:12 PM
To: Sivaraman Nainar; devel@edk2.groups.io
Subject: Re: [edk2-devel] TCP Port for ISCSI Connection<= /p>

 

Siva,

iSCSI targets can be configured to listen on any TCP port.
Changing the UEFI iSCSI Client's TargetPort min/max will effectively preve= nt the user from communicating with the targets configured to listen on por= ts outside that range (in your example: below 1024).
I do not see a reason behind removing that flexibility. If user sets iSCSI= target and client ports to values shared by other services, it is that use= r's mistake.

Thanks,
Maciej

On 01-Sep-20 16:31, Sivaraman Nainar wrote:

Hello Maciej:<= o:p>

 

The ports numbers from 0 to 1023 are having specifi= c roles.

 

Ex: 80 for HTTTP, 443= for HTTPS.

 

In the case can we se= t Min as 1024 and Max as 65535.

 

Thanks

Siva

 

Hi Siva,

What seems to be the problem at hand? What kind of range of values for Tar= getPort do you propose?
TARGET_PORT_MIN/MAX_NUM refer to a range of values (0-65535) that be set i= n TargetPort field in iSCSI HII. 3260 is a default TCP port for iSCSI.
I see nothing wrong with that.

Thanks,
Maciej

On 31-Aug-20 11:05, Sivaraman Nainar wrote:

Rabeda:

 

Could you please prov= ide your comment on this.

 

-Siva

 

Jiaxin:

 

Can you please commen= t on the below query.

 

-Siva

From: devel@edk2.groups.io [mailto:= devel@edk2.groups.io] On Behalf Of Sivaraman Nainar
Sent: Friday, July 17, 2020 5:39 PM
To: devel@edk2.groups.io
Cc: jiaxin.wu@intel.com<= br> Subject: [edk2-devel] Reg: TCP Port for ISCSI Connection=

 

Hello all:

 

In the ISCSI driver, Target TCP Port Input shows th= e default port as 3260. Which can be set from 0 to 65535

 

As per below RFC it = talks about the Default Port only. Still it not clearly said if we can use = the numbers 49152-65535 which is reserved.

htt= ps://tools.ietf.org/html/rfc3720

13. IANA Considerations

This section conforms to [RFC2434].

The well-known user TCP port number for iSCSI connections assigned by
IANA is 3260 and this is the default iSCSI port. Implementations
needing a system TCP port number may use port 860, the port assigned
by IANA as the iSCSI system port; however in order to use port 860,
it MUST be explicitly specified - implementations MUST NOT default to
use of port 860, as 3260 is the only allowed default.

with my understanding, it wouid be good if we can change the below Min and=   MAX port number ranges with right ranges.

 

#define TARGET_PORT_MIN_NUM    =    0

#define TARGET_PORT_MAX_NUM    =    65535

 

Thanks

Siva

This e-mail is intended for the use= of the addressee only and may contain privileged, confidential, or proprie= tary information that is exempt from disclosure under law. If you have received this message in error, please inform us promptly by = reply e-mail, then delete the e-mail and destroy any printed copy. Thank yo= u.

 

 

--_000_B4DE137BDB63634BAC03BD9DE765F19702B4B466B5VENUS1inmegat_--