[Idr] [Errata Held for Document Update] RFC4273 (3782)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 22 November 2013 09:41 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A41071ACCF9; Fri, 22 Nov 2013 01:41:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.427
X-Spam-Level:
X-Spam-Status: No, score=-2.427 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.525, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ivySSuh6d3BW; Fri, 22 Nov 2013 01:41:17 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:126c::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 1D8ED1ACAD7; Fri, 22 Nov 2013 01:41:17 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 8D34775E019; Fri, 22 Nov 2013 01:30:45 -0800 (PST)
To: ramakrishnadtv@infosys.com, jhaas@nexthop.com, skh@nexthop.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20131122093045.8D34775E019@rfc-editor.org>
Date: Fri, 22 Nov 2013 01:30:45 -0800
Cc: idr@ietf.org, rfc-editor@rfc-editor.org, iesg@ietf.org
Subject: [Idr] [Errata Held for Document Update] RFC4273 (3782)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 22 Nov 2013 09:41:18 -0000

The following errata report has been held for document update 
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

--------------------------------------
Status: Held for Document Update
Type: Editorial

Reported by: Ramakrishna DTV <ramakrishnadtv@infosys.com>
Date Reported: 2013-11-04
Held by: Stewart Bryant (IESG)

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".

--------------------------------------
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