1、 IEEE Recommended Practice for Transport of Key Management Protocol (KMP) Datagrams Sponsored by the LAN/MAN Standards Committee IEEE 3 Park Avenue New York, NY 10016-5997 USA IEEE Computer Society IEEE Std 802.15.9-2016 IEEE Std 802.15.9-2016IEEE Recommended Practice for Transport of Key Management
2、 Protocol (KMP) DatagramsPrepared by the LAN/MAN Standards Committee of the IEEE Computer SocietyApproved 3 March 2016IEEE-SA Standards BoardThe Institute of Electrical and Electronics Engineers, Inc.3 Park Avenue, New York, NY 10016-5997, USACopyright 2016 by the Institute of Electrical and Electro
3、nics Engineers, Inc.All rights reserved. Published 17 August 2016. Printed in the United States of America.IEEE and 802 are registered trademarks in the U.S. Patent fitness for a particular purpose; non-infringement; and quality, accuracy, effectiveness, currency, or completeness of material. In add
4、ition, IEEE disclaims any and all conditions relating to: results; and workmanlike effort. IEEE standards documents are supplied “AS IS” and “WITH ALL FAULTS.”Use of an IEEE standard is wholly voluntary. The existence of an IEEE standard does not imply that there are no other ways to produce, test,
5、measure, purchase, market, or provide other goods and services related to the scope of the IEEE standard. Furthermore, the viewpoint expressed at the time a standard is approved and issued is subject to change brought about through developments in the state of the art and comments received from user
6、s of the standard. In publishing and making its standards available, IEEE is not suggesting or rendering professional or other services for, or on behalf of, any person or entity nor is IEEE undertaking to perform any duty owed by any other person or entity to another. Any person utilizing any IEEE
7、Standards document, should rely upon his or her own independent judgment in the exercise of reasonable care in any given circumstances or, as appropriate, seek the advice of a competent professional in determining the appropriateness of a given IEEE standard.IN NO EVENT SHALL IEEE BE LIABLE FOR ANY
8、DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO: PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TO
9、RT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE PUBLICATION, USE OF, OR RELIANCE UPON ANY STANDARD, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE AND REGARDLESS OF WHETHER SUCH DAMAGE WAS FORESEEABLE.Translations The IEEE consensus development process involves the review of
10、documents in English only. In the event that an IEEE standard is translated, only the English version published by IEEE should be considered the approved IEEE standard.IEEE Std 802.15.9-2016IEEE Recommended Practice for Transport of Key Management Protocol (KMP) Datagrams4Copyright 2016 IEEE. All ri
11、ghts reserved.Official statements A statement, written or oral, that is not processed in accordance with the IEEE-SA Standards Board Operations Manual shall not be considered or inferred to be the official position of IEEE or any of its committees and shall not be considered to be, or be relied upon
12、 as, a formal position of IEEE. At lectures, symposia, seminars, or educational courses, an individual presenting information on IEEE standards shall make it clear that his or her views should be considered the personal views of that individual rather than the formal position of IEEE. Comments on st
13、andardsComments for revision of IEEE Standards documents are welcome from any interested party, regardless of membership affiliation with IEEE. However, IEEE does not provide consulting information or advice pertaining to IEEE Standards documents. Suggestions for changes in documents should be in th
14、e form of a proposed change of text, together with appropriate supporting comments. Since IEEE standards represent a consensus of concerned interests, it is important that any responses to comments and questions also receive the concurrence of a balance of interests. For this reason, IEEE and the me
15、mbers of its societies and Standards Coordinating Committees are not able to provide an instant response to comments or questions except in those cases where the matter has previously been addressed. For the same reason, IEEE does not respond to interpretation requests. Any person who would like to
16、participate in revisions to an IEEE standard is welcome to join the relevant IEEE working group.Comments on standards should be submitted to the following address:Secretary, IEEE-SA Standards Board 445 Hoes Lane Piscataway, NJ 08854 USALaws and regulationsUsers of IEEE Standards documents should con
17、sult all applicable laws and regulations. Compliance with the provisions of any IEEE Standards document does not imply compliance to any applicable regulatory requirements. Implementers of the standard are responsible for observing or referring to the applicable regulatory requirements. IEEE does no
18、t, by the publication of its standards, intend to urge action that is not in compliance with applicable laws, and these documents may not be construed as doing so. CopyrightsIEEE draft and approved standards are copyrighted by IEEE under U.S. and international copyright laws.They are made available
19、by IEEE and are adopted for a wide variety of both public and private uses. These include both use, by reference, in laws and regulations, and use in private self-regulation, standardization, and the promotion of engineering practices and methods. By making these documents available for use and adop
20、tion by public authorities and private users, IEEE does not waive any rights in copyright to the docu-ments.Photocopies Subject to payment of appropriate fee, IEEE will grant users a limited, non-exclusive license to photocopy portions of any individual standard for company or organizational interna
21、l use or individual, non-commercial use only. To arrange for payment of licensing fees, 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 educational classroom use c
22、an also be obtained through the Copyright Clearance Center.IEEE Std 802.15.9-2016IEEE Recommended Practice for Transport of Key Management Protocol (KMP) Datagrams5Copyright 2016 IEEE. All rights reserved.Updating of IEEE Standards documentsUsers of IEEE Standards documents should be aware that thes
23、e documents may be superseded at any time by the issuance of new editions or may be amended from time to time through the issuance of amendments, corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of the document together with any amendments, corrig
24、enda, or errata then in effect. Every IEEE Standard is subject to review at least every ten years. When a document is more than ten years ole and has not undergone a revision process, it is reasonable to conclude that its contents although still of some value, do not wholly reflect the present state
25、 of the art. Users are cautioned to check to determine that they have the latest edition of any IEEE standard.In order to determine whether a given document is the current edition and whether it has been amended through the issuance of amendments, corrigenda, or errata, visit the IEEE-SA Website at
26、http:/ieee.org/publications_standards/index.html or contact IEEE at the address listed previously. For more information about the IEEE-SA or IEEEs standards development process, visit the IEEE-SA Website at http:/standards.ieee.org.ErrataErrata, if any, for this and all other standards can be access
27、ed at the following URL: http:/standards.ieee.org/findstds/errata/index.html. Users are encouraged to check this URL for errata periodically.PatentsAttention is called to the possibility that implementation of this standard may require use of subject matter covered by patent rights. By publication o
28、f this standard, no position is taken by the IEEE with respect to the existence or validity of any patent rights in connection therewith. If a patent holder or patent applicant has filed a statement of assurance via an Accepted Letter of Assurance, then the statement is listed on the IEEE-SA Website
29、 http:/standards.ieee.org/about/sasb/patcom/patents.html. Letters of Assurance may indicate whether the Submitter is willing or unwilling to grant licenses under patent rights without compensation or under reasonable rates, with reasonable terms and conditions that are demonstrably free of any unfai
30、r discrimination to applicants desiring to obtain such licenses.Essential Patent Claims may exist for which a Letter of Assurance has not been received. The IEEE is not responsible for identifying Essential Patent Claims for which a license may be required, for conducting inquiries into the legal va
31、lidity or scope of Patents Claims, or determining whether any licensing terms or conditions provided in connection with submission of a Letter of Assurance, if any, or in any licensing agreements are reasonable or non-discriminatory. Users of this standard are expressly advised that determination of
32、 the validity of any patent rights, and the risk of infringement of such rights, is entirely their own responsibility. Further information may be obtained from the IEEE Standards Association.IEEE Std 802.15.9-2016IEEE Recommended Practice for Transport of Key Management Protocol (KMP) Datagrams6Copy
33、right 2016 IEEE. All rights reserved.ParticipantsAt the time this standard was completed, the IEEE 802.15 working group had the following membership:IEEE 802.15 Working groupRobert F. Heile, Working Group ChairRick Alfvin, Working Group Vice-ChairPatrick Kinney, Working Group Vice-Chair, Working Gro
34、up SecretaryJames P. K. Gilb, Working Group Technical EditorBenjamin A. Rolfe, Working Group TreasurerRobert Moskowitz, 802.15.9 ChairPeter Yee, 802.15.9 Vice Chair, SecretaryEsko Vesala, 802.15.9 Technical EditorMajor contributions were received from the following individuals: Keiji AkiyamaHideki A
35、oyamaTuncer BaykasPhilip BeecherMonique BrownEdgar CallawayChris CalvertRadhakrishna CanchiJaesang ChaSoo-Young ChangClint ChaplinStephen ChaskoSangsung ChoiHee-Sang ChungHendricus De RuijterGuido DolmansAndrew EstradaDavid EvansKiyoshi FukuiTim GodfreyYoshiho GotoJussi HaapolaShinsuke HaraMarco Her
36、nandezKen HiragaJay HolcombKoji HorisakiIwao HosakoBing HuiYeong JangSeong-Soon JooVolker JungnickelJeritt KentJaehwan KimJunhyeong KimShoichi KitazawaTero KivinenRyuji KohnoFumihide KojimaKeitarou KondouThomas KuernerAmarjeet KumarByung-Jae KwakNamtuan LeJae LeeMoon-Sik LeeMyung LeeHuan-Bang LiLian
37、g LiMichael LynchItaru MaekawaHiroyuki MatsumuraMichael McInnisKenichi MoriMohammad NekouiChiu NgoTrang NguyenPaul NikolichMakoto NodaJohn NotorMitsuaki OshimaGlenn ParsonsCharles PerkinsAlbert PetrickClinton PowellVerotiana RabarijaonaDemir RakanovicIvan ReedeRichard RobertsNoriyuki SatoNorihiko Se
38、kineNikola SerafimovskiKunal ShahStephen ShellhammerShusaku ShimadaGary StuebingDon SturekMineo TakaiKou TogashiKiyoshi ToshimitsuBilly VersoBrian WeisHidetoshi YokotaYu ZengJunwen ZhangRiccardo BramaChris CalvertDavid EvansRene HummenPiotr KarockiToyoyuki KatoTero KivinenGlenn ParsonsVerotiana Raba
39、rijaonaBenjamin A. RolfeMichael SeamanKunal ShahShusaku ShimadaRene StruikAngela ThomasIEEE Std 802.15.9-2016IEEE Recommended Practice for Transport of Key Management Protocol (KMP) Datagrams7Copyright 2016 IEEE. All rights reserved.The following members of the balloting committee voted on this stan
40、dard. Balloters may have voted for approval, disapproval, or abstention. When the IEEE-SA Standards Board approved this standard on 4 March 2016, it had the following membership: Jean-Philippe Faure, ChairTed Burse, Vice ChairJohn D. Kulick, Past ChairKonstantinos Karachalios, Secretary*Member Emeri
41、tusRick AlfvinButch AntonPhilip BeecherHarry BimsGennaro BoggiaRiccardo BramaNancy BravinSusan BurgessWilliam ByrdJuan CarreonMinho CheongKeith ChowCharles CookSourav DuttaPeter EcclesineRichard EdgarLiu FangfangAvraham FreedmanDevon GayleJames P. K. GilbTim GodfreyRandall GrovesRobert F. HeileMarco
42、 HernandezWerner HoelzlTetsushi IkegamiNoriyuki IkeuchiAkio IsoAtsushi ItoRaj JainAdri JovinShinkyo KakuPiotr KarockiJeritt KentStuart KerryYongbum KimPatrick KinneyTero KivinenBruce KraemerYasushi KudohThomas KuriharaArthur H. LightElvis MaculubaEdward McCallMichael McInnisRobert MoskowitzMichael N
43、ewmanNick S. A. NikjooPaul NikolichJohn NotorYoshihiro OhbaSatoshi OyamaDalibor PokrajacClinton PowellVenkatesha PrasadVerotiana RabarijaonaKaren RandallMaximilian RiegelRobert RobinsonBenjamin A. RolfeBartien SayogoMichael SeamanKunal ShahShusaku ShimadaThomas StaraiRene StruikWalter StrupplerGeral
44、d StueveDon SturekMark SturzaMark-Rene UchidaLorenzo VangelistaDmitri VarsanofievRaj VaswaniGeorge VlantisKarl WeberHung-Yu WeiBrian WeisOren YueChuck AdamsMasayuki AriyoshiStephen DukesJianbin FanJ. Travis GriffithGary HoffmanRonald W. HotchkissMichael Janezic Joseph L. Koepfinger*Hung LingKevin Lu
45、Annette D. ReillyGary RobinsonMehmet UlemaYingli WenHoward WolfmanDon WrightYu YuanDaidi ZhongIEEE Std 802.15.9-2016IEEE Recommended Practice for Transport of Key Management Protocol (KMP) Datagrams8Copyright 2016 IEEE. All rights reserved.IntroductionKey management has been recognized as critical c
46、omponent for network security, but IEEE Std 802.15.4does not provide any methods for key management and leaves it out of scope. So this recommended practice was created to provide a methodology to enable key management by providing a transport for key management protocols (KMPs) outside the applicat
47、ion layers.This introduction is not part of IEEE Std 802.15.9-2016, IEEE Recommended Practice for Transport of Key Management Protocol (KMP) Datagrams.9Copyright 2016 IEEE. All rights reserved.IEEE Std 802.15.9-2016IEEE Recommended Practice for Transport of Key Management Protocol (KMP) DatagramsCon
48、tents1. Overview 121.1 Scope 121.2 Purpose. 122. Normative references. 133. Definitions, acronyms, and abbreviations 133.1 Definitions . 133.2 Acronyms and abbreviations . 134. Introduction 144.1 System view. 144.2 Network view. 164.3 Security associations 164.4 Process flow. 164.5 State machine. 16
49、4.6 Address formats . 174.7 KMP payload size 174.8 Format conventions 175. MPX data service. 175.1 Description. 175.2 MPX data primitives 185.2.1 MPX-DATA.request 215.2.2 MPX-DATA.confirm . 235.2.3 MPX-DATA.indication 245.3 MPX-PURGE primitives . 265.3.1 MPX-PURGE.request 265.3.2 MPX-PURGE.confirm . 276. KMP transport service . 286.1 KMP-CREATE primitives. 296.1.1 KMP-CREATE.request 306.1.2 KMP-CREATE.confirm 316.1.3 KMP-CREATE.indication . 316.1.4 KMP-CREATE.response . 326.2 KMP-FINISHED primitives 336.2.1 KMP-FINISHED.indication 336.3 KMP-DELETE primitives . 346.3.1 KM
