[PWE3] [Technical Errata Reported] RFC5601 (4069)
RFC Errata System <rfc-editor@rfc-editor.org> Tue, 05 August 2014 08:34 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6604D1B28B4 for <pwe3@ietfa.amsl.com>; Tue, 5 Aug 2014 01:34:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.903
X-Spam-Level:
X-Spam-Status: No, score=-106.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 WYiINIm7ScZp for <pwe3@ietfa.amsl.com>; Tue, 5 Aug 2014 01:34:55 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 78E391B289D for <pwe3@ietf.org>; Tue, 5 Aug 2014 01:34:55 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4515C180095; Tue, 5 Aug 2014 01:33:31 -0700 (PDT)
To: thomas.nadeau@bt.com, davidz@oversi.com, brian@innovationslab.net, ted.lemon@nominum.com, matthew.bocci@alcatel-lucent.com, agmalis@gmail.com
X-PHP-Originating-Script: 6000:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20140805083331.4515C180095@rfc-editor.org>
Date: Tue, 05 Aug 2014 01:33:31 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/pwe3/wRGqmSfKXXM8Se6zzfkyDpbG0Vw
Cc: pwe3@ietf.org, rfc-editor@rfc-editor.org
Subject: [PWE3] [Technical Errata Reported] RFC5601 (4069)
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3/>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Aug 2014 08:34:57 -0000
The following errata report has been submitted for RFC5601, "Pseudowire (PW) Management Information Base (MIB)". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5601&eid=4069 -------------------------------------- Type: Technical Reported by: Alexander ("Sasha") Vainshtein <Alexander.Vainshtein@ecitele.com> Section: 12 Original Text ------------- pwAttachedPwIndex OBJECT-TYPE SYNTAX PwIndexOrZeroType MAX-ACCESS read-create STATUS current DESCRIPTION "If the PW is attached to another PW instead of a local native service, this item indicates the pwIndex of the attached PW. Otherwise, this object MUST be set to zero. Attachment to another PW will have no PW specific entry in any of the service MIB modules." DEFVAL { 0 } ::= { pwEntry 10 } Corrected Text -------------- pwAttachedPwIndex OBJECT-TYPE SYNTAX PwIndexOrZeroType MAX-ACCESS read-create STATUS current DESCRIPTION "If the PW is attached to another PW instead of a local native service, this item indicates the pwIndex of the attached PW. Otherwise, this object MUST be set to zero. Attachment to another PW will have no PW specific entry in any of the service MIB modules. With regard to this attribute read-create means that its value can be changed when the containing row in the pwTable represents an inactive PW." DEFVAL { 0 } ::= { pwEntry 10 } Notes ----- Description of the pwEntry object in the same RFC states that "The read-create objects in this table are divided into three categories: 1) Objects that MUST NOT be changed after row activation. These are objects that define basic properties of the PW (for example type, destination, etc.). 2) Objects that MAY be changed when the PW is defined as not active. A change of these objects involves re-signaling of the PW or it might be traffic affecting. PW not active is defined as one of the following conditions: a) The pwRowStatus is notInService(2). b) The pwRowStatus is notReady(3). c) The pwAdminStatus is down(2). If the operator needs to change one of the values for an active row, the operator can either set the pwRowStatus to notInService(2) or set pwAdminStatus to down(2). Signaling (or traffic) is initiated again upon setting the pwRowStatus to active(1) or setting the pwAdminStatus to up(1) or testing(3), respectively. 3) Objects that MAY be changed at any time." In further states (in tthe same description) that "By default, all the read-create objects MUST NOT be changed after row activation, unless specifically indicated in the individual object description." pwAttachedPwIndex object is used to stitch a couple of PWs represented by two different rows in the pwTable, with the pwAttachedPwIndex value in the row representing one of them set to the pwIndex of the other one and vice versa. Since there is no way in the SMIv2 paradigm to create two rows in the same table in a single atomic operation, setting a this attribute in a pair of rows is only possible when both are created. In order to do that, read-create access mode of the pwAttachedPwIndex object has to be interpreted as ability to set its value when the row represents an inactive PW. In accordance with the quoted description, such an interpretation must be explicitly specified in the description of this object. Such a specification is missing in the current text, hence the default interpretation of the read-create access mode is holds. Proposed text fixes this problem. 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. -------------------------------------- RFC5601 (draft-ietf-pwe3-pw-mib-14) -------------------------------------- Title : Pseudowire (PW) Management Information Base (MIB) Publication Date : July 2009 Author(s) : T. Nadeau, Ed., D. Zelig, Ed. Category : PROPOSED STANDARD Source : Pseudo Wire Emulation Edge to Edge INT Area : Internet Stream : IETF Verifying Party : IESG
- [PWE3] [Technical Errata Reported] RFC5601 (4069) RFC Errata System
- [PWE3] [Errata Verified] RFC5601 (4069) RFC Errata System
- Re: [PWE3] [Errata Verified] RFC5601 (4069) Alexander Vainshtein
- Re: [PWE3] [Errata Verified] RFC5601 (4069) Andrew G. Malis
- Re: [PWE3] [Errata Verified] RFC5601 (4069) Alexander Vainshtein