1、 Reference numberECMA-123:2009Ecma International 2009ECMA-393 2ndEdition / June 2012 proxZZZy for sleeping hosts proxZzzyis the registered Community Trade Mark of Ecma International (No 008849606). COPYRIGHT PROTECTED DOCUMENT Ecma International 2012 Ecma International 2012 iContents Page 1 Scope 1
2、2 Conformance . 1 3 Normative references 2 4 Terms and definitions . 3 5 Proxy Usage of Protocols (informative) 3 5.1 Basic Architecture . 3 5.2 Ethernet (IEEE 802.3) 3 5.3 Wireless LAN (IEEE 802.11) 4 5.4 Dynamic Host Configuration Protocol (DHCP). 4 5.5 Internet Protocol v4 Basic Framework (IPv4)
3、. 4 5.5.1 ARP Address Resolution Protocol . 4 5.5.2 Link Local Auto-IP Address Allocation . 5 5.5.3 IPv4 Address Conflict Detection 5 5.5.4 IGMP Internet Group Management Protocol 5 5.5.5 UDP User Datagram Protocol 5 5.5.6 TCP Transmission Control Protocol 5 5.5.7 DNS Domain Name System . 5 5.6 Inte
4、rnet Protocol v6 Basic Framework (IPv6) . 5 5.6.1 MLD Multicast Listener Discovery 6 5.7 Remote Access using SIP and IPv4 6 5.8 Remote Access using Teredo for IPv6 7 5.9 SNMP 7 5.10 Service Discovery using mDNS . 7 5.11 Name Resolution with LLMNR . 7 5.12 Wake Packets . 7 6 Basic Framework Protocols
5、 . 8 6.1 Ethernet 802.3 (Option) . 8 6.1.1 Configuration Data 8 6.1.2 Behavioural Requirements . 8 6.2 WiFi 802.11 (Option) 8 6.2.1 Configuration Data 8 6.2.2 Behavioural Requirements . 9 6.3 ARP . 10 6.3.1 Configuration Data 10 6.3.2 Behavioural Requirements . 11 6.4 Neighbour Discovery 11 6.4.1 Co
6、nfiguration Data 11 6.4.2 Behavioural Requirements . 11 6.5 Wake Packets . 12 6.5.1 Configuration Data 12 6.5.2 Behavioural Requirements . 12 7 Proxy Configuration and Management . 12 7.1 Configuration Data 13 7.2 Behavioural Requirements . 13 7.2.1 Returned Data (Option) . 13 8 Options . 14 8.1 IGM
7、P Multicast (Option) 14 8.1.1 Configuration Data 14 ii Ecma International 20128.1.2 Behavioural Requirements .14 8.2 DHCP Address Allocation (Option) 14 8.2.1 Configuration Data.14 8.2.2 Behavioural Requirements .15 8.3 Remote Access using SIP and IPv4 (Option) 15 8.3.1 Behavioural Requirements .16
8、8.4 Remote Access using Teredo for IPv6 16 8.4.1 Data Configuration.17 8.4.2 Behavioural Requirements .17 8.5 Simple Network Management Protocol (SNMP) .17 8.5.1 Configuration Data.17 8.5.2 Behavioural Requirements .18 8.6 Service Discovery using mDNS .18 8.6.1 Configuration Data.18 8.6.2 Behavioura
9、l Requirements .18 8.7 Name Resolution with LLMNR 21 8.7.1 Configuration Data.21 8.7.2 Behavioural Requirements .21 Annex A (normative) System Considerations 23 A.1 AC and DC Power Mode 23 A.2 Security Considerations .23 Annex B (informative) Protocols Considered but not included .25 B.1 SNMPv3 .25
10、B.2 UPnP .25 Bibliography 27 Ecma International 2012 iiiIntroduction Large amounts of electricity are used by electronic devices that are on solely for the purpose of maintaining network connectivity while they might otherwise be asleep. The computation required to stay connected is small, but these
11、 devices have large power differences between their on and sleep modes; thus, most of this energy use is wasted. Billions of dollars per year of electricity (and consequent carbon emissions) could be saved by widespread use of a “network proxy” for devices like PCs, printers, game consoles and set-t
12、op boxes. A low-power proxy handles key network tasks for a high-power device, thus allowing the high-power device to sleep when not in active use. In 2008, the Energy Star program identified preying in its Computer Specification, version 5.0, as a technology with substantial energy saving potential
13、. The standard designates that a “platform-independent industry standard” will specify the behaviour of a qualifying proxy. It is expected that this document will be that standard. This Standard provides an overall architecture for a proxy and key requirements for preying select protocols. Handling
14、of incoming traffic can require generating a reply packet, causing a system wakeup, or ignoring it. Proxies also do some routine packet generation on their own, and data are exchanged between a host and a proxy when the host goes to sleep and when it wakes up. Existing technologies require other ent
15、ities on the network to know that the host is asleep and alter their behaviour appropriately. A key goal of a proxy is to save energy, while simultaneously keeping the device accessible to the rest of the network. The operations of the proxy are best-effort, both in attempting to extend sleep time,
16、as well as maintaining network access. There are many possible ways to implement proxy functionality, and this Standard seeks to avoid unduly restricting choices in those designs. In particular, it does not specify the location of the proxy, within the host itself or in attached network devices. Thi
17、s 2ndedition is fully aligned with the 1stedition of ISO/IEC 16317:2011. This Ecma Standard has been adopted by the General Assembly of June 2012. iv Ecma International 2012“COPYRIGHT NOTICE This document may be copied, published and distributed to others, and certain derivative works of it may be p
18、repared, copied, published, and distributed, in whole or in part, provided that the above copyright notice and this Copyright License and Disclaimer are included on all such copies and derivative works. The only derivative works that are permissible under this Copyright License and Disclaimer are: (
19、i) works which incorporate all or portion of this document for the purpose of providing commentary or explanation (such as an annotated version of the document), (ii) works which incorporate all or portion of this document for the purpose of incorporating features that provide accessibility, (iii) t
20、ranslations of this document into languages other than English and into different formats and (iv) works by making use of this specification in standard conformant products by implementing (e.g. by copy and paste wholly or partly) the functionality therein. However, the content of this document itse
21、lf may not be modified in any way, including by removing the copyright notice or references to Ecma International, except as required to translate it into languages other than English or into a different format. The official version of an Ecma International document is the English language version o
22、n the Ecma International website. In the event of discrepancies between a translated version and the official version, the official version shall govern. The limited permissions granted above are perpetual and will not be revoked by Ecma International or its successors or assigns. This document and
23、the information contained herein is provided on an “AS IS“ basis and ECMA INTERNATIONAL DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY O
24、R FITNESS FOR A PARTICULAR PURPOSE.“ proxZzzy for sleeping hosts 1 Scope This Standard specifies maintenance of network connectivity and presence by proxies to extend the sleep duration of hosts. This Standard specifies: Capabilities that a proxy may expose to a host. Information that must be exchan
25、ged between a host and a proxy. Proxy behaviour for 802.3 (Ethernet) and 802.11 (WiFi). Required and Option behaviour of a proxy while it is operating, including responding to packets, generating packets, ignoring packets, and waking the host. This Standard does not: Specify communication mechanisms
26、 between hosts and proxies. Extend or modify the referenced specifications (and for any discrepancies those specifications are authoritative). Support security and communication protocols such as IPsec, MACSec, SSL, TLS, Mobile IP, etc. 2 Conformance An “M”, “S” or “O” in the “M/S/O” column in the t
27、ables in Clause 6, 7 and 8 qualify the requirements as “M” for Mandatory, “S” for Should and “O” for Option respectively. Conformant proxies implement at least the mandatory requirements in the “Basic Framework Protocol” in Clause 6 and zero or more Options in Clause 8. Proxies adhere to configurati
28、on and management behaviours as specified in Clause 7. The table below summarises the Requirements and status. Ecma International 2012 1Requirements Implemented Required/Option Media (802.3, 802.11) Requires implementation of 6.1 or 6.2 or both IPv4 ARP Mandatory IPv6 Neighbor Discovery Mandatory DN
29、S Option DHCP OptionIGMP Option MLD Option Remote Access using SIP and IPv4 Option Remote Access using Teredo for IPv6 Option SNMP Option Service Discovery using mDNS Option Name Resolution with LLMNR Option Wake Packets Mandatory 3 Normative references The following referenced documents are indispe
30、nsable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/IEC 8802-3:2000, Information technology - Telecommunications and information exchange betwe
31、en systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications ISO/IEC 8802-11:2005, Information technology - Telecommunications and information exchange between syst
32、ems - Local and metropolitan area networks - Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications ISO/IEC TR 11802-2:2005, Information technology - Telecommunications and information exchange between systems - Local and metropolitan area n
33、etworks - Technical reports and guidelines - Part 2: Standard Group MAC Addresses RFC 826, An Ethernet Address Resolution Protocol; David C. Plummer (MIT); November 1982; http:/tools.ietf.org/html/rfc826 1122RFC 1122, Requirements for Internet Hosts - Communication Layers; R. Braden; October 1989; h
34、ttp:/tools.ietf.org/html/rfc RFC 3261-SIP, Session Initiation Protocol; Many Authors; June 2002; http:/tools.ietf.org/html/rfc3261 RFC 4380, Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs); http:/tools.ietf.org/html/rfc4380 /html/rfc4443RFC 4443, Internet Control Message
35、Protocol (ICMPv6) for Internet Protocol Version 6 (IPv6) Specification; http:/tools.ietf.org 2 Ecma International 2012RFC 2460, Internet Protocol, Version 6 (IPv6) Specification; http:/tools.ietf.org/html/rfc2460 RFC 4861, Neighbor Discovery for IP Version 6 (IPv6); http:/tools.ietf.org/html/rfc4861
36、 IEEE Standard 802.11r-2008, IEEE Standard for information technology Telecommunications and information exchange between systems Local and metropolitan area networks Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications: Amendment 2: Fast Ba
37、sic Service Set (BSS) Transition. http:/tools.ietf.org/html/draft-cheshire-dnsext-multicastdns-08 (Multicast DNS) http:/tools.ietf.org/html/draft-cheshire-dnsext-dns-sd-05 (DNS-Based Service Discovery) MS-LLMNRP “Link Local Multicast Name Resolution (LLMNR) Profile”, Microsoft Developer Network Open
38、 Specifications Developer Center Library, http:/ 4 Terms and definitions For the purposes of this document, the following terms and definitions apply. 4.1 host entity that uses a lower-power proxy for maintaining network presence 4.2 proxy network proxy entity that maintains network presence for a s
39、leeping higher-power host 4.3 sleep (noun) mode in which the host use less energy than it does when fully operational 5 Proxy Usage of Protocols (informative) 5.1 Basic Architecture For a proxy to function correctly and enable a host to sleep, certain basic functions must be present in the proxy, it
40、s host, and in the communications between the proxy and host. This Standard offers a profile of commonly deployed protocols which can be implemented in a proxy to produce the desired system behaviour. 5.2 Ethernet (IEEE 802.3) IEEE standard 802.3 specifies Physical and Media Access Control layers of
41、 an interoperable protocol, commonly known as Ethernet. IEEE 802.3 environments have protocols which may affect proxy operation such as updates of network management parameters in response to LLDP exchanges, including possibly waking the host. IEEE 802.3 interfaces are capable of supporting multiple
42、 MAC addresses simultaneously. This functionality has been applied to supporting virtual machines each with one or more unique MAC addresses (each MAC address with one or more IPv4/v6 addresses) on a single physical interface. Wired deployments differ in nature Home, Enterprise, and Guest network co
43、nnections and, even within each, deployment configuration and network interaction can be significantly different. If link status changes, a Ecma International 2012 3considerable period of time may pass before the proxy will be able to send or receive traffic over the switch port while the Spanning T
44、ree Protocol is executed. 5.3 Wireless LAN (IEEE 802.11) IEEE standard 802.11 specifies Physical Layer and Media Access Control layers of an interoperable wireless protocol, commonly known as WiFi. Wireless communication using 802.11 differs from that of wired (IEEE 802.3) LAN operations in the foll
45、owing ways: 802.11 wireless communications transpire over unlicensed-band which makes it susceptible to multiple levels of interference and coverage issues. Hence, WiFi connectivity cannot be assured. The 802.11 host and the Access Point (AP) are configured to use a common “Profile” a set of connect
46、ion parameters such as band, channel, security, etc. The profile is configured out of band and prior to the host going to sleep. Herein are some wireless-specific deployment considerations for proxy: Hosts often disconnect from an AP, and may re-connect to the same AP or another AP within the same S
47、SID, or to an AP in a different SSID. This is based on the Connection Profiles configuration. A proxy may be unable to operate in public WiFi hotspots that require explicit user authorization, such as requiring a legal agreement (EULA). Some WLAN deployments require a DHCP Renew at association time.
48、 5.4 Dynamic Host Configuration Protocol (DHCP) DHCP is the primary IP address allocation mechanism for IPv4 and stateless IP address allocation mechanism for IPv6 networks. A DHCP Server allocates IP addresses for systems on the network. The lease time of the IP address may expire while the system
49、is asleep. The following methods ensure that the proxy can continue using the same IP address that has been allocated to the host by the DHCP Server. Host sets an internal timer and wakes itself in time to renew the DHCP lease. There are no requirements for the proxy. The proxy wakes the host on a proxy-based timer to renew the DHCP lease. The proxy implements DHCP address renewal functionality, without waking the host. The proxy does
