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

[STDS-802-16] [802.16p][DEV RG] Group ID to support different applications

To: STDS-802-16@LISTSERV.IEEE.ORG
Subject: [STDS-802-16] [802.16p][DEV RG] Group ID to support different applications
From: Kaushik Josiam <kjosiam@STA.SAMSUNG.COM>
Date: Wed, 9 Feb 2011 14:29:23 -0600
Delivered-to: mhonarc@GROUPER.IEEE.ORG
List-help: <http://listserv.ieee.org/cgi-bin/wa?LIST=STDS-802-16>, <mailto:LISTSERV@LISTSERV.IEEE.ORG?body=INFO%20STDS-802-16>
List-owner: <mailto:STDS-802-16-request@LISTSERV.IEEE.ORG>
List-subscribe: <mailto:STDS-802-16-subscribe-request@LISTSERV.IEEE.ORG>
List-unsubscribe: <mailto:STDS-802-16-unsubscribe-request@LISTSERV.IEEE.ORG>
Reply-to: Kaushik Josiam <kjosiam@STA.SAMSUNG.COM>
Thread-index: AcvImAm4hqo/raBWQ+W5l7Tw5kiFpQ==
Thread-topic: [802.16p][DEV RG] Group ID to support different applications

Dear 16p members,

Two contributions C0006 and C0012 defined the concept of a group ID addressing different applications. Please respond to this email thread to voice your thoughts. In particular, we are looking for your inputs on the following:

1. Is a Group ID necessary to be defined for M2M devices?

2. What applications would use a group ID?

3. What are the characteristics of a group ID? (For ex: is it a network specific ID?)

4. What is the size of the proposed group ID?

If you have any other thoughts, proposals or questions, please respond to this thread.

Regards

Kaushik & Ming-Hung

DEV RG Chairs

Prev by Date: [STDS-802-16] [802.16p][DEV-RG] - Email Discussion on M2M device identification
Next by Date: Re: [STDS-802-16] [802.16p] DEV RG Conference Call Materials
Previous by thread: Re: [STDS-802-16] Coordination of P1900.7 draft PAR
Next by thread: Re: [STDS-802-16] [802.16p][DEV RG] Group ID to support different applications
Index(es):
- Date
- Thread