RE: <profile> contained within <greeting>

 
> > A simple question that I cannot find answer from RFC 3080: should a 
> > <greeting> message contain _all_ profiles the BEEP peer 
> supports, or 
> > should it contain only those profiles that it is willing to act as 
> > listener?  What's the intended use for those profile elements in a 
> > <greeting> message?
> 
> the greeting "advertises profiles that it supports". the specification
> does not define what "supports" means. some might say that was on
> purpose...

In my implementation, I advertise only those profiles that I am ready to
accept. And if I am a client peer, I expect that I can call up any
profiles that the server peer advertises. Everything else sounds
illogical to me. 

Just theoretical: a listener - in my point of view - may also
temporarily NOT advertise some profiles if it *temporarily* is unable to
process them (e.g. a needed ressources for one profile is offline while
the other profiles can be handled). So I think <greeting> is of highly
dynamic nature - and the listener should only avertise those profiles
that it actually *expects* to be able to accept (of course, this
assumption may turn out to be false at any time later so the listener
may still need to "ERR" on a requested profile (e.g. while a necessary
ressources goes just at this moment offline) - but I think this is as
always in IT (and life) - expect unexpected things to happen ;)

HTH
Rainer