Document erratum applies to QosDevice:1. List other Erratum s or Documents that this change may apply to or have associated changes with

Similar documents
QosPolicyHolder:1 Erratum

QosManager:1. For UPnP Version 1.0 Date: March 10th, 2005

QosPolicyHolder 1.0. For UPnP Version Date: March 10th, 2005

Restricting complextypes that have mixed content

file://c:\michael\prog\mast\docs\tmp0000.xsd

<xs:element name="record" type="recordtype" maxoccurs="unbounded" /> </xs:sequence> </xs:complextype>

[MS-SSDL]: Store Schema Definition Language File Format. Intellectual Property Rights Notice for Open Specifications Documentation

No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.

UPnP QosManager:2 Service Template Version 1.01

Allegato: AgibilitaRequest_V.1.1.xsd

3MF Slice Extension Specification and Reference Guide 1. 3MF Slice Extension. Specification & Reference Guide. Version 1.

[MS-SSDL]: Store Schema Definition Language File Format. Intellectual Property Rights Notice for Open Specifications Documentation

XML Schema. Mario Alviano A.Y. 2017/2018. University of Calabria, Italy 1 / 28

[MS-OXWSSYNC]: Mailbox Contents Synchronization Web Service Protocol Specification

Oracle B2B 11g Technical Note. Technical Note: 11g_005 Attachments. Table of Contents

Category: Standards Track T. Dietz NEC M. Swany UDel December Information Model and XML Data Model for Traceroute Measurements

Introducing our First Schema

3MF Materials and Properties Extension

[MS-TSWP]: Terminal Services Workspace Provisioning Protocol. Intellectual Property Rights Notice for Open Specifications Documentation

Messages are securely encrypted using HTTPS. HTTPS is the most commonly used secure method of exchanging data among web browsers.

UPnP QosPolicyHolder:3 Service Template Version 1.01

<xs:include schemalocation="rdmessage,ver14 for NatParas.xsd"/> <xs:include schemalocation="natparas3.xsd"/>

[MS-KPS-Diff]: Key Protection Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation

<xs:element name="relationshipdata" type="rr:relationshipdatatype"/> <xs:element name="header" type="rr:rrheadertype"> </xs:element>

[MS-OXSHRMSG]: Sharing Message Attachment Schema. Intellectual Property Rights Notice for Open Specifications Documentation

Level of Assurance Authentication Context Profiles for SAML 2.0

SHS Version 2.0 SOAP-based Protocol Binding to SHS Concepts Försäkringskassan - Swedish Social Insurance Agency

ՕՐԻՆԱԿ. <xs:schema targetnamespace=" xmlns:tax="

XML Schema Element and Attribute Reference

/// Rapport. / Testdocumentatie nieuwe versie Register producten en dienstverlening (IPDC)

CSC503 Exam 2. Assume that the following functional dependencies beyond that of the primary key are valid:

[MS-OXWSXPROP]: Extended Properties Structure. Intellectual Property Rights Notice for Open Specifications Documentation

G16-02SE-A02.1-NUE112_SchedaContatto-Rev5 <?xml version="1.0" encoding="utf-8"?> <xs:schema xmlns:xs="

Cisco Prime Central 1.0 API Guide

Custom Data Access with MapObjects Java Edition

UPnP QosPolicyHolder:2 Service Template Version 1.01

Pattern/Object Markup Language (POML): A Simple XML Schema for Object Oriented Code Description

7.1. Redovna datoteka sa slogovima koji se odnose na kupnje i prodaje valuta na tržištu stranih sredstava plaćanja

ENGINEERING COMMITTEE Digital Video Subcommittee

[MS-DPRDL]: Report Definition Language Data Portability Overview. Intellectual Property Rights Notice for Open Specifications Documentation

Request for Comments: 4661 Category: Standards Track M. Lonnfors J. Costa-Requena Nokia September 2006

Relationship Record Common Data File format V1.1

Document Metadata: document technical metadata for digital preservation

Oracle Utilities Opower Energy Efficiency Web Portal - Classic Single Sign-On

Markup Languages. Lecture 4. XML Schema

Open IPTV Forum Release 1 Specification. Volume 1 Overview. V1.0, January 6, Open IPTV Forum. Copyright 2009 Members of the Open IPTV Forum

Privacy and Personal Data Collection Disclosure. Legal Notice

PSIA Video Analytics Specification V1.0

3GPP TS V8.2.0 ( )

General Service Subscription Management Technical Specification

HVDC LINK DOCUMENT UML MODEL AND SCHEMA

ETSI TS V8.0.0 ( ) Technical Specification

No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.

No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.

VDS Service Broker APIs

1 Adaptive Streaming Overview (Informative)

Internet Engineering Task Force (IETF) Category: Standards Track Columbia U. NTT April 2014

Mapping IDABC Authentication Assurance Levels to SAML V2.0

UPnP QoS Architecture:1.0

Columbia University R. Mahy, Ed. SIP Edge LLC November An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP)

[MS-OXWMT]: Mail Tips Web Service Extensions. Intellectual Property Rights Notice for Open Specifications Documentation

ETSI TS V8.1.0 ( ) Technical Specification

Markets Data API Reference

Internet Engineering Task Force (IETF) Request for Comments: 5985 Category: Standards Track September 2010 ISSN:

No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.

PTS XML STANDARD GUIDELINE

UPDATES TO THE LRIT SYSTEM. Report of the Drafting Group

XEP-0009: Jabber-RPC

PESC Compliant JSON Version /19/2018. A publication of the Technical Advisory Board Postsecondary Electronic Standards Council

PLANNED RESOURCE SCHEDULE DOCUMENT UML MODEL AND SCHEMA

OIPF. Release 1 IPTV Solution. V1.1 Errata 2 [201. Open IPTV Forum. Copyright 2011 Open IPTV Forum

REDISPATCH DOCUMENT UML MODEL AND SCHEMA

Video Streaming over Home Network Peter van der stok

No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.

RESOURCE SCHEDULE CONFIRMATION DOCUMENT UML MODEL AND SCHEMA

[MS-TMPLDISC]: Template Discovery Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation

Request for Comments: 5025 Category: Standards Track December 2007

MWTM 6.1 NBAPI WSDL and XSD Definitions

No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.

No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.

No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.

2006 Martin v. Löwis. Data-centric XML. XML Schema (Part 1)

CAPACITY AUCTION SPECIFICATION DOCUMENT UML MODEL AND SCHEMA

[MS-OXWSMSHR]: Folder Sharing Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation

No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.

Service Modeling Language (SML) Pratul Dublish Principal Program Manager Microsoft Corporation

Request for Comments: 4481 Columbia U. Category: Standards Track July 2006

edmr2.0 XML Documentation Last Updated: 5/12/2010

Cisco Unity Connection Notification Interface (CUNI) API

Distribution List Creation and Usage Web Service Protocol

[MS-QDEFF]: Query Definition File Format. Intellectual Property Rights Notice for Open Specifications Documentation

RESERVE ALLOCATION RESULT DOCUMENT UML MODEL AND SCHEMA

BiTXml. M2M Communications Protocol. Rel

ETSI TS V1.3.0 ( )

AlwaysUp Web Service API Version 11.0

Oracle Enterprise Data Quality

ONVIF. XML Schema Version and Extension Handling White Paper

Status of this Memo. The list of current Internet-Drafts can be accessed at

Apache UIMA Regular Expression Annotator Documentation

Internet Engineering Task Force (IETF) Request for Comments: 6915 Updates: 6155 April 2013 Category: Standards Track ISSN:

Transcription:

Erratum Number: Document and Version: Cross References: QosDevice:1 Erratum Next sequential erratum number Effective Date: July 14, 2006 Document erratum applies to QosDevice:1 List other Erratum s or Documents that this change may apply to or have associated changes with This Erratum has been adopted by the UPnP Technical Committee and includes the following information: A unique Erratum number. The date it becomes effective. The document version to which this Erratum applies. A series of Errata entries (numbered) which list the effected section and page number in the document referenced here, the exiting text in the document with the text to be changed highlighted green and the clarified text with the text modified or added highlighted light blue. THE UPNP FORUM TAKES NO POSITION AS TO WHETHER ANY INTELLECTUAL PROPERTY RIGHTS EXIST IN THE PROPOSED TEMPLATES, IMPLEMENTATIONS OR IN ANY ASSOCIATED TEST SUITES. THIS ERRATUM IS PROVIDED "AS IS" AND "WITH ALL FAULTS". THE UPNP FORUM MAKES NO WARRANTIES, EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE WITH RESPECT TO THE PROPOSED SERVICE TEMPLATES INCLUDING BUT NOT LIMITED TO ALL IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINIGEMENT AND FITNESS FOR A PARTICULAR PURPOSE, OF REASONABLE CARE OR WORKMANLIKE EFFORT, OR RESULTS OR OF LACK OF NEGLIGENCE. 1999-2006 Contributing Members of the UPnP Forum. All Rights Reserved.

Entry 1 Document Section 2.3.3.1 XML Schema Definition Document 7 Page Background Schema Validation rules added. Current Text 2.3.3.1 XML Schema Definition <xs:schema xmlns="http://www.upnp.org/schemas/trafficdescriptorsperinterface.xsd" elementformdefault="qualified" targetnamespace="http://www.upnp.org/schemas/trafficdescriptorsperinterface.xsd" xmlns ="http://www.upnp.org/schemas" xmlns:xs="http://www.w3.org/2001/xmlschema"> <xs:import namespace="http://www.upnp.org/schemas" schemalocation="trafficdescriptorv1.xsd"/> <xs:annotation> <xs:documentation xml:lang="en"> Traffic Descriptors Per Interface schema. Copyright 2004 UPnP(tm). All rights reserved. </xs:documentation> </xs:annotation> <xs:element name="trafficdescriptorsperinterface"> <xs:element name="tdinterfacepair" minoccurs="0" maxoccurs="unbounded"> <xs:element name="upnp-qos:trafficdescriptor" minoccurs="1" maxoccurs="1" /> <xs:element name="interfaceid" type="xs:string" minoccurs="1" maxoccurs="unbounded" /> </xs:schema> New Text 2.3.3.1 XML Schema Definition <?xml version="1.0" encoding="utf-8"?> <xs:schema targetnamespace="http://www.upnp.org/schemas/trafficdescriptorsperinterface.xsd" xmlns="http://www.upnp.org/schemas/trafficdescriptorsperinterface.xsd" xmlns:td="http://www.upnp.org/schemas/trafficdescriptorv1.xsd" xmlns:xs="http://www.w3.org/2001/xmlschema" elementformdefault="qualified" id="trafficdescriptorsperinterface"> <xs:import namespace="http://www.upnp.org/schemas/trafficdescriptorv1.xsd" schemalocation="trafficdescriptorv1.xsd"/>

atum QosDevice:1 Err <xs:annotation> <xs:documentation xml:lang="en"> Traffic Descriptors Per Interface schema. Copyright 2004 UPnP(tm). All rights reserved. </xs:documentation> </xs:annotation> <xs:element name="trafficdescriptorsperinterface" type="trafficdescriptorsperinterfacetype"/> <xs:complextype name="trafficdescriptorsperinterfacetype"> <xs:element name="tdinterfacepair" minoccurs="0" maxoccurs="unbounded"> <xs:element name="trafficdescriptor" type="td:trafficdescriptortype"/> <xs:element name="interfaceid" type="xs:string" maxoccurs="unbounded"/> </xs:schema>

Entry 2 Document Section 2.3.3.3 Sample argument XML string Document 8 Page Background Revised examples based on revised schema. Current Text 2.3.3.3 Sample argument XML string <TrafficDescriptorsPerInterface xmlns="http://www.upnp.org/schemas/trafficdescriptorsperinterface.xsd xmlns:xs="http://www.w3.org/2001/xmlschema"> <TdInterfacePair> <TrafficDescriptor>... </TrafficDescriptor> <InterfaceId>eth0</InterfaceId> </TdInterfacePair> <TdInterfacePair> <TrafficDescriptor>... </TrafficDescriptor> <InterfaceId>eth0</InterfaceId> </TdInterfacePair> <TdInterfacePair> <TrafficDescriptor>... </TrafficDescriptor> <InterfaceId>eth0</InterfaceId> <InterfaceId>eth1</InterfaceId> </TdInterfacePair> <TrafficDescriptorsPerInterface> New Text 2.3.3.3 Sample argument XML string <TrafficDescriptorsPerInterface ="http://www.upnp.org/schemas/trafficdescriptorsperinterface.xsd" :xsi="http://www.w3.org/2001/xmlschema-instance" :schemalocation="http://www.upnp.org/schemas/trafficdescriptorsperinterface.xsd TrafficDescriptorsPerInterface.xsd"> <TdInterfacePair> <TrafficDescriptor> <TrafficHandle>kiwin1</TrafficHandle> <TrafficId> <SourceAddress> <Ipv4>192.168.1.50</Ipv4> </SourceAddress> <SourcePort>23</SourcePort> <DestinationAddress> <Ipv4>192.168.1.50</Ipv4> </DestinationAddress> <DestinationPort>23</DestinationPort> <IpProtocol>1</IpProtocol> </TrafficId>

atum QosDevice:1 Err <AvailableOrderedTspecList> <Tspec> <TspecIndex>300</TspecIndex> <TrafficClass>AV</TrafficClass> </Tspec> <Tspec> <TspecIndex>2</TspecIndex> <TrafficClass>Audio</TrafficClass> </Tspec> </AvailableOrderedTspecList> <ActiveTspecIndex>300</ActiveTspecIndex> <TrafficImportanceNumber>5</TrafficImportanceNumber> <OptionalPolicyParams> <CpName>Amy's CP</CpName> </OptionalPolicyParams> </TrafficDescriptor> <InterfaceId>eth0</InterfaceId> </TdInterfacePair> </TrafficDescriptorsPerInterface>

Entry 3 Document Section 2.3.6.1 XML Schema Definition Document 9 Page Background Schema Validation rules added. Current Text 2.3.6.1 XML Schema Definition <xs:schema xmlns="http://www.upnp.org/schemas/qosdevicecapabilities.xsd" elementformdefault="qualified" id="qosdevicecapabilities" xmlns:xs="http://www.w3.org/2001/xmlschema"> <xs:annotation> <xs:documentation xml:lang="en"> QosDeviceCapabilitiesschema. Copyright 2004 UPnP(tm). All rights reserved. </xs:documentation> </xs:annotation> <xs:element name="qosdevicecapabilities"> <xs:element name="interface" minoccurs="1" maxoccurs="unbounded"> <xs:element minoccurs="1" maxoccurs="1" name="interfaceid" type="xs:string" /> <xs:element minoccurs="0" maxoccurs="1" name="macaddress" type="macaddresstype" /> <xs:simpletype minoccurs="0" maxoccurs="1" name="ianatechnologytype" type="xs:integer" /> <xs:element minoccurs="1" maxoccurs="1" name="admissioncontrolsupported"> <xs:simpletype name="admissioncontroltype"> <xs:restriction base="xs:nmtoken"> <xs:enumeration value="no" /> <xs:enumeration value="yes" /> <xs:simpletype minoccurs="1" maxoccurs="1" name="nativeqos"> <xs:union membertypes="xs:string BasicNativeList"/> <xs:simpletype name="basicnativelist"> <xs:restriction base="xs:nmtoken">

<xs:enumeration value="prioritized" /> <xs:enumeration value="besteffort" /> <xs:element minoccurs="1" maxoccurs="1" name="maxphyrate" type="xs:unsignedint" /> <xs:any minoccurs="0" maxoccurs="unbounded" /> <xs:complextype name="macaddresstype"> <xs:element minoccurs="6" maxoccurs="8" name="octet-n" type="xs:byte" /> </xs:schema> New Text 2.3.6.1 XML Schema Definition <?xml version="1.0" encoding="utf-8"?> <xs:schema xmlns="http://www.upnp.org/schemas/qosdevicecapabilities.xsd" xmlns:xs="http://www.w3.org/2001/xmlschema" targetnamespace="http://www.upnp.org/schemas/qosdevicecapabilities.xsd" elementformdefault="qualified" id="qosdevicecapabilities"> <xs:annotation> <xs:documentation xml:lang="en"> QosDeviceCapabilities schema. Copyright 2004,2005 UPnP(tm). All rights reserved. </xs:documentation> </xs:annotation> <xs:element name="qosdevicecapabilities" type="qosdevicecapabilitiestype"/> <xs:complextype name="qosdevicecapabilitiestype"> <xs:element name="interface" maxoccurs="unbounded"> <xs:element name="interfaceid" type="xs:string"/> <xs:element name="macaddress" type="macaddresstype" minoccurs="0"/> <xs:element name="ianatechnologytype" type="xs:integer" minoccurs="0"/> <xs:element name="admissioncontrolsupported"> <xs:simpletype> <xs:restriction base="xs:string"> <xs:enumeration value="no"/> <xs:enumeration value="yes"/> <xs:element name="nativeqos" type="nativeqostype"/> <xs:element name="maxphyrate" type="xs:unsignedint"/> <xs:element name="v2" type="v2extensiontype" minoccurs="0"/> <!-- allow any element except those from target namespace --> <xs:choice minoccurs="0" maxoccurs="unbounded"> <xs:any namespace="##other" processcontents="lax"/> <xs:any namespace="##local" processcontents="lax"/>

atum QosDevice:1 Err </xs:choice> <xs:simpletype name="macaddresstype"> <xs:restriction base="xs:string"> <xs:pattern value="[0-9a-fa-f]{12}"/> <xs:simpletype name="nativeqostype"> <xs:union membertypes="basicnativelist xs:string"/> <xs:simpletype name="basicnativelist"> <xs:restriction base="xs:string"> <xs:enumeration value="prioritized"/> <xs:enumeration value="besteffort"/> <xs:complextype name="v2extensiontype"> <xs:any namespace="##targetnamespace" processcontents="lax" maxoccurs="unbounded"/> <xs:anyattribute/> </xs:schema>

Entry 4 Document Section 2.3.6.3 Sample argument XML string Document 10 Page Background Revised examples based on revised schema. Current Text 2.3.6.3 Sample argument XML string <QosDeviceCapabilities xmlns="http://www.upnp.org/schemas/ QosDeviceCapabilities.xsd"> <QosDeviceCapabilities> <Interface> <MacAddress>0212abcdef11</MacAddress> <InterfaceId>eth0</InterfaceId> <IanaTechnologyType>6</IanaTechnologyType> <NativeQos>Prioritized</NativeQos> <MaxPhyRate>100000000</MaxPhyRate> <AdmissionControlSupported>No</AdmissionControlSupported> </Interface> <Interface> <MacAddress>0212abcdef12</MacAddress> <InterfaceId>eth1</InterfaceId> <IanaTechnologyType>71</IanaTechnologyType> <NativeQos>Prioritized</NativeQos> <MaxPhyRate>3000000</MaxPhyRate> <AdmissionControlSupported>No</AdmissionControlSupported> </Interface> <Interface> <MacAddress>0212abcdef13</MacAddress> <InterfaceId>eth2</InterfaceId> <IanaTechnologyType>6</IanaTechnologyType> <NativeQos>BestEffort</NativeQos> <MaxPhyRate>5000000</MaxPhyRate> <AdmissionControlSupported>No</AdmissionControlSupported> </Interface> </QosDeviceCapabilities> New Text 2.3.6.3 Sample argument XML string <QosDeviceCapabilities xmlns="http://www.upnp.org/schemas/qosdevicecapabilities.xsd" xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" xsi:schemalocation="http://www.upnp.org/schemas/qosdevicecapabilities.xsd QosDeviceCapabilities.xsd"> <Interface> <InterfaceId>eth0</InterfaceId> <MacAddress>0212abcdef11</MacAddress> <IanaTechnologyType>6</IanaTechnologyType> <AdmissionControlSupported>No</AdmissionControlSupported>

atum QosDevice:1 Err <NativeQos>Prioritized</NativeQos> <MaxPhyRate>100000000</MaxPhyRate> </Interface> <Interface> <InterfaceId>eth1</InterfaceId> <MacAddress>0212abcdef12</MacAddress> <IanaTechnologyType>71</IanaTechnologyType> <AdmissionControlSupported>No</AdmissionControlSupported> <NativeQos>Prioritized</NativeQos> <MaxPhyRate>3000000</MaxPhyRate> </Interface> <Interface> <InterfaceId>eth2</InterfaceId> <MacAddress>0212abcdef13</MacAddress> <IanaTechnologyType>6</IanaTechnologyType> <AdmissionControlSupported>No</AdmissionControlSupported> <NativeQos>BestEffort</NativeQos> <MaxPhyRate>5000000</MaxPhyRate> </Interface> <Interface> <InterfaceId>example1</InterfaceId> <MacAddress>0212abcdefff</MacAddress> <IanaTechnologyType>12</IanaTechnologyType> <AdmissionControlSupported>No</AdmissionControlSupported> <NativeQos>BestEffort</NativeQos> <MaxPhyRate>5000000</MaxPhyRate> </Interface> </QosDeviceCapabilities>

Entry 5 Document Section 2.3.7.1 XML Schema Definition Document 11 Page Background Schema Validation rules added. Current Text 2.3.7.1 XML Schema Definition <xs:schema xmlns="http://www.upnp.org/schemas/qosdevicestate.xsd" elementformdefault="qualified" id="qosdevicestate" xmlns:xs="http://www.w3.org/2001/xmlschema"> <xs:annotation> <xs:documentation xml:lang="en"> QosDeviceState schema. Copyright 2004 UPnP(tm). All rights reserved. </xs:documentation> </xs:annotation> <xs:element name="qosdevicestate"> <xs:element minoccurs="1" maxoccurs="1" name="qosstateid" type="xs:string" /> <xs:element minoccurs="1" maxoccurs="unbounded" name="interface"> <xs:element minoccurs="1" maxoccurs="1" name="interfaceid" type="xs:string" /> <xs:element minoccurs="0" maxoccurs="4" name="ipaddress" type="ipaddresstype"/> <xs:element minoccurs="1" maxoccurs="1" name="interfaceavailability"> <xs:simpletype> <xs:restriction base="xs:nmtoken"> <xs:enumeration value="1" /> <xs:enumeration value="0" /> <xs:any minoccurs="0" maxoccurs="unbounded" /> <xs:any minoccurs="0" maxoccurs="unbounded" />

<xs:simpletype name="ipv4address"> <xs:restriction base="xs:string"> <xs:pattern value="(([1-9]?[0-9] 1[0-9][0-9] 2[0-4][0-9] 25[0-5])\.){3}([1-9]?[0-9] 1[0-9][0-9] 2[0-4][0-9] 25[0-5])" /> <xs:simpletype name="ipv6address"> <xs:restriction base="xs:hexbinary"> <xs:length value="32" /> <xs:complextype name="ipaddresstype"> <xs:choice> <xs:element name="ipv4" type="ipv4address" /> <xs:element name="ipv6" type="ipv6address" /> </xs:choice> <xs:element name="prefixlength"> <xs:simpletype> <xs:restriction base="xs:positiveinteger" minoccurs="0"> <xs:mininclusive value="1" /> <xs:maxinclusive value="128" /> New Text 2.3.7.1 XML Schema Definition <?xml version="1.0" encoding="utf-8"?> <xs:schema xmlns="http://www.upnp.org/schemas/qosdevicestate.xsd" xmlns:xs="http://www.w3.org/2001/xmlschema" targetnamespace="http://www.upnp.org/schemas/qosdevicestate.xsd" elementformdefault="qualified" id="qosdevicestate"> <xs:annotation> <xs:documentation xml:lang="en"> QosDeviceState schema. Copyright 2004 UPnP(tm). All rights reserved. </xs:documentation> </xs:annotation> <xs:element name="qosdevicestate" type="qosdevicestatetype"/> <xs:complextype name="qosdevicestatetype"> <xs:element name="qosstateid" type="xs:string"/> <xs:element name="interface" maxoccurs="unbounded"> <xs:element name="interfaceid" type="xs:string"/> <xs:element name="ipaddress" type="ipaddresstype" minoccurs="0" maxoccurs="4"/> <xs:element name="interfaceavailability"> <xs:simpletype> <xs:restriction base="xs:nmtoken"> <xs:enumeration value="1"/>

atum QosDevice:1 Err <xs:enumeration value="0"/> <xs:element name="v2" type="v2extensiontype" minoccurs="0"/> <!-- allow any element except those from target namespace --> <xs:choice minoccurs="0" maxoccurs="unbounded"> <xs:any namespace="##other" processcontents="lax"/> <xs:any namespace="##local" processcontents="lax"/> </xs:choice> <xs:simpletype name="ipv4address"> <xs:restriction base="xs:string"> <xs:pattern value="(([1-9]?[0-9] 1[0-9][0-9] 2[0-4][0-9] 25[0-5])\.){3}([1-9]?[0-9] 1[0-9][0-9] 2[0-4][0-9] 25[0-5])"/> <xs:simpletype name="ipv6address"> <xs:restriction base="xs:hexbinary"> <xs:length value="32"/> <xs:simpletype name="prefixlength"> <xs:restriction base="xs:positiveinteger"> <xs:mininclusive value="1"/> <xs:maxinclusive value="128"/> <xs:complextype name="ipaddresstype"> <xs:choice> <xs:element name="ipv4" type="ipv4address"/> <xs:element name="ipv6" type="ipv6address"/> </xs:choice> <xs:element name="prefixlength" type="prefixlength" minoccurs="0"/> <xs:complextype name="v2extensiontype"> <xs:any namespace="##targetnamespace" processcontents="lax" maxoccurs="unbounded"/> <xs:anyattribute/> </xs:schema>

Entry 6 Document Section 2.3.8 PathInformation Document 13 Page Background Schema Validation rules added. Current Text 2.3.8 PathInformation PathInformation is a structure that provides MAC address information about devices reachable through each active interface. 2.3.8.1 XML Schema Definition <xs:schema xmlns:xs="http://www.w3.org/2001/xmlschema" xmlns="http://www.upnp.org/schemas/pathinformation.xsd" targetnamespace="http://www.upnp.org/schemas/pathinformation.xsd" elementformdefault="qualified"> <xs:annotation> <xs:documentation xml:lang="en"> QosDevice PathInformation schema. Copyright 2004 UPnP(tm). All rights reserved. </xs:documentation> </xs:annotation> <xs:element name="devicereachablemacs"> <xs:element name="linkreachablemacs" minoccurs="1" maxoccurs="unbounded"> <xs:element name="linkid" type="xs:string" minoccurs="1" maxoccurs="1" /> <xs:element name="bridgeid" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="macaddress" type="macaddresstype" minoccurs= 0 maxoccurs="1" /> <xs:element name="reachablemac" type="macaddresstype" minoccurs="0" maxoccurs="unbounded" /> <xs:any minoccurs="0" maxoccurs="unbounded" /> <xs:any minoccurs="0" maxoccurs="unbounded" /> </xs:schema>

2.3.8.2 Description of fields in PathInformation structure LinkReachableMacs: This is a required field. A LinkReachableMacs definition is required for each available link supported by the device. For a device with physical media dedicated to an interface (such as Ethernet) there will be a LinkReachableMacs definition for each physical interface. For a device with a shared media (such as 802.11) there will be a LinkReachableMacs definition for each device pair where communication is supported by the device. LinkId: This is a required field. Its value is of type string, it must be unique within the device. It identifies the layer-2 link. MacAddress: This is a required field when available. Provides the MAC address of the interface for an end point device. ReachableMac: Provides the MAC address(es) of end point devices that are reachable through the link, if any. BridgedId: Identifies the links that are bridged together. All links that have the same BridgeID are interconnected within the device such that layer-2 frames are forwarded between them. 2.3.8.3 Sample argument XML string PC with two network interfaces This is an example of an end point network device with two network interfaces. <DeviceReachableMacs xmlns="http://www.upnp.org/schemas/qosdevice.xsd"> <LinkId>eth0</LinkId> <MacAddress>112233aabb03</MacAddress> <LinkId>eth1</LinkId> <MacAddress>112233aabb02</MacAddress> </DeviceReachableMacs> 2.3.8.4 Sample argument XML string PC with two network interfaces that are both end point device and bridged Similar to the previous example this is an example of an end point network device with two network interfaces. However this device all forwards layer-2 frames between the two network interfaces. <DeviceReachableMacs xmlns="http://www.upnp.org/schemas/qosdevice.xsd"> <LinkId>eth0</LinkId> <MacAddress>112233aabb03</MacAddress> <LinkId>eth1</LinkId> <MacAddress>112233aabb02</MacAddress> <LinkId>eth0</LinkId> <BridgeId>Bridge</BridgeId> <ReachableMac>112233aabb03</ReachableMac> <ReachableMac>112233aabb02</ReachableMac> <ReachableMac>112233aabb01</ReachableMac> <ReachableMac>112233aabb04</ReachableMac>

<LinkId>eth1</LinkId> <ReachableMac>112233aabb05</ReachableMac> </DeviceReachableMacs> 2.3.8.5 Sample argument XML string Four port Ethernet Switch This is an example of a layer-2 switching device that interconnects four physical Ethernet ports. The device supports layer-2 frame forwarding between all ports. <DeviceReachableMacs xmlns="http://www.upnp.org/schemas/qosdevice.xsd"> <LinkId>eth0</LinkId> <ReachableMac>112233aabb03</ReachableMac> <LinkId>eth1</LinkId> <ReachableMac>112233aabb07</ReachableMac> <ReachableMac>112233aabb05</ReachableMac> <LinkId>eth2</LinkId> <ReachableMac>112233aabb02</ReachableMac> <ReachableMac>112233aabb01</ReachableMac> <ReachableMac>112233aabb04</ReachableMac> <LinkId>eth3</LinkId> </DeviceReachableMacs> 2.3.8.6 Sample argument XML string Wireless AP with one Ethernet Interface This is an example of a wireless access point with three associated wireless stations and a single Ethernet port. The device supports layer-2 frame forwarding between all links. This includes forwarding between wireless station or to the Ethernet interface. <DeviceReachableMacs xmlns="http://www.upnp.org/schemas/qosdevice.xsd"> <LinkId>WL0</LinkId> <ReachableMac>112233aabb02</ReachableMac> <LinkId>WL1</LinkId> <ReachableMac>112233aabb01</ReachableMac> <LinkId>WL2</LinkId>

<ReachableMac>112233aabb04</ReachableMac> <ReachableMac>112233aabb09</ReachableMac> <LinkId>eth0</LinkId> <ReachableMac>112233aabb03</ReachableMac> <ReachableMac>112233aabb07</ReachableMac> <ReachableMac>112233aabb05</ReachableMac> </DeviceReachableMacs> 2.3.8.7 Sample argument XML string Bridge device between Wireless station and Ethernet This is an example of a bridging device with two interfaces on different network technologies. It does layer-2 forwarding of frames between wireless station interface and the wired Ethernet interface. <DeviceReachableMacs xmlns="http://www.upnp.org/schemas/qosdevice.xsd"> <LinkId>WL0</LinkId> <LinkId>eth0</LinkId> <ReachableMac>112233aabb04</ReachableMac> </DeviceReachableMacs >. New Text 2.3.8 PathInformation PathInformation is a structure that provides MAC address information about devices reachable through each active interface. 2.3.8.1 XML Schema Definition <?xml version="1.0" encoding="utf-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/xmlschema" xmlns="http://www.upnp.org/schemas/pathinformation.xsd" targetnamespace="http://www.upnp.org/schemas/pathinformation.xsd" elementformdefault="qualified" id="pathinformation"> <xs:annotation> <xs:documentation xml:lang="en"> QosDevice PathInformation schema. Copyright 2004 UPnP(tm). All rights reserved. </xs:documentation> </xs:annotation> <xs:element name="devicereachablemacs" type="devicereachablemacstype"/> <xs:complextype name="devicereachablemacstype"> <xs:element name="linkreachablemacs" maxoccurs="unbounded"> <xs:element name="linkid" type="xs:string"/> <xs:element name="bridgeid" type="xs:string" minoccurs="0"/> <xs:element name="macaddress" type="macaddresstype" minoccurs="0"/> <xs:element name="reachablemac" type="macaddresstype" minoccurs="0" maxoccurs="unbounded"/> <!-- allow any element except those from target namespace -->

<xs:choice minoccurs="0" maxoccurs="unbounded"> <xs:any namespace="##other" processcontents="lax"/> <xs:any namespace="##local" processcontents="lax"/> </xs:choice> <xs:element name="v2" type="v2extensiontype" minoccurs="0"/> <!-- allow any element except those from target namespace --> <xs:choice minoccurs="0" maxoccurs="unbounded"> <xs:any namespace="##other" processcontents="lax"/> <xs:any namespace="##local" processcontents="lax"/> </xs:choice> <xs:simpletype name="macaddresstype"> <xs:restriction base="xs:string"> <xs:pattern value="[0-9a-fa-f]{12}"/> <xs:complextype name="v2extensiontype"> <xs:any namespace="##targetnamespace" processcontents="lax" maxoccurs="unbounded"/> <xs:anyattribute/> </xs:schema> 2.3.8.2 Description of fields in PathInformation structure LinkReachableMacs: This is a required field. A LinkReachableMacs definition is required for each available link supported by the device. For a device with physical media dedicated to an interface (such as Ethernet) there will be a LinkReachableMacs definition for each physical interface. For a device with a shared media (such as 802.11) there will be a LinkReachableMacs definition for each device pair where communication is supported by the device. LinkId: This is a required field. Its value is of type string, it must be unique within the device. It identifies the layer-2 link. MacAddress: This is a required field when available. Provides the MAC address of the interface for an end point device. ReachableMac: Provides the MAC address(es) of end point devices that are reachable through the link, if any. BridgedId: Identifies the links that are bridged together. All links that have the same BridgeID are interconnected within the device such that layer-2 frames are forwarded between them. 2.3.8.3 Sample argument XML string PC with two network interfaces This is an example of an end point network device with two network interfaces. <DeviceReachableMacs xmlns="http://www.upnp.org/schemas/pathinformation.xsd" xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" xsi:schemalocation="http://www.upnp.org/schemas/pathinformation.xsd PathInformation.xsd"> <LinkId>eth0</LinkId> <MacAddress>112233aabb03</MacAddress>

<LinkId>eth1</LinkId> <MacAddress>112233aabb02</MacAddress> </DeviceReachableMacs> 2.3.8.4 Sample argument XML string PC with two network interfaces that are both end point device and bridged Similar to the previous example this is an example of an end point network device with two network interfaces. However this device all forwards layer-2 frames between the two network interfaces. <DeviceReachableMacs xmlns="http://www.upnp.org/schemas/pathinformation.xsd" xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" xsi:schemalocation="http://www.upnp.org/schemas/pathinformation.xsd PathInformation.xsd"> <LinkId>eth0</LinkId> <MacAddress>112233aabb03</MacAddress> <LinkId>eth1</LinkId> <MacAddress>112233aabb02</MacAddress> <LinkId>eth0</LinkId> <BridgeId>Bridge</BridgeId> <ReachableMac>112233aabb03</ReachableMac> <ReachableMac>112233aabb02</ReachableMac> <ReachableMac>112233aabb01</ReachableMac> <ReachableMac>112233aabb04</ReachableMac> <LinkId>eth1</LinkId> <ReachableMac>112233aabb05</ReachableMac> </DeviceReachableMacs> 2.3.8.5 Sample argument XML string Four port Ethernet Switch This is an example of a layer-2 switching device that interconnects four physical Ethernet ports. The device supports layer-2 frame forwarding between all ports. <DeviceReachableMacs xmlns="http://www.upnp.org/schemas/pathinformation.xsd" xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" xsi:schemalocation="http://www.upnp.org/schemas/pathinformation.xsd PathInformation.xsd"> <LinkId>eth0</LinkId> <ReachableMac>112233aabb03</ReachableMac> <LinkId>eth1</LinkId> <ReachableMac>112233aabb07</ReachableMac> <ReachableMac>112233aabb05</ReachableMac> <LinkId>eth2</LinkId> <ReachableMac>112233aabb02</ReachableMac> <ReachableMac>112233aabb01</ReachableMac>

<ReachableMac>112233aabb04</ReachableMac> <LinkId>eth3</LinkId> </DeviceReachableMacs> 2.3.8.6 Sample argument XML string Wireless AP with one Ethernet Interface This is an example of a wireless access point with three associated wireless stations and a single Ethernet port. The device supports layer-2 frame forwarding between all links. This includes forwarding between wireless station or to the Ethernet interface. <DeviceReachableMacs xmlns="http://www.upnp.org/schemas/pathinformation.xsd" xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" xsi:schemalocation="http://www.upnp.org/schemas/pathinformation.xsd PathInformation.xsd"> <LinkId>WL0</LinkId> <ReachableMac>112233aabb02</ReachableMac> <LinkId>WL1</LinkId> <ReachableMac>112233aabb01</ReachableMac> <LinkId>WL2</LinkId> <ReachableMac>112233aabb04</ReachableMac> <ReachableMac>112233aabb09</ReachableMac> <LinkId>eth0</LinkId> <ReachableMac>112233aabb03</ReachableMac> <ReachableMac>112233aabb07</ReachableMac> <ReachableMac>112233aabb05</ReachableMac> </DeviceReachableMacs> 2.3.8.7 Sample argument XML string Bridge device between Wireless station and Ethernet This is an example of a bridging device with two interfaces on different network technologies. It does layer-2 forwarding of frames between wireless station interface and the wired Ethernet interface. <DeviceReachableMacs xmlns="http://www.upnp.org/schemas/pathinformation.xsd" xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" xsi:schemalocation="http://www.upnp.org/schemas/pathinformation.xsd PathInformation.xsd"> <LinkId>WL0</LinkId> <LinkId>eth0</LinkId> <ReachableMac>112233aabb04</ReachableMac> </DeviceReachableMacs>

Entry 7 Document Section 2.3.9.1 XML Schema Definition Document 16 Page Background Schema Validation rules added. Current Text 2.3.9.1 XML Schema Definition <xs:schema xmlns:xs="http://www.w3.org/2001/xmlschema" xmlns="http://www.upnp.org/schemas/qosdeviceinfo.xsd" targetnamespace="http://www.upnp.org/schemas/qodeviceinfo.xsd" elementformdefault="qualified"> <xs:annotation> <xs:documentation xml:lang="en"> QoS Device Path Information schema. Copyright 2004 UPnP(tm). All rights reserved. </xs:documentation> </xs:annotation> <xs:element name="qosdeviceinfo"> <xs:element name="traffichandle" type="xs:string" minoccurs="1" maxoccurs="1"/> <xs:element name="sourceport" type="ipportnumber" minoccurs="0" maxoccurs="1"/> <xs:element name="destinationport" type="ipportnumber" minoccurs="0" maxoccurs="1" /> <xs:element name="ipprotocol" type=" IpProtocolType" minoccurs="1" maxoccurs="1"/> <xs:any minoccurs="0" maxoccurs="unbounded" /> <xs:simpletype name="ipportnumber"> <xs:restriction base="xs:positiveinteger"> <xs:mininclusive value="0" /> <xs:maxinclusive value="65535" /> <xs:simpletype name="ipprotocoltype"> <xs:restriction base="xs:nonnegativeinteger"> <xs:mininclusive value="0" /> <xs:maxinclusive value="255" />

</xs:schema> QosDevice:1 Erratum New Text 2.3.9.1 XML Schema Definition <?xml version="1.0" encoding="utf-8"?> <xs:schema xmlns="http://www.upnp.org/schemas/qosdeviceinfo.xsd" :xs="http://www.w3.org/2001/xmlschema" ="http://www.upnp.org/schemas/qosdeviceinfo.xsd" ="qualified" id="qosdeviceinfo"> <xs:annotation> <xs:documentation xml:lang="en"> QoS Device Information schema. Copyright 2004, 2005 UPnP(tm). All rights reserved. </xs:documentation> </xs:annotation> <xs:element name="qosdeviceinfo" type="qosdeviceinfotype"/> <xs:complextype name="qosdeviceinfotype"> <xs:element name="traffichandle" type="xs:string"/> <xs:element name="sourceport" type="ipportnumber" minoccurs="0"/> <xs:element name="destinationport" type="ipportnumber" minoccurs="0"/> <xs:element name="ipprotocol" type="ipprotocoltype"/> <xs:element name="v2" type="v2extensiontype" minoccurs="0"/> <!-- allow any element except those from target namespace --> <xs:choice minoccurs="0" maxoccurs="unbounded"> <xs:any namespace="##other" processcontents="lax"/> <xs:any namespace="##local" processcontents="lax"/> </xs:choice> <xs:simpletype name="ipportnumber"> <xs:restriction base="xs:nonnegativeinteger"> <xs:mininclusive value="0"/> <xs:maxinclusive value="65535"/> <xs:simpletype name="ipprotocoltype"> <xs:restriction base="xs:nonnegativeinteger"> <xs:mininclusive value="0"/> <xs:maxinclusive value="255"/> <xs:complextype name="v2extensiontype"> <xs:any namespace="##targetnamespace" processcontents="lax" maxoccurs="unbounded"/> <xs:anyattribute/> </xs:schema>

Entry 8 Document Section 2.5.3 SetupTrafficQos Document 19 Page Background Some of the input parameter restrictions could not be described by XML schema. Hence clarifications are added. Current Text 2.5.3 SetupTrafficQos SetupTrafficQoS interface indicates to the device to setup QoS for the Traffic described by A_ARG_TYPE_TrafficDescriptor. If there is no traffic descriptor with the same A_ARG_TYPE_TrafficHandle, then the traffic descriptor is registered in the device. If the device already has the traffic descriptor (identified by the traffic handle) registered, then the device must return an error (Error Code 702). Please refer to the [QM] document Appendix Traffic Descriptor Matrix for information about all of the fields of the TrafficDescriptor and how they are used. Typically, the QoS Manager calls this action only once per traffic handle registration. If the QoS Manager intends to update QoS associated with the traffic (e.g. the lease time of the traffic), then it has to go over the complete traffic setup process again after it has released the QoS. New Text 2.5.3 SetupTrafficQos SetupTrafficQoS interface indicates to the device to setup QoS for the Traffic described by A_ARG_TYPE_TrafficDescriptor. If there is no traffic descriptor with the same A_ARG_TYPE_TrafficHandle, then the traffic descriptor is registered in the device. If the device already has the traffic descriptor (identified by the traffic handle) registered, then the device must return an error (Error Code 702). Please refer to the [QM] document Appendix Traffic Descriptor Matrix for information about all of the fields of the TrafficDescriptor and how they are used. Typically, the QoS Manager calls this action only once per traffic handle registration. If the QoS Manager intends to update QoS associated with the traffic (e.g. the lease time of the traffic), then it has to go over the complete traffic setup process again after it has released the QoS. When QosManager supplies TrafficDescriptor to QosDevice when calling this action, it must provide TrafficImportanceNumber. If the TrafficImportanceNumber is not provided then QosDevice must return error 711 (Insufficient information) indicating that the input information is not complete. When QosManager supplies TrafficDescriptor to QosDevice when calling this action, it must provide ActiveTspecIndex. If the ActiveTspecIndex is not provided then QosDevice must return error 722.

If a QosManager does not supply a TrafficHandle in a TrafficDescriptor to QosDevice, the QosDevice must return error code 700. In the TrafficDescriptor to the QosDevice, the Tspec for which TrafficPolicy is provided is indicated by the ActiveTspecIndex. ActiveTspecIndex must be one of the TspecIndex values in the AvailableOrderedTspecList. If not, QosDevice must return an error code 723.

Entry 9 Document Section 2.5.4.3 Effect on State (if any) Document Page 20 Background Effect on QosStateId is clarified. Current Text 2.5.4.3 Effect on State (if any) After this call, traffic handle is no longer registered at the device to provide QoS. The device must release all its QoS resources allocated to that traffic. New Text 2.5.4.3 Effect on State (if any) After this call, traffic handle is no longer registered at the device to provide QoS. The device must release all its QoS resources allocated to that traffic. The QosStateId is no longer valid after the completion of this action. Hence the QosDevice must update the QosStateId after every successful completion of this action.