Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [STDS-802-16] [PPC-HN] Agenda and Bridge information for CC#1



Dear Inuk and all,

Thanks for all the discussions.

10 PM PST is mid-night CST. Although it is a little better than in EST, it is not a good time for folks in Central Time zone USA either.

Thanks and best regards,

Ying

 

Ying Li (PhD)

Standards Research Laboratory

Samsung Telecommunications America

yli2@sta.samsung.com

http://www.samsungtelecom.com/StandardsResLab/

 

From: Feder, Peretz (Peretz) [mailto:peretz.feder@ALCATEL-LUCENT.COM]
Sent: Monday, February 14, 2011 10:35 AM
To: STDS-802-16@LISTSERV.IEEE.ORG
Subject: Re: [STDS-802-16] [PPC-HN] Agenda and Bridge information for CC#1

 

 

Dear Inuk:

 

10 PM PST is 1:00 AM EST.

 

How long do you want to run the 1:00 AM EST meeting?

 

Needless to say, this is not a good time for folks in the East Coast.

 

Peretz Feder

 


From: Inuk Jung [mailto:inuk.jung@LGE.COM]
Sent: Monday, February 14, 2011 5:26 AM
To: STDS-802-16@LISTSERV.IEEE.ORG
Subject: Re: [STDS-802-16] [PPC-HN] Agenda and Bridge information for CC#1

 

Dear Vladimir,

 

Im very sorry that the time we have set is a very late one for you.

The time has been agreed to be okay to the members who attended the PPC-HN session during the previous meeting #71.

Would you be so kind to let us know what time would be okay to participate the CC? (tentatively would 10PM PST be okay?)

I think a change of time for the 1st CC need to be confirmed by other members, which Im not sure it would be possible till the CC. Hence, Id like to proceed the 1st CC as announced and will ask members for a change of time during the adhoc for the upcoming CCs (considering the suitable time you give us).

Ill announce the minutes of discussion for every adhoc meting, so to make sure you are not missing much.

 

However, if all members are okay with changing time to 10PM Feb.17th PST, Ill announce the new CC information. If no notice is made, the CC#1 will proceed as announced. Please reply to me with your preference.

 

Also, Vladimir kindly corrected the Korean time, which should be 11AM, 18th Feb. PST time remains the same, 6PM, 17th Feb PST.

 

Best Regards.

Inuk Jung.

 

From: Vladimir Yanover [mailto:vladimir.yanover@ALVARION.COM]
Sent: Monday, February 14, 2011 4:51 PM
To: STDS-802-16@LISTSERV.IEEE.ORG
Subject: Re: [STDS-802-16] [PPC-HN] Agenda and Bridge information for CC#1

 

Dear Inuk,

It is 4am in Israel and 3am in Europe which I think is a bit too early. Can you please reschedule the call to more convenient time?

Thanks

Vladimir

 

From: Inuk Jung [mailto:inuk.jung@LGE.COM]
Sent: Monday, February 14, 2011 9:29 AM
To: STDS-802-16@LISTSERV.IEEE.ORG
Subject: [STDS-802-16] [PPC-HN] Agenda and Bridge information for CC#1

 

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 February 18th 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.

 



************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses(190).
************************************************************************************


************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses(42).
************************************************************************************



************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses(42).
************************************************************************************