| DISCUSSIONS: |
- 1394 TA group is good
- - Develop charter and present to TA. Next 1394 TA meeting is Jan.
13 through 16 in Houston - Compaq. Send e-mail to James Snider
with proposed schedule (completed charter date, etc.). James
will look at and determine if OK.
- Update of issue from 5/14/97 Meeting in San Diego
- If the TA approves DSI then that will be the marketing liaison into the TA. There still may
remain both the PWG-C and DSI. This will not effect the activities of the 1394PWG.
- Ad hoc
- No requirement that these meetings occur in conjunction with TA
meetings. Associate with Printer Working Group sessions.
- Bring up as issue at January 8, 9, and 10 PWG meeting in ABQ,
NM to see if interest is there to form group.
- Short term plan
- Work on charter.
- Select chairperson.
- Write a charter (Greg LeClair will write first draft by 12/25/96)
- "Rope" a leader at Jan. PWG meeting.
- Present charter/plan/update at 1394 TA mtg.
- Begin work
- Update of issue from 5/14/97 Meeting in San Diego
Motion - by Larry Stein to "Request to the IEEE MSC that the 1394PWG be formed as a
formal IEEE Working Group. The April, 1997, 1394PWG Charter will be the basis for the
PAR."
- Seconded by Brian Batchelder
- Discussion ensued as to how the WG would coordinate with the PWG-C. The PWG-C would be
welcome to participate in the IEEE WG.
- Motion passed with no objections, one abstention.
- Update of issue from 6/23/97 Meeting in Nashua
- PAR - Project Authorization Request to MSC.
- Plan would be to submit at 7/14/97 mtg.
- Discussion on whether or not we need two PARs.
- Broader specification for device discovery that covers a wide range of
devices beyond Imaging Devices and Multi Function Devices.
- "Standard for node and Unit function discovery for Control and Status
Register (CSR), ISO IEC 13213 ANSI/IEEE Std 1212, architecture
implementations on the IEEE Std. 1394-1995 Serial Bus."
- p1394.X printing over IEEE 1394.
- "P1394.x Printing Protocol" standard would define a printing protocol
for use on IEEE Std 1394-1995 High Performance Serial Buses.
- CONCLUSION: We DO believe there is a sufficient need to submit the Device function discovery.
- We DO believe there is a sufficient need to submit the Device function discovery.
- We DO NOT believe there is enough understanding of the issues to submit the "P1394.x Printing Protocol" PAR.
- We will continue by refining a new "Requirements" document using our Scope and Purpose and the 1284 SIMPLE Document.
- Update of issue from 8/4/97 Meeting in Redmond, WA
- Logistical Issues
- 1394 TA will have DSI-WG
- DSI working group charter will be discussed on the reflector.
- The difference between the DSI and the PWG & PWG-C charter was not obvious.
- Sharp, Fuji Film, Cannon and Sony have each had independent FCP based proposals,
at the DSI they announced that they will work on a new unified proposal
together. The proposed completion date for the unified proposal is October 1997.
(ED NOTE) - NOT CLEAR ALL WERE BASED ON FCP!
- PWG proposed to draft and own the 1394 Printer Unit Architecture (PUA) document.
- Update of issue from 9/15/97 Meeting in Atlanta, GA
- Process and Logistical Issues
- How to bring closure and issue results
- FDS proposal (PWG & PWG-C)
- SBP-2 based printer definition (PWG)
- FCP based printer definition (PWG-C)
- IP/1394 based printer definition (TBD)
- Update of issue from October 27th Meeting in Boulder, CO
- Logistics - related activities
- 1394 TA mtg. report
- PWG/PWG-C gave a presentation on the Function Discovery Standard two weeks prior to this meeting.
- Sony made a presentation on SDD.
- The IEEE 1212 Working Group planned to meet around November 11-12 at SUN.
- 1284.3/.4 mtg. report
- A meeting was held the prior week to discuss plans to include 1284.3 and 1284.4 support in the
Windows OS. Meeting minutes should be posted to thse reflectors. May have an effect on 1394 PWG.
- Notified that PWG Chair had volunteered 1394 PWG group to propose a PAR for 1394 printing to the IEEE MSC.
- The group must determine who will participate, and who will write the PAR.
- Interested individuals whould contact the chair.
- Update of issue from Dec. 97 meeting in Los Angeles, CA
- Logistical Issues
- 1212 Working Group Summary
- Report on first meeting.
- Scope of work would be extended keys, FDS, and SDD.
- Planned to have meeting to review entire 1212 spec. in Jan. of 1998
- Dr. David James will be the chair.
- PWG-C Update
- Next meeting will be on December 28.
- Direct Printing Protocol has been changed from using FCP to a proprietary protocol. Application layer command set. Ueda-san is developing the transport protocol.
- Matsushita / Panasonic is driving another DPP using AV/C.
- PWG-C may end up supporting two DPP protocols.
- Nakamura-san will have FDS version 0.7 available prior to the next meeting.
- IEEE MSC PAR
- We don't think that we are quite ready to write the PAR at this time. Our study group has until March 1998 to decide.
- From January 26th, 1998 Meeting in Maui, HI
- Logistical Issues
- 1212 Working Group Summary
- Reiteration of points from from LA meeting.
- FDS Update
- Usage of extended key values to be more risky approach.
- Desire to go back to more compact approach.
- FDS Structure addition…
- Vendor Description Enhancement… (originally Sony SDD proposal)
- VDE SDD phase 1…
- VDE – a vendor directory will be added to include model name, brand, corporate id, etc.
- PWG-C Update
- Established on 12/17/96.
- Focusing on consumer "peer to peer" printing.
- PWG Joint Discussion since Mar 97.
- SWG1 - DPP – Target for "light" implementation – a new transport and command set.
- SWG2 - Direct Print using AV/C – extension from AV/C
- Direct Print Protocol Presentation
- Thin Layer Transport
- Not FCP based - see slides for more details
- Register space… - SDU management register is used to control segment data. Segment Data Unit size is negotiated during connection. The number of bits to define the SDU size has not yet been established.
- Questions:
- Why Not SBP-2? Because it is not symmetrical. Decision was that it was very important for between either side to be initiator or target.
- Discussion ensued regarding symmetry, was cut short due to "symmetry is an established requirement".
- DPP Command Set
- Objectives… – Want to assure connections with both simple and complex printers
- Negotiation Parameters - provide support for vendor unique items. - Potential issue regarding good quality print between dfferent manufacturers.
- Questions:
- There are different commands for different device types? How does an application make the distinction? You can find the functionality through FDS. At that point you can tell "Printer using DPP", and make connection based on that knowledge.
- IEEE MSC PAR
- We don't think that we are quite ready to write the PAR at this time. The study group has until March 1998 to decide.
- Tabled motion from LA meeting was discussed. Action held off until after spec review. Original motion was eventually withdrawn.
- From March 2nd, 1998 Meeting in Austin, TX
- 1394 Procedural Issues
- Document Owner
- Person willing to take ownership for a proposal. The responsibilities include (but might not be limited to):
- Validate entries in protocol comparison table
- Revising proposal to address issues
- Voting Rules
- The rules and procedures for voting:
- An individual must be present at a meeting or participate via teleconference to vote.
- Votes are counted on an individual basis - not as companies.
- Eligibility to vote is determined by physically attending two of the previous four meetings. Teleconference participation does not qualify as "attendance" for voting purposes.
- Meeting attendance requires attendance for all days of a scheduled meeting.
- With a simple majority vote, the group may confer voting rights to an individual that is not otherwise eligible to vote.
- Simple majority votes are sufficient for approving procedural and other minor issues.
- Two-thirds majority votes are required for "major technical issues"-as determined by the chairman prior to the discussion on the vote.
- A quorum is defined by having at least 50% of the eligible voters or 10 eligible voters present-whichever is less.
- The chairman will declare when quorum conditions have been met during a meeting. The quorum remains in effect for the duration of the meeting.
- It is the responsibility of the Secretary to maintain the list of eligible voters.
- Don Wright made a motion to adopt the above voting rules for the group.
- The motion passed unanimously.
- IEEE MSC PAR
- Group has still not decided. Discussion limited at this meeting.
- From April 6th, 1998 Meeting in Portland, OR
- Logistical Issues
- 1212 Working Group Summary
- FDS Update
- Notice given that the latest draft of the FDS proposal (now part of IEEE 1212) was posted on the 1394 PWG Website.
- IETF IP/1394 WG Summary
- IP over 1394 -- Making progress faster than originally expected.
- PWG-C Summary
- Reiteration about activities of SWG1 and SWG2.
- PWG-C does not seem to feel there is any problem with multiple protocols.
- 1394 PWG Procedural Issues
- Editor
- The group voted to have Alan Berkema as the new Editor for the Profile document.
- Voting Rules Revisited
- The clarification of "meeting attendance" was raised. Motion made that we (re-)define "meeting attendance" qualification as "physically attending any part of any day of a meeting." The motion passed.
- As a result, the updated voting rules and procedures are given below:
- An individual must be present at a meeting or participate via teleconference to vote.
- Votes are counted on an individual basis -- not as companies.
- Eligibility to vote is determined by physically attending two of the previous four meetings. Teleconference participation does not qualify as "attendance" for voting purposes. (It was suggested that eligibility requirements may be overruled by the chairman if he believes a company is unfairly "stacking" the vote.) "Meeting attendance" requires physical attendance of any part of any day of a meeting.
- With a simple majority vote, the group may confer voting rights to an individual that is not otherwise eligible to vote. This will be done on a "case-by-case" basis, and is intended to address those individuals that have made significant contributions to the group -- but have not attended the required amount of meetings.
- Simple majority votes are sufficient for approving procedural and other minor issues.
- Two-thirds majority votes are required for "major technical issues" -- as determined by the chairman prior to the discussion on the vote.
- A quorum is defined by having at least 50% of the eligible voters or 10 eligible voters present -- whichever is less.
- The chairman will declare quorum conditions have been met at the beginning of the meeting. The quorum remains in effect for the duration of the meeting -- regardless of whether any of the eligible voters leave early.
- It is the responsibility of the Secretary to maintain the list of eligible voters.
- The motion passed unanimously.
- From May 18th, 1998 Meeting in Crystal City, VA
- Logistical Issues
- 1212 Working Group Summary
- FDS Update
- Scope and Objective
- Provide a common, protocol/bus independent method for finding and describing a function in a multi-device (node) topology. This concept was approved as a need by the IEEE MSC.
- Provide a unit (protocol) independent method for (initial) Function Discovery. "Discover the gross functions first, then their supported protocols-and further function description."
- Provide gross functional information
- Provide pointers to associated directories
- Provide detailed information about the function
- PDS - Replaces FDS?
- New concept called Profile Discovery System - last 1212 meeting in Japan.
- A Profile describes a particular set of ROM information, including details about the function description, model information, protocol description, and other information.
- Seems that the information of FDS is orthogonal and independent of the PDS information. The two methods should not be viewed as competing alternatives, because in fact they achieve different goals-and could even co-exist together in the same implementation.
- A Profile directory could possibly be pointed to from the Function directory - no one has proposed....
- Drawback is a very large number of different Profile IDs to represent each unique combination of device information.
- Summary
- Protocol independent Function Discovery is necessary
- PDS and FDS have different objectives-they are not alternatives to each other
- No one person or WG has volunteered to take responsibility for developing the PDS concept into a detailed, coherent, formal proposal.
- ANSI SBP-2 WG Summary
- SBP-2 Draft Update - Note made regarding the latest version of SBP-2 has now been posted.
- PWG-C Summary
- Announcement of plan for Joint PWG / PWG-C meeting on Jun 9-10 in Tokyo area.
- Major agenda item was to approve DPP.
- Conflict with P1212r meeting in Bath.
- From August 17th, 1998 Meeting in Toronto
- Logistical Issues
- 1212 Working Group Summary
- Reviewed activity in 1212r.
- FDS Update
- The FDS proposal and other discovery concepts have been "stabilized" at the Bath meeting last month.
- Noted this doesn't necessarily mean that they can't become unstable in the future....
- PDS
- No further activity has taken place
- From September 28th, 1998 Meeting in Savannah, GA
- 1212 Working Group Summary
- No action taken at this meeting.
- From November 9th, 1998 Meeting in Tucson, AZ
- P1212r Working Group Summary
- Trying to decide how to use keywords for identifying Function Classes.
- IEEE - 1284.3 Working Group Report
- IEEE 1284.3 standard has completed balloting and was approved by a vote of 25 to 1, with 5 abstentions. This standard should be released at the end of Q1'99.
- 1394 PWG Procedural Issues
- Vote on one or two days for future meetings.
- The vote was 14 to 2 for a 2 day meeting.
- From December 14th, 1998 Meeting in San Diego, CA
- P1212r Working Group Summary
- Function Classes: Provide "Keywords" rather than explicit registry items. The keywords would be provided in a restricted ASCII format (lowercase a-z, 0-9, - ).
- Message Request and Message Response extensions.
- Next 1212 Meeting - Tueday following Jan. PWG.
- PWG / PWG-C Joint Meeting in January
- Status of DPP 1.0
- Keyword discussions
- Update of issue from April 13th, 1999 Meeting in New Orleans, LA
- Logistical Issues
- 1394 PWG Charter
- Noted issue to "Review and discuss the initial 1394PWG Charter (3/3/97). Should this be discussed at the general PWG meeting?"
|
