[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re:stds-802-16: SYSREQ: Iissues for debate and discussion at

To: <Brian_Petry@3com.com>, <stds-802-16@ieee.org>
Subject: Re:stds-802-16: SYSREQ: Iissues for debate and discussion at
From: Steve.Farrell@stelhq.com
Date: Thu, 06 May 1999 12:36:23 -0700
Sender: owner-stds-802-16@majordomo.ieee.org

Hi Brian,

I will not be present for the entire 3 days, more likely, I will be there only
on Tuesday, as such, I am not preparing any presentation material, but I would
be happy to speak up and give my informal opinion, if necessary, which is
basically consistent with David Jarrett's opinion, simply put:

    1-the standards group needs to define the applications first--that will
drive system req's, which will drive architecture, etc.

    2-the applications needed today (I my humble opinion and per my experience
in dealing with the LMDS auction winners and in dealing with our partner
Newbridge) is that the LMDS operators are telco focused and want "telcoish"
applications as well as high speed internet.

These are my only two points.  Whether or not this will change over time and
whether or not IP can handle these services are subject to debate.  I am not
trying to say anything else but (1) and (2) above.  I will be happy to speak up
about my opinion if needed.

Thanks and see you on Tues.

Steve Farrell
Product Marketing Manager
Stanford Wireless Broadband Inc.
1221 Crossman Avenue
Sunnyvale, CA  94089-1117
phone:  408-745-2530
fax:    408-745-2673
steve.farrell@stelhq.com


____________________Reply Separator____________________
Subject:    stds-802-16: SYSREQ: Iissues for debate and discussion at 5/
Author: <Brian_Petry@3com.com>
Date:       5/4/99 5:32 PM

[Notice: It is the policy of 802.16 to treat messages posted here as
non-confidential.]



Hello all,

As editor for our System Requirements document, I am proposing some discussion
items for the Boulder meetings so that we can reach consensus on some of the
issues for system requirements.  After reviewing the email discussions and
looking at the outline proposals for a document, I have come up with the
following issues.  For these issues, if you have a specific point of view, I
urge you to participate in Boulder by presenting your views to the group so
that we can discuss them.

If you like, please contact Roger Marks (r.b.marks@ieee.org) to get a spot on
the agenda.  I think the Boulder meetings will focus mainly on coexistence
issues, but it would be great if we could discuss system requirements issues
as well.

[I am going to name some names in the following paragraphs in hopes that it
provokes the named people to present their valuable experience and opinions.
I appologize if I have "pigeon-holed" anyone into a certain camp, but I am
just trying to provoke discussions.]

ATM vs. IP
        I saw two, maybe three points of view here.  If I may, let me
        summarize them:

        1) Must support ATM, perhaps because existing products and system use
           ATM and telco-ish carriers like ATM

           I saw interesting comments from: Steve Farrell and David
           Jarrett--maybe you could come prepared with a short presentation on
           your point of view.  Examples of existing systems that rely on ATM
           would be particularly useful.

        2) Should focus on IP, perhaps because MAC is more efficient, market
           reality is migrating to IP, 802.14 experience

           Comments from Chet Shirali, Jack Fijolek, Jim Mollenauer, Marianna
           Goldhammer were interesting; Imed Frigui (VC from 802.14)
           summarized 802.14's status

           It would be great if any of you came prepared with your points of
           view, supporting IP (or variable-length-frame)-centric approach.

        3) Should support both ATM and IP

           Comments from Jay Klein, Jim Mollenauer, David Jarrent and Peter
           Ecclesine seemed to support an agnostic approach.  Also, an article
           from Jan/Feb of IEEE Network was mentioned.

ATM vs. IP as it relates to QoS

        I sense a general agreement that we want QoS guarantees for telephony,
        videophony, and maybe video broadcast services.  If anyone has
        anything particular to present at the Boulder meeting, I think that
        would be helpful.

TDD vs FDD

        Although I did not see any discussion on the list regarding TDD vs
        FDD, and it may be more of a coexistence issue, I think the group
        would like to see a presentation to make the case for either TDD or
        FDD.  Are there any "system issues" we should consider?

Reference Diagram

        I saw some good comments regarding the reference diagram.  If
        Margarete Ralston (who drew up the proposal that was discussed
        on the list), or anyone else has a new or updated proposal, that would
        be great.

We have a "functional requirements" proposal from Jim Mollenauer.  I didn't
see any comments on it.  Does that mean we all agree with the content?

Nit-Picky Things

        We have two proposals for a system requirements outline, one from the
        task group's work in Austin and another from a group of people
        submitted by Gene Robinson.  There are some inconsistencies between
        the two:

        1) The title.  What should it be?  Should the System Requirements
           task group focus on one document?  I think some people want
           two documents: a "functional requirements" document and a
           "system requirements" document.  Could someone (Gene Robinson?)
           please explain the difference so we can figure out if we need to
           produce two documents?

        2) I thought we decided in Austin to leave out PHY specifics such as
           bps/HZ, modulation approaches, etc.

        3) The section "Layer Management" in 802.16sc-99/6 (submitted by
           Gene) I think defines and describes layer management incorrectly.
           It should describe network management objects, not generic protocol
           layering.

        4) 802.16sc-99/6 (from Gene) and 802.16sc-99/1 (from Austin) are
           outlines that do not "match up" insofar as the various section
           heading titles, order of sections, added sections and omitted
           sections.  I think the authors of 802.16sc-99/6 should be prepared
           to explain why their outline is different from our Austin outline.

Best Regards, and see you in Boulder...

Brian Petry

From: Brian_Petry@3com.com
To: stds-802-16@ieee.org
Message-Id: <88256768.00034532.00@hqoutbound.ops.3com.com>
Date: Tue, 4 May 1999 17:32:18 -0700
Subject: stds-802-16: SYSREQ: Iissues for debate and discussion at 5/99 Boulder meeting
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-stds-802-16@majordomo.ieee.org
Precedence: bulk

Prev by Date: RE: stds-802-16: updated Liaison report from ITU-R 8A/9B
Next by Date: Re: stds-802-16: SYSREQ: Iissues for debate and discussion at 5/99 Boulder meeting
Prev by thread: RE: stds-802-16: updated Liaison report from ITU-R 8A/9B
Next by thread: stds-802-16: SYSREQ: 2 Contributions (Boulder agenda and ITU-R requirements bullets)
Index(es):
- Date
- Thread