[imss] Re: DISCUSS on

Keith McCloghrie <kzm@cisco.com> Thu, 05 January 2006 22:55 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Eue1L-0000zp-HD; Thu, 05 Jan 2006 17:55:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Eue1K-0000zG-2p for imss@megatron.ietf.org; Thu, 05 Jan 2006 17:55:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05539 for <imss@ietf.org>; Thu, 5 Jan 2006 17:54:30 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Eue74-00026F-Ry for imss@ietf.org; Thu, 05 Jan 2006 18:01:44 -0500
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-3.cisco.com with ESMTP; 05 Jan 2006 14:55:35 -0800
X-IronPort-AV: i="3.99,335,1131350400"; d="scan'208"; a="387893686:sNHT30429800"
Received: from cisco.com (cypher.cisco.com [171.69.11.142]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k05MtYjt014092; Thu, 5 Jan 2006 14:55:35 -0800 (PST)
Received: (from kzm@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) id OAA08343; Thu, 5 Jan 2006 14:50:50 -0800 (PST)
From: Keith McCloghrie <kzm@cisco.com>
Message-Id: <200601052250.OAA08343@cisco.com>
To: bwijnen@lucent.com
Date: Thu, 5 Jan 2006 14:50:50 -0800 (PST)
In-Reply-To: <no.id> from "Wijnen, Bert (Bert)" at Jan 05, 2006 05:58:52 PM
X-Mailer: ELM [version 2.5 PL5]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit
Cc: margaret@thingmagic.com, imss@ietf.org, Keith McCloghrie <kzm@cisco.com>
Subject: [imss] Re: DISCUSS on
X-BeenThere: imss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet and Management Support for Storage Working Group <imss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imss>, <mailto:imss-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:imss@ietf.org>
List-Help: <mailto:imss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imss>, <mailto:imss-request@ietf.org?subject=subscribe>
Sender: imss-bounces@ietf.org
Errors-To: imss-bounces@ietf.org

Bert/Margaret,

Tha answer is documented in section 5.5 of draft-ietf-imss-fc-nsm-mib-05.txt
which says:

   The objects defined in the t11NsRegTable represent the values
   registered with the Name Server.  The SNMP agent MUST report the
   actual values, even if they are incorrectly formatted.  This is the
   reason why, for example, the two objects which represent IP-
   addresses, t11NsNodeIpAddress and t11NsPortIpAddress, have the SYNTAX
   of OCTET STRING, so that they are able to represent invalid values
   (which could not be represented using InetAddressType and
   InetAddress).

Keith.

 
> Keith and WG,
> 
>    Margaret Wasserman:
>    Discuss:
>    [2006-01-05] Is there a reason why this MIB includes IP
>    addresses stored as 16-byte octet strings, rather than
>    as InetAddress objects? (e.g. t11NsRegNodeIpAddress)
> 
> I guess the answer is in 
>        REFERENCE
>           "ANSI INCITS 387-2004, Fibre Channel - Generic
>            Services-4 (FC-GS-4)"
> 
> Or you may have answered it in an earlier email.
> 
> But I am in the middle of the IESG conf call now, so won't get to
> go check it untill later. Maybe you have the answer ready 
> right from the top of your head.
> 
> Bert
> 

_______________________________________________
imss mailing list
imss@ietf.org
https://www1.ietf.org/mailman/listinfo/imss