Re: [security-jc] Latest carter statement for approval via email vote

[Phil Griffin <phil.griffin@asn-1.com>]

Actually I meant ASC X9, the accredited standards committee
of ANSI. But I'd also be happy to recognize the directory
folks, as Karl and I have worked to create a liaison with
the ISO part of that group and a 'communication process'
with the ITU-T SG17 part of this joint work.

Not sure how to capture the joint group name in easily
read text - "the ISO/IEC and ITU-T Directory Group"?

Phil

Carlisle Adams wrote:

> Hi Darran,
> 
> One quick comment:  I believe what Phil was asking for in the "champion" 
> section was "X9" (as in ANSI X9), as opposed to "X.509" (as in ISO/IEC 
> X.509).  Having said that, however, I'm happy with either.  Phil can 
> correct me if I mis-heard him.
> 
> Carlisle.
>  
> 
>       ----------
>       From:   Darran Rolls[SMTP:Darran.Rolls@waveset.com]
>       Sent:   Thursday, August 22, 2002 1:49 PM
>       To:     Security Joint Committee
>       Subject:        [security-jc] Latest carter statement for approval
>       via email vote
> 
>       Below is the latest draft of the charter statement that includes
>       the discussion from today's con-call.   As I understand it, we are
>       operating an email vote to accept this text.  One vote per member
>       TC should be forwarded to the chair phil.griffin@asn-1.com before
>       close of business 9/02/2002.
> 
>        
> 
>        
> 
>       To promote the use of consistent terms
> 
>        
> 
>       ?        Through consultation with, and the participation of
>       member TC's, to encourage new and developing TC's to use
>       consistent security terms and definitions in specification
>       documentation.
> 
>        
> 
>       To promote re-use
> 
>        
> 
>       ?        To provide the definition and identification of re-usable
>       security related specification elements.  Security related
>       specification elements are defined as (but are not limited to)
>       object models, use cases, extensible XML elements, cryptographic
>       processes and deployment profiles.
> 
>                                                                                                                   
> 
> 
>       To champion an OASIS security standards model
> 
>        
> 
>       ?        To champion the creation of a reference model that shows
>       how OASIS security TC specifications are inter-related.  This
>       reference model shall define how OASIS security related
>       specifications "fit together" and relate to other security
>       relevant works at W3C, IETF, WS-I, X.509 etc.
> 
>        
> 
>       To provide consistent PR
> 
>        
> 
>       ?        To provide a single point of contact for addressing
>       security related enquiries at OASIS and in doing so to help
>       organize and coordinate security related comment and PR from OASIS.
> 
>        
> 
>       To promote mutuality, operational independence & ethics
> 
>        
> 
>       ?        The SJC will foster and maintain respect among OASIS
>       security TCs and for them in the security community at large. The
>       SJC will maintain a vendor neutral and vendor agnostic view in its
>       support for diverse security technologies.
> 
> 
> 
>       ?        The SJC will promote public safeguards and believes that
>       security technologies should be used solely for legal, ethical,
>       and nondiscriminatory purposes. The joint committee is committed
>       to the highest standards of systems integrity and data security in
>       order to deter identity theft, protect personal privacy, and
>       ensure equal rights in all security applications.
> 
>        
> 
>        
> 
>       Darran Rolls  
>       MSIM  drolls_waveset@hotmail.com
>       AIM    drollswaveset
>       YIM    drolls_waveset
>       http://www.waveset.com/
>       drolls@waveset.com
> 
>        
> 
>