RE: <profile> contained within <greeting>

> In other words, it's no guarantee that a remote peer does not 
> support a 
> given profile if it doesn't appear in the greeting, 

mmmhhh... is this really in the spirit of BEEP? I doubt... My
implementation does NOT request profiles which are NOT advertised and I
think it is not a good idea to do so.

> and it's also no 
> guarantee that a remote peer does support a given profile if 
> it *does* 
> appear in the greeting.  

This sounds reasonable - the profile may also simply have gone offline
for some tech reason.

> The only way you know if the peer supports a 
> profile at the time you want to start a channel for it is if the peer 
> responds to a <start> message with a <profile> response.

So why have the greeting at all? Honestly, if would I agree to your
points, I would conclude that the greeting is a comment. So why shuffle
that comment along the wire if there is no need for it? At least it
should become an optional argument.

I am also sceptic about this as a "security measure". Agree, it would
make probing a little more time intense, but I could request the
profiles anyhow. So I don't see this adds much. Wouldn't it be more
appropriate to use the tuning profiles and allow only trusted
connections in this case ;)

Rainer