[imss] FW: DISCUSS on draft-ietf-imss-fc-nsm-mib-05.txt

"Wijnen, Bert (Bert)" <bwijnen@lucent.com> Fri, 06 January 2006 17:30 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 1EuvQ6-0006da-MB; Fri, 06 Jan 2006 12:30:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EuvQ5-0006dI-St for imss@megatron.ietf.org; Fri, 06 Jan 2006 12:30:29 -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 MAA16669 for <imss@ietf.org>; Fri, 6 Jan 2006 12:29:13 -0500 (EST)
Received: from ihemail1.lucent.com ([192.11.222.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EuvW0-0000Sc-Es for imss@ietf.org; Fri, 06 Jan 2006 12:36:37 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id k06HULcW022161 for <imss@ietf.org>; Fri, 6 Jan 2006 11:30:22 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id <X5BSAA5T>; Fri, 6 Jan 2006 18:30:19 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15508FC8D22@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Imss (E-mail)" <imss@ietf.org>
Date: Fri, 06 Jan 2006 12:49:56 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Subject: [imss] FW: DISCUSS on draft-ietf-imss-fc-nsm-mib-05.txt
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

WG,

the DISCUSS has been cleared, and so the doc is approved by IESG.

Formal announcement will follow in the next few days by
IESG secretaray.

And the FAM MIB oducmnet was also approved yesterday.

Congrats, and thanks to the authors/editors.

Bert

-----Original Message-----
From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org]On Behalf Of
Margaret Wasserman
Sent: Friday, January 06, 2006 02:05
To: 'Wijnen, Bert (Bert)'; 'Keith McCloghrie (E-mail)'
Cc: 'Iesg (E-mail)'
Subject: RE: DISCUSS on



Yes.  I'm sorry that I didn't find that in my review.  I have removed my
discuss.

Margaret
 

> -----Original Message-----
> From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On 
> Behalf Of Wijnen, Bert (Bert)
> Sent: Thursday, January 05, 2006 6:39 PM
> To: Margaret Wasserman (E-mail); Keith McCloghrie (E-mail)
> Cc: Iesg (E-mail)
> Subject: FW: DISCUSS on
> 
> Thanks Keith.
> 
> Margareth, I think this allows you to clear your DISCUSS, right?
> 
> Bert
> 
> -----Original Message-----
> From: Keith McCloghrie [mailto:kzm@cisco.com]
> Sent: Thursday, January 05, 2006 23:51
> To: bwijnen@lucent.com
> Cc: imss@ietf.org; margaret@thingmagic.com; kzm@cisco.com
> Subject: Re: DISCUSS on
> 
> 
> 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