From nobody Mon Feb 8 07:04:15 2016 Return-Path: X-Original-To: payload@ietfa.amsl.com Delivered-To: payload@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F09181B2CAB for ; Mon, 8 Feb 2016 07:04:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.901 X-Spam-Level: X-Spam-Status: No, score=-0.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MSGID_MULTIPLE_AT=1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QGauVPYnEVGU for ; Mon, 8 Feb 2016 07:04:12 -0800 (PST) Received: from cuda.olm1.com (cuda.olm1.com [72.236.255.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 642B31B2CA7 for ; Mon, 8 Feb 2016 07:04:12 -0800 (PST) X-ASG-Debug-ID: 1454943850-092fd30ef61fa880001-U2jSCT Received: from host105.olm1.com (host105.olm1.com [72.236.255.15]) by cuda.olm1.com with ESMTP id WuxM3fiMo4duAezA (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 08 Feb 2016 10:04:10 -0500 (EST) X-Barracuda-Envelope-From: victor.demjanenko@vocal.com X-Barracuda-Apparent-Source-IP: 72.236.255.15 Received: from ClintonLT (rrcs-72-43-202-98.nys.biz.rr.com [72.43.202.98]) by host105.olm1.com (Postfix) with ESMTPSA id 870B5B43260; Mon, 8 Feb 2016 10:04:10 -0500 (EST) From: "Victor Demjanenko, Ph.D." To: "'DRAGE, Keith \(Keith\)'" , References: <20151104044344.11354.19004.idtracker@ietfa.amsl.com> <949EF20990823C4C85C18D59AA11AD8BADE028E9@FR712WXCHMBA10.zeu.alcatel-lucent.com> In-Reply-To: <949EF20990823C4C85C18D59AA11AD8BADE028E9@FR712WXCHMBA10.zeu.alcatel-lucent.com> Date: Mon, 8 Feb 2016 10:04:09 -0500 X-ASG-Orig-Subj: RE: [payload] I-D Action: draft-ietf-payload-melpe-00.txt Message-ID: <05fe01d16281$f6d3bd70$e47b3850$@demjanenko@vocal.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AQHRFrtyJpSCjM79zU6iH3EHt1DfhZ6Se8/QgJBW72A= Content-Language: en-us X-Barracuda-Connect: host105.olm1.com[72.236.255.15] X-Barracuda-Start-Time: 1454943850 X-Barracuda-Encrypted: ECDHE-RSA-AES256-GCM-SHA384 X-Barracuda-URL: https://72.236.255.32:443/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at olm1.com X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.01 X-Barracuda-Spam-Status: No, SCORE=0.01 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=5.0 tests=MSGID_MULTIPLE_AT X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.26857 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.01 MSGID_MULTIPLE_AT Message-ID contains multiple '@' characters Archived-At: Subject: Re: [payload] I-D Action: draft-ietf-payload-melpe-00.txt X-BeenThere: payload@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Audio/Video Transport Payloads working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Feb 2016 15:04:14 -0000 Hi Everyone, We are reposting our MELP RTP payload draft with the suggested revision to the abstract. We have not heard of any other issues so we are hoping to advance this draft toward an RFC. What would the next step(s) be? Thanks Keith for the review and suggestion. Definitely better this way. Regards, Victor -----Original Message----- From: payload [mailto:payload-bounces@ietf.org] On Behalf Of DRAGE, Keith (Keith) Sent: Sunday, November 8, 2015 1:56 PM To: payload@ietf.org Subject: Re: [payload] I-D Action: draft-ietf-payload-melpe-00.txt The abstract of this document could do with something of a revision. The abstract should concentrate on what this document is, which is a payload format for MELPe, along with the associated SDP usage. How MELPe was developed and financed should go in the introduction, if it appears at all. Regards Keith -----Original Message----- From: payload [mailto:payload-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org Sent: 04 November 2015 04:44 To: i-d-announce@ietf.org Cc: payload@ietf.org Subject: [payload] I-D Action: draft-ietf-payload-melpe-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Audio/Video Transport Payloads Working Group of the IETF. Title : RTP Payload Format for MELPe Codec Authors : Victor Demjanenko David Satterlee Filename : draft-ietf-payload-melpe-00.txt Pages : 26 Date : 2015-11-03 Abstract: This document describes the RTP payload format for the Mixed Excitation Linear Prediction Enhanced (MELPe) speech coder algorithm developed by Atlanta Signal Processing (ASPI), Texas Instruments (TI), SignalCom (now Microsoft) and Thales Communications with noise preprocessor contributions from AT&T under contract with NSA/DOD as international NATO Standard STANAG 4591. All three different speech encoding rates and sample frames sizes are included. Comfort noise procedures and packet loss concealment are detailed. Also, within the document there are included necessary details for the use of MELP with SDP. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-payload-melpe/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-payload-melpe-00 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ payload mailing list payload@ietf.org https://www.ietf.org/mailman/listinfo/payload _______________________________________________ payload mailing list payload@ietf.org https://www.ietf.org/mailman/listinfo/payload From nobody Mon Feb 8 10:15:22 2016 Return-Path: X-Original-To: payload@ietf.org Delivered-To: payload@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A6871B30AB; Mon, 8 Feb 2016 10:15:20 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.14.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160208181520.5009.75470.idtracker@ietfa.amsl.com> Date: Mon, 08 Feb 2016 10:15:20 -0800 Archived-At: Cc: payload@ietf.org Subject: [payload] I-D Action: draft-ietf-payload-melpe-01.txt X-BeenThere: payload@ietf.org X-Mailman-Version: 2.1.15 List-Id: Audio/Video Transport Payloads working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Feb 2016 18:15:20 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Audio/Video Transport Payloads of the IETF. Title : RTP Payload Format for MELPe Codec Authors : Victor Demjanenko David Satterlee Filename : draft-ietf-payload-melpe-01.txt Pages : 26 Date : 2016-02-08 Abstract: This document describes the RTP payload format for the Mixed Excitation Linear Prediction Enhanced (MELPe) speech coder. MELPe's three different speech encoding rates and sample frames sizes are supported. Comfort noise procedures and packet loss concealment are detailed. Also, within the document there are included necessary details for the use of MELP with SDP. INTERNET DRAFT RTP Payload Format for the MELPe Codec February 8, 2016 The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-payload-melpe/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-payload-melpe-01 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-payload-melpe-01 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Wed Feb 17 08:26:57 2016 Return-Path: X-Original-To: payload@ietf.org Delivered-To: payload@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F3EC01A8A0F; Wed, 17 Feb 2016 08:14:46 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Meeting Session Request Tool\"" To: X-Test-IDTracker: no X-IETF-IDTracker: 6.14.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160217161446.9832.74348.idtracker@ietfa.amsl.com> Date: Wed, 17 Feb 2016 08:14:46 -0800 Archived-At: X-Mailman-Approved-At: Wed, 17 Feb 2016 08:26:56 -0800 Cc: payload-chairs@ietf.org, payload@ietf.org Subject: [payload] payload - Not having a session at IETF 95 X-BeenThere: payload@ietf.org X-Mailman-Version: 2.1.15 List-Id: Audio/Video Transport Payloads working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Feb 2016 16:14:47 -0000 Ali Begen, a chair of the payload working group, indicated that the payload working group does not plan to hold a session at IETF 95. This message was generated and sent by the IETF Meeting Session Request Tool.