…reason not to. The registration process for these media types is described in [ RFC2048 ]. The registrar for the IETF tree will encourage new XML- based media type registrations in the IETF tree to follow this guideline. Registrars for other trees SHOULD follow this convention Mu…

…g reason not to. The registration process for these media types is described in RFC2048 ]. The registrar for the IETF tree will encourage new XML- based media type registrations in the IETF tree to follow this guideline. Registrars for other trees SHOULD follow this convention Mu…

…ocuments, specifically the MIME document series [ RFC2045 , RFC2046 , RFC2047 , RFC2048 , RFC2049 ], that extend this standard to allow for values outside of that range. Discussion of those mechanisms is not within the scope of this standard. Messages are divided into lines of ch…

… documents, specifically the MIME document series [RFC2045, RFC2046 , RFC2047 , RFC2048 , RFC2049 ], that extend this standard to allow for values outside of that range. Discussion of those mechanisms is not within the scope of this standard. Messages are divided into lines of ch…

…ther documents, specifically the MIME document series [RFC2045, RFC2046 RFC2047 RFC2048 RFC2049 ], that extend this standard to allow for values outside of that range. Discussion of those mechanisms is not within the scope of this standard. Messages are divided into lines of char…

…ther documents, specifically the MIME document series [RFC2045, RFC2046 RFC2047 RFC2048 RFC2049 ], that extend this standard to allow for values outside of that range. Discussion of those mechanisms is not within the scope of this standard. Messages are divided into lines of char…

…ther documents, specifically the MIME document series [RFC2045, RFC2046 RFC2047 RFC2048 RFC2049 ], that extend this standard to allow for values outside of that range. Discussion of those mechanisms is not within the scope of this standard. Messages are divided into lines of char…

…er documents, specifically the MIME document series [RFC2045, RFC2046, RFC2047, RFC2048, RFC2049], that extend this standard to allow for values outside of that range. Discussion of those mechanisms is not within the scope of this standard. Messages are divided into lines of char…

…ther documents, specifically the MIME document series [RFC2045, RFC2046 RFC2047 RFC2048 RFC2049 ], that extend this standard to allow for values outside of that range. Discussion of those mechanisms is not within the scope of this standard. Messages are divided into lines of char…

…excessively restrictive and had to be generalized. This was initially done in [ RFC2048 ], but the procedure defined there was still part of the MIME document set. The media type specification and registration procedure has now been moved to this separate document, to make it cle…

… excessively restrictive and had to be generalized. This was initially done in [RFC2048], but the procedure defined there was still part of the MIME document set. The media type specification and registration procedure is now a separate document, to make it clear that it is indep…

…6 The Internet and the Millennium Problem (Year 2000) June 1999 +=+=+=+=+= File rfc2048 .txt +=+=+=+=+= 'yy' on a line without 'yyyy' found at line 738: 736: 737: To: ietf-types@iana.org 738: Subject: Registration of MIME media type XXX/YYY 739: 740: MIME media type name: +=+=+=+…