| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Dear all, Thank you very much for all the contributions. Agenda slides are updated/uploaded (PPC-HN802_16_PPC_Adhoc_CC1_r2.ppt) to include discussion schedules for submitted contributions. See you soon. Best Regards. Inuk Jung. From: Feder, Peretz (Peretz) [mailto:peretz.feder@ALCATEL-LUCENT.COM] Inuk: Here are the links to the new 72 and 73 contributions: http://dot16.org/ul//upload/temp_db/C80216ppc-10_0072r3.doc http://dot16.org/ul//upload/temp_db/C80216ppc-10_0073r3.doc Peretz Feder From: Feder, Peretz (Peretz) Also Inuk: Taipei contributions 71, 72, and 73 (which ALU is a co author) are supposed to be further discussed tonight. I have uploaded updated version of contribution 71, with changes reflecting agreement reached with Intel. I have also uploaded 72r2 and 73r2. This revised contribution is submitted as a joint Telecordia, Intel, ALU contributions for tonight. With agreed 71r2, it will enable us to move quickly and avoid the contentious ORAT vs. MIH discussion all together. http://dot16.org/ul//upload/temp_db/C80216ppc-10_0071r2.doc See you later, Peretz Feder From: Inuk Jung [mailto:inuk.jung@lge.com] Dear Peretz, Thank you for your correction. I’ll update the latest SR as suggested and will upload it to the ‘temp’ folder. Best Regards. Inuk Jung. From: Feder, Peretz (Peretz) [mailto:peretz.feder@ALCATEL-LUCENT.COM] Dear Inuk: If you want to approve 0008r3, the editor first needs to follow the instructions captured by the Vice Chair at the closing meeting - slide 18: • Editorial instructions: – Remove the items highlighted in yellow from the ad-hoc output report. – Replace “GLL” in Figures 7 and 8 with “?” Thanks much, Peretz Feder From: Inuk Jung [mailto:inuk.jung@LGE.COM] Dear PPC HN members, This is a notice of the bridge information and agenda for CC#1. The agenda is as follows: - Sharing opinions & Discussing on interworking scenarios and methodologies (e.g., C-AP, MIH, O-RAT) for further understanding and building consensus - Comments and suggested amendments on the current Study report, which can be found at IEEE 802.16ppc-10/0008r3 The main goal of CC#1 is to have discussion on interworking technology, for hope of some consensus, which will allow us to propose further (detailed) interworking technologies (refer to slides 4 and 5). For efficient discussion, please review the presentation slide, uploaded at http://dot16.org/ul//upload/temp_db/PPC-HN802_16_PPC_Adhoc_CC1.ppt, and share views or supporting contributions till 16th Feb. We may use the ‘tmp’ upload directory for submitting the contributions at http://dot16.org/ul/ul.cgi?command=viewupload&database=temp_db. For each contribution or email discussion, please name the file or subject of an e-mail with the header code [PPC-HN]. The bridge information for the first HN conference call on 17th Feb is give below. The detail information of the meeting are as follows: Topic: PPC HN Conference call Date: Thursday, February 17, 2011 Time: 6:00pm, PST or 11:00am, Korea Time Meeting Number: 860 005 052 Meeting Password: hnconf Dial in Number(s) Local: 1644-2501 Global: +82 (31) 810-3013 (*I apologize that we only have a Korean international phone number available.) Participant Code: 414981# ------------------------------------------------------- To start the online meeting------------------------------------------------------- 1. Go to https://kobiz.webex.com/kobiz-en/j.php?ED=152335347&UID=481581432&PW=NYzBjMjY3YTcz&RT=MiM1MA%3D%3D 2. If you are participant please click on the “join as a participant” link in the website above To check whether you have the appropriate players installed for UCF (Universal Communications Format) rich media files, go to https://kobiz.webex.com/kobiz-en/systemdiagnosis.php IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. You should inform all meeting attendees prior to recording if you intend to record the meeting. Please note that any such recordings may be subject to discovery in the event of litigation. |