BS ISO/IEC 29341-24-11:2017
$189.07
Information technology. UPnP Device Architecture – Internet gateway device control protocol. Level 2. Wide area network internet protocol v6. Firewall control service
Published By | Publication Date | Number of Pages |
BSI | 2017 | 48 |
This document specifies the characteristics of the UPnP networked service named WANIPv6FirewallControl, version 1. This service definition is compliant with UPnP Service Architecture 1.0 [1].
This service supports the management IPv6 firewall pinholes in Internet gateway devices independent of the WAN access type (PPP, DHCP, …). It also supports access control to restrict operations to authorized control points and users. It enables UPnP control points to:
-
create and delete pinholes of limited duration that allow external communication from the WAN side of the gateway to reach devices on the LAN side
-
determine operational status of a pinhole
This service does not support:
-
retrieving detailed information about pinholes (such as associated external port or remaining lease duration)
-
outbound packet filtering
-
modification of security policies of a gateway device
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | National foreword |
7 | Foreword |
16 | 1 Scope 2 Normative References |
17 | 3 Terms, definitions, symbols and abbreviations |
19 | 4 Notations and conventions 4.1 Notation 4.2 Data types 4.3 Vendor-defined extensions 5 Service Model 5.1 Service Type |
20 | 5.2 Service Architecture 5.3 State Variables 5.3.1 Summary |
22 | 5.3.12 Relationships among State Variables 5.4 Eventing and Moderation 5.4.1 Summary 5.4.2 Eventing of FirewallEnabled 5.4.3 Eventing of InboundPinholeAllowed 5.5 Actions 5.5.1 Summary |
23 | 5.5.2.1 Description 5.5.2.2 Arguments 5.5.2.3 Argument Descriptions 5.5.2.4 Service Requirements 5.5.2.5 Control Point Requirements When Calling The Action 5.5.2.6 Dependency on Service State 5.5.2.7 Effect on Service State 5.5.2.8 Errors 5.5.3.1 Description |
24 | 5.5.3.2 Arguments 5.5.3.3 Argument descriptions 5.5.3.4 Service Requirements 5.5.3.5 Control Point Requirements When Calling The Action 5.5.3.6 Dependency on Service State |
25 | 5.5.3.7 Effect on Service State 5.5.3.8 Errors 5.5.4.1 Description 5.5.4.2 Arguments 5.5.4.3 Argument Descriptions |
26 | 5.5.4.4 Service Requirements 5.5.4.5 Control Point Requirements When Calling The Action 5.5.4.6 Dependency on Service State 5.5.4.7 Effect on Service State 5.5.4.8 Errors |
27 | 5.5.5.1 Description 5.5.5.2 Arguments 5.5.5.3 Argument Descriptions 5.5.5.4 Service Requirements 5.5.5.5 Control Point Requirements When Calling The Action 5.5.5.6 Dependency on Service State |
28 | 5.5.5.7 Effect on Service State 5.5.5.8 Errors 5.5.6.1 Description 5.5.6.2 Arguments 5.5.6.3 Argument Descriptions 5.5.6.4 Service Requirements 5.5.6.5 Control Point Requirements When Calling The Action 5.5.6.6 Dependency on Service State |
29 | 5.5.6.7 Effect on Service State 5.5.6.8 Errors 5.5.7.1 Description 5.5.7.2 Arguments 5.5.7.3 Argument Descriptions 5.5.7.4 Service Requirements |
30 | 5.5.7.5 Control Point Requirements When Calling The Action 5.5.7.6 Dependency on Service State 5.5.7.7 Effect on Service State 5.5.7.8 Errors 5.5.8.1 Description |
31 | 5.5.8.2 Arguments 5.5.8.3 Argument Descriptions 5.5.8.4 Service Requirements 5.5.8.5 Control Point Requirements When Calling The Action 5.5.8.6 Effect on Service State 5.5.8.7 Errors |
32 | 5.5.9 Relationships Between Actions 5.5.10 Error Code Summary 5.6 Service Behavioral Model |
33 | 6 XML Service Description |