Interconnect Software Consorium Socket API Extensions Working Group.
--------------------------------------------------------------------

Meeting:
	Tuesday 23rd July 2002
	20:00GMT (21:00BST, 04:00p EDT, 03:00p CDT, 01:00p PDT,
		 22:00CEST, 05:00JST+) 

	Toll Free (US & Canada):	  1 877 214 5010
	International:			  +1 (504) 588 9772
	Code:				  769497

--------------------------------

Attendees:
	David Edmondson, Sun
	Jeremy Harris, Sun
	John Kasperski, IBM
	Masanori Itoh, Fujitsu
	Jeff Messing, IBM
	Satya Sharma, IBM
	Louis Laborde, HP
	Vish Subramanian, HP

--------------------------------

Agenda:

1. Agenda bashing.
   None.

2. Review action items.
   dme falls at the first.

3. Issues relating to voting on the requirements.
   Louis: A16 has been raised as "too vague".  Concerns expressed
   	  that the treatment of allocated memory, for example, should
   	  be indicated in the requirements document.

	  The group agreed that the current statement could be
	  improved (to indicate that memory would be freed, for
	  example), but that this can be dealt with in the API
	  specification.

   Vish: Does the memory registration section require text which
   	 discusses shared memory segments ?  In particular, it seems
   	 that memory registration calls which indicate memory regions
   	 spanning multiple share memory segments should fail.

	 This will be covered in the API specification.

   Vish: A7.5: Is there a limit to the buffering that will take place?

   	 Jeff: The data should not exceed that space allocated for
   	 socket data buffers, so a limit already exists.

   Vish: A18: If an operation can be partially completed at
   	 initiation time, should some partial completion be returned?
   	 How might this interact with the "no blocking" clause in
   	 A1.1?

	 dme: Plans to vote against A18.
	 Jeff: Synchronous completion of receive operations can be
	       used by some applications, but there are dangers with
	       data ordering (i.e. some buffers may already be
	       sitting in the event queue).

   Jeff: The timers indicated in A19 could be very expensive to
   	 manage.  More useful would be some mechanism for detecting
   	 dead connections.

	 dme: This could be done in the application (or middleware)
	      layer.

   Vish: If HP wish to have A18, but require a socket option to
   	 enable it, how should they vote?

	 dme: Vote "1", with a note that it should be controlled by a
	      socket option toggle.

4. Linux SDP sourced requirements.

   Jeremy: The document should be more clear - it currently confuses
   	   socket protocol families (PF_*) with address families
   	   (AF_*).  In most cases the document should refer to
   	   protocol families.

   Vish: Using PF's is a Linux specific approach, it may not be
   	 applicable in other implementations.

   Jeremy: Using socket options to switch between protocol
   	   implementations feels wrong - it happens after much state
   	   may have been allocated, for instance.

   dme: Possibly a 4th argument to socket() should be added.  This
   	would indicate which instance of a particular {family, type,
   	protocol} should be used when creating a socket.

   The group agreed that no immediate impact from the Linux SDP
   project was known.  If a change to the socket() system call seems
   appropriate, we will discuss it later.

5. Louis' API strawman.
   Postponed until 2002-08-01.

6. AOB
   
   Near term schedule:
      Thursday meeting (2002-07-25): discuss voting results.
      Tuesday  meeting (2002-07-30): cancelled.
      Thursday meeting (2002-08-01): discuss Louis' API proposal.

--------------------------------

Outstanding Actions:

2002-04-18/02 dme.
	Draft a paper describing why a unified socket/file IO API
	would be useful.

2002-07-16/01 all.
	Examine the Linux-SDP paper for relevant material.
	Done.

2002-07-16/02 Annie.
	Ask the Linux-SDP team at Intel if they plan any API
	extensions.
	Done.

2002-07-16/03 dme.
	Revise the requirements and voting documents in light of the
	comments above.  Send out 2002-07-17.
	Done.

--------------------------------

Next Meeting:
	Thursday 25th July 2002
	20:00GMT (21:00BST, 04:00p EDT, 03:00p CDT, 01:00p PDT,
		 22:00CEST, 05:00JST+) 

	Toll Free (US & Canada):          1-888-742-8686
	International:                    +1-303-928-2600
	Conference ID:                    3378790

	Alternate teleconference numbers:
	Toll Free (US & Canada):	  1 877 214 5010
	International:			  +1 (504) 588 9772
	Code:				  769497

--------------------------------

Contact Details:
	email:	icsc-socketwg@opengroup.org
	web:	http://www.opengroup.org/icsc/member/sockets/