60-Day Comment & Disclosure Period FAQ

 

What are the Chair’s responsibilities in preparation for the 60-Day Comment & Disclosure Period?

 

Are test logs required of Sample Implementations?

All Sample Reference Implementers are required to submit test pass logs in order to start the 60-Day Comment & Review Period.  Logs may be submitted as text files via e-mail to the TC Chair, cc:ing the WC Chair and Forum Secretary.  The UPnP™ Certification Test Tool is available to vendors on the Forum web site for pre-certification purposes.  The UPnP Certification Test Tool is available for download after agreeing to a click-through license agreement.  Vendors are encouraged to use the latest version of the UPnP Certification Test Tool.

 

The TC Chair reviews and verifies the test logs for true passes.  The TC Chair then signs his/her section of the 60-Day Comment & Review Period Sign-Off Sheet.

 

How many "master" Sign-Off Sheets are there?

There will be as many master sign-off sheets as there are standards.  If there is one standard per root device, then provide separate 60-Day Comment & Disclosure Period Sign-Off Sheets (with the respective tables, XML configuration files, and sample implementation test logs) for each root device. 

 

If there are multiple root devices, which need to be implemented together in the same standard, then provide one 60-Day Comment & Disclosure Period Sign-Off Sheet. 

 

Who should sign per company?

The company employee who claims responsibility for the Sample Reference Implementation may sign.  This may range from the Engineering Manager to the Program Manager in charge of the Sample Reference Implementation's development, but is a matter for internal company policy.

 

How should the Sample Reference Implementer sign?

Each signatory should sign his/her company’s designated “Sample Reference Implementer” section of the 60-Day Comment & Disclosure Period Sign-Off Sheet and fax his/her signed copy to Forum Secretary.  The Forum Secretary converts the signed fax into a PDF file for posting to the Web site.  All signatures do not need to be on the same fax.

 

How are the Proposed DCPs accessed during the 60-Day Comment & Disclosure Period?

The Proposed DCPs are available from two locations of the UPnP Forum web site:


What about Forum feedback?

A 60-Day Comment & Disclosure Period is required by the UPnP Forum Membership Agreement.  The general membership is asked to review the Proposed DCP(s) and to provide feedback.  A feedback alias is provided for this purpose – upnpfeedback@forum.upnp.org; feedback sent during the Comment & Disclosure Period should include the name of the proposed DCP in the subject line.  The Forum Secretary will forward all feedback to the WC Chair.

 

All feedback will be considered by the WC, including the Sample Implementers, and responded to by the WC Chair.  Not all feedback will necessarily impact the specification; this is clearly stated on the Web site and in the general kick-off announcement. 

 

Most of the feedback may be editorial in nature.  If the feedback significantly affects the specification and requires modification or re-testing of the sample implementations, the Comment & Disclosure Period may need to be repeated after finalization of the amended documents.   Since the timeframe for re-starting the period is not specifically stipulated by the UPnP Forum Membership Agreement, the Steering Committee has discretion in deciding the time duration of the subsequent Comment & Disclosure Period; however, a full 60-Day Comment & Disclosure Period will be assumed, unless specified otherwise.

 

What happens at the close of the 60-Day Comment & Disclosure Period?

  1. The WC Chair summarizes the feedback and steps taken regarding any feedback received.  The Chair drafts a recommendation to the Steering Committee to approve the Proposed DCP as a Standardized DCP, attaching the specification and XML configuration files for testing.  The Chair includes any auxiliary material (e.g., use case scenarios, whitepapers, etc.) that may be helpful in the interpretation or correct implementation of the final spec.  This information is sent by e-mail to the Forum Secretary.
  2. Upon receipt of the email from the WC Chair, the Forum Secretary officially calls for a Steering Committee vote.  The Steering Committee has 10 business days to review, comment, and vote on the Proposed DCPs. 
  3. When a three-quarters majority of affirmative votes is reached, the Proposed DCPs are approved as Standardized DCPs.

 

What happens if the SC 10-business day review, comment and vote period elapses without a three-quarters majority vote?

It is under the Steering Committee’s discretion to send the Proposed DCPs back to the Working Committee with a set of recommendations.

 

From Section 2.1(c)(ii) of the UPnP Forum Membership Agreement:

In the event the Proposed DCP is not adopted by the Steering Committee, the drafters of the Proposed DCP may re-convene to amend and/or modify the Proposed DCP, Reference Implementation test logs or test configuration files for re-submission to the Steering Committee.

 

What happens after the SC votes to approve the Proposed DCP as a Standardized DCP?

  1. The Chair forwards the Forum Secretary a “clean” (i.e. no revision marks or track changes) 1.0 version of the specifications, changing the disclaimer on all specifications to the text of the UPnP Forum Processes & Guidelines Document’s Appendix: Disclaimers).
  2. The Standardized DCP is posted to the public domain of the UPnP Forum web site (http://www.upnp.org/standardizeddcps/default.asp).
  3. The UIC is notified and companies can begin certifying devices against the Standardized DCP.