Re: [payload] Alexey Melnikov's No Objection on draft-ietf-payload-melpe-05: (with COMMENT)

["Victor Demjanenko, Ph.D." <[e-mail]>]

Hi Alexey,

Thanks for your review and comments.  Unfortunately we don't understand the
suggested change.  We understand that only section 4.1 will be extracted and
used in another document.  What we don't understand is what specifically you
see as needing to be changed or modified.  Could you please explain it to us
non-MiME types?

Below is cut and paste from our draft?

Thanks,

Victor & Dave
---------------------------------------------

4.1  Media Type Definition

   Type names:

      audio

   Subtype name:

      MELP, MELP2400, MELP1200, and MELP600

   Required parameters:

      N/A

   Optional parameters:

      ptime, maxptime, bitrate

   Encoding considerations:

      This media type is framed and binary, see section 4.8 in RFC6838
      [RFC6838].

   Security considerations:

      Please see the security considerations in section 8 of RFCxxxx
      (this RFC).

   Interoperability considerations:

      Early implementations used MELP2400, MELP1200, and MELP600 to
      indicate both coder type and bit rate.  These media type names
      should be preserved with this registration.

   Published specification:

      N/A

   Applications that use this media type:

      N/A

   Additional information:

      N/A

   Deprecated alias names for this type:

      N/A

   Magic number(s):

      N/A

   File extension(s):

      N/A

   Macintosh file type code(s):

      N/A

   Person & email address to contact for further information:

      Victor Demjanenko, Ph.D.
      VOCAL Technologies, Ltd.
      520 Lee Entrance, Suite 202
      Buffalo, NY 14228
      USA
      Phone: [phone]
      Email: [e-mail]

   Intended usage:

      COMMON

   Restrictions on usage:

      This media type depends on RTP framing, and hence is only defined
      for transfer via RTP [RFC3550].  Transport within other framing
      protocols is not defined at this time.

   Author:

      Victor Demjanenko

   Change controller:

      IETF Payload working group delegated from the IESG.

   Provisional registration? (standards tree only):

      No



-----Original Message-----
From: payload [mailto:[e-mail]] On Behalf Of Alexey Melnikov
Sent: Thursday, February 2, 2017 3:09 AM
To: The IESG
Cc: [e-mail]; [e-mail];
[e-mail]; [e-mail]
Subject: [payload] Alexey Melnikov's No Objection on
draft-ietf-payload-melpe-05: (with COMMENT)

Alexey Melnikov has entered the following ballot position for
draft-ietf-payload-melpe-05: No Objection

When responding, please keep the subject line intact and reply to all email
addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-payload-melpe/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I have a small issue, but I think it is important to address:

in Section 4.1: media type parameters not specified in the MIME type
registration, even though they are described later in the document. The MIME
type registration will be pasted to a separate file on IANA website, so it
must be self contained.


_______________________________________________
payload mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/payload