Re: [Widex] Widex Servers...

Chaz Ginger <eprparadocs@gmail.com> Tue, 07 February 2006 14:05 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 1F6TTE-0006NG-JZ; Tue, 07 Feb 2006 09:05:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6TTC-0006Co-Bq for widex@megatron.ietf.org; Tue, 07 Feb 2006 09:05:26 -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 JAA27893 for <widex@ietf.org>; Tue, 7 Feb 2006 09:03:37 -0500 (EST)
Received: from mail9.opentransfer.com ([69.6.255.180]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1F6TfT-00012q-DE for widex@ietf.org; Tue, 07 Feb 2006 09:18:08 -0500
Received: (qmail 9627 invoked by uid 399); 7 Feb 2006 14:03:21 -0000
Received: from unknown (HELO ?192.168.0.107?) (71.162.121.161) by mail.opentransfer.com with SMTP; 7 Feb 2006 14:03:21 -0000
Message-ID: <43E8A8A5.9040601@gmail.com>
Date: Tue, 07 Feb 2006 09:03: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: <1C1F3D15859526459B4DD0A7A9B2268B01A6E7EA@trebe101.NOE.Nokia.com>
In-Reply-To: <1C1F3D15859526459B4DD0A7A9B2268B01A6E7EA@trebe101.NOE.Nokia.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
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,

 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