RE: [imss] Vancouver Minutes (DRAFT)

"Roger Cummings" <roger_cummings@symantec.com> Thu, 10 November 2005 23:18 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 1EaLgR-0002WR-Pf; Thu, 10 Nov 2005 18:18:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZvUQ-0004KD-4i for imss@megatron.ietf.org; Wed, 09 Nov 2005 14:20:10 -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 OAA01956 for <imss@ietf.org>; Wed, 9 Nov 2005 14:19:42 -0500 (EST)
Received: from silver.veritas.com ([143.127.12.111]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EZvkT-0006g0-UE for imss@ietf.org; Wed, 09 Nov 2005 14:36:46 -0500
Received: from sxchcon1-int.veritas.com (HELO SVLXCHCON1.enterprise.veritas.com) (10.137.18.171) by silver.veritas.com with ESMTP; 09 Nov 2005 11:19:50 -0800
Received: from hroxchcon1.enterprise.veritas.com ([10.67.33.17]) by SVLXCHCON1.enterprise.veritas.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 9 Nov 2005 11:19:49 -0800
Received: from hroxchcln1.enterprise.veritas.com ([10.67.33.21]) by hroxchcon1.enterprise.veritas.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 9 Nov 2005 14:19:48 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [imss] Vancouver Minutes (DRAFT)
Date: Wed, 09 Nov 2005 14:19:47 -0500
Message-ID: <EC41F8507437734C9D3679FEBC902E660263DC59@hroxchcln1.enterprise.veritas.com>
Thread-Topic: [imss] Vancouver Minutes (DRAFT)
Thread-Index: AcXlW8yjUvH4+6YVSfuimls3OhbsNAAAz7eA
From: Roger Cummings <roger_cummings@symantec.com>
To: Black_David@emc.com, imss@ietf.org
X-OriginalArrivalTime: 09 Nov 2005 19:19:48.0030 (UTC) FILETIME=[8CB735E0:01C5E562]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 10 Nov 2005 18:18:18 -0500
Cc:
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

David,

Thanks for posting the minutes so promptly.

Two minor points:

1) Bert made a suggestion that a message is sent to the Netconf mailing
list soliciting interest in helping with the schema definition. Is that
an AI to you or I?

2) I'd like to modify the last sentence to read " The FLIP concept and
suggested use of netconf will be discussed further at T11 before the
next imss meeting." The focus for December has to be resolving FAIS
Letter Ballot comments, and if that means that the FLIP discussion
doesn't get done until later, that's the way it should be.

Regards,




Roger

> -----Original Message-----
> From: imss-bounces@ietf.org [mailto:imss-bounces@ietf.org] On 
> Behalf Of Black_David@emc.com
> Sent: Wednesday, November 09, 2005 1:28 PM
> To: imss@ietf.org
> Subject: [imss] Vancouver Minutes (DRAFT)
> 
> Please send any corrections, etc. to the list.
> 
> Thanks,
> --David
> 
> Internet and Management Support for Storage (imss) WG Meeting 
> - Vancouver, Canada Tuesday, November 8, 2005: 1740-1840 
> Minutes - DRAFT
> ------------------------------------------------------
> 
> Administrivia, agenda bashing, draft status review, etc.: 15 min
> 		David L. Black, EMC (new imss WG chair)
> 	Blue sheets
> 	Note Well
> 	Milestones (see WG charter page on IETF web site)
> 	WG Draft status
> 		- IP over FC draft is in IETF Last Call
> 		- FAM and NSM MIBs should go to IETF Last Call by the
> 			end of next week (Keith McCloghrie and 
> Bert Wijnen
> 			will coordinate to make this happen).
> 		- Remaining 3 WG MIBs will go to WG Last Call by end
> 			of November.
> 
> --> Record status
> 
> T11.5 Status, Fibre Channel MIBs under development: 20 min
> 		Roger Cummings (Symantec, T11.5 chair)
> 
> See slides.
> 
> T11.5 has 3 more MIBs that will be sent to the imss WG - Zone 
> Server MIB, Registered State Change Notification MIB, and 
> Fabric Configuration Server MIB.  The imss WG's current Apr 
> 06 milestone to determine what to do next will be replaced by 
> a milestone (later in 2006) to work on these 3 MIBs.  These 3 
> MIBs may not be ready for handoff to imss prior to the next 
> IETF meeting, but the mechanism used in Paris for the VF MIB 
> can be reused - the imss WG can decide to accept the drafts 
> as official WG drafts subject to a pending T11 formal votes 
> to pass change control to the IETF.
> 
> T11.5 is considering assigning MIB development responsibility 
> to protocol development work groups instead of the current 
> approach of having a separate group that works on MIBs.  This 
> will be discussed at the T11 meetings in early December.
> 
> FLIP (FAIS Line Interface Protocol) Conceptual Discussion: 25 min
> 		Roger Cummings (Symantec, T11.5 chair)
> 	 draft-cummings-imss-flip-00.txt
> 
> See presentation.  Netconf appears promising for the 
> configuration aspects of FLIP, but currently contains no 
> support for events or notifications from the configured 
> device.  Use of netconf would result in functionality at the 
> level of the configuration model instead of a 1-1 match 
> between FAIS API calls and RPCs.  The required 
> event/notification mechanism needs to be capable of carrying 
> a fair amount of structured information - it is somewhat 
> analogous to the use of COPS to ask a policy decision point 
> "I just received this RSVP reservation request, what should I 
> do about it?".  There are also concerns about effective 
> transmission of bulk binary data (encoding in XML is 
> unworkable, but encapsulation or wrapping in XML is probably 
> ok).  The netconf group is not currently standardizing 
> schemas, but will want/need to, so this could be a timely 
> interaction between imss and netconf.
> 
> The FLIP concept and suggested use of netconf will be 
> discussed further in the early December T11 meetings.
> 
> _______________________________________________
> imss mailing list
> imss@ietf.org
> https://www1.ietf.org/mailman/listinfo/imss
> 

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