stds-802-16: SYSREQ COMMENT:

["Jarrett, David (David)" <djarrett@lucent.com>]

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

I have attached 48 comments on the R4 of the System Requirements Document,
for consideration at the next System Requirements Task Group Meeting.  I
have put these in one e-mail to avoid spamming everyone's systems with 48
separate ones.  Although the editor requested that e-mail submissions be
line-wrapped to 80 characters, my e-mail system does not seem to support
that, so I hope everyone's e-mail reader can wrap text.  

I also have a PowerPoint picture for the comments on Line 12, Page 1.  I
believe the text comments capture all of what the picture shows, but I will
post the picture to the reflector separately with the editor's permission.  

DWJ


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
1

[Starting Line #]
38

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Change the second sentence as follows:

"One implementation may include the item because the target marketplace
requires it or because it enhances the product for example, another
implementation may omit the same item."

[Reason for Edit]
To place the emphasis on the implementation and not the vendor.  A specific
vendor may have many different implementations.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
1

[Starting Line #]
44

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Change clause starting with "in which as least two .." as follows:

"... in which at least one STS communicates with a BTS via  ..."

[Reason for Edit]
To clarify the types of stations communicating, and to clarify that more
than one STS may be part of the system.  Note that terms STS and BTS need to
be synchronized with the new terminology from the Terminology ad hoc group.



[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
1

[Starting Line #]
44

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Remove clause "the interfaces to external networks," from the sentence

[Reason for Edit]
The definition of an 802.16 System for the purposes of the Systems
Requirements document should not include the external interfaces, since we
will not specify them.  Rather, we will specify the bearer services to be
transported by the MAC and PHY layers, as well as internal aspects of the
system.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
2

[Starting Line #]
8

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Remove the clause "interfaces immediately surrounding an 802.16 system,
particularly"

[Reason for Edit]
The definition of an 802.16 System for the purposes of the Systems
Requirements document should not include the external interfaces, since we
will not specify them.  Rather, we will specify the bearer services to be
transported by the MAC and PHY layers, as well as internal aspects of the
system.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
3

[Starting Line #]
26

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Reword first sentence as follows:

"This section describes the bearer services that an 802.16 system at least
SHOULD support (some services are MUST be supported)."  

[Reason for Edit]
To clarify that some services will be required to be supported by the MAC
and PHY layers.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
3

[Starting Line #]
42

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Remove the clause "and aggregated telephony-oriented connections (e.g., T1,
E1, ISDN-PRI, etc.)" and replace with

", legacy TDM digital transmission systems (e.g., Full and Fractional T1 and
E1, etc.),"

[Reason for Edit]
To clarify the wording.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
4

[Starting Line #]
2

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Replace "SHALL" with "MAY" and also remove clause "when technology permits."


[Reason for Edit]
We probably don't want to have requirements that cannot yet be fulfilled, or
any requirement for residential services in general.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
4

[Starting Line #]
11

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Change "SHOULD" to "MUST not preclude"

[Reason for Edit]
The _requirements_ shouldn't preclude this, but the requirements don't need
to address it more directly.   


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
5

[Starting Line #]
14

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Inset the word "all" between "consider" and "the bearer services"

[Reason for Edit]
Should consider all services, whether required to be supported directly of
not.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
5

[Starting Line #]
26

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Change "SHOULD" to "MAY"

[Reason for Edit]
To make direct support for digital telephony in the MAC optional


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
6

[Starting Line #]
8

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Change "Voice Telephony over ATM (VtoA)" to "Voice and Telephony over ATM
(VTOA)"

[Reason for Edit]
Consistency with the relevant standards/specifications.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
6

[Starting Line #]
11

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Insert the following sentence:

"802.16 systems and protocols MUST support the QoS requirements of these
services, as defined in Section 6."  

[Reason for Edit]
Although digital telephony is optional to be supported directly by the MAC
and PHY, the MAC and PHY must support the needed QoS to be able to support
these services indirectly.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
6

[Starting Line #]
13

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Change "an 802.16 system" to "the PSTN and/or a private trunking network"

[Reason for Edit]
Clarify what 802.16 systems are connecting.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
6

[Starting Line #]
34

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Insert "and the D channel" between "channels" and "active," and change "128"
to "144"

[Reason for Edit]
Clarify the full bandwidth for ISDN BRI. 


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
6

[Starting Line #]
40

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Insert "(as specified in Section 6)" between "certain level" and "to
support."  Also, Replace next sentence with "The specific amount of delay
SHOULD be variable based on the quality of service sold to the end user."

[Reason for Edit]
To clarify requirements for maximum delay, and configurable delay in
implementations.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
7

[Starting Line #]
1

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Replace "can be varied" with "SHOULD be variable"

[Reason for Edit]
Clarify requirements terminology.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
7

[Starting Line #]
34

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Replace "SHOULD" with "MUST"

[Reason for Edit]
Consistent with previous comments that must support transport requirements
(QoS) for digital telephony.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
7

[Starting Line #]
38

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Delete first sentence ("Of high-speed ...").  Also, in next sentence change
"routed" to "switched."  

[Reason for Edit]
Sentence adds no value to the requirements.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
7

[Starting Line #]
44

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Change first sentence to "802.16 protocols MUST directly transport ATM Cell
Relay Service efficiently and preserve its QoS features (see Section 6)."
Also, remove the second sentence ("Thus, 802.16 systems ...").  

[Reason for Edit]
Clarify the level of support for ATM services for the MAC/PHY work.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
8

[Starting Line #]
6

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Change "may" to "SHOULD"

[Reason for Edit]
Need more stringent requirement for ATM signaling support.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
8

[Starting Line #]
14

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Insert work "directly" after "MUST"

[Reason for Edit]
To clarify that MAC should directly carry IP.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
8

[Starting Line #]
36

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Change "SHALL" to "MAY" and insert at end of sentence the phrase ", whether
directly or indirectly."  

[Reason for Edit]
To clarify that Bridged LAN service support is optional, and may not
necessarily be support directly by the MAC.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
9

[Starting Line #]
10

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Change "SHOULD not" to "is not expected to"
Also on next line, change "SHOULD" to "is expected to"

[Reason for Edit]
By definition, services in section 2.2.6 should have have any explicit
requirements.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
9

[Starting Line #]
19

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Add the following text:

"The 802.16 protocols SHOULD not preclude the transport of the above
mentioned services."  

[Reason for Edit]
To clarify level of support for the services in this section.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
9

[Starting Line #]
27

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Change part of the sentence starting with "in which at least two ..." to:

"in which at least one STS communicates with a BTS via a radio air
interface, and services transported by the MAC and PHY protocols."  

[Reason for Edit]
Consistent with comments on P1L44, make clear that at least one STS is
communicating with a BTS, and that 802.16 system does not include interfaces
to external network elements.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
9

[Starting Line #]
34

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Change "around 30 GHz" to "in the above range"

[Reason for Edit]
To make consistent with previous statements.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
9

[Starting Line #]
37

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Remove work "generally"

[Reason for Edit]
Not clear to have a requirement that applies in general.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
10

[Starting Line #]
15

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Change"may" to "will likely"

[Reason for Edit]
May implies an option, which does not appear to be what is meant here.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
11

[Starting Line #]
5

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Remove text up to line 7 "the time being"

[Reason for Edit]
Removed text does not add to the requirements statements.  


[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
12

[Starting Line #]
1

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Want to change the figure as follows:

- Remove terms SNI and BNI, as these conflict with definitions in ETSI BRAN
(what we call BNI, they call SNI!). 
- Add multiple STS
- Add the following nodes inside the STS box, connected together, from left
to right:
	- Service IWF
	- 802.16 MAC
	- 802.16 PHY
- Give examples of the types of interfaces that might connect from the
Subscriber Network to the Service IWF (10/100 Base T, Twisted Pair, DS1/E1,
...)
- In at least one of the STS boxes, show that Digital Audio/Video multicast
service will connect directly from the Service IWF to the 802.16 PHY
- In the BTS box, show the following nodes, connected together, from left to
right:
	- 802.16 PHY
	- 802.16 MAC
	- Service IWF
	- Air Interface Control (above and connected to the PHY and MAC)
	- Management Agent (below and connected to the PHY and MAC)
- Show a cloud for a Management Network below the BTS box, connected to the
Management Agent in the BTS, and with an EMS box connected to the cloud
- Show the Core Network as a cloud connected to the Service IWF in the BTS,
with output interfaces from the cloud leading to PSTN, Intranet/VPN,
Internet, and Video Distribution Headend
- Use the term "802.16 Air Interface"
- Show the repeater in a box
- Use some representation for an antenna (e.g., a half-oval) from the STS,
BTS, and Repeater towards the 802.16 Air Interface

[Reason for Edit]
To ajust the figure to more closely reflect the recent agreements on the
definition of an 802.16 System.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
12

[Starting Line #]
18

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Remove entire paragraph

[Reason for Edit]
Text is not relevant to the requirements statements.  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
13

[Starting Line #]
26

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Replace sentence with "This protocol stack model is intended to help develop
terminology, and possibly protocol architecture."  

[Reason for Edit]
Removes unnecessary text, and removes the word "should" which is to be used
to imply requirements (which this is not).  


[Submitter's Last Name] 
Jarrett

[Submitter's First Name]
David

[Starting Page #]
15

[Starting Line #]
3

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Remove rest of paragraph beginning with "For instance, large ..."  Replace
with the following:

"The following scales of capacity SHALL be supported:

* Dedicating an all the bandwidth from a single BTS channel to a single
subscriber.  
* Assigning bandwidth to a collection of STS'es communicating with a
particular BTS channel such that their aggregate peak bandwidth exceeds the
rate that a single BTS channel can support (i.e., link overprovisioning).  
* Assigning as little as 1% of the bandwidth of the link from a BTS channel
to an STS
* Provisioning "pico-systems" in dense metropolitan areas [6] that implement
short-radius beams to a few subscribers."

[Reason for Edit]
To clarify exactly what scalability is required, for both bandwith per user
and type of link.  


[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
15

[Starting Line #]
14

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Change first sentence to:

"802.16 protocols SHALL be optimized to provide the peak per-user capacity
from 2 to 155 Mbps to an STS sufficiently close to the BTS."  

[Reason for Edit]
The current text has no requirement statement.  


[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
15

[Starting Line #]
16

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Add to the end of the paragraph:

"However, 802.16 protocols SHALL not preclude the ability of an 802.16
system to deliver less than 2 Mbps peak per-user capacity." 

[Reason for Edit]
To further clarify the bandwidth ranges 802.16 protocols should support.  


[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
16

[Starting Line #]
23

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Move this paragraph to after line 8.

[Reason for Edit]
Since the paragraphs at line 5 and line 23 both discuss error performance,
they should be kept together.  


[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
16

[Starting Line #]
35

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Remove entire paragraph

[Reason for Edit]
This does not add much to the requirements, and will be addressed in Section
6.  


[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
17

[Starting Line #]
8

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Remove entire line/sentence.  

[Reason for Edit]
Does not add to the requirements statements.  


[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
18

[Starting Line #]
42

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Change to "... bearer services with respect to allocation and prioritization
of bandwidth."  

[Reason for Edit]
To clarify the wording.  


[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
19

[Starting Line #]
1

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Change "fixed" to "constant rate"

[Reason for Edit]
To clarify the wording


[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
19

[Starting Line #]
4

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Remove the word "Permanent" and the letter "P" from "PVC"

[Reason for Edit]
To clarify that connections can be any type of VC (PVC, SVC, SPVC, ...)


[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
21

[Starting Line #]
33

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Remove sentence starting "The 802.16 standards SHALL ..."

[Reason for Edit]
Not useful to have a requirement to consider something.  


[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
21

[Starting Line #]
39

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Add to the section title "or BTS"

[Reason for Edit]
To increase the scope of the section.  


[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
21

[Starting Line #]
40

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Change "from the BTS" to "remote from the STS"

[Reason for Edit]
Should not need to be at the BTS to do this.  


[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
21

[Starting Line #]
41

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Add after current text:

"The operator also MUST have the means to shut down a BTS remotely.  The
802.16 protocols SHOULD support that transmission from an STS or BTS be shut
down automotically in case of malfunction (e.g., power exceeds limits)."   

[Reason for Edit]
To add necessary requirements for malfunction handling.  


[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
23

[Starting Line #]
40

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Should not accept the addition of the proposed text to the System
Requirements document, because the items contained either 1) are already
addressed elsewhere, 2) should be addressed in other sections if not already
addressed, or 3) should be in the MAC specification.  The following are
specific text edits:

- Remove 10.0
- Remove 10.1 -10.3 (should be addressed in MAC specification)
- Remove 10.4 (already address in Section 4.0 where appropriate)
- Remove 10.5 (shold go into a new section 7.4 with specific parameters to
be monitored and tracked in the MIB)

[Reason for Edit]
To address this defered contribution


[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
24

[Starting Line #]
33

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Remove the definition of BNI

[Reason for Edit]
Not necessary, since the System Requirements should not discuss these
interfaces.  


[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
25

[Starting Line #]
40

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Remove definition of SNI

[Reason for Edit]
Not necessary, since the Systems Requirements should not discuss these
interfaces.  

-- 
-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-
David W. Jarrett		Lucent Technologies
Voice: 1-408-952-7452	Wireless Broadband Networks Division
Pager: 1-888-876-0854	890 Tasman Drive 
Fax: 1-408-952-7456	M/S 08-09
E-mail: djarrett@lucent.com	Milpitas, CA 95035-7912