[Disman] RFC 3877 and IPv6

"Mark A. Flacy" <mflacy@verizon.net> Sat, 29 January 2011 22:19 UTC

Return-Path: <mflacy@verizon.net>
X-Original-To: disman@core3.amsl.com
Delivered-To: disman@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 153483A6894 for <disman@core3.amsl.com>; Sat, 29 Jan 2011 14:19:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id HXdi0UuF6e+v for <disman@core3.amsl.com>; Sat, 29 Jan 2011 14:19:02 -0800 (PST)
Received: from vms173013pub.verizon.net (vms173013pub.verizon.net []) by core3.amsl.com (Postfix) with ESMTP id 2C9543A6890 for <disman@ietf.org>; Sat, 29 Jan 2011 14:19:02 -0800 (PST)
Received: from flacy ([unknown] []) by vms173013.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0LFT00IXT24N7W81@vms173013.mailsrvcs.net> for disman@ietf.org; Sat, 29 Jan 2011 16:21:59 -0600 (CST)
Date: Sat, 29 Jan 2011 16:21:59 -0600
From: "Mark A. Flacy" <mflacy@verizon.net>
To: disman@ietf.org
X-Mailer: Balsa 2.4.8
Message-id: <1296339719.32535.0@flacy>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed
Content-disposition: inline
Content-transfer-encoding: quoted-printable
Subject: [Disman] RFC 3877 and IPv6
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: mflacy@verizon.net
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/disman>, <mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/disman>, <mailto:disman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jan 2011 22:19:03 -0000


In the version of RFC 3877 available at datatracker.ietf.org, I noticed  
that the alarmActiveVariableValueType does not include either  
InetAddressType or InetAddress in the enumeration which does not allow  
you to indicate an IPv6 address in the alarmActiveVariableTable.  The  
alarmActiveEngineAddress is expressed according to RFC 2851, so that is  
not a problem.

Will alarmActiveVariableValueType be extended to include  
InetAddressType and InetAddress (along with matching  
alarmActiveVariableInetAddressTypeVal and  
alarmActiveVariableInetAddressVal objects in AlarmActiveVariableEntry)?
Is there a recommended work-around?

Thank you!

Mark A. Flacy