888855 - [MMS] 40 character restriction on content type name of MMS message parts should be removed

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::SMS, defect, P1)

Description

[Leo]

FFOS is having a 40 character restriction on content type name of MMS message parts.This is not as per specification.We should remove this restriction

Comment 1

[Leo]

This is discussed in Taiwan workweek.
We have to remove the following if part for that 40 character restriction

if (name && name.length > MMS.MMS_MAX_LENGTH_NAME_CONTENT_TYPE) {
   return false;
}

Thanks,

Comment 2

[Chia-hung Tai [:ctai :ctai_mozilla :cht]]

Leo, 
One question after re-check the In OMA-TS-MMS_CONF-V1_3-20110511-C 10.2.5.
Why they use headers in "Name-parameter for Content-Type in WSP multipart headers" if it is not check for every part?

Comment 3

[Leo]

Hi Ctai,

This is our understanding. WSP 230 document is used for encoding all the multipart headers. MMS specification also uses the same for encoding. However MMS adds limitations interms of size of header fields. This we have already discussed.
Content type is a general encoding rule defined by WSP 230, which can be used anywhere and Name parameter is a optional. Its used for all the parts not for WSP/WAP headers (other header information in WAP headers are To/CC/Bcc).

Comment 4

[Vicamo Yang [:vicamo][:vyang]]

OMA-TS-MMS-CONF-V1_3-20110913-A clause 10.2.5 "Maximum Values of MMS Parameters" clearly says "Name-parameter for Content-Type in WSP multipart headers" can only have 40 characters in maximum.

Comment 5

[Vicamo Yang [:vicamo][:vyang]]

Per face-to-face meeting, if you just want a long long file name for each part, please file another bug instead.  On that case, file names should have no restrictions on their lengths, at least not addressed in MMS conformance documents.