[Idr] [Editorial Errata Reported] RFC4273 (3782)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 05 November 2013 06:49 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38D3321E809E for <idr@ietfa.amsl.com>; Mon, 4 Nov 2013 22:49:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.436
X-Spam-Level:
X-Spam-Status: No, score=-102.436 tagged_above=-999 required=5 tests=[AWL=0.164, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p77alHJh4qSw for <idr@ietfa.amsl.com>; Mon, 4 Nov 2013 22:49:50 -0800 (PST)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id BEA9921F9AE7 for <idr@ietf.org>; Mon, 4 Nov 2013 22:49:50 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id BB22075E011; Mon, 4 Nov 2013 22:40:27 -0800 (PST)
To: jhaas@nexthop.com, skh@nexthop.com, stbryant@cisco.com, adrian@olddog.co.uk, shares@ndzh.com, jgs@juniper.net
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20131105064027.BB22075E011@rfc-editor.org>
Date: Mon, 04 Nov 2013 22:40:27 -0800
Cc: idr@ietf.org, rfc-editor@rfc-editor.org
Subject: [Idr] [Editorial Errata Reported] RFC4273 (3782)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 06:49:51 -0000

The following errata report has been submitted for RFC4273,
"Definitions of Managed Objects for BGP-4".

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

--------------------------------------
Type: Editorial
Reported by: Ramakrishna DTV <ramakrishnadtv@infosys.com>

Section: 5

Original Text
-------------
There are several management objects defined in this MIB that have a
MAX-ACCESS clause of read-write and/or read-create.

Corrected Text
--------------
There are several management objects defined in this MIB that have a
MAX-ACCESS clause of read-write.

Notes
-----
No object in this MIB has MAX-ACCESS clause of "read-create".

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. 

--------------------------------------
RFC4273 (draft-ietf-idr-bgp4-mib-15)
--------------------------------------
Title               : Definitions of Managed Objects for BGP-4
Publication Date    : January 2006
Author(s)           : J. Haas, Ed., S. Hares, Ed.
Category            : PROPOSED STANDARD
Source              : Inter-Domain Routing
Area                : Routing
Stream              : IETF
Verifying Party     : IESG