Re: formal submission of the security document to QR

[Maryann Hondo <mhondo@us.ibm.com>]

Tim,

the security group is working under the premises you suggest

1) we are editing the document with the comments we have received
2) we would support the release of the document to the other groups with
the understanding
that this is a "living guidelines document"
3) we are targeting to resubmit the document on March 19th

I do believe that in addition we might want to consider two other items:

1) setting up time for the security group ( and possibly the QR team) to
respond to and work with the subgroups which
are reviewing the document.....this could be a conference call, but we
should try to schedule
time to allow for explanation/discussion so that appropriate edits can be
made to the security document and the subgroup document

2) we have received several questions about the future of security work and
ebXML and
it would be helpful if the steering committee could include security when
it addresses the migration
of the ebXML working groups.

also,  we have several questions

is the QR team planning to meet in London and should the Security team plan
to meet with
the QR team or just submit the document?

is there a particular format to follow in documenting the change log?

thanks.

Maryann

"Tim McGrath" <tmcgrath@tedis.com.au> on 02/22/2001 04:22:10 AM

Please respond to tmcgrath@tedis.com.au

To:   Maryann Hondo <mhondo@us.ibm.com>
cc:   christopher ferris <chris.ferris@east.sun.com>,
      "ebxml-stc@lists.ebxml.org" <ebxml-stc@lists.ebxml.org>, "'ebXML
      Coordination'" <ebxml-coord@lists.ebxml.org>
Subject:  Re: formal submission of the security document to QR



my apologies for the delay in formally responding to you.

this document is a risk assessment of the ebXML framework and as such
identifies the areas were security considerations need to be  addressed in
the
ebXML technical specifications.  it is not a technical specification itself
and should not require a plenary vote.

from the perspective of improving the quality of all the ebXML technical
specifications, we are keen to get this document out to the ebXML community
as
early as possible.  in particular, those people involved in developing any
technical specifications about to enter their next review period.

therefore, we propose the following review process:

* we consider our discussions last week were a preliminary review

* the QR team recommend the immediate release of this document both for
public
comment and use as a completeness check with other specifications.
(NB this would mean you should can consider the comments we made and our
editiorial comments, as part of this public review).

* the Security team will then need to resubmit the new document (with a
change
log and
disposition statement) on or before 19th March.  (this will allow any
modifications to be incorporated into the second round of reviews for the
other
specifications).

Klaus, we suggest this document be posted to the "specifications under
review"
page of the ebXML web site and that a notice is put out to the general list
to
that effect, advising the document is open for public commment and also as
a
reference for other teams.

christopher ferris wrote:

> On behalf of Maryann, I formally submit the ta-security
> draft v0.3 to QR for their review.
>
> Cheers,
>
> Chris
> ---------------------
>
> Tim,
>
> I couldn't find a mailing list to submit this to for QR, the web pointer
> didn't seem to allow me to join the QR mailing list.
> Please submit this to the mailing list on behalf of the security group.
> It has one pass on editing but more to come.
>
> (See attached file: ebXML_sec_v0.3.doc)
>
> Thanks.
>
> Maryann Hondo
>
>
------------------------------------------------------------------------
>                          Name: ebXML_sec_v0.3.doc
>    ebXML_sec_v0.3.doc    Type: Download File (application/msword)
>                      Encoding: BASE64

--
regards
tim mcgrath
TEDIS   fremantle  western australia 6160
phone: +618 93352228  fax: +618 93352142