
From Markus.Freudenberger@t-systems.com  Wed Apr 22 00:48:04 2009
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 3C45E28C161 for <adslmib@core3.amsl.com>; Wed, 22 Apr 2009 00:48:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.834
X-Spam-Level: 
X-Spam-Status: No, score=-0.834 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, 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 IboyQ7p3DnDg for <adslmib@core3.amsl.com>; Wed, 22 Apr 2009 00:48:01 -0700 (PDT)
Received: from tcmail33.telekom.de (tcmail33.telekom.de [194.25.30.7]) by core3.amsl.com (Postfix) with ESMTP id 046D228C0D9 for <adslmib@ietf.org>; Wed, 22 Apr 2009 00:48:00 -0700 (PDT)
From: <Markus.Freudenberger@t-systems.com>
Received: from s4de8psaans.blf.telekom.de (HELO s4de8psaans.mitte.t-com.de) ([10.151.180.168]) by tcmail31.telekom.de with ESMTP; 22 Apr 2009 09:49:15 +0200
Received: from S4DE8PSAANK.mitte.t-com.de ([10.151.229.10]) by s4de8psaans.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 22 Apr 2009 09:49:15 +0200
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9C31E.D579F28D"
Date: Wed, 22 Apr 2009 09:49:15 +0200
Message-ID: <1B6169C658325341A3B8066E23919E1C015EB481@S4DE8PSAANK.mitte.t-com.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Influence of BBF TR-165 on the draft-ietf-adslmib-vdsl2
Thread-Index: AcnDHv1Hpt6iPMQbS5GY4c9Yf96iNw==
To: <adslmib@ietf.org>
X-OriginalArrivalTime: 22 Apr 2009 07:49:15.0658 (UTC) FILETIME=[D595F6A0:01C9C31E]
Subject: [Adslmib] Influence of BBF TR-165 on the draft-ietf-adslmib-vdsl2
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: Wed, 22 Apr 2009 07:48:04 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9C31E.D579F28D
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

All,

The TR-165 "Vector of Profiles (VoP)" was recently published by the
Broadband Forum (BBF). It defines an optimized object model for
configuring DSL lines.
http://www.broadband-forum.org/technical/download/TR-165.pdf

It states in chapter 1.1:
...
The Vector of Profiles specified in this Technical Report obsoletes the
object model for
DSL line configuration defined in the Broadband Forum's TR-129. Legacy
systems may
still use that object model for configuration management. All other
object models of TR-
129 remain valid.
...

As TR-129 is is used as a reference in the draft-ietf-adslmib-vdsl2-06,
the influence of TR-165 has to be considered by the group and a decision
has to be made asap how to further proceed.
A stated in chapter 1.1 of TR-165, it obsoletes the object model for DSL
line configuration in TR-129 and this influences directy the
Configuration Template and Profile part of the MIB Draft.

I think of the following options for the working group to proceed:

1) Finish the work on the actual draft and define a new "VoP MIB" in the
next step. Once, the "VoP MIB" is ready, the Configuration Template and
Profile part in the existing MIB is marked as obsolete with reference to
the new "VoP MIB".

2) Finish the work on the actual draft and define a new "VoP MIB" in the
next step as an altenative MIB module for DSL line configuration and
leave the choice, which MIB to use to the users.

3) Define the object structure based on TR-165 and put it into the
existing MIB Draft before publication as a mandatory part and mark the
Configuration Template and Profile part as optional.

4) Leave everything as it is.

I prefer option 1).

Any comments?

Best Regards
Markus Freudenberger

T-Systems Enterprise Services GmbH


------_=_NextPart_001_01C9C31E.D579F28D
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7654.12">
<TITLE>Influence of BBF TR-165 on the draft-ietf-adslmib-vdsl2</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">All,</FONT></SPAN>
</P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">The TR-165 =
&quot;Vector of Profiles (VoP)&quot; was recently published by the =
Broadband Forum (BBF). It defines an optimized object model for =
configuring DSL lines.</FONT></SPAN></P>

<P><SPAN LANG=3D"de"></SPAN><A =
HREF=3D"http://www.broadband-forum.org/technical/download/TR-165.pdf"><SP=
AN LANG=3D"de"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">http://www.broadband-forum.org/technical/download/TR-165.p=
df</FONT></U></SPAN></A><SPAN LANG=3D"de"></SPAN>
</P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">It states in chapter =
1.1:</FONT></SPAN>

<BR><SPAN LANG=3D"de"><I><FONT SIZE=3D2 =
FACE=3D"Arial">...</FONT></I></SPAN>

<BR><SPAN LANG=3D"de"><I><FONT SIZE=3D2 FACE=3D"Arial">The Vector of =
Profiles specified in this Technical Report obsoletes the object model =
for</FONT></I></SPAN>

<BR><SPAN LANG=3D"de"><I><FONT SIZE=3D2 FACE=3D"Arial">DSL line =
configuration defined in the Broadband Forum&#8217;s TR-129. Legacy =
systems may</FONT></I></SPAN>

<BR><SPAN LANG=3D"de"><I><FONT SIZE=3D2 FACE=3D"Arial">still use that =
object model for configuration management. All other object models of =
TR-</FONT></I></SPAN>

<BR><SPAN LANG=3D"de"><I><FONT SIZE=3D2 FACE=3D"Arial">129 remain =
valid.</FONT></I></SPAN>

<BR><SPAN LANG=3D"de"><I><FONT SIZE=3D2 =
FACE=3D"Arial">...</FONT></I></SPAN>
</P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">As TR-129 is is used =
as a reference in the draft-ietf-adslmib-vdsl2-06, the influence of =
TR-165 has to be considered by the group and a decision has to be made =
asap how to further proceed.</FONT></SPAN></P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">A stated in chapter =
1.1 of TR-165, it obsoletes the object model for DSL line configuration =
in TR-129 and this influences directy the Configuration Template and =
Profile part of the MIB Draft.</FONT></SPAN></P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">I think of the =
following options for the working group to proceed:</FONT></SPAN>
</P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">1) Finish the work on =
the actual draft and define a new &quot;VoP MIB&quot; in the next step. =
Once, the &quot;VoP MIB&quot; is ready, the Configuration Template and =
Profile part in the existing MIB is marked as obsolete with reference to =
the new &quot;VoP MIB&quot;.</FONT></SPAN></P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">2) Finish the work on =
the actual draft and define a new &quot;VoP MIB&quot; in the next step =
as an altenative MIB module for DSL line configuration and leave the =
choice, which MIB to use to the users.</FONT></SPAN></P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">3) Define the object =
structure based on TR-165 and put it into the existing MIB Draft before =
publication as a mandatory part and mark the Configuration Template and =
Profile part as optional.</FONT></SPAN></P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">4) Leave everything =
as it is.</FONT></SPAN>
</P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">I prefer option =
1).</FONT></SPAN>
</P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">Any =
comments?</FONT></SPAN>
</P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">Best =
Regards</FONT></SPAN>

<BR><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">Markus =
Freudenberger</FONT></SPAN>
</P>

<P><SPAN LANG=3D"de"><B><FONT SIZE=3D2 FACE=3D"Arial">T-Systems =
Enterprise Services GmbH</FONT></B></SPAN>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C9C31E.D579F28D--

From Menachem.Dodge@ecitele.com  Wed Apr 22 01:27:08 2009
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 8A58A28C43C for <adslmib@core3.amsl.com>; Wed, 22 Apr 2009 01:27:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 ghEGiiyqMJpI for <adslmib@core3.amsl.com>; Wed, 22 Apr 2009 01:27:02 -0700 (PDT)
Received: from eci-iron1.ecitele.com (eci-iron1.ecitele.com [147.234.242.117]) by core3.amsl.com (Postfix) with ESMTP id B18663A6A5C for <adslmib@ietf.org>; Wed, 22 Apr 2009 01:27:01 -0700 (PDT)
Received: from unknown (HELO ILPTAM01.ecitele.com) ([147.234.244.44]) by eci-iron1.ecitele.com with ESMTP; 22 Apr 2009 11:35:10 +0300
Received: from ilptexch01.ecitele.com ([172.31.244.40]) by ILPTAM01.ecitele.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 22 Apr 2009 11:28:17 +0300
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ilptexch01.ecitele.com ([172.31.244.40]) with mapi; Wed, 22 Apr 2009 11:28:17 +0300
From: Menachem Dodge <Menachem.Dodge@ecitele.com>
To: "Markus.Freudenberger@t-systems.com" <Markus.Freudenberger@t-systems.com>,  "adslmib@ietf.org" <adslmib@ietf.org>
Date: Wed, 22 Apr 2009 11:28:14 +0300
Thread-Topic: Influence of BBF TR-165 on the draft-ietf-adslmib-vdsl2
Thread-Index: AcnDHv1Hpt6iPMQbS5GY4c9Yf96iNwAAQPnA
Message-ID: <283DD79798619346BF9B17D7B5035A19EC16C9328C@ILPTMAIL02.ecitele.com>
References: <1B6169C658325341A3B8066E23919E1C015EB481@S4DE8PSAANK.mitte.t-com.de>
In-Reply-To: <1B6169C658325341A3B8066E23919E1C015EB481@S4DE8PSAANK.mitte.t-com.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_283DD79798619346BF9B17D7B5035A19EC16C9328CILPTMAIL02eci_"
MIME-Version: 1.0
X-OriginalArrivalTime: 22 Apr 2009 08:28:17.0938 (UTC) FILETIME=[49B18720:01C9C324]
Subject: Re: [Adslmib] Influence of BBF TR-165 on the draft-ietf-adslmib-vdsl2
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: Wed, 22 Apr 2009 08:27:08 -0000

--_000_283DD79798619346BF9B17D7B5035A19EC16C9328CILPTMAIL02eci_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello Markus,

As you know the current vdsl2 draft was forwarded several months ago for pu=
blication following WG last call and is currently being revised following c=
omments by the MIB Doctors.

I am expecting an updated version to be posted by the editors shortly and t=
hen the document can be forwarded for publication.

Therefore either option #1 or option #2 should be considered.

The Working Group received a Liaison from the DSL Forum on 14th March 2008 =
informing us that work had begun on a new project entitled "Vector of Profi=
les". No further word has been received on that subject from the Broadband =
Forum (DSL Forum).

If there is support for option #1 and option #2 the Working Group would nee=
d to request a Change of Charter in order to take on the new work item.

Best Regards,
Menachem Dodge

From: adslmib-bounces@ietf.org [mailto:adslmib-bounces@ietf.org] On Behalf =
Of Markus.Freudenberger@t-systems.com
Sent: Wednesday, April 22, 2009 10:49 AM
To: adslmib@ietf.org
Subject: [Adslmib] Influence of BBF TR-165 on the draft-ietf-adslmib-vdsl2


All,

The TR-165 "Vector of Profiles (VoP)" was recently published by the Broadba=
nd Forum (BBF). It defines an optimized object model for configuring DSL li=
nes.

http://www.broadband-forum.org/technical/download/TR-165.pdf

It states in chapter 1.1:
...
The Vector of Profiles specified in this Technical Report obsoletes the obj=
ect model for
DSL line configuration defined in the Broadband Forum's TR-129. Legacy syst=
ems may
still use that object model for configuration management. All other object =
models of TR-
129 remain valid.
...

As TR-129 is is used as a reference in the draft-ietf-adslmib-vdsl2-06, the=
 influence of TR-165 has to be considered by the group and a decision has t=
o be made asap how to further proceed.

A stated in chapter 1.1 of TR-165, it obsoletes the object model for DSL li=
ne configuration in TR-129 and this influences directy the Configuration Te=
mplate and Profile part of the MIB Draft.

I think of the following options for the working group to proceed:

1) Finish the work on the actual draft and define a new "VoP MIB" in the ne=
xt step. Once, the "VoP MIB" is ready, the Configuration Template and Profi=
le part in the existing MIB is marked as obsolete with reference to the new=
 "VoP MIB".

2) Finish the work on the actual draft and define a new "VoP MIB" in the ne=
xt step as an altenative MIB module for DSL line configuration and leave th=
e choice, which MIB to use to the users.

3) Define the object structure based on TR-165 and put it into the existing=
 MIB Draft before publication as a mandatory part and mark the Configuratio=
n Template and Profile part as optional.

4) Leave everything as it is.

I prefer option 1).

Any comments?

Best Regards
Markus Freudenberger

T-Systems Enterprise Services GmbH

--_000_283DD79798619346BF9B17D7B5035A19EC16C9328CILPTMAIL02eci_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:D=3D"DAV:" xmln=
s:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2=3D=
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois=3D"http://sc=
hemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://schemas.micro=
soft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3.org/2000/09/=
xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" xmlns:u=
dc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http://www.w3.org=
/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/=
2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" xmlns:sp=3D"=
http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://schemas.micro=
soft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-in=
stance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" xmlns:udc=
xf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p=3D"http:/=
/schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http://schemas.micr=
osoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://schemas.microsoft=
.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.microsoft.com/o=
ffice/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformats.org/package=
/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlformats.org/ma=
rkup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.com/office/200=
4/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/re=
lationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" xm=
lns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types" xml=
ns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messages" x=
mlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" x=
mlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Publis=
hedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:st=3D"&#1;" x=
mlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<title>Influence of BBF TR-165 on the draft-ietf-adslmib-vdsl2</title>
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Hello Markus,<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>As you know the current vdsl2 draft was forwarded several mo=
nths
ago for publication following WG last call and is currently being revised f=
ollowing
comments by the MIB Doctors. <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>I am expecting an updated version to be posted by the editor=
s shortly
and then the document can be forwarded for publication.<o:p></o:p></span></=
p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Therefore either option #1 or option #2 should be considered=
.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>The Working Group received a Liaison from the DSL Forum on 1=
4<sup>th</sup>
March 2008 informing us that work had begun on a new project entitled
&quot;Vector of Profiles&quot;. No further word has been received on that
subject from the Broadband Forum (DSL Forum).<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>If there is support for option #1 and option #2 the Working
Group would need to request a Change of Charter in order to take on the new
work item.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Best Regards,<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Menachem Dodge<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'>

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
adslmib-bounces@ietf.org [mailto:adslmib-bounces@ietf.org] <b>On Behalf Of =
</b>Markus.Freudenberger@t-systems.com<br>
<b>Sent:</b> Wednesday, April 22, 2009 10:49 AM<br>
<b>To:</b> adslmib@ietf.org<br>
<b>Subject:</b> [Adslmib] Influence of BBF TR-165 on the
draft-ietf-adslmib-vdsl2<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p><span lang=3DDE style=3D'font-size:10.0pt;font-family:"Arial","sans-seri=
f"'>All,</span><span
lang=3DDE> </span><o:p></o:p></p>

<p><span lang=3DDE style=3D'font-size:10.0pt;font-family:"Arial","sans-seri=
f"'>The
TR-165 &quot;Vector of Profiles (VoP)&quot; was recently published by the
Broadband Forum (BBF). It defines an optimized object model for configuring=
 DSL
lines.</span><o:p></o:p></p>

<p><a href=3D"http://www.broadband-forum.org/technical/download/TR-165.pdf"=
><span
lang=3DDE style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>http:=
//www.broadband-forum.org/technical/download/TR-165.pdf</span></a>
<o:p></o:p></p>

<p><span lang=3DDE style=3D'font-size:10.0pt;font-family:"Arial","sans-seri=
f"'>It
states in chapter 1.1:</span> <br>
<i><span lang=3DDE style=3D'font-size:10.0pt;font-family:"Arial","sans-seri=
f"'>...</span></i>
<br>
<i><span lang=3DDE style=3D'font-size:10.0pt;font-family:"Arial","sans-seri=
f"'>The
Vector of Profiles specified in this Technical Report obsoletes the object
model for</span></i> <br>
<i><span lang=3DDE style=3D'font-size:10.0pt;font-family:"Arial","sans-seri=
f"'>DSL
line configuration defined in the Broadband Forum&#8217;s TR-129. Legacy
systems may</span></i> <br>
<i><span lang=3DDE style=3D'font-size:10.0pt;font-family:"Arial","sans-seri=
f"'>still
use that object model for configuration management. All other object models=
 of
TR-</span></i> <br>
<i><span lang=3DDE style=3D'font-size:10.0pt;font-family:"Arial","sans-seri=
f"'>129
remain valid.</span></i> <br>
<i><span lang=3DDE style=3D'font-size:10.0pt;font-family:"Arial","sans-seri=
f"'>...</span></i><span
lang=3DDE> </span><o:p></o:p></p>

<p><span lang=3DDE style=3D'font-size:10.0pt;font-family:"Arial","sans-seri=
f"'>As
TR-129 is is used as a reference in the draft-ietf-adslmib-vdsl2-06, the
influence of TR-165 has to be considered by the group and a decision has to=
 be
made asap how to further proceed.</span><o:p></o:p></p>

<p><span lang=3DDE style=3D'font-size:10.0pt;font-family:"Arial","sans-seri=
f"'>A
stated in chapter 1.1 of TR-165, it obsoletes the object model for DSL line
configuration in TR-129 and this influences directy the Configuration Templ=
ate
and Profile part of the MIB Draft.</span><o:p></o:p></p>

<p><span lang=3DDE style=3D'font-size:10.0pt;font-family:"Arial","sans-seri=
f"'>I
think of the following options for the working group to proceed:</span><spa=
n
lang=3DDE> </span><o:p></o:p></p>

<p><span lang=3DDE style=3D'font-size:10.0pt;font-family:"Arial","sans-seri=
f"'>1)
Finish the work on the actual draft and define a new &quot;VoP MIB&quot; in=
 the
next step. Once, the &quot;VoP MIB&quot; is ready, the Configuration Templa=
te
and Profile part in the existing MIB is marked as obsolete with reference t=
o
the new &quot;VoP MIB&quot;.</span><o:p></o:p></p>

<p><span lang=3DDE style=3D'font-size:10.0pt;font-family:"Arial","sans-seri=
f"'>2)
Finish the work on the actual draft and define a new &quot;VoP MIB&quot; in=
 the
next step as an altenative MIB module for DSL line configuration and leave =
the
choice, which MIB to use to the users.</span><o:p></o:p></p>

<p><span lang=3DDE style=3D'font-size:10.0pt;font-family:"Arial","sans-seri=
f"'>3)
Define the object structure based on TR-165 and put it into the existing MI=
B
Draft before publication as a mandatory part and mark the Configuration
Template and Profile part as optional.</span><o:p></o:p></p>

<p><span lang=3DDE style=3D'font-size:10.0pt;font-family:"Arial","sans-seri=
f"'>4)
Leave everything as it is.</span><span lang=3DDE> </span><o:p></o:p></p>

<p><span lang=3DDE style=3D'font-size:10.0pt;font-family:"Arial","sans-seri=
f"'>I
prefer option 1).</span><span lang=3DDE> </span><o:p></o:p></p>

<p><span lang=3DDE style=3D'font-size:10.0pt;font-family:"Arial","sans-seri=
f"'>Any
comments?</span><span lang=3DDE> </span><o:p></o:p></p>

<p><span lang=3DDE style=3D'font-size:10.0pt;font-family:"Arial","sans-seri=
f"'>Best
Regards</span> <br>
<span lang=3DDE style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'=
>Markus
Freudenberger</span><span lang=3DDE> </span><o:p></o:p></p>

<p><b><span lang=3DDE style=3D'font-size:10.0pt;font-family:"Arial","sans-s=
erif"'>T-Systems
Enterprise Services GmbH</span></b><span lang=3DDE> </span><o:p></o:p></p>

</div>

</body>

</html>

--_000_283DD79798619346BF9B17D7B5035A19EC16C9328CILPTMAIL02eci_--

From scott.baillie@nec.com.au  Wed Apr 22 00:56:47 2009
Return-Path: <scott.baillie@nec.com.au>
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 A157328C43A for <adslmib@core3.amsl.com>; Wed, 22 Apr 2009 00:56:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.647
X-Spam-Level: 
X-Spam-Status: No, score=-1.647 tagged_above=-999 required=5 tests=[AWL=0.249,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
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 49wqV+GyQIsB for <adslmib@core3.amsl.com>; Wed, 22 Apr 2009 00:56:46 -0700 (PDT)
Received: from smtp.dc.nec.com.au (smtp.dc.nec.com.au [147.76.15.3]) by core3.amsl.com (Postfix) with ESMTP id 489D428C439 for <adslmib@ietf.org>; Wed, 22 Apr 2009 00:56:46 -0700 (PDT)
Received: from smtp1.nec.com.au (clientnat.dc.nec.com.au [147.76.0.42]) by smtp.dc.nec.com.au (Postfix) with ESMTP id B02F6A26AF for <adslmib@ietf.org>; Wed, 22 Apr 2009 17:57:44 +1000 (EST)
Received: from smtp3.NECAU.NEC.COM.AU (smtp2.nec.com.au [172.31.8.19]) by smtp1.nec.com.au (Postfix) with ESMTP id 01DC67FCAD for <adslmib@ietf.org>; Wed, 22 Apr 2009 17:58:02 +1000 (EST)
Received: from warp.ssd.neca.nec.com.au ([147.76.48.65]) by smtp3.NECAU.NEC.COM.AU with InterScan Messaging Security Suite; Wed, 22 Apr 2009 17:58:01 +1000
Received: from spot.ssd.neca.nec.com.au (spot.ssd.neca.nec.com.au [147.76.48.150]) by warp.ssd.neca.nec.com.au (8.13.8+Sun/8.13.8) with ESMTP id n3M7w1Gm013048; Wed, 22 Apr 2009 17:58:01 +1000 (EST)
From: Scott Baillie <scott.baillie@nec.com.au>
To: Markus.Freudenberger@t-systems.com
In-Reply-To: <1B6169C658325341A3B8066E23919E1C015EB481@S4DE8PSAANK.mitte.t-com.de>
References: <1B6169C658325341A3B8066E23919E1C015EB481@S4DE8PSAANK.mitte.t-com.de>
Content-Type: text/plain; charset=utf-8
Organization: NEC Australia
Date: Wed, 22 Apr 2009 17:56:25 +1000
Message-Id: <1240386985.28785.96.camel@spot.ssd.neca.nec.com.au>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.3 (2.6.3-2.fc5) 
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Thu, 23 Apr 2009 00:19:36 -0700
Cc: adslmib@ietf.org
Subject: Re: [Adslmib] Influence of BBF TR-165 on the	draft-ietf-adslmib-vdsl2
X-BeenThere: adslmib@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: scott.baillie@nec.com.au
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: Wed, 22 Apr 2009 07:56:47 -0000

Hi Markus,

I only had a quick look at the document TR-165 so I
would need to spend some more before I can say that
I understand the model being proposed.

What we can say though is that the current VDSL2 draft
MIB will be published pretty much "as is" with the exception
that we are adding in a number of modifications that have
been proposed by the MIB doctors review team.

We can discuss the management model defined in TR-165 after
the current draft goes RFC.

Regards,

Scott.

On Wed, 2009-04-22 at 09:49 +0200, Markus.Freudenberger@t-systems.com
wrote:
> All,
> 
> The TR-165 "Vector of Profiles (VoP)" was recently published by the
> Broadband Forum (BBF). It defines an optimized object model for
> configuring DSL lines.
> 
> http://www.broadband-forum.org/technical/download/TR-165.pdf
> 
> It states in chapter 1.1: 
> ... 
> The Vector of Profiles specified in this Technical Report obsoletes
> the object model for 
> DSL line configuration defined in the Broadband Forum’s TR-129. Legacy
> systems may 
> still use that object model for configuration management. All other
> object models of TR- 
> 129 remain valid. 
> ...
> 
> As TR-129 is is used as a reference in the
> draft-ietf-adslmib-vdsl2-06, the influence of TR-165 has to be
> considered by the group and a decision has to be made asap how to
> further proceed.
> 
> A stated in chapter 1.1 of TR-165, it obsoletes the object model for
> DSL line configuration in TR-129 and this influences directy the
> Configuration Template and Profile part of the MIB Draft.
> 
> I think of the following options for the working group to proceed:
> 
> 1) Finish the work on the actual draft and define a new "VoP MIB" in
> the next step. Once, the "VoP MIB" is ready, the Configuration
> Template and Profile part in the existing MIB is marked as obsolete
> with reference to the new "VoP MIB".
> 
> 2) Finish the work on the actual draft and define a new "VoP MIB" in
> the next step as an altenative MIB module for DSL line configuration
> and leave the choice, which MIB to use to the users.
> 
> 3) Define the object structure based on TR-165 and put it into the
> existing MIB Draft before publication as a mandatory part and mark the
> Configuration Template and Profile part as optional.
> 
> 4) Leave everything as it is.
> 
> I prefer option 1).
> 
> Any comments?
> 
> Best Regards 
> Markus Freudenberger
> 
> T-Systems Enterprise Services GmbH
> 
> _______________________________________________
> Adslmib mailing list
> Adslmib@ietf.org
> https://www.ietf.org/mailman/listinfo/adslmib


From Markus.Freudenberger@t-systems.com  Thu Apr 23 08:29:13 2009
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 7D6FF3A6D09 for <adslmib@core3.amsl.com>; Thu, 23 Apr 2009 08:29:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.042
X-Spam-Level: 
X-Spam-Status: No, score=-2.042 tagged_above=-999 required=5 tests=[AWL=1.208,  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 SpiYTHGrc306 for <adslmib@core3.amsl.com>; Thu, 23 Apr 2009 08:29:12 -0700 (PDT)
Received: from tcmail33.telekom.de (tcmail33.telekom.de [194.25.30.7]) by core3.amsl.com (Postfix) with ESMTP id F311B3A6ADF for <adslmib@ietf.org>; Thu, 23 Apr 2009 08:29:11 -0700 (PDT)
From: <Markus.Freudenberger@t-systems.com>
Received: from s4de8psaans.blf.telekom.de (HELO s4de8psaans.mitte.t-com.de) ([10.151.180.168]) by tcmail31.telekom.de with ESMTP; 23 Apr 2009 17:30:18 +0200
Received: from S4DE8PSAANK.mitte.t-com.de ([10.151.229.10]) by s4de8psaans.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 23 Apr 2009 17:30:18 +0200
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: Thu, 23 Apr 2009 17:30:18 +0200
Message-ID: <1B6169C658325341A3B8066E23919E1C015EB491@S4DE8PSAANK.mitte.t-com.de>
In-Reply-To: <1240386985.28785.96.camel@spot.ssd.neca.nec.com.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Adslmib] Influence of BBF TR-165 on the draft-ietf-adslmib-vdsl2
Thread-Index: AcnD5A0VLtF27jXLRfWlb/pOrcp84AAQJ8ZA
References: <1B6169C658325341A3B8066E23919E1C015EB481@S4DE8PSAANK.mitte.t-com.de> <1240386985.28785.96.camel@spot.ssd.neca.nec.com.au>
To: <scott.baillie@nec.com.au>
X-OriginalArrivalTime: 23 Apr 2009 15:30:18.0605 (UTC) FILETIME=[686671D0:01C9C428]
Cc: adslmib@ietf.org
Subject: Re: [Adslmib] Influence of BBF TR-165 on the draft-ietf-adslmib-vdsl2
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: Thu, 23 Apr 2009 15:29:13 -0000

Hello Scott,

I can help you if you have specific questions regarding TR-165 as I was =
one of the contributors to the document at the Broadband Forum.
I would appreciate if the working group can decide to spend the effort =
in defining the MIB based for TR-165.

I am available to help, if needed.

By the way: When do you expect publication of the current VDSL2 draft =
MIB?

Regards
Markus

-----Urspr=FCngliche Nachricht-----
Von: adslmib-bounces@ietf.org [mailto:adslmib-bounces@ietf.org] Im =
Auftrag von Scott Baillie
Gesendet: Mittwoch, 22. April 2009 09:56
An: Freudenberger, Markus
Cc: adslmib@ietf.org
Betreff: Re: [Adslmib] Influence of BBF TR-165 onthe =
draft-ietf-adslmib-vdsl2

Hi Markus,

I only had a quick look at the document TR-165 so I would need to spend =
some more before I can say that I understand the model being proposed.

What we can say though is that the current VDSL2 draft MIB will be =
published pretty much "as is" with the exception that we are adding in a =
number of modifications that have been proposed by the MIB doctors =
review team.

We can discuss the management model defined in TR-165 after the current =
draft goes RFC.

Regards,

Scott.

On Wed, 2009-04-22 at 09:49 +0200, Markus.Freudenberger@t-systems.com
wrote:
> All,
>=20
> The TR-165 "Vector of Profiles (VoP)" was recently published by the=20
> Broadband Forum (BBF). It defines an optimized object model for=20
> configuring DSL lines.
>=20
> http://www.broadband-forum.org/technical/download/TR-165.pdf
>=20
> It states in chapter 1.1:=20
> ...=20
> The Vector of Profiles specified in this Technical Report obsoletes=20
> the object model for DSL line configuration defined in the Broadband=20
> Forum's TR-129. Legacy systems may still use that object model for=20
> configuration management. All other object models of TR-
> 129 remain valid.=20
> ...
>=20
> As TR-129 is is used as a reference in the=20
> draft-ietf-adslmib-vdsl2-06, the influence of TR-165 has to be=20
> considered by the group and a decision has to be made asap how to=20
> further proceed.
>=20
> A stated in chapter 1.1 of TR-165, it obsoletes the object model for=20
> DSL line configuration in TR-129 and this influences directy the=20
> Configuration Template and Profile part of the MIB Draft.
>=20
> I think of the following options for the working group to proceed:
>=20
> 1) Finish the work on the actual draft and define a new "VoP MIB" in=20
> the next step. Once, the "VoP MIB" is ready, the Configuration=20
> Template and Profile part in the existing MIB is marked as obsolete=20
> with reference to the new "VoP MIB".
>=20
> 2) Finish the work on the actual draft and define a new "VoP MIB" in=20
> the next step as an altenative MIB module for DSL line configuration=20
> and leave the choice, which MIB to use to the users.
>=20
> 3) Define the object structure based on TR-165 and put it into the=20
> existing MIB Draft before publication as a mandatory part and mark the =

> Configuration Template and Profile part as optional.
>=20
> 4) Leave everything as it is.
>=20
> I prefer option 1).
>=20
> Any comments?
>=20
> Best Regards
> Markus Freudenberger
>=20
> T-Systems Enterprise Services GmbH
>=20
> _______________________________________________
> 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

From scott.baillie@nec.com.au  Thu Apr 23 23:39:10 2009
Return-Path: <scott.baillie@nec.com.au>
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 25F6A3A71F0 for <adslmib@core3.amsl.com>; Thu, 23 Apr 2009 23:39:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.729
X-Spam-Level: 
X-Spam-Status: No, score=-1.729 tagged_above=-999 required=5 tests=[AWL=0.166,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
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 y-wA+tRDtehk for <adslmib@core3.amsl.com>; Thu, 23 Apr 2009 23:39:09 -0700 (PDT)
Received: from smtp.dc.nec.com.au (smtp.dc.nec.com.au [147.76.15.3]) by core3.amsl.com (Postfix) with ESMTP id B53963A72C0 for <adslmib@ietf.org>; Thu, 23 Apr 2009 23:39:08 -0700 (PDT)
Received: from smtp1.nec.com.au (clientnat.dc.nec.com.au [147.76.0.42]) by smtp.dc.nec.com.au (Postfix) with ESMTP id D9C17A26F5 for <adslmib@ietf.org>; Fri, 24 Apr 2009 16:40:07 +1000 (EST)
Received: from smtp3.NECAU.NEC.COM.AU (smtp2.nec.com.au [172.31.8.19]) by smtp1.nec.com.au (Postfix) with ESMTP id 3F6517FD01 for <adslmib@ietf.org>; Fri, 24 Apr 2009 16:40:25 +1000 (EST)
Received: from warp.ssd.neca.nec.com.au ([147.76.48.65]) by smtp3.NECAU.NEC.COM.AU with InterScan Messaging Security Suite; Fri, 24 Apr 2009 16:40:24 +1000
Received: from spot.ssd.neca.nec.com.au (spot.ssd.neca.nec.com.au [147.76.48.150]) by warp.ssd.neca.nec.com.au (8.13.8+Sun/8.13.8) with ESMTP id n3O6eOHM006821; Fri, 24 Apr 2009 16:40:24 +1000 (EST)
From: Scott Baillie <scott.baillie@nec.com.au>
To: Markus.Freudenberger@t-systems.com
In-Reply-To: <1B6169C658325341A3B8066E23919E1C015EB491@S4DE8PSAANK.mitte.t-com.de>
References: <1B6169C658325341A3B8066E23919E1C015EB481@S4DE8PSAANK.mitte.t-com.de> <1240386985.28785.96.camel@spot.ssd.neca.nec.com.au> <1B6169C658325341A3B8066E23919E1C015EB491@S4DE8PSAANK.mitte.t-com.de>
Content-Type: text/plain; charset=utf-8
Organization: NEC Australia
Date: Fri, 24 Apr 2009 16:38:40 +1000
Message-Id: <1240555120.28785.123.camel@spot.ssd.neca.nec.com.au>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.3 (2.6.3-2.fc5) 
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Sun, 26 Apr 2009 00:22:59 -0700
Cc: adslmib@ietf.org
Subject: Re: [Adslmib] Influence of BBF TR-165 on the	draft-ietf-adslmib-vdsl2
X-BeenThere: adslmib@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: scott.baillie@nec.com.au
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: Fri, 24 Apr 2009 06:39:10 -0000

Hi Markus,

Thanks,
I appreciate your offer and we will take you up on that !!

As for when the RFC will be published, as soon as possible
but check with Menachem for details.

Regards,

Scott.

On Thu, 2009-04-23 at 17:30 +0200, Markus.Freudenberger@t-systems.com
wrote:
> Hello Scott,
> 
> I can help you if you have specific questions regarding TR-165 as I was one of the contributors to the document at the Broadband Forum.
> I would appreciate if the working group can decide to spend the effort in defining the MIB based for TR-165.
> 
> I am available to help, if needed.
> 
> By the way: When do you expect publication of the current VDSL2 draft MIB?
> 
> Regards
> Markus
> 
> -----Ursprüngliche Nachricht-----
> Von: adslmib-bounces@ietf.org [mailto:adslmib-bounces@ietf.org] Im Auftrag von Scott Baillie
> Gesendet: Mittwoch, 22. April 2009 09:56
> An: Freudenberger, Markus
> Cc: adslmib@ietf.org
> Betreff: Re: [Adslmib] Influence of BBF TR-165 onthe draft-ietf-adslmib-vdsl2
> 
> Hi Markus,
> 
> I only had a quick look at the document TR-165 so I would need to spend some more before I can say that I understand the model being proposed.
> 
> What we can say though is that the current VDSL2 draft MIB will be published pretty much "as is" with the exception that we are adding in a number of modifications that have been proposed by the MIB doctors review team.
> 
> We can discuss the management model defined in TR-165 after the current draft goes RFC.
> 
> Regards,
> 
> Scott.
> 
> On Wed, 2009-04-22 at 09:49 +0200, Markus.Freudenberger@t-systems.com
> wrote:
> > All,
> > 
> > The TR-165 "Vector of Profiles (VoP)" was recently published by the 
> > Broadband Forum (BBF). It defines an optimized object model for 
> > configuring DSL lines.
> > 
> > http://www.broadband-forum.org/technical/download/TR-165.pdf
> > 
> > It states in chapter 1.1: 
> > ... 
> > The Vector of Profiles specified in this Technical Report obsoletes 
> > the object model for DSL line configuration defined in the Broadband 
> > Forum's TR-129. Legacy systems may still use that object model for 
> > configuration management. All other object models of TR-
> > 129 remain valid. 
> > ...
> > 
> > As TR-129 is is used as a reference in the 
> > draft-ietf-adslmib-vdsl2-06, the influence of TR-165 has to be 
> > considered by the group and a decision has to be made asap how to 
> > further proceed.
> > 
> > A stated in chapter 1.1 of TR-165, it obsoletes the object model for 
> > DSL line configuration in TR-129 and this influences directy the 
> > Configuration Template and Profile part of the MIB Draft.
> > 
> > I think of the following options for the working group to proceed:
> > 
> > 1) Finish the work on the actual draft and define a new "VoP MIB" in 
> > the next step. Once, the "VoP MIB" is ready, the Configuration 
> > Template and Profile part in the existing MIB is marked as obsolete 
> > with reference to the new "VoP MIB".
> > 
> > 2) Finish the work on the actual draft and define a new "VoP MIB" in 
> > the next step as an altenative MIB module for DSL line configuration 
> > and leave the choice, which MIB to use to the users.
> > 
> > 3) Define the object structure based on TR-165 and put it into the 
> > existing MIB Draft before publication as a mandatory part and mark the 
> > Configuration Template and Profile part as optional.
> > 
> > 4) Leave everything as it is.
> > 
> > I prefer option 1).
> > 
> > Any comments?
> > 
> > Best Regards
> > Markus Freudenberger
> > 
> > T-Systems Enterprise Services GmbH
> > 
> > _______________________________________________
> > 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
> _______________________________________________
> Adslmib mailing list
> Adslmib@ietf.org
> https://www.ietf.org/mailman/listinfo/adslmib
> 


From Menachem.Dodge@ecitele.com  Mon Apr 27 06:13:38 2009
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 2FB723A6F6D for <adslmib@core3.amsl.com>; Mon, 27 Apr 2009 06:13:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 es4Cj3VCb-jo for <adslmib@core3.amsl.com>; Mon, 27 Apr 2009 06:13:37 -0700 (PDT)
Received: from ilptiron01.ecitele.com (ilptiron01.ecitele.com [147.234.242.161]) by core3.amsl.com (Postfix) with ESMTP id 3A7B33A6A4E for <adslmib@ietf.org>; Mon, 27 Apr 2009 06:13:36 -0700 (PDT)
Received: from unknown (HELO ILPTAM01.ecitele.com) ([147.234.244.44]) by ilptiron01.ecitele.com with ESMTP; 27 Apr 2009 16:12:42 +0300
Received: from ILPTEXCH02.ecitele.com ([147.234.245.181]) by ILPTAM01.ecitele.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 27 Apr 2009 16:14:56 +0300
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Mon, 27 Apr 2009 16:14:55 +0300
From: Menachem Dodge <Menachem.Dodge@ecitele.com>
To: "scott.baillie@nec.com.au" <scott.baillie@nec.com.au>, "Markus.Freudenberger@t-systems.com" <Markus.Freudenberger@t-systems.com>
Date: Mon, 27 Apr 2009 16:14:54 +0300
Thread-Topic: [Adslmib] Influence of BBF TR-165 on	the draft-ietf-adslmib-vdsl2
Thread-Index: AcnGQAZy7FgcLFFfR2CKtyD/KUOLcwA+WKtA
Message-ID: <283DD79798619346BF9B17D7B5035A19EC16D37F75@ILPTMAIL02.ecitele.com>
References: <1B6169C658325341A3B8066E23919E1C015EB481@S4DE8PSAANK.mitte.t-com.de> <1240386985.28785.96.camel@spot.ssd.neca.nec.com.au> <1B6169C658325341A3B8066E23919E1C015EB491@S4DE8PSAANK.mitte.t-com.de> <1240555120.28785.123.camel@spot.ssd.neca.nec.com.au>
In-Reply-To: <1240555120.28785.123.camel@spot.ssd.neca.nec.com.au>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginalArrivalTime: 27 Apr 2009 13:14:56.0200 (UTC) FILETIME=[28B8CC80:01C9C73A]
Cc: "adslmib@ietf.org" <adslmib@ietf.org>
Subject: Re: [Adslmib] Influence of BBF TR-165 on	the	draft-ietf-adslmib-vdsl2
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, 27 Apr 2009 13:13:38 -0000

SGkgTWFya3VzLCBTY290dCwNCg0KVGhlIGRyYWZ0IHdhcyBmb3J3YXJkZWQgZm9yIHB1YmxpY2F0
aW9uIGJ1dCBmb2xsb3dpbmcgTUlCIERvY3RvciByZXZpZXcsIGFuIHVwZGF0ZWQgZHJhZnQgaXMg
cmVxdWlyZWQuDQpBcyBzb29uIGFzIHRoZSBkcmFmdCBpcyBhdmFpbGFibGUgYW5kIGFzc3VtaW5n
IHRoYXQgYWxsIHRoZSBpc3N1ZXMgcmFpc2VkIGhhdmUgYmVlbiBhZGRyZXNzZWQsIHRoZSBwdWJs
aWNhdGlvbiANCnByb2Nlc3Mgd2lsbCB0aGVuIGNvbnRpbnVlLg0KDQpCZXN0IFJlZ2FyZHMsDQpN
ZW5hY2hlbQ0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBhZHNsbWliLWJv
dW5jZXNAaWV0Zi5vcmcgW21haWx0bzphZHNsbWliLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFs
ZiBPZiBTY290dCBCYWlsbGllDQpTZW50OiBGcmlkYXksIEFwcmlsIDI0LCAyMDA5IDk6MzkgQU0N
ClRvOiBNYXJrdXMuRnJldWRlbmJlcmdlckB0LXN5c3RlbXMuY29tDQpDYzogYWRzbG1pYkBpZXRm
Lm9yZw0KU3ViamVjdDogUmU6IFtBZHNsbWliXSBJbmZsdWVuY2Ugb2YgQkJGIFRSLTE2NSBvbiB0
aGUgZHJhZnQtaWV0Zi1hZHNsbWliLXZkc2wyDQoNCkhpIE1hcmt1cywNCg0KVGhhbmtzLA0KSSBh
cHByZWNpYXRlIHlvdXIgb2ZmZXIgYW5kIHdlIHdpbGwgdGFrZSB5b3UgdXAgb24gdGhhdCAhIQ0K
DQpBcyBmb3Igd2hlbiB0aGUgUkZDIHdpbGwgYmUgcHVibGlzaGVkLCBhcyBzb29uIGFzIHBvc3Np
YmxlDQpidXQgY2hlY2sgd2l0aCBNZW5hY2hlbSBmb3IgZGV0YWlscy4NCg0KUmVnYXJkcywNCg0K
U2NvdHQuDQoNCk9uIFRodSwgMjAwOS0wNC0yMyBhdCAxNzozMCArMDIwMCwgTWFya3VzLkZyZXVk
ZW5iZXJnZXJAdC1zeXN0ZW1zLmNvbQ0Kd3JvdGU6DQo+IEhlbGxvIFNjb3R0LA0KPiANCj4gSSBj
YW4gaGVscCB5b3UgaWYgeW91IGhhdmUgc3BlY2lmaWMgcXVlc3Rpb25zIHJlZ2FyZGluZyBUUi0x
NjUgYXMgSSB3YXMgb25lIG9mIHRoZSBjb250cmlidXRvcnMgdG8gdGhlIGRvY3VtZW50IGF0IHRo
ZSBCcm9hZGJhbmQgRm9ydW0uDQo+IEkgd291bGQgYXBwcmVjaWF0ZSBpZiB0aGUgd29ya2luZyBn
cm91cCBjYW4gZGVjaWRlIHRvIHNwZW5kIHRoZSBlZmZvcnQgaW4gZGVmaW5pbmcgdGhlIE1JQiBi
YXNlZCBmb3IgVFItMTY1Lg0KPiANCj4gSSBhbSBhdmFpbGFibGUgdG8gaGVscCwgaWYgbmVlZGVk
Lg0KPiANCj4gQnkgdGhlIHdheTogV2hlbiBkbyB5b3UgZXhwZWN0IHB1YmxpY2F0aW9uIG9mIHRo
ZSBjdXJyZW50IFZEU0wyIGRyYWZ0IE1JQj8NCj4gDQo+IFJlZ2FyZHMNCj4gTWFya3VzDQo+IA0K
PiAtLS0tLVVyc3Byw7xuZ2xpY2hlIE5hY2hyaWNodC0tLS0tDQo+IFZvbjogYWRzbG1pYi1ib3Vu
Y2VzQGlldGYub3JnIFttYWlsdG86YWRzbG1pYi1ib3VuY2VzQGlldGYub3JnXSBJbSBBdWZ0cmFn
IHZvbiBTY290dCBCYWlsbGllDQo+IEdlc2VuZGV0OiBNaXR0d29jaCwgMjIuIEFwcmlsIDIwMDkg
MDk6NTYNCj4gQW46IEZyZXVkZW5iZXJnZXIsIE1hcmt1cw0KPiBDYzogYWRzbG1pYkBpZXRmLm9y
Zw0KPiBCZXRyZWZmOiBSZTogW0Fkc2xtaWJdIEluZmx1ZW5jZSBvZiBCQkYgVFItMTY1IG9udGhl
IGRyYWZ0LWlldGYtYWRzbG1pYi12ZHNsMg0KPiANCj4gSGkgTWFya3VzLA0KPiANCj4gSSBvbmx5
IGhhZCBhIHF1aWNrIGxvb2sgYXQgdGhlIGRvY3VtZW50IFRSLTE2NSBzbyBJIHdvdWxkIG5lZWQg
dG8gc3BlbmQgc29tZSBtb3JlIGJlZm9yZSBJIGNhbiBzYXkgdGhhdCBJIHVuZGVyc3RhbmQgdGhl
IG1vZGVsIGJlaW5nIHByb3Bvc2VkLg0KPiANCj4gV2hhdCB3ZSBjYW4gc2F5IHRob3VnaCBpcyB0
aGF0IHRoZSBjdXJyZW50IFZEU0wyIGRyYWZ0IE1JQiB3aWxsIGJlIHB1Ymxpc2hlZCBwcmV0dHkg
bXVjaCAiYXMgaXMiIHdpdGggdGhlIGV4Y2VwdGlvbiB0aGF0IHdlIGFyZSBhZGRpbmcgaW4gYSBu
dW1iZXIgb2YgbW9kaWZpY2F0aW9ucyB0aGF0IGhhdmUgYmVlbiBwcm9wb3NlZCBieSB0aGUgTUlC
IGRvY3RvcnMgcmV2aWV3IHRlYW0uDQo+IA0KPiBXZSBjYW4gZGlzY3VzcyB0aGUgbWFuYWdlbWVu
dCBtb2RlbCBkZWZpbmVkIGluIFRSLTE2NSBhZnRlciB0aGUgY3VycmVudCBkcmFmdCBnb2VzIFJG
Qy4NCj4gDQo+IFJlZ2FyZHMsDQo+IA0KPiBTY290dC4NCj4gDQo+IE9uIFdlZCwgMjAwOS0wNC0y
MiBhdCAwOTo0OSArMDIwMCwgTWFya3VzLkZyZXVkZW5iZXJnZXJAdC1zeXN0ZW1zLmNvbQ0KPiB3
cm90ZToNCj4gPiBBbGwsDQo+ID4gDQo+ID4gVGhlIFRSLTE2NSAiVmVjdG9yIG9mIFByb2ZpbGVz
IChWb1ApIiB3YXMgcmVjZW50bHkgcHVibGlzaGVkIGJ5IHRoZSANCj4gPiBCcm9hZGJhbmQgRm9y
dW0gKEJCRikuIEl0IGRlZmluZXMgYW4gb3B0aW1pemVkIG9iamVjdCBtb2RlbCBmb3IgDQo+ID4g
Y29uZmlndXJpbmcgRFNMIGxpbmVzLg0KPiA+IA0KPiA+IGh0dHA6Ly93d3cuYnJvYWRiYW5kLWZv
cnVtLm9yZy90ZWNobmljYWwvZG93bmxvYWQvVFItMTY1LnBkZg0KPiA+IA0KPiA+IEl0IHN0YXRl
cyBpbiBjaGFwdGVyIDEuMTogDQo+ID4gLi4uIA0KPiA+IFRoZSBWZWN0b3Igb2YgUHJvZmlsZXMg
c3BlY2lmaWVkIGluIHRoaXMgVGVjaG5pY2FsIFJlcG9ydCBvYnNvbGV0ZXMgDQo+ID4gdGhlIG9i
amVjdCBtb2RlbCBmb3IgRFNMIGxpbmUgY29uZmlndXJhdGlvbiBkZWZpbmVkIGluIHRoZSBCcm9h
ZGJhbmQgDQo+ID4gRm9ydW0ncyBUUi0xMjkuIExlZ2FjeSBzeXN0ZW1zIG1heSBzdGlsbCB1c2Ug
dGhhdCBvYmplY3QgbW9kZWwgZm9yIA0KPiA+IGNvbmZpZ3VyYXRpb24gbWFuYWdlbWVudC4gQWxs
IG90aGVyIG9iamVjdCBtb2RlbHMgb2YgVFItDQo+ID4gMTI5IHJlbWFpbiB2YWxpZC4gDQo+ID4g
Li4uDQo+ID4gDQo+ID4gQXMgVFItMTI5IGlzIGlzIHVzZWQgYXMgYSByZWZlcmVuY2UgaW4gdGhl
IA0KPiA+IGRyYWZ0LWlldGYtYWRzbG1pYi12ZHNsMi0wNiwgdGhlIGluZmx1ZW5jZSBvZiBUUi0x
NjUgaGFzIHRvIGJlIA0KPiA+IGNvbnNpZGVyZWQgYnkgdGhlIGdyb3VwIGFuZCBhIGRlY2lzaW9u
IGhhcyB0byBiZSBtYWRlIGFzYXAgaG93IHRvIA0KPiA+IGZ1cnRoZXIgcHJvY2VlZC4NCj4gPiAN
Cj4gPiBBIHN0YXRlZCBpbiBjaGFwdGVyIDEuMSBvZiBUUi0xNjUsIGl0IG9ic29sZXRlcyB0aGUg
b2JqZWN0IG1vZGVsIGZvciANCj4gPiBEU0wgbGluZSBjb25maWd1cmF0aW9uIGluIFRSLTEyOSBh
bmQgdGhpcyBpbmZsdWVuY2VzIGRpcmVjdHkgdGhlIA0KPiA+IENvbmZpZ3VyYXRpb24gVGVtcGxh
dGUgYW5kIFByb2ZpbGUgcGFydCBvZiB0aGUgTUlCIERyYWZ0Lg0KPiA+IA0KPiA+IEkgdGhpbmsg
b2YgdGhlIGZvbGxvd2luZyBvcHRpb25zIGZvciB0aGUgd29ya2luZyBncm91cCB0byBwcm9jZWVk
Og0KPiA+IA0KPiA+IDEpIEZpbmlzaCB0aGUgd29yayBvbiB0aGUgYWN0dWFsIGRyYWZ0IGFuZCBk
ZWZpbmUgYSBuZXcgIlZvUCBNSUIiIGluIA0KPiA+IHRoZSBuZXh0IHN0ZXAuIE9uY2UsIHRoZSAi
Vm9QIE1JQiIgaXMgcmVhZHksIHRoZSBDb25maWd1cmF0aW9uIA0KPiA+IFRlbXBsYXRlIGFuZCBQ
cm9maWxlIHBhcnQgaW4gdGhlIGV4aXN0aW5nIE1JQiBpcyBtYXJrZWQgYXMgb2Jzb2xldGUgDQo+
ID4gd2l0aCByZWZlcmVuY2UgdG8gdGhlIG5ldyAiVm9QIE1JQiIuDQo+ID4gDQo+ID4gMikgRmlu
aXNoIHRoZSB3b3JrIG9uIHRoZSBhY3R1YWwgZHJhZnQgYW5kIGRlZmluZSBhIG5ldyAiVm9QIE1J
QiIgaW4gDQo+ID4gdGhlIG5leHQgc3RlcCBhcyBhbiBhbHRlbmF0aXZlIE1JQiBtb2R1bGUgZm9y
IERTTCBsaW5lIGNvbmZpZ3VyYXRpb24gDQo+ID4gYW5kIGxlYXZlIHRoZSBjaG9pY2UsIHdoaWNo
IE1JQiB0byB1c2UgdG8gdGhlIHVzZXJzLg0KPiA+IA0KPiA+IDMpIERlZmluZSB0aGUgb2JqZWN0
IHN0cnVjdHVyZSBiYXNlZCBvbiBUUi0xNjUgYW5kIHB1dCBpdCBpbnRvIHRoZSANCj4gPiBleGlz
dGluZyBNSUIgRHJhZnQgYmVmb3JlIHB1YmxpY2F0aW9uIGFzIGEgbWFuZGF0b3J5IHBhcnQgYW5k
IG1hcmsgdGhlIA0KPiA+IENvbmZpZ3VyYXRpb24gVGVtcGxhdGUgYW5kIFByb2ZpbGUgcGFydCBh
cyBvcHRpb25hbC4NCj4gPiANCj4gPiA0KSBMZWF2ZSBldmVyeXRoaW5nIGFzIGl0IGlzLg0KPiA+
IA0KPiA+IEkgcHJlZmVyIG9wdGlvbiAxKS4NCj4gPiANCj4gPiBBbnkgY29tbWVudHM/DQo+ID4g
DQo+ID4gQmVzdCBSZWdhcmRzDQo+ID4gTWFya3VzIEZyZXVkZW5iZXJnZXINCj4gPiANCj4gPiBU
LVN5c3RlbXMgRW50ZXJwcmlzZSBTZXJ2aWNlcyBHbWJIDQo+ID4gDQo+ID4gX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gPiBBZHNsbWliIG1haWxpbmcg
bGlzdA0KPiA+IEFkc2xtaWJAaWV0Zi5vcmcNCj4gPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL2Fkc2xtaWINCj4gDQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fDQo+IEFkc2xtaWIgbWFpbGluZyBsaXN0DQo+IEFkc2xtaWJAaWV0
Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9hZHNsbWliDQo+
IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IEFkc2xt
aWIgbWFpbGluZyBsaXN0DQo+IEFkc2xtaWJAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby9hZHNsbWliDQo+IA0KDQpfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXw0KQWRzbG1pYiBtYWlsaW5nIGxpc3QNCkFkc2xtaWJA
aWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vYWRzbG1pYg0K
