Re: [Adslmib] Vector of Profiles MIB

<Markus.Freudenberger@t-systems.com> Mon, 09 November 2009 10:27 UTC

Return-Path: <Markus.Freudenberger@t-systems.com>
X-Original-To: adslmib@core3.amsl.com
Delivered-To: adslmib@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9ECC628C1E2 for <adslmib@core3.amsl.com>; Mon, 9 Nov 2009 02:27:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.248
X-Spam-Level:
X-Spam-Status: No, score=-3.248 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3DJnWaEmWDNB for <adslmib@core3.amsl.com>; Mon, 9 Nov 2009 02:27:09 -0800 (PST)
Received: from tcmail73.telekom.de (tcmail73.telekom.de [217.243.239.135]) by core3.amsl.com (Postfix) with ESMTP id E4E1428C1DA for <adslmib@ietf.org>; Mon, 9 Nov 2009 02:27:08 -0800 (PST)
From: <Markus.Freudenberger@t-systems.com>
Received: from s4de8psaanq.blf.telekom.de (HELO S4DE8PSAANQ.mitte.t-com.de) ([10.151.180.166]) by tcmail71.telekom.de with ESMTP; 09 Nov 2009 11:27:25 +0100
Received: from S4DE8PSAANK.mitte.t-com.de ([10.151.229.10]) by S4DE8PSAANQ.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); Mon, 9 Nov 2009 11:27:24 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 9 Nov 2009 11:27:23 +0100
Message-ID: <1B6169C658325341A3B8066E23919E1C029EC7C5@S4DE8PSAANK.mitte.t-com.de>
In-Reply-To: <31373915.1257756744195.JavaMail.root@nskntwebs02p>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Adslmib] Vector of Profiles MIB
Thread-Index: AcphGfuNBAa3HmgbTm2Ihmj9WWu3OQAAWOPQ
References: <31373915.1257756744195.JavaMail.root@nskntwebs02p>
To: <sbaillie@bigpond.net.au>
X-OriginalArrivalTime: 09 Nov 2009 10:27:24.0537 (UTC) FILETIME=[3A6DBE90:01CA6127]
Cc: adslmib@ietf.org, Menachem.Dodge@ecitele.com
Subject: Re: [Adslmib] Vector of Profiles MIB
X-BeenThere: adslmib@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: ADSLMIB <adslmib.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/adslmib>, <mailto:adslmib-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/adslmib>
List-Post: <mailto:adslmib@ietf.org>
List-Help: <mailto:adslmib-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/adslmib>, <mailto:adslmib-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Nov 2009 10:27:10 -0000

Hello Scott,

First of all, I recommend to have a look at this paper: http://www.broadband-forum.org/technical/download/TR-165.pdf. It should answer a lot of your questions. 

Regarding your question 1)
Yes because Broadband Forum's TR-165 requires this. It obsoletes the object model for DSL line configuration defined in the TR-129.

Regarding your question 2)
Yes.

Regarding your question 3)
I am not sure if I got your question. TR-165 structures the xDSL configuration parameters into profiles in a different way. A vector is defined which must not necessarily represent a template.
It can be a template which summarizes a certain set of different profiles but it can also be a single DSL line with single profiles attached.
It might be useful, if you read Appendex I in TR-165. There, the implementation of "direct attached profiles" vs. "indirect attached profiles" (which is similar to the templates in the VDSL2-LINE-MIB) is described. At the end, a potintial VoP MIB should contain the option to switch between both methods.

Regarding your question 4) and 5) and 7)
I recommend to read the "Purpose ans Scope" Section of TR-165 on page 7.

Regarding your question 6)
Yes

Regarding your question 8)
The criteron should be that the VDSL2-LINE-MIB is based on the object model of TR-129, which now is obsoleted with TR-165.
But please be aware that it is not a decision of using one MIB versus another. The new "VoP MIB" deals only with configuration parameters resp. profiles and must be linked together with the VDSL2-LINE-MIB. Most Parts of RFC 5650 like notifications, line status, inventory or PM are not touched by Vector of Profiles anyway.

Hope this helps.

Regards
Markus


-----Ursprüngliche Nachricht-----
Von: sbaillie@bigpond.net.au [mailto:sbaillie@bigpond.net.au] 
Gesendet: Montag, 9. November 2009 09:52
An: Freudenberger, Markus
Cc: Menachem.Dodge@ecitele.com; adslmib@ietf.org
Betreff: Re: [Adslmib] Vector of Profiles MIB

Hi Menachem and Markus,

I think we should have a discussion first about the scope and purpose of the "Vector of Profiles MIB" proposal.

Can we please address some of the following issues :

1. Would the new MIB cover all xDSL technologies like the
    VDSL2 MIB does ?
2. Would the new MIB cover all the parameters defined in G.997.1 ?
3. Would the only difference between the VDSL2 MIB and the new
    MIB be the way templates are represented ?
4. Can you state the things that the new MIB will have that the VDSL2
    MIB does not have.
5. Can you state the things that the VDSL2 MIB has that the new
    MIB does not have.
6. Is the new MIB intended for embedded use such as in DSLAMs
    and xDSL line cards ?
7. Can you justify having two MIBs that do basically the same thing
    but do it in a slightly different way ?
8. If you are a developer of xDSL equipment, what criterion would you
    use to select one MIB or the other ?


Regards,

Scott.


---- Markus.Freudenberger@t-systems.com wrote: 
> on behalf of Deutsche Telekom, I am interested on that item.
>  
> Thanks
> Markus
>  
> ________________________________
> 
> Von: adslmib-bounces@ietf.org [mailto:adslmib-bounces@ietf.org] Im 
> Auftrag von Menachem Dodge
> Gesendet: Montag, 9. November 2009 09:22
> An: Menachem Dodge; 'adslmib@ietf.org'
> Betreff: Re: [Adslmib] Vector of Profiles MIB
> 
> 
> 
> Hello,
> 
>  
> 
> I haven't received any response to my email of last Monday. 
> 
>  
> 
> If anyone at all, has an interest in this item of work, please speak 
> up now.
> 
>  
> 
> Best Regards,
> 
> Menachem Dodge
> 
>  
> 
> From: adslmib-bounces@ietf.org [mailto:adslmib-bounces@ietf.org] On 
> Behalf Of Menachem Dodge
> Sent: Monday, November 02, 2009 7:07 PM
> To: 'adslmib@ietf.org'
> Subject: Re: [Adslmib] Vector of Profiles MIB
> 
>  
> 
> Hello All,
> 
>  
> 
> In April this year, several emails were exchanged regarding 
> development of a "Vector of Profile" MIB in accordance with the 
> Broadband Forum
> TR-165 Vector of Profiles document.
> 
> See the attached thread.
> 
>  
> 
> As this issue has been raised again, I would like to see if there is 
> an interest amongst the members of the Working Group in this work.
> 
>  
> 
> Please share your thoughts on this issue.
> 
>  
> 
> Best Regards,
> 
> Menachem
>