ISO/IEC 29341-18-13:2011 PDF

Information technology — UPnP Device Architecture — Part 18-13: Remote Access Device Control Protocol — Remote Access Transport Agent Configuration Service

First page of standard ISO/IEC 29341-18-13:2011

Open preview (PDF)

Title (English):

ISO/IEC 29341-18-13:2011

Information technology — UPnP Device Architecture — Part 18-13: Remote Access Device Control Protocol — Remote Access Transport Agent Configuration Service

Document status:: Active
Format:: Electronic (PDF)
Number of pages:: 44
Publication date:: August 30, 2011
Edition:: ISO/IEC IS 29341 edition 1 version 1
ICS:: 35.200

Delivery type:

Full version25 €Read online 24h10 €Read online 72h15 €

Document language:

enru

Delivery time:Immediate download

Price:25 €

Description (English):

ISO/IEC 29341-18-13:2011(E) describes a service definition which is compliant with the UPnP Device Architecture version 1.0. It defines a service type referred to herein as RATAConfig service. The RATAConfig service is a UPnP service that allows control points to provision and configure the parameters that are required for enabling a Remote Access Server to accept and a Remote Access Client to initiate remote access connections. This service provides control points with the following functionality: - Determine the Remote Access Transport Agents that can be configured by the service. - Determine the delivery mechanisms for credentials supported by the service. - Configure Remote Access Transport Agent profiles. - Management of Remote Access Transport Agent profiles.

Technical details

Technical committee: ISO/IEC JTC 1 - Information technology
SKU: ISO/IEC 29341-18-13:2011

Abstract

Overview

ISO/IEC 29341-18-13:2011 specifies the RATAConfig (Remote Access Transport Agent Configuration) service, a UPnP-compliant service definition within the UPnP Device Architecture v1.0. The standard defines how UPnP control points can provision and configure the parameters required for Remote Access Servers and Clients to establish remote access connections. It focuses on provisioning, profile configuration and lifecycle management, not on trust models or credential transport mechanisms.

Key Topics and Technical Requirements

Service scope and compliance
- Implements a UPnP service type called RATAConfig, conforming to UPnP Device Architecture 1.0.
Core functionality
- Discover Remote Access Transport Agents that the device can configure.
- Enumerate credential delivery mechanisms supported by the service.
- Create, edit, delete and manage Remote Access Transport Agent profiles used by servers and clients.
Service modeling
- Detailed state variables (e.g., TransportAgentCapabilities, CredentialDelivery, ProfileList).
- Actions exposed for control points, such as:
  - GetTransportAgentCapabilities()
  - GetSupportedCredentialDelivery()
  - GetCredentialsList()
  - GetProfileList(), AddProfile(), EditProfile(), DeleteProfile()
  - GetProfileConfigInfo()
- Eventing and moderation rules for state changes.
Normative and informative annexes
- Data structure templates (ProfileList, ProfileConfig, TransportAgent data).
- Annex C: IPsec templates and sample files.
- Annex D: OpenVPN templates and sample configurations.
- Addressing considerations (IPv4) and theory of operation examples.
Limitations explicitly stated
- The standard does not define trust models or the delivery mechanisms for credentials themselves.

Practical Applications and Who Should Use It

Device and firmware manufacturers of home gateways, routers, NAS appliances and IoT gateways who need standardized remote-access provisioning via UPnP.
Software developers building UPnP control points or management consoles to automate VPN/IPsec/OpenVPN profile provisioning.
Network architects and integrators deploying remote-management solutions that require standardized profile configuration and lifecycle management.
Remote access and managed service providers implementing standardized on-premises provisioning interfaces for client/server transport agents.

Practical use cases include automated setup of VPN profiles on consumer gateways, centralized provisioning of remote access clients in enterprise edge devices, and interoperable control-point-driven configuration of transport agents (IPsec/OpenVPN) via UPnP.

Related Standards

ISO/IEC 29341 series - UPnP Device Architecture (this part is 18-13 in the series).
UPnP Device Architecture version 1.0 (normative baseline for this service).

Keywords: UPnP, RATAConfig, Remote Access Transport Agent, ISO/IEC 29341-18-13:2011, remote access provisioning, IPsec, OpenVPN, device configuration, control point, profile management.

Related standards

Mentioned in the description and other ISO standards

Abstract

Overview

Key Topics and Technical Requirements

Service scope and compliance
- Implements a UPnP service type called RATAConfig, conforming to UPnP Device Architecture 1.0.
Core functionality
- Discover Remote Access Transport Agents that the device can configure.
- Enumerate credential delivery mechanisms supported by the service.
- Create, edit, delete and manage Remote Access Transport Agent profiles used by servers and clients.
Service modeling
- Detailed state variables (e.g., TransportAgentCapabilities, CredentialDelivery, ProfileList).
- Actions exposed for control points, such as:
  - GetTransportAgentCapabilities()
  - GetSupportedCredentialDelivery()
  - GetCredentialsList()
  - GetProfileList(), AddProfile(), EditProfile(), DeleteProfile()
  - GetProfileConfigInfo()
- Eventing and moderation rules for state changes.
Normative and informative annexes
- Data structure templates (ProfileList, ProfileConfig, TransportAgent data).
- Annex C: IPsec templates and sample files.
- Annex D: OpenVPN templates and sample configurations.
- Addressing considerations (IPv4) and theory of operation examples.
Limitations explicitly stated
- The standard does not define trust models or the delivery mechanisms for credentials themselves.

Practical Applications and Who Should Use It

Device and firmware manufacturers of home gateways, routers, NAS appliances and IoT gateways who need standardized remote-access provisioning via UPnP.
Software developers building UPnP control points or management consoles to automate VPN/IPsec/OpenVPN profile provisioning.
Network architects and integrators deploying remote-management solutions that require standardized profile configuration and lifecycle management.
Remote access and managed service providers implementing standardized on-premises provisioning interfaces for client/server transport agents.

Related Standards

ISO/IEC 29341 series - UPnP Device Architecture (this part is 18-13 in the series).
UPnP Device Architecture version 1.0 (normative baseline for this service).

Keywords: UPnP, RATAConfig, Remote Access Transport Agent, ISO/IEC 29341-18-13:2011, remote access provisioning, IPsec, OpenVPN, device configuration, control point, profile management.

ISO/IEC 29341-18-13:2011 PDF

Technical details

Abstract

Overview

Key Topics and Technical Requirements

Practical Applications and Who Should Use It

Related Standards

Related standards

Abstract

Overview

Key Topics and Technical Requirements

Practical Applications and Who Should Use It

Related Standards

Related standards

Information technology — UPnP Device Architecture — Part 4-13: Audio Video Device Control Protocol - Level 2…

Systems and software engineering — Software life cycle processes

Asset management — Vocabulary, overview and principles

Asset management — Asset management system — Requirements

Information technology — Radio frequency identification device conformance test methods — Part 2: Test method…

Information technology — Multimedia framework (MPEG-21) — Part 22: User Description

Milk — Determination of the lactoperoxidase activity — Photometric method (Reference method)

Carbonaceous materials for the production of aluminium — Cold and tepid ramming pastes — Expansion/shrinkage…