Re: [Adslmib] [Technical Errata Reported] RFC3728 (1791)

"Bert Wijnen \(IETF\)" <bertietf@bwijnen.net> Wed, 03 June 2009 11:34 UTC

Return-Path: <bertietf@bwijnen.net>
X-Original-To: adslmib@core3.amsl.com
Delivered-To: adslmib@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DBCE23A69D9 for <adslmib@core3.amsl.com>; Wed, 3 Jun 2009 04:34:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.173
X-Spam-Level:
X-Spam-Status: No, score=0.173 tagged_above=-999 required=5 tests=[AWL=0.615, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GSSYTQl9OLvz for <adslmib@core3.amsl.com>; Wed, 3 Jun 2009 04:34:32 -0700 (PDT)
Received: from relay.versatel.net (beverwijk.tele2.vuurwerk.nl [62.250.3.53]) by core3.amsl.com (Postfix) with ESMTP id E65803A6BE9 for <adslmib@ietf.org>; Wed, 3 Jun 2009 04:33:42 -0700 (PDT)
Received: from [87.215.199.34] (helo=BertLaptop) by relay.versatel.net with smtp (Exim 4.69) (envelope-from <bertietf@bwijnen.net>) id 1MBoiY-0000u1-Ft; Wed, 03 Jun 2009 13:33:14 +0200
Message-ID: <026FDE304BE349A998527EBC9AFB4DEE@BertLaptop>
From: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, RFC Errata System <rfc-editor@rfc-editor.org>, rray@pesa.com, Rajesh.Abbi@alcatel.com, rbonica@juniper.net, sneedmike@hotmail.com, Menachem.Dodge@ecitele.com
References: <200906031104.n53B4Q9L029447@boreas.isi.edu> <EDC652A26FB23C4EB6384A4584434A04017573BE@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04017573BE@307622ANEX5.global.avaya.com>
Date: Wed, 03 Jun 2009 13:32:56 +0200
Organization: Consultant
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0857_01C9E44F.CDC7EA30"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6001.18000
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049
Cc: adslmib@ietf.org, smadar_t@rad.com
Subject: Re: [Adslmib] [Technical Errata Reported] RFC3728 (1791)
X-BeenThere: adslmib@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: ADSLMIB <adslmib.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/adslmib>, <mailto:adslmib-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/adslmib>
List-Post: <mailto:adslmib@ietf.org>
List-Help: <mailto:adslmib-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/adslmib>, <mailto:adslmib-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jun 2009 11:34:34 -0000

I am fine with this new one.

Bert
  ----- Original Message ----- 
  From: Romascanu, Dan (Dan) 
  To: RFC Errata System ; rray@pesa.com ; Rajesh.Abbi@alcatel.com ; rbonica@juniper.net ; sneedmike@hotmail.com ; Menachem.Dodge@ecitele.com 
  Cc: adslmib@ietf.org ; smadar_t@rad.com 
  Sent: Wednesday, June 03, 2009 1:09 PM
  Subject: Re: [Adslmib] [Technical Errata Reported] RFC3728 (1791)


  Based on the previous discussions, unless I hear any objections in the
  next 24 hours I will approve this Errata Report by entering it in
  Verified state. 

  Dan


  > -----Original Message-----
  > From: RFC Errata System [mailto:rfc-editor@rfc-editor.org] 
  > Sent: Wednesday, June 03, 2009 2:04 PM
  > To: rray@pesa.com; Rajesh.Abbi@alcatel.com; Romascanu, Dan 
  > (Dan); rbonica@juniper.net; sneedmike@hotmail.com; 
  > Menachem.Dodge@ecitele.com
  > Cc: smadar_t@rad.com; adslmib@ietf.org; rfc-editor@rfc-editor.org
  > Subject: [Technical Errata Reported] RFC3728 (1791)
  > 
  > 
  > The following errata report has been submitted for RFC3728, 
  > "Definitions of Managed Objects for Very High Speed Digital 
  > Subscriber Lines (VDSL)".
  > 
  > --------------------------------------
  > You may review the report below and at:
  > http://www.rfc-editor.org/errata_search.php?rfc=3728&eid=1791
  > 
  > --------------------------------------
  > Type: Technical
  > Reported by: Smadar Tauber <smadar_t@rad.com>
  > 
  > Section: Global
  > 
  > Original Text
  > -------------
  > UNITS definition of the following MIB objects, should change 
  > from dBm to dB.
  > That will also fix the conflict with the units appearing in 
  > the Description of these MIB objects (dB).
  > 
  > vdslPhysCurrSnrMgn
  > vdslPhysCurrAtn
  > vdslLineConfDownMaxSnrMgn
  > vdslLineConfDownMinSnrMgn
  > vdslLineConfDownTargetSnrMgn
  > vdslLineConfUpMaxSnrMgn
  > vdslLineConfUpMinSnrMgn
  > vdslLineConfUpTargetSnrMgn
  > 
  > Example of original text:
  >    vdslPhysCurrSnrMgn OBJECT-TYPE
  >        SYNTAX       Integer32 (-127..127)
  >        UNITS        "0.25dBm"
  >        MAX-ACCESS   read-only
  >        STATUS       current
  >        DESCRIPTION
  >            "Noise Margin as seen by this Vtu with respect to its
  >            received signal in 0.25dB.  The effective range is
  >            -31.75 to +31.75 dB."
  >        REFERENCE    "T1E1.4/2000-009R3, Part 1, common spec"
  >         ::= { vdslPhysEntry 5 }
  > 
  > Corrected Text
  > --------------
  > Example of corrected text:
  >    vdslPhysCurrSnrMgn OBJECT-TYPE
  >        SYNTAX       Integer32 (-127..127)
  >        UNITS        "0.25dB"
  >        MAX-ACCESS   read-only
  >        STATUS       current
  >        DESCRIPTION
  >            "Noise Margin as seen by this Vtu with respect to its
  >            received signal in 0.25dB.  The effective range is
  >            -31.75 to +31.75 dB."
  >        REFERENCE    "T1E1.4/2000-009R3, Part 1, common spec"
  >         ::= { vdslPhysEntry 5 }
  > 
  > 
  > Notes
  > -----
  > This Errata replaces errata 1788 (rejected because it did not 
  > include list of all MIB objects having this problem and could 
  > not be edited). 
  > It was decided by the adslmib Forum, that the solution should 
  > be as described by this Errata.
  > 
  > Instructions:
  > -------------
  > This errata is currently posted as "Reported". If necessary, 
  > please use "Reply All" to discuss whether it should be 
  > verified or rejected. When a decision is reached, the 
  > verifying party (IESG) can log in to change the status and 
  > edit the report, if necessary. 
  > 
  > --------------------------------------
  > RFC3728 (draft-ietf-adslmib-vdsl-12)
  > --------------------------------------
  > Title               : Definitions of Managed Objects for Very 
  > High Speed Digital Subscriber Lines (VDSL)
  > Publication Date    : February 2004
  > Author(s)           : B. Ray, R. Abbi
  > Category            : PROPOSED STANDARD
  > Source              : ADSL MIB
  > Area                : Operations and Management
  > Stream              : IETF
  > Verifying Party     : IESG
  > 
  _______________________________________________
  Adslmib mailing list
  Adslmib@ietf.org
  https://www.ietf.org/mailman/listinfo/adslmib



------------------------------------------------------------------------------



  No virus found in this incoming message.
  Checked by AVG - www.avg.com 
  Version: 8.5.339 / Virus Database: 270.12.51/2151 - Release Date: 06/02/09 17:53:00