Re: Proposed Charter Change - to include VoP

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 Standard.'

Best Regards,
Menachem

From: Romascanu, Dan (Dan) [mailto:[email protected]]
Sent: Monday, January 25, 2010 1:40 PM
To: Menachem Dodge; [email protected]
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.'   is this Vsdl2 or vector of profiles MIB? is this for consideration as Proposed Standard?

Thanks and Regards,

Dan


________________________________
From: [email protected] [mailto:[email protected]] On Behalf Of Menachem Dodge
Sent: Monday, January 25, 2010 9:21 AM
To: [email protected]
Subject: [Adslmib] Proposed Charter Change - to include VoP

Hello All,

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

 All comments and feedback are appreciated.

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

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 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.



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 ITU
in the definition of these MIBs.

Goals and Milestones:

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.

Thank you kindly,
Menachem Dodge

_______________________________________________
Adslmib mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/adslmib