[VoIP] Rules, Regulations, Etc

[John Novack]

Greg Blakely wrote:
> Anyhow, that's my opinion on September 2, 2007, with a bit of Percocet
> circulating throughout the system.
>
> Greg
>   
When I had a prolonged healing time for my broken leg many moons ago, 
the ( legal ) drug of choice then was Percodan, probably a predecessor.
Certainly took off the rough edges.
Anyone wanting to increase their tolerance for pain, break a leg!

Back on topic, Dennis Hock and I had a very short discussion at the 
show, and we thought that perhaps something similar to what the UK boys 
have set up as a policy might work.
On the trip back, John Jones and I discussed the possibility of a longer 
time period, with some token payment after that period to support the 
continued existence of the ENUM reference point might also prod some 
activity.
Or reserved codes marked as unused for XX time?
Even a token payment some day might become necessary from all the 
members to keep things alive.
Currently there is certainly no shortage of office codes, but a few 
sitting on desirable codes that someone else might be ready to use, but 
discouraged from doing so because they are marked as reserved may have 
an effect on growth.
Perhaps even  a short paragraph on the reservation list to contact  ??? 
if a reserved but unused code is desired by someone else?
I can see several right now that I feel sure will NEVER be used in my 
lifetime, but marked as reserved.
General thoughts on what currently isn't much of a problem.
Perhaps address it before it becomes one?

Hope all in the US are having a calm holiday.
I need to fire up the mower soon myself!

John Novack

> 	
>  
>
>   
>> -----Original Message-----
>> From: voip-bounces at lists.ckts.info 
>> [mailto:voip-bounces at lists.ckts.info] On Behalf Of Lee Spenadel
>> Sent: Sunday, September 02, 2007 9:4	1 AM
>> To: 'Voice Over IP Tandem for Analog Switches'
>> Subject: Re: [VoIP] Rules, Regulations, Etc
>>
>> Greg,
>>
>>  
>>
>> I agree with you regarding being involved with such a great 
>> hobby.  Most of us are fair, reasonable people that are 
>> genuinely interested in helping others get involved in the 
>> hobby, build the knowledgebase and enhance services for the 
>> group's benefit.  However, there are those who take advantage 
>> of the system and others good nature.  There will be those 
>> who tie up resources (such as office codes) with no intention 
>> of implementing a switch.
>>
>>  
>>
>> Unfortunately said people can't think outside of their own 
>> bubble, so (in my
>> opinion) having the automated MW check is just one means to 
>> keep turf wars, flaming and other poor behavior to a minimum, 
>> especially as the hobby gains more interest.  It keeps the 
>> tranquility by automatically weeding out potential problems.  
>> But this is only one example of managing resources such as 
>> office codes.  There may be other resources that need to be 
>> managed as well.
>>
>>  
>>
>> As the hobby continues to grow and resources become scarce, 
>> it will be more difficult to manage these resources.  By 
>> thinking ahead now and managing the "system" we ensure 
>> orderly growth and a fair implementation across the board.
>>
>>  
>>
>> Lee
>>
>>  
>>
>>  
>>
>>  
>>
>>  
>>
>>  
>>
>> <snip>
>>
>>  
>>
>>  
>>
>> It's great that we are thinking ahead, heading off situations where
>>
>> feelings could be hurt, and angry words exchanged.  
>>
>>  
>>
>> It probably will happen eventually, but I am confident that we will be
>>
>> able to sort things out as they happen.
>>
>>  
>>
>> So, I favor the organized anarchy that seems to be the status quo.
>>
>>  
>>
>>  
>>
>>  
>>
>>  
>>
>>  
>>
>>  
>>
>>  
>>
>> _______________________________________________
>> VoIP mailing list
>> VoIP at lists.ckts.info
>> http://lists.ckts.info/mailman/listinfo/voip
>> Project Web Page: http://www.ckts.info/
>>
>>
>>     
> _______________________________________________
> VoIP mailing list
> VoIP at lists.ckts.info
> http://lists.ckts.info/mailman/listinfo/voip
> Project Web Page: http://www.ckts.info/
>
>   

-- 
Dog is my co-pilot