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

Bjoern Hoehrmann <derhoermi@gmx.net> Fri, 20 January 2012 23:41 UTC

Return-Path: <derhoermi@gmx.net>
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 6579521F84F7 for <ietf-types@ietfa.amsl.com>; Fri, 20 Jan 2012 15:41:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.263
X-Spam-Level:
X-Spam-Status: No, score=-3.263 tagged_above=-999 required=5 tests=[AWL=-0.664, BAYES_00=-2.599]
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 WUfCqckdtlwx for <ietf-types@ietfa.amsl.com>; Fri, 20 Jan 2012 15:41:41 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 2A55D21F84F1 for <ietf-types@ietf.org>; Fri, 20 Jan 2012 15:41:40 -0800 (PST)
Received: (qmail invoked by alias); 20 Jan 2012 23:41:39 -0000
Received: from dslb-094-223-223-057.pools.arcor-ip.net (EHLO HIVE) [94.223.223.57] by mail.gmx.net (mp071) with SMTP; 21 Jan 2012 00:41:39 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1+h0yADbpGhDx7hvLtJALORRI3+KD+Dbc3BK9RBzF AS5Q4Z65Ow8oTF
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Date: Sat, 21 Jan 2012 00:41:52 +0100
Message-ID: <q0ujh71l51q36riieq9c54jbjv18l421nn@hive.bjoern.hoehrmann.de>
References: <CD5674C3CD99574EBA7432465FC13C1B226F573B9E@DC-US1MBEX4.global.avaya.com>, <hi7jh75btakoa7q8sai74juabdujda2tt5@hive.bjoern.hoehrmann.de> <CD5674C3CD99574EBA7432465FC13C1B226F573BA8@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B226F573BA8@DC-US1MBEX4.global.avaya.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 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:41:43 -0000

* Worley, Dale R (Dale) wrote:
>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.]]

Regard the comment as an editorial nit that does not really have to be
addressed. My problem is that I do not know "Media Resource Broker" in
the way I know "video conferencing system", "photo editor", or "real-
time chat application". Something about the problem it solves (random
example, "Informs SIP applications of available communication options")
or the enviroment it is used in (random example, "real-time telephony
applications") would be nice, but if there is any trouble coming up with
text for that, don't bother trying as far as I am concerned.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/