headers
Moti Morgenstern | 26 Feb 2007 08:34

draft-ietf-adslmib-vdsl2-02.txt

Hello all,

I've submitted the -02 version to the internet-drafts.

I want to thank Uwe Pauluhn (infineon), John Boyle (Alcatel)

and of course Clay Sikes (Paradyne) for their comments.

Not all comments were already implemented, including those

that mentioned few G.997.1 objects that are (still) missing. The

editors need more time and at least one more draft to cover

all objects.

Here are the main changes included in this revision

compared to -01 version.

1) Created new tables for line/signal attenuation and SNR margin

    measurements, Xdsl2LineBandEntry and xdsl2SCStatusBandTable.

    One table reflects the dynamic changes in those measurements

    while the second one records the measurements next to the

    recent loop diagnostics

2) Created a new textual convention, Xdsl2Band, that serves

     for indexing tables which (also) refer to vdsl2 bands and

     complements Xdsl2Direction.

3) In Section 2.9, replaced the phrase:

"The xdsl2LStatusStatusXtur and adsl2LStatusStatusXtuc" with:

"The xdsl2LineStatusXtur and xdsl2LineStatusXtuc" 

4) For the xdsl2SCStatusSnrMargin object:

Replaced the phrase:

"received at the XTU (XTU-R on downstream direction and XATU-C" with:

"received at the XTU (XTU-R on downstream direction and XTU-C"

5) xDsl2SCStatusMainTable =>

    reverts to RFC 4706 name: xDsl2SCStatusTable.

   Added new: xDsl2SCStatusBandTable.

 

6)  xDsl2SCStatusTable => renamed to xDsl2SCStatusSegmentTable.

7) Implemented all UPBO, DPBO, RFIBANDS related support.

    Also added two Textual Conventions for D/UPBO

8) Implemented changes based on Clay Sikes' comments from 14/10/06.

    Clay sent 66 comments and the editors agreed with most of them.

    Note that there were few comments that the editors didn't accept, such

    as adding "running counters", and use of IMPLIED for

    profile names (Clay withdrawn from that). Other comments, all involve

    adding description here and there, are delayed to a future version.

    

9) Added xdsl2LineConfProfModeSpecBandUsTable for few band level

    parameters that are required specifically for VDSL2 line configuration.

10) Replaced the references to the ADSL2 draft with references to RFC 4706

11) Updated section 2.1.1 ("General IF-MIB Integration (RFC 2863)")

      according to RFC 4706

12) Changed 2.1.2 in Figure 1 near ifType

13) Removed one or two editor's comments. More comments are still there.

14) Replaced references to TR-090 with references to TR-129. Moved the

       DSL Forum reference to the Informative References

15)  Added text for Xdsl2UpboKLF and Xdsl2BandUs

16) In the description of Xdsl2LinePmMode I changed "(L2)" to "(L1/L2)".

17) Corrected few spelling errors.



Best Regards,

Moti Morgenstern



_______________________________________________
Adslmib mailing list
Adslmib <at> ietf.org
https://www1.ietf.org/mailman/listinfo/adslmib
Permalink | Reply | 0 comments |
headers
Internet-Drafts | 26 Feb 2007 21:50
Picon
Favicon

I-D ACTION:draft-ietf-adslmib-gbond-mib-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		: xDSL multi-pair bonding (G.Bond) MIB
	Author(s)	: E. Beili, et al.
	Filename	: draft-ietf-adslmib-gbond-mib-00.txt
	Pages		: 33
	Date		: 2007-2-26
	
   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 GBOND-ATM-MIB, GBOND-ETH-MIB and
   GBOND-TDIM-MIB respectively.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

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-gbond-mib-00.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

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv <at> ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-adslmib-gbond-mib-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
Attachment: message/external-body, 141 bytes
Attachment (draft-ietf-adslmib-gbond-mib-00.txt): message/external-body, 69 bytes
_______________________________________________
Adslmib mailing list
Adslmib <at> ietf.org
https://www1.ietf.org/mailman/listinfo/adslmib
Permalink | Reply | 0 comments |
headers
Internet-Drafts | 27 Feb 2007 21:50
Picon
Favicon

I-D ACTION:draft-ietf-adslmib-vdsl2-02.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)	: M. Morgenstern, et al.
	Filename	: draft-ietf-adslmib-vdsl2-02.txt
	Pages		: 194
	Date		: 2007-2-27
	
This document defines a Management Information Base (MIB) module for
   use with network management protocols in the IfQueueBlockernet
   community.  In particular, it describes objects used for managing
   parameters of the "Very High Speed Digital Subscriber Line 2 (VDSL2)"
   inter   and ADSL2+ interfaces.
face type, which are also applicable for managing ADSL, ADSL2,

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

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

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv <at> ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-adslmib-vdsl2-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
Attachment: message/external-body, 137 bytes
Attachment (draft-ietf-adslmib-vdsl2-02.txt): message/external-body, 69 bytes
_______________________________________________
Adslmib mailing list
Adslmib <at> ietf.org
https://www1.ietf.org/mailman/listinfo/adslmib
Permalink | Reply | 0 comments |
headers
Menachem Dodge | 28 Feb 2007 17:22

New drafts are available.

Hi,
 
    The common xDSL G.Bond MIB initial draft has been posted and is available on the WG web page. Many thanks to Edward for his efforts in producing this document.  Unfortunately the initial drafts of the remaining xDSL G.Bond MIBs are not yet available but I hope that these will be available soon.
 
    In addition, the Vdsl2 draft version 02 has been posted and is available on the web page.  Many thanks to Umberto, Scott and Moti for producing this document.
 
   
Best Regards,
Menachem
 
_______________________________________________
Adslmib mailing list
Adslmib <at> ietf.org
https://www1.ietf.org/mailman/listinfo/adslmib
Permalink | Reply | 0 comments |
headers
Uri Shabi | 28 Feb 2007 16:45
Favicon

draft-ietf-adslmib-gbond-mib-00.txt

Hi all,
I was not involved in your MIB process until now and would like to give
my comments,

1. para 4.1.5 ifSpeed section reads the following:
"For the GBS it is the sum of the current operating data rates of all
BCEs in the aggregation group, without the encapsulation overhead and
G.Bond overhead, but accounting for the Inter-Frame Gaps (IFG)"
As I understand the IFG refers to Ethernet medium but the GBS of type
g9981&3 are not Ethernet.

2. Looking at the G.998.2 and 802.3ah EFM bonding, these are almost the
same thing. AS I understand on the MIB progress, there are the EFM-Cu
and the GBOND-ETH, why to do two MIBs and not keep with a single one?

3. Where can I get WT-157?

Appreciate your comments, Uri.
Permalink | Reply | 2 comments |
headers
frank.van_der_putten | 1 Mar 2007 16:43
Picon

Re: draft-ietf-adslmib-gbond-mib-00.txt


I cannot find this adslmib-gbond-mib-00.txt document on the adslmib 
webpage.  Where is it?

WT-157 = Management Framework for xDSL Bonding
It is on DSLF website for DSLForum members download

Frank

Uri Shabi wrote:

> Hi all,
> I was not involved in your MIB process until now and would like to give
> my comments,
>
> 1. para 4.1.5 ifSpeed section reads the following:
> "For the GBS it is the sum of the current operating data rates of all
> BCEs in the aggregation group, without the encapsulation overhead and
> G.Bond overhead, but accounting for the Inter-Frame Gaps (IFG)"
> As I understand the IFG refers to Ethernet medium but the GBS of type
> g9981&3 are not Ethernet.
>
> 2. Looking at the G.998.2 and 802.3ah EFM bonding, these are almost the
> same thing. AS I understand on the MIB progress, there are the EFM-Cu
> and the GBOND-ETH, why to do two MIBs and not keep with a single one?
>
> 3. Where can I get WT-157?
>
> Appreciate your comments, Uri.
>
>
>
> _______________________________________________
> Adslmib mailing list
> Adslmib <at> ietf.org
> https://www1.ietf.org/mailman/listinfo/adslmib
>
Permalink | Reply | 1 comment |
headers
Menachem Dodge | 1 Mar 2007 21:07

RE: draft-ietf-adslmib-gbond-mib-00.txt

Hello Frank,

	It is in the Internet-Drafts section on the web page. You may
need to refresh your browser or exit and 
open it again, as this page was updated in the last 24 hours.

	Best Regards,
	Menachem.

-----Original Message-----
From: frank.van_der_putten <at> alcatel-lucent.be
[mailto:frank.van_der_putten <at> alcatel-lucent.be] 
Sent: Thursday, March 01, 2007 5:44 PM
To: Uri Shabi
Cc: adslmib <at> ietf.org
Subject: Re: [Adslmib] draft-ietf-adslmib-gbond-mib-00.txt

I cannot find this adslmib-gbond-mib-00.txt document on the adslmib 
webpage.  Where is it?

WT-157 = Management Framework for xDSL Bonding
It is on DSLF website for DSLForum members download

Frank

Uri Shabi wrote:

> Hi all,
> I was not involved in your MIB process until now and would like to
give
> my comments,
>
> 1. para 4.1.5 ifSpeed section reads the following:
> "For the GBS it is the sum of the current operating data rates of all
> BCEs in the aggregation group, without the encapsulation overhead and
> G.Bond overhead, but accounting for the Inter-Frame Gaps (IFG)"
> As I understand the IFG refers to Ethernet medium but the GBS of type
> g9981&3 are not Ethernet.
>
> 2. Looking at the G.998.2 and 802.3ah EFM bonding, these are almost
the
> same thing. AS I understand on the MIB progress, there are the EFM-Cu
> and the GBOND-ETH, why to do two MIBs and not keep with a single one?
>
> 3. Where can I get WT-157?
>
> Appreciate your comments, Uri.
>
>
>
> _______________________________________________
> Adslmib mailing list
> Adslmib <at> ietf.org
> https://www1.ietf.org/mailman/listinfo/adslmib
>

_______________________________________________
Adslmib mailing list
Adslmib <at> ietf.org
https://www1.ietf.org/mailman/listinfo/adslmib
Permalink | Reply | 0 comments |

Gmane