OGSA Teleconference - 12 September 2005
=======================================

* Participants

  Jem Treadwell (HP)
  Andreas Savva (Fujitsu)
  Steven Newhouse (OMII)
  Takuya Mori (NEC)
  Tom Maguire (EMC)
  Hiro Kishimoto (Fujitsu)
  Mike Behrens (R2AD, LLC)

  Minutes: Andreas Savva

* Sep 7 minutes approved with no changes

* Jan 2006 F2F update

  Hiro has reserved a room at the FLA Sunnyvale facility for the week
  of Jan 16. (Same place used for the August meeting.)

* Roadmap 1.0 review

  Review of draft 21.

  - The change in Introduction, first paragraph, should be propagated
    to the Abstract too.
  - "Use of SAML for OGSI Authorization version 1.0"
    - Since this is for OGSI it should be dropped from the Roadmap.
    - Version 2.0 of this document might be based on WSRF but there is
      no concrete decision by the AuthZ WG yet. (Rechartering
      discussion still going on.) So such an entry cannot be added
      now.
    - Agreed to drop and update Roadmap accordingly
      (incl. spreadsheet).

  - "Attributes used in OGSA Authorization" 
    - In its current form it is not a Profile and so should be moved
      to section 4.

  - Roadmap title
    - The title should be changed so as to use OGSA as an adjective
    - It would also be nice to have OGSA(tm) in the title.
    - A number of alternatives were proposed and rejected before
      consensus was reached on 
                "Defining the Grid: A Roadmap for OGSA(tm) Standards
                version 1.0"

  - Sec.2.3: The OGSA-Related Naming Guidelines draft was recently
    made public by the GGF Editor. Section 2.3 should be updated
    accordingly and include a reference to this note.

  - Sec.5.3.3. contents should be made similar to 5.2.3 since they are
    both about the 'same' kind of Profiles.

  - What are the criteria for including a profile in section 5?
    - Agreed to add a sentence that Profiles must be based on the OGSA
      Profile Definition document.

  - All editing actions to be done by Jem.
  - Issue final call on the next draft.

* Secure Channel 1.0 review

  Reviewed draft sent out by Takuya.
  https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-security-profile-secure-channel/en/3

  - Title: It is different from the title given for this document in
    the Roadmap document. Agreed to change the title of this draft.
  - Status: Based on the contents of the Status section of the WSRF
    BP. Agreed to revise to make more specific to this Profile.
  - Abstract: Agreed to rewrite to focus on security aspects
    covered by this Profile.
  - Introduction: Agreed to rewrite to focus on security aspects of
    this Profile.
  - Profile Overview: Agreed to rewrite to focus on security aspects
    of this Profile.
  - Relationship with other profiles: Add relationship to WSRF BP and
    Anonymous Channel Profiles.
  - Targets: Reduce to the ones used in the document directly (and not
    just due to cross-referencing from terms in this section)
  - Conformance claim: Add the general basic security conformance
    claim URI defined by WSRF BP 1.0.
  - Sec.3 Security: Break into sections for each referenced profile
    (BSP and SAML) per WSRF BP.
  - Use of SSL: Takuya's intention with R0305 is to restrict use of SSL
    3.0 ("MUST use TLS")
    - Agreed to revise R0305 for clarity.
  - R0301,0302: mandates that the RECEIVER support both TLS and MLS;
    and SENDER can use either.
    - Hiro thinks that this sets too high a bar on implementations and
      should be relaxed for the RECEIVER also.
    - Takuya thinks that the secure channel profile sets a high bar
      anyway so this additional requirement is acceptable and is
      needed to promote interoperability.
    - No consensus reached.
    - Takuya will put the issue to the list to get more opinions.

* Next call

  - Secure Channel Profile review to be scheduled for the Monday call.