ISO/IEC 29341-18-10:2011

ISO/IEC 29341-18-10
Edition 1.0 2011-08
INTERNATIONAL
STANDARD
colour
inside
Information technology – UPnP device architecture –
Part 18-10: Remote Access Device Control Protocol – Remote Access Inbound
Connection Configuration Service

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: inmail@iec.ch
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: csc@iec.ch
Tel.: +41 22 919 02 11
Fax: +41 22 919 03 00
ISO/IEC 29341-18-10
Edition 1.0 2011-08
INTERNATIONAL
STANDARD
colour
inside
Information technology – UPnP device architecture –
Part 18-10: Remote Access Device Control Protocol – Remote Access Inbound
Connection Configuration Service

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
G
ICS 35.200 ISBN 978-2-88912-650-7

29341-18-10 © ISO/IEC:2011(E)
CONTENTS
1  Overview and Scope . 3
1.1  Introduction . 3
1.2  Notation . 3
1.3  Vendor-defined Extensions . 4
1.4  References . 4
1.4.1  Normative References . 4
1.4.2  Informative References . 4
2  Service Modeling Definitions . 5
2.1  Service Type . 5
2.2  Terms and Abbreviations . 5
2.2.1  Abbrevia tions . 5
2.3  InboundConnectionConfig Service Arch itec ture . 5
2.4  State Vari ables . 5
2.4.1  State Variable Overview . 5
2.4.2  DynamicDNSSupportedProtocols . 6
2.4.3  DynamcDNSConfigInfo . 6
2.4.4  STUNServerAddress . 6
2.4.5  NetworkTopologyInfo . 6
2.5  Eventing and Moderation . 7
2.5.1  Relationships Between State Variables . 7
2.6  Actions . 7
2.6.1  GetDynamicDNSSupportedProtocols() . 7
2.6.2  SetDynamicDNSConfigInfo() . 8
2.6.3  SetSTUNServerAddress() . 9
2.6.4  GetNetworkTopologyInfo() . 9
2.6.5  Relationships Between Actions . 11
2.6.6  Error Code Summary . 11
2.7  Theory of Operation . 11
3  XML Service Description . 12
4  Test . . 13
Annex A (normative) InboundConnectionConfig Data Structures . 14
A.1  DynamicDNSConfig Templa te . 14
A.2  NetworkTopologyInfo Template . 15

Table 2-1 — Abbreviati ons . 5
Table 2-2 — State Variables . 5
Table 2-3 — Eventing and Moderation . 7
Table 2-4 — Actions . 7
Table 2-5 — Arguments for GetDynamicDNSSupportedProtocols() . 7
Table 2-6 — Error Codes for GetDynamicDNSSupportedProtocols() . 8
Table 2-7 — Arguments for SetDynamicDNSConfigInfo() . 8
Table 2-8 — Error Codes for SetDynamicDNSConfigInfo() . 9
Table 2-9 — Arguments for SetSTUNServerAddress() . 9

XXXX: © IEC:2010 — 2 — 29341-18-10 © ISO/IEC:2011(E)

Table 2-10 — Error Codes for SetSTUNServerAddress() . 9
Table 2-11 — Arguments for GetNetworkTopologyInfo() . 10
Table 2-12 — NetworkTopologyInfo meaning in UPnP Remote Access 1.0 . 10
Table 2-13 — Error Codes for GetNetworkTopologyInfo() . 11
Table 2-14 — Error Code Summary . 11

29341-18-10 © ISO/IEC:2011(E)
INFORMATION TECHNOLOGY –
UPNP DEVICE ARCHITECTURE –
Part 18-10: Remote Access Device Control Protocol –
Remote Access Inbound Connection Configuration 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-18-10 was prepared by UPnP Forum Steering
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
UPnP Forum Steering committee, UPnP Forum, 3855 SW 153 Drive, Beaverton, Oregon 97006 USA. See also
“Introduction”.
29341-18-10 © 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.

29341-18-10 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. It defines
a service type referred to herein as InboundConnectionConfig service.
1.1 Introduction
service is a UPnP service that allows control points to
The InboundConnectionConfig
configure the parameters that will enable the service to test if the host device is reachable
from the internet. InboundConnectionConfig uses Dynamic DNS to manage at least one
public address for home-network services; it uses STUN to ensure that any intermediate NAT
device is navigatable, i.e. it is a full-cone NAT. Thus, this service provides control points with
the following functionality:
• Configure the dynamic DNS client co-located with the service,
• Configure the STUN client co-located with the service,
• Check if the device hosting the service is reachable from the internet.
This service does not address:
• Configuration of relay services in the public network, e.g. TURN.
1.2 Notation
• In this document, features are described as Required, Recommended, or Optional as
follows:
The key words “MUST,” “MUST NOT,” “REQUIRED,” “SHALL,” “SHALL NOT,” “SHOULD,”
“SHOULD NOT,” “RECOMMENDED,” “MAY,” and “OPTIONAL” in this specification are to
be interpreted as described in [RFC 2119].
In addition, the following keywords are used in this specification:
PROHIBITED – The definition or behavior is an absolute prohibition of this specification.
Opposite of REQUIRED.
CONDITIONALLY REQUIRED – The definition or behavior depends on a condition. If the
specified condition is met, then the definition or behavior is REQUIRED, otherwise it is
PROHIBITED.
CONDITIONALLY OPTIONAL – The definition or behavior depends on a con
...