Overview
ISO/IEC 29341-18-2:2011 specifies the UPnP device definition for a Remote Access Client (RAClient) device in accordance with the UPnP Device Architecture v1.0. The standard defines the RAClient device type (urn:schemas-upnp-org:device:RAClient:1) and requires embedding the RATAConfig:1 service. RAClient devices enable UPnP control points (management consoles) to discover and configure Remote Access Clients (RACs), including enumeration of supported transport and credential delivery mechanisms and activation of Remote Access Transport profiles. The standard also supplies the XML device description structure used by RAClient implementations.
Key topics and requirements
- Device type and service IDs: Defines RAClient device type and mandates the RATAConfig service (serviceType: urn:schemas-upnp-org:service:RATAConfig:1; serviceId: urn:upnp-org:serviceId:RATAConfig).
- Core capabilities:
- Enumerate supported Remote Access Transport mechanisms.
- Enumerate supported Credentials Delivery mechanisms.
- Configure active Remote Access Transport profiles (RATA profiles).
- Device model and placement: RAClient can be a Root device or Embedded in other UPnP devices; it may host additional standard or vendor-specific services.
- Security/authorization: Interfaces should be available only to authorized RA Management Consoles (control point authentication implied).
- XML device description: Standard includes a sample XML root/device/serviceList structure for publishing the RAClient and its services.
- Scope exclusions: The standard does NOT define filter configuration for which local/remote devices are visible, nor does it specify content- or control-level access control policies for exposed local devices.
- Normative references and conventions: Compliance with UPnP Device Architecture v1.0, RATAConfig service spec, RFC 2119 keyword usage, and XML 1.0 rules for device/service descriptions.
Applications and who uses it
- Device manufacturers and firmware developers building Remote Access Clients (RACs) or gateways that expose local devices to remote networks.
- UPnP software vendors and developers creating control points / management consoles that discover and configure remote access capabilities.
- Network architects and integrators implementing secure remote access for home and small-office networks, IoT endpoints, NAS devices, and consumer gateways.
- Test engineers and QA teams validating UPnP RA interoperability, service discovery, and RATA profile configuration.
Practical benefits include standardized discovery/configuration of remote access transports, interoperable credential delivery options, and a consistent XML device description for automated management.
Related standards
- UPnP Device Architecture v1.0 (normative)
- UPnP RATAConfig service specification (RATAConfig:1)
- UPnP Remote Access Architecture (RAArchitecture) - informative reference
- RFC 2119 (requirement keywords) and W3C XML 1.0 (device description format)
Keywords: ISO/IEC 29341-18-2:2011, UPnP, RAClient, RATAConfig, Remote Access Client, Remote Access Transport, credentials delivery, UPnP Device Architecture, XML device description.
Open preview (PDF)Information technology — UPnP Device Architecture — Part 18-2: Remote Access Device Control Protocol — Remote Access Client Device
