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

stds-802-16:SYSREQ COMMENTS

I an even dozen late breaking comments on the Draft 2 of the document.  I
hope that we will have time on the agenda to cover them, given they are
after the deadline.  

DWJ

  <<DWJP8L6.txt>>  <<DWJ_P6L37.txt>>  <<DWJ_P7L5.txt>>  <<DWJ_P8L29.txt>>  
<<DWJP17L32.txt>>  <<DWJP18L2.txt>>  <<DWJP25L6.txt>>  <<DWJP25L26.txt>>  
<<DWJP25L35.txt>>  <<DWJP11L12.txt>>  <<DWJP22L14txt.txt>>  
<<DWJ_P6L30.txt>> 

-- 
-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



[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]
Insert a bullet:

* Timing - (Fractional) DS1/E1 services require timing to be delivered from the network to the end user's equipment, whether the timing is synchronous with the network (i.e., based on the serving network's clock) or asynchronous with the network (based on a clock other than the serving network's clock).  For synchronous timing, the timing source shall be traceable to a Primary Reference Source (PRS).  For asynchronous timing, the timing on the circuits at the output of the access network shall be +/- 150 ppm for DS1 (ANSI T1.403-1995) and +/- 50 ppm for E1 (ITU-T G.703).  Note that the DS1 spec is relaxed for older equipment; newer equipment can meet the more stringent +/- 32 ppm spec.  In either case, DS1s carried over the acccess network shall have jitter and wander characteristics as specified in ITU-T G.823, and E1s as specified in G.824.  

[Reason for Edit]
Timing is a necessary function for these circuit service.  
[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
6

[Starting Line #]
37

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

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

[Reason for Edit]
The digital telephony section does not need to address ATM in general.  
[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
7

[Starting Line #]
5

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

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

[Reason for Edit]
The digital telephony section does not need to address ATM in general.  
[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
8

[Starting Line #]
29

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

[Detailed Description of Proposed Insertion, Deletion, Change]
Remove text beginning with "Although few ATM networks ..." until the end of the paragraph.  

[Reason for Edit]
This text is opinion and does not place any requirements.  
[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
17

[Starting Line #]
32

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

[Detailed Description of Proposed Insertion, Deletion, Change]
Change to the following

"... receive adequate power 100% of the time and not counting equipment availability."  

[Reason for Edit]
Equipment availability will also impact overall link availability.  It should be clear that this specification only covers impacts on availability due to propagation effects.  
[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
18

[Starting Line #]
2

[(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 this paragraph:

"The 802.16 specifications shall not preclude the ability of the radio link to be engineered for different link availabilities, based on the preference of the system operator."  

[Reason for Edit]
The 802.16 specifications should not take away any deployment flexibility from the system operator.    
[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
25

[Starting Line #]
6

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

[Detailed Description of Proposed Insertion, Deletion, Change]
Change to 

"The 802.16 MAC supports 802 "universal" 48 bit addresses."

[Reason for Edit]
Should not limit the 802.16 MAC to 6 Byte addresses - we should have the flexibility to specify a more byte efficient address for the MAC layer.  
[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
25

[Starting Line #]
26-33

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

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

[Reason for Edit]
Should not limit the 802.16 MAC to IEEE 6 Byte addresses - we should have the flexibility to specify a more byte efficient address for the MAC layer.  Then, each over-riding service will have its address space converged to the MAC layer address.  
[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
25

[Starting Line #]
35

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

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

[Reason for Edit]
Should not limit the 802.16 MAC primitives to those for 802.2, since the latter do not have any support for timing or priority which are both needed in 802.16.  In addition, other 802 MAC layers (e.g., 802.6, 802.9) already support an expanded set of MAC primitives.  
[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
11

[Starting Line #]
12

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

[Detailed Description of Proposed Insertion, Deletion, Change]
Change text to 

"... vicinity around 30 GHz, but possibly in the range from 10 GHz to 66 GHz, to connect a ..."

[Reason for Edit]
The Interoperability PAR mentions that this work "applies to systems operating in the vicinity of 30 GHz but is broadly applicable to systems operating between 10 and 66 GHz."  The System Requirements should be consistent. 
 

[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
22

[Starting Line #]
14

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

[Detailed Description of Proposed Insertion, Deletion, Change]
Change text to 

"Minimum Cell Rate (MCR).  The minimum cell rate supported by a connection (applies to ABR service only).  

[Reason for Edit]
The definition of MCR contained currently is not correct.   

[Submitter's Last Name]
Jarrett

[Submitter's First Name]
David

[Starting Page #]
6

[Starting Line #]
30

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

[Detailed Description of Proposed Insertion, Deletion, Change]
Replace current lines 30-35 with:

Note that many forms of digital telephony are possible:

* Narrowband/Voice Frequency Telephony - POTS (supporting FAX services), Centrex, ISDN BRI
* NxDSO Trunking - Fractional DS1/E1 to PBXs and/or data equipment, ISDN PRI
* Full DS1/E1 - transparent mapping including all framing information

[Reason for Edit]
So that this section will completely reflect the types of digital telephony that an 802.16 can carry.