[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [AVT] RTCP-XR MIB Comments (1)



Thanks, Magnus. Your recollection is close to mine, and your clarification helps. My reading of the phrase "Magnus Westerlund noted that the RTP MIB also needs to be updated for the changes between RFC 1889 and RFC 3550, and this may be an appropriate time to make these changes." was that this statement should be taken as a WG Chair advice. I also had break-out discussions with Alan, as well as a conference call with Allison and Bert after the meeting, all going in the same direction. 

As to the question:

> As MIBs 
> are not my 
> expertise, I would greatly appreciate comments about if it is 
> possible to 
> create the RTCP XR module without updating RFC 2959?
> 

My answer would be that technically you could, but this would not be the appropriate path to take. If RFC 3611 is based upon RFC 3550, and not on the previous version of RTP, the MIB modules should reflect this. More generally, a WG that 'owns' a protocol, should also take responsibility to update the respective MIB modules according to the evolution of the protocol.

Regards,

Dan



> -----Original Message-----
> From: Magnus Westerlund [mailto:magnus.westerlund at ericsson.com]
> Sent: 28 July, 2004 2:54 PM
> To: Romascanu, Dan (Dan)
> Cc: Alan Clark; avt at ietf.org; bwijnen at lucent.com
> Subject: Re: [AVT] RTCP-XR MIB Comments (1)
> 
> 
> Hi Alan and Dan,
> 
> See below:
> 
> Romascanu, Dan (Dan) wrote:
> 
> >     */[Romascanu, Dan (Dan)] I am not sure that I 
> understand the chairs
> >     guidance here. My suggestion in a previous AVT meeting, which I
> >     understood was agreed by the chairs and by the Area Directors
> >     (Alison, Bert) - but maybe I mis-read their heads nodding - was
> >     that to have two documents:/*
> > 
> >         * */RTPv2 MIB - which will be a revision of RFC 
> 2959, bringing
> >           it up-to-date with RFC 3550, and incorporating 
> eventual field
> >           experience/*
> >         * */RTCP-XR MIB - your document/*
> > 
> >     */What seems to have happened is that we do not have an 
> RTPv2 MIB,
> >     while the RTCP-XR MIB is titled as 'RTPv2 MIB' which is 
> confusing/*
> 
> 
> Dan, I do also remember such an discussion to have two 
> documents. However 
> the notes from the meeting (IETF 58) does only note the following:
> 
> "Proposed additions to RTP MIB
> <draft-clark-avt-rtpmibv2-00.txt>
>     The final presentation of the meeting was from Alan Clark on
> proposed additions to the RTP MIB. The rationale for these 
> additions is to
> add support for the new RTCP XR and VoIP metrics.  The draft 
> does this by
> adding an rtcpXrVoipTable to the existing MIB, to support 
> both basic call
> information and RTCP XR
> metrics.
> 
>     Several people expressed concern about adding new 
> features to RFC 2959,
> suggesting instead that the additions are written as a separate draft,
> perhaps under a separate MIB root. Magnus Westerlund noted 
> that the RTP MIB
> also needs to be updated for the changes between RFC 1889 and 
> RFC 3550, and
> this may be an appropriate time to make these changes."
> 
> I did also listen to the audio tape again, and it is clear 
> that their where 
> comments both about splitting XR from the general RTP and 
> that the RTP MIB 
> (RFC 2959) should be updated. Colin ended the session, with 
> that we where 
> going to figure out how to proceed.
> 
> I do also find notes from that session indicating some sort 
> of agreement to 
> do both update and a separate RTCP XR MIB module. As its 
> rather long ago, I 
> am not certain what actually happened or was agreed in the off-line 
> discussion.
> 
> Alan, please rename the current draft-clark-avt-rtpmibv2-01.txt into 
> something more appropriate in the next version. It would also 
> be greatly 
> appreciated if you could look into updating RFC 2959. As MIBs 
> are not my 
> expertise, I would greatly appreciate comments about if it is 
> possible to 
> create the RTCP XR module without updating RFC 2959?
> 
> 
> Cheers
> 
> 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 at ericsson.com
> 

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