Registration for SIPit 20 is open

SIPit 20 will be hosted by Alcatel-Lucent in Antwerp,
Belgium April  
16-20,2007.

Registration is now open - see http://www.sipit.net for
more  
information.

RjS

_______________________________________________
Simple mailing list
Simpleietf.org
https:/
/www1.ietf.org/mailman/listinfo/simple

Hi all,

Concider the following example RLS document:

<?xml version="1.0"
encoding="UTF-8"?>
<rls-services xmlns="urn:ietf:paramsml:ns
:rls-services"
    xmlns:rl="urn:ietf:paramsml:ns
:resource-lists">
  <service uri="sip:marketingexample.com">
    <list name="marketing">
      <rl:list name="europe">
        <rl:entry uri="sip:svenexample.com">
         
<rl:display-name>Sven</rl:display-name>
        </rl:entry>
      </rl:list>
      <rl:entry uri="sip:joeexample.com"/>
      <rl:entry uri="sip:sudhirexample.com"/>
    </list>
    <packages>
      <package>presence</package>
    </packages>
  </service>
</rls-services>

My basic question here is if it is allowed to have a
list-based service 
containg yet another level of list(s). I'm not sure of why
one would need 
such a construction, but rather interested in finding out if
it can ever 
occur.
>From my understanding this should not break the
rls-services schema in 
list-usage-05. Do you agree?

I'm a bit confused of the text (4.4.5 Additional
constraints):
----
   o  In addition, an RLS services document can contain a
<list>
      element, which in turn can contain <entry>,
<entry-ref> and
      <external> elements.  The constraints defined
for these elements
      in Section 3.4.7 MUST be enforced.
----

Should this be interpreted as additional <list>
sub-elements are not 
allowed?

BR,
/Gustav E

____________________________________________________________
_____
Express yourself instantly with MSN Messenger! Download
today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471
ave/direct/01/


_______________________________________________
Simple mailing list
Simpleietf.org
https:/
/www1.ietf.org/mailman/listinfo/simple