ISO/IEC 29341-17-12:2011

Information technology — UPnP Device Architecture — Part 17-12: Quality of Service Device Control Protocol — Level 3 — Quality of Service Policy Holder Service

ISO/IEC 29341-17-12:2011(E) describes the service type that enables modelling of the 'QosPolicyHolder' function capabilities. The functionality for the QosPolicyHolder Service can be implemented by any device on the network. The QosPolicyHolder Service is responsible for providing the traffic policy values for any given traffic stream as requested by an entity that manages the network traffic, typically a QoS Manager. The traffic policy values are determined by applying the policy rules, which are configured for the network, to the requested traffic information. This service definition is compliant with the UPnP Device Architecture version 1.0.

Technologies de l'information — Architecture de dispositif UPnP — Partie 17-12: Protocole de contrôle du dispositif de service de qualité — Niveau 3 — Qualité de service de support de politique de service

General Information

• Status: Published
• Publication Date: 29-Aug-2011
• ICS: 35.200 - Interface and interconnection equipment
• Technical Committee: ISO/IEC JTC 1 - Information technology
• Drafting Committee: ISO/IEC JTC 1 - Information technology
• Current Stage: 9060 - Close of review
• Start Date: 04-Jun-2027

Standards Content (Sample)

ISO/IEC 29341-17-12
Edition 1.0 2011-08
INTERNATIONAL
STANDARD

colour
inside

Information technology – UPnP device architecture –
Part 17-12: Quality of Service Device Control Protocol – Level 3 – Quality of
Service Policy Holder Service




ISO/IEC 29341-17-12:2011(E)

---------------------- Page: 1 ----------------------
THIS PUBLICATION IS COPYRIGHT PROTECTED
Copyright © 2011 ISO/IEC, Geneva, Switzerland


All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester.
If you have any questions about ISO/IEC copyright or have an enquiry about obtaining additional rights to this
publication, please contact the address below or your local IEC member National Committee for further information.

IEC Central Office
3, rue de Varembé
CH-1211 Geneva 20
Switzerland
Email: [e-mail]
Web: www.iec.ch

About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.
 Catalogue of IEC publications: www.iec.ch/searchpub
The IEC on-line Catalogue enables you to search by a variety of criteria (reference number, text, technical committee,…).
It also gives information on projects, withdrawn and replaced publications.
 IEC Just Published: www.iec.ch/online_news/justpub
Stay up to date on all new IEC publications. Just Published details twice a month all new publications released. Available
on-line and also by email.
 Electropedia: www.electropedia.org
The world's leading online dictionary of electronic and electrical terms containing more than 20 000 terms and definitions
in English and French, with equivalent terms in additional languages. Also known as the International Electrotechnical
Vocabulary online.
 Customer Service Centre: www.iec.ch/webstore/custserv
If you wish to give us your feedback on this publication or need further assistance, please visit the Customer Service
Centre FAQ or contact us:
Email: [e-mail]
Tel.: [phone]
Fax: [phone]

---------------------- Page: 2 ----------------------
ISO/IEC 29341-17-12
Edition 1.0 2011-08
INTERNATIONAL
STANDARD

colour
inside

Information technology – UPnP device architecture –
Part 17-12: Quality of Service Device Control Protocol – Level 3 – Quality of
Service Policy Holder Service


INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
P
ICS 35.200 ISBN 978-2-88912-646-0

---------------------- Page: 3 ----------------------
29341-17-12 © ISO/IEC:2011(E)
CONTENTS

1  Overview and Scope . 3
1.1  Referenced Specifications . 3
1.1.1  Normative References . 3
1.1.2  Informative References . 3
2  Service Modeling Definitions . 4
2.1  ServiceType . 4
2.2  Derived Data Types . 4
2.2.1  XML Fragments as UPnP Arguments . 4
2.2.2  Extensibility of XML . 4
2.3  State Vari ables . 6
2.3.1  A_ARG_TYPE_TrafficDescriptor . 6
2.3.2  A_ARG_TYPE_Tra ffic Polic y . 6
2.3.3  A_ARG_TYPE_ListOfTrafficDescriptors . 8
2.3.4  A_ARG_TYPE_ListOfTrafficPolicies . 8
2.3.5  A_ARG_TYPE_IsPreferred . 9
2.3.6  A_ARG_TYPE_QphPolicyRule . 9
2.3.7  A_ARG_TYPE_ListOfQphPolicyRule . 13
2.3.8  A_ARG_TYPE_Position . 14
2.3.9  A_ARG_TYPE_TIN . 14
2.3.10  A_ARG_TYPE_IN . 14
2.3.11  A_ARG_TYPE_ReasonCode . 14
2.3.12  A_ARG_TYPE_PolicyHandl e . 15
2.3.13  A_ARG_TYPE_ListPolicyHandle . 15
2.3.14  PolicyVer s i on . 15
2.3.15  Relationships Between State Variables . 15
2.4  Eventing and Moderation . 16
2.4.1  Event Model. 16
2.5  Actions . 16
2.5.1  GetTrafficPolicy . 17
2.5.2  GetListOfTrafficPolicies . 18
2.5.3  SetAsPreferred . 20
2.5.4  AddQphPolicy . 22
2.5.5  RemoveQphPolicy . 23
2.5.6  RetrieveQphPolicy . 24
2.5.7  GetPolicyVersion . 24
2.5.8  Non-Standard Actions Implemented by a UPnP Vendor . 25
2.5.9  Error Code Summary . 25
3  Theory of Operation (Informative) . 27
3.1  Retrieving Po lic ies . 27
3.2  Preferred QosPolicyHolder Service Selectio n . 27
3.3  QosPolicyHolder Service Configur ation . 28
4  XML Service Description . 29
5  Test . . 32

---------------------- Page: 4 ----------------------
XXXX: © IEC:2010 — 2 — 29341-17-12 © ISO/IEC:2011(E)
Table 2-1 — State Variables . 6
Table 2-2 — Event Moderat ion . 16
Table 2-3 — Actions . 16
Table 2-4 — Arguments for GetTrafficPolicy . 17
Table 2-5 — Error Codes for GetTrafficPolicy . 18
Table 2-6 — Arguments for GetListOfTrafficPolicies . 18
Table 2-7 — Error Codes for GetListOfTrafficPolicie s . 19
Table 2-8 — Arguments for SetAsPreferred . 20
Table 2-9 — Error Codes for SetAsPreferred . 22
Table 2-10 — Arguments for AddQphPolicy . 22
Table 2-11 — Reason code for AddQphPolicy . 23
Table 2-12 — Error code for AddQphPolicy . 23
Table 2-13 — Arguments for RemoveQphPolicy . 23
Table 2-14 — Error code for RemoveQphPolicy . 23
Table 2-15 — Arguments for RetrieveQp hPolic y . 24
Table 2-16 — Arguments for GetPolicyVersion . 25
Table 2-17 — Common Error Codes . 26

---------------------- Page: 5 ----------------------
29341-17-12 © ISO/IEC:2011(E)
INFORMATION TECHNOLOGY –
UPNP DEVICE ARCHITECTURE –
Part 17-12: Quality of Service Device Control Protocol –
Level 3 – Quality of Service Policy Holder Service
FOREWORD
1) ISO (International Organization for Standardization) and IEC (International Electrotechnical Commission) form the
specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in
the development of International Standards. Their preparation is entrusted to technical committees; any ISO and
IEC member body interested in the subject dealt with may participate in this preparatory work. International
governmental and non-governmental organizations liaising with ISO and IEC also participate in this preparation.
2) In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting.
Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote.
3) The formal decisions or agreements of IEC and ISO on technical matters express, as nearly as possible, an
international consensus of opinion on the relevant subjects since each technical committee has representation
from all interested IEC and ISO member bodies.
4) IEC, ISO and ISO/IEC publications have the form of recommendations for international use and are accepted
by IEC and ISO member bodies in that sense. While all reasonable efforts are made to ensure that the
technical content of IEC, ISO and ISO/IEC publications is accurate, IEC or ISO cannot be held responsible for
the way in which they are used or for any misinterpretation by any end user.
5) In order to promote international uniformity, IEC and ISO member bodies undertake to apply IEC, ISO and
ISO/IEC publications transparently to the maximum extent possible in their national and regional publications.
Any divergence between any ISO/IEC publication and the corresponding national or regional publication
should be clearly indicated in the latter.
6) ISO and IEC provide no marking procedure to indicate their approval and cannot be rendered responsible for
any equipment declared to be in conformity with an ISO/IEC publication.
7) All users should ensure that they have the latest edition of this publication.
8) No liability shall attach to IEC or ISO or its directors, employees, servants or agents including individual experts
and members of their technical committees and IEC or ISO member bodies for any personal injury, property
damage or other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees)
and expenses arising out of the publication of, use of, or reliance upon, this ISO/IEC publication or any other IEC,
ISO or ISO/IEC publications.
9) Attention is drawn to the normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
10) Attention is drawn to the possibility that some of the elements of this International Standard may be the subject of
patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
International Standard ISO/IEC 29341-17-12 was prepared by UPnP Forum Steering
1
committee , was adopted, under the fast track procedure, by subcommittee 25:
Interconnection of information technology equipment, of ISO/IEC joint technical committee 1:
Information technology.
The list of all currently available parts of the ISO/IEC 29341 series, under the general title
Information technology – UPnP device architecture, can be found on the IEC web site.
This International Standard has been approved by vote of the member bodies, and the voting
results may be obtained from the address given on the second title page.

—————————
rd
1
 UPnP Forum Steering committee, UPnP Forum, 3855 SW 153 Drive, Beaverton, Oregon 97006 USA. See also
“Introduction”.

---------------------- Page: 6 ----------------------
29341-17-12 © ISO/IEC:2011(E)

IMPORTANT – The “colour inside” logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct understanding
of its contents. Users should therefore print this publication using a colour printer.

---------------------- Page: 7 ----------------------
29341-17-12 XXXX: © IEC:2010 © ISO/IEC:2011(E) — 3 —
1 Overview and Scope
This service definition is compliant with the UPnP Device Architecture version 1.0.
This service type enables modeling of the ‘QosPolicyHolder’ function capabilities. The
functionality for the QosPolicyHolder Service can be implemented by any device on the
network. The QosPolicyHolder Service is responsible for providing the traffic policy values
for any given traffic stream as requested by an entity that manages the network traffic,
typically a QoS Manager. The traffic policy values are determined by applying the policy
rules, which are configured for the network, to the requested traffic information.
A QosPolicyHolder is a dual-role entity that exposes a QosPolicyHolder Service to the
Control Point (mainly the QoS Manager) while acting as a Control Point for the QosDevice
Services running on the network. This document describes the components of the
QosPolicyHolder Service and the QoS Policy Holder. The QoS Policy Holder provides the
Control Point functionality that discovers and controls QosDevice Services, mainly for the
propagation and synchronization of the preferred QosPolicyHolder Service information.
Additional information concerning the QoS Policy Holder may be found in:
• UPnP-QoS Architecture document
• UPnP QosDevice Service Definition Document
1.1 Referenced Specifications
Unless explicitly stated otherwise herein, implementation of the mandatory provisions of any
standard referenced by this specification shall be mandatory for compliance with this
specification.
1.1.1 Normative References
This clause lists the normative references used in this document and includes the tag inside
square brackets that is used for each sub reference:
[XML] – Extensible Markup Language (XML) 1.0 (Second Edition), T. Bray, J.Paoli, C. M.
Sperberg-McQueen, E Maler, eds. W3C Recommendations, 6 October 2000.
[DEVICE] - UPnP Device Architecture, version 1.0, UPnP Forum, July 20, 2006.
Available at: http://upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0-20060720.pdf
Latest version available at: http://upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-
v1.0.pdf
[QM] – UPnP QosManager:3 Service Document: This reference is informative except for the
definitions of the following state variables, which are normative:
A_ARG_TYPE_TrafficDescriptor, and A_ARG_TYPE_ListOfTrafficDescriptors.
Available at: http://www.upnp.org/specs/qos/UPnP-qos-QosManager-v3-Service-
20081130.pdf
Latest version available at: http://www.upnp.org/specs/qos/UPnP-qos-QosManager-v3-
Service.pdf
[RFC3339] – Date and Time on the Internet: Timestamps, G. Klyne, July 2002.
http://www.ietf.org/rfc/rfc3339.txt
1.1.2 Informative References
This clause lists the informative references used in this document and includes the tag inside
square brackets that is used for each sub reference:

---------------------- Page: 8 ----------------------
XXXX: © IEC:2010 — 4 — 29341-17-12 © ISO/IEC:2011(E)
[QoS Architecture] – UPnP QoS Architecture V3.0
Available at: http://www.upnp.org/specs/qos/UPnP-qos-Architecture-v3-20081130.pdf
Latest version available at: http://www.upnp.org/specs/qos/UPnP-qos-Architecture-v3.pdf
[QoS DEV] – UPnP QosDevice:3 Service Document
Available at: http://www.upnp.org/specs/qos/UPnP-qos-QosDevice-v3-Service-20081130.pdf
Latest version available at: http://www.upnp.org/specs/qos/UPnP-qos-QosDevice-v3-
Service.pdf
[IEEE 802.1D] – IEEE 802.1D-2004, Annex G, IEEE Standard for Information technology -
Telecommunications and information exchange between systems - IEEE standard for local
and metropolitan area networks - Common specifications - Media access control (MAC)
Bridges, 2004.
2 Service Modeling Definitions
2.1 ServiceType
The following service type identifies a service that is compliant with this template:
urn:schemas-upnp-org:service:QosPolicyHolder:3
The shorthand ‘QosPolicyHolder Service’ is used herein to refer to this service type.
2.2 Derived Data Types
This clause defines some derived data types that are represented as UPnP string data types
with special syntax.
2.2.1 XML Fragments as UPnP Arguments
UPnP-QoS often uses XML Fragments as arguments in UPnP actions. The containing UPnP
data type is a string. This places restrictions on a string’s content; it has to represent a well-
formed XML fragment (this includes a complete XML document).
An XML fragment, in adherence to the UPnP Device Architecture 1.0 [DEVICE], MUST be
escaped by using the normal XML rules, [XML] Clause 2.4 Character Data and Markup,
before embedding it in a SOAP request / response message or an event notification
message. The XML escaping rules are summarized:
• The (<) character is encoded as (<)
• The (>) character is encoded as (>)
• The (&) character is encoded as (&)
• The (”) character is encoded as (")
• The (‘) character is encoded as (')
In their XML fragments, implementations MAY use an explicit reference to appropriate
namespaces.
2.2.2 Extensibility of XML
The names of UPnP-QoS namespaces come in two flavors. The ones in HTTP-form are
existing UPnP-QoS v1 and v2 namespace names. The ones in URN-form are introduced in
UPnP-QoS v3 (or later).

---------------------- Page: 9 ----------------------
29341-17-12 XXXX: © IEC:2010 © ISO/IEC:2011(E) — 5 —
In order to maintain the extensibility of a namespace, all future modifications of the schema
definition will be proper supersets. The namespace name will not change even when the
service version number changes.
The v2, v3, v4 tags within a schema allow for the UPnP Forum to add newly standardized
elements to the schema definitions without impacting implementations based on previous
version(s) of the schema. UPnP-QoS v3 introduces the v4 tags in a similar way as UPnP-QoS
v2 defined the v3 tags. The contents of the v4 tags MAY be (re)defined in UPnP-QoS v4
depending on needs.
At several places in the XML schemas there is also room for vendor differentiation or future
revisions through the use of the “any”-tag. This tag is placed both in the original schema as
well as within the v2 and v3 tags to allow extensions related to those versions of the
specification.
When extending UPnP-QoS with their own XML tags, vendors SHOULD use a namespace to
prevent collisions of their tags with those of other vendors. It is RECOMMENDED that
implementations are not required to retrieve the corresponding schemas from the Internet.
For example, a vendor MAY provide its own enhancements within the schema.
Below is an example using extensions to TrafficPolicy v2
 xmlns="http://www.upnp.org/schemas/TrafficPolicy.xsd"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:prv="http://myPrivate.com"
 xmlns:prv2="http://myPrivate2.com"
 xlmns:prv3="urn:schemas-myprivate-com:v3Extensions"
 xlmns:prv4="urn:schemas-myprivate-com:v4Extensions"
 xsi:schemaLocation="http://www.upnp.org/schemas/TrafficPolicy.xsd
  http://www.upnp.org/schemas/qos/TrafficPolicy-v2.xsd">
  Enabled
  3
  128
  
   
  uuid:2fac1234-31f8-11b4-a222-08002b34c003:serviceId:qph
 
    2004-11-26T15:03:23-08:00
    Jimmy
   
  http://10.0.0.5/ConfPolicy.html
 
     
       
          
         
          whatever
           
        whatever
       
    whatever
  
  whatever


---------------------- Page: 10 ----------------------
XXXX: © IEC:2010 — 6 — 29341-17-12 © ISO/IEC:2011(E)
2.3 State Variables
The QosPolicyHolder Service is ‘action’ based. This service’s state variables exist primarily
to support argument passing of the service’s actions. A client retrieves QosPolicyHolder
Service information via the return parameters of the actions defined in clause 2.5.
Reader Note: For first-time reader, it may be more insightful to read the theory of
operations first and then the action definitions before reading the state variable
definitions.
Table 2-1 — State Variables
Variable Name Req. or Data Type Allowed Value Default Eng.

a b Units
Opt. Value
A_ARG_TYPE_TrafficDescriptor R string See clause 2.3.1 n/a n/a
(XML
fragment)
A_ARG_TYPE_TrafficPolicy R string See clause 2.3.2 n/a n/a
(XML
fragment)
A_ARG_TYPE_ListOfTrafficDescriptors R See clause 2.3.3 n/a n/a
string
(XML
fragment)
A_ARG_TYPE_ListOfTrafficPolicies R string See clause 2.3.4 n/a n/a
(XML
fragment)
A_ARG_TYPE_IsPreferred O See clause 2.3.5 False n/a
boolean
A_ARG_TYPE_QphPolicyRule O string See clause 2.3.6 n/a n/a
(XML
fragment)
A_ARG_TYPE_ListOfQphPolicyRule O string See clause 2.3.7 n/a n/a
(XML
fragment)
A_ARG_TYPE_Position O ui4 See clause 2.3.8 n/a n/a
A_ARG_TYPE_TIN O ui4 See clause 2.3.9 n/a n/a
A_ARG_TYPE_IN O ui4 See clause 2.3.10 n/a n/a
A_ARG_TYPE_ReasonCode O ui4 See clause 2.3.11 n/a n/a
A_ARG_TYPE_PolicyHandle O ui4 See clause 2.3.12 n/a n/a
A_ARG_TYPE_ListPolicyHandle O String (XML See clause 2.3.13 n/a n/a
fragment)
PolicyVersion O ui4 See clause 2.3.14 n/a n/a
a
R = Required, O = Optional, X = Non-standard
b
Values listed in this column are required. To specify standard optional values or to delegate assignment of

values to the vendor, you must reference a specific instance of an appropriate table below.
2.3.1 A_ARG_TYPE_TrafficDescriptor
This is a string containing an XML fragment. It contains information describing a traffic
descriptor. Refer to the UPnP QosManager:3 [QM] for details of this XML document using the
namespace.
2.3.2 A_ARG_TYPE_TrafficPolicy
This is a string containing an XML fragment. It contains information describing TrafficPolicy
information. The XML fragment in this argument MUST validate against the XML schema for
TrafficPolicy in the XML namespace

---------------------- Page: 11 ----------------------
29341-17-12 XXXX: © IEC:2010 © ISO/IEC:2011(E) — 7 —
“http://www.upnp.org/schemas/TrafficPolicy.xsd” which is located at
http://www.upnp.org/schemas/qos/TrafficPolicy-v2.xsd.
2.3.2.1 Description of fields in the TrafficPolicy structure
TrafficPolicy structure consists of the following seven elements:
• AdmissionPolicy is a required field and is set to “Enabled”.
• TrafficImportanceNumber is a required field of type integer with values in the range of
0 through 7. This value conforms to the numbering scheme for traffic classes as
described in IEEE 802.1D Annex G [IEEE 802.1D] and with additional traffic classes
[QM]. This value is used by QosDevice service(s) in
described in the QosManager:3
the traffic’s path to indicate what priority level to utilize when priority tagging the
traffic’s network packets.
• UserImportanceNumber is a required field of type integer with values in the range of 0
through 255. This is used by a QoS Manager for Preemption. This value is applicable
only when the AdmissionPolicy is enabled. Note that a value of 255 is the highest
user importance and 0 is the lowest.
• PolicyHolderId is an optional field. Refer to the PolicyHolderId field in the
TrafficDescriptor structure in the QosManager:3 [QM] for the definition and more
details.
• PolicyLastModified is an optional field. Refer to the PolicyLastModified field in the
structure in the QosManager:3 [QM] for the definition and more
TrafficDescriptor
details.
• PolicyModifyingUserName is an optional field. Refer to the PolicyModifyingUserName
field in the TrafficDescriptor structure in the QosManager:3 [QM] for the definition and
more details.
• PolicyHolderConfigUrl is an optional field. Refer to the PolicyHolderConfigUrl field in
the TrafficDescriptor structure in the QosManager:3 [QM] for the definition and more
details.
2.3.2.2 Sample Argument XML String
Illustrated below are two separate examples of TrafficPolicy structure.
Example 1:

 xmlns="http://www.upnp.org/schemas/TrafficPolicy.xsd"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://www.upnp.org/schemas/TrafficPolicy.xsd
 http://www.upnp.org/schemas/qos/TrafficPolicy-v2.xsd">
Enabled
3
128

 
  uuid:2fac1234-31f8-11b4-a222-08002b34c003:urn:upnp-
org:serviceId:QosPolicyHolder-3a
 
 2004-11-26T15:03:23-08:00
 Jimmy
 
  http://10.0.0.50/ConfigPolicy.html
 


Example 2:


---------------------- Page: 12 ----------------------
XXXX: © IEC:2010 — 8 — 29341-17-12 © ISO/IEC:2011(E)
 xmlns="http://www.upnp.org/schemas/TrafficPolicy.xsd"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://www.upnp.org/schemas/TrafficPolicy.xsd
 http://www.upnp.org/schemas/qos/TrafficPolicy-v2.xsd">
Enabled
5

 
  uuid:2fac1234-31f8-11b4-a222-08002b34c003:urn:upnp-
org:serviceId:QosPolicyHolder-3b
 
 
  http://10.0.0.50/ConfigPolicy.html
 


2.3.3 A_ARG_TYPE_ListOfTrafficDescriptors
This is a string containing an XML fragment. It contains information describing
ListOfTrafficDescriptors structure. This structure contains a list of traffic descriptor each with
the information for a traffic stream. Refer to the UPnP QosManager:3 [QM] for details of this
XML document using the namespace.
2.3.4 A_ARG_TYPE_ListOfTrafficPolicies
This is a string containing an XML fragment. It contains information describing the
ListOfTrafficPolicies structure. This structure contains traffic policies for a list of traffic
streams. The XML fragment in this argument MUST validate against the XML schema for
ListOfTrafficPolicies in the XML namespace "urn:schemas-upnp-
org:qos:ListOfTrafficPolicies" which is located at
http://www.upnp.org/schemas/qos/ListOfTrafficPolicies-v3.xsd.
2.3.4.1 Description of fields in the ListOfTrafficPolicies structure
The ListOfTrafficPolicies structure consists of the following elements.
AdmissionPolicy: This is a required field. Refer to clause 2.3.2.1 for details.
PolicyHolderId: This is a required field. Refer to the PolicyHolderId field in the
TrafficDescriptor structure in the QoS
...