On Sat, Jun 20, 2009 at 8:07 AM, Sundar Yamunachari<sundar.yamunachari at sun.com> wrote: > Hi, > > The updated functional specifications for AI transport mechanism - version > 2 is available at > http://wikis.sun.com/display/OSOLInstall/AI+Transport+Mechanism+v2+-+Functional+Specification ... > Please review and provide feedback.
[The section numbering seems a little, well, odd. I was going to use section numbers but couldn't make them align properly.] Is P2P an interesting use case for AI? I don't know, as I've never worked on a network that hasn't banned it outright. (I can see downloading the original ISO through P2P, but deploying systems?) You talk about providing observability as part of the user experience. I would expect the transport to be completely invisible to the user. The client or server would provide observability data to the user; they may derive some of it from the transport (although I wouldn't expect them to actually query the transport to get it in many cases. The terminology 'file transfer protocol' may be generic, but could also be construed as specifically referring to FTP. I'm not sure how relevant the supported configuration list is. What does it tell you about the requirements? You need to deal with any number of any sort of hardware of any configuration; equally important is how frequently each machine is rebuilt. Where does DHCP response data fit into transport observability? SMF: if you support server platforms other than Solaris 10+, then you need a separate mechanism to store server configuration information for those platforms. In that case, you should use the same mechanism on Solaris as well. -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
