Re: [Widex] Widex Servers...

Chaz Ginger <eprparadocs@gmail.com> Tue, 07 February 2006 17:17 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6WTI-00009A-4u; Tue, 07 Feb 2006 12:17:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6WTG-00007h-VJ for widex@megatron.ietf.org; Tue, 07 Feb 2006 12:17:43 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13130 for <widex@ietf.org>; Tue, 7 Feb 2006 12:15:52 -0500 (EST)
Received: from mail9.opentransfer.com ([69.6.255.180]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1F6WfV-0007wi-DJ for widex@ietf.org; Tue, 07 Feb 2006 12:30:23 -0500
Received: (qmail 23943 invoked by uid 399); 7 Feb 2006 17:15:19 -0000
Received: from unknown (HELO ?192.168.0.107?) (71.162.121.161) by mail.opentransfer.com with SMTP; 7 Feb 2006 17:15:19 -0000
Message-ID: <43E8D5A5.6020000@gmail.com>
Date: Tue, 07 Feb 2006 12:15:17 -0500
From: Chaz Ginger <eprparadocs@gmail.com>
User-Agent: Mail/News 1.5 (X11/20060206)
MIME-Version: 1.0
To: Vlad.Stirbu@nokia.com
Subject: Re: [Widex] Widex Servers...
References: <1C1F3D15859526459B4DD0A7A9B2268B01A6E9F6@trebe101.NOE.Nokia.com>
In-Reply-To: <1C1F3D15859526459B4DD0A7A9B2268B01A6E9F6@trebe101.NOE.Nokia.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 4b7d60495f1a7f2e853e8cbae7e6dbfc
Content-Transfer-Encoding: 7bit
Cc: widex@ietf.org
X-BeenThere: widex@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Working list for the WIDEX working group at IETF <widex.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/widex>, <mailto:widex-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/widex>
List-Post: <mailto:widex@ietf.org>
List-Help: <mailto:widex-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/widex>, <mailto:widex-request@ietf.org?subject=subscribe>
Sender: widex-bounces@ietf.org
Errors-To: widex-bounces@ietf.org

Vlad, it will do port forwarding or rewrite the entire dest. IP address
(depending on the NAT). The client may or may not have a NAT or proxy,
depending.

Chuck

Vlad.Stirbu@nokia.com wrote:
> But does the client/renderer communicate directly with the server or via
> a proxy/gateway (even if the client is not aware of the proxy)?
>
> Vlad
>
>   
>> -----Original Message-----
>> From: ext Chaz Ginger [mailto:eprparadocs@gmail.com] 
>> Sent: 07 February, 2006 18:03
>> To: Stirbu Vlad (Nokia-TP-MSW/Tampere)
>> Cc: widex@ietf.org
>> Subject: Re: [Widex] Widex Servers...
>>
>> Vlad,
>>
>> We are back at the beginning.  Having run a number of 
>> "public" sites I can say with some amount of certainty that 
>> they are behind NATs.  I am sure there are some webservers 
>> (well Widex servers in this case) that sit directly on the IP 
>> network, but they are the exception rather than the rule. 
>>
>> Chuck Wegrzyn
>>
>>
>> Vlad.Stirbu@nokia.com wrote:
>>     
>>> It seems that I misunderstood your previous example... I 
>>>       
>> thought that 
>>     
>>> you were talking about Widex servers in corporate networks. So, for 
>>> service providers like Google or Yahoo, the server front-end has a 
>>> globally routable, public IP address (and/or FQDN), similar 
>>>       
>> to section 
>>     
>>> 4.1.2.
>>>
>>> Vlad
>>>
>>>   
>>>       
>>>> -----Original Message-----
>>>> From: ext Chaz Ginger [mailto:eprparadocs@gmail.com]
>>>> Sent: 07 February, 2006 16:40
>>>> To: Stirbu Vlad (Nokia-TP-MSW/Tampere)
>>>> Cc: widex@ietf.org
>>>> Subject: Re: [Widex] Widex Servers...
>>>>
>>>> Vlad,
>>>>
>>>> Perhaps you can explain to me how someone like Google, MSN or Yahoo 
>>>> would offer Widex based services? Are you thinking they would use a 
>>>> VPN?
>>>>
>>>> Chuck
>>>>
>>>> Vlad.Stirbu@nokia.com wrote:
>>>>     
>>>>         
>>>>> Yes, but in most of those scenarios you are not accessing
>>>>>       
>>>>>           
>>>> the servers
>>>>     
>>>>         
>>>>> directly but through some kind of VPN, making the Widex
>>>>>       
>>>>>           
>>>> Renderer part
>>>>     
>>>>         
>>>>> of the same network as the Widex Server, case which is already 
>>>>> described in the document.
>>>>>
>>>>> Vlad
>>>>>
>>>>>   
>>>>>       
>>>>>           
>>>>>> -----Original Message-----
>>>>>> From: ext Chaz Ginger [mailto:eprparadocs@gmail.com]
>>>>>> Sent: 07 February, 2006 16:03
>>>>>> To: Stirbu Vlad (Nokia-TP-MSW/Tampere)
>>>>>> Cc: widex@ietf.org
>>>>>> Subject: Re: [Widex] Widex Servers...
>>>>>>
>>>>>> Vlad,
>>>>>>
>>>>>> Why wouldn't you include the case of the Widex server behind a 
>>>>>> firewall? I would expect that to be the most common case.
>>>>>> Most companies that I know and work for all use some sort of 
>>>>>> firewall. Am I missing something?
>>>>>>
>>>>>> Chuck
>>>>>>
>>>>>> Vlad.Stirbu@nokia.com wrote:
>>>>>>     
>>>>>>         
>>>>>>             
>>>>>>>> -----Original Message-----
>>>>>>>> From: widex-bounces@ietf.org [mailto:widex-bounces@ietf.org] On 
>>>>>>>> Behalf Of ext Chaz Ginger
>>>>>>>> Sent: 06 February, 2006 17:12
>>>>>>>> To: Dean Willis
>>>>>>>> Cc: widex@ietf.org
>>>>>>>> Subject: [Widex] Widex Servers...
>>>>>>>>
>>>>>>>> >From looking at the requirement docs I noticed that there
>>>>>>>> isn't a model
>>>>>>>> for a Widex Server behind a NAT.  Why?
>>>>>>>>
>>>>>>>>     
>>>>>>>>         
>>>>>>>>             
>>>>>>>>                 
>>>>>>> We haven't considered the case when the Widex Server to be
>>>>>>>           
>>>>>>>               
>>>> behind a
>>>>     
>>>>         
>>>>>>> NAT device to be very common. For this reason it was not
>>>>>>>           
>>>>>>>               
>>>> included in
>>>>     
>>>>         
>>>>>>> the scope of this document.
>>>>>>>
>>>>>>>   
>>>>>>>       
>>>>>>>           
>>>>>>>               
>>>>>>>> Also why the model where both the server and the renderer
>>>>>>>>         
>>>>>>>>             
>>>>>>>>                 
>>>>>> are behind
>>>>>>     
>>>>>>         
>>>>>>             
>>>>>>>> the NAT? Is this specifically to address the notion of 
>>>>>>>>                 
>> localized 
>>     
>>>>>>>> discovery?
>>>>>>>>
>>>>>>>>     
>>>>>>>>         
>>>>>>>>             
>>>>>>>>                 
>>>>>>> Yes, this scenario is specifically related to localized 
>>>>>>>               
>> discovery.
>>     
>>>>>>> Vlad
>>>>>>>
>>>>>>>
>>>>>>>   
>>>>>>>       
>>>>>>>           
>>>>>>>               
>>>>>>     
>>>>>>         
>>>>>>             
>>>>>   
>>>>>       
>>>>>           
>>>>     
>>>>         
>>>   
>>>       
>>     
>
>
>   


_______________________________________________
Widex mailing list
Widex@ietf.org
https://www1.ietf.org/mailman/listinfo/widex