RE: [Widex] Widex Servers...

Vlad.Stirbu@nokia.com Tue, 07 February 2006 15:54 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 1F6VAr-00040H-IJ; Tue, 07 Feb 2006 10:54:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6VAq-0003z3-7G for widex@megatron.ietf.org; Tue, 07 Feb 2006 10:54:36 -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 KAA05963 for <widex@ietf.org>; Tue, 7 Feb 2006 10:52:54 -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 1F6VNF-0004p9-4y for widex@ietf.org; Tue, 07 Feb 2006 11:07:26 -0500
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext02.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k17FsR2N003994; Tue, 7 Feb 2006 17:54:31 +0200
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 7 Feb 2006 17:53:35 +0200
Received: from trebe101.NOE.Nokia.com ([172.22.124.61]) by esebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 7 Feb 2006 17:53:34 +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 17:53:35 +0200
Message-ID: <1C1F3D15859526459B4DD0A7A9B2268B01A6E9D9@trebe101.NOE.Nokia.com>
In-Reply-To: <43E8B12F.1040208@gmail.com>
Thread-Topic: [Widex] Widex Servers...
Thread-Index: AcYr9LFaL+bNrXwGTq2kxN8I8lwUKQACdpKg
To: eprparadocs@gmail.com
X-OriginalArrivalTime: 07 Feb 2006 15:53:34.0759 (UTC) FILETIME=[A6D96370:01C62BFE]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
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

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