Template Version: @(#)onepager.txt 1.29 04/11/15 SMI

1. Introduction
   1.1. Project/Component Working Name:

	"SCSI SAS 1275 Binding"

   1.2. Name of Document Author/Supplier:

	CONRAD TURLIK
	
   1.3. Date of This Document:

	1/08/08

   1.4. Name of Major Document Customer(s)/Consumer(s):
	1.4.1. The PAC or CPT you expect to review your project:

		N/A

	1.4.2. The ARC(s) you expect to review your project:

		FWARC

	1.4.3. The Director/VP who is "Sponsoring" this project:

		mike.sanfratello@sun.com

	1.4.4. The name of your business unit:

		Common Software

   1.5. Email Aliases:
    	1.5.1. Responsible Manager:	gary.hethcoat@sun.com
    	1.5.2. Responsible Engineer:	conrad.turlik@sun.com
    	1.5.3. Marketing Manager:
	1.5.4. Interest List:

2. Project Summary
   2.1. Project Description:

	Device bindings for SCSI SAS controllers and devices.

   2.2. Risks and Assumptions:

        The binding is intended to be a living document, updated
        as necessary.

3. Business Summary
   3.1. Problem Area:

   	To date SAS controllers have only been directly attached to target
	devices.  The bindings in use are those for parallel SCSI devices and
	work decently in a configuration where there is a single serial link
	between the host adapter and target device.

	There are now several projects that incorporate SAS expanders.  A SAS
	expander allows a single SAS serial link to be used to communicate
	with multiple targets, as well as additional SAS expanders.  In a
	fabric of this sort the parallel SCSI device addressing scheme,
	designed to talk to at most 16 devices, breaks down, and a device
	cannot be guaranteed a specific "target ID" each time it's accessed.
	This can result in inconsistent behavior.

   3.2. Market/Requester:

	Sun is moving heavily into the SAS JBOD space with numerous projects
	such as Vela and Amber Road.  We need to address problems with the
	current implementations that will occur with the deployment of SAS
	expanders at customer sites.

   3.3. Business Justification:

	This is required to support SAS fabrics in a consistent manner.

   3.4. Competitive Analysis:

	N/A

   3.5. Opportunity Window/Exposure:

        The SAS device addressing scheme needs to be standardized.  This 
        must be done before we ship hardware that incorporate SAS expanders.

   3.6. How will you know when you are done?:

	The work will be completed when the prototype is implemented and
	the framework is approved by ARC.

4. Technical Description:
    4.1. Details:

        As noted in 3.1, we are currently shipping platforms that are 
        using the parallel scsi bindings for SAS adapter devices.  These 
        bindings will no longer be sufficient as our products begin
        incorporating SAS expanders. 

	Please refer to sas-bindings.txt in the case material directory
        for details.

    4.2. Bug/RFE Number(s):

	6616566 Enhance OBP to use WWID based addressing of SAS/SATA targets 
    
    4.3. In Scope:

        All future platforms that support SAS controllers.

    4.4. Out of Scope:

        The way SAS adapter devices define the SAS Address is out of scope.
    
    4.5. Interfaces:

	See interfaces-sas.txt in case materials directory.

    4.6. Doc Impact:

	Platform documentation describing SAS disk boot paths will need to
	be updated.
    
    4.7. Admin/Config Impact:

	These new bindings will change the format for platform boot paths.
    
    4.8. HA Impact:

	None.
    
    4.9. I18N/L10N Impact:

	None.
    
    4.10. Packaging & Delivery:

	None.
    
    4.11. Security Impact:

        None.

    4.12. Dependencies:

	This depends on the IEEE 1275 specification and the FWARC cases:
	   2005/751, SAS WWID determined from system MAC address
	   2006/035, LSI SAS Controller Methods for Manufacturing and Service

	Solaris drivers for SAS devices will need to be modified to recognize
	the new unit addresses.


5. Reference Documents:

	materials/sas-bindings.txt - bindings
        materials/interfaces - sas.txt
        http://t10.org/ftp/t10/drafts/sam4/sam4r13.pdf - SAS 1.1 spec
        http://t10.org/ftp/t10/drafts/sam4/sam4r13.pdf - SCSI Architecture Model 4
        http://t10.org/ftp/t10/drafts/sat/sat-r09.pdf - SCSI ATA Translation
        http://noho.eng/1275/practice/spi/spi1_0.ps - SCSI-3 Parallel Bindings

6. Resources and Schedule:
   6.1. Projected Availability:

	2/08.

   6.2. Cost of Effort:

	4 work weeks.	

   6.3. Cost of Capital Resources:

	N/A

   6.4. Product Approval Committee requested information:
   	6.4.1. Consolidation or Component Name:
	
		OpenBoot

	6.4.3. Type of CPT Review and Approval expected:

		
        6.4.4. Project Boundary Conditions:

	6.4.5. Is this a necessary project for OEM agreements:

		No.

	6.4.6. Notes:
	6.4.7. Target RTI Date/Release:

		OpenBoot 4.x  TBD

	6.4.8. Target Code Design Review Date:
	6.4.9. Update approval addition:

		N/A

   6.5. ARC review type:

		Normal

7. Prototype Availability:
   7.1. Prototype Availability:

        Now.

   7.2. Prototype Cost:

        2 work weeks