FC-PI-5, FC-FS-3, and 16GFC.ppt

FC-PI-5, FC-FS-3, and 16GFC FC-PI-5, FC-FS-3, and 16GFC bob.nixon@ T11/09-506v0 - 8/27/2009 * FC-PI-5, FC-FS-3, and 16GFC Hot Potatoes In the course of developing the 16GFC protocols, several things were determined to be out of scope for an FC-1/FC-2 standard So, we’re trying to dump them on FC-PI-x… T11/09-506v0 - 8/27/2009 * FC-PI-5, FC-FS-3, and 16GFC Bit Sync and Loss-of-Signal “Bit Synchronization is defined in FC-PI-x.” (FC-FS-3 6.2) “A receiver may provide a Loss-of-Signal check”, though it is optional (FC-FS-3 ) PI has always done that for us, please do the same for 16GFC. T11/09-506v0 - 8/27/2009 * FC-PI-5, FC-FS-3, and 16GFC Selection of Transmission Code “An FC-0 standard (e.g., FC-PI-5) may specify the use of the 8B/10B transmission code as its frame transfer transmission code.” (FC-FS-3 5.2.1) “An FC-0 standard (e.g., FC-PI-5) may specify the use of the 8B/10B transmission code as its frame transfer transmission code.” (FC-FS-3 5.3.1) This is new, there was never a choice before. FC-PI-5 should select 64B/66B for each physical variant that does NOT use 8B/10B. T11/09-506v0 - 8/27/2009 * FC-PI-5, FC-FS-3, and 16GFC If Transmission Code is 8B/10B “An FC-0 standard (e.g., FC-PI-5) may specify the use of Emission Lowering Protocol when using the 8B/10B transmission code.” (FC-FS-3 10.3.5) “An FC-0 standard (e.g., FC-PI-5) may specify the use of Frame Scrambling when using the 8B/10B transmission code.” (FC-FS-3 10.3.6) FC-PI-5 should select for each 8B/10B physical variant that uses it Frame Scrambling Emission Lowering Protocol (default is neither will be used) PI has been doing this for 8GFC, nothing new needed. T11/09-506v0 - 8/27/2009 * FC-PI-5, FC-FS-3, and 16GFC If Transmission Code is 64B/66B “An FC-0 standard (e.g., FC-PI-5) may specify the use of the Transmitter Training Signal….” (FC-FS-3 5.4.1) Implicitly, Speed Negotiation support depends on physical variant specs. I don’t think we have bothered to explicitly say yes or no per physical varian