DRAFT IETF 45 WEIRD Minutes

> Thanks to Ray Plzak for taking the minutes for the WEIRD working group.
> Here's a draft of what I plan to submit for the proceedings.
> 
> Please request any changes to the minutes by next Wednesday.
> 
> Thanks for participating! It was great to see so many familiar faces in
> Oslo.
> 
> Chris Burke
> 
> -----Original Message-----
> Minutes from Weird WG Meeting - 14 July 1999
> Reported by Ray Plzak
> 
> > 1.  The working group charter was presented and explained.
> > 
> > 2.  The scope of activity was explained.  The scope is limited to
> > factual information relating to IETF WGs and BOFs.  Specultive
> > information will not be posted.
> > 
> > 3.  The name of the WEIRD group's web site was dicussed. 
> > Characteristics of the site name are dependent on target audience,
> > reachability from IETF home page, and discoverability from a search
> > engine.   The web site name will be a third level domain of the
> > IETF.ORG domain.  The name will be something like "info" or "digest"
> > or some similar name that will convey the idea of a repository of
> > information.
> > 
> > 4.  Page design was discussed.  The page will be an IETF content page
> not a WG page.  The design template submitted by Darin Jones
> > (http://www.ravenrock.net/usv/weird.html was deemed to be a suitable
> > functional layout.  Line length will not be more than 60 characters
> > because of human factors.  A site map needs to be developed.  Initial
> > design team volunteers are April Marine and Bob Quinn.  Darin Jones
> > will be asked to participate.  Others may volunteer from the list.
> The size of the design team will be limited to no more than 5 or 6.
> 
> > 5.  Content was discussed.  The target audience is people who are
> > either new to the IETF or are internet generalists.  The scope of the
> > content is:
> > 
> > 	* Current WG and BOF activities.
> > 	* Specific Dependencies and interrelationships between a WG and BOF.
> > 	* BOF history
> > 	* Things hard to find on the IETF pages
> > 	* Things not found on the IETF pages
> > 
> > Hits on various items will be tracked to aid in determining the
> > usefullness of the item.
> > 
> The web page will be put up with a statement that this is work in
> > progress and is initially put up to get information out to the internet
> > community but will be improved over time.  Ideas for improvement
> > will be solicited in this statement.
> > 
> > Items will be identified as either no/low maintenance and required
> > maintenance.  The no/low maintenance items will consist primarily
> > links to other pages.  Maintenance required items will require the
> > participation of the Secretariat.
> > 
> A list of specific content to work on first was discussed.  Three items
> > were selected for immediate action.  Those three are:
> > 
> > 	*  Quick and Dirty Links.  These are links that can be identified
> > and established quickly.  Examples are link to RFC editor queque and the
> > IETF RFC search engine.  A list of links will be solicited from the WG
> > mail list.
> > 	*  Area Director's Overview.  April will prepare a sample using
> > the User Services Area.  She will post this to the list for comment.
> > Based upon comment a template will be developed which she will present
> to
> > the other ADs for their input.
> > 	* Hot Topics.  This item will be developed from the hot topics
> > provided by the ADs and from the list.  Topics from the discussion are
> > IPv6, IPtelephony, QoS, Security, and Multicast.  Ginny Listman will
> > monitor the list for Hot Topics.
> > 
> > Other things to do but for which no implementation schedule was
> > established are:
> > 
> > 	* FAQ links.  A list of questions to assist the visitor in finding
> > content.  There will be a short answer with a link to the source for a
> > more detailed answer.
> > 	* Family tree of documents showing the IDs and RFCs related to
> > specific topic or protocol.
> > 	* RFC Supplement Section.  A collection of documentary items that
> > cannot be included in an RFC because of RFC format requirements -
> > primarily this refers to graphic depictions of concepts, processes, and
> > topologies that are described in the text of an RFC.  The RFC editor
> must
> > become involved in this process.
> > 	* BOFs
> > 	* Other sources (IAB, Plenary session, etc)
> > 	* Meta contents archive
> > 	* Feed Back (feed back form from visitors on what they couldn't
> > find.
> > 	* IETF Rock - A graphical depiction of how an idea proceeds
> > through the ID stage through the RFC stage - how STDs become STDs etc.
> >