idnits 2.17.1 draft-ema-vpim-dur-02.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 2 longer pages, the longest (page 2) being 59 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. (A line matching the expected section header was found, but with an unexpected indentation: ' 1. Abstract' ) ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 4. Security considerations:' ) ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack an Authors' Addresses Section. ** There are 23 instances of too long lines in the document, the longest one being 2 characters in excess of 72. ** The abstract seems to contain references ([VPIM2], [MIME2]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 90: '... Messages MUST contain this sub-t...' Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (July 29, 1997) is 9767 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? 'VPIM2' on line 129 looks like a reference -- Missing reference section? 'MIME2' on line 125 looks like a reference Summary: 14 errors (**), 0 flaws (~~), 2 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Greg Vaudreuil 3 Internet Draft Octel Communications 4 Expires in six months Glenn Parsons 5 Nortel Technology 6 July 29, 1997 8 Content Duration 9 MIME Header Definition 11 13 Status of this Memo 15 This document is an Internet Draft. Internet Drafts are working 16 documents of the Internet Engineering Task Force (IETF), its Areas, 17 and its Working Groups. Note that other groups may also distribute 18 working documents as Internet Drafts. 20 Internet Drafts are valid for a maximum of six months and may be 21 updated, replaced, or obsoleted by other documents at any time. It 22 is inappropriate to use Internet Drafts as reference material or to 23 cite them other than as a "work in progress". 25 To learn the current status of any Internet-Draft, please check the 26 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 27 Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), 28 munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or 29 ftp.isi.edu (US West Coast). 31 Overview 33 This document describes the MIME header Content-Duration that is 34 intended for use with any timed media content (typically audio/* or 35 video/*). 37 1. Abstract 39 This document describes the MIME header Content-Duration that is 40 intended for use with any time varying media content (typically 41 audio/* or video/*). The length of time is represented in seconds 42 without any units indication.. 44 2. Content-Duration Header Field 46 Time varying media contents, for example, a spoken voice message or 47 a video clip, have an inherent time duration. Many audio and video 48 encodings may include their duration as header information or may 49 allow accurate calculation based on the byte length of the data. 50 However, it may be useful to present the time duration of the 51 content in a MIME header to allow its simple determination without 52 dealing with the actual content. 54 2.1 Syntax 56 The Content-Duration field's value is a single number specifying the 57 time duration in seconds of the content. Formally: 59 duration := "Content-Duration" ":" 1*10DIGIT 61 Note that practically (though highly unlikely in MIME media), the 62 upper bound on the numerical value of the time duration is (2^^31 - 63 1) or 2147483647. 65 2.2 Semantics 67 This field represents the time duration of the associated time 68 varying media content. The time duration is noted in seconds with 69 no units tag. The time value should be exact, however the exact 70 value of the time duration cannot be known without opening the 71 content and playing it. If an exact value must be known, then the 72 latter method should be used. This mechanism simply allows placing 73 a sender determined time duration value in the header for easy 74 access. 76 Though there are several ways to present this duration to the 77 recipient (e.g. with the inbox headers, when audio attachment 78 opened), the actual use of this field on reception is a local 79 implementation issue. 81 2.3 Example 83 In this example the content duration represents 33 seconds: 85 Content-Duration: 33 87 3. VPIM Usage 88 The Content-Duration header field for the audio/32KADPCM sub-type is 89 a useful component of the VPIM specification [VPIM2]. All VPIM 90 Messages MUST contain this sub-type to carry the audio of a voice 91 message. It may be useful in some instances (e.g. viewing on a 92 simple MIME or non-MIME desktop) to have the time duration of the 93 voice message available without having to open the audio content. 95 4. Security considerations: 97 This defintion introduces the option of explicitly identifying the 98 time duration of an audio/* or video/* content outside of the binary 99 data that forms the content. In some environments (though likely 100 not the majority), the identification of the actual time duration in 101 a header field may be a security issue and as a result should not be 102 noted. 104 5. Authors' Addresses 106 Glenn W. Parsons 107 Nortel Technology 108 P.O. Box 3511, Station C 109 Ottawa, ON K1Y 4H7 110 Canada 111 Phone: +1-613-763-7582 112 Fax: +1-613-763-8385 113 Glenn.Parsons@Nortel.ca 115 Gregory M. Vaudreuil 116 Octel Communications 117 17080 Dallas Parkway 118 Dallas, TX 75248-1905 119 United States 120 Phone/Fax: +1-972-733-2722 121 Greg.Vaudreuil@Octel.Com 123 6. References 125 [MIME2] N. Freed and N. Borenstein, "Multipurpose Internet Mail 126 Extensions (MIME) Part Two: Media Types ", RFC 2046, Innosoft, 127 First Virtual, Nov 1996. 129 [VPIM2] Greg Vaudreuil and Glenn Parsons, "Voice Profile for 130 Internet Mail - version 2", Work in Progress, July 1997.