attachment
<html><body>
<DIV>Jerry had some interesting comments relative to the subjects of today's concal.</DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>1. The LCRC-?????-?????.doc document is actually intended to be a version of the specification that includes </FONT><FONT face=sans-serif size=2>changes as a result of the last call, not the document list of changes or change log.</FONT> <BR><BR><FONT face=sans-serif size=2>2. I thought we were going to modify figure 8 to include a legacy/SNMP agent somewhere in the tree??</FONT> </DIV>
<DIV> </DIV>
<DIV>Taking the second question first, I did add a legacy unit to the sequence diagram, but not to the topology sketch. I have posted a revised figure 8 at <A href="ftp://ftp.pwg.org/pub/pwg/wims/white/complex_topology2.pdf">ftp://ftp.pwg.org/pub/pwg/wims/white/complex_topology2.pdf</A> for consideration.</DIV>
<DIV> </DIV>
<DIV>With respect to the first issue, I am aware that we have been doing as Jerry indicates, but I checked the process document and neither the Process document nor the sense of the words Last Call Review Comments suggests that LCRC refers to an actual copy of the revised reveiwed document. (perhaps Last Call Review Copy?) Specifically, under Chapter 7 of the process document, it states:
<DIV>
<P align=left>"Supporting documents (see Section 5) are posted in the root Working Group path or a subdivision of that path as appropriate. Filename prefixes for common supporting documents are: </P>
<P align=left>White Paper and Technical Brief – tb </P>
<P align=left>Last Call Review Comments - lcrc "</P>
<P align=left>That is the only reference to LCRC in the document. In Chapter 8, it states</P>
<P align=left>"All issues and their resolution from the most recent Last Call must be published in the Formal Approval announcement. "</P>
<P align=left>So, it would appear the the last call comments should be in the call for vote messageindepedentt of the document itself.</P>
<P align=left>So, since the use of lcrc has been bugging me for a while, I though I would put it to a test. Easy enough to revert to the previous approach if thatrepresetss consensus.</P>Bill Wagner<BR></DIV></DIV></body></html>