scope:

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 RATAConfig service.

Introduction

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

This service does not address:

• The trust model that will enable secure remote access connections.

• The delivery of credentials.

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.

• 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.

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".