Subject: [Adslmib] [Errata Verified] RFC6767 (4417)

From: RFC Errata System <[email-masked]>
Date: Fri, 17 Jul 2015 07:56:29 -0700 (PDT)

The following errata report has been verified for RFC6767,
"Ethernet-Based xDSL Multi-Pair Bonding (G.Bond/Ethernet) MIB". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6767&eid=4417

--------------------------------------
Status: Verified
Type: Technical

Reported by: Yixi Lu <[email-masked]>
Date Reported: 2015-07-17
Verified by: Benoit Claise (IESG)

Section: 6

Original Text
-------------
g9982BasicGroup OBJECT-GROUP
     OBJECTS {
       g9982PortCapTcTypesSupported,
       g9982PortCapBacpSupported,
       g9982PortConfTcAdminType,
       g9982PortStatTcOperType,
       g9982PortStatRxErrors,
       g9982PortStatRxSmallFragments,
       g9982PortStatRxLargeFragments,
       g9982PortStatRxBadFragments,
       g9982PortStatRxLostFragments,
       g9982PortStatRxLostStarts,
       g9982PortStatRxLostEnds,
       g9982PortStatRxOverflows,
|      g9982BceStatTcInCodingErrors,
|      g9982BceStatTcInCrcErrors
     }
     STATUS      current

Corrected Text
--------------
g9982BasicGroup OBJECT-GROUP
     OBJECTS {
       g9982PortCapTcTypesSupported,
       g9982PortCapBacpSupported,
       g9982PortConfTcAdminType,
       g9982PortStatTcOperType,
       g9982PortStatRxErrors,
       g9982PortStatRxSmallFragments,
       g9982PortStatRxLargeFragments,
       g9982PortStatRxBadFragments,
       g9982PortStatRxLostFragments,
       g9982PortStatRxLostStarts,
       g9982PortStatRxLostEnds,
       g9982PortStatRxOverflows
     }
     STATUS      current

Notes
-----
"g9982BceStatTcInCodingErrors,g9982BceStatTcInCrcErrors" should not appear in g9982BasicGroup when they already exist in g9982BceGroup.

--------------------------------------
RFC6767 (draft-ietf-adslmib-gbond-eth-mib-08)
--------------------------------------
Title               : Ethernet-Based xDSL Multi-Pair Bonding (G.Bond/Ethernet) MIB
Publication Date    : February 2013
Author(s)           : E. Beili, M. Morgenstern
Category            : PROPOSED STANDARD
Source              : ADSL MIB
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG

---

From: Benoit Claise <[email-masked]>
Date: Fri, 17 Jul 2015 17:00:55 +0200

Yixi, Randy,

Corrected and approved.

Thanks and regards, Benoit
> Hi,
> Yes. you're right.
> How can I correct it again?
>
> B.R.,
> Yixi
>
>> -----Original Message-----
>> From: Randy Presuhn [mailto:[email-masked]]
>> Sent: Friday, July 17, 2015 19:57
>> To: RFC Errata System <[email-masked]>;
>> [email-masked]; [email-masked];
>> [email-masked]; [email-masked]; [email-masked]
>> Cc: [email-masked]; Yixi Lu <[email-masked]>; [email-masked]
>> Subject: Re: [Adslmib] [Technical Errata Reported] RFC6767 (4417)
>>
>> Hi -
>>
>> The proposed "corrected" text appears to have a syntax error.
>> There should not be a "," (with or without whitespace) before the final "}".
>>
>> Randy
>>
>> -----Original Message-----
>>> From: RFC Errata System <[email-masked]>
>>> Sent: Jul 17, 2015 3:12 AM
>>> To: [email-masked], [email-masked],
>>> [email-masked], [email-masked], [email-masked]
>>> Cc: [email-masked], [email-masked], [email-masked]
>>> Subject: [Adslmib] [Technical Errata Reported] RFC6767 (4417)
>>>
>>> The following errata report has been submitted for RFC6767,
>>> "g9982BceStatTcInCodingErrors,g9982BceStatTcInCrcErrors" should not
>> appear in g9982BasicGroup when they already exist in g9982BceGroup.
>>> Instructions:
>>> -------------
>>> This erratum 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.
>>>
>>> _______________________________________________
>>> Adslmib mailing list
>>> [email-masked]
>>> https://www.ietf.org/mailman/listinfo/adslmib