Skip to content
GitLab
Commit 45f7e27b authored by canterburym's avatar canterburym
Browse files

TS 102 232-2 v3.13.1

parent f1cbc8c8
Pipeline #8741 canceled with stage
Expand all Hide whitespace changes
Inline Side-by-side
102232-2/EmailPDU.asn
View file @ 45f7e27b
This diff is collapsed.
102232-2/portal/EmailPDU,ver17.txt → 102232-2/portal/EmailPDU,ver18.txt
View file @ 45f7e27b
-- ============================
-- Description of the Email PDU
-- ============================
EmailPDU
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) email(2) version17(17)}
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) email(2) version18(18)}
DEFINITIONS IMPLICIT TAGS ::=
BEGIN
IMPORTS
-- from TS 102 232-1 [3]
-- from ETSI TS 102 232-1 [3]
IPAddress
FROM LI-PS-PDU
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) genHeader(1) version26(26)}
-- from TS 102 232-5 [38]
-- from ETSI TS 102 232-5 [38]
IPMMCC
FROM IPMultimediaPDU
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) iPMultimedia(5) version8(8)};
......@@ -21,11 +25,12 @@ IMPORTS
-- Object Identifier Definition
-- ============================
emailIRIObjId RELATIVE-OID ::= {li-ps(5) email(2) version17(17) iRI(1)}
emailCCObjId RELATIVE-OID ::= {li-ps(5) email(2) version17(17) cC(2)}
messagingIRIObjId RELATIVE-OID ::= {li-ps(5) email(2) version17(17) messagingIRI(3)}
messagingCCObjId RELATIVE-OID ::= {li-ps(5) email(2) version17(17) messagingCC(4)}
messagingMMCCObjId RELATIVE-OID ::= {li-ps(5) email(2) version17(17) messagingMMCC(5)}
emailPDUObjId RELATIVE-OID ::= {li-ps(5) email(2) version18(18)}
emailIRIObjId RELATIVE-OID ::= {emailPDUObjId iRI(1)}
emailCCObjId RELATIVE-OID ::= {emailPDUObjId cC(2)}
messagingIRIObjId RELATIVE-OID ::= {emailPDUObjId messagingIRI(3)}
messagingCCObjId RELATIVE-OID ::= {emailPDUObjId messagingCC(4)}
messagingMMCCObjId RELATIVE-OID ::= {emailPDUObjId messagingMMCC(5)}
-- definitions are relative to
-- {itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulintercept(2)}
......@@ -76,9 +81,11 @@ EmailIRI ::= SEQUENCE
client-Octets-Sent [7] INTEGER,
protocol-ID [8] E-mail-Protocol,
e-mail-Sender [9] UTF8String (SIZE (0..255)) OPTIONAL,
-- Not available in some cases; if a value is available, it must be provided
-- Not available in some cases; if a value is available, it shall be provided.
-- Note that as of version 3.13.1, this field may contain RFC 6530-compliant addresses.
e-mail-Recipients [10] E-mail-Address-List OPTIONAL,
-- Not available in some cases; if a value is available, it must be provided
-- Not available in some cases; if a value is available, it shall be provided
-- Note that as of version 3.13.1, this field may contain RFC 6530-compliant addresses.
status [11] E-mail-Status,
total-Recipient-Count [12] INTEGER (0..4294967295) OPTIONAL,
message-ID [13] OCTET STRING OPTIONAL,
......@@ -149,7 +156,7 @@ AAAInformation ::= CHOICE
-- The AAAInformation field allows for POP3 and authenticated SMTP AAA information
{
pOP3AAAInformation [0] POP3AAAInformation,
aSMTPAAAInformation [1] ASMTPAAAInformation,
aSMTPAAAInformation [1] ASMTPAAAInformation,
...,
iMAPAAAInformation [2] IMAPAAAInformation
}
......@@ -210,7 +217,7 @@ AAAauthMethod ::= ENUMERATED
MessagingCC ::= SEQUENCE
-- MessagingCC is the PDU sent for the captured content
{
messaging-cc-obj-id [0] RELATIVE-OID,
messaging-cc-obj-id [0] RELATIVE-OID,
event-identifier [1] INTEGER (0..4294967295),
-- Used to correlate to MessagingIRI within the same CIN
content-identifier [2] INTEGER (0..4294967295) OPTIONAL,
......@@ -225,6 +232,7 @@ MessagingCC ::= SEQUENCE
-- Refer to IETF RFC 2045 [20]
}
MessagingMMCC ::= SEQUENCE
-- MessagingMMCC is the PDU sent for the captured IPMMCC content
{
......@@ -306,8 +314,7 @@ Messaging-Box-Event ::= ENUMERATED
disconnect(16),
connect(17),
...,
unknown(0),
unknown(0),
greeting-play(18),
language-change(19),
pin-security-enable(20),
......@@ -317,7 +324,11 @@ Messaging-Box-Event ::= ENUMERATED
personal-operator-remove(24),
additional-destination-add(25),
additional-destination-change(26),
additional-destination-remove(27), auto-play-enable(28), auto-play-disable(29), header-play-enable(30), header-play-disable(31)
additional-destination-remove(27),
auto-play-enable(28),
auto-play-disable(29),
header-play-enable(30),
header-play-disable(31)
}
Messaging-Notification-Event ::= ENUMERATED
......@@ -357,7 +368,7 @@ Messaging-Party-Information ::= SEQUENCE
party-identity [1] Messaging-Party-Identity,
...,
party-validity [2] Messaging-Party-Validity OPTIONAL,
copy-qualifier [3] Messaging-Copy-Qualifier OPTIONAL
copy-qualifier [3] Messaging-Copy-Qualifier OPTIONAL
}
Messaging-Party-Qualifier ::= ENUMERATED
......@@ -372,52 +383,54 @@ Messaging-Party-Qualifier ::= ENUMERATED
-- the terminating party and all information provided by this party.
...,
associated-party(3)
-- In this case, the partyInformation parameter provides the identites related to
-- an associated party and all information provided by this party
-- In this case, the partyInformation parameter provides the identities related to
-- an associated party and all information provided by this party.
}
Messaging-Party-Identity ::= CHOICE
{
msisdn [0] OCTET STRING (SIZE (1..9)),
msisdn [0] OCTET STRING (SIZE (1..9)),
-- MSISDN of the target, encoded in the same format as the AddressString
-- parameters defined in MAP format 3GPP TS 09.02 [22], clause 17.7.8.
e164-format [1] OCTET STRING (SIZE (1..25)),
e164-format [1] OCTET STRING (SIZE (1..25)),
-- E.164 address of the node in international format. Coded in the same format as
-- the calling party number parameter of the ISUP (parameter part: EN 300 356 [23])
email-address [2] E-mail-Address-List,
email-address [2] E-mail-Address-List,
-- Note that as of version 3.13.1, this field may contain RFC 6530-compliant addresses.
...,
ip-address [3] IPAddress,
--IPAddress is defined by IETF RFC 791 [31] and RFC 2460 [34]
alphanumeric [4] UTF8String,
ip-address-and-port [5] IP-Address-And-Port,
imsi [6] OCTET STRING (SIZE (3..8)),
ip-address [3] IPAddress,
–-IPAddress is defined by IETF RFC 791 [31] and RFC 8200 [34]
alphanumeric [4] UTF8String,
ip-address-and-port [5] IP-Address-And-Port,
imsi [6] OCTET STRING (SIZE (3..8)),
-- International Mobile Subscriber Identity of the target, encoded in the same format as the
-- TBCD-STRING parameter defined in MAP format 3GPP TS 29.002 [36], clause 17.7.8.
-- It is described in 3GPP TS 23.003 [37] clause 2.2.
imei [7] OCTET STRING (SIZE (8)),
imei [7] OCTET STRING (SIZE (8)),
-- International Mobile Equipment Identity of the target, encoded in the same format as the
-- TBCD-STRING parameter defined in MAP format 3GPP TS 23.003 [37] clause 6
fax-url [8] OCTET STRING,
-- TBCD-STRING parameter defined in MAP format 3GPP TS 29.002 [36], clause 17.7.8.
–- It is defined in 3GPP TS 23.003 [37] clause 6.
fax-url [8] OCTET STRING,
-- see format defined in RFC 2806 [29].
tel-url [9] OCTET STRING,
-- see format used in TS 133.108 [5], TS 24 229[30] and defined in RFC 2806 [29].
modem-url [10] OCTET STRING,
tel-url [9] OCTET STRING,
-- see format used in 3GPP TS 33.108 [5], 3GPP TS 24.229 [30] and defined in RFC 2806 [29].
modem-url [10] OCTET STRING,
-- see format defined in RFC 2806 [29].
sip-uri [11] OCTET STRING,
-- see format used in in TS 133.108 [5] and defined in RFC 3261 [32].
sips-uri [12] OCTET STRING,
sip-uri [11] OCTET STRING,
-- see format used in in 3GPP TS 33.108 [5] and defined in RFC 3261 [32].
sips-uri [12] OCTET STRING,
-- see format defined in RFC 3261 [32].
nai [13] OCTET STRING
nai [13] OCTET STRING
-- Network Access Identity of the party, encoded in the same format as used EPS
-- domain in TS 133.108 [5] and defined in RFC 4282 [33].
–- domain in 3GPP TS 33.108 [5] and defined in RFC 7542 [33].
}
IP-Address-And-Port ::= SEQUENCE
{
ip-address [0] IPAddress,
-- IPAddress is defined by IETF RFC 791 [31] and RFC 2460 [34]
–- IPAddress is defined by IETF RFC 791 [31] and RFC 8200 [34]
port-number [1] INTEGER,
-- port-number is defined by IETF RFC 6533 [35]
–- port-number is defined by IETF RFC 6335 [35]
...
}
......@@ -438,7 +451,6 @@ Messaging-Copy-Qualifier ::= ENUMERATED
...
}
Messaging-Trigger ::= ENUMERATED
{
unknown(0),
......@@ -457,9 +469,9 @@ Messaging-Property ::= CHOICE
greeting-type [2] Messaging-Property-Greeting-Type,
notification-type [3] Messaging-Property-Notification-Type,
language [4] OCTET STRING,
-- Language according to RFC 3066 [24]
message-identifier [5] OCTET STRING,
subject [6] UTF8String,
-- Language according to RFC 4646 [24]
message-identifier [5] OCTET STRING,
subject [6] UTF8String,
user-agent [7] UTF8String,
password [8] OCTET STRING,
message-status [9] Messaging-Property-Message-Status,
......@@ -498,7 +510,10 @@ Messaging-Property-Notification-Type ::= ENUMERATED
allow-delivery-report(6),
deny-delivery-report(7),
message-wait-indication(8),
voice-to-text(9), new-message-sms(10), new-message-outcall(11), new-message-reminder(12)
voice-to-text(9),
new-message-sms(10),
new-message-outcall(11),
new-message-reminder(12)
}
Messaging-Property-Message-Status ::= 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