[netmod] error-message

JOEY BOYD <joey.boyd@adtran.com> Mon, 04 March 2019 15:37 UTC

Return-Path: <joey.boyd@adtran.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 883F81310BA for <netmod@ietfa.amsl.com>; Mon, 4 Mar 2019 07:37:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
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 9FGmAR6P6XeP for <netmod@ietfa.amsl.com>; Mon, 4 Mar 2019 07:37:17 -0800 (PST)
Received: from us-smtp-delivery-128.mimecast.com (us-smtp-delivery-128.mimecast.com [216.205.24.128]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04FDF12D7EA for <netmod@ietf.org>; Mon, 4 Mar 2019 07:37:16 -0800 (PST)
Received: from ex-hc1.corp.adtran.com (ex-hc1.adtran.com [76.164.174.81]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-95-XLHBqnwyMDS6Sp2u9s471w-3; Mon, 04 Mar 2019 10:37:13 -0500
Received: from ex-mb3.corp.adtran.com ([fe80::60aa:f95:ad49:a0f1]) by ex-hc1.corp.adtran.com ([fe80::a43f:7ea6:7688:37b%13]) with mapi id 14.03.0382.000; Mon, 4 Mar 2019 09:36:39 -0600
From: JOEY BOYD <joey.boyd@adtran.com>
To: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: error-message
Thread-Index: AdTSn2llQGSojFl0QmmWuHXdWeKWOQ==
Date: Mon, 4 Mar 2019 15:36:38 +0000
Message-ID: <26CE489EF4611643B3EFE43D06E02654018CCE2A94@ex-mb3.corp.adtran.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.22.118.104]
MIME-Version: 1.0
X-MC-Unique: XLHBqnwyMDS6Sp2u9s471w-3
X-Mimecast-Spam-Score: 0
Content-Type: multipart/alternative; boundary="_000_26CE489EF4611643B3EFE43D06E02654018CCE2A94exmb3corpadtr_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/rzhBE-ikPtc-SD1zi24Pm41QFgc>
Subject: [netmod] error-message
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 04 Mar 2019 15:37:20 -0000

Hi,

Is the addition of an 'error-message' to an existing 'must' statement considered backward compatible? I don't see 'error-message' mentioned in the "Updating a Module" section which leads me to believe that it isn't but wanted to double check to see what implications adding one to an existing module would have.

Thanks and regards,
Joey