Commit ff77d8ed authored by Luke Mewburn's avatar Luke Mewburn 💬

remove trailing whitespace

parent d5611e43
Pipeline #7466 passed with stage
in 58 seconds
......@@ -28,7 +28,7 @@ messagingIRIObjId RELATIVE-OID ::= {emailPDUObjId messagingIRI(3)}
messagingCCObjId RELATIVE-OID ::= {emailPDUObjId messagingCC(4)}
messagingMMCCObjId RELATIVE-OID ::= {emailPDUObjId messagingMMCC(5)}
-- definitions are relative to
-- definitions are relative to
-- {itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulintercept(2)}
......@@ -48,7 +48,7 @@ EmailCC ::= SEQUENCE
Email-Format ::= ENUMERATED
{
ip-packet(1),
-- When this is the email format, the content will contain the bytes of the IP packet from
-- When this is the email format, the content will contain the bytes of the IP packet from
-- the IP header through to the end of the IP packet
-- Meets requirement E.2.7
application(2)
......@@ -81,7 +81,7 @@ EmailIRI ::= SEQUENCE
-- 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.
-- Note that as of version 3.13.1, this field may contain RFC 6530-compliant addresses.
-- 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,
......@@ -144,7 +144,7 @@ National-EM-ASN1parameters ::= SEQUENCE
-- 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
-- these national parameters should be defined using the ASN.1 syntax and added after the
-- extension marker (...)
}
......@@ -310,7 +310,6 @@ Messaging-Box-Event ::= ENUMERATED
connect(17),
...,
unknown(0),
greeting-play(18),
language-change(19),
pin-security-enable(20),
......@@ -372,10 +371,10 @@ Messaging-Party-Qualifier ::= ENUMERATED
unknown-party(0),
-- In this case the party cannot be classified as either originating or terminating
originating-party(1),
-- In this case, the partyInformation parameter provides the identities related to
-- In this case, the partyInformation parameter provides the identities related to
-- the originating party and all information provided by this party.
terminating-party(2),
-- In this case, the partyInformation parameter provides the identities related to
-- In this case, the partyInformation parameter provides the identities related to
-- the terminating party and all information provided by this party.
...,
associated-party(3)
......@@ -389,7 +388,7 @@ Messaging-Party-Identity ::= CHOICE
-- 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)),
-- E.164 address of the node in international format. Coded in the same format as
-- 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,
-- Note that as of version 3.13.1, this field may contain RFC 6530-compliant addresses.
......@@ -415,8 +414,8 @@ Messaging-Party-Identity ::= CHOICE
-- see format used in in TS 133.108 [5] and defined in RFC 3261 [32].
sips-uri [12] OCTET STRING,
-- see format defined in RFC 3261 [32].
nai [13] OCTET STRING
-- Network Access Identity of the party, encoded in the same format as used EPS
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].
}
......
Markdown is supported
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