From mailnull@www1.ietf.org Wed Apr 2 05:10:04 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02625 for ; Wed, 2 Apr 2003 05:10:04 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h32AYEu23817 for adslmib-archive@odin.ietf.org; Wed, 2 Apr 2003 05:34:14 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h32AYEK23814 for ; Wed, 2 Apr 2003 05:34:14 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02615 for ; Wed, 2 Apr 2003 05:09:33 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h32AW8K23728; Wed, 2 Apr 2003 05:34:08 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h32AV9K23683 for ; Wed, 2 Apr 2003 05:31:09 -0500 Received: from relay3.clb.oleane.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02515 for ; Wed, 2 Apr 2003 05:06:28 -0500 (EST) Received: from oleane (upper-side.rain.fr [194.250.212.114]) by relay3.clb.oleane.net with SMTP id h32A8rBr013202 for ; Wed, 2 Apr 2003 12:08:54 +0200 Message-ID: <01a101c2f900$0d5fe5e0$0601a8c0@oleane.com> From: "Peter Lewis" To: Date: Wed, 2 Apr 2003 12:10:13 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_019E_01C2F910.D0626EE0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Subject: [Adslmib] TVoDSL 2004 CONFERENCE Sender: adslmib-admin@ietf.org Errors-To: adslmib-admin@ietf.org X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_019E_01C2F910.D0626EE0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =20 TVoDSL 2004 CONFERENCE Broadcasting TV content over ADSL As ADSL access becomes more widespread, new markets for this technology = will start to materialize.=20 TV over ADSL is one of them. Major manufacturing, economic and = regulatory players in this area will share their experience at the = TVoDSL Conference, to take place in Paris on January 20 to 23, 2004.=20 =20 A call for proposal is online at: http://www.upperside.fr/tvodsl04/tvodsl04intro.htm ------=_NextPart_000_019E_01C2F910.D0626EE0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

TVoDSL 2004 = CONFERENCE
Broadcasting TV content over ADSL

As ADSL access becomes more widespread, new = markets=20 for this technology will start to materialize.
TV over ADSL is one = of them.=20 Major manufacturing, economic and regulatory players in this area will = share=20 their experience at the TVoDSL Conference, to take place in Paris on = January 20 to 23, 2004.

A call for proposal is online at:

http://www.up= perside.fr/tvodsl04/tvodsl04intro.htm

------=_NextPart_000_019E_01C2F910.D0626EE0-- _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Mon Apr 7 09:23:31 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19198 for ; Mon, 7 Apr 2003 09:23:31 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h37DRiR09954 for adslmib-archive@odin.ietf.org; Mon, 7 Apr 2003 09:27:44 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h37DRi809951 for ; Mon, 7 Apr 2003 09:27:44 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19190 for ; Mon, 7 Apr 2003 09:22:40 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h37DRF809922; Mon, 7 Apr 2003 09:27:15 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h376Hs812691 for ; Mon, 7 Apr 2003 02:17:54 -0400 Received: from smtp.nlc.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00877 for ; Mon, 7 Apr 2003 02:13:17 -0400 (EDT) Received: from exchange4.nlc.com (exchange4.nlc.com [10.0.0.85]) by smtp.nlc.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h376Fh217807; Sun, 6 Apr 2003 23:15:44 -0700 (PDT) Received: by exchange4.nlc.com with Internet Mail Service (5.5.2653.19) id ; Sun, 6 Apr 2003 23:17:09 -0700 Message-ID: <50859C0B9DE9D411811F009027B11DAC015D3F4D@exchange4.nlc.com> From: "Say, Sabit" To: Flemisch Felix Cc: "'adslmib@ietf.org'" , "'rajesh.abbi@alcatel.com'" , "'moti.morgenstern@inoviatele.com'" , "'rray@pesa.com'" , "'sneedmike@hotmail.com'" , "'greg.bathrick@nokia.com'" , Boll Norbert , Forster Josef Date: Sun, 6 Apr 2003 23:17:08 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Adslmib] RE: dsl2002.298 and SCM LCS MIB Sender: adslmib-admin@ietf.org Errors-To: adslmib-admin@ietf.org X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , Felix, Sorry about not responding to this quickly. I do not receive email from the ietf? list. Do I need to subscribe to some email list or perhaps you can forward relevant correspondence, as you did earlier. I am glad to hear that not including line code specific parameters in the basic MIB is still a valid course. I also agree that we have missed a couple of generic parameters that specify the configuration of the interleaver and the RS frame. The missed parameters should be needed not only for SCM but MCM as well. The first parameter should be called "target burst protection" and it applies only to the Slow channel (Interleaved, if you like) I included the qualifier "target" because the selection of linecode specific intleaver parameters would try to achieve this target, but the result could end up being lower or higher. The parameter applies independently to Upstream and Downstream. I prefer the unit microseconds, because the values are sub-ms. A reasonable range would be 0 to 1000 microseconds in 20 microsecond increments. The other parameter should be called "Maximum redundancy overhead" and it applies only to the Fast channel (Not interleaved, if you like). I included the qualifier "maximum" because the selection of linecode specific framing parameters would use no more, but equal to or less than this percentage, in determining the number of FEC octets. The parameter applies independently to Upstream and Downstream. The % unit is OK. The reasonable range would be 0 to 50% in 1% increments. If this is agreed so far, we can provide a detailed description. Sabit NLC -----Original Message----- From: Flemisch Felix [mailto:felix.flemisch@siemens.com] Sent: Sunday, March 30, 2003 2:42 PM To: 'ssay@nlc.com' Cc: 'adslmib@ietf.org' Subject: dsl2002.298 and SCM LCS MIB Hello Sabit, Moti Morgenstern wrote on Sunday 02 March 2003 (see msg00178.html): "For the VDSL, the DSLF decided to extract the line code specific parameters from the basic MIB only after the members reviewed a contribution from NLC (dsl2002.298) claiming that SCM specific parameters can be determined according to other, generic type, parameters. The problem is that the DSLF discovered only recently that few of those generic parameters are not present in the MIB so configuring a SCM line is impossible without additional parameters. So, I suggest adding the two generic parameters Overhead (%) and Burst Protection (ms) to the MIB, in order to allow determining the Fast Codeword Size and FEC Size for SCM links." But Moti is not aware of the semantics of the proposed parameters (see msg00191.html): "NLC ... to ... provide soon the definitions for the two alternative parameters they mentioned (i.e., overhead-percentage and burst protection)". Therefore, I would like to ask you, Sabit, to resolve asap these issues and the following questions and request of mine (see msg00183.html): Are you proposing to add the parameters vdslChanOverhead (UNITS "%") and vdslChanBurstProtection (UNITS "ms") to VdslChanEntry, which shall be not for ifType interleave(124)? Please provide a formal DESCRIPTION and how they are used for SCM lines. After adding these two parameters, is it then clear that basic configuration of SCM lines is possible, or might something else be needed or useful? If this is the case, and since these extensions are compatible with TR-057 and RFC 2662, I agree to add them to IETF's VDSL MIB and don't see any reason why anybody should not agree. Best regards, Felix Flemisch -------------------------------------- SIEMENS AG Information and Communication Networks Carrier Products Systems Engineering Hofmannstr. 51 D-81359 Munich Tel +49 89 722 62175 e-Mail felix.flemisch@siemens.com -------------------------------------- _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Fri Apr 18 10:09:47 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14620 for ; Fri, 18 Apr 2003 10:09:47 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3IEJOF19016 for adslmib-archive@odin.ietf.org; Fri, 18 Apr 2003 10:19:24 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3IEJO819013 for ; Fri, 18 Apr 2003 10:19:24 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14568 for ; Fri, 18 Apr 2003 10:09:16 -0400 (EDT) Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 196Wac-0007gx-00 for adslmib-web-archive@ietf.org; Fri, 18 Apr 2003 10:11:42 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 196Wac-0007gt-00 for adslmib-web-archive@ietf.org; Fri, 18 Apr 2003 10:11:42 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3IEJG819004; Fri, 18 Apr 2003 10:19:16 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3IEIw818990 for ; Fri, 18 Apr 2003 10:18:58 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14515 for ; Fri, 18 Apr 2003 10:08:50 -0400 (EDT) Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 196WaC-0007gh-00 for adslmib@ietf.org; Fri, 18 Apr 2003 10:11:16 -0400 Received: from ant.hiwaay.net ([216.180.54.10] helo=mail.hiwaay.net) by ietf-mx with esmtp (Exim 4.12) id 196WaC-0007gd-00 for adslmib@ietf.org; Fri, 18 Apr 2003 10:11:16 -0400 Received: from mailserver ([216.180.38.253]) by mail.hiwaay.net (8.12.9/8.12.9) with ESMTP id h3IEBVZc879458 for ; Fri, 18 Apr 2003 09:11:31 -0500 (CDT) Received: from rray ([192.168.0.108]) by pesahsv.com ([127.0.0.1]) with SMTP (MDaemon.PRO.v6.7.2.R) for ; Fri, 18 Apr 2003 09:11:30 -0500 From: "Bob Ray" To: Date: Fri, 18 Apr 2003 09:11:29 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-Reply-To: <3D72C18DF140D311A54F0008C7DBAC8D028512C7@mchh252e.mchh.siemens.de> X-MDRemoteIP: 192.168.0.108 X-Return-Path: rray@pesa.com X-MDaemon-Deliver-To: adslmib@ietf.org Content-Transfer-Encoding: 7bit Subject: [Adslmib] -08 revision Sender: adslmib-admin@ietf.org Errors-To: adslmib-admin@ietf.org X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit I've submitted the -08 revision to the internet drafts editor. As far as I know, all that is missing are the definitions for two objects: vdslChanOverhead vdshChanBurstProtection I put "TBD" in the definitions for now. I believe Felix Flemisch issued a request for these definitions over a month ago. I echo this request. If anyone needs a copy before the draft editor gets it posted, please let me know! Regards, Bob Ray PESA Switching Systems _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Sat Apr 19 02:29:31 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA19049 for ; Sat, 19 Apr 2003 02:29:31 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3J6dRU23020 for adslmib-archive@odin.ietf.org; Sat, 19 Apr 2003 02:39:27 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3J6dR823017 for ; Sat, 19 Apr 2003 02:39:27 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA19044 for ; Sat, 19 Apr 2003 02:29:00 -0400 (EDT) Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 196lsj-0003RA-00 for adslmib-web-archive@ietf.org; Sat, 19 Apr 2003 02:31:25 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 196lsi-0003R6-00 for adslmib-web-archive@ietf.org; Sat, 19 Apr 2003 02:31:24 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3J6dJ823007; Sat, 19 Apr 2003 02:39:19 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3J6cP822981 for ; Sat, 19 Apr 2003 02:38:25 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA19039 for ; Sat, 19 Apr 2003 02:27:58 -0400 (EDT) Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 196lri-0003R3-00 for adslmib@ietf.org; Sat, 19 Apr 2003 02:30:22 -0400 Received: from beamer.mchh.siemens.de ([194.138.158.163]) by ietf-mx with esmtp (Exim 4.12) id 196lri-0003Qz-00 for adslmib@ietf.org; Sat, 19 Apr 2003 02:30:22 -0400 Received: from moody.mchh.siemens.de ([139.21.205.85]) by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id IAA25776; Sat, 19 Apr 2003 08:30:36 +0200 (MET DST) Received: from mchh248e.mchh.siemens.de (mchh248e.mchh.siemens.de [139.21.200.58]) by moody.mchh.siemens.de (8.9.3/8.9.1) with ESMTP id IAA12534; Sat, 19 Apr 2003 08:30:35 +0200 (MET DST) Received: by mchh248e.mchh.siemens.de with Internet Mail Service (5.5.2653.19) id ; Sat, 19 Apr 2003 08:30:16 +0200 Message-ID: <3D72C18DF140D311A54F0008C7DBAC8D028512D7@mchh252e.mchh.siemens.de> From: Flemisch Felix To: "'ssay@nlc.com'" , "'rray@pesa.com'" Cc: "'adslmib@ietf.org'" Date: Sat, 19 Apr 2003 08:30:14 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C3063D.231DC0B0" Subject: [Adslmib] RE: Adslmib digest, Vol 1 #84 - 1 msg Sender: adslmib-admin@ietf.org Errors-To: adslmib-admin@ietf.org X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C3063D.231DC0B0 Content-Type: text/plain; charset="ISO-8859-1" Hi Sabit and Ray, thanks, Ray, for the awaited update. From my point of view the best thing would be if you two get together immediately to replace the TBD parts in -08 by proper contents (and inform the internet drafts editor that an update is on its way). I had some questions on the issue but they seem not easy to be answered by e-mail. Sabit, you announced to provide a detailed description (see attachment). Thanks, Felix (on holiday until 28 April) From: "Bob Ray" To: Date: Fri, 18 Apr 2003 09:11:29 -0500 Subject: [Adslmib] -08 revision I've submitted the -08 revision to the internet drafts editor. As far as I know, all that is missing are the definitions for two objects: vdslChanOverhead vdshChanBurstProtection I put "TBD" in the definitions for now. I believe Felix Flemisch issued a request for these definitions over a month ago. I echo this request. If anyone needs a copy before the draft editor gets it posted, please let me know! Regards, Bob Ray PESA Switching Systems ------_=_NextPart_000_01C3063D.231DC0B0 Content-Type: message/rfc822 Content-Description: RE: dsl2002.298 and SCM LCS MIB Message-ID: <50859C0B9DE9D411811F009027B11DAC015D3F4D@exchange4.nlc.com> From: "Say, Sabit" To: Flemisch Felix Cc: "'adslmib@ietf.org'" , "'rajesh.abbi@alcatel.com'" , "'moti.morgenstern@inoviatele.com'" , "'rray@pesa.com'" , "'sneedmike@hotmail.com'" , "'greg.bathrick@nokia.com'" , Boll Norbert , Forster Josef Subject: RE: dsl2002.298 and SCM LCS MIB Date: Mon, 7 Apr 2003 08:17:08 +0200 Return-Receipt-To: "Say, Sabit" MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="ISO-8859-1" Felix, Sorry about not responding to this quickly. I do not receive email from the ietf? list. Do I need to subscribe to some email list or perhaps you can forward relevant correspondence, as you did earlier. I am glad to hear that not including line code specific parameters in the basic MIB is still a valid course. I also agree that we have missed a couple of generic parameters that specify the configuration of the interleaver and the RS frame. The missed parameters should be needed not only for SCM but MCM as well. The first parameter should be called "target burst protection" and it applies only to the Slow channel (Interleaved, if you like) I included the qualifier "target" because the selection of linecode specific intleaver parameters would try to achieve this target, but the result could end up being lower or higher. The parameter applies independently to Upstream and Downstream. I prefer the unit microseconds, because the values are sub-ms. A reasonable range would be 0 to 1000 microseconds in 20 microsecond increments. The other parameter should be called "Maximum redundancy overhead" and it applies only to the Fast channel (Not interleaved, if you like). I included the qualifier "maximum" because the selection of linecode specific framing parameters would use no more, but equal to or less than this percentage, in determining the number of FEC octets. The parameter applies independently to Upstream and Downstream. The % unit is OK. The reasonable range would be 0 to 50% in 1% increments. If this is agreed so far, we can provide a detailed description. Sabit NLC -----Original Message----- From: Flemisch Felix [mailto:felix.flemisch@siemens.com] Sent: Sunday, March 30, 2003 2:42 PM To: 'ssay@nlc.com' Cc: 'adslmib@ietf.org' Subject: dsl2002.298 and SCM LCS MIB Hello Sabit, Moti Morgenstern wrote on Sunday 02 March 2003 (see msg00178.html): "For the VDSL, the DSLF decided to extract the line code specific parameters from the basic MIB only after the members reviewed a contribution from NLC (dsl2002.298) claiming that SCM specific parameters can be determined according to other, generic type, parameters. The problem is that the DSLF discovered only recently that few of those generic parameters are not present in the MIB so configuring a SCM line is impossible without additional parameters. So, I suggest adding the two generic parameters Overhead (%) and Burst Protection (ms) to the MIB, in order to allow determining the Fast Codeword Size and FEC Size for SCM links." But Moti is not aware of the semantics of the proposed parameters (see msg00191.html): "NLC ... to ... provide soon the definitions for the two alternative parameters they mentioned (i.e., overhead-percentage and burst protection)". Therefore, I would like to ask you, Sabit, to resolve asap these issues and the following questions and request of mine (see msg00183.html): Are you proposing to add the parameters vdslChanOverhead (UNITS "%") and vdslChanBurstProtection (UNITS "ms") to VdslChanEntry, which shall be not for ifType interleave(124)? Please provide a formal DESCRIPTION and how they are used for SCM lines. After adding these two parameters, is it then clear that basic configuration of SCM lines is possible, or might something else be needed or useful? If this is the case, and since these extensions are compatible with TR-057 and RFC 2662, I agree to add them to IETF's VDSL MIB and don't see any reason why anybody should not agree. Best regards, Felix Flemisch -------------------------------------- SIEMENS AG Information and Communication Networks Carrier Products Systems Engineering Hofmannstr. 51 D-81359 Munich Tel +49 89 722 62175 e-Mail felix.flemisch@siemens.com -------------------------------------- ------_=_NextPart_000_01C3063D.231DC0B0-- _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Mon Apr 21 09:16:37 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14403 for ; Mon, 21 Apr 2003 09:16:37 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3LDRfc29610 for adslmib-archive@odin.ietf.org; Mon, 21 Apr 2003 09:27:41 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3LDRf829607 for ; Mon, 21 Apr 2003 09:27:41 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14397 for ; Mon, 21 Apr 2003 09:16:06 -0400 (EDT) Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 197bBl-0000Ek-00 for adslmib-web-archive@ietf.org; Mon, 21 Apr 2003 09:18:29 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 197bBl-0000Eg-00 for adslmib-web-archive@ietf.org; Mon, 21 Apr 2003 09:18:29 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3LDRY829590; Mon, 21 Apr 2003 09:27:35 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3LBgN822761 for ; Mon, 21 Apr 2003 07:42:23 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09581; Mon, 21 Apr 2003 07:30:50 -0400 (EDT) Message-Id: <200304211130.HAA09581@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: adslmib@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Mon, 21 Apr 2003 07:30:50 -0400 Subject: [Adslmib] I-D ACTION:draft-ietf-adslmib-vdsl-08.txt Sender: adslmib-admin@ietf.org Errors-To: adslmib-admin@ietf.org X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , --NextPart 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-08.txt Pages : 65 Date : 2003-4-18 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 [T1E1311, T1E1011, T1E1013, ETSI2701, ETSI2702, ITU9931]. This document specifies a MIB module in a manner that is compliant to the SMIv2 (STD 58 [RFC2578, RFC2579, RFC2580]). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-adslmib-vdsl-08.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-08.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@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-adslmib-vdsl-08.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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-4-18131621.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-adslmib-vdsl-08.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-adslmib-vdsl-08.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-4-18131621.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Mon Apr 28 15:14:56 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11715 for ; Mon, 28 Apr 2003 15:14:56 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3SJJcI04707 for adslmib-archive@odin.ietf.org; Mon, 28 Apr 2003 15:19:38 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3SJJb804704 for ; Mon, 28 Apr 2003 15:19:37 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11653 for ; Mon, 28 Apr 2003 15:14:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19AE7D-0004pT-00 for adslmib-web-archive@ietf.org; Mon, 28 Apr 2003 15:16:39 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19AE7D-0004pP-00 for adslmib-web-archive@ietf.org; Mon, 28 Apr 2003 15:16:39 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3SJJH804675; Mon, 28 Apr 2003 15:19:17 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3SJIa804641 for ; Mon, 28 Apr 2003 15:18:36 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11546 for ; Mon, 28 Apr 2003 15:13:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19AE6E-0004ov-00 for adslmib@ietf.org; Mon, 28 Apr 2003 15:15:38 -0400 Received: from ant.hiwaay.net ([216.180.54.10] helo=mail.hiwaay.net) by ietf-mx with esmtp (Exim 4.12) id 19AE6D-0004os-00 for adslmib@ietf.org; Mon, 28 Apr 2003 15:15:37 -0400 Received: from mailserver ([216.180.38.253]) by mail.hiwaay.net (8.12.9/8.12.9) with ESMTP id h3SJGCHb934132 for ; Mon, 28 Apr 2003 14:16:12 -0500 (CDT) Received: from [192.168.0.122] ([192.168.0.122]) by pesahsv.com ([127.0.0.1]) with SMTP (MDaemon.PRO.v6.7.2.R) for ; Mon, 28 Apr 2003 14:16:10 -0500 From: Bob Ray Reply-To: rray@pesa.com To: adslmib mail list Content-Type: text/plain Message-Id: <1051557370.5314.5.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 28 Apr 2003 14:16:10 -0500 Content-Transfer-Encoding: 7bit X-MDRemoteIP: 192.168.0.122 X-Return-Path: rray@pesa.com X-MDaemon-Deliver-To: adslmib@ietf.org Content-Transfer-Encoding: 7bit Subject: [Adslmib] vdsl-08 question Sender: adslmib-admin@ietf.org Errors-To: adslmib-admin@ietf.org X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi. I propose that I remove the two objects vdslChanBurstProtection vdslChanOverhead from the -08 draft (producing a -09 draft) and move it ahead in the queue. Haven't heard any comments or suggestions in several weeks, so I guess no one really cares about the two objects (i.e. they are unimportant). If I don't hear any objections in the next day or so, I'll get -09 out. -- Bob Ray _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Tue Apr 29 02:40:25 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08570 for ; Tue, 29 Apr 2003 02:40:25 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3T6jLk06606 for adslmib-archive@odin.ietf.org; Tue, 29 Apr 2003 02:45:21 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3T6jK806603 for ; Tue, 29 Apr 2003 02:45:20 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08567 for ; Tue, 29 Apr 2003 02:39:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19AOoZ-0000ky-00 for adslmib-web-archive@ietf.org; Tue, 29 Apr 2003 02:42:07 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19AOoZ-0000kv-00 for adslmib-web-archive@ietf.org; Tue, 29 Apr 2003 02:42:07 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3T6jE806590; Tue, 29 Apr 2003 02:45:14 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3T6ir806555 for ; Tue, 29 Apr 2003 02:44:53 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08549; Tue, 29 Apr 2003 02:39:27 -0400 (EDT) From: Moti.Morgenstern@ecitele.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19AOo8-0000km-00; Tue, 29 Apr 2003 02:41:40 -0400 Received: from mink.ecitele.com ([147.234.1.100]) by ietf-mx with esmtp (Exim 4.12) id 19AOo7-0000kh-00; Tue, 29 Apr 2003 02:41:39 -0400 Received: from olive.ecitele.com (ilsmtp04.ecitele.com [147.234.8.125]) by mink.ecitele.com (8.12.8+Sun/8.12.8) with ESMTP id h3T6aspP025442; Tue, 29 Apr 2003 09:36:55 +0300 (IDT) Subject: Re: [Adslmib] vdsl-08 question To: rray@pesa.com Cc: adslmib@ietf.org, adslmib-admin@ietf.org X-Mailer: Lotus Notes Release 5.0.2b (Intl) 16 December 1999 Message-ID: Date: Tue, 29 Apr 2003 09:42:04 +0300 X-MIMETrack: Serialize by Router on ILSMTP04/ECI Telecom(Release 5.0.9a |January 7, 2002) at 04/29/2003 09:42:13 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: adslmib-admin@ietf.org Errors-To: adslmib-admin@ietf.org X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , Hi Bob, The main reason all SCM specific parameters were removed from the model is because there was an input from NLC to the DSLF (dsl2003.298) showing that with the existing generic parameters plus (new) vdslChanBurstProtection and vdslChanOverhead, one can configure a SCM line. So we should choose between including the generic parameters, according to Sabit's mail from 7-Apr-03, and the SCM parameters (vdslSCMConfProfileFastCodewordSize and vdslSCMConfProfileFastFecSize) according to your mail from 27-Mar-03. We cannot leave outside both the original and the alternative parameters, because there is no one who claims it is possible to configure a SCM link that way. Best regards, Moti Morgenstern Senior Systems Engineer ECI Telecoms Ltd. Inovia Broadband Access Division 30 Hasivim St. Petach Tikva, Israel 49133 Tel.: +972-3-9266258 Fax: +972-3-9268182 Cell: +972-55-786258 e-mail: Moti.Morgenstern@ecitele.com www.ecitele.com Bob Ray To: adslmib mail list Sent by: cc: adslmib-admin@ Subject: [Adslmib] vdsl-08 question ietf.org 28/04/03 22:16 Please respond to rray Hi. I propose that I remove the two objects vdslChanBurstProtection vdslChanOverhead from the -08 draft (producing a -09 draft) and move it ahead in the queue. Haven't heard any comments or suggestions in several weeks, so I guess no one really cares about the two objects (i.e. they are unimportant). If I don't hear any objections in the next day or so, I'll get -09 out. -- Bob Ray _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Tue Apr 29 09:21:16 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15923 for ; Tue, 29 Apr 2003 09:21:16 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3TDQKN08402 for adslmib-archive@odin.ietf.org; Tue, 29 Apr 2003 09:26:20 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3TDQK808399 for ; Tue, 29 Apr 2003 09:26:20 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15906 for ; Tue, 29 Apr 2003 09:20:46 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19AV4U-0002QL-00 for adslmib-web-archive@ietf.org; Tue, 29 Apr 2003 09:22:59 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19AV4U-0002QI-00 for adslmib-web-archive@ietf.org; Tue, 29 Apr 2003 09:22:58 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3TDQB808364; Tue, 29 Apr 2003 09:26:11 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3TDPN808329 for ; Tue, 29 Apr 2003 09:25:23 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15888 for ; Tue, 29 Apr 2003 09:19:49 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19AV3a-0002Pr-00 for adslmib@ietf.org; Tue, 29 Apr 2003 09:22:02 -0400 Received: from ant.hiwaay.net ([216.180.54.10] helo=mail.hiwaay.net) by ietf-mx with esmtp (Exim 4.12) id 19AV3Z-0002Po-00 for adslmib@ietf.org; Tue, 29 Apr 2003 09:22:01 -0400 Received: from mailserver ([216.180.38.253]) by mail.hiwaay.net (8.12.9/8.12.9) with ESMTP id h3TDMVHb645218 for ; Tue, 29 Apr 2003 08:22:31 -0500 (CDT) Received: from [192.168.0.122] ([192.168.0.122]) by pesahsv.com ([127.0.0.1]) with SMTP (MDaemon.PRO.v6.7.2.R) for ; Tue, 29 Apr 2003 08:22:27 -0500 Subject: Re: [Adslmib] vdsl-08 question From: Bob Ray Reply-To: rray@pesa.com To: Moti.Morgenstern@ecitele.com Cc: adslmib mail list In-Reply-To: References: Content-Type: text/plain Message-Id: <1051622547.2991.8.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 29 Apr 2003 08:22:27 -0500 Content-Transfer-Encoding: 7bit X-MDRemoteIP: 192.168.0.122 X-Return-Path: rray@pesa.com X-MDaemon-Deliver-To: adslmib@ietf.org Content-Transfer-Encoding: 7bit Sender: adslmib-admin@ietf.org Errors-To: adslmib-admin@ietf.org X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit On Tue, 2003-04-29 at 01:42, Moti.Morgenstern@ecitele.com wrote: > Hi Bob, > > The main reason all SCM specific parameters were removed from the model is > because there was an input from NLC to the DSLF (dsl2003.298) showing that > with the existing generic parameters plus (new) vdslChanBurstProtection and > vdslChanOverhead, one can configure a SCM line. So we should choose between > including the generic parameters, according to Sabit's mail from 7-Apr-03, > and the SCM parameters (vdslSCMConfProfileFastCodewordSize and > vdslSCMConfProfileFastFecSize) according to your mail from 27-Mar-03. > > We cannot leave outside both the original and the alternative parameters, > because there is no one who claims it is possible to configure a SCM link > that way. > > Best regards, > Moti Morgenstern > Hi Moti. I asked the list for two sentences (DESCRIPTION for these two objects). On the assumption SOMEONE/ANYONE would provide them, I removed all the other LCS objects from the draft. Since NO ONE has provided the two sentences in the two months since Felix first asked for them, and three weeks since I first asked for them, I assumed no one cared whether they were in or not. Hence, my post. As I understand the process, these two sentences are all that is keeping us from moving these two drafts to the RFC editor queue. Which is what I want to do. I did not see the presentation from NLC. One would think that they would be happy to provide the DESCRIPTIONs, no? -- Bob Ray _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Tue Apr 29 09:53:37 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19384 for ; Tue, 29 Apr 2003 09:53:37 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3TDwgg12116 for adslmib-archive@odin.ietf.org; Tue, 29 Apr 2003 09:58:42 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3TDwg812113 for ; Tue, 29 Apr 2003 09:58:42 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19328 for ; Tue, 29 Apr 2003 09:53:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19AVZo-0003RE-00 for adslmib-web-archive@ietf.org; Tue, 29 Apr 2003 09:55:20 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19AVZn-0003RB-00 for adslmib-web-archive@ietf.org; Tue, 29 Apr 2003 09:55:19 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3TDwF812090; Tue, 29 Apr 2003 09:58:15 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3TDvB812013 for ; Tue, 29 Apr 2003 09:57:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19215 for ; Tue, 29 Apr 2003 09:51:36 -0400 (EDT) From: Moti.Morgenstern@ecitele.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19AVYL-0003Ou-00 for adslmib@ietf.org; Tue, 29 Apr 2003 09:53:49 -0400 Received: from mink.ecitele.com ([147.234.1.100]) by ietf-mx with esmtp (Exim 4.12) id 19AVYI-0003OY-00 for adslmib@ietf.org; Tue, 29 Apr 2003 09:53:47 -0400 Received: from olive.ecitele.com (ilsmtp04.ecitele.com [147.234.8.125]) by mink.ecitele.com (8.12.8+Sun/8.12.8) with ESMTP id h3TDmnpP013961; Tue, 29 Apr 2003 16:48:50 +0300 (IDT) Subject: Re: [Adslmib] vdsl-08 question To: rray@pesa.com Cc: adslmib@ietf.org, "Say, Sabit" X-Mailer: Lotus Notes Release 5.0.2b (Intl) 16 December 1999 Message-ID: Date: Tue, 29 Apr 2003 16:54:00 +0300 X-MIMETrack: Serialize by Router on ILSMTP04/ECI Telecom(Release 5.0.9a |January 7, 2002) at 04/29/2003 04:54:16 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: adslmib-admin@ietf.org Errors-To: adslmib-admin@ietf.org X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , Bob, First we had a comprehensive solution in IETF based on LCS parameters. Then came NLC (actually they convinced the DSLF) and said it's better to use generic parameters. This is obviously a better solution once you have the detailed definitions. The PROBLEM is that Sabit doesn't receive email from the IETF (as he wrote on 18-Apr-2003). Therefore I added Sabit on CC and suggest that: - Sabit will add himself to the list :-) - Sabit (or his colleague) will at last find the time to provide the detailed spec of those two generic parameters. If nothing happens, we should return to the two "old and good" SCM specific parameters (for which we already have detailed definitions) and move them to the main profile table. They can and should be conditionally mandatory for SCM applications. Bye, Moti Morgenstern Senior Systems Engineer ECI Telecoms Ltd. Inovia Broadband Access Division 30 Hasivim St. Petach Tikva, Israel 49133 Tel.: +972-3-9266258 Fax: +972-3-9268182 Cell: +972-55-786258 e-mail: Moti.Morgenstern@ecitele.com www.ecitele.com Bob Ray To: Moti.Morgenstern@ecitele.com cc: adslmib mail list 29/04/03 16:22 Subject: Re: [Adslmib] vdsl-08 question Please respond to rray On Tue, 2003-04-29 at 01:42, Moti.Morgenstern@ecitele.com wrote: [snipped my original email] Hi Moti. I asked the list for two sentences (DESCRIPTION for these two objects). On the assumption SOMEONE/ANYONE would provide them, I removed all the other LCS objects from the draft. Since NO ONE has provided the two sentences in the two months since Felix first asked for them, and three weeks since I first asked for them, I assumed no one cared whether they were in or not. Hence, my post. As I understand the process, these two sentences are all that is keeping us from moving these two drafts to the RFC editor queue. Which is what I want to do. I did not see the presentation from NLC. One would think that they would be happy to provide the DESCRIPTIONs, no? -- Bob Ray _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Tue Apr 29 22:10:01 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21439 for ; Tue, 29 Apr 2003 22:10:01 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3U2FK222791 for adslmib-archive@odin.ietf.org; Tue, 29 Apr 2003 22:15:20 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3U2FK822788 for ; Tue, 29 Apr 2003 22:15:20 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21416 for ; Tue, 29 Apr 2003 22:09:30 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Ah4Q-0002f9-00 for adslmib-web-archive@ietf.org; Tue, 29 Apr 2003 22:11:42 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Ah4Q-0002f5-00 for adslmib-web-archive@ietf.org; Tue, 29 Apr 2003 22:11:42 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3U2FE822773; Tue, 29 Apr 2003 22:15:14 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3TN2j802576 for ; Tue, 29 Apr 2003 19:02:45 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15855 for ; Tue, 29 Apr 2003 18:57:00 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Ae47-0001Dn-00 for adslmib@ietf.org; Tue, 29 Apr 2003 18:59:11 -0400 Received: from smtp.nlc.com ([209.204.132.15]) by ietf-mx with esmtp (Exim 4.12) id 19Ae46-0001DJ-00 for adslmib@ietf.org; Tue, 29 Apr 2003 18:59:10 -0400 Received: from exchange4.nlc.com (exchange4.nlc.com [10.0.0.85]) by smtp.nlc.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h3TMwa516446; Tue, 29 Apr 2003 15:58:37 -0700 (PDT) Received: by exchange4.nlc.com with Internet Mail Service (5.5.2653.19) id ; Tue, 29 Apr 2003 15:58:41 -0700 Message-ID: <50859C0B9DE9D411811F009027B11DAC015D40ED@exchange4.nlc.com> From: "Say, Sabit" To: rray@pesa.com, Moti.Morgenstern@ecitele.com Cc: adslmib mail list Subject: RE: [Adslmib] vdsl-08 question Date: Tue, 29 Apr 2003 15:58:36 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: adslmib-admin@ietf.org Errors-To: adslmib-admin@ietf.org X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , If this is all you need: vdslChanOverhead OBJECT-TYPE SYNTAX Gauge32 UNITS "%" MAX-ACCESS read-only STATUS current DESCRIPTION "Channel overhead applies independently to downstream and upstream directions, and only to fast channel. It indicates the percentage of redundant octets to the total FEC block. The range is 0 to 100. In the case where the ifType is interleave(124), use noSuchObject." ::= { vdslChanEntry 4 } vdslChanBurstProtection OBJECT-TYPE SYNTAX Gauge32 UNITS "0.005 ms" MAX-ACCESS read-only STATUS current DESCRIPTION "Channel burst protection applies independently to downstream and upstream, and only to interleave (slow) channel. It indicates the correctable burst size with the interleaver settings. The range is 0 to 1.275 ms. In the case where the ifType is fast(125), use noSuchObject." ::= { vdslChanEntry 5 } -----Original Message----- From: Bob Ray [mailto:rray@pesa.com] Sent: Tuesday, April 29, 2003 9:22 AM To: Moti.Morgenstern@ecitele.com Cc: adslmib mail list Subject: Re: [Adslmib] vdsl-08 question On Tue, 2003-04-29 at 01:42, Moti.Morgenstern@ecitele.com wrote: > Hi Bob, > > The main reason all SCM specific parameters were removed from the model is > because there was an input from NLC to the DSLF (dsl2003.298) showing that > with the existing generic parameters plus (new) vdslChanBurstProtection and > vdslChanOverhead, one can configure a SCM line. So we should choose between > including the generic parameters, according to Sabit's mail from 7-Apr-03, > and the SCM parameters (vdslSCMConfProfileFastCodewordSize and > vdslSCMConfProfileFastFecSize) according to your mail from 27-Mar-03. > > We cannot leave outside both the original and the alternative parameters, > because there is no one who claims it is possible to configure a SCM link > that way. > > Best regards, > Moti Morgenstern > Hi Moti. I asked the list for two sentences (DESCRIPTION for these two objects). On the assumption SOMEONE/ANYONE would provide them, I removed all the other LCS objects from the draft. Since NO ONE has provided the two sentences in the two months since Felix first asked for them, and three weeks since I first asked for them, I assumed no one cared whether they were in or not. Hence, my post. As I understand the process, these two sentences are all that is keeping us from moving these two drafts to the RFC editor queue. Which is what I want to do. I did not see the presentation from NLC. One would think that they would be happy to provide the DESCRIPTIONs, no? -- Bob Ray _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Tue Apr 29 22:10:02 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21453 for ; Tue, 29 Apr 2003 22:10:02 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3U2FMS22813 for adslmib-archive@odin.ietf.org; Tue, 29 Apr 2003 22:15:22 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3U2FM822810 for ; Tue, 29 Apr 2003 22:15:22 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21420 for ; Tue, 29 Apr 2003 22:09:32 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Ah4S-0002fI-00 for adslmib-web-archive@ietf.org; Tue, 29 Apr 2003 22:11:44 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Ah4R-0002fF-00 for adslmib-web-archive@ietf.org; Tue, 29 Apr 2003 22:11:43 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3U2FD822757; Tue, 29 Apr 2003 22:15:13 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3TMT5831497 for ; Tue, 29 Apr 2003 18:29:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14609 for ; Tue, 29 Apr 2003 18:23:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19AdXY-0000um-00 for adslmib@ietf.org; Tue, 29 Apr 2003 18:25:32 -0400 Received: from smtp.nlc.com ([209.204.132.15]) by ietf-mx with esmtp (Exim 4.12) id 19AdXX-0000uX-00 for adslmib@ietf.org; Tue, 29 Apr 2003 18:25:32 -0400 Received: from exchange4.nlc.com (exchange4.nlc.com [10.0.0.85]) by smtp.nlc.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h3TMP6516083; Tue, 29 Apr 2003 15:25:06 -0700 (PDT) Received: by exchange4.nlc.com with Internet Mail Service (5.5.2653.19) id ; Tue, 29 Apr 2003 15:25:11 -0700 Message-ID: <50859C0B9DE9D411811F009027B11DAC015D40EC@exchange4.nlc.com> From: "Say, Sabit" To: rray@pesa.com, adslmib mail list Subject: RE: [Adslmib] vdsl-08 question Date: Tue, 29 Apr 2003 15:25:03 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C30E9E.2E0A3B70" Sender: adslmib-admin@ietf.org Errors-To: adslmib-admin@ietf.org X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C30E9E.2E0A3B70 Content-Type: text/plain; charset="iso-8859-1" Bob, But I did send this email about my agrement to the two objects and provided some details. If no objections, I can complete the definitions, but I am not fluent in MIB definitions so somebody who does needs to help me. So, you should not remove them. The alternative of putting back the line code specific parameters is totally unacceptable. The best way is to move forward, with these two parameters properly defined. Sabit -----Original Message----- From: Bob Ray [mailto:rray@pesa.com] Sent: Monday, April 28, 2003 3:16 PM To: adslmib mail list Subject: [Adslmib] vdsl-08 question Hi. I propose that I remove the two objects vdslChanBurstProtection vdslChanOverhead from the -08 draft (producing a -09 draft) and move it ahead in the queue. Haven't heard any comments or suggestions in several weeks, so I guess no one really cares about the two objects (i.e. they are unimportant). If I don't hear any objections in the next day or so, I'll get -09 out. -- Bob Ray _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib ------_=_NextPart_000_01C30E9E.2E0A3B70 Content-Type: message/rfc822 Content-Description: RE: dsl2002.298 and SCM LCS MIB From: "Say, Sabit" To: Flemisch Felix Cc: "'adslmib@ietf.org'" , "'rajesh.abbi@alcatel.com'" , "'moti.morgenstern@inoviatele.com'" , "'rray@pesa.com'" , "'sneedmike@hotmail.com'" , "'greg.bathrick@nokia.com'" , Boll Norbert , Forster Josef Subject: RE: dsl2002.298 and SCM LCS MIB Date: Sun, 6 Apr 2003 23:13:31 -0700 Return-Receipt-To: "Say, Sabit" MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Felix, Sorry about not responding to this quickly. I do not receive email from the ietf? list. Do I need to subscribe to some email list or perhaps you can forward relevant correspondence, as you did earlier. I am glad to hear that not including line code specific parameters in the basic MIB is still a valid course. I also agree that we have missed a couple of generic parameters that specify the configuration of the interleaver and the RS frame. The missed parameters should be needed not only for SCM but MCM as well. The first parameter should be called "target burst protection" and it applies only to the Slow channel (Interleaved, if you like) I included the qualifier "target" because the selection of linecode specific intleaver parameters would try to achieve this target, but the result could end up being lower or higher. The parameter applies independently to Upstream and Downstream. I prefer the unit microseconds, because the values are sub-ms. A reasonable range would be 0 to 1000 microseconds in 20 microsecond increments. The other parameter should be called "Maximum redundancy overhead" and it applies only to the Fast channel (Not interleaved, if you like). I included the qualifier "maximum" because the selection of linecode specific framing parameters would use no more, but equal to or less than this percentage, in determining the number of FEC octets. The parameter applies independently to Upstream and Downstream. The % unit is OK. The reasonable range would be 0 to 50% in 1% increments. If this is agreed so far, we can provide a detailed description. Sabit NLC -----Original Message----- From: Flemisch Felix [mailto:felix.flemisch@siemens.com] Sent: Sunday, March 30, 2003 2:42 PM To: 'ssay@nlc.com' Cc: 'adslmib@ietf.org' Subject: dsl2002.298 and SCM LCS MIB Hello Sabit, Moti Morgenstern wrote on Sunday 02 March 2003 (see msg00178.html): "For the VDSL, the DSLF decided to extract the line code specific parameters from the basic MIB only after the members reviewed a contribution from NLC (dsl2002.298) claiming that SCM specific parameters can be determined according to other, generic type, parameters. The problem is that the DSLF discovered only recently that few of those generic parameters are not present in the MIB so configuring a SCM line is impossible without additional parameters. So, I suggest adding the two generic parameters Overhead (%) and Burst Protection (ms) to the MIB, in order to allow determining the Fast Codeword Size and FEC Size for SCM links." But Moti is not aware of the semantics of the proposed parameters (see msg00191.html): "NLC ... to ... provide soon the definitions for the two alternative parameters they mentioned (i.e., overhead-percentage and burst protection)". Therefore, I would like to ask you, Sabit, to resolve asap these issues and the following questions and request of mine (see msg00183.html): Are you proposing to add the parameters vdslChanOverhead (UNITS "%") and vdslChanBurstProtection (UNITS "ms") to VdslChanEntry, which shall be not for ifType interleave(124)? Please provide a formal DESCRIPTION and how they are used for SCM lines. After adding these two parameters, is it then clear that basic configuration of SCM lines is possible, or might something else be needed or useful? If this is the case, and since these extensions are compatible with TR-057 and RFC 2662, I agree to add them to IETF's VDSL MIB and don't see any reason why anybody should not agree. Best regards, Felix Flemisch -------------------------------------- SIEMENS AG Information and Communication Networks Carrier Products Systems Engineering Hofmannstr. 51 D-81359 Munich Tel +49 89 722 62175 e-Mail felix.flemisch@siemens.com -------------------------------------- ------_=_NextPart_000_01C30E9E.2E0A3B70-- _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Wed Apr 30 09:05:51 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01250 for ; Wed, 30 Apr 2003 09:05:51 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3UDBNi00676 for adslmib-archive@odin.ietf.org; Wed, 30 Apr 2003 09:11:23 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UDBN800673 for ; Wed, 30 Apr 2003 09:11:23 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01225 for ; Wed, 30 Apr 2003 09:05:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ArJ5-0006cb-00 for adslmib-web-archive@ietf.org; Wed, 30 Apr 2003 09:07:31 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ArJ5-0006cY-00 for adslmib-web-archive@ietf.org; Wed, 30 Apr 2003 09:07:31 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UDBE800654; Wed, 30 Apr 2003 09:11:14 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UDAK800569 for ; Wed, 30 Apr 2003 09:10:20 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01145 for ; Wed, 30 Apr 2003 09:04:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ArI5-0006bm-00 for adslmib@ietf.org; Wed, 30 Apr 2003 09:06:29 -0400 Received: from ant.hiwaay.net ([216.180.54.10] helo=mail.hiwaay.net) by ietf-mx with esmtp (Exim 4.12) id 19ArI4-0006bg-00 for adslmib@ietf.org; Wed, 30 Apr 2003 09:06:28 -0400 Received: from mailserver ([216.180.38.253]) by mail.hiwaay.net (8.12.9/8.12.9) with ESMTP id h3UD76Hb894269 for ; Wed, 30 Apr 2003 08:07:06 -0500 (CDT) Received: from [192.168.0.122] ([192.168.0.122]) by pesahsv.com ([127.0.0.1]) with SMTP (MDaemon.PRO.v6.7.2.R) for ; Wed, 30 Apr 2003 08:07:03 -0500 Subject: RE: [Adslmib] vdsl-08 question From: Bob Ray Reply-To: rray@pesa.com To: "Say, Sabit" Cc: Moti.Morgenstern@ecitele.com, adslmib mail list In-Reply-To: <50859C0B9DE9D411811F009027B11DAC015D40ED@exchange4.nlc.com> References: <50859C0B9DE9D411811F009027B11DAC015D40ED@exchange4.nlc.com> Content-Type: text/plain Message-Id: <1051708022.26581.2.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 30 Apr 2003 08:07:03 -0500 Content-Transfer-Encoding: 7bit X-MDRemoteIP: 192.168.0.122 X-Return-Path: rray@pesa.com X-MDaemon-Deliver-To: adslmib@ietf.org Content-Transfer-Encoding: 7bit Sender: adslmib-admin@ietf.org Errors-To: adslmib-admin@ietf.org X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit That's it! Thanks. Bob Ray On Tue, 2003-04-29 at 17:58, Say, Sabit wrote: > If this is all you need: > > vdslChanOverhead OBJECT-TYPE > SYNTAX Gauge32 > UNITS "%" > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "Channel overhead applies independently to downstream and > upstream directions, and only to fast channel. It indicates the percentage > of redundant octets to the total FEC block. The range is 0 to 100. In the > case where the ifType is interleave(124), use noSuchObject." > ::= { vdslChanEntry 4 } > > vdslChanBurstProtection OBJECT-TYPE > SYNTAX Gauge32 > UNITS "0.005 ms" > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "Channel burst protection applies independently to downstream > and upstream, and only to interleave (slow) channel. It indicates the > correctable burst size with the interleaver settings. The range is 0 to > 1.275 ms. In the case where the ifType is fast(125), use noSuchObject." > ::= { vdslChanEntry 5 } > > > -----Original Message----- > From: Bob Ray [mailto:rray@pesa.com] > Sent: Tuesday, April 29, 2003 9:22 AM > To: Moti.Morgenstern@ecitele.com > Cc: adslmib mail list > Subject: Re: [Adslmib] vdsl-08 question > > > On Tue, 2003-04-29 at 01:42, Moti.Morgenstern@ecitele.com wrote: > > Hi Bob, > > > > The main reason all SCM specific parameters were removed from the model is > > because there was an input from NLC to the DSLF (dsl2003.298) showing that > > with the existing generic parameters plus (new) vdslChanBurstProtection > and > > vdslChanOverhead, one can configure a SCM line. So we should choose > between > > including the generic parameters, according to Sabit's mail from 7-Apr-03, > > and the SCM parameters (vdslSCMConfProfileFastCodewordSize and > > vdslSCMConfProfileFastFecSize) according to your mail from 27-Mar-03. > > > > We cannot leave outside both the original and the alternative parameters, > > because there is no one who claims it is possible to configure a SCM link > > that way. > > > > Best regards, > > Moti Morgenstern > > > > Hi Moti. > > I asked the list for two sentences (DESCRIPTION for these two objects). > On the assumption SOMEONE/ANYONE would provide them, I removed all > the other LCS objects from the draft. > > Since NO ONE has provided the two sentences in the two months since > Felix first asked for them, and three weeks since I first asked for > them, I assumed no one cared whether they were in or not. Hence, > my post. > > As I understand the process, these two sentences are all that is > keeping us from moving these two drafts to the RFC editor queue. > Which is what I want to do. > > I did not see the presentation from NLC. One would think that they > would be happy to provide the DESCRIPTIONs, no? -- Bob Ray _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Wed Apr 30 09:47:41 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03156 for ; Wed, 30 Apr 2003 09:47:40 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3UDrEn08536 for adslmib-archive@odin.ietf.org; Wed, 30 Apr 2003 09:53:14 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UDrE808533 for ; Wed, 30 Apr 2003 09:53:14 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03140 for ; Wed, 30 Apr 2003 09:47:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ArxZ-0007BP-00 for adslmib-web-archive@ietf.org; Wed, 30 Apr 2003 09:49:21 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ArxZ-0007BM-00 for adslmib-web-archive@ietf.org; Wed, 30 Apr 2003 09:49:21 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UDr6808502; Wed, 30 Apr 2003 09:53:06 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UDqf808480 for ; Wed, 30 Apr 2003 09:52:41 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03124 for ; Wed, 30 Apr 2003 09:46:38 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Arx3-0007B2-00 for adslmib@ietf.org; Wed, 30 Apr 2003 09:48:49 -0400 Received: from hostr490.alcatel.com ([143.209.4.144] helo=aurmsd.aur.alcatel.com) by ietf-mx with esmtp (Exim 4.12) id 19Arx2-0007Av-00 for adslmib@ietf.org; Wed, 30 Apr 2003 09:48:48 -0400 Received: from alcatel.com (localhost [127.0.0.1]) by aurmsd.aur.alcatel.com (8.12.8+Sun/8.11.3) with ESMTP id h3UDmfRk014806; Wed, 30 Apr 2003 09:48:41 -0400 (EDT) Message-ID: <3EAFD438.2CFBD260@alcatel.com> Date: Wed, 30 Apr 2003 09:48:41 -0400 From: Rajesh Abbi Organization: Alcatel X-Mailer: Mozilla 4.79 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: rray@pesa.com CC: "Say, Sabit" , Moti.Morgenstern@ecitele.com, adslmib mail list Subject: Re: [Adslmib] vdsl-08 question References: <50859C0B9DE9D411811F009027B11DAC015D40ED@exchange4.nlc.com> <1051708022.26581.2.camel@localhost.localdomain> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: adslmib-admin@ietf.org Errors-To: adslmib-admin@ietf.org X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Sabit, Thanks for the input. I have a few suggestions for the definitions provided by you below. * vdslChanBurstProtection : - Suggest rename to vdslChanMinInterleaveBurstProtection Note: It is impractical to specify a specific/exact value. Also, ITU-T G.997.1 defines the parameter as "7.3.2.3 Minimum Impulse Noise Protection". - Suggest using micro-seconds as units. - Suggested DESCRIPTION: "This parameter provisions the minimum level of impulse noise (burst) protection the Interleaver associated with the Interleave (Slow) channel should maintain. This parameter is not applicable to the Fast channel (noSuchObject should be returned)." * vdslChanOverhead : - Suggest rename to vdslChanMaxFastFecOverhead: Note: Once again it is impractical to require exact values for this. - The range should be much smaller, 1..50% is more than adequate. It would be absurd to have this 100% ;-). - Suggested DESCRIPTION: "This parameter provisions the maximum level of Forward Error Correction (FEC) redundancy releated overhead to be maintained for the Fast channel. This parameter is not applicable to the Interleave (Slow) channel (noSuchObject should be returned)." Note: No need to indicate that the parameters apply independently in up/downstream directions since that is implied by the MIB (indexed by vdslPhysSide). Regards, Rajesh Bob Ray wrote: > That's it! Thanks. > > Bob Ray > > On Tue, 2003-04-29 at 17:58, Say, Sabit wrote: > > If this is all you need: > > > > vdslChanOverhead OBJECT-TYPE > > SYNTAX Gauge32 > > UNITS "%" > > MAX-ACCESS read-only > > STATUS current > > DESCRIPTION > > "Channel overhead applies independently to downstream and > > upstream directions, and only to fast channel. It indicates the percentage > > of redundant octets to the total FEC block. The range is 0 to 100. In the > > case where the ifType is interleave(124), use noSuchObject." > > ::= { vdslChanEntry 4 } > > > > vdslChanBurstProtection OBJECT-TYPE > > SYNTAX Gauge32 > > UNITS "0.005 ms" > > MAX-ACCESS read-only > > STATUS current > > DESCRIPTION > > "Channel burst protection applies independently to downstream > > and upstream, and only to interleave (slow) channel. It indicates the > > correctable burst size with the interleaver settings. The range is 0 to > > 1.275 ms. In the case where the ifType is fast(125), use noSuchObject." > > ::= { vdslChanEntry 5 } > > > > > > -----Original Message----- > > From: Bob Ray [mailto:rray@pesa.com] > > Sent: Tuesday, April 29, 2003 9:22 AM > > To: Moti.Morgenstern@ecitele.com > > Cc: adslmib mail list > > Subject: Re: [Adslmib] vdsl-08 question > > > > > > On Tue, 2003-04-29 at 01:42, Moti.Morgenstern@ecitele.com wrote: > > > Hi Bob, > > > > > > The main reason all SCM specific parameters were removed from the model is > > > because there was an input from NLC to the DSLF (dsl2003.298) showing that > > > with the existing generic parameters plus (new) vdslChanBurstProtection > > and > > > vdslChanOverhead, one can configure a SCM line. So we should choose > > between > > > including the generic parameters, according to Sabit's mail from 7-Apr-03, > > > and the SCM parameters (vdslSCMConfProfileFastCodewordSize and > > > vdslSCMConfProfileFastFecSize) according to your mail from 27-Mar-03. > > > > > > We cannot leave outside both the original and the alternative parameters, > > > because there is no one who claims it is possible to configure a SCM link > > > that way. > > > > > > Best regards, > > > Moti Morgenstern > > > > > > > Hi Moti. > > > > I asked the list for two sentences (DESCRIPTION for these two objects). > > On the assumption SOMEONE/ANYONE would provide them, I removed all > > the other LCS objects from the draft. > > > > Since NO ONE has provided the two sentences in the two months since > > Felix first asked for them, and three weeks since I first asked for > > them, I assumed no one cared whether they were in or not. Hence, > > my post. > > > > As I understand the process, these two sentences are all that is > > keeping us from moving these two drafts to the RFC editor queue. > > Which is what I want to do. > > > > I did not see the presentation from NLC. One would think that they > > would be happy to provide the DESCRIPTIONs, no? > -- > Bob Ray > > _______________________________________________ > Adslmib mailing list > Adslmib@ietf.org > https://www1.ietf.org/mailman/listinfo/adslmib _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Wed Apr 30 10:43:50 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06562 for ; Wed, 30 Apr 2003 10:43:50 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3UEnOp24551 for adslmib-archive@odin.ietf.org; Wed, 30 Apr 2003 10:49:24 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UEnO824548 for ; Wed, 30 Apr 2003 10:49:24 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06516 for ; Wed, 30 Apr 2003 10:43:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Aspv-0007kz-00 for adslmib-web-archive@ietf.org; Wed, 30 Apr 2003 10:45:31 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Aspu-0007kw-00 for adslmib-web-archive@ietf.org; Wed, 30 Apr 2003 10:45:30 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UEnG824535; Wed, 30 Apr 2003 10:49:16 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UEm6824434 for ; Wed, 30 Apr 2003 10:48:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06417 for ; Wed, 30 Apr 2003 10:42:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Asof-0007jd-00 for adslmib@ietf.org; Wed, 30 Apr 2003 10:44:13 -0400 Received: from ant.hiwaay.net ([216.180.54.10] helo=mail.hiwaay.net) by ietf-mx with esmtp (Exim 4.12) id 19Asod-0007ja-00 for adslmib@ietf.org; Wed, 30 Apr 2003 10:44:12 -0400 Received: from mailserver ([216.180.38.253]) by mail.hiwaay.net (8.12.9/8.12.9) with ESMTP id h3UEiiHd636672 for ; Wed, 30 Apr 2003 09:44:46 -0500 (CDT) Received: from rray ([192.168.0.108]) by pesahsv.com ([127.0.0.1]) with SMTP (MDaemon.PRO.v6.7.2.R) for ; Wed, 30 Apr 2003 09:44:44 -0500 From: "Bob Ray" To: "Rajesh Abbi" Cc: "Say, Sabit" , , "adslmib mail list" Subject: RE: [Adslmib] vdsl-08 question Date: Wed, 30 Apr 2003 09:44:43 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal In-Reply-To: <3EAFD438.2CFBD260@alcatel.com> X-MDRemoteIP: 192.168.0.108 X-Return-Path: rray@pesa.com X-MDaemon-Deliver-To: adslmib@ietf.org Content-Transfer-Encoding: 7bit Sender: adslmib-admin@ietf.org Errors-To: adslmib-admin@ietf.org X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Rajesh suggests: > - Suggested DESCRIPTION: > "This parameter provisions the minimum level of impulse noise (burst) protection the > Interleaver associated with the Interleave (Slow) channel should maintain. This > parameter is not applicable to the Fast channel (noSuchObject should be returned)." > "This parameter provisions the maximum level of Forward Error Correction (FEC) > redundancy releated overhead to be maintained for the Fast channel. This parameter > is not applicable to the Interleave (Slow) channel (noSuchObject should be returned)." Please note that a) these objects are in the channel table b) these objects are not persistent c) these objects are read-only d) there is no 'provisioning' going on with these objects If these need to be moved to the profile table, please speak up now!!!! Bob Ray _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Wed Apr 30 10:45:37 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06728 for ; Wed, 30 Apr 2003 10:45:37 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3UEpCT24753 for adslmib-archive@odin.ietf.org; Wed, 30 Apr 2003 10:51:12 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UEpB824750 for ; Wed, 30 Apr 2003 10:51:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06700 for ; Wed, 30 Apr 2003 10:45:06 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Asre-000012-00 for adslmib-web-archive@ietf.org; Wed, 30 Apr 2003 10:47:18 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Asrd-00000z-00 for adslmib-web-archive@ietf.org; Wed, 30 Apr 2003 10:47:17 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UEp1824724; Wed, 30 Apr 2003 10:51:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UEon824674 for ; Wed, 30 Apr 2003 10:50:49 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06657 for ; Wed, 30 Apr 2003 10:44:43 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19AsrH-000008-00 for adslmib@ietf.org; Wed, 30 Apr 2003 10:46:55 -0400 Received: from ant.hiwaay.net ([216.180.54.10] helo=mail.hiwaay.net) by ietf-mx with esmtp (Exim 4.12) id 19AsrG-0007nk-00 for adslmib@ietf.org; Wed, 30 Apr 2003 10:46:54 -0400 Received: from mailserver ([216.180.38.253]) by mail.hiwaay.net (8.12.9/8.12.9) with ESMTP id h3UElWHb673012 for ; Wed, 30 Apr 2003 09:47:32 -0500 (CDT) Received: from rray ([192.168.0.108]) by pesahsv.com ([127.0.0.1]) with SMTP (MDaemon.PRO.v6.7.2.R) for ; Wed, 30 Apr 2003 09:47:29 -0500 From: "Bob Ray" To: "Adslmib" Date: Wed, 30 Apr 2003 09:47:28 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal X-MDRemoteIP: 192.168.0.108 X-Return-Path: rray@pesa.com X-MDaemon-Deliver-To: adslmib@ietf.org Content-Transfer-Encoding: 7bit Subject: [Adslmib] units changing Sender: adslmib-admin@ietf.org Errors-To: adslmib-admin@ietf.org X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi. I've received email suggesting that I change all occurrences of '1024' to 1000. Similarly, to note that 1 kbps = 1000 bps, not 1024 bps. Anyone have any objection to this change? Regards, Bob Ray _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Wed Apr 30 11:09:45 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08232 for ; Wed, 30 Apr 2003 11:09:45 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3UFFLt01631 for adslmib-archive@odin.ietf.org; Wed, 30 Apr 2003 11:15:21 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UFFL801628 for ; Wed, 30 Apr 2003 11:15:21 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08219 for ; Wed, 30 Apr 2003 11:09:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19AtF1-0000Ox-00 for adslmib-web-archive@ietf.org; Wed, 30 Apr 2003 11:11:27 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19AtF0-0000Ou-00 for adslmib-web-archive@ietf.org; Wed, 30 Apr 2003 11:11:26 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UFFA801588; Wed, 30 Apr 2003 11:15:10 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UFD4801255 for ; Wed, 30 Apr 2003 11:13:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08125 for ; Wed, 30 Apr 2003 11:06:59 -0400 (EDT) From: Moti.Morgenstern@ecitele.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19AtCo-0000NJ-00 for adslmib@ietf.org; Wed, 30 Apr 2003 11:09:10 -0400 Received: from mink.ecitele.com ([147.234.1.100]) by ietf-mx with esmtp (Exim 4.12) id 19AtCn-0000NG-00 for adslmib@ietf.org; Wed, 30 Apr 2003 11:09:09 -0400 Received: from olive.ecitele.com (ilsmtp04.ecitele.com [147.234.8.125]) by mink.ecitele.com (8.12.8+Sun/8.12.8) with ESMTP id h3UF4JpP002944; Wed, 30 Apr 2003 18:04:19 +0300 (IDT) Subject: RE: [Adslmib] vdsl-08 question To: "Bob Ray" Cc: adslmib@ietf.org, Rajesh.Abbi@alcatel.com, ssay@nlc.com X-Mailer: Lotus Notes Release 5.0.2b (Intl) 16 December 1999 Message-ID: Date: Wed, 30 Apr 2003 18:09:31 +0300 X-MIMETrack: Serialize by Router on ILSMTP04/ECI Telecom(Release 5.0.9a |January 7, 2002) at 04/30/2003 06:09:39 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: adslmib-admin@ietf.org Errors-To: adslmib-admin@ietf.org X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , Bob, Sorry, but the term "shocked" quite describes what I feel. Thank you Bob for indicating this possible disaster. Once again (not for you Bob but for other people): The idea was that it is possible to remove the LCS CONFIGURATION section and use other, existing and generic CONFIGURATION parameters for CONFIGURING SCM links. The problem was that there were two LCS CONFIGURATION parameters that could not be removed unless we define alternative generic CONFIGURATION parameters. The two new parameters should be part of the CONFIGURATION profile and it should be possible in the profile to assign different values per each transmission direction (what we call upstream and downstream). It is also obvious that the new parameters are persistent as all other profile details. The only difference between the two new parameters and other profile parameters is that the two new parameters are used only for SCM links' CONFIGURATION. That's the only difference. I don't mind (or even be glad) if, IN ADDITION to those two CONFIGURATION parameters, the IETF memebers find it appropriate to add read-only parameters that provide the actual values achieved during synchronization. Best regards, Moti Morgenstern Senior Systems Engineer ECI Telecoms Ltd. Inovia Broadband Access Division 30 Hasivim St. Petach Tikva, Israel 49133 Tel.: +972-3-9266258 Fax: +972-3-9268182 Cell: +972-55-786258 e-mail: Moti.Morgenstern@ecitele.com www.ecitele.com "Bob Ray" To: "Rajesh Abbi" cc: "Say, Sabit" , , "adslmib mail 30/04/03 17:44 list" Subject: RE: [Adslmib] vdsl-08 question Rajesh suggests: > - Suggested DESCRIPTION: > "This parameter provisions the minimum level of impulse noise (burst) protection the > Interleaver associated with the Interleave (Slow) channel should maintain. This > parameter is not applicable to the Fast channel (noSuchObject should be returned)." > "This parameter provisions the maximum level of Forward Error Correction (FEC) > redundancy releated overhead to be maintained for the Fast channel. This parameter > is not applicable to the Interleave (Slow) channel (noSuchObject should be returned)." Please note that a) these objects are in the channel table b) these objects are not persistent c) these objects are read-only d) there is no 'provisioning' going on with these objects If these need to be moved to the profile table, please speak up now!!!! Bob Ray _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Wed Apr 30 11:34:54 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08932 for ; Wed, 30 Apr 2003 11:34:53 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3UFeUT10923 for adslmib-archive@odin.ietf.org; Wed, 30 Apr 2003 11:40:30 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UFeU810920 for ; Wed, 30 Apr 2003 11:40:30 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08922 for ; Wed, 30 Apr 2003 11:34:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19AtdL-0000ZG-00 for adslmib-web-archive@ietf.org; Wed, 30 Apr 2003 11:36:35 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19AtdK-0000ZD-00 for adslmib-web-archive@ietf.org; Wed, 30 Apr 2003 11:36:34 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UFeE810898; Wed, 30 Apr 2003 11:40:14 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UFd4810598 for ; Wed, 30 Apr 2003 11:39:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08837 for ; Wed, 30 Apr 2003 11:32:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Atby-0000YS-00 for adslmib@ietf.org; Wed, 30 Apr 2003 11:35:10 -0400 Received: from hostr490.alcatel.com ([143.209.4.144] helo=aurmsd.aur.alcatel.com) by ietf-mx with esmtp (Exim 4.12) id 19Atbx-0000Y5-00 for adslmib@ietf.org; Wed, 30 Apr 2003 11:35:09 -0400 Received: from alcatel.com (localhost [127.0.0.1]) by aurmsd.aur.alcatel.com (8.12.8+Sun/8.11.3) with ESMTP id h3UFZ9Rk016481; Wed, 30 Apr 2003 11:35:09 -0400 (EDT) Message-ID: <3EAFED2C.F592726D@alcatel.com> Date: Wed, 30 Apr 2003 11:35:08 -0400 From: Rajesh Abbi Organization: Alcatel X-Mailer: Mozilla 4.79 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Bob Ray CC: "Say, Sabit" , Moti.Morgenstern@ecitele.com, adslmib mail list Subject: Re: [Adslmib] vdsl-08 question References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: adslmib-admin@ietf.org Errors-To: adslmib-admin@ietf.org X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit I guess while looking at the trees we lost track of the "forest" ;-). These parameters do need to be added to the vdslLineConfProfileTable with following changes: vdslChanBurstProtection would become: - vdslLineConfDownstreamMinSlowBurstProtection (RW) - vdslLineConfUpstreamMinSlowBurstProtection (RW) vdslChanOverhead would become: - vdslLineConfDownstreamMaxFastFecOverhead (RW) - vdslLineConfUpstreamMaxFastFecOverhead (RW) Regards, Rajesh Bob Ray wrote: > Rajesh suggests: > > > - Suggested DESCRIPTION: > > "This parameter provisions the minimum level of impulse noise > (burst) protection the > > Interleaver associated with the Interleave (Slow) channel should > maintain. This > > parameter is not applicable to the Fast channel (noSuchObject > should be returned)." > > > "This parameter provisions the maximum level of Forward Error > Correction (FEC) > > redundancy releated overhead to be maintained for the Fast > channel. This parameter > > is not applicable to the Interleave (Slow) channel (noSuchObject > should be returned)." > > Please note that > > a) these objects are in the channel table > b) these objects are not persistent > c) these objects are read-only > d) there is no 'provisioning' going on with these objects > > If these need to be moved to the profile table, please speak up now!!!! > > Bob Ray > > _______________________________________________ > Adslmib mailing list > Adslmib@ietf.org > https://www1.ietf.org/mailman/listinfo/adslmib _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Wed Apr 30 12:29:29 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10823 for ; Wed, 30 Apr 2003 12:29:29 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3UGZ7L02784 for adslmib-archive@odin.ietf.org; Wed, 30 Apr 2003 12:35:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UGZ6802781 for ; Wed, 30 Apr 2003 12:35:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10804 for ; Wed, 30 Apr 2003 12:28:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19AuUB-00012p-00 for adslmib-web-archive@ietf.org; Wed, 30 Apr 2003 12:31:11 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19AuUA-00012m-00 for adslmib-web-archive@ietf.org; Wed, 30 Apr 2003 12:31:10 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UGYh802613; Wed, 30 Apr 2003 12:34:43 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UFQY802145 for ; Wed, 30 Apr 2003 11:26:34 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08470 for ; Wed, 30 Apr 2003 11:20:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19AtPs-0000Sh-00 for adslmib@ietf.org; Wed, 30 Apr 2003 11:22:40 -0400 Received: from postman.nlc.com ([209.204.132.16]) by ietf-mx with esmtp (Exim 4.12) id 19AtPr-0000SX-00 for adslmib@ietf.org; Wed, 30 Apr 2003 11:22:39 -0400 Received: from exchange4.nlc.com (exchange4.nlc.com [10.0.0.85]) by postman.nlc.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h3UFMGx12874; Wed, 30 Apr 2003 08:22:16 -0700 (PDT) Received: by exchange4.nlc.com with Internet Mail Service (5.5.2653.19) id ; Wed, 30 Apr 2003 08:22:22 -0700 Message-ID: <50859C0B9DE9D411811F009027B11DAC015D40F3@exchange4.nlc.com> From: "Say, Sabit" To: Bob Ray , Adslmib Subject: RE: [Adslmib] units changing Date: Wed, 30 Apr 2003 08:22:20 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: adslmib-admin@ietf.org Errors-To: adslmib-admin@ietf.org X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , No objections. I was a little disturbed to see that defined as 1024. Reminded me of the kibi discussion in the recent IEEE 802 meeting. -----Original Message----- From: Bob Ray [mailto:rray@pesa.com] Sent: Wednesday, April 30, 2003 10:47 AM To: Adslmib Subject: [Adslmib] units changing Hi. I've received email suggesting that I change all occurrences of '1024' to 1000. Similarly, to note that 1 kbps = 1000 bps, not 1024 bps. Anyone have any objection to this change? Regards, Bob Ray _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Wed Apr 30 12:29:41 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10847 for ; Wed, 30 Apr 2003 12:29:41 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3UGZI202801 for adslmib-archive@odin.ietf.org; Wed, 30 Apr 2003 12:35:18 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UGZI802798 for ; Wed, 30 Apr 2003 12:35:18 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10808 for ; Wed, 30 Apr 2003 12:29:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19AuUM-00012v-00 for adslmib-web-archive@ietf.org; Wed, 30 Apr 2003 12:31:22 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19AuUM-00012s-00 for adslmib-web-archive@ietf.org; Wed, 30 Apr 2003 12:31:22 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UGZ2802705; Wed, 30 Apr 2003 12:35:02 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UGSd824898 for ; Wed, 30 Apr 2003 12:28:39 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10660 for ; Wed, 30 Apr 2003 12:22:31 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19AuNv-0000zy-00 for adslmib@ietf.org; Wed, 30 Apr 2003 12:24:43 -0400 Received: from smtp.nlc.com ([209.204.132.15]) by ietf-mx with esmtp (Exim 4.12) id 19AuNu-0000zV-00 for adslmib@ietf.org; Wed, 30 Apr 2003 12:24:42 -0400 Received: from exchange4.nlc.com (exchange4.nlc.com [10.0.0.85]) by smtp.nlc.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h3UGO6524009; Wed, 30 Apr 2003 09:24:06 -0700 (PDT) Received: by exchange4.nlc.com with Internet Mail Service (5.5.2653.19) id ; Wed, 30 Apr 2003 09:24:12 -0700 Message-ID: <50859C0B9DE9D411811F009027B11DAC015D40F8@exchange4.nlc.com> From: "Say, Sabit" To: Rajesh Abbi , Bob Ray Cc: "Say, Sabit" , Moti.Morgenstern@ecitele.com, adslmib mail list Subject: RE: [Adslmib] vdsl-08 question Date: Wed, 30 Apr 2003 09:24:11 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: adslmib-admin@ietf.org Errors-To: adslmib-admin@ietf.org X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , Can I suggest a change? vdslChanBurstProtection would become: - vdslLineConfDownstreamTargetSlowBurstProtection (RW) - vdslLineConfUpstreamTargetSlowBurstProtection (RW) The reason is that you might end up more or less, not necessarily more. Also the read-only ACTUAL values could be: - vdslLineDownstreamSlowBurstProtection (R) - vdslLineUpstreamSlowBurstProtection (R) For completeness: vdslChanOverhead would become: - vdslLineConfDownstreamMaxFastFecOverhead (RW) - vdslLineConfUpstreamMaxFastFecOverhead (RW) and read-only - vdslLineownstreamFastFecOverhead (R) - vdslLineUpstreamFastFecOverhead (R) This time, the actual value is always less or equal to configured. -----Original Message----- From: Rajesh Abbi [mailto:Rajesh.Abbi@alcatel.com] Sent: Wednesday, April 30, 2003 11:35 AM To: Bob Ray Cc: Say, Sabit; Moti.Morgenstern@ecitele.com; adslmib mail list Subject: Re: [Adslmib] vdsl-08 question I guess while looking at the trees we lost track of the "forest" ;-). These parameters do need to be added to the vdslLineConfProfileTable with following changes: vdslChanBurstProtection would become: - vdslLineConfDownstreamMinSlowBurstProtection (RW) - vdslLineConfUpstreamMinSlowBurstProtection (RW) vdslChanOverhead would become: - vdslLineConfDownstreamMaxFastFecOverhead (RW) - vdslLineConfUpstreamMaxFastFecOverhead (RW) Regards, Rajesh Bob Ray wrote: > Rajesh suggests: > > > - Suggested DESCRIPTION: > > "This parameter provisions the minimum level of impulse noise > (burst) protection the > > Interleaver associated with the Interleave (Slow) channel should > maintain. This > > parameter is not applicable to the Fast channel (noSuchObject > should be returned)." > > > "This parameter provisions the maximum level of Forward Error > Correction (FEC) > > redundancy releated overhead to be maintained for the Fast > channel. This parameter > > is not applicable to the Interleave (Slow) channel (noSuchObject > should be returned)." > > Please note that > > a) these objects are in the channel table > b) these objects are not persistent > c) these objects are read-only > d) there is no 'provisioning' going on with these objects > > If these need to be moved to the profile table, please speak up now!!!! > > Bob Ray > > _______________________________________________ > Adslmib mailing list > Adslmib@ietf.org > https://www1.ietf.org/mailman/listinfo/adslmib _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Wed Apr 30 12:29:44 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10861 for ; Wed, 30 Apr 2003 12:29:44 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3UGZME02817 for adslmib-archive@odin.ietf.org; Wed, 30 Apr 2003 12:35:22 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UGZL802814 for ; Wed, 30 Apr 2003 12:35:21 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10812 for ; Wed, 30 Apr 2003 12:29:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19AuUQ-000132-00 for adslmib-web-archive@ietf.org; Wed, 30 Apr 2003 12:31:26 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19AuUP-00012z-00 for adslmib-web-archive@ietf.org; Wed, 30 Apr 2003 12:31:25 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UGZ1802685; Wed, 30 Apr 2003 12:35:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UFQg802149 for ; Wed, 30 Apr 2003 11:26:42 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08479 for ; Wed, 30 Apr 2003 11:20:36 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19AtQ0-0000St-00 for adslmib@ietf.org; Wed, 30 Apr 2003 11:22:48 -0400 Received: from postman.nlc.com ([209.204.132.16]) by ietf-mx with esmtp (Exim 4.12) id 19AtPz-0000SY-00 for adslmib@ietf.org; Wed, 30 Apr 2003 11:22:48 -0400 Received: from exchange4.nlc.com (exchange4.nlc.com [10.0.0.85]) by postman.nlc.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h3UFMGx12877; Wed, 30 Apr 2003 08:22:16 -0700 (PDT) Received: by exchange4.nlc.com with Internet Mail Service (5.5.2653.19) id ; Wed, 30 Apr 2003 08:22:22 -0700 Message-ID: <50859C0B9DE9D411811F009027B11DAC015D40F2@exchange4.nlc.com> From: "Say, Sabit" To: Moti.Morgenstern@ecitele.com, Bob Ray Cc: adslmib@ietf.org, Rajesh.Abbi@alcatel.com, ssay@nlc.com Subject: RE: [Adslmib] vdsl-08 question Date: Wed, 30 Apr 2003 08:22:20 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: adslmib-admin@ietf.org Errors-To: adslmib-admin@ietf.org X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , Sorry for my ignorance re: actual MIB definitions. I totally agree with Moti that these two should be configuration parameters. I thought they would be somehow (magically) be both read-only and configurable. Anyway, it also helps that they are reported. And now thinking clearer, the descriptions should be slightly different, one configuring a max or target, and the other one reading the actual used by the PMD layer. Also I have to disagree on the difference and point out that these are needed NOT ONLY for configuring SCM but also MCM. I think now I have to read the whole MIB and suggest more input on these. -----Original Message----- From: Moti.Morgenstern@ecitele.com [mailto:Moti.Morgenstern@ecitele.com] Sent: Wednesday, April 30, 2003 11:10 AM To: Bob Ray Cc: adslmib@ietf.org; Rajesh.Abbi@alcatel.com; ssay@nlc.com Subject: RE: [Adslmib] vdsl-08 question Bob, Sorry, but the term "shocked" quite describes what I feel. Thank you Bob for indicating this possible disaster. Once again (not for you Bob but for other people): The idea was that it is possible to remove the LCS CONFIGURATION section and use other, existing and generic CONFIGURATION parameters for CONFIGURING SCM links. The problem was that there were two LCS CONFIGURATION parameters that could not be removed unless we define alternative generic CONFIGURATION parameters. The two new parameters should be part of the CONFIGURATION profile and it should be possible in the profile to assign different values per each transmission direction (what we call upstream and downstream). It is also obvious that the new parameters are persistent as all other profile details. The only difference between the two new parameters and other profile parameters is that the two new parameters are used only for SCM links' CONFIGURATION. That's the only difference. I don't mind (or even be glad) if, IN ADDITION to those two CONFIGURATION parameters, the IETF memebers find it appropriate to add read-only parameters that provide the actual values achieved during synchronization. Best regards, Moti Morgenstern Senior Systems Engineer ECI Telecoms Ltd. Inovia Broadband Access Division 30 Hasivim St. Petach Tikva, Israel 49133 Tel.: +972-3-9266258 Fax: +972-3-9268182 Cell: +972-55-786258 e-mail: Moti.Morgenstern@ecitele.com www.ecitele.com "Bob Ray" To: "Rajesh Abbi" cc: "Say, Sabit" , , "adslmib mail 30/04/03 17:44 list" Subject: RE: [Adslmib] vdsl-08 question Rajesh suggests: > - Suggested DESCRIPTION: > "This parameter provisions the minimum level of impulse noise (burst) protection the > Interleaver associated with the Interleave (Slow) channel should maintain. This > parameter is not applicable to the Fast channel (noSuchObject should be returned)." > "This parameter provisions the maximum level of Forward Error Correction (FEC) > redundancy releated overhead to be maintained for the Fast channel. This parameter > is not applicable to the Interleave (Slow) channel (noSuchObject should be returned)." Please note that a) these objects are in the channel table b) these objects are not persistent c) these objects are read-only d) there is no 'provisioning' going on with these objects If these need to be moved to the profile table, please speak up now!!!! Bob Ray _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Wed Apr 30 13:56:56 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14900 for ; Wed, 30 Apr 2003 13:56:56 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3UI2Yh20860 for adslmib-archive@odin.ietf.org; Wed, 30 Apr 2003 14:02:34 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UI2Y820814 for ; Wed, 30 Apr 2003 14:02:34 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14863 for ; Wed, 30 Apr 2003 13:56:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Avqm-00022l-00 for adslmib-web-archive@ietf.org; Wed, 30 Apr 2003 13:58:36 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Avql-00022i-00 for adslmib-web-archive@ietf.org; Wed, 30 Apr 2003 13:58:35 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UI2D819481; Wed, 30 Apr 2003 14:02:13 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UI1Y816588 for ; Wed, 30 Apr 2003 14:01:34 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14757 for ; Wed, 30 Apr 2003 13:55:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Avpo-00021O-00 for adslmib@ietf.org; Wed, 30 Apr 2003 13:57:36 -0400 Received: from ant.hiwaay.net ([216.180.54.10] helo=mail.hiwaay.net) by ietf-mx with esmtp (Exim 4.12) id 19Avpl-00021B-00 for adslmib@ietf.org; Wed, 30 Apr 2003 13:57:35 -0400 Received: from mailserver ([216.180.38.253]) by mail.hiwaay.net (8.12.9/8.12.9) with ESMTP id h3UHw4Hd696941 for ; Wed, 30 Apr 2003 12:58:09 -0500 (CDT) Received: from rray ([192.168.0.108]) by pesahsv.com ([127.0.0.1]) with SMTP (MDaemon.PRO.v6.7.2.R) for ; Wed, 30 Apr 2003 12:58:02 -0500 From: "Bob Ray" To: "Rajesh Abbi" Cc: "Say, Sabit" , , "adslmib mail list" Date: Wed, 30 Apr 2003 12:58:00 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: <3EAFD438.2CFBD260@alcatel.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-MDRemoteIP: 192.168.0.108 X-Return-Path: rray@pesa.com X-MDaemon-Deliver-To: adslmib@ietf.org Content-Transfer-Encoding: 7bit Subject: [Adslmib] six objects Sender: adslmib-admin@ietf.org Errors-To: adslmib-admin@ietf.org X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Following are the working object declarations. Let me know if I've got them right. Please. Bob Ray ------------------------------------------------------------------------- vdslChanCurrFastFecOverhead OBJECT-TYPE SYNTAX Gauge32 UNITS "%" MAX-ACCESS read-only STATUS current DESCRIPTION "Actual Forward Error Correction (FEC) redundancy related overhead for a fast channel. This parameter is not applicable to an interleaved (slow) channel. For interleaved channels, noSuchObject should be returned." ::= { vdslChanEntry 4 } vdslChanCurrSlowBurstProtection OBJECT-TYPE SYNTAX Gauge32 UNITS "microseconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Actual level of impulse noise (burst) protection for an interleaved (slow) channel. This parameter is not applicable to fast channels. For fast channels, noSuchObject should be returned." REFERENCE "ITU-T G.997.1" -- section 7.3.2.3 ::= { vdslChanEntry 5 } vdslLineConfDownstreamTargetSlowBurstProtection OBJECT-TYPE SYNTAX Unsigned32 (0..1275) UNITS "microseconds" MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the target level of impulse noise (burst) protection for an interleaved (slow) channel." REFERENCE "ITU-T G.997.1" -- section 7.3.2.3 ::= { vdslLineConfProfileEntry 41 } vdslLineConfUpstreamTargetBurstProtection OBJECT-TYPE SYNTAX Unsigned32 (0..1275) UNITS "microseconds" MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the target level of impulse noise (burst) protection for an interleaved (slow) channel." REFERENCE "ITU-T G.997.1" -- section 7.3.2.3 ::= { vdslLineConfProfileEntry 42 } vdslLineConfDownstreamMaxFastFecOverhead OBJECT-TYPE SYNTAX Unsigned32 (0..50) UNITS "%" MAX-ACCESS read-create STATUS current DESCRIPTION "This parameter provisions the maximum level of Forward Error Correction (FEC) redundancy related overhead to be maintained for the Fast channel." ::= { vdslLineConfProfileEntry 43 } vdslLineConfUpstreamMaxFastFecOverhead OBJECT-TYPE SYNTAX Unsigned32 (0..50) UNITS "%" MAX-ACCESS read-create STATUS current DESCRIPTION "This parameter provisions the maximum level of Forward Error Correction (FEC) redundancy related overhead to be maintained for the Fast channel." ::= { vdslLineConfProfileEntry 44 } _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Wed Apr 30 14:10:42 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15491 for ; Wed, 30 Apr 2003 14:10:42 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3UIGLD28981 for adslmib-archive@odin.ietf.org; Wed, 30 Apr 2003 14:16:21 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UIGK828978 for ; Wed, 30 Apr 2003 14:16:20 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15453 for ; Wed, 30 Apr 2003 14:10:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Aw46-0002BG-00 for adslmib-web-archive@ietf.org; Wed, 30 Apr 2003 14:12:22 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Aw46-0002BD-00 for adslmib-web-archive@ietf.org; Wed, 30 Apr 2003 14:12:22 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UIG5828858; Wed, 30 Apr 2003 14:16:05 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3UIFP828731 for ; Wed, 30 Apr 2003 14:15:25 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15422 for ; Wed, 30 Apr 2003 14:09:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Aw3D-0002Ap-00 for adslmib@ietf.org; Wed, 30 Apr 2003 14:11:27 -0400 Received: from avocet.mail.pas.earthlink.net ([207.217.120.50]) by ietf-mx with esmtp (Exim 4.12) id 19Aw3C-0002Am-00 for adslmib@ietf.org; Wed, 30 Apr 2003 14:11:27 -0400 Received: from h-68-165-66-75.snvacaid.covad.net ([68.165.66.75] helo=oemcomputer) by avocet.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 19Aw3p-0000JN-00 for adslmib@ietf.org; Wed, 30 Apr 2003 11:12:05 -0700 Message-ID: <002501c30f43$ecaa11e0$7f1afea9@oemcomputer> From: "Randy Presuhn" To: "adslmib mail list" References: