…the MIME document series ([ RFC2045 ], [ RFC2046 ], [ RFC2047 ], [ RFC2049 ], [ RFC4288 ], [ RFC4289 ]), that extend this specification to allow for values outside of that range. Discussion of those mechanisms is not within the scope of this specification. Messages are divided in…

…y the MIME document series ([ RFC2045 ], RFC2046 ], [ RFC2047 ], [ RFC2049 ], [ RFC4288 ], [ RFC4289 ]), that extend this specification to allow for values outside of that range. Discussion of those mechanisms is not within the scope of this specification. Messages are divided in…

…ifically the MIME document series ([RFC2045], [RFC2046], [RFC2047], [RFC2049], [RFC4288], [RFC4289]), that extend this specification to allow for values outside of that range. Discussion of those mechanisms is not within the scope of this specification. Messages are divided into …

…y the MIME document series ([ RFC2045 ], RFC2046 ], [ RFC2047 ], [ RFC2049 ], [ RFC4288 ], [ RFC4289 ]), that extend this specification to allow for values outside of that range. Discussion of those mechanisms is not within the scope of this specification. Messages are divided in…

…y the MIME document series ([ RFC2045 ], RFC2046 ], [ RFC2047 ], [ RFC2049 ], [ RFC4288 ], [ RFC4289 ]), that extend this specification to allow for values outside of that range. Discussion of those mechanisms is not within the scope of this specification. Messages are divided in…

…ody-parts" or, popularly, "attachments". RFC2045 ], [ RFC2046 ], [ RFC2047 ], [ RFC4288 ], [ RFC4289 ], [ RFC2049 ]. In addition, Internet Mail has a few conventions for special control data, notably: Delivery Status Notification (DSN): A Delivery Status Notification (DSN) is a m…

…ociated with this payload format. The section registers the media types, as per RFC4288 RFC4288 4.1.1 . Registration of media type audio/speex Media type name: audio Media subtype name: speex Required parameters: rate: RTP timestamp clock rate, which is equal to the sampling rate…

…pe-name ; Where "type-name" and "subtype-name" are ; defined in Section 4.2 of [RFC4288] . Description: This parameter can be specified on properties that are used to reference an object. The parameter specifies the media type [ RFC4288 ] of the referenced object. For example, on…

…he following rules are included from [ RFC3986 ]: URI and URI-Reference; from [ RFC4288 ]: type-name and subtype-name; from [ W3C.REC-html401-19991224 ]: MediaDesc; from [ RFC5646 ]: Language-Tag; and from [ RFC5987 ], ext-value and parmname. Nottingham Standards Track [Page 3] R…

…, the following rules are included from [RFC3986]: URI and URI-Reference; from [RFC4288]: type-name and subtype-name; from [W3C.REC-html401-19991224]: MediaDesc; from [RFC5646]: Language-Tag; and from [RFC5987], ext-value and parmname. Nottingham Standards Track [Page 3] RFC 5988…

…than what is allowed by the ABNF in Section 5.1 of [RFC2045] or Section 4.2 of [RFC4288]. Also note that while this syntax allows names of up to 127 characters, implementation limits may make such long names problematic. For this reason, <type-name> and <subtype-name> SHOULD be l…

…pe-name ; Where "type-name" and "subtype-name" are ; defined in Section 4.2 of [RFC4288]. Description: This parameter can be specified on properties that are used to reference an object. The parameter specifies the media type [RFC4288] of the referenced object. For example, on th…

…pe-name ; Where "type-name" and "subtype-name" are ; defined in Section 4.2 of [RFC4288]. Description: This parameter can be specified on properties that are used to reference an object. The parameter specifies the media type [RFC4288] of the referenced object. For example, on th…

…pe-name ; Where "type-name" and "subtype-name" are ; defined in Section 4.2 of [RFC4288] Description: This parameter can be specified on properties that are used to reference an object. The parameter specifies the media type [ RFC4288 ] of the referenced object. For example, on t…

…he following rules are included from [ RFC3986 ]: URI and URI-Reference; from [ RFC4288 ]: type-name and subtype-name; from W3C.REC-html401-19991224 ]: MediaDesc; from [ RFC5646 ]: Language-Tag; and from [ RFC5987 ], ext-value and parmname. Nottingham Standards Track [Page 3] RFC…