Skip to content
GitLab
Commit 21011c6f authored by canterburym's avatar canterburym
Browse files

TS 102 232-3 v3.4.1 (2016-09-27) agreed at LI#43 (Sorrento, 2016-09-19)

parent e16417ec
Pipeline #4104 passed with stage
in 6 seconds
Hide whitespace changes
Inline Side-by-side
102232-3/IPAccessPDU.asn
View file @ 21011c6f
IPAccessPDU
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) iPAccess(3) version10(10)}
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) iPAccess(3) version11(11)}
DEFINITIONS IMPLICIT TAGS ::=
BEGIN
......@@ -8,15 +8,21 @@ IMPORTS
-- from ETSI TS 101 671 [1]
IPAddress
FROM HI2Operations
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) hi2(1) version17(17)};
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) hi2(1) version18(18)}
-- from ETSI TS 102 232-1 [2]
Location
FROM LI-PS-PDU
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) genHeader(1) version24(24)};
-- ============================
-- Object Identifier Definition
-- ============================
iPIRIObjId RELATIVE-OID ::= {li-ps(5) iPAccess(3) version10(10) iRI(1)}
iPCCObjId RELATIVE-OID ::= {li-ps(5) iPAccess(3) version10(10) cC(2)}
iPIRIOnlyObjId RELATIVE-OID ::= {li-ps(5) iPAccess(3) version10(10) iRIOnly(3)}
iPIRIObjId RELATIVE-OID ::= {li-ps(5) iPAccess(3) version11(11) iRI(1)}
iPCCObjId RELATIVE-OID ::= {li-ps(5) iPAccess(3) version11(11) cC(2)}
iPIRIOnlyObjId RELATIVE-OID ::= {li-ps(5) iPAccess(3) version11(11) iRIOnly(3)}
-- all three definitions relative to {itu-t(0) identified-organization(4)
-- etsi(0) securityDomain(2) lawfulintercept(2)}
......@@ -66,6 +72,7 @@ IPIRIContents ::= SEQUENCE
targetLocation [7] UTF8String (SIZE (1..64)) OPTIONAL,
-- When internetAccessType is Wireless LAN, this field should contain a string which
-- uniquely identifies the wireless accesspoint within the SvP domain
-- New implementations are encouraged to use the location [24] parameter where possible.
pOPPortNumber [8] INTEGER (0..4294967295) OPTIONAL,
-- The POP port number used by the target
callBackNumber [9] UTF8String (SIZE (1..20)) OPTIONAL,
......@@ -99,10 +106,13 @@ IPIRIContents ::= SEQUENCE
-- Use of this field is fully described in section 6.2.1
authenticationType [22] AuthenticationType OPTIONAL,
-- Field used to identify the authentication type to assist with LEMF data validation
otherTargetIdentifiers [23] SEQUENCE OF OtherTargetIdentifiers OPTIONAL
otherTargetIdentifiers [23] SEQUENCE OF OtherTargetIdentifiers OPTIONAL,
-- This parameter will carry the second and subsequent IPv4 or IPv6 target IP addresses
-- It is used when multiple subnet/prefix ranges are assigned to a target service.
-- Use of this field is fully described in section 6.2.1
location [24] Location OPTIONAL
-- The location associated with the target
}
AccessEventType ::= ENUMERATED
......
102232-3/portal/IPAccessPDU,ver10.txt → 102232-3/portal/IPAccessPDU,ver11.txt
View file @ 21011c6f
IPAccessPDU
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) iPAccess(3) version10(10)}
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) iPAccess(3) version11(11)}
DEFINITIONS IMPLICIT TAGS ::=
BEGIN
......@@ -8,15 +8,21 @@ IMPORTS
-- from ETSI TS 101 671 [1]
IPAddress
FROM HI2Operations
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) hi2(1) version17(17)};
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) hi2(1) version18(18)}
-- from ETSI TS 102 232-1 [2]
Location
FROM LI-PS-PDU
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) genHeader(1) version24(24)};
-- ============================
-- Object Identifier Definition
-- ============================
iPIRIObjId RELATIVE-OID ::= {li-ps(5) iPAccess(3) version10(10) iRI(1)}
iPCCObjId RELATIVE-OID ::= {li-ps(5) iPAccess(3) version10(10) cC(2)}
iPIRIOnlyObjId RELATIVE-OID ::= {li-ps(5) iPAccess(3) version10(10) iRIOnly(3)}
iPIRIObjId RELATIVE-OID ::= {li-ps(5) iPAccess(3) version11(11) iRI(1)}
iPCCObjId RELATIVE-OID ::= {li-ps(5) iPAccess(3) version11(11) cC(2)}
iPIRIOnlyObjId RELATIVE-OID ::= {li-ps(5) iPAccess(3) version11(11) iRIOnly(3)}
-- all three definitions relative to {itu-t(0) identified-organization(4)
-- etsi(0) securityDomain(2) lawfulintercept(2)}
......@@ -66,6 +72,7 @@ IPIRIContents ::= SEQUENCE
targetLocation [7] UTF8String (SIZE (1..64)) OPTIONAL,
-- When internetAccessType is Wireless LAN, this field should contain a string which
-- uniquely identifies the wireless accesspoint within the SvP domain
-- New implementations are encouraged to use the location [24] parameter where possible.
pOPPortNumber [8] INTEGER (0..4294967295) OPTIONAL,
-- The POP port number used by the target
callBackNumber [9] UTF8String (SIZE (1..20)) OPTIONAL,
......@@ -99,10 +106,13 @@ IPIRIContents ::= SEQUENCE
-- Use of this field is fully described in section 6.2.1
authenticationType [22] AuthenticationType OPTIONAL,
-- Field used to identify the authentication type to assist with LEMF data validation
otherTargetIdentifiers [23] SEQUENCE OF OtherTargetIdentifiers OPTIONAL
otherTargetIdentifiers [23] SEQUENCE OF OtherTargetIdentifiers OPTIONAL,
-- This parameter will carry the second and subsequent IPv4 or IPv6 target IP addresses
-- It is used when multiple subnet/prefix ranges are assigned to a target service.
-- Use of this field is fully described in section 6.2.1
location [24] Location OPTIONAL
-- The location associated with the target
}
AccessEventType ::= ENUMERATED
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment