RE: [dss-x] dss:RequesterIdentity use of saml:NameIdentifierType

["Pope, Nick" <Nick.Pope@thales-esecurity.com>]

Juan Carlos,

Unfortunately I cannot make the 4th Feb meeting.  Will attempt to attend the
following meeting on 18th if you wish to continue discussions.

Nick

> -----Original Message-----
> From: Juan Carlos Cruellas [mailto:cruellas@ac.upc.edu]
> Sent: 28 January 2008 16:59
> To: Pope, Nick
> Cc: dss-x@lists.oasis-open.org; 'Arshad Noor'
> Subject: Re: [dss-x] dss:RequesterIdentity use of saml:NameIdentifierType
> 
> Nick,
> 
> I would suggest to include this issue in the agenda of our next conf
> call so that we may start a thread on that and go back and comment to
> Arshad.....
> 
> Stefan, could you please to add such an item in the agenda of the next
> conf call?
> 
> Regards
> 
> Juan Carlos.
> Pope, Nick escribió:
> > Juan Carlos and All,
> >
> > I had an enquiry from Ashad Noor regarding DSS.  He is looking at
> applying a
> > legal signature profiles spec which makes use of the DSS
> > <dss:RequesterIdentity>.
> >
> > He asks:
> >
> >>    The DSS element <dss:RequesterIdentity>is from the DSS 1.0 spec and
> >>     references the saml:NameIdentifierType" from the SAML 1.0 spec.
> >>
> >>    As you know, even though applications can continue to reference
> >>    SAML 1.0, eNotary is defining its XSD at a time when SAML 2.0
> >>    is the current standard, and SAML 2.0 does not define a similar
> >>    element.
> >>
> >>    So, the question is, do you know what DSS itself is going to do
> >>    about the saml:NameIdentifierType for its schema, and should ECF
> >>    take that into consideration for the Symmetric Key profile, and
> >>    thus eNotary TC too?
> >>
> >
> > As far as I am aware no changes are planned in this area.  Is this true?
> >
> > Nick
> > Consider the environment before printing this mail.
> > "Thales e-Security Limited is incorporated in England and Wales with
> company
> > registration number 2518805. Its registered office is located at 2
> Dashwood
> > Lang Road, The Bourne Business Park, Addlestone, Nr. Weybridge, Surrey
> KT15
> > 2NX.
> > The information contained in this e-mail is confidential. It may also be
> > privileged. It is only intended for the stated addressee(s) and access
> to it
> > by any other person is unauthorised. If you are not an addressee or the
> > intended addressee, you must not disclose, copy, circulate or in any
> other
> > way use or rely on the information contained in this e-mail. Such
> > unauthorised use may be unlawful. If you have received this e-mail in
> error
> > please delete it (and all copies) from your system, please also inform
> us
> > immediately on +44 (0)1844 201800 or email postmaster@thales-
> esecurity.com.
> > Commercial matters detailed or referred to in this e-mail are subject to
> a
> > written contract signed for and on behalf of Thales e-Security Limited".
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this mail list, you must leave the OASIS TC that
> > generates this mail.  You may a link to this group and all your TCs in
> OASIS
> > at:
> > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
Consider the environment before printing this mail.
"Thales e-Security Limited is incorporated in England and Wales with company
registration number 2518805. Its registered office is located at 2 Dashwood
Lang Road, The Bourne Business Park, Addlestone, Nr. Weybridge, Surrey KT15
2NX.
The information contained in this e-mail is confidential. It may also be
privileged. It is only intended for the stated addressee(s) and access to it
by any other person is unauthorised. If you are not an addressee or the
intended addressee, you must not disclose, copy, circulate or in any other
way use or rely on the information contained in this e-mail. Such
unauthorised use may be unlawful. If you have received this e-mail in error
please delete it (and all copies) from your system, please also inform us
immediately on +44 (0)1844 201800 or email postmaster@thales-esecurity.com.
Commercial matters detailed or referred to in this e-mail are subject to a
written contract signed for and on behalf of Thales e-Security Limited".