1、IEEE Std 1394.3-2003IEEE Standards1394.3TMIEEE Standard for a High PerformanceSerial Bus Peer-to-Peer DataTransport Protocol (PPDT)Published by The Institute of Electrical and Electronics Engineers, Inc.3 Park Avenue, New York, NY 10016-5997, USA14 April 2004IEEE Computer SocietySponsored by theMicr
2、oprocessor and Microcomputer Standards CommitteeIEEE StandardsPrint: SH95173PDF: SS95173IEEE Std 1394.3-2003 (R2008)IEEE Standard for a High Performance Serial Bus Peer-to-Peer Data Transport Protocol (PPDT)SponsorMicroprocessor and Microcomputer Standards Committeeof theIEEE Computer SocietyReaffir
3、med 10 December 2008Approved 11 September 2003IEEE-SA Standards BoardApproved 29 January 2004American National Standards InstituteRecognized as anAmerican National Standard (ANSI)The Institute of Electrical and Electronics Engineers, Inc.3 Park Avenue, New York, NY 10016-5997, USACopyright 2004 by t
4、he Institute of Electrical and Electronics Engineers, Inc.All rights reserved. Published 14 April 2004. Printed in the United States of America.Print:ISBN 0-7381-3820-7 SH95173PDF:ISBN 0-7381-3821-5 SS95173No part of this publication may be reproduced in any form, in an electronic retrieval system o
5、r otherwise, without the prior written permission of the publisher.Abstract:This standard denes a peer-to-peer data transport (PPDT) protocol between Serial Busdevices that implement Serial Bus Protocol 2 (SBP-2). The facilities specied include device andservice discovery, self-congurable (plug and
6、play) binding, and connection management.Keywords: computers, CSR architecture, connect, peer-to-peer, SBP-2, transport protocolIEEE Standardsdocuments are developed within the IEEE Societies and the Standards Coordinating Committees of theIEEE Standards Association (IEEE-SA) Standards Board. The IE
7、EE develops its standards through a consensusdevelopment process, approved by the American National Standards Institute, which brings together volunteers representingvaried viewpoints and interests to achieve the nal product. Volunteers are not necessarily members of the Institute andserve without c
8、ompensation. While the IEEE administers the process and establishes rules to promote fairness in theconsensus development process, the IEEE does not independently evaluate, test, or verify the accuracy of any of theinformation contained in its standards.Use of an IEEE Standard is wholly voluntary. T
9、he IEEE disclaims liability for any personal injury, property or other dam-age, of any nature whatsoever, whether special, indirect, consequential, or compensatory, directly or indirectly resultingfrom the publication, use of, or reliance upon this, or any other IEEE Standard document.The IEEE does
10、not warrant or represent the accuracy or content of the material contained herein, and expressly disclaimsany express or implied warranty, including any implied warranty of merchantability or tness for a specic purpose, or thatthe use of the material contained herein is free from patent infringement
11、. IEEE Standards documents are supplied “AS IS.”The existence of an IEEE Standard does not imply that there are no other ways to produce, test, measure, purchase, market,or provide other goods and services related to the scope of the IEEE Standard. Furthermore, the viewpoint expressed at thetime a s
12、tandard is approved and issued is subject to change brought about through developments in the state of the art andcomments received from users of the standard. Every IEEE Standard is subjected to review at least every ve years for revi-sion or reafrmation. When a document is more than ve years old a
13、nd has not been reafrmed, it is reasonable to concludethat its contents, although still of some value, do not wholly reect the present state of the art. Users are cautioned to checkto determine that they have the latest edition of any IEEE Standard.In publishing and making this document available, t
14、he IEEE is not suggesting or rendering professional or other servicesfor, or on behalf of, any person or entity. Nor is the IEEE undertaking to perform any duty owed by any other person orentity to another. Any person utilizing this, and any other IEEE Standards document, should rely upon the advice
15、 of a com-petent professional in determining the exercise of reasonable care in any given circumstances.Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to specicapplications. When the need for interpretations is brought to the attention
16、 of IEEE, the Institute will initiate action to prepareappropriate responses. Since IEEE Standards represent a consensus of concerned interests, it is important to ensure that anyinterpretation has also received the concurrence of a balance of interests. For this reason, IEEE and the members of itss
17、ocieties and Standards Coordinating Committees are not able to provide an instant response to interpretation requestsexcept in those cases where the matter has previously received formal consideration. Comments for revision of IEEE Standards are welcome from any interested party, regardless of membe
18、rship afliation withIEEE. Suggestions for changes in documents should be in the form of a proposed change of text, together with appropriatesupporting comments. Comments on standards and requests for interpretations should be addressed to:Secretary, IEEE-SA Standards Board445 Hoes LaneP.O. Box 1331P
19、iscataway, NJ 08855-1331USAAuthorization to photocopy portions of any individual standard for internal or personal use is granted by the Institute ofElectrical and Electronics Engineers, Inc., provided that the appropriate fee is paid to Copyright Clearance Center. Toarrange for payment of licensing
20、 fee, please contact Copyright Clearance Center, Customer Service, 222 Rosewood Drive,Danvers, MA 01923 USA; +1 978 750 8400. Permission to photocopy portions of any individual standard for educationalclassroom use can also be obtained through the Copyright Clearance Center.Note: Attention is called
21、 to the possibility that implementation of this standard may require use of subject mat-ter covered by patent rights. By publication of this standard, no position is taken with respect to the existence orvalidity of any patent rights in connection therewith. The IEEE shall not be responsible for ide
22、ntifying patentsfor which a license may be required by an IEEE standard or for conducting inquiries into the legal validity orscope of those patents that are brought to its attention.ivCopyright 2004 IEEE. All rights reserved.IntroductionThis introduction is not part of IEEE Std 1394.3-2003, IEEE St
23、andard for a High Performance Serial Bus Peer-to-Peer Data Transport Protocol (PPDT).The IEEE approved P1394.3 on 30 January 2000 at the request of Gregory LeClair, former Chair of the 1394Printer Working Group (PWG), an informal industry consortium. Although nal approval of this standardhas taken p
24、lace under the aegis of the IEEE, most of the signicant effort occurred prior to the formation ofthe P1394.3 working group.The necessity for a Serial Bus transport protocol for printers and similar devices was rst broached in hall-way conversation at the quarterly meeting of the 1394 Trade Associati
25、on in Redmond, WA, in October,1996. This lead to a “birds of a feather” assembly hosted at Adobe Systems in San Jose, CA, on 6 December1996. The attendees at this crowded gathering discussed the suitability of existing protocols, particularlySBP-2, and the venue for the proposed standards work. The
26、group concluded that no existing protocol suitedtheir needs: one would have to be developed. Don Wright offered the services of the PWG, an ad hoc indus-try forum whose principal participants are printer vendors, and Greg LeClair wrote the initial charter for thegroup.The rst ofcial meeting of the 1
27、394 PWG was held in Albuquerque, NM, early in 1997. Consensus wasquickly reached that the new protocol must be friendly to legacy data formats; this exposed the two majorareas that occupied the working group for the next three years: a) device discovery and enumeration, and b)a data transport protoc
28、ol.The working group examined the facilities of IEEE Std 1394-1995 and the CSR architecture and concludedthat conguration ROM might permit practical solutions for device discovery but that the current standard,ISO/IEC 13213:1994, did not adequately specify the necessary building blocks. The 1394 PWG
29、 applied tothe IEEE Microprocessor and Microcomputer Standards Committee (MMSC) for a project authorizationrequest (PAR) to commence new work. Simultaneously, the CSR architecture was due for revision and theMMSC approved a PAR for IEEE P1212 now approved and published as IEEE Std 1212-2001, IEEESta
30、ndard for a Control and Status Registers (CSR) Architecture for Microcomputer Buses and suggested tothe 1394 PWG that work be transferred to the IEEE. In fact, many participants became simultaneously activein the IEEE P1212 working group and provided strong continuity between the two complementary e
31、fforts.With work on device discovery split off to IEEE P1212, the 1394 PWG was free to focus its efforts on thetransport protocol. There were two principal candidates, SBP-2 and the “thin” protocol jointly developed bycamera and printer companies in Japan. No matter which protocol (or adaptation the
32、reof) was ultimatelychosen, the 1394 PWG thought it was important to recognize the peer-to-peer nature of the desired operatingenvironment. The working group concluded that a solution similar to the “sockets” API that supported con-rmed, efcient bi-directional data delivery between peers would suit
33、their needs. Close to a year was spentdebating the pros and cons of different approaches. In the end, the group converged on Serial Bus Protocol 2(SBP-2) as the underlying mechanism: the 1394 PWG would focus its efforts on enhancements to SBP-2 torender it more fully peer-to-peer.Once the selection
34、of an underlying protocol was agreed, work progressed fairly quickly on what was even-tually dubbed peer-to-peer data transport (PPDT) protocol. The prototype efforts expended by some earlyadopters, both in Japan and the United States, have been invaluable in the resolution of detailed technicalques
35、tions that arose as this standard was rened. In particular, the essential mechanisms rst proposed as theSimple High Performance Transport (SHPT) were ultimately adopted. SHPT took advantage of the SBP-2unordered execution model to provide independent, bi-directional data transport within the context
36、 of a sin-gle SBP-2 login. SHPT also optimized error recovery operations after bus reset by using execution contextinformation known by both initiator and target.Copyright 2004 IEEE. All rights reserved.vTowards the end of summer 1999, it was apparent that the work neared conclusion; at this time th
37、e workinggroup discussed possible homes for the draft standard and agreed upon the IEEE as the best choice.Patent noticeAttention is called to the possibility that implementation of this standard may require use of subject mattercovered by patent rights. By publication of this standard, no position
38、is taken with respect to the existence orvalidity of any patent rights in connection therewith. The IEEE shall not be responsible for identifying allpatents for which a license may be required by an IEEE standard or for conducting inquiries into the legalvalidity or scope of those patents that are b
39、rought to its attention.The patent holder has, however, led a statement of assurance that it will grant a license under these rightswithout compensation or under reasonable rates and nondiscriminatory, reasonable terms and conditions toall applicants desiring to obtain such a license. The IEEE makes
40、 no representation as to the reasonablenessof rates and/or terms and conditions of the license agreement offered by the patent holder. Contact informa-tion may be obtained from the IEEE Standards Department.ParticipantsThe following is a list of active participants in the IEEE 1394.3 working group (
41、those who attended morethan three meetings from original inception of the predecessor 1394 Printer Working Group activity to thetime of publication).Gregory LeClair,ChairAlan Berkema,Vice ChairPeter Johansson,EditorLee Farrell,Co-secretaryLarry Stein,Co-secretaryThe following members of the ballotin
42、g committee voted on this standard. Balloters may have voted forapproval, disapproval, or abstention. Brian BatchelderScott BonarMike FenelonDoug FritzJohn FullerOsamu HirataTakashi IsodaLaurie LassloBob MorfordFumio NagasakaBrian NagyAtsushi NakamuraKazuo NomuraCharles RiceFumio SamitsuYuji SasakiH
43、itoshi SekineAkihiro ShimuraNobuhiko ShinodaGreg ShueJerry ThrasherRandy TurnerShigeru UedaRainier WolfcastleDon WrightEdmund H. BaulsirAlan BerkemaLon CanadayKeith ChowSourav K. DuttaEdwin Vivian El-KarehLee FarrellMichael A. FischerJohn FullerClay E. HudginsPeter JohanssonThomas M. KuriharaConrad
44、A. LaurvickGregory LeClairJoseph R. MarshallGene E. MilliganKlaus-Dieter MuellerAtsushi NakamuraRobert OHaraRoman OrzolCharles RiceGary S. RobinsonJaideep RoyAkihiro ShimuraGary K. SloaneLarry SteinMichael TeenerJerry ThrasherColin Whitby-StrevensDon WrightOren YuenJanusz ZalewskiviCopyright 2004 IE
45、EE. All rights reserved.The following individuals served on the ballot response committee: When the IEEE-SA Standards Board approved this standard on 11 September 2003, it had the followingmembership:Don Wright,ChairHoward M. Frazier,Vice ChairJudith Gorman,Secretary*Member EmeritusAlso included are
46、 the following nonvoting IEEE-SA Standards Board liaisons:Alan Cookson, NIST RepresentativeSatish K. Aggarwal, NRC RepresentativeAndrew IckowiczIEEE Standards Project EditorBrian BatchelderAlan BerkemaLon CanadayLee FarrellMike FenelonPeter JohanssonFumio NagasakaAkihiro ShimuraJerry ThrasherDon Wri
47、ghtH. Stephen BergerJoe BruderBob DavisRichard DeBlasioJulian Forster*Toshio FukudaArnold M. GreenspanRaymond HapemanDonald M. HeirmanLaura HitchcockRichard H. HulettAnant JainLowell G. JohnsonJoseph L. Koepnger*Tom McGeanSteve MillsDaleep C. MohlaWilliam J. MoylanPaul NikolichGary RobinsonMalcolm V
48、. ThadenGeoffrey O. ThompsonDoug ToppingHoward L. WolfmanCopyright 2004 IEEE. All rights reserved.viiContents1. Overview 11.1 Scope 11.2 Purpose. 12. References 23. Definitions, abbreviations, and notation 23.1 Definitions 23.2 Abbreviations. 63.3 Notation 64. Model (informative). 84.1 Protocol stac
49、k and service model. 84.2 Independent data paths for each service 94.3 Connection management 104.4 Data transfer between initiator and target 114.5 Control requests and responses 124.6 Unsolicited status. 134.7 Reverse login and logout . 135. Data structures . 145.1 Transport flow ORBs. 145.2 Status block 155.3 Control information . 175.4 Queue information . 205.5 Reverse login request and response .216. Control operations 236.1 Login, reverse login and queue zero236.2 Autonomous response information 246.3 Connection management 256.4 Queue status info
