IETF Logo Mail Archive

Re: [ietf-types] Registration of application/mrb-publish+xml and application/mrb-consumer+xml

"Worley, Dale R (Dale)" <dworley@avaya.com> Fri, 20 January 2012 23:24 UTC

Return-Path: <dworley@avaya.com>
X-Original-To: ietf-types@ietfa.amsl.com
Delivered-To: ietf-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2888421F86C4 for <ietf-types@ietfa.amsl.com>; Fri, 20 Jan 2012 15:24:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.631
X-Spam-Level:
X-Spam-Status: No, score=-102.631 tagged_above=-999 required=5 tests=[AWL=-0.032, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id je8nYa5GZXf0 for <ietf-types@ietfa.amsl.com>; Fri, 20 Jan 2012 15:24:51 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 964A221F86C2 for <ietf-types@ietf.org>; Fri, 20 Jan 2012 15:24:51 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAAn2GU/GmAcF/2dsb2JhbABDrgqBBYFyAQEBAQIBEig/BQsCAQgNAQchEDIlAQEEDgUIGodanR+bQItDYwSIPJJUjHI
X-IronPort-AV: E=Sophos;i="4.71,545,1320642000"; d="scan'208";a="227850557"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 20 Jan 2012 18:24:50 -0500
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 20 Jan 2012 18:19:56 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.137]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Fri, 20 Jan 2012 18:24:49 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Fri, 20 Jan 2012 18:24:48 -0500
Thread-Topic: [ietf-types] Registration of application/mrb-publish+xml and application/mrb-consumer+xml
Thread-Index: AczXlkLVHPRtFsJRQhGBzHYKZF20WQAM292Q
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B226F573BA8@DC-US1MBEX4.global.avaya.com>
References: <CD5674C3CD99574EBA7432465FC13C1B226F573B9E@DC-US1MBEX4.global.avaya.com>, <hi7jh75btakoa7q8sai74juabdujda2tt5@hive.bjoern.hoehrmann.de>
In-Reply-To: <hi7jh75btakoa7q8sai74juabdujda2tt5@hive.bjoern.hoehrmann.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Lorenzo Miniero <lorenzo@meetecho.com>, Chris Boulton <chris@ns-technologies.com>, Eric Burger <eburger@standardstrack.com>, "ietf-types@ietf.org" <ietf-types@ietf.org>
Subject: Re: [ietf-types] Registration of application/mrb-publish+xml and application/mrb-consumer+xml
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jan 2012 23:24:52 -0000

> From: Bjoern Hoehrmann [derhoermi@gmx.net]
> 
> >   Published specification:   Section 10 of RFCXXXX [[NOTE TO RFC-
> >      EDITOR/IANA: Please replace XXXX with the RFC number of this
> >      specification.]].
> >
> >   Applications which use this media type:   This document type has been
> >      used to support a Media Resource Broker (MRB) entity.
> 
> I suppose this might be okay in the context of the document, in general
> it should give people like "oh, this is for document management" or "oh,
> yet enother 3d modeling format".

We will work on updating the I-D based on your comments.  But there is
a difficulty with this item:  "Media Resource Broker" is the term used
by the various vendors of MRB devices.  And this I-D is one of a very
few IETF documents that describes MRB functionality.  Unfortunately,
there is no larger, better-known class that contains MRB.

Perhaps we could at least warn the reader that the RFC is the only
generic description of MRB:

   Applications which use this media type:   This document type has been
      used to support a Media Resource Broker (MRB) entity.  MRB is
      described in RFCXXXX. [[NOTE TO RFC-EDITOR/IANA: Please replace
      XXXX with the RFC number of this specification.]]

Dale

v2.23.0 | Report a Bug | By Email