Re: [payload] WGLC on draft-ietf-payload-melpe-02

"Roni Even" <ron.even.tlv@gmail.com> Mon, 08 August 2016 21:40 UTC

Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: payload@ietfa.amsl.com
Delivered-To: payload@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2CF712D158; Mon, 8 Aug 2016 14:40:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 ppLnBerFNVMk; Mon, 8 Aug 2016 14:40:44 -0700 (PDT)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 207B912D176; Mon, 8 Aug 2016 14:40:44 -0700 (PDT)
Received: by mail-wm0-x232.google.com with SMTP id q128so143172518wma.1; Mon, 08 Aug 2016 14:40:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:thread-index:content-language; bh=u0TBkdx9w2eInWkgPDrIFWzwPwGPt+H5XL8zROnGIRg=; b=nPtZZppzYWzZpPXhj6sfFTbB3Mjvk+IgmaoNBdk51SxWJz7CXluUBWOfsLw+rkdkYj aLBKJMY0cJMB39jj3cHDXO/PtulRBuzF+Uwsac6tUEoaJQ1x4sUxUQugqxLalGt3541y 04aPR5h670rY7tYnT4aJiy/gvvHdQT+zqGRavwnWWK+ryBLXKigKHOXoNb/bPmN3Cjqi daqyU2sj8XCNSBJmSENa4uQprHDLCVQnc2REww3ro6vlpQdbTDkyP6uVCPD8Z7WcdieY NDgWouUNDzDrFD/ttikN0UXfgXTBlkgmBoLuFyJIa8jdLElzEIl1YqoGqmk06g6aeir/ eGVg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=u0TBkdx9w2eInWkgPDrIFWzwPwGPt+H5XL8zROnGIRg=; b=iLH94/cVftx9IVzEuH5eMrR6kz8FbR2LeOjRIP6l7s0pENbHliPUSjNWJ23g8TA6Vy EzAqw1yiL1OqzjWmi8FLTMTIxiQuw8NTxP7WtT67Do0bcVa/i3OCaiGzzy4W11xptqRZ yeBcGVx7ByIIMV5pMXfEgsiUZMNA1uFNAgLF6vInsgt1lUczfgo1+HV1yeqaI4S9v9lc 2+ouCZE8BokiITWc5rDWACmGLiJiyCKvDdCe3wmnJNJyMnbe8gwTvA2nCLh44Jdta2HV XtAa4zM+Yef3OpPbw4p8SVL7jiCgy2AZcqqhkGW26FuH9d3uafZgfAN3oOZ84EjSGykE Mjpg==
X-Gm-Message-State: AEkoouuZylauyXGb31uy04GnqHpID1+/nPyhwDerePKpogMqfRRy3NTXtNzH+c7nlcTEjA==
X-Received: by 10.28.199.131 with SMTP id x125mr18364810wmf.49.1470692442321; Mon, 08 Aug 2016 14:40:42 -0700 (PDT)
Received: from RoniPC (bzq-79-176-39-238.red.bezeqint.net. [79.176.39.238]) by smtp.gmail.com with ESMTPSA id q186sm303980wma.1.2016.08.08.14.40.40 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 08 Aug 2016 14:40:41 -0700 (PDT)
From: Roni Even <ron.even.tlv@gmail.com>
To: payload@ietf.org
References:
In-Reply-To:
Date: Tue, 09 Aug 2016 00:40:28 +0300
Message-ID: <011901d1f1bd$7b734580$7259d080$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_011A_01D1F1D6.A0C1DD10"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdHnBhrfOOr7ktHaRfyfFTzHl5kaagKsQreA
Content-Language: he
Archived-At: <https://mailarchive.ietf.org/arch/msg/payload/QDMVt19JrLNdmBbUDufIqYumBr4>
Cc: draft-ietf-payload-melpe@ietf.org
Subject: Re: [payload] WGLC on draft-ietf-payload-melpe-02
X-BeenThere: payload@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Audio/Video Transport Payloads working group discussion list <payload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/payload>, <mailto:payload-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/payload/>
List-Post: <mailto:payload@ietf.org>
List-Help: <mailto:payload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/payload>, <mailto:payload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2016 21:40:46 -0000

Hi,

I reviewed the document and have some comments

 

1.       In the abstract you can delete the last sentence "Also, within the
document there are included necessary details for the use of MELP with SDP."


2.       I assume that sections 3.1.1, 3.1.2, 3.1.3, 3.2 are copied from
STANAG 4591 in which case you can just provide a reference to the relevant
sections

3.       In section 3.3 it looks like a MELPE packet can be of zero coded
frame and zero comfort noise frame?

4.       For section 3.4 look at RFC7587 section 5 for text suggestions

5.       In section 4.1 the type name is audio while the subtype names are
MELP,.

6.       In section 4.1 published specification "RFCXXXX" to be replaced by
the RFC Editor

7.       In section 4.2 we do not use MIME but "media type" (audio) and
"media subtype " (MELPE,.)

8.       The following text is not clear "A remote MELPe encoder SHALL
receive "bitrate" parameter in the SDP "a=fmtp" attribute by copying them
directly from the MIME media type string as a semicolon separated with
parameter=value, where parameter is "bitrate", and value can be one or more
of 2400, 1200, and 600 separated by commas (where each bit-rate value
indicates the corresponding MELPe coder). Is this for the an offer?

9.       We use "For declarative SDP" and not "For streaming media". It also
better to have a sub section for SDP offer answer considerations and
Declarative SDP considerations

10.   In section 8 "its media decoder" use "the MELPe encoder"

 

Roni Even

 

From: Roni Even [mailto:ron.even.tlv@gmail.com] 
Sent: Tuesday, July 26, 2016 9:24 AM
To: 'payload@ietf.org' (payload@ietf.org)
Cc: 'draft-ietf-payload-melpe@ietf.org'
Subject: WGLC on draft-ietf-payload-melpe-02

 

Hi,

I would like to start a WGLC on
https://tools.ietf.org/html/draft-ietf-payload-melpe-02  , RTP Payload
Format for MELPe Codec
 
 
 

The WGLC will end on August 9th , 2016

 

Please review the draft and send comments to the list.

 

For the draft authors;  Are you aware of any IPR that applies to
draft-ietf-payload-melpe-02? 

If so, has this IPR been disclosed in compliance with IETF IPR rules?

The above question is needed for the document write-up when sent to
publication.
 
 

Thanks

 

Roni Even

Payload  co-chair