[netmod] [Technical Errata Reported] RFC6991 (7062)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 29 July 2022 17:32 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19AC7C15A724 for <netmod@ietfa.amsl.com>; Fri, 29 Jul 2022 10:32:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.659
X-Spam-Level:
X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id if1pVM8AhQyz for <netmod@ietfa.amsl.com>; Fri, 29 Jul 2022 10:32:36 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF8E5C15A732 for <netmod@ietf.org>; Fri, 29 Jul 2022 10:32:27 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 6621F4C29E; Fri, 29 Jul 2022 10:32:27 -0700 (PDT)
To: j.schoenwaelder@jacobs-university.de, warren@kumari.net, rwilton@cisco.com, kent+ietf@watsen.net, joelja@bogus.com, lberger@labn.net
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: mazhar.rana@sophos.com, netmod@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20220729173227.6621F4C29E@rfcpa.amsl.com>
Date: Fri, 29 Jul 2022 10:32:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/h3UFcVmLsusQl6mm8sZ_HaXwz_4>
Subject: [netmod] [Technical Errata Reported] RFC6991 (7062)
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2022 17:32:40 -0000

The following errata report has been submitted for RFC6991,
"Common YANG Data Types".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7062

--------------------------------------
Type: Technical
Reported by: Mazhar Rana <mazhar.rana@sophos.com>

Section: 4

Original Text
-------------
     typedef ipv4-address-no-zone {
       type inet:ipv4-address {
         pattern '[0-9\.]*';
       }
       description
         "An IPv4 address without a zone index.  This type, derived from
          ipv4-address, may be used in situations where the zone is
          known from the context and hence no zone index is needed.";
     }

Corrected Text
--------------
     typedef ipv4-address-no-zone {
       type inet:ipv4-address {
         pattern '(([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\.){3}'
         +  '([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])';
       }
       description
         "An IPv4 address without a zone index.  This type, derived from
          ipv4-address, may be used in situations where the zone is
          known from the context and hence no zone index is needed.";
     }

Notes
-----
As per RFC 4001, dotted decimal format of IPv4 address is typically written in decimal digits, formatted as four 8-bit fields that are separated by periods.

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  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC6991 (draft-ietf-netmod-rfc6021-bis-03)
--------------------------------------
Title               : Common YANG Data Types
Publication Date    : July 2013
Author(s)           : J. Schoenwaelder, Ed.
Category            : PROPOSED STANDARD
Source              : Network Modeling
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG