= Agenda   $Revision: 1.6 $

DATE: WEDNESDAY, August 1, 2012
TIME: 0900-1130
Location: REGENCY F

Jabber:
xmpp:weirds@jabber.ietf.org
http://jabber.ietf.org/logs/weirds


Note, currently there are no specific documents that are being
discussed. The assumption is that all potential working group
documents, the ones listed on http://tools.ietf.org/wg/weirds/, have
been read as there may be references made to them.


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

ADMINISTRATIVE (5 min) chairs.
	
   * NOTE WELL
   * AGENDA BASH
   * BLUESHEETS 
   * NOTE TAKER and JABBER


PART A. Some guiding questsions =====
   Goal: Identify, clarify, and possibly answer some questions that will help us
         guide during the hand-work
   Best outcome: Consensus about appropriateness of the questions, and
   consensus on the high-level direction.

   A.1. Supporting Objects.
        Goal: Make sure that there will not be misunderstandings
        later-on when the working group talks about "Supporting Objects".
        Context: Mailthread with subject "Supporting Objects".

	+ WG chairs (5 mins)

   A.2. Service Differentiation in a REST-pect-ful way.

        How to define objects so you can restrict access to certain
	resources within the object.
	Context: Mailthread with subject: "REST-pect-ful"        

        In particular Personal Identity Information; it might be that
	linking several resources to the same ID is not
	allowed. Assuming that that policy requirements holds
	somewhere. How to design the protocol to allow for that policy
	to be implemented?

      + Shuo Shen: Considerations and questions on authentication
        issues of WEIRDS ( 30 mins including discussion)


   A.3. RESTful versioning and extensions
        Goal: Determine whether we want to be able to version the
        protocol (in terms of supported objects) and determine if and
        how we want to go about extensibility.
        
        Context: See maillist-thread with subject "extensibility in
	weirds" and a mails with subject "Category of Objects".
        http://www.ietf.org/mail-archive/web/weirds/current/msg01225.html

	+ Andy Newton presents the issues. (30 mins including discussion)

   A.4. Object inventory
        Approach to defining the set of data that should go into version 1 of the core protocol
        Context: see maillist-trhead with subject "Divide and Concquer" 
        * presentation of the spreadsheets.
        * Design team approach. (one or more).

      + Ning Kong: Presents the object inventory (30 mins including discussion)


   A.5. Finding the appropriate resource
        Goal: 1. Determine whether mapping is in scope and if so
        if that scope is limited.
             2.  Establish which ideas are on the table and if
        possible choose a direction.

        Context: Mailthread with subject "Redirection in the RESTful WHOIS world"

	+ Chris Wright and John Levine provide context and describe the issues (30 mins including discussion)


Part B. Specfics.
   Goal: Resolve issues and questions that are specific to certain documents.

There are no specific issues at this time.




Part C. Organizing next steps
   Goal: Define actions and identify owners.

   Topics for discssions and action are:
   * Adapting working group documents (as working documents, not
     necessarily on the track towards RFC)
   * Identify editors, or appoint design teams.

   + Chairs (10 mins)