From widex-bounces@ietf.org Thu Sep 07 12:08:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLMQF-0004t5-Ne; Thu, 07 Sep 2006 12:08:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GLMNZ-0004KP-SA
	for widex@ietf.org; Thu, 07 Sep 2006 12:05:25 -0400
Received: from mgw-ext14.nokia.com ([131.228.20.173])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GLMAx-0001c0-V5
	for widex@ietf.org; Thu, 07 Sep 2006 11:52:25 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext14.nokia.com (Switch-3.1.10/Switch-3.1.7) with ESMTP id
	k87FqJGV014448; Thu, 7 Sep 2006 18:52:22 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 7 Sep 2006 18:52:22 +0300
Received: from trebe101.NOE.Nokia.com ([172.22.124.61]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 7 Sep 2006 18:52:22 +0300
x-mimeole: Produced By Microsoft Exchange V6.5
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] Review of Requirements document
Date: Thu, 7 Sep 2006 18:48:56 +0300
Message-ID: <1C1F3D15859526459B4DD0A7A9B2268B027DEA61@trebe101.NOE.Nokia.com>
In-Reply-To: <13AE21B8-D606-4C11-BE46-74DF5067E4E1@osafoundation.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Widex] Review of Requirements document
Thread-Index: Acas+/NCuAThgqI9Sp2fzFi/WoGB6AkwzVfw
From: <Vlad.Stirbu@nokia.com>
To: <lisa@osafoundation.org>, <widex@ietf.org>
X-OriginalArrivalTime: 07 Sep 2006 15:52:22.0051 (UTC)
	FILETIME=[9B160730:01C6D295]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
Cc: 
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>
Errors-To: widex-bounces@ietf.org

Hi Lisa,

>-----Original Message-----
>From: ext Lisa Dusseault [mailto:lisa@osafoundation.org]=20
>Sent: 21 July, 2006 22:29
>To: widex@ietf.org
>Subject: [Widex] Review of Requirements document
>
>
>This review comes from me as an individual.  These are=20
>questions and suggestions for improving the document (not=20
>requirements from your advising AD), and it may well be that I=20
>don't understand the problem space well enough yet.
>
>4.  Scenarios
>
>I am not sure why the NAT traversal and IPv4/IPv6 stuff is in=20
>this document in so much detail.  Does it require this much=20
>explanation and diagrams?  What requirements follow from these=20
>scenarios?

The relation might not be so obvious but, as Widex will define both a
framework and a message exchange used for synchronization (e.g. WOs),
implementers needs to be aware of the network environment challenges
when they will choose the service discovery and session setup mechanism
and the transport protocol that is most appropriate for their particular
target environment. We might have gone too deep into details in this
document and a better place for those should have been the framework
document but they are quite important to understand the problem.

>
>To a reader like me, a scenario that described an example use=20
>case justifying the "multiple modes of interaction" would be useful.

Would it be enough if we point the reader instead to the W3C's
Multimodal Architecture which is one possible customer of the Widex
framework?

>
>I think your scenarios are designed for a reader that=20
>understands the problem that's being solved but may not=20
>understand the networking challenges, whereas I'm a reader who=20
>understands the networking challenges more than I understand=20
>the problem being solved :)
>
>5.  Requirements
>
>5.1:
>"   o  The framework MUST be modular, e.g. multiple session setup
>       mechanisms may be used."
>
>Flexibility is good; interoperability is even better.  How=20
>about adding something like: "There must be ONE=20
>mandatory-to-implement session setup mechanism" (you might=20
>also add desired characteristics for the mandatory mech.)

The Widex framework can be used in different environments and those can
have characteristics that differentiate them quite a lot and these
characteristics were taken into account by the developers of the service
discovery and session setup protocols. For example, in an unmanaged
network like those typically found in home networks, an implementer may
choose between Rendezvous/Bonjour and UPnP. In other environments, where
SIP infrastructure is available, implementers can use it. Other
alternatives include SLP or SRV records or it might be possible that in
some close environments there is no need for service discovery and
session setup at all if you have means to manually input the URL of the
server in the client.

It would be great if a mandatory mechanism will be defined but it seems
that we don't have any mechanisms that is universally applicable. For
this reason, in order to help interoperability and to provide a somehow
unified experience regardless of what is the actual service discovery
and session setup mechanism, the framework has some requirements on what
the mechanism must and should negotiate (they are listed in the
framework draft).

>
>5.2:
>"   o  The service discovery mechanism MUST be able to discover both
>       Widex Renderers and Widex Servers."
>
>At a minimum, there are Security Considerations implications=20
>from this, particularly w.r.t. privacy of renderers.  I would=20
>like to understand better the reasoning behind the requirement=20
>for discoverability of Widex renderers.

A TV set or a smart screen can play very well the role of Widex renderer
and it might be useful if you could use this as a secondary display. Of
course, privacy of the renderers is very important and implementers
should balance what capabilities should be revealed and which should be
kept private. For example, somebody can choose not to reveal anything
about the renderer besides that it is a Widex renderer but that will
have quite negative impact as the server will not be able to provide the
UI that best suits the renderer capabilities, instead providing the
default UI.

Privacy concerns are valid also for the Widex servers which might host
sensitive applications and you want to allow only specific
users/renderers to interact with. Fortunately, these issues were taken
into account by the designers of service discovery and session setup
mechanisms.=20

>
>5.3:
>"   o  The WOs MUST contain only information having remote scope."
>
>I just don't understand this requirement.

The meaning of WOs was defined in section 3.3. and specifically refers
to the WOs.Event. Do you think that we need to be more specific about
which WOs this requirement is about? We need to think that while
developing the framework document we detected that we need more WOs than
initially envisioned in this document (e.g. WO.Selector) and the
requirement should cover also those ones.

>
>5.3:
>"   o  The WOs MAY support multiple modes of interaction, and it is the
>       responsibility of the application to synchronise modalities and
>       not that of the Widex protocol."
>
>I believe this implies that multiple modes would indicate=20
>multiple Widex protocol sessions. Is that correct?  It might=20
>be good to state the implication.

Yes, this implication in correct.

>
>Thanks,
>Lisa
>



Thanks,
Vlad

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



From widex-bounces@ietf.org Mon Sep 18 15:13:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GPOYP-0004oC-9B; Mon, 18 Sep 2006 15:13:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GPOYN-0004nn-OZ
	for widex@ietf.org; Mon, 18 Sep 2006 15:13:15 -0400
Received: from nylon.softarmor.com ([66.135.38.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GPOYL-0002mY-8n
	for widex@ietf.org; Mon, 18 Sep 2006 15:13:15 -0400
Received: from [64.101.149.162] ([64.101.149.162]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.1/8.13.1) with ESMTP id k8IIFwDE023877
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO);
	Mon, 18 Sep 2006 13:16:00 -0500
In-Reply-To: <1C1F3D15859526459B4DD0A7A9B2268B027DEA61@trebe101.NOE.Nokia.com>
References: <1C1F3D15859526459B4DD0A7A9B2268B027DEA61@trebe101.NOE.Nokia.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <77D30015-71EA-4221-BA18-B8ECB7D1A1A3@softarmor.com>
Content-Transfer-Encoding: 7bit
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Widex] Review of Requirements document
Date: Mon, 18 Sep 2006 14:13:09 -0500
To: widex@ietf.org
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ded6070f7eed56e10c4f4d0d5043d9c7
Cc: "Vlad.Stirbu@nokia.com> <Vlad.Stirbu@nokia.com" <Vlad.Stirbu@nokia.com>
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>
Errors-To: widex-bounces@ietf.org


It seems to me that the commentary from Lisa indicates a few things  
that should be touched up before requesting Apps-area expert review  
on the document, which I would like to do either before or in  
conjunction with working-group last call.

With a document of this sort and the small community that we have  
working on it, I think it is important to get some external review so  
that we can discover whether the level of exposition is adequate for   
a new reader.

What do you folks think of revving this document fairly quickly to  
accommodate the suggestions below, then starting area and working  
group final reviews?

--
Dean Willis, as chair


On Sep 7, 2006, at 10:48 AM, <Vlad.Stirbu@nokia.com>  
<Vlad.Stirbu@nokia.com> wrote:

> Hi Lisa,
>
>> -----Original Message-----
>> From: ext Lisa Dusseault [mailto:lisa@osafoundation.org]
>> Sent: 21 July, 2006 22:29
>> To: widex@ietf.org
>> Subject: [Widex] Review of Requirements document
>>
>>
>> This review comes from me as an individual.  These are
>> questions and suggestions for improving the document (not
>> requirements from your advising AD), and it may well be that I
>> don't understand the problem space well enough yet.
>>
>> 4.  Scenarios
>>
>> I am not sure why the NAT traversal and IPv4/IPv6 stuff is in
>> this document in so much detail.  Does it require this much
>> explanation and diagrams?  What requirements follow from these
>> scenarios?
>
> The relation might not be so obvious but, as Widex will define both a
> framework and a message exchange used for synchronization (e.g. WOs),
> implementers needs to be aware of the network environment challenges
> when they will choose the service discovery and session setup  
> mechanism
> and the transport protocol that is most appropriate for their  
> particular
> target environment. We might have gone too deep into details in this
> document and a better place for those should have been the framework
> document but they are quite important to understand the problem.
>
>>
>> To a reader like me, a scenario that described an example use
>> case justifying the "multiple modes of interaction" would be useful.
>
> Would it be enough if we point the reader instead to the W3C's
> Multimodal Architecture which is one possible customer of the Widex
> framework?
>
>>
>> I think your scenarios are designed for a reader that
>> understands the problem that's being solved but may not
>> understand the networking challenges, whereas I'm a reader who
>> understands the networking challenges more than I understand
>> the problem being solved :)
>>
>> 5.  Requirements
>>
>> 5.1:
>> "   o  The framework MUST be modular, e.g. multiple session setup
>>       mechanisms may be used."
>>
>> Flexibility is good; interoperability is even better.  How
>> about adding something like: "There must be ONE
>> mandatory-to-implement session setup mechanism" (you might
>> also add desired characteristics for the mandatory mech.)
>
> The Widex framework can be used in different environments and those  
> can
> have characteristics that differentiate them quite a lot and these
> characteristics were taken into account by the developers of the  
> service
> discovery and session setup protocols. For example, in an unmanaged
> network like those typically found in home networks, an implementer  
> may
> choose between Rendezvous/Bonjour and UPnP. In other environments,  
> where
> SIP infrastructure is available, implementers can use it. Other
> alternatives include SLP or SRV records or it might be possible  
> that in
> some close environments there is no need for service discovery and
> session setup at all if you have means to manually input the URL of  
> the
> server in the client.
>
> It would be great if a mandatory mechanism will be defined but it  
> seems
> that we don't have any mechanisms that is universally applicable. For
> this reason, in order to help interoperability and to provide a  
> somehow
> unified experience regardless of what is the actual service discovery
> and session setup mechanism, the framework has some requirements on  
> what
> the mechanism must and should negotiate (they are listed in the
> framework draft).
>
>>
>> 5.2:
>> "   o  The service discovery mechanism MUST be able to discover both
>>       Widex Renderers and Widex Servers."
>>
>> At a minimum, there are Security Considerations implications
>> from this, particularly w.r.t. privacy of renderers.  I would
>> like to understand better the reasoning behind the requirement
>> for discoverability of Widex renderers.
>
> A TV set or a smart screen can play very well the role of Widex  
> renderer
> and it might be useful if you could use this as a secondary  
> display. Of
> course, privacy of the renderers is very important and implementers
> should balance what capabilities should be revealed and which  
> should be
> kept private. For example, somebody can choose not to reveal anything
> about the renderer besides that it is a Widex renderer but that will
> have quite negative impact as the server will not be able to  
> provide the
> UI that best suits the renderer capabilities, instead providing the
> default UI.
>
> Privacy concerns are valid also for the Widex servers which might host
> sensitive applications and you want to allow only specific
> users/renderers to interact with. Fortunately, these issues were taken
> into account by the designers of service discovery and session setup
> mechanisms.
>
>>
>> 5.3:
>> "   o  The WOs MUST contain only information having remote scope."
>>
>> I just don't understand this requirement.
>
> The meaning of WOs was defined in section 3.3. and specifically refers
> to the WOs.Event. Do you think that we need to be more specific about
> which WOs this requirement is about? We need to think that while
> developing the framework document we detected that we need more WOs  
> than
> initially envisioned in this document (e.g. WO.Selector) and the
> requirement should cover also those ones.
>
>>
>> 5.3:
>> "   o  The WOs MAY support multiple modes of interaction, and it  
>> is the
>>       responsibility of the application to synchronise modalities and
>>       not that of the Widex protocol."
>>
>> I believe this implies that multiple modes would indicate
>> multiple Widex protocol sessions. Is that correct?  It might
>> be good to state the implication.
>
> Yes, this implication in correct.
>
>>
>> Thanks,
>> Lisa
>>
>
>
>
> Thanks,
> Vlad
>
> _______________________________________________
> Widex mailing list
> Widex@ietf.org
> https://www1.ietf.org/mailman/listinfo/widex
>


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



From widex-bounces@ietf.org Tue Sep 19 19:17:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GPoq3-0007YT-7K; Tue, 19 Sep 2006 19:17:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GPoq2-0007YN-Cb
	for widex@ietf.org; Tue, 19 Sep 2006 19:17:14 -0400
Received: from laweleka.osafoundation.org ([204.152.186.98])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GPopz-0005vo-P0
	for widex@ietf.org; Tue, 19 Sep 2006 19:17:14 -0400
Received: from localhost (localhost [127.0.0.1])
	by laweleka.osafoundation.org (Postfix) with ESMTP id 3DC01142282;
	Tue, 19 Sep 2006 16:17:07 -0700 (PDT)
Received: from laweleka.osafoundation.org ([127.0.0.1])
	by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 25136-04; Tue, 19 Sep 2006 16:17:06 -0700 (PDT)
Received: from [192.168.2.2] (c-69-181-78-47.hsd1.ca.comcast.net
	[69.181.78.47]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by laweleka.osafoundation.org (Postfix) with ESMTP id 51CE9142280;
	Tue, 19 Sep 2006 16:17:06 -0700 (PDT)
In-Reply-To: <1C1F3D15859526459B4DD0A7A9B2268B027DEA61@trebe101.NOE.Nokia.com>
References: <1C1F3D15859526459B4DD0A7A9B2268B027DEA61@trebe101.NOE.Nokia.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <2509F7FF-CFE3-4283-B415-B5F1FD84097A@osafoundation.org>
Content-Transfer-Encoding: 7bit
From: Lisa Dusseault <lisa@osafoundation.org>
Subject: Re: [Widex] Review of Requirements document
Date: Tue, 19 Sep 2006 16:17:03 -0700
To: <Vlad.Stirbu@nokia.com> <Vlad.Stirbu@nokia.com>
X-Mailer: Apple Mail (2.752.2)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: df9edf1223802dd4cf213867a3af6121
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>
Errors-To: widex-bounces@ietf.org


Discussion continued below inline...

On Sep 7, 2006, at 8:48 AM, <Vlad.Stirbu@nokia.com>  
<Vlad.Stirbu@nokia.com> wrote:

> Hi Lisa,
>
>> -----Original Message-----
>> From: ext Lisa Dusseault [mailto:lisa@osafoundation.org]
>> Sent: 21 July, 2006 22:29
>> To: widex@ietf.org
>> Subject: [Widex] Review of Requirements document
>>
>>
>> This review comes from me as an individual.  These are
>> questions and suggestions for improving the document (not
>> requirements from your advising AD), and it may well be that I
>> don't understand the problem space well enough yet.
>>
>> 4.  Scenarios
>>
>> I am not sure why the NAT traversal and IPv4/IPv6 stuff is in
>> this document in so much detail.  Does it require this much
>> explanation and diagrams?  What requirements follow from these
>> scenarios?
>
> The relation might not be so obvious but, as Widex will define both a
> framework and a message exchange used for synchronization (e.g. WOs),
> implementers needs to be aware of the network environment challenges
> when they will choose the service discovery and session setup  
> mechanism
> and the transport protocol that is most appropriate for their  
> particular
> target environment. We might have gone too deep into details in this
> document and a better place for those should have been the framework
> document but they are quite important to understand the problem.

I'm still concerned about the risk of describing NATs, or suggested  
solutions to the problems NATs post, in a way that's incompatible  
with the many other documents the IETF has produced on the topic.  It  
feels odd to type that; I'm generally in favour of explanatory text  
to help implementors!  I guess I'm not suggesting simply taking out  
the text, unless you really can refer to some BEHAVE or transport  
area document.  At some point it would need to be tied, as you  
suggest, to helping implementors choose the appropriate WIDEX options  
for their environment.  I would support moving this to the framework  
document.

>
>>
>> To a reader like me, a scenario that described an example use
>> case justifying the "multiple modes of interaction" would be useful.
>
> Would it be enough if we point the reader instead to the W3C's
> Multimodal Architecture which is one possible customer of the Widex
> framework?

Probably yes

>
>>
>> I think your scenarios are designed for a reader that
>> understands the problem that's being solved but may not
>> understand the networking challenges, whereas I'm a reader who
>> understands the networking challenges more than I understand
>> the problem being solved :)
>>
>> 5.  Requirements
>>
>> 5.1:
>> "   o  The framework MUST be modular, e.g. multiple session setup
>>       mechanisms may be used."
>>
>> Flexibility is good; interoperability is even better.  How
>> about adding something like: "There must be ONE
>> mandatory-to-implement session setup mechanism" (you might
>> also add desired characteristics for the mandatory mech.)
>
> The Widex framework can be used in different environments and those  
> can
> have characteristics that differentiate them quite a lot and these
> characteristics were taken into account by the developers of the  
> service
> discovery and session setup protocols. For example, in an unmanaged
> network like those typically found in home networks, an implementer  
> may
> choose between Rendezvous/Bonjour and UPnP. In other environments,  
> where
> SIP infrastructure is available, implementers can use it. Other
> alternatives include SLP or SRV records or it might be possible  
> that in
> some close environments there is no need for service discovery and
> session setup at all if you have means to manually input the URL of  
> the
> server in the client.
>
> It would be great if a mandatory mechanism will be defined but it  
> seems
> that we don't have any mechanisms that is universally applicable. For
> this reason, in order to help interoperability and to provide a  
> somehow
> unified experience regardless of what is the actual service discovery
> and session setup mechanism, the framework has some requirements on  
> what
> the mechanism must and should negotiate (they are listed in the
> framework draft).

I was a little confused here by what a "session setup mechanism" is.   
Here's what I was thinking: TCP is expected to work all over the  
Internet, and there's one way to create a session in TCP.  If you  
want a fancier kind of setting, BEEP or XMPP could work anywhere TCP  
works, and each of those have one way of creating a session.  So I  
was thinking WIDEX would require support for one of those.

But if you're indeed talking about service discovery, then I agree  
there's not one standardized mechanism that's guaranteed to work  
everywhere and be useful for each case.  Not every WIDEX server will  
be able to create SRV records, for example.  Still, if service  
discovery is very important for WIDEX (it isn't in email and  
calendaring where users type in their server addresses) then there'll  
need to be a lot of thought about whether the existing mechanisms are  
sufficient or whether WIDEX needs to "raise the bar" in this area by  
demanding (or specifying ) more.

>
>>
>> 5.2:
>> "   o  The service discovery mechanism MUST be able to discover both
>>       Widex Renderers and Widex Servers."
>>
>> At a minimum, there are Security Considerations implications
>> from this, particularly w.r.t. privacy of renderers.  I would
>> like to understand better the reasoning behind the requirement
>> for discoverability of Widex renderers.
>
> A TV set or a smart screen can play very well the role of Widex  
> renderer
> and it might be useful if you could use this as a secondary  
> display. Of
> course, privacy of the renderers is very important and implementers
> should balance what capabilities should be revealed and which  
> should be
> kept private. For example, somebody can choose not to reveal anything
> about the renderer besides that it is a Widex renderer but that will
> have quite negative impact as the server will not be able to  
> provide the
> UI that best suits the renderer capabilities, instead providing the
> default UI.

You might want to explain the use case that illustrates or motivates  
the requirement, in the requirements doc.  (I don't think exhaustive  
use-casing is very successful in IETF but in this case I just didn't  
get it without an example)

>
> Privacy concerns are valid also for the Widex servers which might host
> sensitive applications and you want to allow only specific
> users/renderers to interact with. Fortunately, these issues were taken
> into account by the designers of service discovery and session setup
> mechanisms.
>
>>
>> 5.3:
>> "   o  The WOs MUST contain only information having remote scope."
>>
>> I just don't understand this requirement.
>
> The meaning of WOs was defined in section 3.3. and specifically refers
> to the WOs.Event. Do you think that we need to be more specific about
> which WOs this requirement is about? We need to think that while
> developing the framework document we detected that we need more WOs  
> than
> initially envisioned in this document (e.g. WO.Selector) and the
> requirement should cover also those ones.

I read "WOs" as short for "Widex Objects".  I don't agree it implies  
Event as is.  There were other problem words -- "having scope" and  
which end "remote" is.

Would this be correct?  "  o  The Widex Objects MUST contain only  
information meaningful in context of the renderer."

>
>>
>> 5.3:
>> "   o  The WOs MAY support multiple modes of interaction, and it  
>> is the
>>       responsibility of the application to synchronise modalities and
>>       not that of the Widex protocol."
>>
>> I believe this implies that multiple modes would indicate
>> multiple Widex protocol sessions. Is that correct?  It might
>> be good to state the implication.
>
> Yes, this implication in correct.
>
>>
>> Thanks,
>> Lisa
>>
>
>
>
> Thanks,
> Vlad


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



From widex-bounces@ietf.org Thu Sep 28 16:20:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GT2Mm-0000u9-32; Thu, 28 Sep 2006 16:20:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GT2Mk-0000ts-Rm
	for widex@ietf.org; Thu, 28 Sep 2006 16:20:18 -0400
Received: from mgw-ext14.nokia.com ([131.228.20.173])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GT2Mh-0001Wr-1z
	for widex@ietf.org; Thu, 28 Sep 2006 16:20:18 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext14.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id
	k8SKKEfI004976 for <widex@ietf.org>; Thu, 28 Sep 2006 23:20:14 +0300
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 28 Sep 2006 23:20:14 +0300
Received: from trebe101.NOE.Nokia.com ([172.22.124.61]) by
	esebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 28 Sep 2006 23:20:14 +0300
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 28 Sep 2006 23:20:13 +0300
Message-ID: <1C1F3D15859526459B4DD0A7A9B2268B0293766B@trebe101.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Updated Widex requirements draft (-03)
Thread-Index: AcbjO4Dv0VKmdhwSTFS+SgF7IUMqqw==
From: <Vlad.Stirbu@nokia.com>
To: <widex@ietf.org>
X-OriginalArrivalTime: 28 Sep 2006 20:20:14.0179 (UTC)
	FILETIME=[817EE330:01C6E33B]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Subject: [Widex] Updated Widex requirements draft (-03)
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>
Content-Type: multipart/mixed; boundary="===============0750331284=="
Errors-To: widex-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0750331284==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6E33B.80D890CE"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6E33B.80D890CE
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

Until posted in the IETF drafts repository the draft can be found here:=20
http://www.kolumbus.fi/vlad.stirbu/draft-ietf-widex-requirements-03.txt

Vlad

------_=_NextPart_001_01C6E33B.80D890CE
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7650.21">
<TITLE>Updated Widex requirements draft (-03)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Verdana">Hi,</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Verdana">Until posted in the =
IETF drafts repository the draft can be found here: </FONT>

<BR><A =
HREF=3D"http://www.kolumbus.fi/vlad.stirbu/draft-ietf-widex-requirements-=
03.txt"><U></U><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Verdana">http://www.kolumbus.fi/vlad.stirbu/draft-ietf-widex-requ=
irements-03.txt</FONT></U></A>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Verdana">Vlad</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C6E33B.80D890CE--


--===============0750331284==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0750331284==--




From widex-bounces@ietf.org Fri Sep 29 10:50:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GTJgp-0007Rv-Ra; Fri, 29 Sep 2006 10:50:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GTJgg-0007Iq-QF; Fri, 29 Sep 2006 10:50:02 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GTJgg-00077Q-Fc; Fri, 29 Sep 2006 10:50:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 6CBFC3288C;
	Fri, 29 Sep 2006 14:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GTJgg-0000aV-78; Fri, 29 Sep 2006 10:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1GTJgg-0000aV-78@stiedprstage1.ietf.org>
Date: Fri, 29 Sep 2006 10:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: widex@ietf.org
Subject: [Widex] I-D ACTION:draft-ietf-widex-requirements-03.txt 
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>
Errors-To: widex-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Widget Description Exchange Service Working Group of the IETF.

	Title		: Widget Description Exchange Service (WIDEX) Requirements
	Author(s)	: V. Stirbu, D. Raggett
	Filename	: draft-ietf-widex-requirements-03.txt
	Pages		: 11
	Date		: 2006-9-29
	
This document defines functional requirements for a framework and a
   protocol used to support XML-based user interfaces, where the user
   interface and application logic may be on different machines, and
   coupled via an exchange of XML DOM events and update/mutation
   operations.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-widex-requirements-03.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-widex-requirements-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-widex-requirements-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2006-9-29040930.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-widex-requirements-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-widex-requirements-03.txt"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2006-9-29040930.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--NextPart--





