I-D ACTION:draft-ietf-adslmib-vdsl-11.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 Lines (VDSL)
	Author(s)	: B. Ray, R. Abbi
	Filename	: draft-ietf-adslmib-vdsl-11.txt
	Pages		: 68
	Date		: 2003-9-2
	
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 Very High Speed
Digital Subscriber Line (VDSL) interfaces.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-adslmib-vdsl-11.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

I-D ACTION:draft-ietf-adslmib-hc-tc-05.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		: High Capacity Textual Conventions for MIB Modules 
                          Using Performance History Based on 15 Minute Intervals
	Author(s)	: B. Ray, R. Abbi
	Filename	: draft-ietf-adslmib-hc-tc-05.txt
	Pages		: 10
	Date		: 2003-9-2
	
This document presents a set of High Capacity Textual Conventions 
for use in MIB modules which require performance history based upon 
15 minute intervals.  The Textual Conventions defined in this 
document extend the conventions presented in RFC 2493 to 64 bit 
resolution using the conventions presented in RFC 2856.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-adslmib-hc-tc-05.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-adslmib-hc-tc-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Fwd: WG Action: RECHARTER: ADSL MIB (adslmib)

>From: The IESG <iesg-secretary <at> ietf.org>
>To: IETF-Announce: ;
>CC: Michael Sneed <sneedmike <at> hotmail.com>
>Subject: WG Action: RECHARTER: ADSL MIB (adslmib)
>Date: Wed, 03 Sep 2003 15:44:04 -0400
>
>The charter of the ADSL MIB (adslmib) Working Group in the Operations and
>Management Area of the IETF has been updated. For additional information,
>please contact the Area Directors or the Working Group Chair.
>
>ADSL MIB (adslmib)
>-------------------
>
>Current Status: Active Working Group
>
>Chair(s):
>Michael Sneed <sneedmike <at> hotmail.com>
>
>Operations and Management Area Director(s):
>Randy Bush <randy <at> psg.com>
>Bert Wijnen <bwijnen <at> lucent.com>
>
>Operations and Management Area Advisor:
>Bert Wijnen <bwijnen <at> lucent.com>
>
>Technical Advisor(s):
>Randy Presuhn <randy_presuhn <at> mindspring.com>
>
>Mailing Lists:

RE: Fwd: WG Action: RECHARTER: ADSL MIB (adslmib)

Hi All,

	Now that the recharter is in place I would like to offer my two
individual, draft LCS extension
MIB, submissions to the working group and propose that the working group
accept these as the 
starting point for its work on the line code specific extension managed
objects as outlined in the
new charter.
	The drafts can be found at the following URLS:

	
http://www.ietf.org/internet-drafts/draft-dodge-adslmib-vdsl-ext-mcm-01.txt

http://www.ietf.org/internet-drafts/draft-dodge-adslmib-vdsl-ext-scm-01.txt

	Should  these drafts be accepted, I have agreed to Mike's offer to
take up the responsibility 
of editorship together with Bob Ray who has kindly agreed to remain on as
co-editor with me. 

	Regards,

	Menachem Dodge

	Infineon Technologies

-----Original Message-----
From: Michael Sneed [mailto:sneedmike <at> hotmail.com]
Sent: Wednesday, September 03, 2003 11:52 PM

draft updates

All:

Per input from Bert Wijnen and Randy Presuhn (and belatedly, Felix
Flemisch), I updated the vdsl and hc-tc drafts (producing -11 and -05
respectively).

Here is a list of changes done:

1.  Fixed the problems noted by Felix in his email of June 17, 2003.
2.  Added "MUST, SHOULD, MAY" sentence to both drafts.
3.  Changed "counter are" to "counters are", page 8.
4.  Changed reference to RFC2575 to RFC2415, page 10.
5.  Changed RFC editor note to use Bert's suggestion that we use
    "transmission 97".
6.  Added persistence statement to tables that should be treated
    as persistent.
7.  Changed names of objects in vdslPhysTable to have a consistent
    prefix of vdslPhys.
8.  Changed names of objects in vdslPerfDataTable to have a consistent
    prefix of vdslPerfData.
9.  Changed names of objects in vdslPerfIntervalTable to have a
    consistent prefix of vdslPerfInterval.
10. Changed "portion of the" to "", page 1
11. Changed "its" to "their", page 7
12. Changed "SHOULD" to "should", page 10
13. Fixed indentation in bibliographic section
14. Updated security boilerplate per www.ops.ietf.org/mib-security.html
    (I hope!) in vdsl mib.
15. Replaced security section with Bert's text in hc-tc mib.

Re: draft updates

On Mon, 2003-09-08 at 12:47, Mike Thatcher wrote:

> > 4.  Changed reference to RFC2575 to RFC2415, page 10.
> 
> shouldn't this be RFC3415?
> 

Ooops.  That should read RFC3415.  The typo was in the 
email, not in the -11 draft.

Whew!

--

-- 
Bob Ray <rray <at> pesa.com>

(no subject)

[ NOTE: replies to sender, public comments to mibs <at> ops.ietf.org ]

Colleagues --

As those of you who saw the recent announcement on the IETF-Announce
list will know, instead of getting rechartered and reactivated the
ifmib WG got closed down.  That leaves the IF-MIB (RFC 2863) at
Draft Standard and the IF-INVERTED-STACK-MIB (RFC 2864) at Proposed
Standard.

It occurred to me that a useful interim step would be to collect the
implementation reports needed to advance RFC 2864 to Draft Standard,
and I have volunteered to do just that.  So, if you or your
organization has implemented the IF-INVERTED-STACK-MIB, I would
appreciate it if you would fill out the following template and
return it to me.  If you would prefer that your company's name not
be made public, please so indicate and its name will be omitted from
the public version of the implementation report (although it must be
disclosed to the IESG in order for the data to be included).

Note that the template below is intended to evaluate conformance
to the ifInvCompliance compliance statement, and consequently
requests information not only on the ifInvStackTable but also
on the ifStackTable and ifStackLastChange, which are defined in
IF-MIB.  Since ifInvCompliance does not have an OBJECT clause
that specifies a MIN-ACCESS of read-only for ifStackStatus, it
would be of particular interest to hear of implementations that
actually provide read-create access to that object.

In the template below please fill in the items in angle brackets

Advancing RFC 2864 (IF-INVERTED-STACK-MIB)

[ NOTE: replies to sender, public comments to mibs <at> ops.ietf.org ]

Colleagues --

As those of you who saw the recent announcement on the IETF-Announce
list will know, instead of getting rechartered and reactivated the
ifmib WG got closed down.  That leaves the IF-MIB (RFC 2863) at
Draft Standard and the IF-INVERTED-STACK-MIB (RFC 2864) at Proposed
Standard.

It occurred to me that a useful interim step would be to collect the
implementation reports needed to advance RFC 2864 to Draft Standard,
and I have volunteered to do just that.  So, if you or your
organization has implemented the IF-INVERTED-STACK-MIB, I would
appreciate it if you would fill out the following template and
return it to me.  If you would prefer that your company's name not
be made public, please so indicate and its name will be omitted from
the public version of the implementation report (although it must be
disclosed to the IESG in order for the data to be included).

Note that the template below is intended to evaluate conformance
to the ifInvCompliance compliance statement, and consequently
requests information not only on the ifInvStackTable but also
on the ifStackTable and ifStackLastChange, which are defined in
IF-MIB.  Since ifInvCompliance does not have an OBJECT clause
that specifies a MIN-ACCESS of read-only for ifStackStatus, it
would be of particular interest to hear of implementations that
actually provide read-create access to that object.

In the template below please fill in the items in angle brackets

Liason from the DSL Forum

Following is the text of a liason letter received from the DSL Forum.  The 
originals were in Word format; I have performed an automatic conversion to 
text for the purposes of the mailing list.  If anyone would prefer the 
original format, please send me an email and I will forward it to you.

Regards,

Mike

_________________________________________________________________
Get a FREE computer virus scan online from McAfee. 
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

5th September 2003

DSL Forum Liaison to:
Mike Sneed, IETF ADSLMIB Chair

From:
Gavin Young, DSL Forum Technical Committee Chair
gyoung <at> dslforum.org

Date: September 5th, 2003

Subject: DSL Forum Liaison to the IETF

Dear Mr. Sneed,

LCS MIBs

As no objections have been raised to the WG adopting the LCS MIB IDs 
submitted by Menachem and Bob, pursuant to our updated charter which 
includes this work, I suggest that the editors re-submit them as adslmib WG 
drafts so we can proceed with working on them as a group.

Regards,

Mike

_________________________________________________________________
Send and receive larger attachments with Hotmail Extra Storage.   
http://join.msn.com/?PAGE=features/es