Perhaps even more accurate would be
"Set of Tools and Usages for NAT traversal".
- Philip
On 30-Nov-06, at 17:47 , Francois Audet wrote:
> Yes agreed.
>
> In fact, the worst names we come up with is when we try
to match an
> acronym.
> For example, "Behavior Engineering for Hindrance
Avoidance"...
>
>> -----Original Message-----
>> From: Philip Matthews [mailto:philip_matthews magma.ca]
>> Sent: Thursday, November 30, 2006 14:37
>> To: Spencer Dawkins; Audet, Francois (SC100:3055);
Pete Cordell
>> Cc: ietf-behavelist.sipfoundry.org
>> Subject: Re: [BEHAVE] STUN -> Session Traversal
Underneath NAT
>>
>> I also agree with Francois and Spencer.
>> Though I will suggest that
>> "Set of Tools Useful for NAT traversal
(STUN)" would be more
>> accurate.
>>
>> And there is a history of not always having the
acronym
>> correspond directly to the first letter of each
work.
>> Consider, for example, RSVP (Resource Reservation
Protocol).
>> I am sure folks can come up with other examples.
>>
>> - Philip
>>
>>
>> On 30-Nov-06, at 14:15 , Spencer Dawkins wrote:
>>
>>> Agree with Francois here. This would be a lot
less confusing than
>>> having two specs come out for NAT traversal at
the same time...
>>>
>>> Spencer
>>>
>>> ----- Original Message ----- From:
"Francois Audet"
>> <audetnortel.com>
>>> To: <behaveietf.org>
>>> Sent: Thursday, November 30, 2006 12:58 PM
>>> Subject: RE: [BEHAVE] STUN -> Session
Traversal Underneath NAT
>>>
>>>
>>> When you think about it, it's not even for NAT
traversal
>> anymore (that
>>> would be ICE).
>>>
>>> It's more a set of generic tools for NAT
support.
>>>
>>> STUN: Set of Tools Useful for NAT
>>> ^ ^ ^ ^
>>>
>>> Cheers.
>>>
>>>
>>> _______________________________________________
>>> Behave mailing list
>>> Behaveietf.org
>>> https:/
/www1.ietf.org/mailman/listinfo/behave
>>
>>
>
_______________________________________________
Behave mailing list
Behaveietf.org
https:/
/www1.ietf.org/mailman/listinfo/behave
|