public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ye, Ting" <ting.ye@intel.com>
To: Blibbet <blibbet@gmail.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: Iscsi Specification Document
Date: Thu, 24 Aug 2017 01:07:47 +0000	[thread overview]
Message-ID: <BC0C045B0E2A584CA4575E779FA2C12A1A93120B@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <9175ca21-33c6-106b-8ecc-b198f5492db8@gmail.com>

UEFI iSCSI is RFC3720 compatible. It is not updated yet.

Thanks,
Ting Ye

-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Blibbet
Sent: Thursday, August 24, 2017 5:23 AM
To: edk2-devel@lists.01.org
Subject: Re: [edk2] Iscsi Specification Document

On 08/23/2017 02:04 AM, Karunakar P wrote:
> Do we have any specific Document for Iscsi?
> Any document that describes the standard iscsi behavior.

I'm not aware of any 'design specification', that may be hoping for too much.

http://uefi.org/uefi points to 4 [i]SCSI-related URLs:

[RFC 3720] Internet Small Computer Systems Interface (iSCSI)

[RFC 4173] Bootstrapping Clients using the Internet Small Computer System Interface (iSCSI) Protocol

iSCSI Boot Firmware Table (iBFT)
http://www.microsoft.com/whdc/system/platform/firmware/ibft.mspx

SCSI Block Commands:
 http://www.t10.org

However this may be the best doc for UEFI iSCSI:
https://github.com/tianocore/edk2/search?utf8=%E2%9C%93&q=iscsi&type=

BTW, iSCSI is up to RFC 7143 these years, RFC 3720 is now OBSOLETE. I wonder if UEFI's iSCSI is RFC 7143-compatiable?
https://tools.ietf.org/html/rfc7143

HTH,
Thanks,
Lee Fisher
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel


      reply	other threads:[~2017-08-24  1:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-23  9:04 Iscsi Specification Document Karunakar P
2017-08-23 21:22 ` Blibbet
2017-08-24  1:07   ` Ye, Ting [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BC0C045B0E2A584CA4575E779FA2C12A1A93120B@SHSMSX104.ccr.corp.intel.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox