IETF Logo Mail Archive

Re: [MMUSIC] Last Call: <draft-ietf-mmusic-sdp-g723-g729-04.txt> (Offer/Answer Considerations for G723 Annex A and G729 Annex B) to Proposed Standard

SM <sm@resistor.net> Wed, 04 December 2013 16:12 UTC

Return-Path: <sm@resistor.net>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC7B11AE155 for <mmusic@ietfa.amsl.com>; Wed, 4 Dec 2013 08:12:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.49
X-Spam-Level:
X-Spam-Status: No, score=-1.49 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, MIME_8BIT_HEADER=0.3, T_DKIM_INVALID=0.01] 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 34oTcY8fC1-j for <mmusic@ietfa.amsl.com>; Wed, 4 Dec 2013 08:12:04 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id E2BDB1AE2D4 for <mmusic@ietf.org>; Wed, 4 Dec 2013 08:11:58 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id rB4GBi57013771; Wed, 4 Dec 2013 08:11:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1386173511; bh=zlYH4qS+HMNkrTH3LZMkq4+56AMJITZT+KOb61LhXls=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=omuvtXQTV/lZ98bpvRgAm0FrgkiJQdholtXVY8KLnlpOawfo28e+ELD4V5ilaumN0 X+5uTBmRK3BGMjjX8bYkvoWmOsKHm/zBesR9IRpCdi2yFIIWxzTtax2LUh8sEJK9rG 6K6dWsD1ngd92CK4C16BsTGzLaN6R8ymvLmENcs4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1386173511; i=@resistor.net; bh=zlYH4qS+HMNkrTH3LZMkq4+56AMJITZT+KOb61LhXls=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=qU4hkQgckathwOQMVkBICXFXC7pstEzjXgSmAqYw1JUqKoegGABgjljsrv5V93qIK u0LtYv4f7rmzJHMQAraz5XE6Ou3zOzsdPUoNPzJsDFh/1qJWv5vtKmT+fhF2zC5CGZ 3u0nJIWQ+LiI5Ev6PgoxFftCRZUQ7KYYhqeTOBg8=
Message-Id: <6.2.5.6.2.20131204072722.0e064590@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 04 Dec 2013 08:11:17 -0800
To: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>, Ari Keränen <ari.keranen@ericsson.com>
From: SM <sm@resistor.net>
In-Reply-To: <E721D8C6A2E1544DB2DEBC313AF54DE2243737E1@xmb-rcd-x02.cisco .com>
References: <20131030131748.6987.86198.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131030185231.0ddfb7a8@resistor.net> <00a101ced981$77414d60$65c3e820$@co.in> <00ab01cee555$05f53560$11dfa020$@co.in> <6.2.5.6.2.20131119110213.0cb0dd40@resistor.net> <003301cee952$852cd120$8f867360$@co.in> <6.2.5.6.2.20131129000812.0bdaa088@resistor.net> <016d01ceed31$aa7a1130$ff6e3390$@co.in> <6.2.5.6.2.20131130003721.0d65a980@resistor.net> <E721D8C6A2E1544DB2DEBC313AF54DE22436AD4D@xmb-rcd-x02.cisco.com> <6.2.5.6.2.20131203011102.0db5d8c0@resistor.net> <E721D8C6A2E1544DB2DEBC313AF54DE2243737E1@xmb-rcd-x02.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: "Flemming Andreasen (fandreas)" <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Last Call: <draft-ietf-mmusic-sdp-g723-g729-04.txt> (Offer/Answer Considerations for G723 Annex A and G729 Annex B) to Proposed Standard
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Dec 2013 16:12:05 -0000

Hi Muthu,
At 22:28 03-12-2013, Muthu Arul Mozhi Perumal (mperumal) wrote:
>Sorry, not clear to me. Can you provide some examples?

As an example:

   "The reproduction of the [RFC4695] IANA considerations section appears
    directly below.

    This section makes a series of requests to IANA.  The IANA has
    completed registration/assignments of the below requests."

Please note that I picked one at random.

>Also, draft-ietf-mmusic-sdp-g723-g729-04 doesn't need any IANA 
>action (see the IANA Considerations section). So, why should it be 
>published as an Informational RFC?

The issue (using the word loosely) is that the draft is referring to 
a registration request in Section 1.1 of RFC 4856 which is about IANA 
Considerations.  My argument is that the working group has not 
provide an explanation about why the proposal should be published on 
the Standards Track.  Instead of objecting to the publication as a 
RFC I suggested publishing the proposal as an Informational RFC.

Regards,
-sm

v2.23.0 | Report a Bug | By Email