September 2007
Eldad Perahia (Intel)
Slide 1
doc.: IEEE 802.11-07/2379r2
Submission
Coex Ad Hoc May Montreal Agenda and Report
Date: 2007-09-12
Name Company Address Phone email
Eldad Perahia Intel [email protected]
Authors:
September 2007
Eldad Perahia (Intel)
Slide 2
doc.: IEEE 802.11-07/2379r2
Submission
Abstract
Coex Ad Hoc in September Hawaii agenda and report regarding comment resolution of LB97 (802.11n), including straw polls
September 2007
Eldad Perahia (Intel)
Slide 3
doc.: IEEE 802.11-07/2379r2
Submission
Overview
⢠Submissions⢠Comment Resolution⢠Latest version of spreadsheet: 07/0339r18
September 2007
Eldad Perahia (Intel)
Slide 4
doc.: IEEE 802.11-07/2379r2
Submission
Highlights of the IEEE-SA Standards Board Bylaws on Patents in Standards
â Participants have a duty to tell the IEEE if they know (based on personal awareness) of potentially Essential Patent Claims they or their employer own
â Participants are encouraged to tell the IEEE if they know of potentially Essential Patent Claims owned by others
⢠This encouragement is particularly strong as the third party may not be a participant in the standards processâ Working Group required to request assuranceâ Early assurance is encouragedâ Terms of assurance shall be either:
⢠Reasonable and nondiscriminatory, with or without monetary compensation; or,⢠A statement of non-assertion of patent rights
â Assurances⢠Shall be provided on the IEEE-SA Standards Board approved LOA form⢠May optionally include not-to-exceed rates, terms, and conditions⢠Shall not be circumvented through sale or transfer of patents⢠Shall be brought to the attention of any future assignees or transferees⢠Shall apply to Affiliates unless explicitly excluded⢠Are irrevocable once submitted and accepted⢠Shall be supplemented if Submitter becomes aware of other potential Essential Patent Claims
â A âBlanket Letter of Assuranceâ may be provided at the option of the patent holderâ A patent holder has no duty to perform a patent searchâ Full policy available at http://standards.ieee.org/guides/bylaws/sect6-7.html#6
1
September 2007
Eldad Perahia (Intel)
Slide 5
doc.: IEEE 802.11-07/2379r2
Submission
6.2 Policy
IEEE standards may be drafted in terms that include the use of Essential Patent Claims. If the IEEE receives notice that a [Proposed] IEEE Standard may require the use of a potential Essential Patent Claim, the IEEE shall request licensing assurance, on the IEEE Standards Board approved Letter of Assurance form, from the patent holder or patent applicant. The IEEE shall request this assurance without coercion.
The Submitter of the Letter of Assurance may, after Reasonable and Good Faith Inquiry, indicate it is not aware of any Patent Claims that the Submitter may own, control, or have the ability to license that might be or become Essential Patent Claims. If the patent holder or patent applicant provides an assurance, it should do so as soon as reasonably feasible in the standards development process. This assurance shall be provided prior to the Standards Boardâs approval of the standard. This assurance shall be provided prior to a reaffirmation if the IEEE receives notice of a potential Essential Patent Claim after the standardâs approval or a prior reaffirmation. An asserted potential Essential Patent Claim for which an assurance cannot be obtained (e.g., a Letter of Assurance is not provided or the Letter of Assurance indicates that assurance is not being provided) shall be referred to the Patent Committee.
A Letter of Assurance shall be either:
a) A general disclaimer to the effect that the Submitter without conditions will not enforce any present or future Essential Patent Claims against any person or entity making, using, selling, offering to sell, importing, distributing, or implementing a compliant implementation of the standard; or
b) A statement that a license for a compliant implementation of the standard will be made available to an unrestricted number of applicants on a worldwide basis without compensation or under reasonable rates, with reasonable terms and conditions that are demonstrably free of any unfair discrimination. At its sole option, the Submitter may provide with its assurance any of the following: (i) a not-to-exceed license fee or rate commitment, (ii) a sample license agreement, or (iii) one or more material licensing terms.
IEEE-SA Standards Board Bylaws on Patents in Standards
2
September 2007
Eldad Perahia (Intel)
Slide 6
doc.: IEEE 802.11-07/2379r2
Submission
Copies of an Accepted LOA may be provided to the working group, but shall not be discussed, at any standards working group meeting.
The Submitter and all Affiliates (other than those Affiliates excluded in a Letter of Assurance) shall not assign or otherwise transfer any rights in any Essential Patent Claims that are the subject of such Letter of Assurance that they hold, control, or have the ability to license with the intent of circumventing or negating any of the representations and commitments made in such Letter of Assurance.
The Submitter of a Letter of Assurance shall agree (a) to provide notice of a Letter of Assurance either through a Statement of Encumbrance or by binding any assignee or transferee to the terms of such Letter of Assurance; and (b) to require its assignee or transferee to (i) agree to similarly provide such notice and (ii) to bind its assignees or transferees to agree to provide such notice as described in (a) and (b).
This assurance shall apply to the Submitter and its Affiliates except those Affiliates the Submitter specifically excludes on the relevant Letter of Assurance.
If, after providing a Letter of Assurance to the IEEE, the Submitter becomes aware of additional Patent Claim(s) not already covered by an existing Letter of Assurance that are owned, controlled, or licensable by the Submitter that may be or become Essential Patent Claim(s) for the same IEEE Standard but are not the subject of an existing Letter of Assurance, then such Submitter shall submit a Letter of Assurance stating its position regarding enforcement or licensing of such Patent Claims. For the purposes of this commitment, the Submitter is deemed to be aware if any of the following individuals who are from, employed by, or otherwise represent the Submitter have personal knowledge of additional potential Essential Patent Claims, owned or controlled by the Submitter, related to a [Proposed] IEEE Standard and not already the subject of a previously submitted Letter of Assurance: (a) past or present participants in the development of the [Proposed] IEEE Standard, or (b) the individual executing the previously submitted Letter of Assurance.
IEEE-SA Standards Board Bylaws on Patents in Standards
3
September 2007
Eldad Perahia (Intel)
Slide 7
doc.: IEEE 802.11-07/2379r2
Submission
The assurance is irrevocable once submitted and accepted and shall apply, at a minimum, from the date of the standard's approval to the date of the standard's withdrawal.
The IEEE is not responsible for identifying Essential Patent Claims for which a license may be required, for conducting inquiries into the legal validity or scope of those Patent Claims, or for determining whether any licensing terms or conditions are reasonable or non-discriminatory.
Nothing in this policy shall be interpreted as giving rise to a duty to conduct a patent search. No license is implied by the submission of a Letter of Assurance.
In order for IEEEâs patent policy to function efficiently, individuals participating in the standards development process: (a) shall inform the IEEE (or cause the IEEE to be informed) of the holder of any potential Essential Patent Claims of which they are personally aware and that are not already the subject of an existing Letter of Assurance, owned or controlled by the participant or the entity the participant is from, employed by, or otherwise represents; and (b) should inform the IEEE (or cause the IEEE to be informed) of any other holders of such potential Essential Patent Claims that are not already the subject of an existing Letter of Assurance.
IEEE-SA Standards Board Bylaws on Patents in Standards
4
September 2007
Eldad Perahia (Intel)
Slide 8
doc.: IEEE 802.11-07/2379r2
Submission
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 fixing product prices, allocation of customers, or dividing 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.
--------------------------------------------------------------- If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at [email protected] or visit
http://standards.ieee.org/board/pat/index.html
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.
This slide set is available at http://standards.ieee.org/board/pat/pat-slideset.ppt 5
September 2007
Eldad Perahia (Intel)
Slide 9
doc.: IEEE 802.11-07/2379r2
Submission
Further Information
⢠IEEE Code of Ethicsâ http://www.ieee.org/web/membership/ethics/code_ethics.html
⢠IEEE-SA Affiliation FAQâ http://standards.ieee.org/faqs/affiliationFAQ.html
⢠IEEE-SA Antitrust & Competition Policyâ http://standards.ieee.org/resources/antitrust-guidelines.pdf
⢠IEEE-SA LETTER OF ASSURANCE (LOA) FORMâ http://standards.ieee.org/board/pat/loa.pdf
⢠IEEE-SA STANDARDS BOARD PATENT COMMITTEE (PATCOM) INFORMATIONâ http://standards.ieee.org/board/pat/index.html
⢠IEEE-SA PATENT FAQâ http://standards.ieee.org/board/pat/faq.pdf
⢠IEEE 802 LAN / MAN STANDARDS COMMITTEE (LMSC) POLICIES & PROCEDURESâ http://grouper.ieee.org/groups/802/policies-and-procedures.pdf
⢠IEEE 802.11 WLANS WORKING GROUP POLICIES & PROCEDURESâ http://www.ieee802.org/11/DocFiles/06/11-06-0812-03-0000-802-11-policies-and-proceedures.htm
September 2007
Eldad Perahia (Intel)
Slide 10
doc.: IEEE 802.11-07/2379r2
Submission
Rules / Procedure
⢠As a general rule, we will NOT be reviewing CIDs on a one by one basis
⢠Resolution of comments will in most cases be based on submissions
⢠Coex Ad Hoc chair will bring resolutions which passed by 75% or more for motion in TGn, with affirmation of Ad Hoc
⢠Votes between 50% - 75% may be brought to TGn for further discussion and votes to break deadlock
September 2007
Eldad Perahia (Intel)
Slide 11
doc.: IEEE 802.11-07/2379r2
Submission
Subgroups (1/2)
⢠40-20 in 2.4GHzâ 6 commentsâ CIDs: 2134, 2883, 2509, 2581 (Matt F., 07/2020)â CID 2481: 40MHz in 2.4 GHz scanning TBDsâ CID 2906: duplicate DSSS (Allert)
⢠PCOâ 31 commentsâ 11.16â Tomo is assignee
⢠L-SIG TXOPâ 6 commentsâ CIDs 2233, 232, 2254 (07/734)â CIDs 2171, 566, 1743 â Yuichi is assignee
⢠ECSAâ CID 3024 (Add Supported Regulatory Classes sub-element to Optional Extension of Neighbor Report)â Refer comment to TGk?
⢠DFS & channel selectionâ 9 commentsâ CIDs 3083, 2582, 1870, 2583, 2585 (Matt F., 07/2020)â CIDs 2572, 2893, 2575, 2894 (Solomon, 07/2326 and/or TGy 07/2365)
September 2007
Eldad Perahia (Intel)
Slide 12
doc.: IEEE 802.11-07/2379r2
Submission
Subgroups (2/2)
⢠Channel switchingâ 14 comments (Matt F., 07/2020)
⢠CCA sensingâ 4 commentsâ 568, 70, 187, 2963 â Assaf is assigneeâ CID 70, Doug, 07/2334
⢠40/20â 6 commentsâ All addressed by Vinko, 07/611
⢠Protection mechanismsâ 64 commentsâ 24 addressed by Bjorn in 07/2316â 40 addressed by Bjorn in 07/2380
⢠DSSS-CCKâ 9 commentsâ All addressed by Eldad, 07/2328
September 2007
Eldad Perahia (Intel)
Slide 13
doc.: IEEE 802.11-07/2379r2
Submission
Submissions Related to Comment Resolution
⢠Matt F.â 11-07-2020-13-000n-lb97-cid-2582-bss-width-switching.doc
⢠Vinkoâ 11-07-0611-03-000n-lb97-coex-20-40-coex-comments-resolution.doc
⢠Yuichiâ Continuation of 11-07-734 (3/4 done)â 11-07-2394-00-000n-lb78-coex-lsigtxop-final.doc
⢠Bjornâ 11-07-2316-01-000n-lb97-coex-protection-mechanisms-part-1.docâ 11-07-2380-00-000n-lb97-coex-protection-mechanisms-part-2.doc
⢠Dougâ 11-07-2334-01-000n-discussion-on-cca-sensing-on-20-40-mhz-secondary-channel-with-pifs-and-difs.pptâ 20/40 operation in 5 GHz
⢠Eldadâ 11-07-2326-02-000n-tgn-lb97-coex-cid-2893.docâ 11-07-2328-02-000n-coex-dsss-cck.docâ Scanning parameter
⢠Tomokoâ 11-07-2122-00-000n-tgn-lb97-submission-for-category-pco-in-coex-ad-hoc.doc
⢠Assaf⢠Peter
â Scanning parameter
Red indicates completedsubmissions
(+) indicates submissionwas discussed
September 2007
Eldad Perahia (Intel)
Slide 14
doc.: IEEE 802.11-07/2379r2
Submission
ERs & EMR
⢠CID 2243 (ER)â Comment proposes to modify a paragraph in the LSIG TXOP section that was already
deleted based on CID 1737â Resolution in July was to Accept and refer to CID 1737â Resolution should be âCounter. refer to CID 1737â
⢠CID 3272 (ER)â 07/614r10 deleted all text in 9.20.4 and replaced it with new textâ However the resolution to CID 3272 was to accept a modification to the second
paragraph in 9.20.4, that now no longer exists⢠Change "A non-AP STA that is a member of a 40 MHz BSS shall not transmit 20 MHz frames
in the secondary channel." to "A non-AP STA that is a member of a 40 MHz BSS shall not transmit non-Control type 20 MHz frames in the secondary channel.â
â Previously agreed upon resolution to CID 3272 in 07/614r10 will be added to 07/2020â Resolution should be âAccept. Refer to 07/2020rXXâ
⢠CID 1669 (EMR)â Comment states that the scanning is too slowâ Comment is recycled, as was CID 2481, awaiting scanning parameters discussion of
TBDs
September 2007
Eldad Perahia (Intel)
Slide 15
doc.: IEEE 802.11-07/2379r2
Submission
DFS & Channel Selection & E-CSA
⢠All modifications to 11.9.7 have been removed from the draft, as they were incorporated in the TGy draft
⢠CIDs 2572, 2893, 2575, 2894 ask for modifications to text that is in the TGy draft, along with addition modifications to signaling E-CSA capability
⢠07/2326 resolves these CIDs by modifying both TGy and adding new TGn text⢠07/2326r0 was presented on the August 22 Coex conference call and was updated to
07/2326r2 based on comments during call⢠TGy has incorporated proposed changes in 07/2326r2 into their own E-CSA
submission 07/2365, since similar comments were also submitted to their letter ballot
⢠TGy will vote on the adoption of 07/2365 on Tuesday, September 18th during the AM1 session
⢠Proposed steps:â Defer discussion of 07/2326 until after TGy meetingâ If 07/2365 adopted by TGy, resolve CIDs 2572, 2893, 2575, 2894 with âCounter. addressed
by TGy 07/2365ââ If 07/2365 not adopted by TGy, discuss 07/2326r2
September 2007
Eldad Perahia (Intel)
Slide 16
doc.: IEEE 802.11-07/2379r2
Submission
E-CSA CID 3024
⢠Comment: Information on supported Regulatory Classes has to be advertised in the Neighbor Report as well
⢠Proposed change: Add Supported Regulatory Classes sub-element to Optional Extension of Neighbor Report
⢠Historyâ On August 21, Bruce emailed the chairs of TGy and TGk regarding
whether this change can be done and whether there is interest in making this change in TGk
â On September 6, Eldad emailed the chairs of TGn and TGk a reminder of this comment and a repeat of the suggestion that TGk take this comment
⢠Proposed Resolutionâ Counter. Since the Neighbor Report is still being changed in TGk, it is
preferable to manage all the Neighbor Report changes in TGk. The chair of TGk has been informed of this comment.
â (Bjorn: would could reject)
September 2007
Eldad Perahia (Intel)
Slide 17
doc.: IEEE 802.11-07/2379r2
Submission
40 MHz in 2.4 GHz Scanning Parameters
⢠As per motion #217, 07/614r10 was adopted with the following amendmentâ âvalues for the ranges and the DEFVALs of all the MIB
attributes that have a syntax of integer be replaced with TBDâ
⢠CIDs 2481 & 1669 are unresolved, pending decision on scanning parameters MIB attribute values
⢠Proposed stepsâ In order to address other open CIDs, defer discussion to next weekâ Make decision next week whether to discuss in Coex ad hoc or full
TGn
September 2007
Eldad Perahia (Intel)
Slide 18
doc.: IEEE 802.11-07/2379r2
Submission
Wed September 12 Agenda
⢠Submissionsâ 11-07-2122 (Tomo)â 11-07-2328-01-000n-coex-dsss-cck.doc (Eldad)â 11-07-2020-13-000n-lb97-cid-2582-bss-width-switching.doc
(Matt)
September 2007
Eldad Perahia (Intel)
Slide 19
doc.: IEEE 802.11-07/2379r2
Submission
Minutes for Wed September 12
⢠ERsâ Resolution should be âCounter. refer to CID 1737ââ No objection to updating the database accordingly
⢠DFS & Channel Selection & E-CSA CIDs 2572, 2893, 2575, 2894 â No objection to proposed steps on slide 15
⢠E-CSA CID 3024â Bjorn: we could reject
⢠40 MHz in 2.4 GHz Scanning Parametersâ Defer discussion to next week, unless we finish other CIDs
September 2007
Eldad Perahia (Intel)
Slide 20
doc.: IEEE 802.11-07/2379r2
Submission
07/2122 (PCO, Tomo)⢠CID 72
â Changes made to the first paragraphâ Changes made to third paragraph to define timer at beginning of paragraphâ Changes made to third paragraph to add âshallsâ to clarify normative natureâ There is now no change to text that was added by the previously resolved CID 71, so new resolution to CID 70 is deleted
⢠CID 652â Add â20 MHzâ to sentence for clarification
⢠CID 1772â Change from counter to reject
⢠CID 2603â Add status code for rejecting associationâ Change from accept to counter
⢠CID 2599â Operating Mode changed to HT Protectionâ need to confirm that the PCO exception to HT Protection is covered in HT Protection section
⢠CID 2600â Change to counterâ Delete quoted textâ Add sentence indicated that PCO operation occurs in a 20/40 MHz BSS
⢠CID 2604â Change to counter
⢠CID 2607â Change to counterâ Add âplus a transition timeâ
⢠CID 2609â Change to counterâ Modify proposed change to âat least PIFSâ
⢠Reviewed through 2612
September 2007
Eldad Perahia (Intel)
Slide 21
doc.: IEEE 802.11-07/2379r2
Submission
Thursday September 13 Agenda
⢠Submissionsâ 11-07-2122 (Tomo)â 11-07-2316-01-000n-lb97-coex-protection-mechanisms-part-1.docâ 11-07-2380-00-000n-lb97-coex-protection-mechanisms-part-2.doc
September 2007
Eldad Perahia (Intel)
Slide 22
doc.: IEEE 802.11-07/2379r2
Submission
Thursday September 13 minutes
⢠07/2122 (PCO, Tomo)â Continue with CID 2613â CID 2615
⢠Change âPCO non-AP active STAâ to âPCO active non-AP STAââ CID 2965 & 2966
⢠Change to rejectâ Do you accept 07/2122r3 as resolution to PCO CIDs contained in
said document, and bringing CIDs to motion in full TGn?⢠Yes: 13⢠No: 1⢠Abs: 0
September 2007
Eldad Perahia (Intel)
Slide 23
doc.: IEEE 802.11-07/2379r2
Submission
07/2316r1 (Protection Mechanisms, Part 1)
⢠CID 26â Yuichi is planning on submission changing multi-rate section forcing a response controlled by initiator of the
protection exchangeâ Defer
⢠CID 106â Undo proposed changeâ Change âshallâ to âareâ
⢠CID 1734â No objection to deleting note (after some discussion)â Need to redo resolution for 107
⢠Change it to counter, with resolution ânote deleted, refer to CID 1734â⢠CID 1701 & CID 109
â No objection to deleting note (after some discussion)⢠CID 1849
â Change to âcounterââ Discussion on whether to change protection of GF frames in presence of non-GF device from âshallâ to âmayââ Change proposed change from âmayâ to âshouldâ and delete âbut it is not a requirementâ
⢠CID 322â Change to ârejectâ (no draft text change)
⢠CID 1539â Discussion on duplicate DSSS
September 2007
Eldad Perahia (Intel)
Slide 24
doc.: IEEE 802.11-07/2379r2
Submission
CID 1539
⢠Do you support resolving CID 1539 with protection frame using Duplicate DSSS waveform?â Yes: 5â No: 12â Abstain: 2
⢠Defer CID 1539 to re-do strawpoll in TGn full ⢠Implies deferral of
â 1538, 25, 1848
⢠No objections to deferring
September 2007
Eldad Perahia (Intel)
Slide 25
doc.: IEEE 802.11-07/2379r2
Submission
07/2316, continued
⢠CID 1702â Need to confirm text in 9.13.3.3 and 9.13.3.2 before resolving this â Defer
⢠CID 2222â Change to âcounterââ Defer for CID 26
⢠CID 2809â Need to re-resolve CID 565: âCounter. Refer to CID 2809â
⢠CID 2815â Bjorn to have Shravan to send withdrawal to Eldad
September 2007
Eldad Perahia (Intel)
Slide 26
doc.: IEEE 802.11-07/2379r2
Submission
07/2380r0 (Protection Mechanisms, Part 2)
⢠CID 1658 & 1659â Modify resolution to refer to 2.07â Minority in favor of deferring CID in order to contact commenter
⢠CID 1660â Strawpoll: Should we reject CID 1660?
⢠Yes 13⢠No 4⢠Abs 4
â Strawpoll: accept wording in 07/2380r0⢠Yes: 9⢠No: 4⢠Abs: 5
â Strawpoll: resolution â07/329r2 was presented during March 2007 coex ad hoc. Straw polls were taken indicating that the TG needed additional evidence of a problem. No such evidence was presented.â
⢠Yes: 15 ⢠No: 1⢠Abs: 4
September 2007
Eldad Perahia (Intel)
Slide 27
doc.: IEEE 802.11-07/2379r2
Submission
07/2380r0 continued
⢠CID 28â Modified âsecond columnâ to column labeled ââŚâ
⢠CID 1540, 1850, 1706, 3094, 3095â Matt Smith: will be compatibility issue between D3.0 and D2.0 if RIFS Mode field is removedâ Defer to tomorrow for Matt to investigate
⢠CID 323â Strawpoll:
⢠Reject CID: 13⢠Do not reject CID: 2⢠Abs: 3
â Strawpoll:⢠In favor of current resolution wording: 11⢠Opposed to current resolution wording: 0⢠Abstain: 7
⢠CID 76â Strawpoll:
⢠Reject CID: 12⢠Do not reject CID:4⢠Abs: 3
â Strawpoll:⢠In favor of current resolution wording: 11⢠Opposed to current resolution wording:4⢠Abstain:2
â Strawpoll: removing âTG believes that theâ⢠In favor of modified resolution: 13⢠Opposed: 3⢠Abs: 4
September 2007
Eldad Perahia (Intel)
Slide 28
doc.: IEEE 802.11-07/2379r2
Submission
Motions
September 2007
Eldad Perahia (Intel)
Slide 29
doc.: IEEE 802.11-07/2379r2
Submission
Motion #
⢠Moved: Approve resolution of comments found on the tab labelled âcoex pending motion set 1â in document 11-07/0339r18.â Based on resolutions for a few more 20/40 comments in 07/2280r1â Resolves 12 comment with Cs and Râ Passed by no objection on July 25th Coex Ad Hoc conference call
September 2007
Eldad Perahia (Intel)
Slide 30
doc.: IEEE 802.11-07/2379r2
Submission
Motion #
⢠Moved: Approve resolution of comments found on the tab labelled âcoex pending motion set 2â in document 11-07/0339r18.â Based on resolutions for DFS Channel selection comments in
07/2098r3â Resolves 3 comment with Rsâ Passed by no objection on August 1st Coex Ad Hoc conference
call
September 2007
Eldad Perahia (Intel)
Slide 31
doc.: IEEE 802.11-07/2379r2
Submission
Motion #
⢠Moved: Approve resolution of comments found on the tab labelled âcoex pending motion set 3â in document 11-07/0339r18.â Based on resolutions for channel switching in 07/2055r3â Resolves 15 comment with A, Cs and Rsâ Passed by no objection on August 22nd Coex Ad Hoc conference
call
September 2007
Eldad Perahia (Intel)
Slide 32
doc.: IEEE 802.11-07/2379r2
Submission
Motion #
⢠Moved: Approve resolution of comments found on the tab labelled âcoex pending motion set 4â in document 11-07/0339r18.â CID 2479 was to be motioned in July as part of resolutions in
07/568r2â Allert asked for this CID to be deferredâ Allert later stated via email on Aug 23 that he accepts the
resolutionâ Resolves 1 comment with A