IETF Logo Mail Archive

Re: [MMUSIC] Notification for draft-salgueiro-mmusic-image-iana-registration-00

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Thu, 28 April 2011 10:06 UTC

Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A9A2E06D7 for <mmusic@ietfa.amsl.com>; Thu, 28 Apr 2011 03:06:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.952
X-Spam-Level:
X-Spam-Status: No, score=-105.952 tagged_above=-999 required=5 tests=[AWL=0.296, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UXZTfjOEfBmS for <mmusic@ietfa.amsl.com>; Thu, 28 Apr 2011 03:06:25 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id 71531E0676 for <mmusic@ietf.org>; Thu, 28 Apr 2011 03:06:25 -0700 (PDT)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p3SA4qhQ029586 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 28 Apr 2011 12:06:21 +0200
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.47]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Thu, 28 Apr 2011 12:06:06 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Gonzalo Salgueiro <gsalguei@cisco.com>
Date: Thu, 28 Apr 2011 12:06:05 +0200
Thread-Topic: [MMUSIC] Notification for draft-salgueiro-mmusic-image-iana-registration-00
Thread-Index: AcwE+0dXxg38DYbbTsyDnpxTxKYftQAkFxZA
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE21F5DBC87@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <27FDAD4D-2EC4-48D1-A357-622BE582BDCA@cisco.com> <EDC0A1AE77C57744B664A310A0B23AE21F5DBB63@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <1A1E3EC8-7BBA-4A6F-A1E2-E90399D5012C@cisco.com>
In-Reply-To: <1A1E3EC8-7BBA-4A6F-A1E2-E90399D5012C@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_EDC0A1AE77C57744B664A310A0B23AE21F5DBC87FRMRSSXCHMBSC3d_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Cc: Flemming Andreasen <fandreas@cisco.com>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] Notification for draft-salgueiro-mmusic-image-iana-registration-00
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 28 Apr 2011 10:06:26 -0000

But then there is no RFC 2119 language used in the document, except for extracted text (with associated references) from other documents, where the conventions in those other documents have to apply, rather than the ones in this document.

Check with the RFC editor on the need for the 2119 boilerplate when no such usage is made.

Regards

Keith

________________________________
From: Gonzalo Salgueiro [mailto:gsalguei@cisco.com]
Sent: 27 April 2011 17:51
To: DRAGE, Keith (Keith)
Cc: mmusic; Flemming Andreasen
Subject: Re: [MMUSIC] Notification for draft-salgueiro-mmusic-image-iana-registration-00

Many thanks for the feedback Keith.

If we think there is value in making things a bit more brief by removing the references to RFC 5226 and the SDP media type registry, then I can certainly accommodate that.

FYI - The reference to RFC 2119 is in Section 1.

Warm Regards,

Gonzalo

On Apr 27, 2011, at 9:57 AM, DRAGE, Keith (Keith) wrote:


Section 3

  This document registers with IANA the 'image' media type in the
  Session Description Protocol (SDP) Parameters registry [SDP-IANA] in
  accordance with the "Standards Action" policy defined in Section 4.1
  of [RFC5226].


>From the perspective of brevity, I do not believe the reference to RFC 5226 is necessary. IANA will apply the policy stated in the table, which now exists, rather than anything that is said in this RFC. I also do not believe you need the [SDP-IANA] reference. If you put the full stop after "registry" you have clearly identified the table to IANA.

  This document registers with IANA the 'image' media type in the
  Session Description Protocol (SDP) Parameters registry.

References

RFC 2119 is never used as a reference. Delete.

Otherwise the document looks good to me.

Regards

Keith

________________________________________
From: mmusic-bounces@ietf.org<mailto:mmusic-bounces@ietf.org> [mailto:mmusic-bounces@ietf.org] On Behalf Of Gonzalo Salgueiro
Sent: 26 April 2011 19:28
To: mmusic
Cc: Flemming Andreasen
Subject: [MMUSIC] Notification for draft-salgueiro-mmusic-image-iana-registration-00

Folks,

In reference to some discussion we had on the list recently, I wanted to bring your attention to an Internet Draft I submitted that registers 'image' in the newly created SDP media type registry. For some reason (unbeknownst to me) this was omitted in RFC 4566 when the other media types were registered. This draft aims to rectify that oversight.

The draft can be found at:

http://tools.ietf.org/html/draft-salgueiro-mmusic-image-iana-registration-00

I would welcome any comments on the draft.

Warm Regards,

Gonzalo

v2.29.0 | Report a Bug | By Email | System Status