1. Project: IEEE 802.15 Working Group for Wireless Personal Area Networks (WPANs)
Submission Title: [WG Liaison Report, No.15]
Date Submitted: [12Nov01]
Source: [Ian Gifford] Company [Consultant]
Address [23 Kelshill Road, MA USA 01863]
Voice:[ ], FAX: [ ],
Re: [-01/291r1, etc.]
Abstract: [This Liaison Report is a running Liaison report that is offered to the WG for their consideration. It is only as good as what is provided to the Author…there are many WG Liaisons that are not captured as they are not provided to the Author or Liaison Officer.]
Purpose: [Our Sponsor requested that an official Liaison Officer be added to the WG. This report is for the Sponsor and/or the WG.]
Notice: This document has been prepared to assist the IEEE It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.
Release: The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by
July 2001
doc.: IEEE /291r0
March 2001
Ian Gifford, Consultant
Ian Gifford, Consultant

2. IEEE 802.15 Working Group for Wireless Personal Area Networks™
July 2001
doc.: IEEE /291r0
March 2001
IEEE Working Group for Wireless Personal Area Networks™
Liaison Report #15
November 2001 Austin, TX USA
Ian Gifford, Consultant
Ian Gifford, Consultant

3. Contents Liaison Objectives Liaison Summary Liaison Reports
March 2001
Contents
Liaison Objectives
Liaison Summary
Liaison Reports
Liaison Negotiations
Liaison Observations
Ian Gifford, Consultant

4. Liaison Objectives Promote the IEEE as a Value Add
March 2001
Liaison Objectives
Promote the IEEE as a Value Add
Promote the IEEE 802 as a leader in Wireless Standards-Making
Promote P as an expert in WPANs
Request/Receive Draft Standard Submissions from External and Internal (IEEE) from our Liaison activities
Ian Gifford, Consultant

5. Liaison Summary Active Liaison List Nonactive Liaison List
July 2001
doc.: IEEE /291r0
March 2001
Liaison Summary
Active Liaison List
TG1 – BSIG (Gifford/Siep-Truntzer)
TG2 – BSIG (Shellhammer/Sizer)
TG3 – BSIG (Barr/Siep)
*TG4 – WMA (Allen/?)
TG4 – BSIG (Heile/Siep)
TG4 – ZigBee Working Group
IEEE (?/Kerry)
IEEE (?/RogerM )
IEEE
Standards Activities, Standards Publishing Programs (Gifford/Tatiner)
IEEE Standards Dept., Balloting Center (Gifford/Nielsen)
*IEEE PatCom (Gifford/?)
*IEEE RevCom (Gifford/Ringle)
Nonactive Liaison List
IEEE (/Lindinsky)
IEEE (/Carlson)
ATM Forum WATM (/Delaverson)
Digital Imaging Group (Allen/?)
DSRC (?/Kurihara)
ETSI BRAN (?/Khun-Jush)
HomeRF Working Group (/Manny)
IETF BOF on Bluetooth over IP (Siep/Atwal, Akers)
IrDA (/McKay)
UWBWG (/Withington)
WAP Forum (/Parrish)
WECA (Heile/?)
WLANA (?/DiCillo)
Other Liaisons?
Note 1: /Liaison
Note 2: ? Unknown
Note 3: * = new
Ian Gifford, Consultant
Ian Gifford, Consultant

6. IEEE 802.15 Working Group for Wireless Personal Area Networks
March 2001
IEEE Working Group for Wireless Personal Area Networks
External Liaison Report
Ian Gifford, Consultant

7. Bluetooth™ TG1 Report Telecon & Meetings E-Mail’s to Bluetooth SIG
July 2001
doc.: IEEE /291r0
March 2001
Bluetooth™ TG1 Report
Telecon & Meetings
27Oct01 Truntzer & Gifford meeting
Miscellaneous
’s to Bluetooth SIG
3Oct01 Bluetooth SIG LoA
’s from Bluetooth SIG
23Oct01 Bluetooth SIG LoA
Next Steps
Update BSIG PM during/post Session #15/Austin
Joint BSIG & IEEE Press Release
Bluetooth SIGnal Editor/Publisher and Issue No. 7, 8, 9, etc., follow up
Ian Gifford, Consultant
Ian Gifford, Consultant

8. ZigBee Working Group ? July 2001 doc.: IEEE 802.15-01/291r0 March 2001
From:
To:
Sent: Monday, June 11, :13 PM
Subject: ZigBee information
Dear all,
The temporary ZigBee working group web page can be found at:
This will replaced by at some point in time.
On the site (the name PURLnet was one of our old unsuccessful
attempts at getting a working name), select "Membership Information"
and then download the "Participants Agreement" and contact
for application instructions.
As a signed participant you will get access to the members only part
of the site (which includes the latest ZigBee specification) and
access to the face-face meetings.
Best regards,
Phil.
Phil Jamieson,
Advanced Systems & Applications Laboratory,
Philips Electronics UK Ltd.,
Cross Oak Lane, Direct Telephone: +44 (0)
Redhill, Switchboard: +44 (0)
Surrey, Fax: +44 (0)
RH1 5HA,
United Kingdom Central URL:
Ian Gifford, Consultant
Ian Gifford, Consultant

9. Wireless Multimedia Alliance
July 2001
doc.: IEEE /291r0
March 2001
Wireless Multimedia Alliance ?
From:
To:
Sent: Monday, June 11, :13 PM
Subject: ZigBee information
Dear all,
The temporary ZigBee working group web page can be found at:
This will replaced by at some point in time.
On the site (the name PURLnet was one of our old unsuccessful
attempts at getting a working name), select "Membership Information"
and then download the "Participants Agreement" and contact
for application instructions.
As a signed participant you will get access to the members only part
of the site (which includes the latest ZigBee specification) and
access to the face-face meetings.
Best regards,
Phil.
Phil Jamieson,
Advanced Systems & Applications Laboratory,
Philips Electronics UK Ltd.,
Cross Oak Lane, Direct Telephone: +44 (0)
Redhill, Switchboard: +44 (0)
Surrey, Fax: +44 (0)
RH1 5HA,
United Kingdom Central URL:
Ian Gifford, Consultant
Ian Gifford, Consultant

10. IEEE 802.15 Working Group for Wireless Personal Area Networks
March 2001
IEEE Working Group for Wireless Personal Area Networks
Internal Liaison Report
Ian Gifford, Consultant

11. IEEE Report Telecon & Meetings E-Mail’s to IEEE E-Mail’s from IEEE
July 2001
doc.: IEEE /291r0
March 2001
IEEE Report
Telecon & Meetings
Miscellaneous
’s to IEEE
’s from IEEE
Next Steps
Follow up on /D Comments or D1.1 for FINAL RevCom approval 5Dec01
Follow up on Handbook request and plan Manuscript due 1H02
Follow up on RevCom pre submission feedback (Mid Nov01) and PatCom LoA feedback.
Ian Gifford, Consultant
Ian Gifford, Consultant

12. Liaison Negotiations Bluetooth™ SIG, Inc. IEEE
March 2001
Liaison Negotiations
Bluetooth™ SIG, Inc.
Joint BSIG & IEEE Press Release
IEEE
Review SA actions (see prior slide)
802.11/ Interim Meetings?
We need to identify hosts and venue 12 months out, or more.
We need to benchmark our Admin tools i.e., Balloting Tools, Comment DB, etc. to other IEEE WGs and other SDOs. As well as future proof our Membership DB.
Ian Gifford, Consultant

13. Liaison Observation – LBs for 802.15.2, .3, and .4
July 2001
doc.: IEEE /291r0
March 2001
Liaison Observation – LBs for , .3, and .4
The 92 Voters and the pending 28 nearly Voters are going to have their hands full voting on the following drafts:
IEEE Std
IEEE Std
IEEE Std
Note: The 2002 could slide to 2003 if we do not think this through.
We need to review the WG Balloting Tools to make it (1) consistent TG to TG and (2) as efficient as possible.
ACTION: AC to review recent DB (see slide notes below) and discuss. Update WG if something new is planned.
Definition of Terms:
*Comment formatting tool = Balloter to Ballot Resolution Committee (BRC)
comment formatting tool e.g., ASCII, XLS, DOC, etc.
*Comment resolution tool = Ballot Resolution Committee (BRC) to WG comment
resolution tool e.g., MDB, FP5, etc. - one (1) unique DB per draft/letter
ballot
*Ballot Resolution Committee (BRC) = formed after each WG Letter Ballot =
 ----- Original Message From: "Ian Gifford" "Steve J. Shellhammer" "Richard Alfvin" "Pat W. Kinney" "Nada Golmie" "Mike D. McInnis" "Jose Gutierrez" "John R. Barr" "Jim Meyer" "Jim D. Allen" "James Gilb" "David E. Cypher" "Bruce P. Kraemer" "Bob F. Heile" "Stuart Kerry" Friday, November 09, :23 AMSubject: Re: please post > Hi Rick, > > RA>Can you post this? > Done. > > RA>talk with you as soon as possible about our comment resolution database. > Ok. > > Definition of Terms: > *Comment formatting tool = Balloter to Ballot Resolution Committee (BRC) > comment formatting tool e.g., ASCII, XLS, DOC, etc. > *Comment resolution tool  = Ballot Resolution Committee (BRC) to WG comment > resolution tool e.g., MDB, FP5, etc. - one (1) unique DB per draft/letter > ballot > *Ballot Resolution Committee (BRC) = formed after each WG Letter Ballot > > Is this comment resolution tool for P /D0.8 or P /D0.9?  What > is the estimated opening date for the WG Letter Ballot?  If we assume > 19Nov01 then the need date for the D0.8 comment resolution tool DB becomes > very critical days after this date.  Of course it is nice to have the > DB now but it will take some time because the fields keep changing: > > In reviewing the TG3 comment formatting tool i.e., -01/373r1 > [01373r1P802-15_TG3-Issue-Submission-Template.xls]: > > 1 Issue Number > 2 Commenter's Initials > 3 Draft Version Number > 4 Clause number e.g., > 5 Page number e.g., , etc. > 6 Line number e.g., 1-54 > 7 Type of comments (E=editorial/T=technical) > 8 Class of Problem > 9 Comment/Rationale (Issue and reasoning behind it.) > 10 Recommended change (What change(s) it would take to make this clause > acceptable.) > 11 Disposition/Rebuttal (Do not write here during ballot phase; this is for > comment resolution phase.) > 12 Issue Status X,D,A,R > 13 Resolution Status O,A,W,C,Z > 14 Date Entered > 15 Date Completed > 16 Assignee > > I see 16 fields and that the Balloter is responsible for 3-10;  1-2 can be > derived post submission and the BRC is responsible for > > RA>I believe TG4 will most likely want to use the same tools. > > Does TG4 agree with the fields? or more importantly will they use the same > TG3 comment formatting tool i.e., -01/373r1?  Is this comment resolution > tool for P /D1.2 or P /D1.3?  What is the estimated opening > date for the WG Letter Ballot? > > SteveS - what about TG2? > > FWIW I can create a new comment formatting tool & a comment resolution tool > for TG3 & TG4 in a few days (or less) but I need stable fields/records.  The > formatting tool is mutually exclusive from the resolution tool but it is > important to (1) discuss the tools, (2) agree to a format, and (3) keep the > format (comment formatting tool & a comment resolution tool) stable over the > WG Letter Ballot Phase; this way the Balloters will remain loyal :). > > Note 1: After careful review of the (FM Pro5/MS Access), .11, .16 (MS > Word/FM Pro5), .17 (MS Access), and IEEE-SA Ballot Center (PERL script/) > comment formatting tools & a comment resolution tools I still like the ease > of use and sharing that the single TG1 MS Excel comment formatting tool & > comment resolution tool afforded Project   A flatfile approach has > limitiations but we were able to focus on the content vs. a relational DB > tool. > > Note 2: The current generation of IEEE802 comment formatting tool Forms & > DBs drop out text in the input format for the master database... > > TIA, > > -Ian > > Original Message > From: > To: > Cc: > Sent: Friday, November 09, :53 AM > Subject: please post > > > > From: Richard L Alfvin > > > > Hi Ian- > > I'm behind a firewall for the next 6 hours. Can you post this? > > > > On another note, it looks like we need to talk with you as soon as > possible > > about our comment resolution database. We were going to wait until after > > Austin, however anything you can offer up in the interim would be greatly > > appreciated. I believe TG4 will most likely want to use the same tools. > > > > Thanks! > > -RIck > > Forwarded by Richard L Alfvin/484762/EKC on > > 11/09/ :48 AM > > > > > > James D Allen > > 11/09/ :12 AM > > > > To:   Richard L > > cc: > > Subject:  please post > > > > From: James D Allen > > > > (See attached file: 01483r9P802-15_TG3-Running-Minutes-Rolling > > Meadows-to-Austin.doc) > > > > >
Ian Gifford, Consultant
Ian Gifford, Consultant

14. Previous Liaison Reports On Web, Server & Flash Card(s)
July 2001
doc.: IEEE /291r0
March 2001
Previous Liaison Reports On Web, Server & Flash Card(s)
Report #1 -99/005r0 [99005r0P802-15_Liaison-Report.ppt]
Report #2 -99/029r0 [99029r0P802-15_Liaison-Report-2.ppt]
Report #3 -99/063r1 [99063r1P802-15_Liaison-Report-3.ppt]
Report #4 -99/124r0 [99124r0P802-15_Liaison-Report-4.ppt]
Report #5 -99/174r0 [99174r0P802-15_WG-Liaison-Report-5.ppt]
Report #6 -00/037r1 [00037r1P802-15_WG-Liaison-Report-6.ppt]
Report #7 -00/118r0 [00118r1P802-15_WG-Liaison-Report-7.ppt]
Report #8 -00/182r0 [00182r0P802-15_WG-Liaison-Report-8.ppt]
Report #9 -00/266r0 [00266r0P802-15_WG-Liaison-Report-9.ppt]
Report #10 -00/340r2 [00340r2P802-15_WG-Liaison-Report-10.ppt]
Report #11 –01/020r1 [01020r1P802-15_WG-Liaison-Report-11.ppt]
Report #12 –01/112r0 [01112r1P802-15_WG-Liaison-Report-12.ppt]
Report #13 –01/215r0 [01215r0P802-15_WG-Liaison-Report-13.ppt]
Report #14 –01/291r1 [01467r0P802-15_WG-Liaison-Report-15.ppt]
Ian Gifford, Consultant
Ian Gifford, Consultant