1 / 18

March 1 st Vice Chair Report

March 1 st Vice Chair Report. Authors:. Date: 2012-05-14. Abstract. This slide contains request reports and status from the 802.11 1 st Vice-Chair: Current Patent Slides. Participants, Patents, and Duty to Inform.

ralph-osborne
Download Presentation

March 1 st Vice Chair Report

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. March 1st Vice Chair Report Authors: Date: 2012-05-14 Jon Rosdahl (CSR)

  2. Abstract This slide contains request reports and status from the 802.11 1st Vice-Chair: Current Patent Slides Jon Rosdahl (CSR)

  3. Participants, Patents, and Duty to Inform All participants in this meeting have certain obligations under the IEEE-SA Patent Policy. Participants [Note: Quoted text excerpted from IEEE-SA Standards Board Bylaws subclause 6.2]: “Shall inform the IEEE (or cause the IEEE to be informed)” of the identity of each “holder of any potential Essential Patent Claims of which they are personally aware” if the claims are owned or controlled by the participant or the entity the participant is from, employed by, or otherwise represents “Personal awareness” means that the participant “is personally aware that the holder may have a potential Essential Patent Claim,” even if the participant is not personally aware of the specific patents or patent claims “Should inform the IEEE (or cause the IEEE to be informed)” of the identity of “any other holders of such potential Essential Patent Claims” (that is, third parties that are not affiliated with the participant, with the participant’s employer, or with anyone else that the participant is from or otherwise represents) The above does not apply if the patent claim is already the subject of an Accepted Letter of Assurance that applies to the proposed standard(s) under consideration by this group Early identification of holders of potential Essential Patent Claims is strongly encouraged No duty to perform a patent search Jon Rosdahl (CSR)

  4. Patent Related Links All participants should be familiar with their obligations under the IEEE-SA Policies & Procedures for standards development. Patent Policy is stated in these sources: IEEE-SA Standards Boards Bylaws http://standards.ieee.org/develop/policies/bylaws/sect6-7.html#6 IEEE-SA Standards Board Operations Manual http://standards.ieee.org/develop/policies/opman/sect6.html#6.3 Material about the patent policy is available at http://standards.ieee.org/about/sasb/patcom/materials.html If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at patcom@ieee.org or visit http://standards.ieee.org/about/sasb/patcom/index.html This slide set is available at https://development.standards.ieee.org/myproject/Public/mytools/mob/slideset.ppt Jon Rosdahl (CSR)

  5. Call for Potentially Essential Patents If anyone in this meeting is personally aware of the holder of any patent claims that are potentially essential to implementation of the proposed standard(s) under consideration by this group and that are not already the subject of an Accepted Letter of Assurance: Either speak up now or Provide the chair of this group with the identity of the holder(s) of any and all such claims as soon as possible or Cause an LOA to be submitted Jon Rosdahl (CSR)

  6. Other Guidelines for IEEE WG Meetings • All IEEE-SA standards meetings shall be conducted in compliance with all applicable laws, including antitrust and competition laws. • Don’t discuss the interpretation, validity, or essentiality of patents/patent claims. • Don’t discuss specific license rates, terms, or conditions. • Relative costs, including licensing costs of essential patent claims, of different technical approaches may be discussed in standards development meetings. • Technical considerations remain primary focus • Don’t discuss or engage in the fixing of product prices, allocation of customers, or division of sales markets. • Don’t discuss the status or substance of ongoing or threatened litigation. • Don’t be silent if inappropriate topics are discussed … do formally object. --------------------------------------------------------------- See IEEE-SA Standards Board Operations Manual, clause 5.3.10 and “Promoting Competition and Innovation: What You Need to Know about the IEEE Standards Association's Antitrust and Competition Policy” for more details. Jon Rosdahl (CSR)

  7. Current Procedures • IEEE 802 Policies & Procedures • (link to AudCom, approved by IEEE-SA Standards Board 25 August, 2010) • http://standards.ieee.org/board/aud/LMSC.pdf • IEEE 802 Operations Manual(effective 16 July, 2010) • http://ieee802.org/PNP/2010-07/IEEE_802_LMSC_OM_approved_100716.pdf • IEEE 802 Working Group Policies and Procedures(effective 22 July, 2011) • http://ieee802.org/PNP/2011-07/LMSC%20WG%20P&P%20Approved%20110722%20-%20Clean.pdf • IEEE 802.11 Operations Manual (WG11 OM)(Effective Sept 23, 2011) • https://mentor.ieee.org/802.11/documents?is_dcn=2&is_year=2009 Policies and Procedures hierarchy • http://www.ieee802.org/11/Rules/rules.shtml Jon Rosdahl (CSR)

  8. Reminder for Posting Documents • From 802.11OM – • All submissions presented to and all minutes shall be posted to the 802.11 document server. • Please check to ensure all documents are posted • If you have a “pending” document that is in error, let Adrian or Jon know. Jon Rosdahl (CSR)

  9. Proposed Rule Changes to 802 LMSC P&P • 802 LMSC P&P Changes: • Changes approved in March not yet accepted by AudCom • Subsequent changes made last night, and approved during Monday EC Meeting rolled up for new P&P to go to AudCom on Friday. • Changes:https://mentor.ieee.org/802-ec/dcn/12/ec-12-0022-01-00EC-july-pandp-suggested-changes.doc • Summary: • Remove redundant sentence • Defined Non-voting Members of Sponsor • Clarified who needs Endorsement letter and Confirmation • Explicitly states All WG use the LMSC WG P&P • Change “Calendar Days” to “Days” and define it as 24 hours. Jon Rosdahl (CSR)

  10. Proposed Changes to 802 LMSC OM • Some changes from March not adopted • Meeting Manager and Venue Selection clauses added • Officers allowed up to $500 for resonabe expenses between meetings. • Removed redundant definition of Sponsor • Further discussion this week, and then final proposal to be made on Friday. Jon Rosdahl (CSR)

  11. Proposed Changes to 802.11 OM • Changes to the OM are to address an attendee’s presence at a meeting, and to address ANA requests from the Regulatory SC. Jon Rosdahl (CSR)

  12. Proposed Changes to 802.11 OM • 3.6.4.1 • Add Paragraph: • Occasionally an attendee may wish to record their participation at a meeting (as required by IEEE-SA rules), but does not want (or is not entitled) to claim attendance credit. For example, the attendee may have been present for less than 75% of the slot. Such an attendee should send an email once per session to the WG Vice-Chair responsible for attendance to record the attendee’s presence. • New clause 9.1.6 to support requests from the regulatory SC to the ANA • Two minor edits (plural, double period). Jon Rosdahl (CSR)

  13. New: 9.1.6 ANA requests from the Regulatory SC The ANA accepts requests for allocation of numbers from the 802.11 Regulatory (REG) SC, subject to approval by the WG. The purpose of this support is to allow the WG to track rapidly changing regulatory requirements in a controlled way. Jon Rosdahl (CSR)

  14.  New: 9.1.6 (Cont-1) The process is as follows: 1. A request to the ANA from the REG SC shall be approved by motion in a meeting of the REG SC. The intent to hold a motion and the supporting documentation shall be announced to the WG on the WG reflector 4 weeks in advance of the motion being considered. Any motion in the REG SC shall be brought to the WG for confirmation. Jon Rosdahl (CSR)

  15. New: 9.1.6 (Cont-2) 2. The request shall be accompanied by a submission that can be referenced from the Description field of any allocation (i.e., entry in the ANA database) explaining how that value is used, and providing any additional information that cannot be recorded in the ANA database. • For example, a request for a new operating class would be accompanied by all the information that would go in a draft amendment or standard associated with the value – i.e., the full table row contents. Jon Rosdahl (CSR)

  16. New: 9.16.6 (Cont-3) 3. The ANA shall circulate the requests and tentative assignments to the 802.11 editor's reflector and ask TG editors to check for any conflict.  Typically the requests are generated following a session.  The ANA should respond to the request within 1 week.  The ANA shall reject any request that is not properly formed, i.e., does not supply all information required by the ANA form, or does not provide a reference document that fully describes the use of the requested value.  The last item of any resource will never be assigned and will always automatically be designated as “escape bit/number”. Jon Rosdahl (CSR)

  17. New 9.1.6 (Cont-4) 4. After a period of 1 week has elapsed and no conflict has been reported, the assignments are confirmed and the ANA shall upload an updated database document and notify the WG reflector. 5. The REG SC can, at its option, update the cited reference document to show the allocated value(s). 6. The ANA will bring any such allocations as a proposed change to TGm when a revision project is active. Jon Rosdahl (CSR)

  18. References Jon Rosdahl (CSR)

More Related