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

RE: August 3rd ad hoc on requirements



Reijo,

This is a valid concern. Something like this came up on last week's call. The strategy proposed was to accept requirements at this high level, but structure the work and the implementation of the 802.21 standards such that future needs can be accommodated.

This might involve extensibility and flexibility of the architectural model, proper layering, and transport independence. It might also involve SDOs that want to support the standards authoring their spec.

Regarding guesswork, you are right we cannot guess. Hopefully the liaison effort can be stepped up and we can get requirements from the SDO's.

You intimate that .21 would have greater freedom to support 3GPP by not using Scenarios 4 & 5 as requirements. Can you speculate how would we have more freedom?

Regarding .21  creating a requirement which would then be too burdensome on 3GPP/PP2 in order to conform, your insight is valuable. We need to structure the standard so that doesn't happen. The specific item you raise doesn't appear to be an architectural issue, does it?

Let's add this issue to the ad hoc's agenda, and if not addressed today, then on a subsequent call.

Best Regards,
Michael

-----Original Message-----
From: ext Reijo Salminen [mailto:reijo.salminen@seesta.com]
Sent: Tuesday, August 03, 2004 1:15 AM
To: Williams Michael.G (Nokia-ES/MtView); STDS-802-21@listserv.ieee.org
Subject: RE: August 3rd ad hoc on requirements


Greetings,

Comment 1 on chapter 5.2 on rev 6 requirement document:

The following text:

"The 802.21 standard shall facilitate handover scenarios related to
WLAN-cellular inter-working as specified by Scenarios 4 and 5 in 3GPP
standard."

Shall be removed.

Reason: It is a major architectural requirement, which forces the proposals
to guess how the 3GPP release 7 (in which the scenarios 4 and 5 are possible
candidates) might solve the problem. This is not feasible on the current
802.21 timeframe.

Further information: If the 802.11/15/16/(20?) AP:s are connected to
cellular system's BSCs/RNCs, which possibly is the consequence of the
scenarios 4 and 5 which must be expanded to all the 802 systems that 802.21
should cover, it means considerable additions on the above mentioned
cellular system nodes. By removing the above mentioned text, the proposals
will have more freedom how to solve the interoperability between 802 and
cellular systems. When the 802.21 proposals are available for evaluation, it
is possibly also better known also within the 802.21 into which direction
the 3GPP is moving on the scenarios 4 and 5, and thus the evaluation process
can take that information also into account.


Best Regards, Reijo Salminen, Ab Seesta Oy


-----Original Message-----
From: owner-stds-802-21@listserv.ieee.org
[mailto:owner-stds-802-21@listserv.ieee.org] On Behalf Of
Michael.G.Williams@NOKIA.COM
Sent: 3. elokuuta 2004 8:03
To: STDS-802-21@listserv.ieee.org
Subject: August 3rd ad hoc on requirements

Greetings everyone,

Tuesday August 3rd
Call at 9AM-11AM Pacific ******** NEW TIME 2hrs later ***********
IEEE 802.21 conf call info:
DIAL-IN NUMBERS & PASSCODES:
Toll Numbers:   USA     1-210-280-7160
Participant Passcode:   313495

Agenda:
- Roll Call
- Requirements Review (Please review the latest doc, rev 6 sent to list via
ZIP  7/29/2004)
        - Peretz Feder input (completed from 7/27/2004 ZIP comments, also
5/13 comments?)
        - Eric Njedjou (emailed to list inline 7/26/2004)
        - Mahalingam Mani input (emailed to list .doc referring to rev 5 on
7/25/2004)
        - Ajay Rajkumar's input (emailed as .doc referring to rev 6 on
8/2/2004)
        - (Note to editor, submission 115 from last meeting was accepted but
perhaps not incorporated?)
- Next Steps (Call for Proposals)

We will continue to focus on architecturally significant requirements. All
are encouraged to focus on adding value to the  standard as first priority.


Looking forward to speaking with you soon,
Michael Williams
IEEE 802.21 Vice Chair