Information technology - UPnP Device Architecture - Part 18-3: Remote Access Device Control Protocol - Remote Access Server Device

ISO/IEC 29341-18-3:2011(E) includes the device definition which is compliant with the UPnP Device Architecture version 1.0. It defines a device type referred to herein as RAServer Device. The RAServer Device is a UPnP Device UPnP device that allows control points to configure Remote Access Servers. This Device provides control points with the following functionality: - Determine if the Remote Access Server is reachable from the public Internet; - Enable a Remote Access Server to be reachable from the public Internet; - Enumerate the Remote Access Transport mechanisms supported by the Remote Access Server; - Enumerate the Credentials Delivery mechanisms supported by the Remote Access Server; - Configure active Remote Access Transport profiles; - Configure filters for allowing which local Devices are visible in remote networks; - Configure filters for allowing which remote Devices are visible in the local network; - Maintains list of registered remote users, and authenticates when they log in depending on their pre-configured info appropriately.

General Information

Status
Published
Publication Date
29-Aug-2011
Current Stage
PPUB - Publication issued
Start Date
30-Nov-2011
Completion Date
29-Aug-2011
Ref Project

Buy Standard

Standard
ISO/IEC 29341-18-3:2011 - Information technology - UPnP device architecture - Part 18-3: Remote Access Device Control Protocol - Remote Access Server Device
English language
6 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


ISO/IEC 29341-18-3
Edition 1.0 2011-08
INTERNATIONAL
STANDARD
colour
inside
Information technology – UPnP device architecture –
Part 18-3: Remote Access Device Control Protocol – Remote Access Server
Device
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-3
Edition 1.0 2011-08
INTERNATIONAL
STANDARD
colour
inside
Information technology – UPnP device architecture –
Part 18-3: Remote Access Device Control Protocol – Remote Access Server
Device
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
C
ICS 35.200 ISBN 978-2-88912-651-4

29341-18-3 © ISO/IEC:2011(E)
CONTENTS
1  Overview and Scope . 2
1.1  Introduction . 2
1.2  Notation . 2
1.3  Vendor-defined Extensions . 3
1.4  References . 3
1.4.1  Normative References . 3
1.4.2  Informative References . 3
2  Device Definitions . 4
2.1  Device Type . 4
2.2  Terms and Abbreviations . 4
2.2.1  Abbrevia tions . 4
2.2.2  Terms . 4
2.3  RAServer Device Architecture . 5
2.4  Device Model . 5
2.4.1  Description of Device Require ments . 6
2.5  Theory of Operation . 6
3  XML Device Description . 6
4  Test . 7

Figure 2-1 — RAServer Device Archit ec ture. . 5

Table 2-1 — Abbreviati ons . 4
Table 2-2 — Device Require ments . 6

29341-18-3 © ISO/IEC:2011(E)
INFORMATION TECHNOLOGY –
UPNP DEVICE ARCHITECTURE –
Part 18-3: Remote Access Device Control Protocol –
Remote Access Server Device
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-3 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-3 © 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.

XXX: © IEC:2010 — 2 — 29341-18-3 © ISO/IEC:2011(E)
1 Overview and Scope
This device definition is compliant with the UPnP Device Architecture version 1.0. It defines a
device type referred to herein as RAServer Device.
1.1 Introduction
Device is a UPnP Device UPnP device that allows control points to configure
The RAServer
Remote Access Servers. This Device provides control points with the following functionality:
• Determine if the Remote Access Server is reachable from the public Internet
• Enable a Remote Access Server to be reachable from the public Internet
• Enumerate the Remote Access Transport mechanisms supported by the Remote Access
Server
• Enumerate the Credentials Delivery mechanisms supported by the Remote Access Server
• Configure active Remote Access Transport profiles
• Configure filters for allowing which local Devices are visible in remote networks
• Configure filters for allowing which remote Devices are visible in the local network
• Maintains list of registered remote users, and authenticates when they log in depending
on their pre-configured info appropriately
This Device does not address:
• Control level and content level Access Control for local Devices which are exposed to
remote networks
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 condition. If the
specified condition is met, then the definition or behavior is OPTIONAL, otherwise it is
PROHIBITED.
These keywords are thus capitalized when used to unambiguously specify requirements
over protocol and application features and behavior that affect the interoperability and
security of implementations. When these words are not capitalized, they are meant in
their natural-language sense.
• Strings that are to be taken literally are enclosed in “double quotes”.
• Placeholder values that need to be replaced are enclosed in the curly brackets “{” and “}”.
• Words that are emphasized are printed in italic.

• Keywords that are defined by the UPnP Working Committee are printed using the forum
character style.
29341-18-3 XXX: © IEC:2010 © ISO/IEC:2011(E) — 3 —
• Keywords that are defined by the UPnP Device Architecture are printed using the arch
character style.
• A double colon delimiter, “::”, signifies a hierarchical parent-child (parent::child)
relationship between the two objects separated by the double colon. This delimiter is used
in multiple contexts, for example: Service::Action(), Action()::Argument,
parentProperty::childProperty.
1.3 Vendor-defined Extensions
Whenever vendors create additional vendor-defined state variables, actions or properties,
their assigned names and XML representation MUST follow the naming conventions and XML
rules as specified in [DEVICE], Clause 2.5, “Description: Non-standard vendor extensions”.
1.4 References
1.4.1 Normative References
This clause lists the normative references used in this specification and includes the tag
inside square brackets that is used for each such reference:
[DEVICE] – UPnP Device Architecture, version 1.0. Available at:
http://www.upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0-20080424.pdf. Latest
version available at: http://www.upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0.pdf.
[ICC] – InboundConnectionConfig:1, UPnP Forum, Available at:
http://www.upnp.org/specs/ra/UPnP-ra-InboundConnectionConfig-v1-Service-20090930.pdf.
Latest version available at: http://www.upnp.org/specs/ra/UPnP-ra-InboundConnectionConfig-
v1-Service.pdf.
[RADAConfig] – RADAConfig:1, UPnP Forum,  Available at:
http://www.upnp.org/specs/ra/UPnP-ra-RADAConfig-v1-Service-20090930.pdf. Latest
version available at: http://www.upnp.org/specs/ra/UPnP-ra-RADAConfig-v1-Service.pdf.
[RADASync] – RADASync:1, UPnP Forum, Available at: http://www.upnp.org/specs/ra/UPnP-
ra-RADASync-v1-Service-20090930.pdf. Latest version available at:
http://www.upnp.org/specs/ra/UPnP-ra-RADASync-v1-Service.pdf.
[RATAConfig] – RATAConfig:1, UPnP Forum,  Available at:
http://www.upnp.org/specs/ra/UPnP-ra-RATAConfig-v1-Service-20090930.pdf. Latest version
available at: http://ww
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.