headers
RFC Errata System | 15 Apr 2013 15:59
Favicon

[Technical Errata Reported] RFC6765 (3592)

The following errata report has been submitted for RFC6765,
"xDSL Multi-Pair Bonding (G.Bond) MIB".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6765&eid=3592

--------------------------------------
Type: Technical
Reported by: Edward Beili <edward.beili <at> actelis.com>

Section: 8

Original Text
-------------
An object identifier for gBondMIB MODULE-IDENTITY has been allocated
by IANA in the MIB-2 transmission sub-tree (211).

This document defines the first version of the IANA-maintained IANA-
GBOND-TC-MIB module.  It is intended that each new G.998 bonding
scheme defined by the ITU-T Q4/SG15 working group and approved for
publication in a revision of ITU-T G.998.x will be added to the IANA-
maintained MIB module, provided that it is suitable for being managed
by the base objects in the GBOND-MIB module.  An object identifier
for ianaGBondTcMIB MODULE-IDENTITY has been allocated by IANA in the
MIB-2 transmission sub-tree (215).

Corrected Text
--------------
An object identifier for gBondMIB MODULE-IDENTITY has been allocated
(Continue reading)

Permalink | Reply | 0 comments |
headers
RFC Errata System | 15 Apr 2013 15:50
Favicon

[Technical Errata Reported] RFC6768 (3591)

The following errata report has been submitted for RFC6768,
"ATM-Based xDSL Bonded Interfaces MIB".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6768&eid=3591

--------------------------------------
Type: Technical
Reported by: Edward Beili <edward.beili <at> actelis.com>

Section: 8

Original Text
-------------
IANA has assigned 208 as the object identifier for g9981MIB MODULE-IDENTITY in the MIB-2 transmission
sub-tree <http://www.iana.org/>.

Corrected Text
--------------
IANA has assigned 208 as the object identifier for g9981MIB MODULE-IDENTITY in the MIB-2 tree <http://www.iana.org/>.

Notes
-----
Since the ifType value for g9981 is 263, the same value must be reserved under the transmission sub-tree in
the IANA registry, see http://www.iana.org/assignments/smi-numbers/smi-numbers.xml

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
(Continue reading)

Permalink | Reply | 0 comments |
headers
RFC Errata System | 15 Apr 2013 15:41
Favicon

[Technical Errata Reported] RFC6767 (3590)

The following errata report has been submitted for RFC6767,
"Ethernet-Based xDSL Multi-Pair Bonding (G.Bond/Ethernet) MIB".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6767&eid=3590

--------------------------------------
Type: Technical
Reported by: Edward Beili <edward.beili <at> actelis.com>

Section: 6

Original Text
-------------
    ::= { mib-2 264 }

Corrected Text
--------------
    ::= { mib-2 209 }

Notes
-----
The following changes must be made by IANA in
http://www.iana.org/assignments/smi-numbers/smi-numbers.xml :
1. The entry for the value of 209 under mib-2 shall be changed to:
209  g9982MIB  G9982-MIB  [RFC6767]
2. The entry for the value of 264 under transmission sub-tree shall be changed to:
264  Reserved  Reserved
(Continue reading)

Permalink | Reply | 0 comments |
headers
RFC Errata System | 15 Apr 2013 15:39
Favicon

[Technical Errata Reported] RFC6767 (3589)

The following errata report has been submitted for RFC6767,
"Ethernet-Based xDSL Multi-Pair Bonding (G.Bond/Ethernet) MIB".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6767&eid=3589

--------------------------------------
Type: Technical
Reported by: Edward Beili <edward.beili <at> actelis.com>

Section: 8

Original Text
-------------
IANA has assigned 264 as the object identifier for the g9982MIB MODULE-IDENTITY in the MIB-2 transmission
sub-tree <http://www.iana.org/>.

Corrected Text
--------------
IANA has assigned 209 as the object identifier for the g9982MIB MODULE-IDENTITY in the MIB-2 tree <http://www.iana.org/>.

Notes
-----
The following changes must be made by IANA in
http://www.iana.org/assignments/smi-numbers/smi-numbers.xml :
1. The entry for the value of 209 under mib-2 shall be changed to:
209  g9982MIB  G9982-MIB  [RFC6767]
2. The entry for the value of 264 under transmission sub-tree shall be changed to:
264  Reserved  Reserved
(Continue reading)

Permalink | Reply | 0 comments |
headers
RFC Errata System | 15 Apr 2013 15:25
Favicon

[Technical Errata Reported] RFC6766 (3588)

The following errata report has been submitted for RFC6766,
"xDSL Multi-Pair Bonding Using Time-Division Inverse Multiplexing (G.Bond/TDIM) MIB".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6766&eid=3588

--------------------------------------
Type: Technical
Reported by: Edward Beili <edward.beili <at> actelis.com>

Section: 8. IANA Cons

Original Text
-------------
IANA has allocated value 210 as the Object identifier for g9983MIB MODULE-IDENTITY
<http://www.iana.org/> in the MIB-2 transmission sub-tree.

Corrected Text
--------------
IANA has allocated value 210 as the Object identifier for g9983MIB MODULE-IDENTITY
<http://www.iana.org/> under the MIB-2 tree.

Notes
-----
According to RFC6765, the ifType number 265 was registered for g9983.
According to the registration note for the ifType registry, for every ifType registration, the
corresponding transmission number should be registered or marked "Reserved, therefore the value 265 in
the Transmission Group registry should be marked as Reserved.
(Continue reading)

Permalink | Reply | 0 comments |
headers
rfc-editor | 25 Feb 2013 16:10
Favicon

RFC 6768 on ATM-Based xDSL Bonded Interfaces MIB


A new Request for Comments is now available in online RFC libraries.

        
        RFC 6768

        Title:      ATM-Based xDSL Bonded Interfaces MIB 
        Author:     E. Beili
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2013
        Mailbox:    edward.beili <at> actelis.com
        Pages:      34
        Characters: 64283
        Updates/Obsoletes/SeeAlso:   None

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

        URL:        http://www.rfc-editor.org/rfc/rfc6768.txt

This document defines a 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 ATM-based multi-pair bonded xDSL
interfaces, as defined in ITU-T Recommendation G.998.1.

This document is a product of the ADSL MIB Working Group of the IETF.

This is now a Proposed Standard.
(Continue reading)

Permalink | Reply | 0 comments |
headers
rfc-editor | 25 Feb 2013 16:10
Favicon

RFC 6767 on Ethernet-Based xDSL Multi-Pair Bonding (G.Bond/Ethernet) MIB


A new Request for Comments is now available in online RFC libraries.

        
        RFC 6767

        Title:      Ethernet-Based xDSL Multi-Pair Bonding
                    (G.Bond/Ethernet) MIB 
        Author:     E. Beili, M. Morgenstern
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2013
        Mailbox:    edward.beili <at> actelis.com, 
                    moti.morgenstern <at> ecitele.com
        Pages:      53
        Characters: 105415
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-adslmib-gbond-eth-mib-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6767.txt

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

This document is a product of the ADSL MIB Working Group of the IETF.
(Continue reading)

Permalink | Reply | 0 comments |
headers
rfc-editor | 25 Feb 2013 16:10
Favicon

RFC 6766 on xDSL Multi-Pair Bonding Using Time-Division Inverse Multiplexing (G.Bond/TDIM) MIB


A new Request for Comments is now available in online RFC libraries.

        
        RFC 6766

        Title:      xDSL Multi-Pair Bonding Using Time-Division 
                    Inverse Multiplexing (G.Bond/TDIM) MIB 
        Author:     E. Beili
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2013
        Mailbox:    edward.beili <at> actelis.com
        Pages:      55
        Characters: 107078
        Updates/Obsoletes/SeeAlso:   None

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

        URL:        http://www.rfc-editor.org/rfc/rfc6766.txt

This document defines a 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), as defined in ITU-T
Recommendation G.998.3.

This document is a product of the ADSL MIB Working Group of the IETF.
(Continue reading)

Permalink | Reply | 0 comments |
headers
rfc-editor | 25 Feb 2013 16:10
Favicon

RFC 6765 on xDSL Multi-Pair Bonding (G.Bond) MIB


A new Request for Comments is now available in online RFC libraries.

        
        RFC 6765

        Title:      xDSL Multi-Pair Bonding (G.Bond) MIB 
        Author:     E. Beili, M. Morgenstern
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2013
        Mailbox:    edward.beili <at> actelis.com, 
                    moti.morgenstern <at> ecitele.com
        Pages:      73
        Characters: 154301
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-adslmib-gbond-mib-11.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6765.txt

This document defines a Management Information Base (MIB) module for
use with network management protocols in TCP/IP-based internets.
This document defines an extension to the Interfaces Group MIB with a
set of common objects for managing multi-pair bonded Digital
Subscriber Line (xDSL) interfaces, as defined in ITU-T
Recommendations G.998.1, G.998.2, and G.998.3.  The textual
conventions defining the bonding schemes are contained in a separate
MIB module maintained by Internet Assigned Numbers Authority (IANA).
The MIB modules specific to each bonding technology are defined in
(Continue reading)

Permalink | Reply | 4 comments |
headers
internet-drafts | 4 Dec 2012 22:13
Picon
Favicon

I-D Action: draft-ietf-adslmib-xdsl-vop-00.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           : Definitions of Managed Objects for Very High Speed Digital Subscriber Line 2 (VDSL2)
	Author(s)       : Moti Morgenstern
                          Scott Baillie
                          Markus Freudenberger
	Filename        : draft-ietf-adslmib-xdsl-vop-00.txt
	Pages           : 223
	Date            : 2012-11-06

Abstract:
   This document defines a Management Information Base (MIB) module for
   use with network management protocols in the Internet community.  In
   particular, it describes objects used for managing parameters of the
   "Very High Speed Digital Subscriber Line 2 (VDSL2)" interface type,
   which are also applicable for managing Asymmetric Digital Subscriber
   Line (ADSL), ADSL2, and ADSL2+ interfaces.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-adslmib-xdsl-vop

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-adslmib-xdsl-vop-00

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
Permalink | Reply | 0 comments |
headers
מנחם דודג' | 1 Nov 2012 16:50
Picon

Nomcom Request for IETF Community Input

Hi All,
 
Please take note of the following email from the Nomcom Chair requesting input from the IETF Community with regard to the candidates standing for Nomcom positions and general feedback relating to the positions:
 

"In order to ensure that your input is received in time to be useful, the
NomCom needs to receive community feedback on or before Sunday, November 11.

The final list of candidates (as per RFC 5680) that the NomCom is
considering for open positions can be found at:
https://www.ietf.org/group/nomcom/2012/input/

The NomCom will be holding office hours during IETF 85, Monday-
Thursday from 1:00pm to 3:00pm in Room 305. The NomCom welcomes
comments on specific individuals, as well as general feedback related to
any of the positions that NomCom is considering.

Note: A list of leadership positions that the NomCom is considering can be
found at: https://www.ietf.org/group/nomcom/2012/

If the NomCom office hours are inconvenient for you or if you cannot
attend IETF 85, the NomCom is happy to take community input via email
to nomcom12 at ietf.org. Additionally, the NomCom is happy to arrange a
meeting outside of office hours, just send us email and we can set
something up.

Comments on specific candidates can also be provided to the NomCom
via the web feedback tool:
https://www.ietf.org/group/nomcom/2012/input/

Thank you for your help,
- Matt Lepinski
nomcom-chair at ietf.org "
 
 
Thank you kindly,
 
Best Regards,
Menachem Dodge
_______________________________________________
Adslmib mailing list
Adslmib <at> ietf.org
https://www.ietf.org/mailman/listinfo/adslmib
Permalink | Reply | 0 comments |

Gmane