RE: [Widex] Widex Servers...

Vlad.Stirbu@nokia.com Tue, 07 February 2006 16:40 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 1F6VtY-0005al-RQ; Tue, 07 Feb 2006 11:40:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6VtV-0005Vj-Nc for widex@megatron.ietf.org; Tue, 07 Feb 2006 11:40:45 -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 LAA09077 for <widex@ietf.org>; Tue, 7 Feb 2006 11:39:03 -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 1F6W5v-0006HC-48 for widex@ietf.org; Tue, 07 Feb 2006 11:53:36 -0500
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext02.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k17GefJp014652; Tue, 7 Feb 2006 18:40:42 +0200
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 7 Feb 2006 18:40:31 +0200
Received: from trebe101.NOE.Nokia.com ([172.22.124.61]) by esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 7 Feb 2006 18:40:32 +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: Tue, 07 Feb 2006 18:40:30 +0200
Message-ID: <1C1F3D15859526459B4DD0A7A9B2268B01A6E9F6@trebe101.NOE.Nokia.com>
In-Reply-To: <43E8C4C4.1020401@gmail.com>
Thread-Topic: [Widex] Widex Servers...
Thread-Index: AcYsAFprwPndnLOBRgSMCVsKYw109QAAke6Q
To: eprparadocs@gmail.com
X-OriginalArrivalTime: 07 Feb 2006 16:40:32.0082 (UTC) FILETIME=[361AC320:01C62C05]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 2ed806e2f53ff1a061ad4f97e00345ac
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

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