Router Rg Wlan

8/8/2019 Router Rg Wlan

1/24

Network Infrastructure DeviceImplementers Guide

Requirements and implementation details for Consumer and Small Business routers,

WLAN APs, and residential gateways for systems that run the MicrosoftWindowsVista operating system

August 5, 2005 Version 0.6

Abstract

This paper describes the requirements and implementation details for Consumer and SmallBusiness routers, wireless LAN access points (WLAN APs), and residential gateways tointeroperate with the Microsoft Windows Vista operating system.

Windows Vista delivers a number of new and enhanced experiences for home networks,including ease of setup, ease of use, and distribution of digital media throughout the home.Devices that meet the requirements outlined in this paper will deliver the best experiencewith Windows Vista and other Microsoft products, including Microsoft Xbox and WindowsMedia Center Extender, and will receive the benefits of the Windows Vista Logo Program.

The information in this document applies for the Microsoft Windows Vista operating system.References and resources discussed here are listed at the end of this paper. The currentversion of this paper is maintained on the Web at: http://go.microsoft.com/fwlink/?LinkId=50286

For questions or comments about these requirements or implementation guidelines, pleasesend e-mail [email protected].

ContentsIntroduction .............................................................................................................................3Document Scope ............................................................................................................. ...... ..3Technology Framework and Definitions ...................................................................................4Setup and Configuration ..........................................................................................................6

WCN-Config .........................................................................................................................................6WCN-FlashConfig .............................................................................................................................. ..6WCN-Config Network ...........................................................................................................................7Simple Config Overview .......................................................................................................... ...... .......7Requirements for Wireless Routers and WLAP APs ............................................................................8

Network and Bus Basics ............................................................................................. ...... ...... .8Router IP Basics ...................................................................................................................................8802.11 Requirements for Premium Logo (Streaming Media) ..............................................................9

Transparent Connectivity .......................................................................................................11IPv4 NAT ............................................................................................................................................11

Port Assignment Policy ..................................................................................................................11Port Filtering Policy ........................................................................................................................11

IPv6 and Transition Technologies ..................................................................................................... .11Private IPv4 Connectivity (Teredo) ................................................................................................12

Public IPv4 Connectivity (6to4) ......................................................................................................13Home Router Considerations When Supporting IPv6 ...................................................................14Summary ............................................................................................................................................14

Discovery and Control............................................................................................................ 15Link Layer Topology Discovery ..........................................................................................................15Requirements for WSD, UPnP, and Auto-Bridge Mode Selection .....................................................16

Quality of Service ................................................................................................................ ...17QoS and qWAVE ................................................................................................................................17QoS Requirements .............................................................................................................................19

Resources and References ...................................................................................................19Appendix A DHCP Enable Vendor Extension Schema .......................................................21Appendix B UPnP Byte Counter Implementation Details ....................................................23Appendix C Guidelines Summary .......................................................................................24
http://go.microsoft.com/fwlink/?LinkId=50286http://go.microsoft.com/fwlink/?LinkId=50286http://go.microsoft.com/fwlink/?LinkId=50286mailto:[email protected]:[email protected]:[email protected]://go.microsoft.com/fwlink/?LinkId=50286http://go.microsoft.com/fwlink/?LinkId=50286mailto:[email protected]


2/24

Network Infrastructure Device Implementers Guide - 2

DisclaimerThis is a preliminary document and may be changed substantially prior to final commercial release of the softwaredescribed herein.

The information contained in this document represents the current view of Microsoft Corporation on the issuesdiscussed as of the date of publication. Because Microsoft must respond to changing market conditions, it shouldnot be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of anyinformation presented after the date of publication.

This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS,IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.

Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights undercopyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmittedin any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose,without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rightscovering subject matter in this document. Except as expressly provided in any written license agreement fromMicrosoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, orother intellectual property.

Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos,people, places and events depicted herein are fictitious, and no association with any real company, organization,product, domain name, email address, logo, person, place or event is intended or should be inferred.

2005 Microsoft Corporation. All rights reserved.

Microsoft, Windows, Windows Vista, and Xbox are either registered trademarks or trademarks of MicrosoftCorporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.



3/24


IntroductionThe difficulty in setting up home networks is often cited as the single largest impediment toincreased Internet usage and delivery of broadband services. Currently, users are confusedby the choices they face in selecting home networking equipment, and are frustrated whenthey purchase the wrong equipment or when they configure their network incorrectly andtheir devices or applications fail to work. As a result, mainstream consumers are hesitant to

purchase home networking devices and fail to move beyond simple single-PC tasks such asemail and Web surfing.

The Microsoft Windows Vista operating system delivers capabilities that change thelandscape for home networks and networking device vendors. Windows Vista makes it easyto set up routers, Wireless LAN access points (WLAN APs), and residential gateways thatdeliver reliable connectivity and securityprovided that these devices meet a base level ofrequirements for interoperating with Windows Vista. This document describes thoserequirements.

The Windows Vista Logo Program for Consumer routers and WLAN APs creates a single,unified set of requirements across Microsoft. This ensures that vendors can develop productsthat address multiple scenarios, without being constrained by conflicting requirements.Although these requirements specifically reflect the capabilities and technologies included in

Windows Vista, care has been taken to rationalize all Microsoft requirements for routers andWLAN APs. Requirements from Microsoft Xbox, Windows Media Center, MSN, and SmallBusiness have been unified into one cohesive set to maximize the programs effectivenessand benefits to partners.

Note: Small businesses experience network setup and connectivity problems similar to thosefound in consumer home networks. For consistency, this document refers primarily to Homenetwork scenarios; these scenarios are either identical or very similar to those for SmallBusiness networks, and hence one set of requirements addresses both customer segments.

Document ScopeThis paper provides the specific requirements and implementation details for vendors whodesign and produce routers, wireless access points, and residential gateways to interoperate

with Windows Vista. Devices that meet the requirements and guidelines in this document willmeet the requirements for the Windows Vista Logo Program.

Device Types

This paper describes requirements and implementation details for these types of devices:

Routers (both wireless and wired)

Wireless LAN access points (WLAN APs)

Residential gateways

Definitions of device types are provided in Technology Framework and Definitions later inthis paper.

Note: In this paper, the term residential gateway is not used to denote a separate deviceclass; instead, a residential gateway is treated as a router that includes an integratedbroadband modem. To receive a logo for a residential gateway product, vendors must meetthe requirements for the router device type. No requirements are defined for the modemfunctionality in a residential gateway.

Requirements for the following device types are not discussed in this document:switches, hubs, wireless bridge gaming adapters, broadband modems.



4/24


Product Qualification Levels

The Windows Vista Logo Program defines requirements for devices that can interoperationwith Windows, and also introduces qualification levels for different types of products:

The Standard logo ensures baseline compatibility and user experience withWindows Vista.

The Premium logo is reserved for products that enable and deliver premiumexperiences.

This document provides additional detail to the individual requirements for the Networkdevice types defined in the Windows Vista Logo Program requirements. This documentshould be used for design and implementation guidance, and to assist vendors in ensuringthat their products will pass the validation tests for Windows Vista Premium or Standardlogos.

Note: In cases where logo designations (Standard vs. Premium) conflict between thisdocument and Windows Vista Logo Program System and Device Requirements, Version 3.0,the Standard versus Premium definitions in the Windows Vista Logo Program System andDevice Requirements take precedence.

In this document, the Standard versus Premium information is denoted as follows:

Must indicates that the item is required for the Standard Logo.

For the Premium logo, items are designated with the phrase must be implemented forthe Windows Vista Premium logo.

All requirements for both the Standard and Premium logos will be tested as part of theWindows Vista Logo Program test suite.

Should indicates that the item is optional, but recommended.

If implemented indicates that the item must meet specific guidelines only when thefeature is implemented in a device, though the feature itself is not required.

Technology Framework and DefinitionsThe following technology framework summarizes the key networking components inWindows Vista. This framework provides the structure and order for technologies discussed

in this document.

Table 1 Technology Framework Summary



5/24


Technology Definitions

BridgeA Data Link layer (L2) device that connects two or more different LAN segments to forma single network segment (also known as a subnet or single broadcast domain). A bridgeimplements a spanning tree algorithm for network loop detection.

Broadband modemA Data Link layer (L2) device that bridges a physical broadband WAN interface into

Ethernet or USB.Hub

A Physical layer device that connects multiple wired network nodes together on the sameLAN segment. A hub implements a repeater function and is a single Ethernet collisiondomain.

Network address port translator (NAT)An IP router that translates the IP addresses and TCP/UDP port numbers of packets asthey are forwarded, as defined by RFC 1631. A NAT allows multiple private networkcomputers to use a single public IPv4 address. (See NAT references listed at the end ofthis paper.)

Definitions of NAT sub-types are as follows:

Full cone

All requests from the same internal IP address and port are mapped to the sameexternal IP address and port. Any external host can send a packet to the internalhost by sending a packet to the mapped external address. This NAT type is also bereferred to as an Open NAT.

Restricted coneAll requests from the same internal IP address and port are mapped to the sameexternal IP address and port. Unlike a full cone NAT, an external host (with IPaddress X) can send a packet to the internal host only if the internal host hadpreviously sent a packet to IP address X.

Port restricted coneSimilar to a restricted cone NAT, but the restriction includes port numbers.Specifically, an external host can send a packet, with source IP address X andsource port P, to the internal host only if the internal host had previously sent a

packet to IP address X and port P.Symmetric (or strict NAT)All requests from the same internal IP address and port, to a specific destination IPaddress and port, are mapped to the same external IP address and port. If the samehost sends a packet with the same source address and port, but to a differentdestination, a different mapping is used. Only the external host that receives apacket can send a UDP packet back to the internal host. Symmetric NATs do notinteroperate properly with Windows and many other operating systems andapplications, and should be avoided at all times.

Residential gatewayA device that combines an IP router with a broadband modem, designed to connect aprivate network to the Internet. Residential gateways that meet the requirementsdescribed in this document for routers meet the requirements for the Windows Vista

Logo Program, since they contain a full set of router functionality.

RouterA Network layer (L3) device that connects disparate network segments (that is, subnets)and forwards traffic based on a combination of a network address and a node address.NAT functionality must be included.

Note: A router with multiple Ethernet interfaces (or one or more wireless interfaces)does not route between LAN-side interfaces; they are typically switched or bridged.In other words, a home router generally routes only between the WAN and LANinterfaces.



6/24


In this document, the term router refers to both wired-only routers (those that haveonly wired Ethernet interfaces) and wireless routers (a router with a wireless accesspoint as one of its LAN interfaces).

SwitchA multi-port store-and-forward device that may also implement MAC address learning toselectively forward frames to switch ports based on the destination MAC address. Aswitch does not implement a spanning tree algorithm.

Wired routerA router with no wireless (802.11) capabilities.

Wireless bridge gaming adapterA device that connects an individual Ethernet device to a WLAN. This device type onlybridges between wired and wireless media and only implements a station function on thewireless interface. Requirements for this device type are not discussed in this document.

Wireless LAN access point (WLAN AP)A wireless base station used for hosting infrastructure mode IEEE 802.11 wirelessnetworks. WLAN APs bridge network traffic between wireless clients and a wired networksegment. A wireless access point enables one or more wireless stations (clients) toassociate to its 802.11 interface.

Wireless routerA router that also contains WLAN AP functionality. A wireless router supports all thefunctionality defined by both a non-wireless router and WLAN AP.

Setup and ConfigurationThe Setup and Configuration technology area of Windows Connect Now (as listed in Table 1)delivers effortless and secure-by-default setup of wireless infrastructure devices and wirelessclients.

WCN-ConfigTo ensure that a user has a positive experience configuring a secure wireless home network,it is important that the wireless router and WLAN AP devices designed for use in the homesupport a consistent, secure method for configuration. These capabilities are provided by

implementing one or both of the setup methods provided by Windows Connect Now, knownas WCN-FlashConfig and WCN-Config Network.

WCN-FlashConfig and WCN-Config Network are both mechanisms for configuring wirelessdevices, but they differ in the method used to transfer wireless configuration settings:

WCN-FlashConfig requires that a physical storage device, such as a USB flash drive(UFD) or CompactFlash storage card, be physically moved between the computer andthe device in need of wireless configuration settings.

WCN-Config Network over Ethernet uses UPnP to transfer settings over the wire.WCN-Config Network over Wi-Fi transfers settings using wireless in-band (that is, nophysical medium is needed for transfer).

WCN-FlashConfigWCN-FlashConfig first shipped in Windows XP Service Pack 2, and greatly eased thedifficulty associated with setting up wireless networks and adding wireless devices to themfor the small office/home office (SOHO). WCN-FlashConfig is the technology used by theWireless Network Setup Wizard in Windows XP Service Pack 2, which can be accessed fromthe Control Panel as a Networking task, as identified by the following icon.

Figure 1. WCN-FlashConfig icon



7/24


WCN-Config NetworkWCN-Config Network over Ethernet and over Wi-Fi use the Simple Config protocol forconfiguration and setup.

Simple Config OverviewFigure 2 depicts the major components and their interfaces as defined by Wi-Fi Simple

Config. There are three logical components involved: the Registrar, the access point (AP),and the Enrollee.

The Enrollee is a device seeking to join a WLAN domain. Once an Enrollee obtainsa valid credential, it becomes a member.

A Registraris an entity with the authority to issue and revoke domain credentials. Aregistrar can be integrated into an AP.

The AP can be either a WLAN AP or a wireless router.

Figure 2. Major Components of WCN-Config Network

Registration initiation is ordinarily accomplished by a user action such as powering up theEnrollee and, optionally, running a setup wizard on the Registrar (PC).

Interface MThis interface is between the AP and the Registrar. Interface M enables an externalRegistrar to manage a Wi-Fi Simple Config AP. Wi-Fi Simple Config uses a similarprotocol for setting up the AP Management interface as for issuing credentials toEnrollee devices.

AP

The AP implements Interface M by:

Acting as the Enrollee in the Registration Protocol for initial setup with one ormore external Registrars. This includes sending its own Discovery message acrossall appropriate channels (Ethernet and/or 802.11 probe response over Wi-Fi).

Implementing the Management Interface described in the WFADevice andWFAWLANConfig Service documents. This requires the AP to be a UPnP devicethat includes support for the Wi-Fi Simple Config proxy service.

Monitoring 802.11 probe request and EAP messages from Enrollees andconverting them to UPnP Event messages according to the method described in theWFAWLANConfig Service document.

Interface A

This interface is between the Enrollee and the AP. The function of Interface A is toenable discovery of the Simple Config WLAN and to enable communication between theEnrollee and Ethernet-only Registrars.

APThe AP implements Interface A by:

Sending out 802.11 beacons indicating support for Simple Config andgenerating Probe Response messages containing a description of the AP.

Implementing an 802.1X authenticator and the Simple Config EAP method.

Proxying 802.11 probe request and EAP messages between Enrollees andexternal Registrars as described in the WFADevice and WFAWLANConfig Servicedocuments.



8/24


Requirements for Wireless Routers and WLAP APsTo ensure that devices work well with Windows Vista WCN-Config, WLAN APs and wirelessrouters must meet the following requirements:

Device must support WCN-Flash Config, WCN-Ethernet, or WCN-Wi-Fi.

A device that supports WCN-Config Network over Ethernet:

Must support the Windows Connect Now Simple Config protocol.

Must use an 8 character PIN.

Must be discoverable using SSDP.

A device that supports wireless WCN-Config Network over Wi-Fi:

Must support the Windows Connect Now Simple Config protocol.

Must be discoverable using the Layer 2 wireless EAP method.

Should dynamically create a PIN.

For Windows Vista Premium logo, the device must use an 8-character PIN.

A device that supports WCN-FlashConfig:

Must include one of the supported flash drive types.

Must comply with the WCN Specification.

Device must follow the implementation details provided in the Windows ConnectNow specification. (See references listed at the end of this paper.)

Network and Bus BasicsThe Network and Bus Basics technology area of Windows Connect Now (as listed in Table1) ensures that the networking media and infrastructure devices are correctly matched forthe end-use applications and are performing properly.

Router IP BasicsRouters should properly handle basic packet routing in order to interoperate with Internet-

based services. Applications that depend on proper router behavior include online gamingservices, peer-to-peer networks, and Internet-based media streaming. Windows Vistadelivers new functionality for online and peer-to-peer services. To be compatible withWindows Vista functionality, the router must meet the following requirements:

Packet handling and routing:

It must be possible for UDP packets from multiple IP addresses to traversethe NAT component of the router.

Port mappings must not be changed or closed after receiving an ICMP port-unreachable packet on the WAN side interface.

MTU size / Fragmentation requirement:

IP routers must not fragment IP frames (either LAN to WAN or WAN to LAN)

that are less than 1440 bytes. IP routers should not fragment IP frames that are lessthan 1500 bytes. (This requirement ensures interoperability with latency-sensitiveonline services.)

It must be possible to download packets on TCP ports 80 and 3074.

DHCP Lease characteristics:When the router assigns IP addresses through DHCP, it must provide the same IPaddress with a lease duration of longer than five minutes when a client makes repeatedrequests to renew its IP address.

Session policy:The router must keep a port association open when the only traffic it is receiving is keepalive traffic generated by way of UDP packets received on the LAN-side interface.



9/24


10/24


This requirement is to ensure that the equipment can provide a high-definition multimediastream to a typical house or apartment. Figure 3 shows the layout of an apartment with therouter in the northeast corner and three wireless stations in adjoining rooms. Various, typicalobstructions such as walls, doors, furniture, and appliances are also shown. The lineardistance between the wireless access points and the stations is of some consequence, butthe number of obstructions such as walls is more important.

T P2

T P3

T P1

9 4'-1"

101'-6"

2

4

'-0

"

60'-67/16"

92'-13/8"

97'-41/4"

Figure 3. Test Layout for Wireless Access Point and Stations

Requirements for Reliability: Sustained Throughput for 8 Hours

Each radio of a wireless router or AP must be able to transmit to a wireless station asimulated high-definition video stream on UDP/TCP at 22 Mbps for eight hours with less than1% packet loss.

Sustained 22 Mbps throughput is a requirement for lightly compressed video streams, suchas MPEG-2, and to enable an infrastructure that allows for high-definition streaming in thefuture. Further, some homes are playing video such as television at almost a constant rate.The requirement for sustaining a simulated video stream for eight hours with less than 1%packet loss is meant to validate that the wireless equipment can be used without reboot orpower cycles for extended periods by the customer, with the reliability typical of mainstream

Consumer Electronics equipment.

Requirements for Reliability: Maximum Throughput Stress

Each radio and each wired interface of a wireless router or AP must be able tosimultaneously transmit to a client station at maximum capacity on UDP for one hour withless than 1% packet loss. The streams will be run simultaneously to stress the device andsimulate a heavy load.

This requirement stresses the wireless device on all its wireless interfaces (both the 802.11aand 802.11g radios on a dual-band router) at theirmaximum rate for one hour,simultaneously. This ensures that the device can handle stressful network congestion.

Note: Requirements in this section are equivalent to requirements established in theDesigned for Windows XP Media Center Edition logo program. Vendors whose productsmeet the current Logo Program router requirements can take advantage of this whenmeeting the Windows Vista Premium logo requirements for routers.



11/24


Transparent ConnectivityThe Transparent Connectivity technology area of Windows Connect Now (as listed in Table1) ensures that home networks are properly protected from the WAN environment, whileemploying firewall traversal and port mapping technologies to seamlessly deliver Internet-based experiences.

IPv4 NATMost home networks involve the use of a cable modem or DSL modem, together with arouter, to share the broadband connection to the Internet with all of the computers on theprivate network. These devices typically perform this sharing function by acting as a NAT.

It is important to understand the influence of a NAT on applications such as online gaming,chat, and other peer-to-peer dependent connections. NAT makes it difficult to establish peer-to-peer sessions between computers separated by one or more NATs. It is criticallyimportant that users do not have to manually configure their NAT devices to access all theservices available on the Internet. As a result, proper NAT behavior in routers is an essentialpart of the Windows Vista experience.

Port Assignment Policy

When a NAT receives a UDP packet from a client device, it must decide what UDP port toassign to that UDP source port on that client device. The different types of NATs aredescribed in Technology Framework and Definitions earlier in this paper.

For these three NAT types, symmetric NATs cause the most difficulty when establishingpeer-to-peer connectivity between two devices located behind NATs. Symmetric NATs mustnot be implemented.

Port Filtering PolicySome NATs apply filters on incoming traffic. The possible filtering policies include thefollowing:

No filtering.Any packet addressed to a port that the NAT has assigned to client devices is forwarded.

When combined with a minimal port assignment policy, this is sometimes referred to as afull cone NAT.

Address sensitive filtering.A packet addressed to a port that the NAT has assigned is forwarded only if it originatedfrom an IP address to which the client device has previously communicated.

Address and port sensitive filtering.A packet addressed to a port that the NAT has assigned is forwarded only if it originatedfrom an IP address and port to which the client device has previously communicated.

Windows Vista works best with cone NATs (those with a minimal port assignment policy) thatimplement no filtering or address sensitive filtering. Users behind these types of NATs will beable to connect to any other user behind any type of NAT, even symmetric NATs.

Routers must be capable of performing Network Address Translation. The NATimplementation type must comply with either the Cone or Restricted NAT type definitionsdescribed earlier in this paper.

IPv6 and Transition TechnologiesInternet Protocol version 6 (IPv6) is a suite of protocols designed to replace the existing layerprotocols of the TCP/IP protocol suite known as Internet Protocol version 4 (IPv4) on whichmost of todays Internet traffic is based. Although the most obvious difference between IPv4and IPv6 is the total number of IP addresses the new protocol supports, IPv6 offers manymore benefits, such as a hierarchical addressing structure, additional security, and greatermobility. IPv6 is a requirement for supporting new classes of computing and communicationparadigms that are difficult to deliver on the existing IPv4 infrastructure.August 5, 2005 Version 0.6


12/24


Every Windows component in Windows Vista is IPv6 capable and attempts to use IPv6 asthe preferred means of communication. Computers running Windows Vista will dramaticallyincrease the rate of deployment of IPv6, and as a result, the availability of IPv6-enableddevices and services.

For routers, full support of IPv6 is a requirement for interoperability with Windows Vista.Implementing IPv6 will simplify the customer experience with Windows Vista. Because mostof the Internet still uses IPv4, the most important pieces of the IPv6 requirements is to

support two transition technologies, called Teredo and 6to4, which allow IPv6 traffic to becarried over IPv4 networks. This allows applications to communicate using IPv6 even whenthey are connected to IPv4 networks.

With Teredo, the Windows Vista network stack tunnels IPv6 traffic over IPv4 UDP. With 6to4tunneling, the router itself (that is, with no involvement of the operating system) canencapsulate IPv6 traffic for transmission across the IPv4 Internet.

Support for both Teredo and 6to4 are required for residential gateways that want tointeroperate with Windows Vista. Implementing 6to4 can only be done by creating acomplete IPv6 stack and related protocols (e.g. DHCPv6, etc).

The following sections outline the two basic types of connectivity scenarios provided byInternet Service Providers (ISPs) and multiple service operators (MSOs), and the resultingrouter requirements in an IPv4-based network. These scenarios describe how to achieve

IPv6 connectivity over an existing IPv4 network infrastructure. For information aboutadditional scenarios that cover native IPv6 deployment, see the IPv6 IGD Cookbook. (Seethe references and resources listed at the end of this paper.)

The additional requirements for achieving full native IPv6 support, described later in thissection, must also be met for a router to receive a Windows Vista logo.

Private IPv4 Connectivity (Teredo)If the ISP provides only private IPv4 addresses to the WAN interface of the router, thenrouters cannot use 6to4 to tunnel IPv6 traffic across the IPv4 Internet. Instead, individualhosts will acquire IPv6 addresses and connectivity themselves by using Teredo technology,independently of the routers. Teredo is an IPv6 transition technology that tunnels IPv6packets as IPv4-based UDP messages.

Figure 4 shows the automated configuration of a Teredo client and how the Teredo clientdetects the type of NAT behind which it is located.

Figure 4. Automated Teredo client configuration

For Teredo to work properly, the router must meet these basic requirements:

Support UPnP IGD port mapping requests.



13/24


The Teredo client must be able to send outbound UDP traffic to the Teredo server. Ifthe router has outbound filtering, then it must support UPnP IGD port mapping requeststo allow Teredo to open the ports it needs.

Avoid resetting port mappings if an Internet Control Message Protocol (ICMP) Echomessage fails or times out.

Implement cone or restricted NAT.

Do not use a symmetric NAT implementation. Teredo only works over cone andrestricted NATs.

Support Hairpin or Loopback functionality in the NAT.

This means the NAT must carry out a twice-NAT translation of addresses for localsystems, allowing them to communicate with one another. In other words, when a hoston the private side of a NAT device attempts to connect with another host behind thesame NAT device using the public address of the host, the NAT device must performthe equivalent of a twice-NAT translation on the packet. The originating host's privateendpoint must be translated into its assigned public endpoint, and the target host'spublic endpoint must be translated into its private endpoint, before the packet isforwarded to the target host.

For details about Teredo, see the related references listed at the end of this paper.

Public IPv4 Connectivity (6to4)If the ISP provides a public IPv4 address to the router WAN interface, it is preferable that therouter handle all the IPv6 to IPv4 encapsulations (and back again), allowing the hosts on thelocal network to act as if they are directly attached to an IPv6 network when communicatingwith remote IPv6 systems across the IPv4 Internet.

Routers can provide this transparent IPv6 functionality by supporting the 6to4 transitiontechnology specified in RFCs 3056 and 3068. 6to4 requires the egress router (the router) toan IPv4 network to encapsulate IPv6 packets using an IPv4 header with the Protocol fieldvalue set to 41. In the home scenario, the home router is the egress router connected to theIPv4 Internet. However, the LAN itself can run in IPv6 native mode. Some LAN hosts mightstill use Teredo.

Therefore, a home router must meet the following requirements for WAN and LANfunctionality:

WAN interface (connected to the IPv4 Internet):

Must support 6to4 IPv6-in-IPv4 encapsulation and decapsulation, providing6to4 router functionality.

LAN interface:

Must configure an IPv6 prefix on the LAN interface derived from the publicIPv4 address from the WAN adapter, as specified in RFC 3056.

Must support IPv6 Neighbor Discovery and host autoconfiguration (respondto router Solicitation messages and send Router Advertisement messages with theIPv6 prefix derived from the public IPv4 address), as specified in RFC 2461.

Must be able to receive IPv6 Router Solicitations and Send IPv6 RouterAdvertisements.

Must support DHCPv6 stateless server functionality to add DNSconfiguration to the autoconfigured host, as specified in RFC 3315.

It is not required to support DHCPv6 server stateful functionality, although itcan be useful to support cascading prefix delegation for automatic subnetting. Forexample, a home can be allocated a /48 or /63 prefix, and the home router can thendelegate a /64 prefix to an internal router within the home. However, the assumptionfor home networks is that they have a single subnet.

Must always assign the address of the residential gateway for DNS queriesby using DHCPv6.



14/24


15/24


Note: It is not necessary to implement all IPv6 services for the WAN interface as part of theSilver logo requirements. Residential Gateways need to be able to work with IPv6 clients onthe LAN side, but IPv6 support is not a requirement on the WAN connection. Full support forIPv6 on the WAN interface is an optional requirement for Premium.

Discovery and ControlThe Discovery and Control technology area of Windows Connect Now (as listed in Table 1)

ensures that consumers experience effortless discovery of network devices and resources,and that they can securely access and control computers and devices in their home network.

Link Layer Topology DiscoveryLink Layer Topology Discovery (LLTD) is a method for discovering devices on a network andhow they are connected without the need for proper IP configuration. The informationprovided through LLTD will help users and support professionals identify where networkingproblems are occurring and improve the overall support experience.

LLTD consists of a Mapper and a Responder:

The Mapper starts the network topology mapping session and interprets the resultsto draw a topologically correct map, with no need for IP connectivity at any network node.

The Responder participates in the mapping session, telling the Mapper of itspresence, performing tests requested by the Mapper, and describing the networkinfrastructure devices to which it is connected and what other devices it has detected.

The following describes the operation of the LLTD protocol. Responders operate in one offour states, as shown in Figure 5.

Figure 5. Responder Operational States

Quiescent. A Responder waits for a Mapper to start the mapping process. After the

Responder receives a MapBegin frame, it moves to the Hello state to begin associationwith a Mapper.

Hello. A Responder associates with a Mapper. The Mapper gets a list of theResponders on the network. A generation number (an identifier for the mapping session)is created. Responders avoid network overload on large networks. After association withMapper is complete, a Responder moves to the Command Loop state.

Command Loop. During an active mapping session, devices spend most of theirtime in the Command Loop state. When the device is connected using a wired 802.3interface, the interface must enter promiscuous mode; however, this is not necessary fordevices that connect using Wi-Fi. Responders execute Emit and Query commandsreceived from a Mapper. After a timeout period or after receiving a command from theMapper that the map session is complete, the device returns to its usual Quiescent state.

Emit. Each entry from the existing list of Emit requests is serviced in turn. AResponder continues to handle incoming protocol frames. While in this state, it dropsincoming Emit and Query requests. After all the requests are serviced, the Responderreturns to the Command Loop state.

To ensure that devices work well with the Windows Vista LLTD protocol, routers and WLANAPs must do the following:

Implement LLTD Responder according to the LLTD specification. (See referencesand resources at the end of this document.)

Report properly formatted metadata for mandatory TLVs (Type Length Value pairs)according to LLTD specification.



16/24


Meet minimum performance requirements (response time) as described in LLTDspecification.

Perform primary functions (routing, bridging, and so on) reliably after repeated(>100) consecutive mapping sessions.

Issue already response after receiving a second MapBegin command whenmapping session is already in progress.

Requirements for WSD, UPnP, and Auto-Bridge ModeSelection

In Windows Vista, the Web Services for Devices (WSD) protocol delivers improveddiscovery, additional security methods, and rich interoperability with Internet-based Webprotocols. To be eligible for a Windows Vista Premium logo, routers and WLAN APs mustimplement WSD-Discovery. Guidelines for delivering an improved experience with legacyUPnP-based devices are summarized in this section.

Figure 4 shows the logical structure of devices and services within the UPnP IGD DCP.

UPnP Internet Gateway Device

Layer 3 Port

Forwarding

Service

WAN Device

LAN Device

LANHost Config

Management Service

(Optional)

WAN Connection

Device

Figure 4. The Logical Structure of Devices and Services within UPnP IGD

The following requirements apply for routers and wireless APs:

Receive certification for UPnP IGD implementation from the UPnP ImplementersCorporation.

Ship with UPnP IGD functionality enabled (turned on) on the devices LAN interfaceby default. Default enablement must survive a hard device reset.

Implement the following actions and state variables, and accurately report statisticsin order to interoperate with Windows Vista:

Implement the GetTotalBytesSent and GetTotalBytesReceived actionscontained within the WANDevice virtual device of the UPnP IGD v1.0 DCP.

Values returned by these actions must accurately report traffic sent orreceived across the WAN interface. For more information on proper implementationof Byte Counters, see Appendix B.

Populate sufficient metadata in the UPnP device description document todescribe the device and its characteristics during discovery. This functionality isrecognized by the PnP-X and Function Discovery components of Windows Vista.The required and optional PnP-X metadata are:

Required: deviceType, manufacturer, modelName, modelNumber, friendlyName

Optional: hardwareID, compatibleID, deviceCategory



17/24


Populating the Optional metadata values is strongly recommended. For more informationabout PnP-X, see the Network Connected Devices, Function Discovery and PnP-Xwhitepaper. (See references listed at the end of this paper.)

Support Auto-Bridge that is, entering a Bridge modeas follows:

The device must continually perform a DHCP IP address assignmentrequest on its WAN interface.

If it receives a private address in the range 192.168.x.y, where x and y are any

values between 0 and 9, the device must toggle (configure) itself into a bridgedmode, to prevent the creation of an additional subnet.

In this mode, the device will act as a pure WLAN AP on its WAN interface (that is, itwill bridge between the LAN and WAN), and as a switch on all wired interfaces. NAT,DHCP address assignment, and IP routing are disabled in Bridge mode.

All interfaces must be bridged together when the device enters Bridge mode.

The device must ship with Auto-Bridge configuration as its default mode.

The vendor can implement the ability to override default settings through the devicesWeb interface management UI. However, the device must ship with Auto-Bridgeconfiguration as the default mode (that is, its factory-configured state), and thedevice must return to this state after a hard device reset.

DHCP server on the router assigns addresses from a preset pool in one ofthe 192.168.x.y/24 networks ( where x is any value between 0 and 9).

The UPnP IGD implementation, must support configuration of at least 25simultaneous port mappings.

In the devices default (factory-shipping) state, all ports numbers must be allowed to bemapped, including well-known ports such as 21, 25, 80, 445, and 3389.

An optional service and schema that the device might choose to implement is outlined inAppendix A.

Quality of ServiceThe Quality of Service (QoS) component of Windows Connect Now (as listed in Table 1)ensures that home routers, WLAN APs, and wireless routers employ the necessary protocolsto report status, diagnose problems, and manage bandwidth on the home network.

QoS and qWAVENetwork QoS ensures that bandwidth-sensitive applications continue to operate despitebottlenecks or transient network conditions that reduce available bandwidth. To ensure agood experience for media distribution, it is essential to ensure that network infrastructuredevices (routers, WLAN APs, and so on) properly implement and follow QoS guidelines,particularly for wireless networks. The implementation of QoS also provides opportunities tointroduce new device capabilities that will work well with Windows Vista.

A brief description of a QoS-enabled scenario is outlined in this section, followed by therelated device requirements for home routers, WLAN APs, and wireless routers to properlyimplement QoS in Windows Vista.

Figure 5 shows the topology of a home network with simultaneous audio/video (AV) and datatraffic.



18/24


Figure 5. Example Home Network with Simultaneous AV and Data Traffic

In this example, there are the following:

Two concurrent high-definition video streams are running over the home networkfrom a computer in the den to display devices in the family room and master bedroom.

A tablet PC is accessing e-mail over the Internet.

A live gaming session is occurring over the Internet.

A job is printing on the network printer.

Traffic scenarios such as this, with multiple high-quality video streams and multiple datastreams, are already appearing and will be increasingly common in the Windows Vistatimeframe.

Quality Windows Audio Video Experience (qWAVE), the next generation network QoSfunctionality available in Windows Vista, addresses home AV streaming scenarios thatinvolve real-time, high-priority traffic that shares a single network with best-effort and low-priority traffic. These scenarios present challenges for network QoS. The challenges aremore critical for scenarios involving home networks that use Wi-Fi technology because ofbandwidth, stability, and range limitations.

qWAVE provides mechanisms to support home AV streaming scenarios such as distributedadmission control, intelligent packet prioritization, bandwidth measurement, run-timemonitoring and enforcement, and feedback (congestion notification) that can be used by AVapplications to provide glitch-free streaming to the user. The qWAVE framework usesstandard Layer 2 technologies with little or no dependency on the network hardwareinfrastructure. The qWAVE solution is independent of the physical media type (fine tuned for

802.3 and 802.11 mediums), and therefore will work on every IP-based network, whether it iswired or wireless.

qWAVE will be integrated with solutions that address other issues for successful AVstreaming in the home. These solutions include transport mechanisms for AV streaming,such as RTP and RTCP, network diagnostics, troubleshooting, and content discovery andmanagement.

The quality of home routers and wireless routers is crucial for AV streaming. Unstablebandwidth, poor reach (distance), intolerance to RF interference, and poor support for QoSthrough WMM, 802.1Q, and DSCP can cause unacceptable user experiences with AVstreaming applications.



19/24


QoS RequirementsBaseline QoS requirements for routers and WLAN APs are:

Must never drop an 802.1Q priority tagged packet or modify the 802.1Q priority tag.

Note: 802.1Q refers to the priority field (i.e. formerly 802.1P), not VLAN.

Must never add an 802.1Q tag with priority value of zero (0).

Best effort (BE) packets must not carry any 802.1Q priority tag.

Must never modify the DSCP field of a packet.

Premium QoS requirements for routers and WLAN APs are:

Must support IEEE 802.1D Annex G for priority mapping (Table 3 collapses thisspecification into four traffic classes).

802.11 wireless access points and routers must have Wi-Fi WMM certification.

Must implement LLTD Responder protocol with time probe (QoS) extensions. SeeLink Layer Topology Discovery earlier in this document.

When bridging packets from an 802.3 LAN interface to an 802.11 LAN interface:

If an incoming packet contains an 802.1Q priority tag, this tag must betranslated to a WMM access category as defined in section 3.3.1 of WMM

specification If an incoming packet does not contain an 802.1Q priority tag, but doescontain a DSCP value, this value must be translated to a WMM access category asdefined by Table 3.

If the DSCP value is not one of those listed in Table 3, the best effort (BE) WMMaccess category must be used.

When bridging packets from an 802.11 LAN interface to an 802.3 LAN interface, ifassociation with 802.11 station (STA) is WMM enabled, the WMM access category mustbe translated to an 802.1Q priority tag as defined by Table 3.

Table 3 WMM Access to 802.1Q Priority Translation

Description 802.1Q user priority WMM accesscategory

DSCP

Background 1 BK 0x08Best Effort 0 BE 0x00Video (AV) 5 VI 0x28Voice 7 VO 0x38

Resources and ReferencesFor questions or comments about these requirements or implementation guidelines, pleasesend e-mail [email protected].

For additional information, see the following references.

IEEE Specifications

2004 Bridge Specification: standards.ieee.org/getieee802/download/802.1D-2004.pdf

IPv6IPv6:http://www.ietf.org/rfc/rfc2460.txt

Neighbor Discovery: http://www.ietf.org/rfc/rfc2461.txt

6to4: http://www.ietf.org/rfc/rfc3056.txt

Microsoft IPv6 Support in Internet Gateway Devices white paper:http://www.microsoft.com/whdc/hwdev/tech/network/IPv6_IGD.mspx

Microsoft Windows IPv6 Web site: http://www.microsoft.com/ipv6/

For more information about how Teredo works, see Teredo Overview:http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/teredo.mspxAt the time of writing, the Teredo Internet draft can be found at

mailto:[email protected]:[email protected]:[email protected]://standards.ieee.org/getieee802/download/802.1D-2004.pdfhttp://www.ietf.org/rfc/rfc2460.txthttp://www.ietf.org/rfc/rfc2460.txthttp://www.ietf.org/rfc/rfc2461.txthttp://www.ietf.org/rfc/rfc3056.txthttp://www.microsoft.com/whdc/hwdev/tech/network/IPv6_IGD.mspxhttp://www.microsoft.com/ipv6/http://www.microsoft.com/ipv6/http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/teredo.mspxhttp://www.microsoft.com/technet/prodtechnol/winxppro/maintain/teredo.mspxmailto:[email protected]://standards.ieee.org/getieee802/download/802.1D-2004.pdfhttp://www.ietf.org/rfc/rfc2460.txthttp://www.ietf.org/rfc/rfc2461.txthttp://www.ietf.org/rfc/rfc3056.txthttp://www.microsoft.com/whdc/hwdev/tech/network/IPv6_IGD.mspxhttp://www.microsoft.com/ipv6/http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/teredo.mspx


20/24


http://www.ietf.org/html.charters/ngtrans-charter.html, under the title Teredo: TunnelingIPv6 over UDP through NATs.

Link Layer Topology Discovery (LLTD)

WinHEC 2005 presentation: http://www.microsoft.com/whdc/winhec/Pres05.mspxAdditional information: http://www.microsoft.com/whdc/device/netAttach/WCN.mspx

NAT

Network Address Translation information and type descriptions:

http://www.ietf.org/html.charters/nat-charter.htmlandhttp://www.ietf.org/rfc/rfc3489.txtqWAVE APIs and QoS

Whitepaper:http://www.microsoft.com/whdc/device/stream/Home-AVstream.mspx

UPnP Device Architecture, IGDv1, and Basic Device:

UPnP IGDv1: http://www.upnp.com/standardizeddcps/igd.asp

Device Certification: www.upnp-ic.com

UPnP Developer Documentation on MSDN:http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wcecomm5/html/wce50oriUniversalPlugPlayUPnP.asp

UPnP DCPs:http://www.upnp.org/standardizeddcps/default.asp

NATs and NAT Traversal in Windows XP:www.microsoft.com/technet/prodtechnol/winxppro/deploy/nattrnsv.mspx

Web Services and Web Services for Devices

Web Services: http://msdn.microsoft.com/webservices/default.aspx

Web Services Feedback Workshops:http://msdn.microsoft.com/webservices/community/workshops/

Web Services Basics:http://msdn.microsoft.com/webservices/understanding/webservicebasics/

Devices Profile for Web Services: http://msdn.microsoft.com/ws/2004/08/devprof

WS-Discovery: http://msdn.microsoft.com/ws/2004/10/ws-discovery/

Network Connected Devices, Function Discovery and PnP-X:http://www.microsoft.com/whdc/device/netattach/default.mspx

Wi-Fi Alliance Certification

http://www.wi-fi.org

http://www.wi-fi.org/OpenSection/MediaResources.asp?TID=5

WMM and QoS: http://www.wi-fi.org/OpenSection/pdf/WMM_QoS_whitepaper.pdf

802.11n Q&A:http://www.wi-fi.org/OpenSection/pdf/802.11n_Q_A.pdf

WFA certification of 802.11g: http://www.wi-fi.org/OpenSection/pdf/TGG_QA.pdf

Windows Connect Now

http://www.microsoft.com/whdc/device/netAttach/WCN.mspx

Website contents include whitepapers, specification details, and so on.

Windows Vista Logo Program

Microsoft Windows Vista Logo Program System and Device Requirements, Version 3.0:http://www.microsoft.com/whdc/winlogo/default.mspx

Tests for the Windows Vista Logo Program are built into the Microsoft Windows Driver

Kit (WDK): http://www.microsoft.com/whdc/driver/WDK/aboutWDK.mspx

Designed for Windows Media Center Logo Program:http://www.microsoft.com/WindowsXP/MediaCenter/partners/dfw.mspx

Xbox Live

Whitepaper: http://www.microsoft.com/whdc/winhec/papers04.mspx

Router FAQ: http://www.xbox.com/en-AU/live/start/connect/faq/routers.htm

Getting Started: http://www.xbox.com/en-nz/live/start/broadband/

Diagnosing Xbox Live! Connections:http://www.xbox.com/en-us/live/connect/diagnosing.htm

http://www.ietf.org/html.charters/ngtrans-charter.htmlhttp://www.microsoft.com/whdc/winhec/Pres05.mspxhttp://www.microsoft.com/whdc/device/netAttach/WCN.mspxhttp://www.microsoft.com/whdc/device/netAttach/WCN.mspxhttp://www.ietf.org/html.charters/nat-charter.htmlhttp://www.ietf.org/html.charters/nat-charter.htmlhttp://www.ietf.org/rfc/rfc3489.txthttp://www.ietf.org/rfc/rfc3489.txthttp://www.microsoft.com/whdc/device/stream/Home-AVstream.mspxhttp://opt/scribd/conversion/tmp/scratch28321/%20http://www.upnp.com/standardizeddcps/igd.asphttp://opt/scribd/conversion/tmp/scratch28321/www.upnp-ic.comhttp://msdn.microsoft.com/library/default.asp?url=/library/en-us/wcecomm5/html/wce50oriUniversalPlugPlayUPnP.asphttp://msdn.microsoft.com/library/default.asp?url=/library/en-us/wcecomm5/html/wce50oriUniversalPlugPlayUPnP.asphttp://msdn.microsoft.com/library/default.asp?url=/library/en-us/wcecomm5/html/wce50oriUniversalPlugPlayUPnP.asphttp://www.upnp.org/standardizeddcps/default.asphttp://www.upnp.org/standardizeddcps/default.asphttp://www.upnp.org/standardizeddcps/default.asphttp://opt/scribd/conversion/tmp/scratch28321/www.microsoft.com/technet/prodtechnol/winxppro/deploy/nattrnsv.mspxhttp://opt/scribd/conversion/tmp/scratch28321/www.microsoft.com/technet/prodtechnol/winxppro/deploy/nattrnsv.mspxhttp://msdn.microsoft.com/webservices/default.aspxhttp://msdn.microsoft.com/webservices/community/workshops/http://msdn.microsoft.com/webservices/understanding/webservicebasics/default.aspxhttp://msdn.microsoft.com/webservices/understanding/webservicebasics/default.aspxhttp://msdn.microsoft.com/ws/2004/08/devprofhttp://msdn.microsoft.com/ws/2004/10/ws-discovery/http://www.microsoft.com/whdc/device/netattach/default.mspxhttp://www.wi-fi.org/http://www.wi-fi.org/OpenSection/MediaResources.asp?TID=5http://www.wi-fi.org/OpenSection/pdf/WMM_QoS_whitepaper.pdfhttp://www.wi-fi.org/OpenSection/pdf/802.11n_Q_A.pdfhttp://www.wi-fi.org/OpenSection/pdf/802.11n_Q_A.pdfhttp://www.wi-fi.org/OpenSection/pdf/802.11n_Q_A.pdfhttp://www.wi-fi.org/OpenSection/pdf/TGG_QA.pdfhttp://www.microsoft.com/whdc/device/netAttach/WCN.mspxhttp://www.microsoft.com/whdc/winlogo/default.mspxhttp://www.microsoft.com/whdc/driver/WDK/aboutWDK.mspxhttp://www.microsoft.com/whdc/driver/WDK/aboutWDK.mspxhttp://www.microsoft.com/WindowsXP/MediaCenter/partners/dfw.mspxhttp://www.microsoft.com/whdc/winhec/papers04.mspxhttp://www.microsoft.com/whdc/winhec/papers04.mspxhttp://www.xbox.com/en-AU/live/start/connect/faq/routers.htmhttp://www.xbox.com/en-nz/live/start/broadband/http://www.xbox.com/en-us/live/connect/diagnosing.htmhttp://www.xbox.com/en-us/live/connect/diagnosing.htmhttp://www.xbox.com/en-us/live/connect/diagnosing.htmhttp://www.ietf.org/html.charters/ngtrans-charter.htmlhttp://www.microsoft.com/whdc/winhec/Pres05.mspxhttp://www.microsoft.com/whdc/device/netAttach/WCN.mspxhttp://www.ietf.org/html.charters/nat-charter.htmlhttp://www.ietf.org/rfc/rfc3489.txthttp://www.microsoft.com/whdc/device/stream/Home-AVstream.mspxhttp://opt/scribd/conversion/tmp/scratch28321/%20http://www.upnp.com/standardizeddcps/igd.asphttp://opt/scribd/conversion/tmp/scratch28321/www.upnp-ic.comhttp://msdn.microsoft.com/library/default.asp?url=/library/en-us/wcecomm5/html/wce50oriUniversalPlugPlayUPnP.asphttp://msdn.microsoft.com/library/default.asp?url=/library/en-us/wcecomm5/html/wce50oriUniversalPlugPlayUPnP.asphttp://www.upnp.org/standardizeddcps/default.asphttp://opt/scribd/conversion/tmp/scratch28321/www.microsoft.com/technet/prodtechnol/winxppro/deploy/nattrnsv.mspxhttp://msdn.microsoft.com/webservices/default.aspxhttp://msdn.microsoft.com/webservices/community/workshops/http://msdn.microsoft.com/webservices/understanding/webservicebasics/default.aspxhttp://msdn.microsoft.com/ws/2004/08/devprofhttp://msdn.microsoft.com/ws/2004/10/ws-discovery/http://www.microsoft.com/whdc/device/netattach/default.mspxhttp://www.wi-fi.org/http://www.wi-fi.org/OpenSection/MediaResources.asp?TID=5http://www.wi-fi.org/OpenSection/pdf/WMM_QoS_whitepaper.pdfhttp://www.wi-fi.org/OpenSection/pdf/802.11n_Q_A.pdfhttp://www.wi-fi.org/OpenSection/pdf/TGG_QA.pdfhttp://www.microsoft.com/whdc/device/netAttach/WCN.mspxhttp://www.microsoft.com/whdc/winlogo/default.mspxhttp://www.microsoft.com/whdc/driver/WDK/aboutWDK.mspxhttp://www.microsoft.com/WindowsXP/MediaCenter/partners/dfw.mspxhttp://www.microsoft.com/whdc/winhec/papers04.mspxhttp://www.xbox.com/en-AU/live/start/connect/faq/routers.htmhttp://www.xbox.com/en-nz/live/start/broadband/http://www.xbox.com/en-us/live/connect/diagnosing.htmhttp://www.xbox.com/en-us/live/connect/diagnosing.htm


21/24


Appendix A DHCP Enable Vendor ExtensionSchema

Routers and wireless routers can also support remote configuration of DHCP servicesthrough UPnP. The UPnP IGD LANHostConfigMangement service may be included in theparent UPnP IGD Device to perform these tasks.

If such support is implemented, the DHCPConfigurable state variable must be set to 1 as itsdefault setting. Also, if implemented, this service must be configurable such that SubnetMask, DNS server, Domain Name, Minimum DHCP address, Maximum DHCP address, andReserved Addresses can be configured via UPnP.

In addition, if implemented, the DHCP state must be able to be set by way of the vendorextension actions X_SetDHCPEnabled and X_GetDHCPEnabled.

State Variables

Variable name Required or Optional

Data type Allowedvalue

Defaultvalue

Eng units

X_DHCPEnabled X Boolean 0,1 Notspecified

N/A

R = Required, O = Optional, X = Non-standard.

X_DHCPEnabledThis variable enables the DHCP services on the LAN interface. If the value is set to 1, theDHCP server will function according to how DHCPRelay variable is set. If the value is set to0, IGD will not respond to DHCP requests.

Eventing and Moderation

Variable name Evented Moderatedevent

Max eventrate

Logicalcombination

Min deltaper event

X_DHCPEnabled No No N/A N/A N/A

Actions

Action name Required or OptionalX_SetDHCPEnabled XX_GetDHCPEnabled X

X_SetDHCPEnabledThis action enables or disables the DHCP services on the LAN interface.

Arguments

Argument Direction relatedStateVariableNewDHCPEnabled IN X_DHCPEnabled

Dependency on State (if any)

Effect on State (if any)

This action enables or disables other actions in this service.

ErrorserrorCode errorDescription402 Invalid Args

501 Action Failed

X_GetDHCPEnabledThis action retrieves the current setting of a flag that indicates whether the DHCP servicesare enabled.

Arguments

Argument Direction relatedStateVariable



22/24


NewDHCPEnabled OUT X_DHCPEnabled

Dependency on State (if any)

Effect on State (if any)

None.

Errors

errorCode errorDescription402 Invalid Args

501 Action Failed

XML Service Description

X_SetDHCPEnabled

NewDHCPEnabled

inX_DHCPEnabled

X_GetDHCPEnabled

NewDHCPEnabledoutX_DHCPEnabled

X_DHCPEnabled

boolean



23/24


Appendix B UPnP Byte Counter ImplementationDetails

Routers must implement the GetTotalBytesReceived and GetTotalBytesSent actions of theWANCommonInterfaceConfig service of UPnP IGD v1.0 DCP. Because Windows Vista willquery these statistics multiple times per second, devices must respond to the actions as fast

as possible.For the Windows Vista Premium Logo, devices must respond within 25 ms and be capable ofservicing five simultaneous requests, because multiple machines might query the statistics.The 25 ms requirement is based on a WAN connection speed of 2 Mbps since it is acceptedthat device implementations might not have a fast enough processor to handle full LANspeeds though the WAN link.

Common mistakes to check for in your existing implementation:

Returning 0.

Returning random values.

Drastically underreporting the statistics. Some existing devices only report about30% of the actual traffic.

Treating the statistics as signed numbers. UPnP IGD v1.0 requires these numbers tobe unsigned. Signed values will be rejected by the schema validation code of UPnP API.

Responding very slowing to queries. Some existing devices take over one second torespond.

Placing the operation to increment the statistics in a queue. The pitfall with thisapproach is that it adds latency and the queue can overflow resulting in underreporting.

Simple tests to ensure appropriate implementation:

Connect the device up to a 2 Mbps+ WAN link and query the statistics. Transfer a filethough HTTP and check the statistics at the end. The statistics should be a goodrepresentation of the data that was actually transferred.

Flood the WAN link though the device and repeatedly query the counters. Thedevice should respond to counter queries within 25 ms and not report any errors. Repeatthis test for 12 hours.



24/24


Appendix C Guidelines SummaryFramework category Technology

( = Required, P = Premiumqualification, O = Optional)

Wired router WLAN AP Wireless router

Setup andConfiguration

Windows Connect Now - Config

WCN-FlashConfign/a

- One Required

(vendor choice)

- One Required

(vendor choice)WCN-Config Network or Wi-Fi

Network and BusBasics

Wired Router IP Basics

ICMP Response, MTU size,DHCP Lease characteristics,TCP FIN segment response

n/a

802.11 Wireless Router Basics

Wi-Fi Certified Dualband (a+g) n/a P P

Prolonged throughput for 8hours, minimal packet loss

n/a P P

22 Mbps for 2 hours,

Documents

Router Rg Wlan