remove channel name?

Hi, As I'm nearing the finale of channel implementation, I have nagging doubts about the brilliance of having both a channel name and a channel server. The potential security loopholes are not pleasing, and it introduces some necessary complexity in order to validate these. Would anyone have any reservations about removing the name field from channel.xml, and simply using server as the name? This is the recommended setting anyways, so that channel pear.php.net refers to pear.php.net. The original intent was to allow a channel to change the server name, but I'm now thinking it would be better to simply assume that if a channel needs to change its server name, then there is enough upheaval that its users can handle a bit more trouble with the new channel's packages conflicting with the old channel's packages. Also, these packages can always be installed by hand if a channel goes defunct, without requiring a channel name change in package.xml. This would guarantee, for instance, that a channel can be auto-discovered, by recommending that channel.xml be in the root, so that pear.php.net/channel.xml contains the latest channel.xml. The HTTP LastModified header can be used to determine whether a refresh is needed on channel-update, removing another xml-rpc call (always a good thing, IMO). Greg