From adslmib-bounces@ietf.org Sun Sep 03 05:50:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GJocZ-000499-Bo; Sun, 03 Sep 2006 05:50:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GJocY-00048u-Ez; Sun, 03 Sep 2006 05:50:30 -0400
Received: from nj300815-ier2.net.avaya.com ([198.152.12.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GJocX-0001Q7-Ex; Sun, 03 Sep 2006 05:50:30 -0400
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by nj300815-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP
	id k839eUTL026143; Sun, 3 Sep 2006 05:40:31 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Subject: RE: [Adslmib] Re: Liaison to DSL Forum
Date: Sun, 3 Sep 2006 12:49:23 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0B274A30@IS0004AVEXU1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Adslmib] Re: Liaison to DSL Forum
Thread-Index: AcbNCclljguzcEKMRo+ReK3tNkGOGgCM+RTQ
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: <Menachem.Dodge@ecitele.com>, <adslmib@ietf.org>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 3d926c18f94eda32f0a6732c7d97b75a
Cc: David Kessens <david.kessens@nokia.com>, hubmib@ietf.org,
	EdwardB@actelis.com, narendranath.nair@wipro.com
X-BeenThere: adslmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ADSLMIB <adslmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/adslmib>,
	<mailto:adslmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:adslmib@ietf.org>
List-Help: <mailto:adslmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/adslmib>,
	<mailto:adslmib-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0842290644=="
Errors-To: adslmib-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0842290644==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6CF3E.3C2D6D31"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6CF3E.3C2D6D31
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Menachem,
=20
I would suggest that you make clear the impact of this charter action on
the current charter and schedules of hubmib, if there is any. For this
purpose I would suggest that you copy hubmib@ietf.org on further mails
on this subject.=20
=20
Please also copy David Kessens. As I am wearing both AD and hubmib chair
hats, it's better to have both ADs looking at this.=20
=20
Dan
=20
=20
=20
=20
=20
=20


  _____ =20

	From: Menachem.Dodge@ecitele.com
[mailto:Menachem.Dodge@ecitele.com]=20
	Sent: Thursday, August 31, 2006 3:08 PM
	To: adslmib@ietf.org
	Cc: EdwardB@actelis.com; narendranath.nair@wipro.com
	Subject: RE: [Adslmib] Re: Liaison to DSL Forum
=09
=09

	It seems that there is agreement for a common MIB that will hold
the common information and will then reference 3 specific MIBs=20
	for the ATM, Ethernet and TDIM specific parameters.=20
=09
	Unless I hear something to the contrary, I will draft a charter
and present it on the mailing list early next week.=20
=09
	Best Regards,=20
	Menachem=20
=09
=09
=09
=09
<narendranath.nair@wipro.com>=20

31/08/2006 14:07=20

To
<EdwardB@actelis.com>, <frank.van_der_putten@alcatel.be>,
<Menachem.Dodge@ecitele.com>=20
cc
adslmib@ietf.org=20
Subject
RE: [Adslmib] Re: Liaison to DSL Forum

=09




	I am also in agreement with having a common MIB and then
specific ones based on the L2 technology type.=20
	 =20
	Regards=20
	Naren=20
	 =20

  _____ =20


	From: Edward Beili [mailto:EdwardB@actelis.com]=20
	Sent: Thursday, August 31, 2006 4:20 PM
	To: frank.van_der_putten@alcatel.be; Menachem.Dodge@ecitele.com
	Cc: adslmib@ietf.org
	Subject: RE: [Adslmib] Re: Liaison to DSL Forum=20
	 =20
	I agree with Frank, there should be a separate MIB for each
G.Bond specification.=20
	 =20
	The ifAvailableStackTable and ifStackTable (with their inverse
counterparts) are of course common for all 3 MIBs.=20
	 =20
	We could create a common MIB for all 3 specifications, providing
G.Bond overview, referencing 3 specific MIBs and may be even providing
some common objects in a MIB, for example LowBandwidth trap etc.=20
	 =20
	Regards,=20
	-E.=20
	-----Original Message-----
	From: frank.van_der_putten@alcatel.be
[mailto:frank.van_der_putten@alcatel.be]
	Sent: Thursday, August 31, 2006 11:35 AM
	To: Menachem.Dodge@ecitele.com
	Cc: adslmib@ietf.org
	Subject: Re: [Adslmib] Re: Liaison to DSL Forum=20
	Menachem,
	Liaison is OK.
	On the bonding MIB: the three bonding standards each handle
different things (cells, packets,bits).
	So I believe the MIBs should be separate as I expect a lot of
the managed objects will be different.
	Regards,
	Frank
=09
=09
	Menachem.Dodge@ecitele.com <mailto:Menachem.Dodge@ecitele.com>
wrote:
=09
=09
	Hello,=20
=09
	       I haven't received any further feedback on the Liaison,
so I will send it to the DSL Forum.=20
=09
	               Regarding xDSL bonding issue, I believe that:=20
=09
	       1.  There is Working Group agreement to base our work on
the three ITU-T specifications: G.998.1 (ATM), G.998.2 (Ethernet) and
G.998.3 (TDIM).=20
=09
	       2. There are differing opinions as to whether there
should be one MIB or 3 separate MIBs to handle the three=20
	cases - ATM, Ethernet, and TDIM.=20
=09
=09
	       I wish to resolve this issue now, so I would appreciate
if everyone would state their opinion (again).=20
=09
	Best Regards,=20
	Menachem=20
=09
=09
=09

=09
Menachem Dodge/ECI Telecom=20

28/08/2006 19:02=20



To
adslmib@ietf.org <mailto:adslmib@ietf.org> =20
cc
 =20
Subject
Liaison to DSL Forum

 =20



  	=20



=09
=09
	Hi,=20
=09
	       I have added an additional paragraph informing the DSL
Forum of our progress on the VDSL2 MIB (as per the charter). Let me know

	if you have any comments, until Wednesday 30th August.=20
=09
=09
=09
=09
=09
	       =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=20
=09
=09
	       Regarding the xDSL Bonding, I have several volunteers for
editors of the document(s) but I need to know if there is anyone=20
	prepared to review the document. Please let me know (privately
if you wish) whether you are willing to review the document. It would be
helpful=20
	to know if there is anyone who will be implementing the MIB as
well.=20
=09
	       Once I have this, the following steps are required:=20
=09
	       1. I will put forward a modified charter for approval by
the Working Group.=20
	       2. Once approved by the Working Group, I will send the
new charter text to the AD, Dan Romascanu, requesting that he brings the

	charter to the IESG for approval.=20
=09
=09
	       =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =

=09
	               Regarding the Vdsl2 draft, I would like to see
some review, comments, feedback ....=20
	              =20
=09
	Best Regards,=20
	Menachem=20
=09

=09
=09
=09
  _____ =20

=09
=09
=09

	 =20
	Subject: Response To Your Liaison on WT-129.=20
	 =20
	Date:  28th August, 2006.=20
	 =20
	 =20
	To:    Gavin Young,=20
	       DSL Forum Technical Committee Chair=20
	       "Gavin Young" <gyoung@dslforum.org>
<mailto:gyoung@dslforum.org> =20
	 =20
	       Peter Adams,=20
	       DSL Forum Operations and Network Management Working Group
Chair=20
	       "Peter Adams" <p.f.adams@btopenworld.com>
<mailto:p.f.adams@btopenworld.com> =20
	 =20
	 =20
	Cc:    IETF statements@ietf.org <mailto:statements@ietf.org> =20
	       IAB@ietf.org <mailto:IAB@ietf.org> =20
	       =20
	       Loa Andersson=20
	       "Loa Andersson" <loa@pi.se> <mailto:loa@pi.se> =20
	 =20
	       Dan Romascanu=20
	       Operations and Management Area Director=20
	       "Romascanu, Dan" <dromasca@avaya.com>
<mailto:dromasca@avaya.com> =20
	 =20
	       Michael Sneed=20
	       IETF ADSL MIB Working Group Co-Chair=20
	       "Michael Sneed" sneedmike@hotmail.com
<mailto:sneedmike@hotmail.com> =20
	       =20
	 =20
	From:  IETF ADSL MIB Working Group=20
	 =20
	Response  contact:   Menachem Dodge=20
	                        IETF ADSL MIB Working Group Co-Chair=20
	                        "Menachem Dodge"
<menachem.dodge@ecitele.com> <mailto:menachem.dodge@ecitele.com> =20
	 =20
	Technical contact:      "Menachem Dodge"
<menachem.dodge@ecitele.com> <mailto:menachem.dodge@ecitele.com> =20
	 =20
	 =20
	PURPOSE: Response=20
	 =20
	Subject: Response To Your Liaison on WT-129.=20
	 =20
	Dear Gavin and Peter,=20
	 =20
	 =20
	      Thank you for your liaison and WT-129 Version 3.0. We
would be very grateful if=20
	you would continue to keep us informed of any changes to this
Working Text document.=20
	 =20
	      As I informed you in February this year, work has begun on
development of a MIB=20
	for DSL (ADSL, ADSL2, ADSL2+ and VDSL2) lines. This work has
progressed and the latest draft=20
	can be found at
http://www.ietf.org/internet-drafts/draft-ietf-adslmib-vdsl2-01.txt
<http://www.ietf.org/internet-drafts/draft-ietf-adslmib-vdsl2-01.txt> .
We would=20
	be most pleased, if you would inform us of any feedback that the
DSL Forum may have on this=20
	document.=20
	 =20
	      We would like to raise the issue of xDSL Bonding, as
defined by the ITU-T documents=20
	 G.998.1, G.998.2 and G.998.3.  The management of xDSL Bonded
lines has currently not been=20
	addressed, by the DSL Forum. The IETF ADSL MIB Working Group
believes that this issue is important=20
	and would be very pleased if the DSL Forum Operations and
Network Management Working Group=20
	would address this issue and provide a management framework for
xDSL Bonding.=20
	 =20
	 =20
	      Yours Sincerely,=20
	 =20
	 =20
	      Menachem Dodge=20
	        IETF ADSL MIB Working Group Co-Chair=20
	 =20
	 =20
	 =20
	     =20

=09
=09
=09
  _____ =20

=09
=09
=09

	 =20
	_______________________________________________=20
	Adslmib mailing list=20
	Adslmib@ietf.org <mailto:Adslmib@ietf.org> =20
	https://www1.ietf.org/mailman/listinfo/adslmib
<https://www1.ietf.org/mailman/listinfo/adslmib> =20
	  _______________________________________________
	Adslmib mailing list
	Adslmib@ietf.org
	https://www1.ietf.org/mailman/listinfo/adslmib
=09
=09


------_=_NextPart_001_01C6CF3E.3C2D6D31
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2963" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D116244509-03092006><FONT face=3DArial color=3D#0000ff =

size=3D2><STRONG><EM>Menachem,</EM></STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=3D116244509-03092006><FONT face=3DArial color=3D#0000ff =

size=3D2><STRONG><EM></EM></STRONG></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D116244509-03092006><FONT face=3DArial color=3D#0000ff =

size=3D2><STRONG><EM>I would&nbsp;suggest that you make clear&nbsp;the =
impact of=20
this charter action on the current charter and schedules of hubmib, if =
there is=20
any. For this purpose I would suggest that you copy <A=20
href=3D"mailto:hubmib@ietf.org">hubmib@ietf.org</A> on further mails on =
this=20
subject. </EM></STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=3D116244509-03092006><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D116244509-03092006><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Please also copy David Kessens. As I am wearing both AD and =
hubmib chair=20
hats, it's better to have both ADs looking at this.=20
</FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D116244509-03092006><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D116244509-03092006><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Dan</FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D116244509-03092006></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D116244509-03092006><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D116244509-03092006><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Menachem.Dodge@ecitele.com=20
  [mailto:Menachem.Dodge@ecitele.com] <BR><B>Sent:</B> Thursday, August =
31, 2006=20
  3:08 PM<BR><B>To:</B> adslmib@ietf.org<BR><B>Cc:</B> =
EdwardB@actelis.com;=20
  narendranath.nair@wipro.com<BR><B>Subject:</B> RE: [Adslmib] Re: =
Liaison to=20
  DSL Forum<BR></FONT><BR></DIV>
  <DIV></DIV><BR><FONT face=3Dsans-serif size=3D2>It seems that there is =
agreement=20
  for a common MIB that will hold the common information and will then =
reference=20
  3 specific MIBs</FONT> <BR><FONT face=3Dsans-serif size=3D2>for the =
ATM, Ethernet=20
  and TDIM specific parameters.</FONT> <BR><BR><FONT face=3Dsans-serif=20
  size=3D2>Unless I hear something to the contrary, I will draft a =
charter and=20
  present it on the mailing list early next week.</FONT> <BR><BR><FONT=20
  face=3Dsans-serif size=3D2>Best Regards,</FONT> <BR><FONT =
face=3Dsans-serif=20
  size=3D2>Menachem</FONT> <BR><BR><BR><BR>
  <TABLE width=3D"100%">
    <TBODY>
    <TR vAlign=3Dtop>
      <TD width=3D"40%"><FONT face=3Dsans-serif=20
        size=3D1><B>&lt;narendranath.nair@wipro.com&gt;</B> </FONT>
        <P><FONT face=3Dsans-serif size=3D1>31/08/2006 14:07</FONT> </P>
      <TD width=3D"59%">
        <TABLE width=3D"100%">
          <TBODY>
          <TR vAlign=3Dtop>
            <TD>
              <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>To</FONT></DIV>
            <TD><FONT face=3Dsans-serif =
size=3D1>&lt;EdwardB@actelis.com&gt;,=20
              &lt;frank.van_der_putten@alcatel.be&gt;,=20
              &lt;Menachem.Dodge@ecitele.com&gt;</FONT>=20
          <TR vAlign=3Dtop>
            <TD>
              <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>cc</FONT></DIV>
            <TD><FONT face=3Dsans-serif size=3D1>adslmib@ietf.org</FONT> =

          <TR vAlign=3Dtop>
            <TD>
              <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>Subject</FONT></DIV>
            <TD><FONT face=3Dsans-serif size=3D1>RE: [Adslmib] Re: =
Liaison to DSL=20
              Forum</FONT></TR></TBODY></TABLE><BR>
        <TABLE>
          <TBODY>
          <TR vAlign=3Dtop>
            <TD>
            =
<TD></TR></TBODY></TABLE><BR></TR></TBODY></TABLE><BR><BR><BR><FONT =
face=3DArial=20
  color=3D#000080 size=3D2>I am also in agreement with having a common =
MIB and then=20
  specific ones based on the L2 technology type.</FONT> <BR><FONT =
face=3DArial=20
  color=3D#000080 size=3D2>&nbsp;</FONT> <BR><FONT face=3DArial =
color=3D#000080=20
  size=3D2>Regards</FONT> <BR><FONT face=3DArial color=3D#000080 =
size=3D2>Naren</FONT>=20
  <BR><FONT face=3DArial color=3D#000080 size=3D2>&nbsp;</FONT>=20
  <DIV align=3Dcenter><BR>
  <HR>
  </DIV><BR><FONT face=3DTahoma size=3D2><B>From:</B> Edward Beili=20
  [mailto:EdwardB@actelis.com] <B><BR>Sent:</B> Thursday, August 31, =
2006 4:20=20
  PM<B><BR>To:</B> frank.van_der_putten@alcatel.be;=20
  Menachem.Dodge@ecitele.com<B><BR>Cc:</B> =
adslmib@ietf.org<B><BR>Subject:</B>=20
  RE: [Adslmib] Re: Liaison to DSL Forum</FONT> <BR><FONT face=3D"Times =
New Roman"=20
  size=3D3>&nbsp;</FONT> <BR><FONT face=3DArial color=3Dblue size=3D2>I =
agree with=20
  Frank, there should be a separate MIB for each G.Bond =
specification.</FONT>=20
  <BR><FONT face=3D"Times New Roman" size=3D3>&nbsp;</FONT> <BR><FONT =
face=3DArial=20
  color=3Dblue size=3D2>The ifAvailableStackTable and ifStackTable (with =
their=20
  inverse counterparts) are of course common for all 3 MIBs.</FONT> =
<BR><FONT=20
  face=3D"Times New Roman" size=3D3>&nbsp;</FONT> <BR><FONT face=3DArial =
color=3Dblue=20
  size=3D2>We could create a common MIB for all 3 specifications, =
providing G.Bond=20
  overview, referencing 3 specific MIBs and may be even providing some =
common=20
  objects in a MIB, for example LowBandwidth trap etc.</FONT> <BR><FONT=20
  face=3D"Times New Roman" size=3D3>&nbsp;</FONT> <BR><FONT face=3DArial =
color=3Dblue=20
  size=3D2>Regards,</FONT> <BR><FONT face=3DArial color=3Dblue =
size=3D2>-E.</FONT>=20
  <BR><FONT face=3DTahoma size=3D2>-----Original =
Message-----<B><BR>From:</B>=20
  frank.van_der_putten@alcatel.be=20
  [mailto:frank.van_der_putten@alcatel.be]<B><BR>Sent:</B> Thursday, =
August 31,=20
  2006 11:35 AM<B><BR>To:</B> Menachem.Dodge@ecitele.com<B><BR>Cc:</B>=20
  adslmib@ietf.org<B><BR>Subject:</B> Re: [Adslmib] Re: Liaison to DSL=20
  Forum</FONT> <BR><FONT face=3D"Times New Roman" =
size=3D3>Menachem,<BR>Liaison is=20
  OK.<BR>On the bonding MIB: the three bonding standards each handle =
different=20
  things (cells, packets,bits).<BR>So I believe the MIBs should be =
separate as I=20
  expect a lot of the managed objects will be=20
  different.<BR>Regards,<BR>Frank<BR><BR></FONT><FONT face=3D"Times New =
Roman"=20
  color=3Dblue size=3D3><U><BR></U></FONT><A=20
  href=3D"mailto:Menachem.Dodge@ecitele.com"><FONT face=3D"Times New =
Roman"=20
  color=3Dblue =
size=3D3><U>Menachem.Dodge@ecitele.com</U></FONT></A><FONT=20
  face=3D"Times New Roman" size=3D3> wrote:<BR></FONT><BR><FONT =
face=3Dsans-serif=20
  size=3D2><BR>Hello, </FONT><FONT face=3D"Times New Roman" =
size=3D3><BR></FONT><FONT=20
  face=3Dsans-serif size=3D2><BR>&nbsp; &nbsp; &nbsp; &nbsp;I haven't =
received any=20
  further feedback on the Liaison, so I will send it to the DSL=20
  Forum.</FONT><FONT face=3D"Times New Roman" size=3D3> <BR></FONT><FONT =

  face=3Dsans-serif size=3D2><BR>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;=20
  &nbsp;Regarding xDSL bonding issue, I believe that:</FONT><FONT=20
  face=3D"Times New Roman" size=3D3> <BR></FONT><FONT face=3Dsans-serif=20
  size=3D2><BR>&nbsp; &nbsp; &nbsp; &nbsp;1. &nbsp;There is Working =
Group=20
  agreement to base our work on the three </FONT><FONT face=3DArial=20
  size=3D2>ITU-T</FONT><FONT face=3Dsans-serif size=3D2> </FONT><FONT =
face=3DArial=20
  size=3D2>specifications: G.998.1 (ATM), G.998.2 (Ethernet) and G.998.3 =

  (TDIM).</FONT><FONT face=3DArial color=3Dblue size=3D2> </FONT><FONT=20
  face=3D"Times New Roman" size=3D3><BR></FONT><FONT face=3Dsans-serif=20
  size=3D2><BR>&nbsp; &nbsp; &nbsp; &nbsp;2. There are differing =
opinions as to=20
  whether there should be one MIB or 3 separate MIBs to handle the three =

  <BR>cases - ATM, Ethernet, and TDIM.</FONT><FONT face=3D"Times New =
Roman"=20
  size=3D3> <BR><BR></FONT><FONT face=3Dsans-serif size=3D2><BR>&nbsp; =
&nbsp; &nbsp;=20
  &nbsp;I wish to resolve this issue now, so I would appreciate if =
everyone=20
  would state their opinion (again).</FONT><FONT face=3D"Times New =
Roman" size=3D3>=20
  <BR></FONT><FONT face=3Dsans-serif size=3D2><BR>Best =
Regards,</FONT><FONT=20
  face=3D"Times New Roman" size=3D3> </FONT><FONT face=3Dsans-serif=20
  size=3D2><BR>Menachem </FONT><FONT face=3D"Times New Roman"=20
  size=3D3><BR><BR><BR></FONT>
  <P>
  <TABLE width=3D"100%">
    <TBODY>
    <TR vAlign=3Dtop>
      <TD width=3D"57%"><FONT face=3Dsans-serif size=3D1><B>Menachem =
Dodge/ECI=20
        Telecom</B> </FONT>
        <P><FONT face=3Dsans-serif size=3D1>28/08/2006 19:02</FONT><FONT =

        face=3D"Times New Roman" size=3D3> </FONT></P>
      <TD width=3D"42%"><BR>
        <TABLE width=3D"100%">
          <TBODY>
          <TR vAlign=3Dtop>
            <TD width=3D"26%">
              <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>To</FONT></DIV>
            <TD width=3D"73%"><A href=3D"mailto:adslmib@ietf.org"><FONT=20
              face=3Dsans-serif color=3Dblue=20
              size=3D1><U>adslmib@ietf.org</U></FONT></A><FONT=20
              face=3D"Times New Roman" size=3D3> </FONT>
          <TR vAlign=3Dtop>
            <TD>
              <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>cc</FONT></DIV>
            <TD><FONT face=3D"Times New Roman" size=3D3>&nbsp;</FONT>=20
          <TR vAlign=3Dtop>
            <TD>
              <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>Subject</FONT></DIV>
            <TD><FONT face=3Dsans-serif size=3D1>Liaison to DSL=20
          Forum</FONT></TR></TBODY></TABLE><BR><FONT face=3D"Times New =
Roman"=20
        size=3D3>&nbsp;</FONT>=20
        <P><BR>
        <TABLE width=3D"100%">
          <TBODY>
          <TR vAlign=3Dtop>
            <TD width=3D"50%"><FONT face=3D"Times New Roman" =
size=3D3>&nbsp;</FONT>=20
            <TD width=3D"50%"><FONT face=3D"Times New Roman"=20
          =
size=3D3>&nbsp;</FONT></TR></TBODY></TABLE><BR></P></TR></TBODY></TABLE><=
BR><FONT=20
  face=3D"Times New Roman" size=3D3><BR></FONT><FONT face=3Dsans-serif=20
  size=3D2><BR>Hi,</FONT><FONT face=3D"Times New Roman" size=3D3> =
<BR></FONT><FONT=20
  face=3Dsans-serif size=3D2><BR>&nbsp; &nbsp; &nbsp; &nbsp;I have added =
an=20
  additional paragraph informing the DSL Forum of our progress on the =
VDSL2 MIB=20
  (as per the charter). Let me know</FONT><FONT face=3D"Times New Roman" =
size=3D3>=20
  </FONT><FONT face=3Dsans-serif size=3D2><BR>if you have any comments, =
until=20
  Wednesday 30th August.</FONT><FONT face=3D"Times New Roman" size=3D3>=20
  <BR><BR><BR><BR><BR></FONT><FONT face=3Dsans-serif size=3D2><BR>&nbsp; =
&nbsp;=20
  &nbsp; =
&nbsp;=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D</FONT><FONT face=3D"Times New Roman"=20
  size=3D3> <BR><BR></FONT><FONT face=3Dsans-serif size=3D2><BR>&nbsp; =
&nbsp; &nbsp;=20
  &nbsp;Regarding the xDSL Bonding, I have several volunteers for =
editors of the=20
  document(s) but I need to know if there is anyone <BR>prepared to =
review the=20
  document. Please let me know (privately if you wish) whether you are =
willing=20
  to review the document. It would be helpful</FONT><FONT face=3D"Times =
New Roman"=20
  size=3D3> </FONT><FONT face=3Dsans-serif size=3D2><BR>to know if there =
is anyone who=20
  will be implementing the MIB as well. </FONT><FONT face=3D"Times New =
Roman"=20
  size=3D3><BR></FONT><FONT face=3Dsans-serif size=3D2><BR>&nbsp; &nbsp; =
&nbsp;=20
  &nbsp;Once I have this, the following steps are required:</FONT><FONT=20
  face=3D"Times New Roman" size=3D3> <BR></FONT><FONT face=3Dsans-serif=20
  size=3D2><BR>&nbsp; &nbsp; &nbsp; &nbsp;1. I will put forward a =
modified charter=20
  for approval by the Working Group.</FONT><FONT face=3D"Times New =
Roman" size=3D3>=20
  </FONT><FONT face=3Dsans-serif size=3D2><BR>&nbsp; &nbsp; &nbsp; =
&nbsp;2. Once=20
  approved by the Working Group, I will send the new charter text to the =
AD, Dan=20
  Romascanu, requesting that he brings the</FONT><FONT face=3D"Times New =
Roman"=20
  size=3D3> </FONT><FONT face=3Dsans-serif size=3D2><BR>charter to the =
IESG for=20
  approval.</FONT><FONT face=3D"Times New Roman" size=3D3> =
<BR><BR></FONT><FONT=20
  face=3Dsans-serif size=3D2><BR>&nbsp; &nbsp; &nbsp;=20
  =
&nbsp;=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D</FONT><FONT face=3D"Times New Roman" size=3D3>=20
  <BR></FONT><FONT face=3Dsans-serif size=3D2><BR>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;=20
  &nbsp; &nbsp; &nbsp;Regarding the Vdsl2 draft, I would like to see =
some=20
  review, comments, feedback ....</FONT><FONT face=3D"Times New Roman" =
size=3D3>=20
  </FONT><FONT face=3Dsans-serif size=3D2><BR>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;=20
  &nbsp; &nbsp; &nbsp;</FONT><FONT face=3D"Times New Roman"=20
  size=3D3><BR></FONT><FONT face=3Dsans-serif size=3D2><BR>Best =
Regards,</FONT><FONT=20
  face=3D"Times New Roman" size=3D3> </FONT><FONT face=3Dsans-serif=20
  size=3D2><BR>Menachem </FONT><FONT face=3D"Times New Roman" =
size=3D3><BR></FONT>
  <DIV align=3Dcenter><BR><FONT face=3D"Courier New" =
size=3D2><BR><BR></FONT>
  <HR>
  <FONT face=3D"Courier New" size=3D2><BR><BR></FONT></DIV><BR><FONT=20
  face=3D"Courier New" size=3D2>&nbsp;</FONT> <BR><FONT face=3D"Courier =
New"=20
  size=3D2>Subject: Response To Your Liaison on WT-129.</FONT> <BR><FONT =

  face=3D"Courier New" size=3D2>&nbsp;</FONT> <BR><FONT face=3D"Courier =
New"=20
  size=3D2>Date: &nbsp;28th August, 2006.</FONT> <BR><FONT =
face=3D"Courier New"=20
  size=3D2>&nbsp;</FONT> <BR><FONT face=3D"Courier New" =
size=3D2>&nbsp;</FONT>=20
  <BR><FONT face=3D"Courier New" size=3D2>To: &nbsp; &nbsp;Gavin Young,=20
  </FONT><BR><FONT face=3D"Courier New" size=3D2>&nbsp; &nbsp; &nbsp; =
&nbsp;DSL=20
  Forum Technical Committee Chair</FONT> <BR><FONT face=3D"Courier New"=20
  size=3D2>&nbsp; &nbsp; &nbsp; &nbsp;"Gavin Young" </FONT><A=20
  href=3D"mailto:gyoung@dslforum.org"><FONT face=3D"Courier New" =
color=3Dblue=20
  size=3D2><U>&lt;gyoung@dslforum.org&gt;</U></FONT></A> <BR><FONT=20
  face=3D"Courier New" size=3D2>&nbsp;</FONT> <BR><FONT face=3D"Courier =
New"=20
  size=3D2>&nbsp; &nbsp; &nbsp; &nbsp;Peter Adams, </FONT><BR><FONT=20
  face=3D"Courier New" size=3D2>&nbsp; &nbsp; &nbsp; &nbsp;DSL Forum =
Operations and=20
  Network Management Working Group Chair</FONT> <BR><FONT =
face=3D"Courier New"=20
  size=3D2>&nbsp; &nbsp; &nbsp; &nbsp;"Peter Adams" </FONT><A=20
  href=3D"mailto:p.f.adams@btopenworld.com"><FONT face=3D"Courier New" =
color=3Dblue=20
  size=3D2><U>&lt;p.f.adams@btopenworld.com&gt;</U></FONT></A> <BR><FONT =

  face=3D"Courier New" size=3D2>&nbsp;</FONT> <BR><FONT face=3D"Courier =
New"=20
  size=3D2>&nbsp;</FONT> <BR><FONT face=3D"Courier New" size=3D2>Cc: =
&nbsp; &nbsp;IETF=20
  </FONT><A href=3D"mailto:statements@ietf.org"><FONT face=3D"Courier =
New"=20
  color=3Dblue size=3D2><U>statements@ietf.org</U></FONT></A> <BR><FONT=20
  face=3D"Courier New" size=3D2>&nbsp; &nbsp; &nbsp; &nbsp;</FONT><A=20
  href=3D"mailto:IAB@ietf.org"><FONT face=3D"Courier New" color=3Dblue=20
  size=3D2><U>IAB@ietf.org</U></FONT></A> <BR><FONT face=3D"Courier New" =

  size=3D2>&nbsp; &nbsp; &nbsp; &nbsp; </FONT><BR><FONT face=3D"Courier =
New"=20
  size=3D2>&nbsp; &nbsp; &nbsp; &nbsp;Loa Andersson</FONT> <BR><FONT=20
  face=3D"Courier New" size=3D2>&nbsp; &nbsp; &nbsp; &nbsp;"Loa =
Andersson" </FONT><A=20
  href=3D"mailto:loa@pi.se"><FONT face=3D"Courier New" color=3Dblue=20
  size=3D2><U>&lt;loa@pi.se&gt;</U></FONT></A> <BR><FONT face=3D"Courier =
New"=20
  size=3D2>&nbsp;</FONT> <BR><FONT face=3D"Courier New" size=3D2>&nbsp; =
&nbsp; &nbsp;=20
  &nbsp;Dan Romascanu</FONT> <BR><FONT face=3D"Courier New" =
size=3D2>&nbsp; &nbsp;=20
  &nbsp; &nbsp;Operations and Management Area Director</FONT> <BR><FONT=20
  face=3D"Courier New" size=3D2>&nbsp; &nbsp; &nbsp; &nbsp;"Romascanu, =
Dan"=20
  </FONT><A href=3D"mailto:dromasca@avaya.com"><FONT face=3D"Courier =
New" color=3Dblue=20
  size=3D2><U>&lt;dromasca@avaya.com&gt;</U></FONT></A> <BR><FONT=20
  face=3D"Courier New" size=3D2>&nbsp;</FONT> <BR><FONT face=3D"Courier =
New"=20
  size=3D2>&nbsp; &nbsp; &nbsp; &nbsp;Michael Sneed</FONT> <BR><FONT=20
  face=3D"Courier New" size=3D2>&nbsp; &nbsp; &nbsp; &nbsp;IETF ADSL MIB =
Working=20
  Group Co-Chair</FONT> <BR><FONT face=3D"Courier New" size=3D2>&nbsp; =
&nbsp; &nbsp;=20
  &nbsp;"Michael Sneed" </FONT><A =
href=3D"mailto:sneedmike@hotmail.com"><FONT=20
  face=3D"Courier New" color=3Dblue =
size=3D2><U>sneedmike@hotmail.com</U></FONT></A>=20
  <BR><FONT face=3D"Courier New" size=3D2>&nbsp; &nbsp; &nbsp; =
&nbsp;</FONT>=20
  <BR><FONT face=3D"Courier New" size=3D2>&nbsp;</FONT> <BR><FONT =
face=3D"Courier New"=20
  size=3D2>From: &nbsp;IETF ADSL MIB Working Group</FONT> <BR><FONT=20
  face=3D"Courier New" size=3D2>&nbsp;</FONT> <BR><FONT face=3D"Courier =
New"=20
  size=3D2>Response &nbsp;contact: &nbsp; Menachem Dodge</FONT> =
<BR><FONT=20
  face=3D"Courier New" size=3D2>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;=20
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; IETF ADSL MIB Working Group =
Co-Chair</FONT>=20
  <BR><FONT face=3D"Courier New" size=3D2>&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;=20
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "Menachem Dodge" </FONT><A=20
  href=3D"mailto:menachem.dodge@ecitele.com"><FONT face=3D"Courier New" =
color=3Dblue=20
  size=3D2><U>&lt;menachem.dodge@ecitele.com&gt;</U></FONT></A> =
<BR><FONT=20
  face=3D"Courier New" size=3D2>&nbsp;</FONT> <BR><FONT face=3D"Courier =
New"=20
  size=3D2>Technical contact: &nbsp; &nbsp; &nbsp;"Menachem Dodge" =
</FONT><A=20
  href=3D"mailto:menachem.dodge@ecitele.com"><FONT face=3D"Courier New" =
color=3Dblue=20
  size=3D2><U>&lt;menachem.dodge@ecitele.com&gt;</U></FONT></A> =
<BR><FONT=20
  face=3D"Courier New" size=3D2>&nbsp;</FONT> <BR><FONT face=3D"Courier =
New"=20
  size=3D2>&nbsp;</FONT> <BR><FONT face=3D"Courier New" =
size=3D2>PURPOSE:=20
  Response</FONT> <BR><FONT face=3D"Courier New" size=3D2>&nbsp;</FONT> =
<BR><FONT=20
  face=3D"Courier New" size=3D2>Subject: Response To Your Liaison on =
WT-129.</FONT>=20
  <BR><FONT face=3D"Courier New" size=3D2>&nbsp;</FONT> <BR><FONT =
face=3D"Courier New"=20
  size=3D2>Dear Gavin and Peter,</FONT> <BR><FONT face=3D"Courier New"=20
  size=3D2>&nbsp;</FONT> <BR><FONT face=3D"Courier New" =
size=3D2>&nbsp;</FONT>=20
  <BR><FONT face=3D"Courier New" size=3D2>&nbsp; &nbsp; &nbsp; Thank you =
for your=20
  liaison and WT-129 Version 3.0. We would be very grateful if</FONT> =
<BR><FONT=20
  face=3D"Courier New" size=3D2>you would continue to keep us informed =
of any=20
  changes to this Working Text document.</FONT> <BR><FONT =
face=3D"Courier New"=20
  size=3D2>&nbsp;</FONT> <BR><FONT face=3D"Courier New" size=3D2>&nbsp; =
&nbsp; &nbsp;=20
  As I informed you in February this year, work has begun on development =
of a=20
  MIB </FONT><BR><FONT face=3D"Courier New" size=3D2>for DSL (ADSL, =
ADSL2, ADSL2+=20
  and VDSL2) lines. This work has progressed and the latest draft</FONT> =

  <BR><FONT face=3D"Courier New" size=3D2>can be found at </FONT><A=20
  =
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-adslmib-vdsl2-01.t=
xt"><FONT=20
  face=3D"Courier New" color=3Dblue=20
  =
size=3D2><U>http://www.ietf.org/internet-drafts/draft-ietf-adslmib-vdsl2-=
01.txt</U></FONT></A><FONT=20
  face=3D"Courier New" size=3D2>. We would </FONT><BR><FONT =
face=3D"Courier New"=20
  size=3D2>be most pleased, if you would inform us of any feedback that =
the DSL=20
  Forum may have on this </FONT><BR><FONT face=3D"Courier New"=20
  size=3D2>document.</FONT> <BR><FONT face=3D"Courier New" =
size=3D2>&nbsp;</FONT>=20
  <BR><FONT face=3D"Courier New" size=3D2>&nbsp; &nbsp; &nbsp; We would =
like to=20
  raise the issue of xDSL Bonding, as defined by the ITU-T =
documents</FONT>=20
  <BR><FONT face=3D"Courier New" size=3D2>&nbsp;G.998.1, G.998.2 and =
G.998.3.=20
  &nbsp;The management of xDSL Bonded lines has currently not been=20
  </FONT><BR><FONT face=3D"Courier New" size=3D2>addressed, by the DSL =
Forum. The=20
  IETF ADSL MIB Working Group believes that this issue is =
important</FONT>=20
  <BR><FONT face=3D"Courier New" size=3D2>and would be very pleased if =
the DSL Forum=20
  Operations and Network Management Working Group</FONT> <BR><FONT=20
  face=3D"Courier New" size=3D2>would address this issue and provide a =
management=20
  framework for xDSL Bonding.</FONT> <BR><FONT face=3D"Courier New"=20
  size=3D2>&nbsp;</FONT> <BR><FONT face=3D"Courier New" =
size=3D2>&nbsp;</FONT>=20
  <BR><FONT face=3D"Courier New" size=3D2>&nbsp; &nbsp; &nbsp; Yours=20
  Sincerely,</FONT> <BR><FONT face=3D"Courier New" =
size=3D2>&nbsp;</FONT> <BR><FONT=20
  face=3D"Courier New" size=3D2>&nbsp;</FONT> <BR><FONT face=3D"Courier =
New"=20
  size=3D2>&nbsp; &nbsp; &nbsp; Menachem Dodge</FONT> <BR><FONT =
face=3D"Courier New"=20
  size=3D2>&nbsp; &nbsp; &nbsp; &nbsp; IETF ADSL MIB Working Group =
Co-Chair</FONT>=20
  <BR><FONT face=3D"Courier New" size=3D2>&nbsp;</FONT> <BR><FONT =
face=3D"Courier New"=20
  size=3D2>&nbsp;</FONT> <BR><FONT face=3D"Courier New" =
size=3D2>&nbsp;</FONT>=20
  <BR><FONT face=3D"Courier New" size=3D2>&nbsp; &nbsp; &nbsp; </FONT>
  <DIV align=3Dcenter><BR><FONT face=3D"Courier New" =
size=3D2><BR><BR></FONT>
  <HR>
  <FONT face=3D"Courier New" size=3D2><BR><BR></FONT></DIV><BR><FONT=20
  face=3D"Courier New" size=3D2>&nbsp;</FONT> <BR><FONT face=3D"Courier =
New"=20
  size=3D2>_______________________________________________</FONT> =
<BR><FONT=20
  face=3D"Courier New" size=3D2>Adslmib mailing list</FONT> <BR><A=20
  href=3D"mailto:Adslmib@ietf.org"><FONT face=3D"Courier New" =
color=3Dblue=20
  size=3D2><U>Adslmib@ietf.org</U></FONT></A> <BR><A=20
  href=3D"https://www1.ietf.org/mailman/listinfo/adslmib"><FONT =
face=3D"Courier New"=20
  color=3Dblue=20
  =
size=3D2><U>https://www1.ietf.org/mailman/listinfo/adslmib</U></FONT></A>=
=20
  <BR><FONT face=3D"Courier New" size=3D2>&nbsp; </FONT><FONT=20
  =
size=3D2><TT>_______________________________________________<BR>Adslmib =
mailing=20
  =
list<BR>Adslmib@ietf.org<BR>https://www1.ietf.org/mailman/listinfo/adslmi=
b<BR></TT></FONT><BR></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C6CF3E.3C2D6D31--


--===============0842290644==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0842290644==--




From adslmib-bounces@ietf.org Sun Sep 03 11:01:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GJtTd-0002Pp-0d; Sun, 03 Sep 2006 11:01:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GJtTb-0002Pg-S6; Sun, 03 Sep 2006 11:01:35 -0400
Received: from ilsmtp01.ecitele.com ([147.234.1.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GJtTY-0002IY-DA; Sun, 03 Sep 2006 11:01:35 -0400
In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F0B274A30@IS0004AVEXU1.global.avaya.com>
To: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
Subject: RE: [Adslmib] Re: Liaison to DSL Forum
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.3 September 14, 2004
Message-ID: <OF0D50D3D3.688C3FAB-ONC22571DE.00511BEB-C22571DE.0052874B@ecitele.com>
From: Menachem.Dodge@ecitele.com
Date: Sun, 3 Sep 2006 18:01:25 +0300
X-MIMETrack: Serialize by Router on ILSMTP01/ECI Telecom(Release 6.5.3FP1 |
	December 22, 2004) at 09/03/2006 18:10:10,
	Serialize complete at 09/03/2006 18:10:10
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 72be645574b2b4b84446d27f730bf563
Cc: adslmib@ietf.org, EdwardB@actelis.com,
	David Kessens <david.kessens@nokia.com>,
	narendranath.nair@wipro.com, hubmib@ietf.org
X-BeenThere: adslmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ADSLMIB <adslmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/adslmib>,
	<mailto:adslmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:adslmib@ietf.org>
List-Help: <mailto:adslmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/adslmib>,
	<mailto:adslmib-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0647306790=="
Errors-To: adslmib-bounces@ietf.org

This is a multipart message in MIME format.
--===============0647306790==
Content-Type: multipart/alternative;
	boundary="=_alternative 0052873EC22571DE_="

This is a multipart message in MIME format.
--=_alternative 0052873EC22571DE_=
Content-Type: text/plain; charset="US-ASCII"

Dan,

        Ok, I will copy the hubmib WG and David Kessens on all further 
emails on this subject.

        I believe that the only impact for the hubmib WG is the change 
that was stated earlier for the Efm Cu MIB namely, 
the separation of the ifAvailableStack MIB and the addition of the 
ifInvAvailableStack MIB into a distinct MIB module with 
revised DESCRIPTION. 

 
Best Regards,
Menachem





"Romascanu, Dan \(Dan\)" <dromasca@avaya.com> 
03/09/2006 12:49

To
<Menachem.Dodge@ecitele.com>, <adslmib@ietf.org>
cc
David Kessens <david.kessens@nokia.com>, hubmib@ietf.org, 
EdwardB@actelis.com, narendranath.nair@wipro.com
Subject
RE: [Adslmib] Re: Liaison to DSL Forum






Menachem,
 
I would suggest that you make clear the impact of this charter action on 
the current charter and schedules of hubmib, if there is any. For this 
purpose I would suggest that you copy hubmib@ietf.org on further mails on 
this subject. 
 
Please also copy David Kessens. As I am wearing both AD and hubmib chair 
hats, it's better to have both ADs looking at this. 
 
Dan
 
 
 
 
 
 

From: Menachem.Dodge@ecitele.com [mailto:Menachem.Dodge@ecitele.com] 
Sent: Thursday, August 31, 2006 3:08 PM
To: adslmib@ietf.org
Cc: EdwardB@actelis.com; narendranath.nair@wipro.com
Subject: RE: [Adslmib] Re: Liaison to DSL Forum


It seems that there is agreement for a common MIB that will hold the 
common information and will then reference 3 specific MIBs 
for the ATM, Ethernet and TDIM specific parameters. 

Unless I hear something to the contrary, I will draft a charter and 
present it on the mailing list early next week. 

Best Regards, 
Menachem 



<narendranath.nair@wipro.com> 
31/08/2006 14:07 


To
<EdwardB@actelis.com>, <frank.van_der_putten@alcatel.be>, 
<Menachem.Dodge@ecitele.com> 
cc
adslmib@ietf.org 
Subject
RE: [Adslmib] Re: Liaison to DSL Forum








I am also in agreement with having a common MIB and then specific ones 
based on the L2 technology type. 
  
Regards 
Naren 
  



From: Edward Beili [mailto:EdwardB@actelis.com] 
Sent: Thursday, August 31, 2006 4:20 PM
To: frank.van_der_putten@alcatel.be; Menachem.Dodge@ecitele.com
Cc: adslmib@ietf.org
Subject: RE: [Adslmib] Re: Liaison to DSL Forum 
  
I agree with Frank, there should be a separate MIB for each G.Bond 
specification. 
  
The ifAvailableStackTable and ifStackTable (with their inverse 
counterparts) are of course common for all 3 MIBs. 
  
We could create a common MIB for all 3 specifications, providing G.Bond 
overview, referencing 3 specific MIBs and may be even providing some 
common objects in a MIB, for example LowBandwidth trap etc. 
  
Regards, 
-E. 
-----Original Message-----
From: frank.van_der_putten@alcatel.be 
[mailto:frank.van_der_putten@alcatel.be]
Sent: Thursday, August 31, 2006 11:35 AM
To: Menachem.Dodge@ecitele.com
Cc: adslmib@ietf.org
Subject: Re: [Adslmib] Re: Liaison to DSL Forum 
Menachem,
Liaison is OK.
On the bonding MIB: the three bonding standards each handle different 
things (cells, packets,bits).
So I believe the MIBs should be separate as I expect a lot of the managed 
objects will be different.
Regards,
Frank


Menachem.Dodge@ecitele.com wrote:


Hello, 

       I haven't received any further feedback on the Liaison, so I will 
send it to the DSL Forum. 

               Regarding xDSL bonding issue, I believe that: 

       1.  There is Working Group agreement to base our work on the three 
ITU-T specifications: G.998.1 (ATM), G.998.2 (Ethernet) and G.998.3 
(TDIM). 

       2. There are differing opinions as to whether there should be one 
MIB or 3 separate MIBs to handle the three 
cases - ATM, Ethernet, and TDIM. 


       I wish to resolve this issue now, so I would appreciate if everyone 
would state their opinion (again). 

Best Regards, 
Menachem 



Menachem Dodge/ECI Telecom 
28/08/2006 19:02 


To
adslmib@ietf.org 
cc
  
Subject
Liaison to DSL Forum

  


  
 




Hi, 

       I have added an additional paragraph informing the DSL Forum of our 
progress on the VDSL2 MIB (as per the charter). Let me know 
if you have any comments, until Wednesday 30th August. 





       ========================== 


       Regarding the xDSL Bonding, I have several volunteers for editors 
of the document(s) but I need to know if there is anyone 
prepared to review the document. Please let me know (privately if you 
wish) whether you are willing to review the document. It would be helpful 
to know if there is anyone who will be implementing the MIB as well. 

       Once I have this, the following steps are required: 

       1. I will put forward a modified charter for approval by the 
Working Group. 
       2. Once approved by the Working Group, I will send the new charter 
text to the AD, Dan Romascanu, requesting that he brings the 
charter to the IESG for approval. 


       ======================== 

               Regarding the Vdsl2 draft, I would like to see some review, 
comments, feedback .... 
 

Best Regards, 
Menachem 






  
Subject: Response To Your Liaison on WT-129. 
  
Date:  28th August, 2006. 
  
  
To:    Gavin Young, 
       DSL Forum Technical Committee Chair 
       "Gavin Young" <gyoung@dslforum.org> 
  
       Peter Adams, 
       DSL Forum Operations and Network Management Working Group Chair 
       "Peter Adams" <p.f.adams@btopenworld.com> 
  
  
Cc:    IETF statements@ietf.org 
       IAB@ietf.org 
 
       Loa Andersson 
       "Loa Andersson" <loa@pi.se> 
  
       Dan Romascanu 
       Operations and Management Area Director 
       "Romascanu, Dan" <dromasca@avaya.com> 
  
       Michael Sneed 
       IETF ADSL MIB Working Group Co-Chair 
       "Michael Sneed" sneedmike@hotmail.com 
        
  
From:  IETF ADSL MIB Working Group 
  
Response  contact:   Menachem Dodge 
                        IETF ADSL MIB Working Group Co-Chair 
                        "Menachem Dodge" <menachem.dodge@ecitele.com> 
  
Technical contact:      "Menachem Dodge" <menachem.dodge@ecitele.com> 
  
  
PURPOSE: Response 
  
Subject: Response To Your Liaison on WT-129. 
  
Dear Gavin and Peter, 
  
  
      Thank you for your liaison and WT-129 Version 3.0. We would be very 
grateful if 
you would continue to keep us informed of any changes to this Working Text 
document. 
  
      As I informed you in February this year, work has begun on 
development of a MIB 
for DSL (ADSL, ADSL2, ADSL2+ and VDSL2) lines. This work has progressed 
and the latest draft 
can be found at 
http://www.ietf.org/internet-drafts/draft-ietf-adslmib-vdsl2-01.txt. We 
would 
be most pleased, if you would inform us of any feedback that the DSL Forum 
may have on this 
document. 
  
      We would like to raise the issue of xDSL Bonding, as defined by the 
ITU-T documents 
 G.998.1, G.998.2 and G.998.3.  The management of xDSL Bonded lines has 
currently not been 
addressed, by the DSL Forum. The IETF ADSL MIB Working Group believes that 
this issue is important 
and would be very pleased if the DSL Forum Operations and Network 
Management Working Group 
would address this issue and provide a management framework for xDSL 
Bonding. 
  
  
      Yours Sincerely, 
  
  
      Menachem Dodge 
        IETF ADSL MIB Working Group Co-Chair 
  
  
  
 






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


--=_alternative 0052873EC22571DE_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Dan,</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Ok,
I will copy the hubmib WG and David Kessens on all further emails on this
subject.</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; I
believe that the only impact for the hubmib WG is the change that was stated
earlier for the Efm Cu MIB namely, </font>
<br><font size=2 face="sans-serif">the separation of the ifAvailableStack
MIB and the addition of the ifInvAvailableStack MIB into a distinct MIB
module with </font>
<br><font size=2 face="sans-serif">revised DESCRIPTION. </font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=2 face="sans-serif">Best Regards,</font>
<br><font size=2 face="sans-serif">Menachem</font>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>&quot;Romascanu, Dan \(Dan\)&quot;
&lt;dromasca@avaya.com&gt;</b> </font>
<p><font size=1 face="sans-serif">03/09/2006 12:49</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">&lt;Menachem.Dodge@ecitele.com&gt;,
&lt;adslmib@ietf.org&gt;</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">David Kessens &lt;david.kessens@nokia.com&gt;,
hubmib@ietf.org, EdwardB@actelis.com, narendranath.nair@wipro.com</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">RE: [Adslmib] Re: Liaison to DSL Forum</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2 color=blue face="Arial"><b><i>Menachem,</i></b></font>
<br><font size=3>&nbsp;</font>
<br><font size=2 color=blue face="Arial"><b><i>I would suggest that you
make clear the impact of this charter action on the current charter and
schedules of hubmib, if there is any. For this purpose I would suggest
that you copy </i></b></font><a href=mailto:hubmib@ietf.org><font size=2 color=blue face="Arial"><b><i><u>hubmib@ietf.org</u></i></b></font></a><font size=2 color=blue face="Arial"><b><i>
on further mails on this subject. </i></b></font>
<br><font size=3>&nbsp;</font>
<br><font size=2 color=blue face="Arial"><b><i>Please also copy David Kessens.
As I am wearing both AD and hubmib chair hats, it's better to have both
ADs looking at this. </i></b></font>
<br><font size=3>&nbsp;</font>
<br><font size=2 color=blue face="Arial"><b><i>Dan</i></b></font>
<br><font size=3>&nbsp;</font>
<br><font size=3>&nbsp;</font>
<br><font size=3>&nbsp;</font>
<br><font size=3>&nbsp;</font>
<br><font size=3>&nbsp;</font>
<br><font size=3>&nbsp;</font>
<br>
<br>
<hr><font size=2 face="Tahoma"><b>From:</b> Menachem.Dodge@ecitele.com
[mailto:Menachem.Dodge@ecitele.com] <b><br>
Sent:</b> Thursday, August 31, 2006 3:08 PM<b><br>
To:</b> adslmib@ietf.org<b><br>
Cc:</b> EdwardB@actelis.com; narendranath.nair@wipro.com<b><br>
Subject:</b> RE: [Adslmib] Re: Liaison to DSL Forum</font><font size=3><br>
</font>
<br><font size=2 face="sans-serif"><br>
It seems that there is agreement for a common MIB that will hold the common
information and will then reference 3 specific MIBs</font><font size=3>
</font><font size=2 face="sans-serif"><br>
for the ATM, Ethernet and TDIM specific parameters.</font><font size=3>
<br>
</font><font size=2 face="sans-serif"><br>
Unless I hear something to the contrary, I will draft a charter and present
it on the mailing list early next week.</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
Best Regards,</font><font size=3> </font><font size=2 face="sans-serif"><br>
Menachem</font><font size=3> <br>
<br>
<br>
</font>
<table width=100%>
<tr valign=top>
<td width=26%><font size=1 face="sans-serif"><b>&lt;narendranath.nair@wipro.com&gt;</b>
</font>
<p><font size=1 face="sans-serif">31/08/2006 14:07</font><font size=3>
</font>
<td width=73%>
<br>
<table width=100%>
<tr valign=top>
<td width=13%>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td width=86%><font size=1 face="sans-serif">&lt;EdwardB@actelis.com&gt;,
&lt;frank.van_der_putten@alcatel.be&gt;, &lt;Menachem.Dodge@ecitele.com&gt;</font><font size=3>
</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">adslmib@ietf.org</font><font size=3>
</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">RE: [Adslmib] Re: Liaison to DSL Forum</font></table>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=49%>
<td width=50%></table>
<br></table>
<br><font size=3><br>
<br>
</font><font size=2 color=#000080 face="Arial"><br>
I am also in agreement with having a common MIB and then specific ones
based on the L2 technology type.</font><font size=3> </font><font size=2 color=#000080 face="Arial"><br>
 </font><font size=3>&nbsp;</font><font size=2 color=#000080 face="Arial"><br>
Regards</font><font size=3> </font><font size=2 color=#000080 face="Arial"><br>
Naren</font><font size=3> </font><font size=2 color=#000080 face="Arial"><br>
 </font><font size=3>&nbsp;</font>
<div align=center>
<br><font size=3><br>
</font>
<hr></div>
<br><font size=2 face="Tahoma"><b><br>
From:</b> Edward Beili [mailto:EdwardB@actelis.com] <b><br>
Sent:</b> Thursday, August 31, 2006 4:20 PM<b><br>
To:</b> frank.van_der_putten@alcatel.be; Menachem.Dodge@ecitele.com<b><br>
Cc:</b> adslmib@ietf.org<b><br>
Subject:</b> RE: [Adslmib] Re: Liaison to DSL Forum</font><font size=3>
</font><font size=3 face="Times New Roman"><br>
 </font><font size=3>&nbsp;</font><font size=2 color=blue face="Arial"><br>
I agree with Frank, there should be a separate MIB for each G.Bond specification.</font><font size=3>
</font><font size=3 face="Times New Roman"><br>
 </font><font size=3>&nbsp;</font><font size=2 color=blue face="Arial"><br>
The ifAvailableStackTable and ifStackTable (with their inverse counterparts)
are of course common for all 3 MIBs.</font><font size=3> </font><font size=3 face="Times New Roman"><br>
 </font><font size=3>&nbsp;</font><font size=2 color=blue face="Arial"><br>
We could create a common MIB for all 3 specifications, providing G.Bond
overview, referencing 3 specific MIBs and may be even providing some common
objects in a MIB, for example LowBandwidth trap etc.</font><font size=3>
</font><font size=3 face="Times New Roman"><br>
 </font><font size=3>&nbsp;</font><font size=2 color=blue face="Arial"><br>
Regards,</font><font size=3> </font><font size=2 color=blue face="Arial"><br>
-E.</font><font size=3> </font><font size=2 face="Tahoma"><br>
-----Original Message-----<b><br>
From:</b> frank.van_der_putten@alcatel.be [mailto:frank.van_der_putten@alcatel.be]<b><br>
Sent:</b> Thursday, August 31, 2006 11:35 AM<b><br>
To:</b> Menachem.Dodge@ecitele.com<b><br>
Cc:</b> adslmib@ietf.org<b><br>
Subject:</b> Re: [Adslmib] Re: Liaison to DSL Forum</font><font size=3>
</font><font size=3 face="Times New Roman"><br>
Menachem,<br>
Liaison is OK.<br>
On the bonding MIB: the three bonding standards each handle different things
(cells, packets,bits).<br>
So I believe the MIBs should be separate as I expect a lot of the managed
objects will be different.<br>
Regards,<br>
Frank<br>
</font><font size=3 color=blue face="Times New Roman"><u><br>
</u></font><font size=3 color=blue><u><br>
</u></font><a href=mailto:Menachem.Dodge@ecitele.com><font size=3 color=blue face="Times New Roman"><u>Menachem.Dodge@ecitele.com</u></font></a><font size=3 face="Times New Roman">
wrote:</font><font size=3><br>
</font><font size=2 face="sans-serif"><br>
<br>
Hello, <br>
<br>
 &nbsp; &nbsp; &nbsp; I haven't received any further feedback on the Liaison,
so I will send it to the DSL Forum.</font><font size=3 face="Times New Roman">
</font><font size=2 face="sans-serif"><br>
<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Regarding xDSL bonding
issue, I believe that:</font><font size=3 face="Times New Roman"> </font><font size=2 face="sans-serif"><br>
<br>
 &nbsp; &nbsp; &nbsp; 1. &nbsp;There is Working Group agreement to base
our work on the three </font><font size=2 face="Arial">ITU-T</font><font size=2 face="sans-serif">
</font><font size=2 face="Arial">specifications: G.998.1 (ATM), G.998.2
(Ethernet) and G.998.3 (TDIM).</font><font size=2 color=blue face="Arial">
</font><font size=2 face="sans-serif"><br>
<br>
 &nbsp; &nbsp; &nbsp; 2. There are differing opinions as to whether there
should be one MIB or 3 separate MIBs to handle the three <br>
cases - ATM, Ethernet, and TDIM.</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="sans-serif"><br>
<br>
 &nbsp; &nbsp; &nbsp; I wish to resolve this issue now, so I would appreciate
if everyone would state their opinion (again).</font><font size=3 face="Times New Roman">
</font><font size=2 face="sans-serif"><br>
<br>
Best Regards,</font><font size=3 face="Times New Roman"> </font><font size=2 face="sans-serif"><br>
Menachem </font><font size=3 face="Times New Roman"><br>
<br>
</font>
<p>
<table width=100%>
<tr valign=top>
<td width=56%><font size=1 face="sans-serif"><b>Menachem Dodge/ECI Telecom</b>
</font>
<p><font size=1 face="sans-serif">28/08/2006 19:02</font><font size=3 face="Times New Roman">
</font>
<td width=43%>
<br>
<table width=100%>
<tr valign=top>
<td width=27%>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td width=72%><a href=mailto:adslmib@ietf.org><font size=1 color=blue face="sans-serif"><u>adslmib@ietf.org</u></font></a><font size=3 face="Times New Roman">
</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=3 face="Times New Roman">&nbsp;</font><font size=3> </font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Liaison to DSL Forum</font></table>
<br><font size=3 face="Times New Roman"><br>
 </font><font size=3>&nbsp;</font>
<p>
<br>
<table width=100%>
<tr valign=top>
<td width=61%><font size=3 face="Times New Roman">&nbsp;</font><font size=3>
</font>
<td width=38%><font size=3 face="Times New Roman">&nbsp;</font></table>
<br></table>
<p><font size=3 face="Times New Roman"><br>
</font><font size=2 face="sans-serif"><br>
<br>
Hi,</font><font size=3 face="Times New Roman"> </font><font size=2 face="sans-serif"><br>
<br>
 &nbsp; &nbsp; &nbsp; I have added an additional paragraph informing the
DSL Forum of our progress on the VDSL2 MIB (as per the charter). Let me
know</font><font size=3 face="Times New Roman"> </font><font size=2 face="sans-serif"><br>
if you have any comments, until Wednesday 30th August.</font><font size=3 face="Times New Roman">
<br>
<br>
<br>
<br>
</font><font size=2 face="sans-serif"><br>
<br>
 &nbsp; &nbsp; &nbsp; ==========================</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="sans-serif"><br>
<br>
 &nbsp; &nbsp; &nbsp; Regarding the xDSL Bonding, I have several volunteers
for editors of the document(s) but I need to know if there is anyone <br>
prepared to review the document. Please let me know (privately if you wish)
whether you are willing to review the document. It would be helpful</font><font size=3 face="Times New Roman">
</font><font size=2 face="sans-serif"><br>
to know if there is anyone who will be implementing the MIB as well. <br>
<br>
 &nbsp; &nbsp; &nbsp; Once I have this, the following steps are required:</font><font size=3 face="Times New Roman">
</font><font size=2 face="sans-serif"><br>
<br>
 &nbsp; &nbsp; &nbsp; 1. I will put forward a modified charter for approval
by the Working Group.</font><font size=3 face="Times New Roman"> </font><font size=2 face="sans-serif"><br>
 &nbsp; &nbsp; &nbsp; 2. Once approved by the Working Group, I will send
the new charter text to the AD, Dan Romascanu, requesting that he brings
the</font><font size=3 face="Times New Roman"> </font><font size=2 face="sans-serif"><br>
charter to the IESG for approval.</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="sans-serif"><br>
<br>
 &nbsp; &nbsp; &nbsp; ========================</font><font size=3 face="Times New Roman">
</font><font size=2 face="sans-serif"><br>
<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Regarding the Vdsl2 draft,
I would like to see some review, comments, feedback ....</font><font size=3 face="Times New Roman">
</font><font size=2 face="sans-serif"><br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
<br>
Best Regards,</font><font size=3 face="Times New Roman"> </font><font size=2 face="sans-serif"><br>
Menachem </font>
<div align=center>
<br><font size=2 face="Courier New"><br>
<br>
</font><font size=3><br>
</font>
<hr><font size=2 face="Courier New"><br>
</font></div>
<br><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
Subject: Response To Your Liaison on WT-129.</font><font size=3> </font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
Date: &nbsp;28th August, 2006.</font><font size=3> </font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
To: &nbsp; &nbsp;Gavin Young, <br>
 &nbsp; &nbsp; &nbsp; DSL Forum Technical Committee Chair</font><font size=3>
</font><font size=2 face="Courier New"><br>
 &nbsp; &nbsp; &nbsp; &quot;Gavin Young&quot; </font><a href=mailto:gyoung@dslforum.org><font size=2 color=blue face="Courier New"><u>&lt;gyoung@dslforum.org&gt;</u></font></a><font size=3>
</font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
 &nbsp; &nbsp; &nbsp; Peter Adams, <br>
 &nbsp; &nbsp; &nbsp; DSL Forum Operations and Network Management Working
Group Chair</font><font size=3> </font><font size=2 face="Courier New"><br>
 &nbsp; &nbsp; &nbsp; &quot;Peter Adams&quot; </font><a href=mailto:p.f.adams@btopenworld.com><font size=2 color=blue face="Courier New"><u>&lt;p.f.adams@btopenworld.com&gt;</u></font></a><font size=3>
</font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
Cc: &nbsp; &nbsp;IETF </font><a href=mailto:statements@ietf.org><font size=2 color=blue face="Courier New"><u>statements@ietf.org</u></font></a><font size=3>
</font><font size=2 face="Courier New"><br>
 &nbsp; &nbsp; &nbsp; </font><a href=mailto:IAB@ietf.org><font size=2 color=blue face="Courier New"><u>IAB@ietf.org</u></font></a><font size=3>
</font><font size=2 face="Courier New"><br>
 &nbsp; &nbsp; &nbsp; &nbsp;<br>
 &nbsp; &nbsp; &nbsp; Loa Andersson</font><font size=3> </font><font size=2 face="Courier New"><br>
 &nbsp; &nbsp; &nbsp; &quot;Loa Andersson&quot; </font><a href=mailto:loa@pi.se><font size=2 color=blue face="Courier New"><u>&lt;loa@pi.se&gt;</u></font></a><font size=3>
</font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
 &nbsp; &nbsp; &nbsp; Dan Romascanu</font><font size=3> </font><font size=2 face="Courier New"><br>
 &nbsp; &nbsp; &nbsp; Operations and Management Area Director</font><font size=3>
</font><font size=2 face="Courier New"><br>
 &nbsp; &nbsp; &nbsp; &quot;Romascanu, Dan&quot; </font><a href=mailto:dromasca@avaya.com><font size=2 color=blue face="Courier New"><u>&lt;dromasca@avaya.com&gt;</u></font></a><font size=3>
</font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
 &nbsp; &nbsp; &nbsp; Michael Sneed</font><font size=3> </font><font size=2 face="Courier New"><br>
 &nbsp; &nbsp; &nbsp; IETF ADSL MIB Working Group Co-Chair</font><font size=3>
</font><font size=2 face="Courier New"><br>
 &nbsp; &nbsp; &nbsp; &quot;Michael Sneed&quot; </font><a href=mailto:sneedmike@hotmail.com><font size=2 color=blue face="Courier New"><u>sneedmike@hotmail.com</u></font></a><font size=3>
</font><font size=2 face="Courier New"><br>
 &nbsp; &nbsp; &nbsp; </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
From: &nbsp;IETF ADSL MIB Working Group</font><font size=3> </font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
Response &nbsp;contact: &nbsp; Menachem Dodge</font><font size=3> </font><font size=2 face="Courier New"><br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp;IETF ADSL MIB Working Group Co-Chair</font><font size=3> </font><font size=2 face="Courier New"><br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp;&quot;Menachem Dodge&quot; </font><a href=mailto:menachem.dodge@ecitele.com><font size=2 color=blue face="Courier New"><u>&lt;menachem.dodge@ecitele.com&gt;</u></font></a><font size=3>
</font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
Technical contact: &nbsp; &nbsp; &nbsp;&quot;Menachem Dodge&quot; </font><a href=mailto:menachem.dodge@ecitele.com><font size=2 color=blue face="Courier New"><u>&lt;menachem.dodge@ecitele.com&gt;</u></font></a><font size=3>
</font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
PURPOSE: Response</font><font size=3> </font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
Subject: Response To Your Liaison on WT-129.</font><font size=3> </font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
Dear Gavin and Peter,</font><font size=3> </font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
 &nbsp; &nbsp; &nbsp;Thank you for your liaison and WT-129 Version 3.0.
We would be very grateful if</font><font size=3> </font><font size=2 face="Courier New"><br>
you would continue to keep us informed of any changes to this Working Text
document.</font><font size=3> </font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
 &nbsp; &nbsp; &nbsp;As I informed you in February this year, work has
begun on development of a MIB <br>
for DSL (ADSL, ADSL2, ADSL2+ and VDSL2) lines. This work has progressed
and the latest draft</font><font size=3> </font><font size=2 face="Courier New"><br>
can be found at </font><a href="http://www.ietf.org/internet-drafts/draft-ietf-adslmib-vdsl2-01.txt"><font size=2 color=blue face="Courier New"><u>http://www.ietf.org/internet-drafts/draft-ietf-adslmib-vdsl2-01.txt</u></font></a><font size=2 face="Courier New">.
We would <br>
be most pleased, if you would inform us of any feedback that the DSL Forum
may have on this <br>
document.</font><font size=3> </font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
 &nbsp; &nbsp; &nbsp;We would like to raise the issue of xDSL Bonding,
as defined by the ITU-T documents</font><font size=3> </font><font size=2 face="Courier New"><br>
 G.998.1, G.998.2 and G.998.3. &nbsp;The management of xDSL Bonded lines
has currently not been <br>
addressed, by the DSL Forum. The IETF ADSL MIB Working Group believes that
this issue is important</font><font size=3> </font><font size=2 face="Courier New"><br>
and would be very pleased if the DSL Forum Operations and Network Management
Working Group</font><font size=3> </font><font size=2 face="Courier New"><br>
would address this issue and provide a management framework for xDSL Bonding.</font><font size=3>
</font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
 &nbsp; &nbsp; &nbsp;Yours Sincerely,</font><font size=3> </font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
 &nbsp; &nbsp; &nbsp;Menachem Dodge</font><font size=3> </font><font size=2 face="Courier New"><br>
 &nbsp; &nbsp; &nbsp; &nbsp;IETF ADSL MIB Working Group Co-Chair</font><font size=3>
</font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
 &nbsp; &nbsp; &nbsp;</font>
<div align=center>
<br><font size=2 face="Courier New"><br>
<br>
</font><font size=3><br>
</font>
<hr><font size=2 face="Courier New"><br>
</font></div>
<br><font size=2 face="Courier New"><br>
 </font><font size=3>&nbsp;</font><font size=2 face="Courier New"><br>
_______________________________________________</font><font size=3> </font><font size=2 face="Courier New"><br>
Adslmib mailing list</font><font size=3> </font><font size=3 color=blue><u><br>
</u></font><a href=mailto:Adslmib@ietf.org><font size=2 color=blue face="Courier New"><u>Adslmib@ietf.org</u></font></a><font size=3>
</font><font size=3 color=blue><u><br>
</u></font><a href=https://www1.ietf.org/mailman/listinfo/adslmib><font size=2 color=blue face="Courier New"><u>https://www1.ietf.org/mailman/listinfo/adslmib</u></font></a><font size=3>
</font><font size=2 face="Courier New"><br>
 &nbsp;</font><font size=2><tt>_______________________________________________<br>
Adslmib mailing list<br>
Adslmib@ietf.org<br>
https://www1.ietf.org/mailman/listinfo/adslmib</tt></font><font size=3><br>
</font><font size=2><tt>_______________________________________________<br>
Adslmib mailing list<br>
Adslmib@ietf.org<br>
https://www1.ietf.org/mailman/listinfo/adslmib<br>
</tt></font>
<br>
--=_alternative 0052873EC22571DE_=--


--===============0647306790==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0647306790==--




From adslmib-bounces@ietf.org Sun Sep 03 11:20:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GJtld-00039U-Jp; Sun, 03 Sep 2006 11:20:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GJtlc-00031c-T7; Sun, 03 Sep 2006 11:20:12 -0400
Received: from ilsmtp01.ecitele.com ([147.234.1.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GJtlb-0004j5-79; Sun, 03 Sep 2006 11:20:12 -0400
To: adslmib@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.3 September 14, 2004
Message-ID: <OFAD7893FC.F415370C-ONC22571DE.004E9A45-C22571DE.00543E2F@ecitele.com>
From: Menachem.Dodge@ecitele.com
Date: Sun, 3 Sep 2006 18:20:08 +0300
X-MIMETrack: Serialize by Router on ILSMTP01/ECI Telecom(Release 6.5.3FP1 |
	December 22, 2004) at 09/03/2006 18:28:49
Content-Type: multipart/mixed; boundary="=_mixed 00543E27C22571DE_="
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Cc: David Kessens <david.kessens@nokia.com>, hubmib@ietf.org
Subject: [Adslmib] xDsl Bonding
X-BeenThere: adslmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ADSLMIB <adslmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/adslmib>,
	<mailto:adslmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:adslmib@ietf.org>
List-Help: <mailto:adslmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/adslmib>,
	<mailto:adslmib-request@ietf.org?subject=subscribe>
Errors-To: adslmib-bounces@ietf.org

--=_mixed 00543E27C22571DE_=
Content-Type: multipart/alternative;
	boundary="=_alternative 00543E27C22571DE_="


--=_alternative 00543E27C22571DE_=
Content-Type: text/plain; charset="US-ASCII"

Hi All,

        I would like to thank Edward Beili, Naren Nair and Moti 
Morgenstern for agreeing to work as editors on the xDSL Bonding documents.
Many thanks as well to Clay Sikes, Umberto Bonollo and Scott Baillie for 
agreeing to act as reviewers of these documents.

        I am attaching the draft of the updated charter. Please provide 
your comments.




        Due to the status of the G.997.1 and WT-129, I wish to allow 
additional time before the VDSL2 document goes to Last Call. This
will allow these documents to be finalised before the work on the VDSL2 
document is completed. I hope that this change is acceptable.
I am expecting reviews from Clay, Naren and Veena on the VDSL2 document 
and thank them for their efforts.

 

Best Regards,
Menachem 

--=_alternative 00543E27C22571DE_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi All,</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; I
would like to thank Edward Beili, Naren Nair and Moti Morgenstern for agreeing
to work as editors on the xDSL Bonding documents.</font>
<br><font size=2 face="sans-serif">Many thanks as well to Clay Sikes, Umberto
Bonollo and Scott Baillie for agreeing to act as reviewers of these documents.</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; I
am attaching the draft of the updated charter. Please provide your comments.</font>
<br>
<br>
<br>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Due
to the status of the G.997.1 and WT-129, I wish to allow additional time
before the VDSL2 document goes to Last Call. This</font>
<br><font size=2 face="sans-serif">will allow these documents to be finalised
before the work on the VDSL2 document is completed. I hope that this change
is acceptable.</font>
<br><font size=2 face="sans-serif">I am expecting reviews from Clay, Naren
and Veena on the VDSL2 document and thank them for their efforts.</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br>
<br><font size=2 face="sans-serif">Best Regards,</font>
<br><font size=2 face="sans-serif">Menachem <br>
</font>
--=_alternative 00543E27C22571DE_=--
--=_mixed 00543E27C22571DE_=
Content-Type: text/plain; name="charter.txt"
Content-Disposition: attachment; filename="charter.txt"
Content-Transfer-Encoding: quoted-printable


The working group will define:
1.  A set of managed objects to be used for
    management of newer versions of Digital Subscriber Line (xDSL) as=20
    defined in ITU-T Recommendation G.997.1 (02/2006).

2. A set of managed objects to handle the bonding of xDSL lines according to
    the ITU-T Recommendations G.998.1 (ATM), G.998.2 (Ethernet) and=20
    G.998.3 (TDIM). A common MIB will be developed to handle the common
    objects and three specific MIBs will be developed to handle the three s=
eparate=20
    layer-2 technologies. Use will be made of the ifStack and ifInvStack Ta=
bles defined=20
    in RFC 2863 and RFC 2864 respectively. Use will also be made of the=20
    ifAvailableStack and ifInvAvailableStack tables as defined by the Hubmi=
b WG.

The MIB defined by this group will be generated using SMIv2, will be
consistent with the SNMP management framework, and will describe the
relationship of the objects defined to existing MIBs such as those
described in other work products of this Working Group, the interfaces
MIB, and the AToM MIB.

The working group will consider the input of the DSL forum and the ITU
in the definition of these MIBs.



Goals and Milestones
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


 =20
Nov 2006    Initial draft of all four xDsl bonding MIBs (1 Common and 3 spe=
cific MIB drafts).
DEC 2006    Inform the ITU-T and DSL Forum that work has begun on the xDSL =
Bonding MIBs.
Dec 2006    Complete WG last call on VDSL2 MIB.
Jan 2006    Submit VDSL2 MIB to IESG for consideration as Proposed Standard.
Jan 2007    Updated draft for all four xDsl bonding MIBs.
Feb 2007    Inform the ITU-T and DSL Forum of the progress on the xDSL Bond=
ing MIBs.
Mar 2007    Complete WG last call on the four xDsl bonding MIBs.
Apr 2007    Submit the four xDsl bonding MIBs to IESG for consideration as =
a Proposed Standard.
May 2007    Recharter or close down.

--=_mixed 00543E27C22571DE_=
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--=_mixed 00543E27C22571DE_=--




From adslmib-bounces@ietf.org Thu Sep 07 09:45:44 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLKBy-0001nC-Am; Thu, 07 Sep 2006 09:45:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLKBx-0001n4-16; Thu, 07 Sep 2006 09:45:17 -0400
Received: from ilsmtp01.ecitele.com ([147.234.1.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GLKBv-0005iR-CE; Thu, 07 Sep 2006 09:45:16 -0400
In-Reply-To: <OFAD7893FC.F415370C-ONC22571DE.004E9A45-C22571DE.00543E2F@LocalDomain>
To: adslmib@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.3 September 14, 2004
Message-ID: <OF2FB97354.09BCFFC2-ONC22571E2.004B0153-C22571E2.004B8B16@ecitele.com>
From: Menachem.Dodge@ecitele.com
Date: Thu, 7 Sep 2006 16:45:08 +0300
X-MIMETrack: Serialize by Router on ILSMTP01/ECI Telecom(Release 6.5.3FP1 |
	December 22, 2004) at 09/07/2006 16:53:53
Content-Type: multipart/mixed; boundary="=_mixed 004B8B0DC22571E2_="
X-Spam-Score: 0.3 (/)
X-Scan-Signature: bf422c85703d3d847fb014987125ac48
Cc: David Kessens <david.kessens@nokia.com>, hubmib@ietf.org
Subject: [Adslmib] Re: xDsl Bonding
X-BeenThere: adslmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ADSLMIB <adslmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/adslmib>,
	<mailto:adslmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:adslmib@ietf.org>
List-Help: <mailto:adslmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/adslmib>,
	<mailto:adslmib-request@ietf.org?subject=subscribe>
Errors-To: adslmib-bounces@ietf.org

--=_mixed 004B8B0DC22571E2_=
Content-Type: multipart/alternative;
	boundary="=_alternative 004B8B0DC22571E2_="


--=_alternative 004B8B0DC22571E2_=
Content-Type: text/plain; charset="US-ASCII"

Hi All,

I have not received any comments regarding the proposed charter. 

If there is no response until Tuesday 12th September, I will assume that 
everyone agrees to the text and proceed with the re-charter.

Best Regards,
Menachem Dodge




Menachem Dodge/ECI Telecom 
03/09/2006 18:20

To
adslmib@ietf.org
cc
David Kessens <david.kessens@nokia.com>, "Romascanu, Dan \(Dan\)" 
<dromasca@avaya.com>, hubmib@ietf.org
Subject
xDsl Bonding





Hi All,

        I would like to thank Edward Beili, Naren Nair and Moti 
Morgenstern for agreeing to work as editors on the xDSL Bonding documents.
Many thanks as well to Clay Sikes, Umberto Bonollo and Scott Baillie for 
agreeing to act as reviewers of these documents.

        I am attaching the draft of the updated charter. Please provide 
your comments.




        Due to the status of the G.997.1 and WT-129, I wish to allow 
additional time before the VDSL2 document goes to Last Call. This
will allow these documents to be finalised before the work on the VDSL2 
document is completed. I hope that this change is acceptable.
I am expecting reviews from Clay, Naren and Veena on the VDSL2 document 
and thank them for their efforts.

 

Best Regards,
Menachem 


--=_alternative 004B8B0DC22571E2_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi All,</font>
<br>
<br><font size=2 face="sans-serif">I have not received any comments regarding
the proposed charter. </font>
<br>
<br><font size=2 face="sans-serif">If there is no response until Tuesday
12th September, I will assume that everyone agrees to the text and proceed
with the re-charter.</font>
<br>
<br><font size=2 face="sans-serif">Best Regards,</font>
<br><font size=2 face="sans-serif">Menachem Dodge<br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Menachem Dodge/ECI Telecom</b>
</font>
<p><font size=1 face="sans-serif">03/09/2006 18:20</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">adslmib@ietf.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">David Kessens &lt;david.kessens@nokia.com&gt;,
&quot;Romascanu, Dan \(Dan\)&quot; &lt;dromasca@avaya.com&gt;, hubmib@ietf.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">xDsl Bonding</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br><font size=2 face="sans-serif">Hi All,</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; I
would like to thank Edward Beili, Naren Nair and Moti Morgenstern for agreeing
to work as editors on the xDSL Bonding documents.</font>
<br><font size=2 face="sans-serif">Many thanks as well to Clay Sikes, Umberto
Bonollo and Scott Baillie for agreeing to act as reviewers of these documents.</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; I
am attaching the draft of the updated charter. Please provide your comments.</font>
<br>
<br>
<br>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Due
to the status of the G.997.1 and WT-129, I wish to allow additional time
before the VDSL2 document goes to Last Call. This</font>
<br><font size=2 face="sans-serif">will allow these documents to be finalised
before the work on the VDSL2 document is completed. I hope that this change
is acceptable.</font>
<br><font size=2 face="sans-serif">I am expecting reviews from Clay, Naren
and Veena on the VDSL2 document and thank them for their efforts.</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br>
<br><font size=2 face="sans-serif">Best Regards,</font>
<br><font size=2 face="sans-serif">Menachem <br>
</font>
<br>
--=_alternative 004B8B0DC22571E2_=--
--=_mixed 004B8B0DC22571E2_=
Content-Type: text/plain; name="charter.txt"
Content-Disposition: attachment; filename="charter.txt"
Content-Transfer-Encoding: quoted-printable


The working group will define:
1.  A set of managed objects to be used for
    management of newer versions of Digital Subscriber Line (xDSL) as=20
    defined in ITU-T Recommendation G.997.1 (02/2006).

2. A set of managed objects to handle the bonding of xDSL lines according to
    the ITU-T Recommendations G.998.1 (ATM), G.998.2 (Ethernet) and=20
    G.998.3 (TDIM). A common MIB will be developed to handle the common
    objects and three specific MIBs will be developed to handle the three s=
eparate=20
    layer-2 technologies. Use will be made of the ifStack and ifInvStack Ta=
bles defined=20
    in RFC 2863 and RFC 2864 respectively. Use will also be made of the=20
    ifAvailableStack and ifInvAvailableStack tables as defined by the Hubmi=
b WG.

The MIB defined by this group will be generated using SMIv2, will be
consistent with the SNMP management framework, and will describe the
relationship of the objects defined to existing MIBs such as those
described in other work products of this Working Group, the interfaces
MIB, and the AToM MIB.

The working group will consider the input of the DSL forum and the ITU
in the definition of these MIBs.



Goals and Milestones
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


 =20
Nov 2006    Initial draft of all four xDsl bonding MIBs (1 Common and 3 spe=
cific MIB drafts).
DEC 2006    Inform the ITU-T and DSL Forum that work has begun on the xDSL =
Bonding MIBs.
Dec 2006    Complete WG last call on VDSL2 MIB.
Jan 2006    Submit VDSL2 MIB to IESG for consideration as Proposed Standard.
Jan 2007    Updated draft for all four xDsl bonding MIBs.
Feb 2007    Inform the ITU-T and DSL Forum of the progress on the xDSL Bond=
ing MIBs.
Mar 2007    Complete WG last call on the four xDsl bonding MIBs.
Apr 2007    Submit the four xDsl bonding MIBs to IESG for consideration as =
a Proposed Standard.
May 2007    Recharter or close down.

--=_mixed 004B8B0DC22571E2_=
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--=_mixed 004B8B0DC22571E2_=--




From adslmib-bounces@ietf.org Fri Sep 08 12:35:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLjKC-0007vl-Oa; Fri, 08 Sep 2006 12:35:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLjKB-0007vX-TD; Fri, 08 Sep 2006 12:35:27 -0400
Received: from co300216-ier2.net.avaya.com ([198.152.13.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GLjKA-0006hC-Fb; Fri, 08 Sep 2006 12:35:27 -0400
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP
	id k88GSMxF009501; Fri, 8 Sep 2006 12:28:23 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 8 Sep 2006 19:35:22 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0B32D0A3@IS0004AVEXU1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: xDsl Bonding
Thread-Index: AcbSg9hrcxK4Vx5OQl2rC+81ictYdAA4KVAg
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: <Menachem.Dodge@ecitele.com>, <adslmib@ietf.org>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.3 (/)
X-Scan-Signature: a0534e6179a1e260079328e8b03c7901
Cc: David Kessens <david.kessens@nokia.com>, hubmib@ietf.org
Subject: [Adslmib] RE: xDsl Bonding
X-BeenThere: adslmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ADSLMIB <adslmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/adslmib>,
	<mailto:adslmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:adslmib@ietf.org>
List-Help: <mailto:adslmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/adslmib>,
	<mailto:adslmib-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0081873161=="
Errors-To: adslmib-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0081873161==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6D364.C7C93AED"

This is a multi-part message in MIME format.

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

Messages on the lines of 'I read, agree and am interested in this work'
are also welcome.=20
=20
Dan
=20
=20
=20


  _____ =20

	From: Menachem.Dodge@ecitele.com
[mailto:Menachem.Dodge@ecitele.com]=20
	Sent: Thursday, September 07, 2006 4:45 PM
	To: adslmib@ietf.org
	Cc: David Kessens; Romascanu, Dan (Dan); hubmib@ietf.org
	Subject: Re: xDsl Bonding
=09
=09

	Hi All,=20
=09
	I have not received any comments regarding the proposed charter.

=09
	If there is no response until Tuesday 12th September, I will
assume that everyone agrees to the text and proceed with the re-charter.

=09
	Best Regards,=20
	Menachem Dodge
=09
=09
=09
=09
Menachem Dodge/ECI Telecom=20

03/09/2006 18:20=20

To
adslmib@ietf.org=20
cc
David Kessens <david.kessens@nokia.com>, "Romascanu, Dan \(Dan\)"
<dromasca@avaya.com>, hubmib@ietf.org=20
Subject
xDsl Bonding

=09



	Hi All,=20
=09
	        I would like to thank Edward Beili, Naren Nair and Moti
Morgenstern for agreeing to work as editors on the xDSL Bonding
documents.=20
	Many thanks as well to Clay Sikes, Umberto Bonollo and Scott
Baillie for agreeing to act as reviewers of these documents.=20
=09
	        I am attaching the draft of the updated charter. Please
provide your comments.=20
=09
=09
=09
=09
	        Due to the status of the G.997.1 and WT-129, I wish to
allow additional time before the VDSL2 document goes to Last Call. This=20
	will allow these documents to be finalised before the work on
the VDSL2 document is completed. I hope that this change is acceptable.=20
	I am expecting reviews from Clay, Naren and Veena on the VDSL2
document and thank them for their efforts.=20
=09
	       =20
=09
	Best Regards,=20
	Menachem=20
=09
=09


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2963" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D544183316-08092006><FONT face=3DArial color=3D#0000ff =

size=3D2><STRONG><EM>Messages on the lines of 'I read, agree and am =
interested in=20
this work' are also welcome. </EM></STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=3D544183316-08092006><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D544183316-08092006><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Dan</FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D544183316-08092006></SPAN>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Menachem.Dodge@ecitele.com=20
  [mailto:Menachem.Dodge@ecitele.com] <BR><B>Sent:</B> Thursday, =
September 07,=20
  2006 4:45 PM<BR><B>To:</B> adslmib@ietf.org<BR><B>Cc:</B> David =
Kessens;=20
  Romascanu, Dan (Dan); hubmib@ietf.org<BR><B>Subject:</B> Re: xDsl=20
  Bonding<BR></FONT><BR></DIV>
  <DIV></DIV><BR><FONT face=3Dsans-serif size=3D2>Hi All,</FONT> =
<BR><BR><FONT=20
  face=3Dsans-serif size=3D2>I have not received any comments regarding =
the proposed=20
  charter. </FONT><BR><BR><FONT face=3Dsans-serif size=3D2>If there is =
no response=20
  until Tuesday 12th September, I will assume that everyone agrees to =
the text=20
  and proceed with the re-charter.</FONT> <BR><BR><FONT =
face=3Dsans-serif=20
  size=3D2>Best Regards,</FONT> <BR><FONT face=3Dsans-serif =
size=3D2>Menachem=20
  Dodge<BR></FONT><BR><BR><BR>
  <TABLE width=3D"100%">
    <TBODY>
    <TR vAlign=3Dtop>
      <TD width=3D"40%"><FONT face=3Dsans-serif size=3D1><B>Menachem =
Dodge/ECI=20
        Telecom</B> </FONT>
        <P><FONT face=3Dsans-serif size=3D1>03/09/2006 18:20</FONT> </P>
      <TD width=3D"59%">
        <TABLE width=3D"100%">
          <TBODY>
          <TR vAlign=3Dtop>
            <TD>
              <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>To</FONT></DIV>
            <TD><FONT face=3Dsans-serif size=3D1>adslmib@ietf.org</FONT> =

          <TR vAlign=3Dtop>
            <TD>
              <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>cc</FONT></DIV>
            <TD><FONT face=3Dsans-serif size=3D1>David Kessens=20
              &lt;david.kessens@nokia.com&gt;, "Romascanu, Dan \(Dan\)"=20
              &lt;dromasca@avaya.com&gt;, hubmib@ietf.org</FONT>=20
          <TR vAlign=3Dtop>
            <TD>
              <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>Subject</FONT></DIV>
            <TD><FONT face=3Dsans-serif size=3D1>xDsl=20
        Bonding</FONT></TR></TBODY></TABLE><BR>
        <TABLE>
          <TBODY>
          <TR vAlign=3Dtop>
            <TD>
            =
<TD></TR></TBODY></TABLE><BR></TR></TBODY></TABLE><BR><BR><FONT=20
  face=3Dsans-serif size=3D2>Hi All,</FONT> <BR><BR><FONT =
face=3Dsans-serif=20
  size=3D2>&nbsp; &nbsp; &nbsp; &nbsp; I would like to thank Edward =
Beili, Naren=20
  Nair and Moti Morgenstern for agreeing to work as editors on the xDSL =
Bonding=20
  documents.</FONT> <BR><FONT face=3Dsans-serif size=3D2>Many thanks as =
well to Clay=20
  Sikes, Umberto Bonollo and Scott Baillie for agreeing to act as =
reviewers of=20
  these documents.</FONT> <BR><BR><FONT face=3Dsans-serif =
size=3D2>&nbsp; &nbsp;=20
  &nbsp; &nbsp; I am attaching the draft of the updated charter. Please =
provide=20
  your comments.</FONT> <BR><BR><BR><BR><BR><FONT face=3Dsans-serif =
size=3D2>&nbsp;=20
  &nbsp; &nbsp; &nbsp; Due to the status of the G.997.1 and WT-129, I =
wish to=20
  allow additional time before the VDSL2 document goes to Last Call. =
This</FONT>=20
  <BR><FONT face=3Dsans-serif size=3D2>will allow these documents to be =
finalised=20
  before the work on the VDSL2 document is completed. I hope that this =
change is=20
  acceptable.</FONT> <BR><FONT face=3Dsans-serif size=3D2>I am expecting =
reviews=20
  from Clay, Naren and Veena on the VDSL2 document and thank them for =
their=20
  efforts.</FONT> <BR><BR><FONT face=3Dsans-serif size=3D2>&nbsp; &nbsp; =
&nbsp;=20
  &nbsp; </FONT><BR><BR><FONT face=3Dsans-serif size=3D2>Best =
Regards,</FONT>=20
  <BR><FONT face=3Dsans-serif size=3D2>Menachem=20
<BR></FONT><BR></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C6D364.C7C93AED--


--===============0081873161==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0081873161==--




From adslmib-bounces@ietf.org Sat Sep 09 02:36:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLwS7-0000zV-N4; Sat, 09 Sep 2006 02:36:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLwS2-0000Nf-2y; Sat, 09 Sep 2006 02:36:26 -0400
Received: from wip-ec-wd.wipro.com ([203.91.193.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GLwLU-0003UT-Uv; Sat, 09 Sep 2006 02:29:43 -0400
Received: from wip-ec-wd.wipro.com (localhost.wipro.com [127.0.0.1])
	by localhost (Postfix) with ESMTP id 5D2D02068D;
	Sat,  9 Sep 2006 11:55:20 +0530 (IST)
Received: from blr-ec-bh02.wipro.com (blr-ec-bh02.wipro.com [10.201.50.92])
	by wip-ec-wd.wipro.com (Postfix) with ESMTP id 37F80205F6;
	Sat,  9 Sep 2006 11:55:20 +0530 (IST)
Received: from BLR-EC-MBX01.wipro.com ([10.201.50.164]) by
	blr-ec-bh02.wipro.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 9 Sep 2006 11:59:26 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Adslmib] RE: xDsl Bonding
Date: Sat, 9 Sep 2006 11:57:28 +0530
Message-ID: <B424DE8774D62944B66658960D4E1C32017E7CF7@BLR-EC-MBX01.wipro.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Adslmib] RE: xDsl Bonding
Thread-Index: AcbSg9hrcxK4Vx5OQl2rC+81ictYdAA4KVAgABzaoBA=
From: <veena.naidu@wipro.com>
To: <dromasca@avaya.com>,
	<Menachem.Dodge@ecitele.com>,
	<adslmib@ietf.org>
X-OriginalArrivalTime: 09 Sep 2006 06:29:26.0743 (UTC)
	FILETIME=[4C428670:01C6D3D9]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 4b21264b25b2584da3ddf2bd579ca48f
Cc: david.kessens@nokia.com, hubmib@ietf.org
X-BeenThere: adslmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ADSLMIB <adslmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/adslmib>,
	<mailto:adslmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:adslmib@ietf.org>
List-Help: <mailto:adslmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/adslmib>,
	<mailto:adslmib-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0115843382=="
Errors-To: adslmib-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0115843382==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6D3D9.4BE07A41"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6D3D9.4BE07A41
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello Romascanu,

=20

Iam very much interested in modeling XDSL bonding .

=20

Regards,

veena

=20

________________________________

From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]=20
Sent: Friday, September 08, 2006 10:05 PM
To: Menachem.Dodge@ecitele.com; adslmib@ietf.org
Cc: David Kessens; hubmib@ietf.org
Subject: [Adslmib] RE: xDsl Bonding

=20

Messages on the lines of 'I read, agree and am interested in this work'
are also welcome.=20

=20

Dan

=20

=20

=20

	=20

=09
________________________________


	From: Menachem.Dodge@ecitele.com
[mailto:Menachem.Dodge@ecitele.com]=20
	Sent: Thursday, September 07, 2006 4:45 PM
	To: adslmib@ietf.org
	Cc: David Kessens; Romascanu, Dan (Dan); hubmib@ietf.org
	Subject: Re: xDsl Bonding

=09
	Hi All,=20
=09
	I have not received any comments regarding the proposed charter.

=09
	If there is no response until Tuesday 12th September, I will
assume that everyone agrees to the text and proceed with the re-charter.

=09
	Best Regards,=20
	Menachem Dodge
=09
=09
=09

Menachem Dodge/ECI Telecom=20

03/09/2006 18:20=20

To

adslmib@ietf.org=20

cc

David Kessens <david.kessens@nokia.com>, "Romascanu, Dan \(Dan\)"
<dromasca@avaya.com>, hubmib@ietf.org=20

Subject

xDsl Bonding

=20

=20

=20

=09
=09
	Hi All,=20
=09
	        I would like to thank Edward Beili, Naren Nair and Moti
Morgenstern for agreeing to work as editors on the xDSL Bonding
documents.=20
	Many thanks as well to Clay Sikes, Umberto Bonollo and Scott
Baillie for agreeing to act as reviewers of these documents.=20
=09
	        I am attaching the draft of the updated charter. Please
provide your comments.=20
=09
=09
=09
=09
	        Due to the status of the G.997.1 and WT-129, I wish to
allow additional time before the VDSL2 document goes to Last Call. This=20
	will allow these documents to be finalised before the work on
the VDSL2 document is completed. I hope that this change is acceptable.=20
	I am expecting reviews from Clay, Naren and Veena on the VDSL2
document and thank them for their efforts.=20
=09
	       =20
=09
	Best Regards,=20
	Menachem=20


------_=_NextPart_001_01C6D3D9.4BE07A41
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-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=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 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:sans-serif;
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Hello =
Romascanu,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Iam very much interested in =
modeling XDSL
bonding .<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Regards,<o:p></o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>veena<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Romascanu, Dan
(Dan) [mailto:dromasca@avaya.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Friday, September =
08, 2006
10:05 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> =
Menachem.Dodge@ecitele.com;
adslmib@ietf.org<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> David Kessens; =
hubmib@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [Adslmib] RE: =
xDsl
Bonding</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p class=3DMsoNormal><em><b><i><font size=3D2 color=3Dblue =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue;font-weight:bold'>=
Messages
on the lines of 'I read, agree and am interested in this work' are also
welcome. </span></font></i></b></em><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><em><b><i><font size=3D2 color=3Dblue =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue;font-weight:bold'>=
Dan</span></font></i></b></em><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<blockquote style=3D'border:none;border-left:solid blue =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>

</span></font></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>
Menachem.Dodge@ecitele.com [mailto:Menachem.Dodge@ecitele.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, September =
07, 2006
4:45 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> adslmib@ietf.org<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> David Kessens; =
Romascanu, Dan
(Dan); hubmib@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: xDsl =
Bonding</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'><br>
</span></font><font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;
font-family:sans-serif'>Hi All,</span></font> <br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>I
have not received any comments regarding the proposed charter. =
</span></font><br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>If
there is no response until Tuesday 12th September, I will assume that =
everyone
agrees to the text and proceed with the re-charter.</span></font> <br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>Best
Regards,</span></font> <br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>Menachem
Dodge<br>
</span></font><br>
<br>
<o:p></o:p></p>

<table class=3DMsoNormalTable border=3D0 cellpadding=3D0 width=3D"100%"
 style=3D'width:100.0%'>
 <tr>
  <td width=3D"40%" valign=3Dtop style=3D'width:40.0%;padding:.75pt =
.75pt .75pt .75pt'>
  <p class=3DMsoNormal><b><font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:
  7.5pt;font-family:sans-serif;font-weight:bold'>Menachem Dodge/ECI =
Telecom</span></font></b><font
  size=3D1 face=3Dsans-serif><span =
style=3D'font-size:7.5pt;font-family:sans-serif'> =
</span></font><o:p></o:p></p>
  <p><font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:7.5pt;font-family:
  sans-serif'>03/09/2006 18:20</span></font> <o:p></o:p></p>
  </td>
  <td width=3D"59%" valign=3Dtop style=3D'width:59.0%;padding:.75pt =
.75pt .75pt .75pt'>
  <table class=3DMsoNormalTable border=3D0 cellpadding=3D0 =
width=3D"100%"
   style=3D'width:100.0%'>
   <tr>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><font =
size=3D1
    face=3Dsans-serif><span =
style=3D'font-size:7.5pt;font-family:sans-serif'>To</span></font><o:p></o=
:p></p>
    </td>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal><font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:
    7.5pt;font-family:sans-serif'>adslmib@ietf.org</span></font> =
<o:p></o:p></p>
    </td>
   </tr>
   <tr>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><font =
size=3D1
    face=3Dsans-serif><span =
style=3D'font-size:7.5pt;font-family:sans-serif'>cc</span></font><o:p></o=
:p></p>
    </td>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal><font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:
    7.5pt;font-family:sans-serif'>David Kessens
    &lt;david.kessens@nokia.com&gt;, &quot;Romascanu, Dan \(Dan\)&quot;
    &lt;dromasca@avaya.com&gt;, hubmib@ietf.org</span></font> =
<o:p></o:p></p>
    </td>
   </tr>
   <tr>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><font =
size=3D1
    face=3Dsans-serif><span =
style=3D'font-size:7.5pt;font-family:sans-serif'>Subject</span></font><o:=
p></o:p></p>
    </td>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal><font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:
    7.5pt;font-family:sans-serif'>xDsl =
Bonding</span></font><o:p></o:p></p>
    </td>
   </tr>
  </table>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>
  <table class=3DMsoNormalTable border=3D0 cellpadding=3D0>
   <tr>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
    style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>
    </td>
    <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
    <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
    style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>
    </td>
   </tr>
  </table>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt'><o:p></o:p></span></font></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'><br>
<br>
</span></font><font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;
font-family:sans-serif'>Hi All,</span></font> <br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>&nbsp;
&nbsp; &nbsp; &nbsp; I would like to thank Edward Beili, Naren Nair and =
Moti
Morgenstern for agreeing to work as editors on the xDSL Bonding =
documents.</span></font>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>Many
thanks as well to Clay Sikes, Umberto Bonollo and Scott Baillie for =
agreeing to
act as reviewers of these documents.</span></font> <br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>&nbsp;
&nbsp; &nbsp; &nbsp; I am attaching the draft of the updated charter. =
Please
provide your comments.</span></font> <br>
<br>
<br>
<br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>&nbsp;
&nbsp; &nbsp; &nbsp; Due to the status of the G.997.1 and WT-129, I wish =
to allow
additional time before the VDSL2 document goes to Last Call. =
This</span></font>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>will
allow these documents to be finalised before the work on the VDSL2 =
document is
completed. I hope that this change is acceptable.</span></font> <br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>I
am expecting reviews from Clay, Naren and Veena on the VDSL2 document =
and thank
them for their efforts.</span></font> <br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>&nbsp;
&nbsp; &nbsp; &nbsp; </span></font><br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>Best
Regards,</span></font> <br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>Menachem
</span></font><o:p></o:p></p>

</blockquote>

</div>

</body>

</html>

------_=_NextPart_001_01C6D3D9.4BE07A41--


--===============0115843382==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0115843382==--




