IETF Logo Mail Archive

Re: [AVT] Follow up to AVT meeting - RTCP XR MIB vs RTP MIB

Magnus Westerlund <magnus.westerlund@ericsson.com> Mon, 11 April 2005 13:48 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14300 for <avt-archive@ietf.org>; Mon, 11 Apr 2005 09:48:39 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DKzQl-00009s-2V for avt-archive@ietf.org; Mon, 11 Apr 2005 09:58:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DKzFs-0007NR-GE; Mon, 11 Apr 2005 09:47:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DKzFq-0007Ld-Sl for avt@megatron.ietf.org; Mon, 11 Apr 2005 09:47:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14154 for <avt@ietf.org>; Mon, 11 Apr 2005 09:46:56 -0400 (EDT)
Received: from penguin.ericsson.se ([193.180.251.47]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DKzP6-00006I-GA for avt@ietf.org; Mon, 11 Apr 2005 09:56:41 -0400
Received: from esealmw127.eemea.ericsson.se ([153.88.254.122]) by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id j3BDjXhB023497; Mon, 11 Apr 2005 15:45:34 +0200 (MEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.173]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Mon, 11 Apr 2005 15:45:33 +0200
Received: from [147.214.237.37] ([147.214.237.37]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Mon, 11 Apr 2005 15:45:33 +0200
Message-ID: <425A7F7D.6040802@ericsson.com>
Date: Mon, 11 Apr 2005 15:45:33 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Subject: Re: [AVT] Follow up to AVT meeting - RTCP XR MIB vs RTP MIB
References: <AAB4B3D3CF0F454F98272CBE187FDE2F07F67AFC@is0004avexu1.global.avaya.com>
In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F07F67AFC@is0004avexu1.global.avaya.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 11 Apr 2005 13:45:33.0414 (UTC) FILETIME=[BBA8A860:01C53E9C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit
Cc: Amy Pendleton <aspen@nortel.com>, "Avt@Ietf. Org" <avt@ietf.org>, csp@csperkins.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit

Hi Dan,

Sure, I don't want to go against any recommendations. This was only due 
to my lack of MIB knowledge. The important thing is to get good 
integration and extensibility.

Cheers

Magnus

Romascanu, Dan (Dan) wrote:
> Magnus,
> 
> I agree and support your proposal. 
> 
> I have however a concern related to your third point:
> 
> 
>>- Make RTCP XR MIB also as an addition to the common session root.
> 
> 
> If by this you mean making the RTCP XR MIB a subtree under the RTP MIB, I believe that this is not necessary, and also contrary to the design recommendations of the Operations and Management Area http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-review-guidelines-04.txt
> 
>    - The value assigned to the MODULE-IDENTITY descriptor MUST be unique
>      and (for IETF standards-track MIB modules) SHOULD reside under the
>      mgmt subtree [RFC2578].  Most often it will be an IANA-assigned
>      value directly under mib-2 [RFC2578], although for media-specific
>      MIB modules that extend the IF-MIB [RFC2863] it is customary to use
>      an IANA-assigned value under transmission [RFC2578].  In the past
>      some IETF working groups have made their own assignments from
>      subtrees delegated to them by IANA, but that practice has proven
>      problematic and is NOT RECOMMENDED.
> 
> This does not affect the integrality that you are trying to reach for the RTP MIB and RTCP XR MIB, as a OID is just a pointer in the management objects space. As long as the RTP MIB and RTCP XR MIB are different MIB modules defined by two different documents I suggest that we follow the MIB Guidelines recommendations. 
> 


-- 

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

v2.23.0 | Report a Bug | By Email