RE: [Widex] Widex Servers...

Vlad.Stirbu@nokia.com Wed, 08 February 2006 09:34 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 1F6lit-0005En-R0; Wed, 08 Feb 2006 04:34:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6lis-0005DN-Lt for widex@megatron.ietf.org; Wed, 08 Feb 2006 04:34:50 -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 EAA03887 for <widex@ietf.org>; Wed, 8 Feb 2006 04:33:08 -0500 (EST)
From: Vlad.Stirbu@nokia.com
Received: from mgw-ext02.nokia.com ([131.228.20.94]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6lvR-0004h3-L7 for widex@ietf.org; Wed, 08 Feb 2006 04:47:50 -0500
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-ext02.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k189HLYN022477; Wed, 8 Feb 2006 11:17:24 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 8 Feb 2006 11:17:22 +0200
Received: from trebe101.NOE.Nokia.com ([172.22.124.61]) by esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 8 Feb 2006 11:17:23 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7233.31
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Widex] Widex Servers...
Date: Wed, 08 Feb 2006 11:17:20 +0200
Message-ID: <1C1F3D15859526459B4DD0A7A9B2268B01AA84A4@trebe101.NOE.Nokia.com>
In-Reply-To: <43E8D5A5.6020000@gmail.com>
Thread-Topic: [Widex] Widex Servers...
Thread-Index: AcYsCns5YJIp4iyRR4aQiYHkmCrDSwAf0WwQ
To: eprparadocs@gmail.com
X-OriginalArrivalTime: 08 Feb 2006 09:17:23.0286 (UTC) FILETIME=[785C3760:01C62C90]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: a3f7094ccc62748c06b21fcf44c073ee
Content-Transfer-Encoding: quoted-printable
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

Chuck,

When we wrote the NAT considerations the main criteria was to indicate
that NATs can have some effects on one or more Widex components (see
Widex framework); we didn't meant this draft to include all scenarios
where NAT boxes can be envolved or deployed. It would be useful to get
more information, why he would like to see such scenario addressed.

So, in order to better understand the relation beteen the NAT device and
the Widex in your case I'd like to ask you these questions:

1. Which entity is creating or managing these port mapping/forwarding?
2. What is its relationship with the Widex components, e.g. is the
management done by a Widex component? If yes, which?
3. Is this a specific Widex problem or is a generic problem?
4. Is the work adressed in a more generic way in some other activities,
e.g. Rserpool WG
http://www.ietf.org/html.charters/rserpool-charter.html?

Thanks,
Vlad

>-----Original Message-----
>From: ext Chaz Ginger [mailto:eprparadocs@gmail.com] 
>Sent: 07 February, 2006 19:15
>To: Stirbu Vlad (Nokia-TP-MSW/Tampere)
>Cc: widex@ietf.org
>Subject: Re: [Widex] Widex Servers...
>
>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