Ray, Robert | 6 May 16:19 2005

Congratulations to Menachem!!


http://www.ietf.org/rfc/rfc4069.txt?number=4069
http://www.ietf.org/rfc/rfc4070.txt?number=4070

Very good work.  I think everyone on the list appreciates 
your efforts in seeing these two documents through (and I am
personally very glad that you have agreed to work on the 
ADSL2/ADSLplus effort).

Thank you.

Bob Ray
Menachem Dodge | 6 May 17:48 2005
Picon

áòðééï: [Adslmib] Congratulations to Menachem!!

Hello Bob,

    Thank you kindly for your good wishes and I am very pleased
that these documents have been accepted as RFCs.

    Many thanks and much appreciation is owed to Randy and Bert
for their great efforts in correcting and re-correcting the various drafts,
and to you Bob, as co-editor for your help and assistance whenever I needed
it.

    My appreciation to the RFC editor for their work in finalising the RFC.

    I look forward to working together with everyone on the ADSL2/ADSLplus
document.

    Best Regards,

    Menachem.

----- Original Message -----
From: Ray, Robert <RobertRay <at> pesa.com>
To: ADSL MIB (E-mail) (E-mail) <adslmib <at> ietf.org>
Sent: Friday, May 06, 2005 4:19 PM
Subject: [Adslmib] Congratulations to Menachem!!

http://www.ietf.org/rfc/rfc4069.txt?number=4069
http://www.ietf.org/rfc/rfc4070.txt?number=4070

Very good work.  I think everyone on the list appreciates
your efforts in seeing these two documents through (and I am
(Continue reading)

rfc-editor | 10 May 01:01 2005

RFC 4069 on Definitions of Managed Object Extensions for Very High Speed Digital Subscriber Lines (VDSL) Using Single Carrier Modulation (SCM) Line Coding


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

        RFC 4069

        Title:      Definitions of Managed Object Extensions
                    for Very High Speed Digital Subscriber Lines
                    (VDSL) Using Single Carrier Modulation (SCM) Line
                    Coding
        Author(s):  M. Dodge, B. Ray
        Status:     Standards Track
        Date:       May 2005
        Mailbox:    mbdodge <at> ieee.org, rray <at> pesa.com
        Pages:      19
        Characters: 35712
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-adslmib-vdsl-ext-scm-08.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4069.txt

This document defines a portion of the Management Information Base
(MIB) module for use with network management protocols in the
Internet community.  In particular, it describes objects used for
managing the Line Code Specific parameters of Very High Speed
Digital Subscriber Line (VDSL) interfaces using Single Carrier
Modulation (SCM) Line Coding.  It is an optional extension to the
VDSL-LINE-MIB, RFC 3728, which handles line code independent
objects.

(Continue reading)

rfc-editor | 10 May 01:03 2005

RFC 4070 on Definitions of Managed Object Extensions for Very High Speed Digital Subscriber Lines (VDSL) Using Multiple Carrier Modulation (MCM) Line Coding


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

        RFC 4070

        Title:      Definitions of Managed Object Extensions
                    for Very High Speed Digital Subscriber Lines
                    (VDSL) Using Multiple Carrier Modulation (MCM)
                    Line Coding
        Author(s):  M. Dodge, B. Ray
        Status:     Standards Track
        Date:       May 2005
        Mailbox:    mbdodge <at> ieee.org, rray <at> pesa.com
        Pages:      24
        Characters: 48561
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-adslmib-vdsl-ext-mcm-06.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4070.txt

This document defines a portion of the Management Information Base
(MIB) module for use with network management protocols in the
Internet community.  In particular, it describes objects used for
managing the Line Code Specific parameters of Very High Speed
Digital Subscriber Line (VDSL) interfaces using Multiple Carrier
Modulation (MCM) Line Coding.  It is an optional extension to the
VDSL-LINE-MIB, RFC 3728, which handles line code independent
objects.

(Continue reading)

Wijnen, Bert (Bert | 14 May 15:28 2005
Picon

IESG/IABl WG Review: Recharter of ADSL MIB (adslmib)

Below is the report from the IESG Telechat Last Thursday.
So the new charter is not yet approved. Such will probably
happen on May 26th, unless we get (unexpected) serious
objections before that time.

I would suggest that the WG starts/continues the work to 
complete the work described by the charter.

Bert

------------ ADSLMIB WG rechartering status in IESG:

o ADSL MIB (adslmib) - 1 of 1
Token: Bert Wijnen

The IESG decided that the charter must go for External Review.  The Secretariat
will send a Working Group Review: RECHARTER announcement, with a separate
message to new-work. The Secretariat will place it back on the agenda for the
next IESG Teleconference (05/26/2005).

------------ The charter as proposed:

ADSL MIB (adslmib)
------------------

Last Modified: 2005-5-12

Current Status: Active Working Group

Chair(s):
(Continue reading)

Bob Ray | 14 May 15:33 2005
Picon

RE: IESG/IABl WG Review: Recharter of ADSL MIB (adslmib)

Okay.  Please remember the g.sdhsl.bis draft too!

Thank you,
Bob Ray

-----Original Message-----
From: adslmib-bounces <at> ietf.org [mailto:adslmib-bounces <at> ietf.org]On
Behalf Of Wijnen, Bert (Bert)
Sent: Saturday, May 14, 2005 8:28 AM
To: Bob Ray; Michael Sneed
Cc: Adslmib (E-mail)
Subject: [Adslmib] IESG/IABl WG Review: Recharter of ADSL MIB (adslmib)

Below is the report from the IESG Telechat Last Thursday.
So the new charter is not yet approved. Such will probably
happen on May 26th, unless we get (unexpected) serious
objections before that time.

I would suggest that the WG starts/continues the work to
complete the work described by the charter.

Bert

------------ ADSLMIB WG rechartering status in IESG:

o ADSL MIB (adslmib) - 1 of 1
Token: Bert Wijnen

The IESG decided that the charter must go for External Review.  The
Secretariat
(Continue reading)

Wijnen, Bert (Bert | 16 May 10:34 2005
Picon

RE: IESG/IABl WG Review: Recharter of ADSL MIB (adslmib )

putting it on IESG agenda as we speak. 
That is for next IESG telechat on May 26th.

Bert

> -----Original Message-----
> From: Bob Ray [mailto:robertray <at> knology.net]
> Sent: Saturday, May 14, 2005 15:34
> To: Wijnen, Bert (Bert); Bob Ray; Michael Sneed
> Cc: Adslmib (E-mail)
> Subject: RE: [Adslmib] IESG/IABl WG Review: Recharter of ADSL MIB
> (adslmib)
> 
> 
> Okay.  Please remember the g.sdhsl.bis draft too!
> 
> Thank you,
> Bob Ray
> 
> -----Original Message-----
> From: adslmib-bounces <at> ietf.org [mailto:adslmib-bounces <at> ietf.org]On
> Behalf Of Wijnen, Bert (Bert)
> Sent: Saturday, May 14, 2005 8:28 AM
> To: Bob Ray; Michael Sneed
> Cc: Adslmib (E-mail)
> Subject: [Adslmib] IESG/IABl WG Review: Recharter of ADSL MIB 
> (adslmib)
> 
> 
> Below is the report from the IESG Telechat Last Thursday.
(Continue reading)

Frank Chao (fchao | 18 May 01:47 2005
Picon

some counters related to ATM Cell in G.997.1

Hi,
 
   We would like to know that is there standard MIB has cover some counters related to ATM Cell in G.997.1, such as
 
 

NE-HEC-violation-Count

(HEC-P)

Count of number of occurrences of a near-end hec anomaly in the ATM Data Path

NE-Delineated-total-cell-count (CD-P)

Near-End count of the total number of cells passed through the cell delineation and HEC function process operating on the ATM data Path while in SYNC state

NE-Usr-Total-Cell-Count

(CU-P)

 

Near-End count of the total number cells delivered to ATU-C

NE-Idle-Cell-Bit-Error-Count (IBE-P)

Near-End count of the number of bit errors in the idle cell payload received in the ATM data path at the near end.

FE-HEC-violation-Count

(HEC-P)

Count of number of occurrences of the far-end hec anomaly in the ATM Data Path

FE-Delineated-total-cell-count (CD-P)

Far-End count of the total number of cells passed through the cell delineation and HEC function process operating on the ATM data Path while in SYNC state

FE-Usr-Total-Cell-Count

(CU-P)

 

Far-End count of the total number cells delivered to ATU-R

FE-Idle-Cell-Bit-Error-Count (IBE-P)

Far-End count of the number of bit errors in the idle cell payload received in the ATM data path at the far end.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Thanks,
 
Frank
 
_______________________________________________
Adslmib mailing list
Adslmib <at> ietf.org
https://www1.ietf.org/mailman/listinfo/adslmib
Ray, Robert | 18 May 16:06 2005

RE: some counters related to ATM Cell in G.997.1

Hi.
 
You might peruse the documents produced by the AToM MIB working group.
 
 
Regards,
Bob Ray
-----Original Message-----
From: adslmib-bounces <at> ietf.org [mailto:adslmib-bounces <at> ietf.org]On Behalf Of Frank Chao (fchao)
Sent: Tuesday, May 17, 2005 6:47 PM
To: adslmib <at> ietf.org
Subject: [Adslmib] some counters related to ATM Cell in G.997.1

Hi,
 
   We would like to know that is there standard MIB has cover some counters related to ATM Cell in G.997.1, such as
 
 

NE-HEC-violation-Count

(HEC-P)

Count of number of occurrences of a near-end hec anomaly in the ATM Data Path

NE-Delineated-total-cell-count (CD-P)

Near-End count of the total number of cells passed through the cell delineation and HEC function process operating on the ATM data Path while in SYNC state

NE-Usr-Total-Cell-Count

(CU-P)

 

Near-End count of the total number cells delivered to ATU-C

NE-Idle-Cell-Bit-Error-Count (IBE-P)

Near-End count of the number of bit errors in the idle cell payload received in the ATM data path at the near end.

FE-HEC-violation-Count

(HEC-P)

Count of number of occurrences of the far-end hec anomaly in the ATM Data Path

FE-Delineated-total-cell-count (CD-P)

Far-End count of the total number of cells passed through the cell delineation and HEC function process operating on the ATM data Path while in SYNC state

FE-Usr-Total-Cell-Count

(CU-P)

 

Far-End count of the total number cells delivered to ATU-R

FE-Idle-Cell-Bit-Error-Count (IBE-P)

Far-End count of the number of bit errors in the idle cell payload received in the ATM data path at the far end.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Thanks,
 
Frank
 
_______________________________________________
Adslmib mailing list
Adslmib <at> ietf.org
https://www1.ietf.org/mailman/listinfo/adslmib
IESG Secretary | 18 May 20:06 2005
Picon

WG Review: Recharter of ADSL MIB (adslmib)

A modified charter has been submitted for the ADSL MIB (adslmib) working group
in the Operations and Management Area of the IETF. The IESG has not made any
determination as yet. The modified charter is provided below for informational
purposes only. Please send your comments to the IESG mailing list
(iesg <at> ietf.org) by May 25th.

+++

ADSL MIB (adslmib)
------------------

Current Status: Active Working Group

Chair(s):
Bob Ray <rray <at> pesa.com>
Michael Sneed <sneedmike <at> hotmail.com>

Operations and Management Area Director(s):
Bert Wijnen <bwijnen <at> lucent.com>
David Kessens <david.kessens <at> nokia.com>

Operations and Management Area Advisor:
Bert Wijnen <bwijnen <at> lucent.com>

Technical Advisor(s):
Randy Presuhn <randy_presuhn <at> mindspring.com>

Mailing Lists:
General Discussion: adslmib <at> ietf.org
To Subscribe: https://www1.ietf.org/mailman/listinfo/adslmib
Archive: http://www.ietf.org/mail-archive/web/adslmib/index.html

Description of Working Group:

The working group will define a set of managed objects to be used for
management of newer versions of Asymmetric Digital Subscriber Line
(ADSL), called ADSL2 and ADSLplus, as defined in ITU-T Recommendation
G.997.1 (2003) and ITU-T Recommendation G.997.1 Amendment 1 (December
12, 2003). 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 this MIB.

(New) Goals and Milestones:

[.. dropped all the DONE items for now]

May 05 Initial WG Internet-Draft covering ADSL2 management objects.
June 05 Integrate working group changes and produce revised draft.
Sept 05 Complete WG last call on ADSL2 MIB.
Oct 05 Submit ADSL2 MIB to IESG for consideration as Proposed Standard.
Dec 05 Re-charter or close down.

_______________________________________________
IETF-Announce mailing list
IETF-Announce <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce


Gmane