From 7cab3beb92ed72321d37f64da2568f697061e959 Mon Sep 17 00:00:00 2001 From: mark Date: Mon, 15 Jun 2020 12:27:58 +0100 Subject: [PATCH] TS 102 232-5 v3.1.1 (2012-02-28) agreed at LI#29 (Dun Laoghaire, 2012-01-24) --- 102232-5/IPMultimediaPDU.asn | 48 ++++++++++++------- ...aPDU,ver4.txt => IPMultimediaPDU,ver5.txt} | 48 ++++++++++++------- 2 files changed, 64 insertions(+), 32 deletions(-) rename 102232-5/portal/{IPMultimediaPDU,ver4.txt => IPMultimediaPDU,ver5.txt} (71%) diff --git a/102232-5/IPMultimediaPDU.asn b/102232-5/IPMultimediaPDU.asn index 93731a2..1ce9a63 100644 --- a/102232-5/IPMultimediaPDU.asn +++ b/102232-5/IPMultimediaPDU.asn @@ -1,5 +1,5 @@ IPMultimediaPDU -{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) iPMultimedia(5) version4(4)} +{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) iPMultimedia(5) version5(5)} DEFINITIONS IMPLICIT TAGS ::= BEGIN @@ -8,14 +8,14 @@ IMPORTS -- from TS 101 671 [1] IPAddress FROM HI2Operations - {itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) hi2(1) version10(10)}; + {itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) hi2(1) version14(14)}; -- ============================ -- Object Identifier Definition -- ============================ -iPMMIRIObjId RELATIVE-OID ::= {li-ps(5) iPMultimedia(5) version4(4) iRI(1)} -iPMMCCObjId RELATIVE-OID ::= {li-ps(5) iPMultimedia(5) version4(4) cC(2)} +iPMMIRIObjId RELATIVE-OID ::= {li-ps(5) iPMultimedia(5) version5(5) iRI(1)} +iPMMCCObjId RELATIVE-OID ::= {li-ps(5) iPMultimedia(5) version5(5) cC(2)} -- both definitions relative to: -- {itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2)} @@ -23,13 +23,13 @@ iPMMCCObjId RELATIVE-OID ::= {li-ps(5) iPMultimedia(5) version4(4) cC(2)} -- IP Multimedia Communications Contents -- ===================================== -IPMMCC ::= SEQUENCE +IPMMCC ::= SEQUENCE { iPMMCCObjId [0] RELATIVE-OID, mMCCContents [1] OCTET STRING, -- Copy of the multimediastream, i.e. all related RTP/RTCP or MSRP packets -- Each IPMMCC shall contain one intercepted packet - -- Protocol of the multimedia packets is indicated by means of mMCCprotocol parameter + -- Protocol of the multimedia packets is indicated by means of mMCCprotocol parameter -- mMCCContents was called rTPCCContents in earlier versions until v2.3.2. ..., frameType [2] FrameType OPTIONAL, @@ -46,7 +46,7 @@ IPMMCC ::= SEQUENCE -- Absence means mMCCContents contains RTP/RTCP packets } -FrameType ::= ENUMERATED +FrameType ::= ENUMERATED { ipFrame(0), -- All headers are present @@ -61,7 +61,7 @@ FrameType ::= ENUMERATED -- IP header is missing } -MMCCprotocol ::= ENUMERATED +MMCCprotocol ::= ENUMERATED { rTP(0), -- mMCCContents parameter contains RTP/RTCP packets @@ -74,14 +74,14 @@ MMCCprotocol ::= ENUMERATED -- Intercept-related information for IP Multimedia sessions -- ======================================================== -IPMMIRI ::= SEQUENCE +IPMMIRI ::= SEQUENCE { iPMMIRIObjId [0] RELATIVE-OID, iPMMIRIContents [1] IPIRIContents, ... } -IPIRIContents ::= CHOICE +IPIRIContents ::= CHOICE { originalIPMMMessage [0] OCTET STRING, -- Copy of the IP MM signalling packet including the original IP and UDP/TCP headers @@ -89,11 +89,13 @@ IPIRIContents ::= CHOICE -- Copy of the SIP content and the source and destination IP address h323Message [2] H323Message, -- Copy of the H.323 content and the source and destination IP address - ... - + ..., + nationalIPMMIRIParameters [3] NationalIPMMIRIParameters + -- This parameter is used according to national regulations + -- This parameter shall be delivered as an IRI-Report-record } -SIPMessage ::= SEQUENCE +SIPMessage ::= SEQUENCE { iPSourceAddress [0] IPAddress, iPDestinationAddress [1] IPAddress, @@ -101,7 +103,7 @@ SIPMessage ::= SEQUENCE ... } -H323Message ::= SEQUENCE +H323Message ::= SEQUENCE { iPSourceAddress [0] IPAddress, iPDestinationAddress [1] IPAddress, @@ -109,7 +111,7 @@ H323Message ::= SEQUENCE ... } -H323MessageContent ::= CHOICE +H323MessageContent ::= CHOICE { h225CSMessageContent [0] OCTET STRING, h225RASMessageContent [1] OCTET STRING, @@ -118,5 +120,19 @@ H323MessageContent ::= CHOICE ... } -END -- end of IP Multimedia PDU +NationalIPMMIRIParameters ::= SEQUENCE +{ + countryCode [1] PrintableString (SIZE (2)), + -- Country Code according to ISO 3166-1 [16], + -- the country to which the parameters inserted after the extension marker apply. + ... + -- In case a given country wants to use additional national parameters according to its law, + -- these national parameters should be defined using the ASN.1 syntax and added after the + -- extension marker (...). + -- It is recommended that "version parameter" and "vendor identification parameter" are + -- included in the national parameters definition. Vendor identifications can be + -- retrieved from the IANA web site (see Annex E Bibliography). Besides, it is recommended + -- to avoid using tags from 240 to 255 in a formal type definition. +} +END -- end of IP Multimedia PDU diff --git a/102232-5/portal/IPMultimediaPDU,ver4.txt b/102232-5/portal/IPMultimediaPDU,ver5.txt similarity index 71% rename from 102232-5/portal/IPMultimediaPDU,ver4.txt rename to 102232-5/portal/IPMultimediaPDU,ver5.txt index 93731a2..1ce9a63 100644 --- a/102232-5/portal/IPMultimediaPDU,ver4.txt +++ b/102232-5/portal/IPMultimediaPDU,ver5.txt @@ -1,5 +1,5 @@ IPMultimediaPDU -{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) iPMultimedia(5) version4(4)} +{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) iPMultimedia(5) version5(5)} DEFINITIONS IMPLICIT TAGS ::= BEGIN @@ -8,14 +8,14 @@ IMPORTS -- from TS 101 671 [1] IPAddress FROM HI2Operations - {itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) hi2(1) version10(10)}; + {itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) hi2(1) version14(14)}; -- ============================ -- Object Identifier Definition -- ============================ -iPMMIRIObjId RELATIVE-OID ::= {li-ps(5) iPMultimedia(5) version4(4) iRI(1)} -iPMMCCObjId RELATIVE-OID ::= {li-ps(5) iPMultimedia(5) version4(4) cC(2)} +iPMMIRIObjId RELATIVE-OID ::= {li-ps(5) iPMultimedia(5) version5(5) iRI(1)} +iPMMCCObjId RELATIVE-OID ::= {li-ps(5) iPMultimedia(5) version5(5) cC(2)} -- both definitions relative to: -- {itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2)} @@ -23,13 +23,13 @@ iPMMCCObjId RELATIVE-OID ::= {li-ps(5) iPMultimedia(5) version4(4) cC(2)} -- IP Multimedia Communications Contents -- ===================================== -IPMMCC ::= SEQUENCE +IPMMCC ::= SEQUENCE { iPMMCCObjId [0] RELATIVE-OID, mMCCContents [1] OCTET STRING, -- Copy of the multimediastream, i.e. all related RTP/RTCP or MSRP packets -- Each IPMMCC shall contain one intercepted packet - -- Protocol of the multimedia packets is indicated by means of mMCCprotocol parameter + -- Protocol of the multimedia packets is indicated by means of mMCCprotocol parameter -- mMCCContents was called rTPCCContents in earlier versions until v2.3.2. ..., frameType [2] FrameType OPTIONAL, @@ -46,7 +46,7 @@ IPMMCC ::= SEQUENCE -- Absence means mMCCContents contains RTP/RTCP packets } -FrameType ::= ENUMERATED +FrameType ::= ENUMERATED { ipFrame(0), -- All headers are present @@ -61,7 +61,7 @@ FrameType ::= ENUMERATED -- IP header is missing } -MMCCprotocol ::= ENUMERATED +MMCCprotocol ::= ENUMERATED { rTP(0), -- mMCCContents parameter contains RTP/RTCP packets @@ -74,14 +74,14 @@ MMCCprotocol ::= ENUMERATED -- Intercept-related information for IP Multimedia sessions -- ======================================================== -IPMMIRI ::= SEQUENCE +IPMMIRI ::= SEQUENCE { iPMMIRIObjId [0] RELATIVE-OID, iPMMIRIContents [1] IPIRIContents, ... } -IPIRIContents ::= CHOICE +IPIRIContents ::= CHOICE { originalIPMMMessage [0] OCTET STRING, -- Copy of the IP MM signalling packet including the original IP and UDP/TCP headers @@ -89,11 +89,13 @@ IPIRIContents ::= CHOICE -- Copy of the SIP content and the source and destination IP address h323Message [2] H323Message, -- Copy of the H.323 content and the source and destination IP address - ... - + ..., + nationalIPMMIRIParameters [3] NationalIPMMIRIParameters + -- This parameter is used according to national regulations + -- This parameter shall be delivered as an IRI-Report-record } -SIPMessage ::= SEQUENCE +SIPMessage ::= SEQUENCE { iPSourceAddress [0] IPAddress, iPDestinationAddress [1] IPAddress, @@ -101,7 +103,7 @@ SIPMessage ::= SEQUENCE ... } -H323Message ::= SEQUENCE +H323Message ::= SEQUENCE { iPSourceAddress [0] IPAddress, iPDestinationAddress [1] IPAddress, @@ -109,7 +111,7 @@ H323Message ::= SEQUENCE ... } -H323MessageContent ::= CHOICE +H323MessageContent ::= CHOICE { h225CSMessageContent [0] OCTET STRING, h225RASMessageContent [1] OCTET STRING, @@ -118,5 +120,19 @@ H323MessageContent ::= CHOICE ... } -END -- end of IP Multimedia PDU +NationalIPMMIRIParameters ::= SEQUENCE +{ + countryCode [1] PrintableString (SIZE (2)), + -- Country Code according to ISO 3166-1 [16], + -- the country to which the parameters inserted after the extension marker apply. + ... + -- In case a given country wants to use additional national parameters according to its law, + -- these national parameters should be defined using the ASN.1 syntax and added after the + -- extension marker (...). + -- It is recommended that "version parameter" and "vendor identification parameter" are + -- included in the national parameters definition. Vendor identifications can be + -- retrieved from the IANA web site (see Annex E Bibliography). Besides, it is recommended + -- to avoid using tags from 240 to 255 in a formal type definition. +} +END -- end of IP Multimedia PDU -- GitLab