Menachem Dodge | 12 Mar 2012 12:24

G.BOND MIB documents

WARNING: contains banned part
From: Menachem Dodge <Menachem.Dodge <at> ecitele.com>
Subject: G.BOND MIB documents
Date: 2012-03-12 11:24:48 GMT
Hello,

As you are aware the four G.Bond MIB documents are currently being reviewed by the IESG for publication.

Please indicate how much interest you, (or your organization) have in seeing these documents published .

It is urgent that you send your response before Thursday, when the IESG will be making their decision
regarding these documents.

Thank you kindly.

Best Regards,
Menachem Dodge

This e-mail message is intended for the recipient only and contains information which is CONFIDENTIAL and
which may be proprietary to ECI Telecom. If you have received this transmission in error, please inform us
by e-mail, phone or fax, and then delete the original and all copies thereof.

Attachment (winmail.dat): application/ms-tnef, 7005 bytes
(Continue reading)

internet-drafts | 13 Mar 2012 00:48
Picon
Favicon

I-D Action: draft-ietf-adslmib-gbond-mib-10.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item
of the ADSL MIB Working Group of the IETF.

	Title           : xDSL multi-pair bonding (G.Bond) MIB
	Author(s)       : Edward Beili
                          Moti Morgenstern
	Filename        : draft-ietf-adslmib-gbond-mib-10.txt
	Pages           : 70
	Date            : 2012-03-12

   This document defines Management Information Base (MIB) module for
   use with network management protocols in TCP/IP-based internets.
   This document proposes an extension to the Interfaces Group MIB with
   a set of common objects for managing multi-pair bonded Digital
   Subscriber Line (xDSL) interfaces, defined in ITU-T recommendations
   G.998.1, G.998.2 and G.998.3.  The MIB modules specific to each
   bonding technology are defined in G9981-MIB, G9982-MIB and G9983-MIB
   respectively.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-adslmib-gbond-mib-10.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-adslmib-gbond-mib-10.txt
internet-drafts | 13 Mar 2012 00:49
Picon
Favicon

I-D Action: draft-ietf-adslmib-gbond-atm-mib-06.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item
of the ADSL MIB Working Group of the IETF.

	Title           : ATM-Based xDSL Bonded Interfaces MIB
	Author(s)       : Edward Beili
	Filename        : draft-ietf-adslmib-gbond-atm-mib-06.txt
	Pages           : 33
	Date            : 2012-03-12

   This document defines Management Information Base (MIB) module for
   use with network management protocols in TCP/IP based networks.  This
   document proposes an extension to the GBOND-MIB module with a set of
   objects for managing ATM-based multi-pair bonded xDSL interfaces,
   defined in ITU-T recommendation G.998.1.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-adslmib-gbond-atm-mib-06.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-adslmib-gbond-atm-mib-06.txt
internet-drafts | 13 Mar 2012 00:51
Picon
Favicon

I-D Action: draft-ietf-adslmib-gbond-eth-mib-06.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item
of the ADSL MIB Working Group of the IETF.

	Title           : Ethernet-based xDSL multi-pair bonding (G.Bond/Ethernet) MIB
	Author(s)       : Edward Beili
                          Moti Morgenstern
	Filename        : draft-ietf-adslmib-gbond-eth-mib-06.txt
	Pages           : 53
	Date            : 2012-03-12

   This document defines Management Information Base (MIB) module for
   use with network management protocols in TCP/IP based internets.
   This document proposes an extension to the GBOND-MIB module with a
   set of objects for managing Ethernet-based multi-pair bonded xDSL
   interfaces, defined in ITU-T recommendation G.998.2.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-adslmib-gbond-eth-mib-06.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-adslmib-gbond-eth-mib-06.txt
internet-drafts | 13 Mar 2012 00:52
Picon
Favicon

I-D Action: draft-ietf-adslmib-gbond-tdim-mib-08.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item
of the ADSL MIB Working Group of the IETF.

	Title           : xDSL multi-pair bonding using Time-Division Inverse Multiplexing (G.Bond/TDIM) MIB
	Author(s)       : Edward Beili
	Filename        : draft-ietf-adslmib-gbond-tdim-mib-08.txt
	Pages           : 54
	Date            : 2012-03-12

   This document defines Management Information Base (MIB) module for
   use with network management protocols in TCP/IP based internets.
   This document proposes an extension to the GBOND-MIB module with a
   set of objects for managing multi-pair bonded xDSL interfaces using
   Time-Division Inverse Multiplexing (TDIM), defined in ITU-T
   recommendation G.998.3.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-adslmib-gbond-tdim-mib-08.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-adslmib-gbond-tdim-mib-08.txt
Romascanu, Dan (Dan | 21 Mar 2012 13:44
Favicon

Re: Protocol Action: 'ATM-Based xDSL Bonded Interfaces MIB'to Proposed Standard (draft-ietf-adslmib-gbond-atm-mib-06.txt)

Special thanks to our editor and congratulations to the chair and the
whole WG for having two of the final set of four documents approved by
the IESG. Hopefully we will be able to get the other two documents in
the next few days or weeks, and successfully conclude the work on ADSL
MIB in the IETF. 

Regards,

Dan

> -----Original Message-----
> From: adslmib-bounces <at> ietf.org [mailto:adslmib-bounces <at> ietf.org] On
> Behalf Of The IESG
> Sent: Monday, March 19, 2012 8:49 PM
> To: IETF-Announce
> Cc: adslmib mailing list; adslmib chair; RFC Editor
> Subject: [Adslmib] Protocol Action: 'ATM-Based xDSL Bonded Interfaces
> MIB'to Proposed Standard (draft-ietf-adslmib-gbond-atm-mib-06.txt)
> 
> The IESG has approved the following document:
> - 'ATM-Based xDSL Bonded Interfaces MIB'
>   (draft-ietf-adslmib-gbond-atm-mib-06.txt) as a Proposed Standard
> 
> This document is the product of the ADSL MIB Working Group.
> 
> The IESG contact persons are Dan Romascanu and Ronald Bonica.
> 
> A URL of this Internet Draft is:
> http://datatracker.ietf.org/doc/draft-ietf-adslmib-gbond-atm-mib/
> 
(Continue reading)

Romascanu, Dan (Dan | 21 Mar 2012 14:28
Favicon

two questions on draft-ietf-adslmib-gbond-mib-10

Hi Ed,

The I-D draft-ietf-adslmib-gbond-mib-10 was approved by the IESG with
'point raised'. This means that I would like to get clarification from
you (and the WG if needed) on a couple of points before approving the
document. 

The two questions derive from the COMMENT entered by Adrian Farrel. They
are non-blocking from his perspective, yet I think that they are
interesting enough to deserve being answered, even if they do not lead
to changes in the document. 

1.  How likely is it that new bonding schemes (i.e. other
technologies) will come along and be handled by this MIB module without
extensions? I think the intention is that this module is technology-
independent, so that it would not need to be revised for a new bonding
type.

However, GBondSchemeList and GBondScheme are closed lists such that you
would need to revise the module to support new technologies. That seems
a shame.

You could move the TCs into a separate module so that only that module
needs to be revised.

An alternative, is to define an IANA Textual convention for this and
allow just the TC to be updated as necessary.

---                     

(Continue reading)

Menachem Dodge | 26 Mar 2012 19:21

Re: Protocol Action: 'ATM-Based xDSL Bonded Interfaces MIB'to Proposed Standard (draft-ietf-adslmib-gbond-atm-mib-06.txt)

Hello,

I wish to thank you, Dan, for all your help and advice that you have provided to me as chair, and to the editors
and the working group as a whole, in your capacity as AD.

Thank you for all your hard work and for being there whenever we sought your assistance.

I wish you, all the very best in your future endeavors.

Benoit, I extend to you a warm welcome and look forward to working together with you.

In addition to the G.Bond MIBs, there is an outstanding item on the WG charter, namely the Vectoring of
Profiles MIB, the charter reads as follows:

"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 ITU-T G.997.1 will also be considered in the
definition of this extension."

The Broadband Forum requested this MIB to be developed in a liaison some two years ago, but also warned that
work on a revision of TR-129 and TR-165 was underway. 
 My understanding is that this work at the Broadband Forum is now reaching completion.

The question that I put to the Working Group is, whether there is still interest in developing the optional
extension to RFC 5650.
In addition to showing your interest please also indicate your willingness to participate in developing
the MIB, as an editor or reviewer, and whether you or your company are likely to implement/deploy  the MIB if
it is developed.
(Continue reading)

Romascanu, Dan (Dan | 28 Mar 2012 11:00
Favicon

Re: two questions on draft-ietf-adslmib-gbond-mib-10

I do not think that I saw answers to these questions yet. As I am
transferring today my yellow dot and AD responsibilities to Benoit, this
document together with eth-mib transfer to him, and hopefully the
remaining issues will be quickly answered. 

Dan

> -----Original Message-----
> From: adslmib-bounces <at> ietf.org [mailto:adslmib-bounces <at> ietf.org] On
> Behalf Of Romascanu, Dan (Dan)
> Sent: Wednesday, March 21, 2012 3:28 PM
> To: Edward Beili
> Cc: adrian <at> olddog.co.uk; adslmib mailing list
> Subject: [Adslmib] two questions on draft-ietf-adslmib-gbond-mib-10
> 
> Hi Ed,
> 
> The I-D draft-ietf-adslmib-gbond-mib-10 was approved by the IESG with
> 'point raised'. This means that I would like to get clarification from
> you (and the WG if needed) on a couple of points before approving the
> document.
> 
> The two questions derive from the COMMENT entered by Adrian Farrel.
> They
> are non-blocking from his perspective, yet I think that they are
> interesting enough to deserve being answered, even if they do not lead
> to changes in the document.
> 
> 1.  How likely is it that new bonding schemes (i.e. other
> technologies) will come along and be handled by this MIB module
(Continue reading)

Moti Morgenstern | 28 Mar 2012 11:37

Re: two questions on draft-ietf-adslmib-gbond-mib-10

Hi Dan,

I previously didn't send my opinion as the 'To' list included Ed alone.
However, if it matters, the following is (briefly) my answer to those questions.

1) New Bonding Schemes
Each new scheme will probably require developing a MIB for it. The 'common' MIB module is not expected to be
modified too much, but it's obvious that it would not be left untouched. As a minimum, every component that
currently mentions the existing bonding schemes will need to mention the 'new' scheme as well. I mean,
shouldn't the MIB document describe its applicability to the 'new' scheme and indicate the reference
standard? Shouldn't the edge devices exchange their capability to support that scheme? Etc.

2) GBondSchemeList
I think that it's up to the implementation to decide whether or not it wishes to distinguish between a device
that explicitly reports it doesn't support any of the 3 standard schemes and a device that simply didn't
report so far its capability. The value 0 may be sufficient for both (because in both cases it's impossible
for the edge devices to agree on a scheme at the moment) and then the optional value 'none' won't be
supported. 
BTW, we are familiar with textual conventions for failures/alarms in which the value 0 means: 'no problem'
while there are other TCs in which the 'no problem' is allocated its own bit-position, correct?.  

Best Regards (and good luck in your future projects),
Moti

-----Original Message-----
From: adslmib-bounces <at> ietf.org [mailto:adslmib-bounces <at> ietf.org] On Behalf Of Romascanu, Dan (Dan)
Sent: Wednesday, March 28, 2012 11:00 AM
To: Romascanu, Dan (Dan); Edward Beili
Cc: adrian <at> olddog.co.uk; adslmib mailing list
Subject: Re: [Adslmib] two questions on draft-ietf-adslmib-gbond-mib-10
(Continue reading)


Gmane