From Menachem.Dodge@ecitele.com Tue Jan 19 02:56:17 2010 Return-Path: X-Original-To: adslmib@core3.amsl.com Delivered-To: adslmib@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DA4293A68E4 for ; Tue, 19 Jan 2010 02:56:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.739 X-Spam-Level: X-Spam-Status: No, score=-0.739 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id drQjoJu2nsId for ; Tue, 19 Jan 2010 02:56:17 -0800 (PST) Received: from ilptbmg01.ecitele.com (ilptbmg01-out.ecitele.com [147.234.242.234]) by core3.amsl.com (Postfix) with ESMTP id C2FAE3A688F for ; Tue, 19 Jan 2010 02:56:16 -0800 (PST) X-AuditID: 93eaf2e7-b7c38ae000000ed6-88-4b558ec59bd2 Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id 5E.52.03798.5CE855B4; Tue, 19 Jan 2010 12:51:49 +0200 (IST) Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Tue, 19 Jan 2010 12:56:11 +0200 From: Menachem Dodge To: "adslmib@ietf.org" Date: Tue, 19 Jan 2010 12:56:10 +0200 Thread-Topic: Vector of Profiles Thread-Index: AcqY9gJLvFSLUqbwTwyIkagmOsCAwQ== Message-ID: <283DD79798619346BF9B17D7B5035A190107FF1723AB@ILPTMAIL02.ecitele.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_283DD79798619346BF9B17D7B5035A190107FF1723ABILPTMAIL02e_" MIME-Version: 1.0 X-Brightmail-Tracker: AAAAAA== Subject: [Adslmib] Vector of Profiles X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: ADSLMIB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jan 2010 10:56:18 -0000 --_000_283DD79798619346BF9B17D7B5035A190107FF1723ABILPTMAIL02e_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello, I wish to inform the WG that Moti, Scott and Umberto have all agreed to act= as editors of the Vector of Profiles draft. In addition, Frank, Gerd and Peidaoyu have kindly agreed to act as reviewer= s. I am now working on a re-charter proposal which I will post on the mailing = list for WG approval. Best Regards, Menachem --_000_283DD79798619346BF9B17D7B5035A190107FF1723ABILPTMAIL02e_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello,

 

I wish to inform the WG that Moti, Scott and Umberto h= ave all agreed to act as editors of the Vector of Profiles draft.

 

In addition, Frank, Gerd and Peidaoyu have kindly agre= ed to act as reviewers.

 

I am now working on a re-charter proposal which I will= post on the mailing list for WG approval.

 

Best Regards,

Menachem

--_000_283DD79798619346BF9B17D7B5035A190107FF1723ABILPTMAIL02e_-- From Menachem.Dodge@ecitele.com Sun Jan 24 23:20:47 2010 Return-Path: X-Original-To: adslmib@core3.amsl.com Delivered-To: adslmib@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF4533A6782 for ; Sun, 24 Jan 2010 23:20:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.184 X-Spam-Level: X-Spam-Status: No, score=-0.184 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HzqvdhBlzu0m for ; Sun, 24 Jan 2010 23:20:46 -0800 (PST) Received: from ilptbmg01.ecitele.com (ilptbmg01-out.ecitele.com [147.234.242.234]) by core3.amsl.com (Postfix) with ESMTP id A1C803A6767 for ; Sun, 24 Jan 2010 23:20:45 -0800 (PST) X-AuditID: 93eaf2e7-b7c38ae000000ed6-d2-4b5d452f752a Received: from ilptexch01.ecitele.com ( [172.31.244.40]) by ilptbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id 8D.4E.03798.F254D5B4; Mon, 25 Jan 2010 09:15:59 +0200 (IST) Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ilptexch01.ecitele.com ([172.31.244.40]) with mapi; Mon, 25 Jan 2010 09:20:49 +0200 From: Menachem Dodge To: "adslmib@ietf.org" Date: Mon, 25 Jan 2010 09:20:42 +0200 Thread-Topic: Proposed Charter Change - to include VoP Thread-Index: Acqc1mdOTQp0yvfKRT2oTO3IjXny2QAuBZTA Message-ID: <283DD79798619346BF9B17D7B5035A190107FF172BDD@ILPTMAIL02.ecitele.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_283DD79798619346BF9B17D7B5035A190107FF172BDDILPTMAIL02e_" MIME-Version: 1.0 X-Brightmail-Tracker: AAAAAA== Subject: [Adslmib] Proposed Charter Change - to include VoP X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: ADSLMIB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jan 2010 07:20:48 -0000 --_000_283DD79798619346BF9B17D7B5035A190107FF172BDDILPTMAIL02e_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello All, Please review the proposed updated working group charter and milestones (be= low). All comments and feedback are appreciated. =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 The working group will define: 1. 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 G.998.3 (TDIM). A common MIB module will be developed to handle the common objects and three specific MIB modules will be developed to handle the three separate layer-2 technologies. Use will be made of the ifStack and ifInvStack Tables defined in RFC 2863 and RFC 2864 respectively. Use will also be made of the ifAvailableStack and ifInvAvailableStack tables as defined by the Hubmib WG. 2. The working group will develop a set of managed objects as an optional e= xtension to RFC 5650 that shall provide an alternative approach, known as t= he "Vector of Profiles", for the configuration of DSL lines. The Vector of = Profiles MIB will be based on the Broadband Forum TR-165 document. The MIB modules 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, the Ethernet MIB modules and the AToM MIB. The working group will consider the input of the Broadband forum and the IT= U in the definition of these MIBs. Goals and Milestones: Feb 2010 Initial Vector of Profiles draft to be accepted by the Working Gro= up. Apr 2010 Post Vector of Profiles Draft version 01. Jun 2010 Revise the draft and post vector of Profiles draft version 02. Jul 2010 Working Group review of the Vector of Profiles draft. Aug 2010 Post Vector of Profiles Draft version 03. Sep 2010 Present the Vdsl2 document to the IESG. Thank you kindly, Menachem Dodge --_000_283DD79798619346BF9B17D7B5035A190107FF172BDDILPTMAIL02e_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

Hello All,

 

Please review the proposed updated working group chart= er and milestones (below).

 =

 All comments and feedback are appreciated. =

 

=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

 

The working group will define: 

 

1. A set of managed objects to handle the bonding of x= DSL lines 

according to the ITU-T Recommendations G.998.1 (ATM), G.998.2 (Ethernet)

and G.998.3 (TDIM). A common MIB module will be develo= ped to handle the

common objects and three specific MIB modules will be developed to

handle the three separate layer-2 technologies. Use wi= ll be made of the

ifStack and ifInvStack Tables defined in RFC 2863 and = RFC 2864

respectively. Use will also be made of the ifAvailable= Stack and

ifInvAvailableStack tables as defined by the Hubmib WG= .

 

 

2. The working group will develop a set of managed obj= ects as an optional extension to RFC 5650 that shall provide an alternative approach, known as the "Vector of Profiles", for the configuratio= n of DSL lines. The Vector of Profiles MIB will be based on the Broadband Forum TR-165 document.

 

 

 

The MIB modules defined by this group will be generate= d using SMIv2, 

will be consistent with the SNMP management framework,= and will describe

the relationship of the objects defined to existing MI= Bs such as those

described in other work products of this Working Group= , the interfaces

MIB, the Ethernet MIB modules and the AToM MIB. <= /o:p>

 

The working group will consider the input of the Broad= band forum and the ITU

in the definition of these MIBs.

 

Goals and Milestones:

 

Feb 2010 Initial Vector of Profiles draft to be accept= ed by the Working Group.

Apr 2010 Post Vector of Profiles Draft version 01.

Jun 2010 Revise the draft and post vector of Profiles = draft version 02.

Jul  2010  Working Group review of the Vecto= r of Profiles draft.

Aug 2010 Post Vector of Profiles Draft version 03.

Sep 2010 Present the Vdsl2 document to the IESG.<= /o:p>

 

Thank you kindly,

Menachem Dodge

 

--_000_283DD79798619346BF9B17D7B5035A190107FF172BDDILPTMAIL02e_-- From dromasca@avaya.com Mon Jan 25 03:40:20 2010 Return-Path: X-Original-To: adslmib@core3.amsl.com Delivered-To: adslmib@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DAEB43A6980 for ; Mon, 25 Jan 2010 03:40:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.949 X-Spam-Level: X-Spam-Status: No, score=-2.949 tagged_above=-999 required=5 tests=[AWL=-0.351, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3k03sqZDsKex for ; Mon, 25 Jan 2010 03:40:19 -0800 (PST) Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id A37923A65A6 for ; Mon, 25 Jan 2010 03:40:19 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.49,338,1262581200"; d="scan'208,217";a="201946907" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 25 Jan 2010 06:40:23 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.11]) by co300216-co-erhwest-out.avaya.com with ESMTP; 25 Jan 2010 06:40:23 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA9DB3.23DAED56" Date: Mon, 25 Jan 2010 12:40:05 +0100 Message-ID: In-Reply-To: <283DD79798619346BF9B17D7B5035A190107FF172BDD@ILPTMAIL02.ecitele.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Adslmib] Proposed Charter Change - to include VoP Thread-Index: Acqc1mdOTQp0yvfKRT2oTO3IjXny2QAuBZTAAAhhJAA= References: <283DD79798619346BF9B17D7B5035A190107FF172BDD@ILPTMAIL02.ecitele.com> From: "Romascanu, Dan (Dan)" To: "Menachem Dodge" , Subject: Re: [Adslmib] Proposed Charter Change - to include VoP X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: ADSLMIB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jan 2010 11:40:20 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01CA9DB3.23DAED56 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Comments and Questions:=20 =20 - do you plan for this text to replace the current charter? if so, can you please revise the whole text, including the headers. It's a good opportunity to take out the names of the editors and advisors who are not active any longer and replace them with the current ones - be more specific on what SG in the ITU-T the WG needs to coordinate with - 'Jul 2010 Working Group review of the Vector of Profiles draft.' do you mean WG last call? - 'Sep 2010 Present the Vdsl2 document to the IESG.' is this Vsdl2 or vector of profiles MIB? is this for consideration as Proposed Standard?=20 =20 Thanks and Regards, =20 Dan =20 ________________________________ From: adslmib-bounces@ietf.org [mailto:adslmib-bounces@ietf.org] On Behalf Of Menachem Dodge Sent: Monday, January 25, 2010 9:21 AM To: adslmib@ietf.org Subject: [Adslmib] Proposed Charter Change - to include VoP =09 =09 =20 Hello All, =20 Please review the proposed updated working group charter and milestones (below). =20 All comments and feedback are appreciated.=20 =20 = =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 The working group will define: =20 =20 1. 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 G.998.3 (TDIM). A common MIB module will be developed to handle the common objects and three specific MIB modules will be developed to handle the three separate layer-2 technologies. Use will be made of the ifStack and ifInvStack Tables defined in RFC 2863 and RFC 2864 respectively. Use will also be made of the ifAvailableStack and ifInvAvailableStack tables as defined by the Hubmib WG. [[DR]] =20 =20 =20 2. The working group will develop a set of managed objects as an optional extension to RFC 5650 that shall provide an alternative approach, known as the "Vector of Profiles", for the configuration of DSL lines. The Vector of Profiles MIB will be based on the Broadband Forum TR-165 document.=20 =20 =20 =20 The MIB modules defined by this group will be generated using SMIv2, =20 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, the Ethernet MIB modules and the AToM MIB.=20 =20 The working group will consider the input of the Broadband forum and the ITU=20 in the definition of these MIBs. =20 Goals and Milestones: =20 Feb 2010 Initial Vector of Profiles draft to be accepted by the Working Group. Apr 2010 Post Vector of Profiles Draft version 01. Jun 2010 Revise the draft and post vector of Profiles draft version 02. Jul 2010 Working Group review of the Vector of Profiles draft. Aug 2010 Post Vector of Profiles Draft version 03. Sep 2010 Present the Vdsl2 document to the IESG. =20 Thank you kindly, Menachem Dodge =20 ------_=_NextPart_001_01CA9DB3.23DAED56 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Comments and  Questions:
 
- do=20 you plan for this text to replace the current charter? if so, can you = please=20 revise the whole text, including the headers. It's a good opportunity to = take=20 out the names of the editors and advisors who are not active any longer = and=20 replace them with the current ones
- be=20 more specific on what SG in the ITU-T the WG needs to coordinate=20 with
-=20 'Jul  2010  Working Group review of the = Vector of=20 Profiles draft.' do you mean WG last call?
- 'Sep=20 2010 Present the Vdsl2 document to the IESG.'   is this Vsdl2 or vector of profiles MIB? = is this for=20 consideration as Proposed Standard?
 
Thanks=20 and Regards,
 
Dan
 


From: adslmib-bounces@ietf.org=20 [mailto:adslmib-bounces@ietf.org] On Behalf Of Menachem=20 Dodge
Sent: Monday, January 25, 2010 9:21 AM
To:=20 adslmib@ietf.org
Subject: [Adslmib] Proposed Charter Change = - to=20 include VoP

 

Hello All,

 

Please review the proposed updated working group = charter=20 and milestones (below).

 

 All comments and feedback are appreciated.=20

 

=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

 

The working group will define:  =

 

1. A set of managed objects to handle the bonding = of xDSL=20 lines 

according to the ITU-T Recommendations G.998.1 = (ATM),=20 G.998.2 (Ethernet)

and G.998.3 (TDIM). A common MIB module will be = developed=20 to handle the

common objects and three specific MIB modules = will be=20 developed to

handle the three separate layer-2 technologies. = Use will be=20 made of the

ifStack and ifInvStack Tables defined in RFC 2863 = and RFC=20 2864

respectively. Use will also be made of the = ifAvailableStack=20 and

ifInvAvailableStack tables as defined by the = Hubmib WG.=20 [[DR]]  

 

 

2. The working group will develop a set of = managed objects=20 as an optional extension to RFC 5650 that shall provide an alternative = approach, known as the "Vector of Profiles", for the configuration of = DSL=20 lines. The Vector of Profiles MIB will be based on the Broadband Forum = TR-165=20 document.

 

 

 

The MIB modules defined by this group will be = generated=20 using SMIv2, 

will be consistent with the SNMP management = framework, and=20 will describe

the relationship of the objects defined to = existing MIBs=20 such as those

described in other work products of this Working = Group, the=20 interfaces

MIB, the Ethernet MIB modules and the AToM MIB.=20

 

The working group will consider the input of the = Broadband=20 forum and the ITU

in the definition of these MIBs.

 

Goals and Milestones:

 

Feb 2010 Initial Vector of Profiles draft to be = accepted by=20 the Working Group.

Apr 2010 Post Vector of Profiles Draft version=20 01.

Jun 2010 Revise the draft and post vector of = Profiles draft=20 version 02.

Jul  2010  Working Group review of the = Vector of=20 Profiles draft.

Aug 2010 Post Vector of Profiles Draft version=20 03.

Sep 2010 Present the Vdsl2 document to the=20 IESG.

 

Thank you kindly,

Menachem Dodge

 

------_=_NextPart_001_01CA9DB3.23DAED56-- From Menachem.Dodge@ecitele.com Mon Jan 25 05:53:22 2010 Return-Path: X-Original-To: adslmib@core3.amsl.com Delivered-To: adslmib@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A928F3A697D for ; Mon, 25 Jan 2010 05:53:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.391 X-Spam-Level: X-Spam-Status: No, score=-1.391 tagged_above=-999 required=5 tests=[AWL=1.207, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iKyGhQ7HaVyh for ; Mon, 25 Jan 2010 05:53:21 -0800 (PST) Received: from ilptbmg01.ecitele.com (ilptbmg01-out.ecitele.com [147.234.242.234]) by core3.amsl.com (Postfix) with ESMTP id E47463A69DC for ; Mon, 25 Jan 2010 05:53:19 -0800 (PST) X-AuditID: 93eaf2e7-b7c38ae000000ed6-ed-4b5da12dc8a6 Received: from ilptexch01.ecitele.com ( [172.31.244.40]) by ilptbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id 4F.09.03798.D21AD5B4; Mon, 25 Jan 2010 15:48:29 +0200 (IST) Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ilptexch01.ecitele.com ([172.31.244.40]) with mapi; Mon, 25 Jan 2010 15:53:19 +0200 From: Menachem Dodge To: "Romascanu, Dan (Dan)" , "adslmib@ietf.org" Date: Mon, 25 Jan 2010 15:53:18 +0200 Thread-Topic: [Adslmib] Proposed Charter Change - to include VoP Thread-Index: Acqc1mdOTQp0yvfKRT2oTO3IjXny2QAuBZTAAAhhJAAABSOeoA== Message-ID: <283DD79798619346BF9B17D7B5035A190107FF172D5E@ILPTMAIL02.ecitele.com> References: <283DD79798619346BF9B17D7B5035A190107FF172BDD@ILPTMAIL02.ecitele.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_283DD79798619346BF9B17D7B5035A190107FF172D5EILPTMAIL02e_" MIME-Version: 1.0 X-Brightmail-Tracker: AAAAAA== Subject: Re: [Adslmib] Proposed Charter Change - to include VoP X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: ADSLMIB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jan 2010 13:53:22 -0000 --_000_283DD79798619346BF9B17D7B5035A190107FF172D5EILPTMAIL02e_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello Dan, Thanks for your comments and questions. I will revise the whole text including the headers as you suggest. I will update the milestones: 'Jul 2010 Working Group Last Call for the Vector of Profiles draft.' 'Sep 2010 Submit Vector Of Profile document to the IESG as Proposed Standar= d.' Best Regards, Menachem From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: Monday, January 25, 2010 1:40 PM To: Menachem Dodge; adslmib@ietf.org Subject: RE: [Adslmib] Proposed Charter Change - to include VoP Comments and Questions: - do you plan for this text to replace the current charter? if so, can you = please revise the whole text, including the headers. It's a good opportunit= y to take out the names of the editors and advisors who are not active any = longer and replace them with the current ones - be more specific on what SG in the ITU-T the WG needs to coordinate with - 'Jul 2010 Working Group review of the Vector of Profiles draft.' do you= mean WG last call? - 'Sep 2010 Present the Vdsl2 document to the IESG.' is this Vsdl2 or vec= tor of profiles MIB? is this for consideration as Proposed Standard? Thanks and Regards, Dan ________________________________ From: adslmib-bounces@ietf.org [mailto:adslmib-bounces@ietf.org] On Behalf = Of Menachem Dodge Sent: Monday, January 25, 2010 9:21 AM To: adslmib@ietf.org Subject: [Adslmib] Proposed Charter Change - to include VoP Hello All, Please review the proposed updated working group charter and milestones (be= low). All comments and feedback are appreciated. =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 The working group will define: 1. 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 G.998.3 (TDIM). A common MIB module will be developed to handle the common objects and three specific MIB modules will be developed to handle the three separate layer-2 technologies. Use will be made of the ifStack and ifInvStack Tables defined in RFC 2863 and RFC 2864 respectively. Use will also be made of the ifAvailableStack and ifInvAvailableStack tables as defined by the Hubmib WG. [[DR]] 2. The working group will develop a set of managed objects as an optional e= xtension to RFC 5650 that shall provide an alternative approach, known as t= he "Vector of Profiles", for the configuration of DSL lines. The Vector of = Profiles MIB will be based on the Broadband Forum TR-165 document. The MIB modules 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, the Ethernet MIB modules and the AToM MIB. The working group will consider the input of the Broadband forum and the IT= U in the definition of these MIBs. Goals and Milestones: Feb 2010 Initial Vector of Profiles draft to be accepted by the Working Gro= up. Apr 2010 Post Vector of Profiles Draft version 01. Jun 2010 Revise the draft and post vector of Profiles draft version 02. Jul 2010 Working Group review of the Vector of Profiles draft. Aug 2010 Post Vector of Profiles Draft version 03. Sep 2010 Present the Vdsl2 document to the IESG. Thank you kindly, Menachem Dodge --_000_283DD79798619346BF9B17D7B5035A190107FF172D5EILPTMAIL02e_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello Dan,

 =

Thanks for your comments= and questions.

 =

I will revise the whole = text including the headers as you suggest.

 =

I will update the milest= ones:

 =

'Jul  2010  Wo= rking Group Last Call for the Vector of Profiles draft.'

'Sep 2010 Submit Vector = Of Profile document to the IESG as Proposed Standard.' 

 =

Best Regards,=

Menachem

 =

From: Romascanu, Da= n (Dan) [mailto:dromasca@avaya.com]
Sent: Monday, January 25, 2010 1:40 PM
To: Menachem Dodge; adslmib@ietf.org
Subject: RE: [Adslmib] Proposed Charter Change - to include VoP=

 

Comments and  Questions:

 

- do you plan for this text to replace the current charter? if = so, can you please revise the whole text, including the headers. It's a good opportunity to take out the names of the editors and advisors who are not active any longer and replace them with the current ones

- be more specific on what SG in the ITU-T the WG needs to coordinate with

- 'Jul  2010  Working Group review of the Vector of Profiles draft.' do you mean WG last call?

- 'Sep 2010 Present the Vdsl2 document to the IESG.' &nbs= p; is this Vsdl2 or vector of profiles MIB? is this for consideration as Proposed Standard?

 

Thanks and Regards,

 

Dan

 

 


From: adslmib-bounces@ietf.org [mailto:adslmib-bounces@ietf.org] On Behalf Of Menachem Dodge
Sent: Monday, January 25, 2010 9:21 AM
To: adslmib@ietf.org
Subject: [Adslmib] Proposed Charter Change - to include VoP

 

Hello All,

 

Please review the proposed updated working group chart= er and milestones (below).

 =

 All comments and feedback are appreciated. =

 

=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

 

The working group will define: 

 

1. A set of managed objects to handle the bonding of x= DSL lines 

according to the ITU-T Recommendations G.998.1 (ATM), G.998.2 (Ethernet)

and G.998.3 (TDIM). A common MIB module will be develo= ped to handle the

common objects and three specific MIB modules will be developed to

handle the three separate layer-2 technologies. Use wi= ll be made of the

ifStack and ifInvStack Tables defined in RFC 2863 and = RFC 2864

respectively. Use will also be made of the ifAvailable= Stack and

ifInvAvailableStack tables as defined by the Hubmib WG= . [[DR= ]]  

 

 

2. The working group will develop a set of managed obj= ects as an optional extension to RFC 5650 that shall provide an alternative approach, known as the "Vector of Profiles", for the configuratio= n of DSL lines. The Vector of Profiles MIB will be based on the Broadband Forum TR-165 document.

 

 

 

The MIB modules defined by this group will be generate= d using SMIv2, 

will be consistent with the SNMP management framework,= and will describe

the relationship of the objects defined to existing MI= Bs such as those

described in other work products of this Working Group= , the interfaces

MIB, the Ethernet MIB modules and the AToM MIB. <= /o:p>

 

The working group will consider the input of the Broad= band forum and the ITU

in the definition of these MIBs.

 

Goals and Milestones:

 

Feb 2010 Initial Vector of Profiles draft to be accept= ed by the Working Group.

Apr 2010 Post Vector of Profiles Draft version 01.

Jun 2010 Revise the draft and post vector of Profiles = draft version 02.

Jul  2010  Working Group review of the Vecto= r of Profiles draft.

Aug 2010 Post Vector of Profiles Draft version 03.

Sep 2010 Present the Vdsl2 document to the IESG.<= /o:p>

 

Thank you kindly,

Menachem Dodge

 

--_000_283DD79798619346BF9B17D7B5035A190107FF172D5EILPTMAIL02e_-- From Menachem.Dodge@ecitele.com Tue Jan 26 14:05:08 2010 Return-Path: X-Original-To: adslmib@core3.amsl.com Delivered-To: adslmib@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F0CC3A68C5 for ; Tue, 26 Jan 2010 14:05:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.995 X-Spam-Level: X-Spam-Status: No, score=-1.995 tagged_above=-999 required=5 tests=[AWL=0.603, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2RBxDmLpHzKf for ; Tue, 26 Jan 2010 14:05:04 -0800 (PST) Received: from ilptbmg01.ecitele.com (ilptbmg01-out.ecitele.com [147.234.242.234]) by core3.amsl.com (Postfix) with ESMTP id 7E27D3A679C for ; Tue, 26 Jan 2010 14:05:01 -0800 (PST) X-AuditID: 93eaf2e7-b7c38ae000000ed6-ca-4b5f65ee6ad8 Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id C8.38.03798.EE56F5B4; Wed, 27 Jan 2010 00:00:15 +0200 (IST) Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Wed, 27 Jan 2010 00:05:11 +0200 From: Menachem Dodge To: "Romascanu, Dan (Dan)" , "adslmib@ietf.org" Date: Wed, 27 Jan 2010 00:05:10 +0200 Thread-Topic: [Adslmib] Proposed Charter Change - to include VoP Thread-Index: Acqc1mdOTQp0yvfKRT2oTO3IjXny2QAuBZTAAAhhJAAABSOeoAAAZXnAAEL80BA= Message-ID: <283DD79798619346BF9B17D7B5035A190107FF173044@ILPTMAIL02.ecitele.com> References: <283DD79798619346BF9B17D7B5035A190107FF172BDD@ILPTMAIL02.ecitele.com> <283DD79798619346BF9B17D7B5035A190107FF172D5E@ILPTMAIL02.ecitele.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_283DD79798619346BF9B17D7B5035A190107FF173044ILPTMAIL02e_" MIME-Version: 1.0 X-Brightmail-Tracker: AAAAAA== X-Mailman-Approved-At: Tue, 26 Jan 2010 14:06:26 -0800 Subject: Re: [Adslmib] Proposed Charter Change - to include VoP X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: ADSLMIB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jan 2010 22:05:08 -0000 --_000_283DD79798619346BF9B17D7B5035A190107FF173044ILPTMAIL02e_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi All, I have revised the Working Group charter page, please see below. Comments and feedback are welcome. =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=3D=3D=3D=3D ADSL MIB (adslmib) Last Modified: 2009-08-24 Additional information is available at tools.ietf.org/wg/adslmib Chair(s): * Menachem Dodge Operations and Management Area Director(s): * Dan Romascanu * Ronald Bonica Operations and Management Area Advisor: * Dan Romascanu Editor(s): * Scott Baillie * Moti Morgenstern * Umberto Bonollo * Edward Beili Mailing Lists: General Discussion: adslmib@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/adslmib Archive: http://www.ietf.org/mail-archive/web/adslmib/current/maillist.html Description of Working Group: The working group will define: 1. 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 G.998.3 (TDIM). A common MIB module will be developed to handle the common objects and three specific MIB modules will be developed to handle the three separate layer-2 technologies. Use will be made of the ifStack and ifInvStack Tables defined in RFC 2863 and RFC 2864 respectively. Use will also be made of the ifCapStack and ifInvCapStack tables as defined in RFC 5066. The Broadband forum TR-159 wil= l be used in the definition of these MIBs. 2. The working group will develop a set of managed objects as an optional e= xtension to RFC 5650 that shall provide an alternative approach, known as t= he "Vector of Profiles", for the configuration of DSL lines. The Vector of = Profiles MIB will be based on the Broadband Forum TR-165 document. The ITU-= T G.997.1 will also be considered in the definition of this extension. The MIB modules 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, the Ethernet MIB modules and the AToM MIB. Goals and Milestones: Done Submit Internet-Draft to cover subscriber equipment Done Meet at Chicago IETF to review Internet-Drafts Done Submit Internet-Draft to IESG for consideration as Proposed Standard. Done Meet at Oslo IETF to review new Internet-Drafts and discuss implementation = experience on initial MIB Done Submit supplementary Internet-Draft to IESG for consideration as Proposed S= tandard. Done Produce Internet-Draft covering HDSL2 management objects. Done Submit updated HDSL2/SHDSL Internet-Draft Done Complete WG last call for HDSL2/SHDSL management objects Done Collect implementation reports for ADSL MIB Done Submit HDSL2/SHDSL MIB to IESG for consideration as Proposed Standard Done Submit initial Internet-Draft VDSL MIB Done Complete WG last call on VDSL MIB Done Submit updated VDSL MIB Internet-Draft Done Submit final VDSL MIB Internet-Draft Done Submit VDSL MIB to IESG for consideration as Proposed Standard Done New WG I-Ds for the LCS MCM and SCM MIB modules Done Initial WG Internet-Draft covering ADSL2 management objects Done Integrate working group changes and produce revised draft Done Complete WG last call on ADSL2 MIB Done Submit ADSL2 MIB to IESG for consideration as Proposed Standard Done Re-charter or close down Done Initial WG Internet-Draft covering VDSL2 management objects Done Inform the ITU-T and DSL Forum that work on the VDSL2 MIB has begun Done Integrate working group changes and produce revised VDSL2 MIB draft Done Post Initial Drafts of all the xDsl Bonding MIB drafts Done Post Vdsl2 draft version 03 Done Post Vdsl2 draft version 04. Done Complete Thorough Working Group Reviews of the Vdsl2 draft and produce vers= ion 05. Done Working Group Last Call for the Vdsl2 document. Done Early MIB Doctor Reviews of the Vdsl2 draft. Done Make Correction to the draft following the review. Done Working Group Last Call for the Vdsl2 document following corrections. Done Present the Vdsl2 document to the IESG. Feb 2010 Feb 2010 Complete the work on all the four G.Bond documents. Initial Vector of Profiles draft to be accepted by the Working Group. Mar 2010 Working Group Last Call on all the G. Bond documents. Apr 2010 Submit G.Bond documents to IESG as Proposed Standard Apr 2010 Post Vector of Profiles Draft version 01. Jun 2010 Revise the draft and post vector of Profiles draft version 02= . Jul 2010 Working Group Last Call for the Vector of Profiles draft. Aug 2010 Post Vector of Profiles Draft version 03. Sep 2010 Submit the Vector Of Profile document to the IESG as Proposed= Standard. Oct 2010 Re-charter or close down. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Best Regards, Menachem --_000_283DD79798619346BF9B17D7B5035A190107FF173044ILPTMAIL02e_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi All,

I have revised the Working Group charter page, please see below.

Comments and feedback are welcome.

A= DSL MIB (adslmib)

La= st Modified: 2009-08-24

Ad= ditional information is available at to= ols.ietf.org/wg/adslmib

C= hair(s):

O= perations and Management Area Director(s):

O= perations and Management Area Advisor:

E= ditor(s):

M= ailing Lists:

General Discussion: adslmib@ietf.org
To Subscribe: htt= ps://www.ietf.org/mailman/listinfo/adslmib
Archive: http://www.ietf.org/mail-archive/web/adslmib/current/maillist.html

D= escription of Working Group:

The working group will define:

1. 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 G.998.3 (TDIM). A common MIB module will be developed to handle the
common objects and three specific MIB modules will be developed to
handle the three separate layer-2 technologies. Use will be made of the
ifStack and ifInvStack Tables defined in RFC 2863 and RFC 2864
respectively. Use will also be made of the ifCapStack and
ifInvCapStack tables as defined in RFC 5066. The Broadband forum TR-159 wil= l be used in the definition of these MIBs.

 

2. The working group will develop a set of managed obj= ects as an optional extension to RFC 5650 that shall provide an alternative approach, known as the "Vector of Profiles", for the configuratio= n of DSL lines. The Vector of Profiles MIB will be based on the Broadband Forum TR-165 document. The ITU-T G.997.1 will also be considered in the definition of this extension.

The MIB modules 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, the Ethernet MIB modules and the AToM MIB.

G= oals and Milestones:

Done

  

Submit Internet-Draft to cover subscriber equipment

Done

  

Meet at Chicago IETF to review Internet-Drafts

Done

  

Submit Internet-Draft to IESG for consideration as Proposed Standard.

Done

  

Meet at Oslo IETF to review new Internet-Drafts and discuss implementation experience on initial MIB

Done

  

Submit supplementary Internet-Draft to IESG for consideratio= n as Proposed Standard.

Done

  

Produce Internet-Draft covering HDSL2 management objects.

Done

  

Submit updated HDSL2/SHDSL Internet-Draft =

Done

  

Complete WG last call for HDSL2/SHDSL management objects

Done

  

Collect implementation reports for ADSL MIB

Done

  

Submit HDSL2/SHDSL MIB to IESG for consideration as Proposed Standard

Done

  

Submit initial Internet-Draft VDSL MIB

Done

  

Complete WG last call on VDSL MIB

Done

  

Submit updated VDSL MIB Internet-Draft

Done

  

Submit final VDSL MIB Internet-Draft

Done

  

Submit VDSL MIB to IESG for consideration as Proposed Standa= rd

Done

  

New WG I-Ds for the LCS MCM and SCM MIB modules <= /span>

Done

  

Initial WG Internet-Draft covering ADSL2 management objects =

Done

  

Integrate working group changes and produce revised draft

Done

  

Complete WG last call on ADSL2 MIB

Done

  

Submit ADSL2 MIB to IESG for consideration as Proposed Stand= ard

Done

  

Re-charter or close down

Done

  

Initial WG Internet-Draft covering VDSL2 management objects =

Done

  

Inform the ITU-T and DSL Forum that work on the VDSL2 MIB ha= s begun

Done

  

Integrate working group changes and produce revised VDSL2 MI= B draft

Done

  

Post Initial Drafts of all the xDsl Bonding MIB drafts =

Done

  

Post Vdsl2 draft version 03

Done

  

Post Vdsl2 draft version 04.

Done

  

Complete Thorough Working Group Reviews of the Vdsl2 draft a= nd produce version 05.

Done

  

Working Group Last Call for the Vdsl2 document. <= /span>

Done

  

Early MIB Doctor Reviews of the Vdsl2 draft.

Done

  

Make Correction to the draft following the review.

Done

  

Working Group Last Call for the Vdsl2 document following corrections.

Done

  

Present the Vdsl2 document to the IESG.

Feb 2010

Feb 2010    

  

Complete the work on all the four G.Bond documents. <= span style=3D'font-size:9.5pt;font-family:"Verdana","sans-serif";color:black'>=

Initial Vector of Profiles draft to be accepted by the Worki= ng Group.

Mar 2010

  

Working Group Last Call on all the G. Bond documents. <= /o:p>

Apr 2010      Submit G.Bond documents= to IESG as Proposed Standard

Apr 2010      Post Vector of Profiles Draft version 01.

Jun 2010      Revise the draft and po= st vector of Profiles draft version 02.

Jul  2010      Working Group Last Cal= l for the Vector of Profiles draft.

Aug 2010      Post Vector of Profiles Draft version 03.

Sep 2010      Submit the Vector Of Profile document to the IESG as Proposed Standard.

Oct 2010       Re-charter or clo= se down.

 =

 =

=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

 =

 =

 =

 =

--_000_283DD79798619346BF9B17D7B5035A190107FF173044ILPTMAIL02e_--