《EIA-SP-4998-2002.pdf》由会员分享,可在线阅读,更多相关《EIA-SP-4998-2002.pdf(60页珍藏版)》请在三一文库上搜索。
1、 June 7, 2002 SUBJECT: Standards Proposal No. 4998, Proposed Upgrade of EIA/CEA-852 “Tunneling Component Network Protocols Over Internet Protocol Channels” (if approved, to be published as ANSI/EIA/CEA-852). BACKGROUND: The attached material was approved by R-7.1 HCS-1. SP-4998 is herewith submitted
2、 for ANSI public review as a step toward standardization. NOTE: Please provide the following information for your comment(s). Number each comment if they encompass both editorial and technical. Company Name- Comment No. Type of Comment- Technical or Editorial Reference- Page No., Clause No., Line Su
3、ggested Change- Change From:. To:. Add:, Delete: Rationale for Technical Change COMMENT PERIOD EXPIRES: August 7, 2002 Prior to this date, as a public comment submitter, you may forward your comments to the designated EIA contact noted below. Following the expiration of the comment period, this Stan
4、dards Proposal will be submitted to the EIA Technology Strategy OR; 2. Fax your comments, prior to the deadline, to: 703-907-7693. Include this form with your signature Fax 703 907 7693; Email smcgeehance.org COMMENT PERIOD EXPIRES: August 7, 2002 Each comment submission should indicate either: _ I
5、am providing the attached technical comments concerning standardization of the contents of SP-4998 as an American National Standard, and recommend that the attached, along with the reason(s) for making the recommendation, be considered by R-7.1 HCS-1. _ I am providing the attached editorial comments
6、 concerning standardization of the contents of SP-4998 as an American National Standard, and recommend that the attached, along with the reason(s) for making the recommendation, be considered by R-7.1 HCS-1. DATE:_ NAME:_ Please Print TEL:_ NAME:_ Signature E-MAIL_ COMPANY_ _ ADDRESS_ _ -page 2- Cop
7、yright Electronic Industries Alliance Provided by IHS under license with EIALicensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 03/30/2007 20:39:29 MDTNo reproduction or networking permitted without license from IHS -,-,- NOTICE This document is an EIA Engineering Standards Proposal
8、, rather than an interim or final Standard. It is published for purposes of comment and is subject to further review and modification by the Technology Strategy & Standards Department, which may accept or reject the Standards Proposal. Accordingly, readers of this Standards Proposal are cautioned ag
9、ainst relying on information contained therein prior to the adoption of a final standard. EIA disclaims any liability or responsibility for the consequences of such reliance. Published by ELECTRONIC INDUSTRIES ALLIANCE 2002 Technology Strategy & Standards Department 2500 Wilson Boulevard Arlington,
10、VA 22201 All rights reserved Printed in U.S.A. PRICE: $70.00 Copyright Electronic Industries Alliance Provided by IHS under license with EIALicensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 03/30/2007 20:39:29 MDTNo reproduction or networking permitted without license from IHS -,-
11、,- Copyright Electronic Industries Alliance Provided by IHS under license with EIALicensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 03/30/2007 20:39:29 MDTNo reproduction or networking permitted without license from IHS -,-,- SP-4998 EIA/CEA-852 1 FOREWORD This standard was develo
12、ped under the auspices of the CEA Engineering R-7 Home Networking Committee. Copyright Electronic Industries Alliance Provided by IHS under license with EIALicensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 03/30/2007 20:39:29 MDTNo reproduction or networking permitted without lice
13、nse from IHS -,-,- SP-4998 EIA/CEA-852 ii Copyright Electronic Industries Alliance Provided by IHS under license with EIALicensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 03/30/2007 20:39:29 MDTNo reproduction or networking permitted without license from IHS -,-,- SP-4998 EIA/CEA-
14、852 iii CONTENTS Tunneling Device Area Network Protocols Over Internet Protocol Channels.1 1 Definitions.1 2 Introduction.2 3 Requirements3 4 DAN/IP Device Specification4 5 IP Channel Specification5 5.1 IP Transport Mechanisms 7 6 DAN/IP Device Configuration 9 6.1 Configuration Parameters9 6.1.1 Cha
15、nnel Definition Parameters.10 6.1.2 Send List Parameters10 6.1.3 Device Parameters.10 6.2 Configuration Techniques .11 6.2.1 Manual Configuration11 6.2.2 BOOTP and DHCP11 6.2.3 Configuration Servers.11 7 DAN/IP Messages and Modes of Operation.12 7.1 Common Message Header.12 7.2 Packet Segmentation13
16、 7.2.1 Overview.13 7.2.2 Segment Exchange14 7.2.3 Discussion15 7.3 Data Packet Exchange16 7.3.1 Out of Order Packets.17 7.3.2 Duplicate Packet Detection.18 7.3.3 Stale Packet Detection 18 7.4 Configuration Server Interactions.19 7.4.1 General Device Interaction19 7.4.2 General Protocol Interaction.2
17、1 7.4.3 Packet Segmentation.21 7.4.4 Device Registration .22 7.4.5 Channel Membership 24 7.4.6 Send List.24 7.4.7 Channel Routing25 7.5 Miscellaneous Status Messages .27 7.5.1 DAN/IP Device Status 27 7.5.2 Device Configuration.29 7.5.3 Device Send List29 7.5.4 Channel Membership List.29 7.5.5 Channe
18、l Routing Information.30 7.6 Vendor Specific Messages.30 8 Packet Formats.32 8.1 Packet Types .32 8.2 Common DAN/IP Header 33 Copyright Electronic Industries Alliance Provided by IHS under license with EIALicensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 03/30/2007 20:39:29 MDTNo
19、reproduction or networking permitted without license from IHS -,-,- SP-4998 EIA/CEA-852 iv 8.3 Segment Packet 35 8.4 DAN Data Packets.36 8.5 DAN/IP Device Registration/Configuration Packets36 8.6 Channel Membership Packet.39 8.7 Channel Routing Packet.40 8.8 Request Packet .43 8.9 Acknowledge Packet
20、.44 8.10 Send List Packet .45 8.11 Node Status/Health/Statistics Response Message45 9 Annex A Specifications for EIA-709 (Normative).48 10 Annex B Specifications for EIA-709 (Informative) .49 11 Annex A Specifications for EIA-600 (Normative).49 12 Annex A Specifications for EIA-600 (Informative) .49
21、 13 References 50 Copyright Electronic Industries Alliance Provided by IHS under license with EIALicensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 03/30/2007 20:39:29 MDTNo reproduction or networking permitted without license from IHS -,-,- SP-4998 EIA/CEA-852 v Figures Figure 1.
22、Typical DAN/IP Application.3 Figure 2. IP Protocol Stack .8 Figure 3. Packet Bunching13 Copyright Electronic Industries Alliance Provided by IHS under license with EIALicensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 03/30/2007 20:39:29 MDTNo reproduction or networking permitted w
23、ithout license from IHS -,-,- SP-4998 EIA/CEA-852 vi Tables Table 1. Device Registration with Configuration Server Protocol 23 Table 2. Server to Device Unsolicited Configuration Message Protocol23 Table 3. Device to Server Channel Membership Request Protocol24 Table 4. Device to Server Send List Re
24、quest Protocol.25 Table 5. Device to Server Channel Routing Update Protocol26 Table 6. Device to Server Channel Routing Request Protocol26 Table 7. Protocol for Requesting a Devices Configuration 29 Table 8. Protocol for Requesting a Devices Send List29 Table 9. Protocol for Requesting a Devices Cha
25、nnel Definition 29 Table 10. Protocol for Requesting a Devices Channel Routing Information 30 Table 11. Message Type Cross Reference.33 Table 12. Common Packet Header Format 33 Table 13. Segment Packet Format35 Table 14. Data Packet Format .36 Table 15. Device Registration/Configuration Packet Forma
26、t.37 Table 16. Channel Membership Packet Format.40 Table 17. Channel Routing Packet Formats41 Table 18. Configuration Request Packet Format43 Table 19. Request Reason Codes.43 Table 20. Request Amount Codes43 Table 21. Request Action Codes.44 Table 22. Acknowledge Packet Formats44 Table 23. Send Lis
27、t Packet Format.45 Table 24. Node Status/Health/Statistics Response Message 47 Copyright Electronic Industries Alliance Provided by IHS under license with EIALicensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 03/30/2007 20:39:29 MDTNo reproduction or networking permitted without li
28、cense from IHS -,-,- SP-4998 EIA/CEA-852 1 Tunneling Component Network Protocols Over Internet Protocol Channels 1 Definitions The key words “MUST“, “MUST NOT“, “REQUIRED“, “SHALL“, “SHALL NOT“, “SHOULD“, “SHOULD NOT“, “RECOMMENDED“, “MAY“, and “OPTIONAL“ in this document are to be interpreted as de
29、scribed in RFC 2119 10. A Component Network (CN) is a network of nodes (devices) that are capable of computing, sensing, and actuating. Typically these devices are used for control and telemetry purposes including applications such as HVAC, security, energy management, machine control, etc. These de
30、vices are typically not used for data processing or general purpose computing purposes. Some of the characteristics of CNs that set them apart from traditional data networks include: Typically lower bandwidth requirements. Small packet/message sizes. Tighter constraints on message reliability and de
31、livery latencies. A number of existing standards apply to networks of this type including EIA-709 2 and EIA-600 11. Tunneling refers to the encapsulation of one protocols packet within the payload of another protocols packets. The Internet Protocol (IP) is a packet switched protocol that allows netw
32、orks to be built that consist of a loose confederation of hosts that can communicate over a wide range of physical media and topologies to exchange data. Refer to 7. A channel refers to the common communications transport mechanism that a specific collection of CN devices share and communicate over
33、without the use of a router. Channels are used to transport CN packets below the link layer of the CN protocol stack. Typically this refers to some type of physical media such as power line, RF, or twisted pair, but in the case of IP networks this channel is not physical, but a protocol tunnel. A CN
34、 device is considered to be any device that uses the CN protocol to communicate with other CN devices. Specifically a CN/IP device is a CN device that communicates with other CN devices over an IP channel. A CN router is special type of CN device that routes CN protocol packets between two or more c
35、hannels. Specifically a CN/IP router is a CN router in which at least one of the channels it routes packets over is an IP channel. A CN node is special type of CN device that can send or receive CN protocol packets, but does not route them between channels. Specifically a CN/IP node is a CN node in
36、which at least one of the channels it sends and receives packets over is an IP channel. All CN devices are either routers, nodes or both. A CN group is a collection of CN devices that share a common multicast address. The Address Resolution Protocol (ARP) is a TCP/IP protocol used to convert an IP a
37、ddress into a physical address such as an Ethernet address. A host wishing to obtain a physical address Copyright Electronic Industries Alliance Provided by IHS under license with EIALicensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 03/30/2007 20:39:29 MDTNo reproduction or networ
38、king permitted without license from IHS -,-,- SP-4998 EIA/CEA-852 2 broadcast an ARP request onto the TCP/IP network. The host on the network that has the IP address in the request then replies with its physical hardware address. There is also Reverse ARP (RARP) that can be used by a host to discove
39、r its IP address. In this case, the host broadcasts its physical address and a RARP server replies with the hosts IP address. The Internet Control Message Protocol (ICMP), is an extension to the Internet Protocol (IP) IP defined by RFC 792. ICMP supports packet containing error, control, and informa
40、tional messages. The PING command, for example, uses ICMP to test an Internet connection. Internet Group Management Protocol (IGMP) is defined in RFC 1112 as the standard for IP multicasting in the Internet. Its used to establish host memberships in particular multicast groups on a single network. T
41、he mechanisms of the protocol allow a host to inform its local router, using Host Membership Reports, that it wants to receive messages addressed to a specific multicast group. All hosts conforming to level 2 of the IP multicasting specification require IGMP. A domain is a group of computers and dev
42、ices on a network that are administered as a unit with common rules and procedures. Domains are defined by an address referred to as the “domain address“. Different network protocols specify the domain address in different ways. A subnet is a portion of a network that shares a common address compone
43、nt known as the “subnet address“. Different network protocols specify the subnet address in different ways. A node ID is a logical network address that differentiates nodes within the same subnet or domain. A unique ID is a network address that is globally unique. No two nodes anywhere can share the
44、 same unique ID. Data Skew refers to the situation that exists when a data set that forms the basis for a message changes while the message is in the course of being transmitted to another device. The term MBZ in protocol fields stands for Must Be Zero. This stands for a reserved field that may be u
45、sed in following versions of the protocol. Such fields shall be sent as zero and ignored by the receiver in implementations conforming to the current version of the specification. 2 Introduction This document provides specifications for the transporting of Component Network (CN) packets over Interne
46、t Protocol (IP) networks using a tunneling mechanism wherein the CN packets are encapsulated within the IP packets. It applies to both CN nodes and CN routers. The purpose of this specification is to insure interoperability between various CN devices that wish to use IP networks to communicate using
47、 a particular CN protocol. The specification is intended to be general enough to handle a wide range of CN protocols. In particular this specification will cover the following standard CN protocols: EIA-709 2 EIA-600 11 The main body of this specification is independent of the CN protocol being transported over the IP network. The reader is directed to Annex A and Annex B for the normative and informative, respectively, aspects of this specification that are specific
链接地址:https://www.31doc.com/p-3754702.html