1、 Reference number ISO/IEC 16317:2011(E) ISO/IEC 2011INTERNATIONAL STANDARD ISO/IEC 16317 First edition 2011-10-01 Information technology Telecommunications and information exchange between systems proxZzzy for sleeping hosts Technologies de linformation Tlinformatique proxZzzy pour htes dormants ISO
2、/IEC 16317:2011(E) COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2011 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from eith
3、er ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO/IEC 2011 All rights reservedISO/IEC 16317:2011(
4、E) ISO/IEC 2011 All rights reserved iiiContents Page Foreword . v Introduction vi 1 Scope 1 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 Dy
5、namic Host Configuration Protocol (DHCP). 4 5.5 Internet Protocol v4 Basic Framework (IPv4) . 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 Pr
6、otocol 5 5.5.6 TCP Transmission Control Protocol 5 5.5.7 DNS Domain Name System . 5 5.6 Internet 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 mD
7、NS . 7 5.11 Name Resolution with LLMNR . 7 5.12 Wake Packets . 7 6 Basic Framework Protocols . 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 C
8、onfiguration Data 10 6.3.2 Behavioural Requirements . 10 6.4 Neighbour Discovery 11 6.4.1 Configuration 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 1
9、2 7.2 Behavioural Requirements . 12 7.2.1 Returned Data (Option) . 13 8 Options . 13 ISO/IEC 16317:2011(E) iv ISO/IEC 2011 All rights reserved8.1 IGMP Multicast (Option) 13 8.1.1 Configuration Data.13 8.1.2 Behavioural Requirements .13 8.2 DHCP Address Allocation (Option) 14 8.2.1 Configuration Data
10、.14 8.2.2 Behavioural Requirements .14 8.3 Remote Access using SIP and IPv4 (Option) 14 8.3.1 Behavioural Requirements .15 8.4 Remote Access using Teredo for IPv6 15 8.4.1 Data Configuration.16 8.4.2 Behavioural Requirements .16 8.5 Simple Network Management Protocol (SNMP) .16 8.5.1 Configuration D
11、ata.16 8.5.2 Behavioural Requirements .17 8.6 Service Discovery using mDNS .17 8.6.1 Configuration Data.17 8.6.2 Behavioural Requirements .18 8.7 Name Resolution with LLMNR 20 8.7.1 Configuration Data.20 8.7.2 Behavioural Requirements .20 Annex A (informative) System Considerations 21 Annex B (infor
12、mative) Protocols Considered but not included .23 Bibliography 24 ISO/IEC 16317:2011(E) ISO/IEC 2011 All rights reserved vForeword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardizatio
13、n. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual i
14、nterest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance w
15、ith the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard r
16、equires approval by at least 75 % of the national bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. ISO/IEC 16317 was pr
17、epared by Ecma International (as ECMA-393) and was adopted, under a special “fast- track procedure”, by Joint Technical Committee ISO/IEC JTC 1, Information technology, in parallel with its approval by national bodies of ISO and IEC. ISO/IEC 16317:2011(E) vi ISO/IEC 2011 All rights reservedIntroduct
18、ion 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 devices have large power differences between their on and sleep
19、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-top boxes. A low-power proxy handles key network tasks for a high-
20、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. The standard designates that a “platform-independent industry s
21、tandard” will specify the behaviour of a qualifying proxy. It is expected that ISO/IEC 16317 will be that standard. This International Standard provides an overall architecture for a proxy and key requirements for preying select protocols. Handling of incoming traffic can require generating a reply
22、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 entities on the network to know that the host is aslee
23、p 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, as well as maintaining network access. There are ma
24、ny possible ways to implement proxy functionality, and this International 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. INTERNATIONAL STANDARD ISO/IEC 16317:201
25、1(E) ISO/IEC 2011 All rights reserved 1Information technology Telecommunications and information exchange between systems proxZzzy for sleeping hosts 1 Scope This International Standard specifies maintenance of network connectivity and presence by proxies to extend the sleep duration of hosts. This
26、International Standard specifies: capabilities that a proxy may expose to a host; information that must be exchanged between a host and a proxy; proxy behaviour for 802.3 (Ethernet) and 802.11 (WiFi); required and optional behaviour of a proxy while it is operating, including responding to packets,
27、generating packets, ignoring packets, and waking the host. This International Standard does not: specify communication mechanisms between hosts and proxies; extend or modify the referenced specifications (and for any discrepancies those specifications are authoritative); support security and communi
28、cation 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 tables 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 mandato
29、ry requirements in the “Basic Framework Protocol” in Clause 6 and zero or more Options in Clause 8. Proxies adhere to configuration and management behaviours as specified in Clause 7. The table below summarises the Requirements and status. ISO/IEC 16317:2011(E) 2 ISO/IEC 2011 All rights reservedRequ
30、irements 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 DNS Option DHCP Option IGMP Option MLD Option Remote Access using SIP and IPv4 Option Remote Access using Teredo for IPv6 Option SNMP Option S
31、ervice Discovery using mDNS Option Name Resolution with LLMNR Option Wake Packets Mandatory 3 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest editi
32、on of the referenced document (including any amendments) applies. ISO/IEC 8802-3:2000, Information technology Telecommunications and information exchange between systems Local and metropolitan area networks Specific requirements Part 3: Carrier sense multiple access with collision detection (CSMA/CD
33、) access method and physical layer specifications ISO/IEC 8802-11:2005, 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) specificati
34、ons ISO/IEC TR 11802-2:2005, Information technology Telecommunications and information exchange between systems Local and metropolitan area networks Technical reports and guidelines Part 2: Standard Group MAC Addresses RFC 826, An Ethernet Address Resolution Protocol; David C. Plummer (MIT); Novembe
35、r 1982; http:/tools.ietf.org/html/rfc826 RFC 1122, Requirements for Internet Hosts Communication Layers; R. Braden; October 1989; http:/tools.ietf.org/html/rfc1122 RFC 3261, SIP: Session Initiation Protocol; Many Authors; June 2002; http:/tools.ietf.org/html/rfc3261 RFC 4380, Teredo: Tunneling IPv6
36、over UDP through Network Address Translations (NATs); http:/tools.ietf.org/html/rfc4380 RFC 4443, Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification, http:/tools.ietf.org/html/rfc4443 ISO/IEC 16317:2011(E) ISO/IEC 2011 All rights reserved 3RFC 2460, I
37、nternet 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 IEEE Std 802.11r-2008, IEEE Standard for information technology Telecommunications and information exchange between systems Loca
38、l and metropolitan area networks Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications: Amendment 2: Fast Basic Service Set (BSS) Transition” http:/tools.ietf.org/html/draft-cheshire-dnsext-multicastdns-08 (Multicast DNS) http:/tools.ietf.org
39、/html/draft-cheshire-dnsext-dns-sd-05 (DNS-Based Service Discovery) MS-LLMNRP “Link Local Multicast Name Resolution (LLMNR) Profile”, Microsoft Developer Network Open Specifications Developer Center Library, http:/ 4 Terms and definitions For the purposes of this document, the following terms and de
40、finitions 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 sleeping higher-power host 4.3 sleep (noun) mode in which the host uses less energy than it does when fully operational 5 Proxy Usage o
41、f 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, its host, and in the communications between the proxy and host. This International Standard offers a profile of commonly deployed proto
42、cols 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 an interoperable protocol, commonly known as Ethernet. IEEE 802.3 environments have protocols which may affect proxy o
43、peration 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 MAC addresses simultaneously. This functionality has been applied to supporting virtual machines each with one or more
44、 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 connections and, even within each, deployment configuration and network interaction can be significantly different. If li
45、nk status changes, a ISO/IEC 16317:2011(E) 4 ISO/IEC 2011 All rights reservedconsiderable period of time may pass before the proxy will be able to send or receive traffic over the switch port while the Spanning Tree Protocol is executed. 5.3 Wireless LAN (IEEE 802.11) IEEE standard 802.11 specifies
46、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 following ways: 802.11 wireless communications transpire over unlicensed-band which makes it
47、 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 connection parameters such as band, channel, security, etc. The profile is configured out of ba
48、nd 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 SSID, or to an AP in a different SSID. This is based on the Connection Profiles configura
49、tion. 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. 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
