attachment
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns:xsd><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META content="MSHTML 6.00.2800.1522" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=176405900-08022006><FONT face=Arial color=#0000ff size=4>Hi
Bill,</FONT></SPAN></DIV>
<DIV><SPAN class=176405900-08022006><FONT face=Arial color=#0000ff
size=4></FONT></SPAN> </DIV>
<DIV><SPAN class=176405900-08022006><FONT face=Arial color=#0000ff size=4>Thanks
- then I'll take a crack at updating the schemas
accordingly.</FONT></SPAN></DIV>
<DIV><SPAN class=176405900-08022006><FONT face=Arial color=#0000ff size=4>I've
got the flu, so I may not get the schema updates out by next
week.</FONT></SPAN></DIV>
<DIV><SPAN class=176405900-08022006><FONT face=Arial color=#0000ff
size=4></FONT></SPAN> </DIV>
<DIV><SPAN class=176405900-08022006><FONT face=Arial color=#0000ff
size=4>Cheers,</FONT></SPAN></DIV>
<DIV><SPAN class=176405900-08022006><FONT face=Arial color=#0000ff size=4>-
Ira</FONT></SPAN></DIV>
<DIV> </DIV>
<P><FONT size=2>Ira McDonald (Musician / Software Architect)<BR>Blue Roof Music
/ High North Inc<BR>PO Box 221 Grand Marais, MI 49839<BR>phone:
+1-906-494-2434<BR>email: imcdonald@sharplabs.com</FONT> </P>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> owner-wims@pwg.org
[mailto:owner-wims@pwg.org]<B>On Behalf Of
</B>wamwagner@comcast.net<BR><B>Sent:</B> Tuesday, February 07, 2006 6:10
PM<BR><B>To:</B> 'wims@pwg.org'<BR><B>Subject:</B> Re: WIMS> Changes for
multi-level WIMS Proxy configurations<BR><BR></FONT></DIV>
<DIV>I will take a crack at implementing these changes to the document so that
they can be considered in context. Should have this posted by
the weekend. Would apprecaite review by WG members so that we can have
detailed discussion on 15 Feb. But if you have comments to Ira's message
earlier, please send them.</DIV>
<DIV> </DIV>
<DIV>Feb 8 WIMS protocol concall remains cancelled. I have not seen any
messge from Pete on SM call in that spot.</DIV>
<DIV> </DIV>
<DIV>Bill Wagner</DIV>
<DIV> </DIV>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">--------------
Original message -------------- <BR>From: "McDonald, Ira"
<imcdonald@sharplabs.com> <BR><BR>> Hi folks, Tuesday (7 February
2006) <BR>> <BR>> Below are proposed WIMS Protocol spec and WIMS XML
schema updates for <BR>> support of multi-level (or 'chained') WIMS Proxy
configurations that we <BR>> discussed at the January PWG face-to-face
and last week's WIMS telecon. <BR>> <BR>> Basically, in _every_ Action
_except_ UpdateSchedule, replace the <BR>> (one-level) 'agentReferences :
AgentReferences' parameter with a <BR>> (multi-level) 'agentPaths :
AgentPaths' parameter (see below). <BR>> <BR>> UpdateSchedule MUST NOT
be forwarded and MUST still use a single-valued <BR>> 'agentReference :
AgentReference' parameter that MUST resolve to the <BR>> local
(receiving) WIMS Agent. <BR>> <BR>> <BR>> The processing model is
simple: <!
BR>> <BR>> (1) WIMS Proxy receives incoming 'Action' from adjacent
upstream WIMS <BR>> Manager (via running Schedule or ExecuteAction
request). <BR>> (2) WIMS Proxy rewrites 'ActionAgentPaths' of 'Action',
removing the <BR>> _first_ WIMS Agent reference (to itself) in each agent
path in the <BR>> array of paths. <BR>> (3) WIMS Proxy forwards
rewritten 'Action' to the adjacent downstream <BR>> WIMS Agents via
ExecuteAction requests and/or Legacy Agents via <BR>> legacy protocol
requests (e.g., SNMP Set). <BR>> (4) Recursion of steps (1) to (3) leads
to final WIMS Agents or Legacy <BR>> Agents (nearest to actual managed
entities). <BR>> (5) Upstream ExecuteAction or legacy protocol responses
convey resulting <BR>> status back to original WIMS Proxy who conveys
resulting status <BR>> back via SendReports request or ExecuteAction
response to original <BR>> WIMS Manager. <BR>> <BR>> <BR>> Note:
ExecuteAction is used here for ! operation forwarding downstream in <BR>>
order to preserve ! the 'imm ediate' nature of a triggered Action in a
<BR>> Schedule. It would be possible to forward operations via downstream
<BR>> Schedule objects, but vastly more complicated to correlate the
responses <BR>> and not faithful to an 'immediate' trigger. <BR>>
<BR>> Comments? <BR>> <BR>> Cheers, <BR>> - Ira <BR>>
<BR>> <BR>> Ira McDonald (Musician / Software Architect) <BR>> Blue
Roof Music / High North Inc <BR>> PO Box 221 Grand Marais, MI 49839
<BR>> phone: +1-906-494-2434 <BR>> email: imcdonald@sharplabs.com
<BR>> <BR>>
------------------------------------------------------------------------
<BR>> [WIMS Protocol spec] <BR>> <BR>> <BR>> [diagrams and notes
in section 4] <BR>> <BR>> [change] <BR>> agentReferences <BR>>
[to] <BR>> agentPaths <BR>> <BR>> <BR>> [definition in section
6.1.1 - note plural 'Paths'] <BR>> <BR>> [change] <BR>>
agentReferences : AgentReferences <BR>> [to] <BR>&g! t; agentPaths :
AgentPaths <BR>> <BR>> [change] <BR>> References to the WIMS...
<BR>> [to] <BR>> Paths to the WIMS... <BR>> <BR>> <BR>>
[definition in section 6.1.3 - note plural 'Paths'] <BR>> <BR>>
[change] <BR>> agentReferences : AgentReferences <BR>> [to] <BR>>
agentPaths : AgentPaths <BR>> <BR>> [change] <BR>> References to
the WIMS... <BR>> [to] <BR>> Paths to the WIMS... <BR>> <BR>>
<BR>> [RegisterForManagement in section 6.2.1 - note plural 'Paths']
<BR>> <BR>> [change] <BR>> agentReferences : AgentReferences
<BR>> [to] <BR>> agentPaths : AgentPaths <BR>> <BR>> <BR>>
[UnregisterForManagement in section 6.2.2 - note plural 'Paths'] <BR>>
<BR>> [change] <BR>> agentReferences : AgentReferences <BR>> [to]
<BR>> agentPaths : AgentPaths <BR>> <BR>> <BR>> [actions in
sections 6.4, 6.5, and 6.6 - note plural 'Paths'] <BR>> <BR>> [change]
<BR>> agentReferen! ces : AgentReferences <BR>> [to] <BR>>
agentPaths : Agen! tPaths < BR>> <BR>> <BR>>
------------------------------------------------------------------------
<BR>> [WIMS Message schema] <BR>> <BR>> <BR>>
[RegisterForManagement and UnregisterForManagement requests] <BR>>
<BR>> [change] <BR>> RequestAgentReferences <BR>> [to] <BR>>
RequestAgentPaths <BR>> <BR>> <BR>>
------------------------------------------------------------------------
<BR>> [WIMS Type schema] <BR>> <BR>> <BR>> [add two new types]
<BR>> <BR>> <xsd:complexType name="ObjectAgentPath"><BR>> <!-- path to legacy or WIMS agent nearest to a managed entity --><BR>> <!-- for support of multi-level WIMS Proxy configurations --><BR>>
<xsd:sequence><BR>> <xsd:element name="ObjectAgentReference" <BR>>
type="ObjectAgentReference" <BR>> minOccurs="0"
maxOccurs="unbounded"/> <BR>> </xsd:sequence><BR>>
</xsd:complexType><BR>> <BR>> <xsd:complexType
name="ObjectAgent! Paths"><BR>> <xsd:sequence><BR>>
<xsd:element name="ObjectAgentPath" <BR>> type="ObjectAgentPath" <BR>>
minOccurs="0" maxOccurs="unbounded"/> <BR>> </xsd:sequence><BR>>
</xsd:complexType><BR>> <BR>> <BR>>
------------------------------------------------------------------------
<BR>> [WIMS Schedule schema] <BR>> <BR>> <BR>> [delete unused
'ActionAgentReferences' element] <BR>> <BR>> <BR>> [add new
'ActionAgentPaths' element] <BR>> <BR>> <xsd:element
name="ActionAgentPaths" <BR>> type="ObjectAgentPaths"/> <BR>> <!-- OPTIONAL - MAY be multi-valued --><BR>> <!-- paths to legacy or WIMS agents nearest to managed entities --><BR>> <!-- for support of multi-level WIMS Proxy configurations --><BR>>
<BR>> <BR>> [modify each action in WIMS Schedule schema, for example]
<BR>> <BR>> <xsd:element name="ActionGetElements"><BR>>
<xsd:complexType name="ActionGetElements" <BR>> <xsd:sequence><BR>>! ;
<xsd:element <BR ref="ActionAgentPaths">> minOccurs="0" m! axOccurs
="1"/> <BR>> <xsd:element <BR ref="ActionTargetObjects">>
minOccurs="0" maxOccurs="1"/> <BR>> <xsd:element <BR
ref="ActionRequestedElements">> minOccurs="0" maxOccurs="1"/> <BR>>
<xsd:element <BR ref="ActionVendorParameters">> minOccurs="0"
maxOccurs="1"/> <BR>> </xsd:sequence><BR>>
</xsd:complexType><BR>> </xsd:element><BR>> <BR>> <BR>>
------------------------------------------------------------------------
</BLOCKQUOTE></BLOCKQUOTE></xsd:element></xsd:element></xsd:element></xsd:element></xsd:element></xsd:element></xsd:element></BODY></HTML>