PN-4407 (to be published as TIA/EIA TSB-110)
The operating system shall enable the RG to:
Manage and allocate network resources
Unify the operation of multiple element gateways into a single system
Integrate control over appliances, servers, clients, actuators, etc.
Provide directory/naming services used for addressing communications to endpoints
Provide security functions and non-repudiation log files
Provide easy-to-use interfaces for consumers
The strategic role of the Residential Gateway makes it imperative that access to the RG is protected against hacker attacks and environmental hazards that may affect communications to and in the residential environment. Security functions shall:
Protect the privacy of service usage,
Prevent physical destruction of platform components,
Make it virtually impossible for database items to be inadvertently or intentionally corrupted.
The recommended security functions shall include but are not limited to:
Authentication: A mechanism by which a resident and the service provider or its authorized agent are authenticated by the RG. This mechanism shall provide a means to prevent the RG from reacting to potentially disruptive commands from unauthorized users.
Access Control: A mechanism by which a user shall have read only, write only, or a read/write privilege. For example, a user with read-only privilege is only allowed to read data base information.
Non-repudiation: A mechanism that records user actions to track responsibilities for system changes or actions.
Physical Security: A means by which the RG and its system components shall be protected from unauthorized physical access.
. FUNCTIONAL REQUIREMENTS
From the customers viewpoint, the services availability criteria is independent of the network and equipment architectures. Service availability contrasts with equipment downtime criteria, which depend on network technology and architecture. For consumer-oriented services, a customer services approach is necessary in addition to the more traditional approach based on technology considerations.
Customers expect different services to have different levels of availability. For example POTS should be highly reliable, while video and data services may be less critical thus it is reasonable to specify different classes of service availability and reliability. Services may be put into different classes such as POTS, security systems, video, data, etc. Requirements are only explicitly stated here for POTS and emergency services.