Subject: RE: [Geopriv] Schema in common-policy-06 does not allow empty<identity/> element

From: "Thomson, Martin" <[email-masked]>
Date: Sun, 4 Dec 2005 23:07:42 -0600

That text sounds like it works; however, I'd suggest having only one way of saying "any authenticated entity".  I don't have any particular preference though, either works for me.

> -----Original Message-----
> From: [email-masked] [mailto:[email-masked]] On Behalf
> Of Jonathan Rosenberg
> Sent: Tuesday, 22 November 2005 2:13 AM
> To: Binu K S
> Cc: [email-masked]
> Subject: Re: [Geopriv] Schema in common-policy-06 does not allow
> empty<identity/> element
> 
> Good point, yes I see that now. This is the text I had in mind:
> 
> > 7.1.1.  Overview
> >
> >    The identity condition restricts matching of a rule either to a
> >    single entity or a group of entitites.  Only authenticated entities
> >    can be matched; acceptable means of authentication are defined in
> >    protocol-specific documents.  As usual, if the <identity> element is
> >    (or all its child elements are) omitted, identities are not
> >    considered and, thus, the condition matches any user, authenticated
> >    or not.
> 
> 
> which I interpreted to mean that <identity/> itself effectively catches
> only authenticated identities.
> 
> Either way is fine, really, we just need to be sure its clear.
> 
> -Jonathan R.
> 
> 
> Binu K S wrote:
> 
> > Hi Jonathan,
> >
> > Section 7.1.4.1 (Page 17) in common-policy-06 makes a distinction
> between
> >
> > <identity/>
> >
> > and
> >
> > <identity>
> >   <many/>
> > </identity>
> >
> > The first case matches all authenticated and unauthenticated
> > identities while the second matched authenticated identities.
> >
> > -Binu
> >
> > On 11/16/05, Jonathan Rosenberg <[email-masked]> wrote:
> >
> >>An empty identity element would imply all AUTHENTICATED identities, I
> >>think. Unauthenticated ones would not match.
> >>
> >>-Jonathan R.
> >>
> >>Binu K S wrote:
> >>
> >>
> >>>Hi,
> >>>
> >>>The current schema in common-policy-06 has a restriction that the
> >>>identity element cannot be empty. As a result, documents containing
> >>>the <identity/> element (all authenticated and unauthenticated
> >>>identities) are not validating. The identityType definition should
> >>>have minOccurs="0" in the choice specification.
> >>>
> >>>-Binu
> >>>
> >>>_______________________________________________
> >>>Geopriv mailing list
> >>>[email-masked]
> >>>https://www1.ietf.org/mailman/listinfo/geopriv
> >>>
> >>
> >>--
> >>Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
> >>Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
> >>Cisco Systems
> >>[email-masked]                              FAX:   (973) 952-5050
> >>http://www.jdrosen.net                         PHONE: (973) 952-5000
> >>http://www.cisco.com
> >>
> >
> >
> 
> --
> Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
> Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
> Cisco Systems
> [email-masked]                              FAX:   (973) 952-5050
> http://www.jdrosen.net                         PHONE: (973) 952-5000
> http://www.cisco.com
> 
> _______________________________________________
> Geopriv mailing list
> [email-masked]
> https://www1.ietf.org/mailman/listinfo/geopriv

------------------------------------------------------------------------------------------------
This message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private information.  
If you have received it in error, please notify the sender
immediately and delete the original.  Any unauthorized use of
this email is prohibited.
------------------------------------------------------------------------------------------------
[mf2]

_______________________________________________
Geopriv mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/geopriv