Re: [Adslmib] Vector of Profiles MIB

Menachem Dodge <Menachem.Dodge@ecitele.com> Sun, 15 November 2009 10:24 UTC

Return-Path: <Menachem.Dodge@ecitele.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 ACAD93A6956 for <adslmib@core3.amsl.com>; Sun, 15 Nov 2009 02:24:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.204
X-Spam-Level:
X-Spam-Status: No, score=-0.204 tagged_above=-999 required=5 tests=[AWL=-2.147, BAYES_00=-2.599, CN_BODY_35=0.339, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45]
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 CJcZrV9ZojJX for <adslmib@core3.amsl.com>; Sun, 15 Nov 2009 02:24:12 -0800 (PST)
Received: from ilptiron01.ecitele.com (ilptiron01.ecitele.com [147.234.242.161]) by core3.amsl.com (Postfix) with ESMTP id A21B53A6957 for <adslmib@ietf.org>; Sun, 15 Nov 2009 02:24:10 -0800 (PST)
Received: from ilptexfe.ecitele.com (HELO ILPTEXCH02.ecitele.com) ([147.234.245.181]) by ilptiron01.ecitele.com with ESMTP; 15 Nov 2009 12:14:55 +0200
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Sun, 15 Nov 2009 12:22:56 +0200
From: Menachem Dodge <Menachem.Dodge@ecitele.com>
To: "pdyu@huawei.com" <pdyu@huawei.com>, "adslmib@ietf.org" <adslmib@ietf.org>
Date: Sun, 15 Nov 2009 12:22:53 +0200
Thread-Topic: [Adslmib] Vector of Profiles MIB
Thread-Index: AcphTlF9hIqyyWBjR/648dJ2YX1cvQCZTYnwABXqO1AAdHWxAA==
Message-ID: <283DD79798619346BF9B17D7B5035A1901079812D21F@ILPTMAIL02.ecitele.com>
References: <283DD79798619346BF9B17D7B5035A19010797EA489A@ILPTMAIL02.ecitele.com> <000301ca640b$3d853b80$482c460a@china.huawei.com>
In-Reply-To: <000301ca640b$3d853b80$482c460a@china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: Moti Morgenstern <Moti.Morgenstern@ecitele.com>, "Markus.Freudenberger@t-systems.com" <Markus.Freudenberger@t-systems.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: Sun, 15 Nov 2009 10:24:13 -0000

Hello Peidaoyu,

Thank you kindly for your comments.

I'd still like to hear from more people on this subject.

Best Regards,
Menachem Dodge

-----Original Message-----
From: peidaoyu [mailto:pdyu@huawei.com] 
Sent: Friday, November 13, 2009 4:45 AM
To: Menachem Dodge; adslmib@ietf.org
Cc: Moti Morgenstern; Markus.Freudenberger@t-systems.com
Subject: 答复: [Adslmib] Vector of Profiles MIB

Hi all,
The key difference between the VoP MIB and the RFC5650 is that VoP MIB based
on TR165, and RFC5650 based on TR-129 model. TR-129 model has been used
widely now, and some network operator feedback that the TR129 and
“draft-ietf-adslmib-vdsl2-x” can not meet their requirement. 
Maybe add the VoP MIB to RFC5650 and provide a switch to switch over between
these two models is a good choice.
Best regards
Peidaoyu

-----邮件原件-----
发件人: adslmib-bounces@ietf.org [mailto:adslmib-bounces@ietf.org] 代表
Menachem Dodge
发送时间: 2009年11月13日 0:25
收件人: 'adslmib@ietf.org'
抄送: Moti Morgenstern; Markus.Freudenberger@t-systems.com
主题: Re: [Adslmib] Vector of Profiles MIB

Hello, 

Is there anyone in the working group who would like to comment on this
issue?

At this stage I'm not looking for volunteers, I'm just trying to get a feel
of how many of the working group members 
are interested that this Vector Of Profiles MIB be developed.

I would appreciate more people speaking up and sharing their opinions.

Thank you kindly,
Menachem

-----Original Message-----
From: sbaillie@bigpond.net.au [mailto:sbaillie@bigpond.net.au] 
Sent: Monday, November 09, 2009 5:07 PM
To: Moti Morgenstern
Cc: sbaillie@bigpond.net.au; Menachem Dodge; Markus.Freudenberger@t-systems.
com; adslmib@ietf.org
Subject: RE: [Adslmib] Vector of Profiles MIB

Hi Moti,

I am well, thank you.

If the VoP MIB was to go ahead, do you see it as an extension to
RFC5650 or would it be a completely new MIB with some copy and
paste from RFC5650 to get the new MIB started.

Also, what is your feeling for the demand for such a fine grained
profile model ? In my experience at NEC we are being asked to
provide the opposite approach, ISP's want 4 or 5 service types
( i.e. bronze, silver, gold, platinum ) and most of the configuration
parameters are exactly the same because each DSLAM tends to
service just one type of customer class ( e.g. FTTH or FTTC or FTTB ).

Regards,

Scott.

---- Moti Morgenstern <Moti.Morgenstern@ecitele.com> wrote: 
> Hi Scott,
> 
> How are you?
> See my embedded answers
> 
> Moti M
> 
> -----Original Message-----
> From: adslmib-bounces@ietf.org [mailto:adslmib-bounces@ietf.org] On Behalf
Of sbaillie@bigpond.net.au
> Sent: Monday, November 09, 2009 10:52 AM
> To: Markus.Freudenberger@t-systems.com
> Cc: adslmib@ietf.org; Menachem Dodge
> Subject: 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 ?
> [MM] Yes. It refers to the same TR-129 and G.997.1 documents
> 
> 2. Would the new MIB cover all the parameters defined in G.997.1 ?
> [MM] No. It more-or-less arranges the configuration parameters in a
different way.
> However, it does not address the status parameters, the PM parameters,
alarm 
> thresholds or notifications.
> 
> 3. Would the only difference between the VDSL2 MIB and the new
>     MIB be the way templates are represented ?
> [MM] In addition to (2) above, the main issue is the way 'templates' are
represented. 
> The other issue is that the 'template', which is now called 'VoP', may
belong to a 
> single line. If that ('direct') mode is being utilized then the 'template'
(VoP) is 
> indexed by the line's ifIndex rather than by an ordered identifier/number.

> 
> 4. Can you state the things that the new MIB will have that the VDSL2
>     MIB does not have.
> [MM] In principle (ignoring few details) the configuration VoP is the same
as what 
> we call 'template'. The differences are: The 'direct' vs. 'indirect' VoP
attachment 
> methods, and better (with some compromises) division of the configuration
parameters 
> into smaller, focused, profiles. There are also few minor errors (in the
vdsl2 MIB) that
> are corrected in the new MIB.
> 
> 5. Can you state the things that the VDSL2 MIB has that the new
>     MIB does not have.
> [MM] First of all, we're talking about the configuration part of the vdsl2
MIB. 
> Other parts remain the same. I think the new MIB preserves the
characteristics
> of the vdsl2 MIB, except for the indexing. The VoP and related profiles
indices are 
> numeric rather than textual. 
> 
> 6. Is the new MIB intended for embedded use such as in DSLAMs
>     and xDSL line cards ?
> [MM] yes.
> 
> 7. Can you justify having two MIBs that do basically the same thing
>     but do it in a slightly different way ?
> [MM] There is no justification. The reason VoP was invented is because
operators felt that
> TR-129 model does not divide the configuration parameters in an optimal
way and that may cause
> waste of memory. The issue of 'direct' vs. 'indirect' attachment methods
could also be solved 
> with the TR-129 model. Was it pleasant for the BBF to publish two
management models within 
> a year or two? Certainly not.
>    
> 8. If you are a developer of xDSL equipment, what criterion would you
>     use to select one MIB or the other ?
> [MM] A very good question. There's no natural mechanism to determine, such
as different ifIndex values.
> 
> 
> 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
> > 
> 
> _______________________________________________
> Adslmib mailing list
> Adslmib@ietf.org
> https://www.ietf.org/mailman/listinfo/adslmib

_______________________________________________
Adslmib mailing list
Adslmib@ietf.org
https://www.ietf.org/mailman/listinfo/adslmib