[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
stds-802-16: TG1 COMMENTS

To: "'stds-802-16@ieee.org'" <stds-802-16@ieee.org>
Subject: stds-802-16: TG1 COMMENTS
From: Ken Stanwood <ken@ensemblecom.com>
Date: Thu, 26 Oct 2000 20:39:23 -0700
Sender: owner-stds-802-16@ieee.org

[Submitter's Last Name] 
Stanwood

[Submitter's First Name]
Ken

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
137

[Starting Line #]
62

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Change both occurrences of "channel ID" with "upstream channel ID"

[Reason for Edit]
clarity

[Submitter's Last Name] 
Stanwood

[Submitter's First Name]
Ken

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
137

[Starting Line #]
62

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
change "fromUCD" to "from UCD"

[Reason for Edit]
typo

[Submitter's Last Name] 
Stanwood

[Submitter's First Name]
Ken

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
141

[Starting Line #]
26

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Change "'s" to "SS's"

[Reason for Edit]
typo

[Submitter's Last Name] 
Stanwood

[Submitter's First Name]
Ken

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
141

[Starting Line #]
33

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Change "Physical" to "Uplink"

[Reason for Edit]
typo

[Submitter's Last Name] 
Stanwood

[Submitter's First Name]
Ken

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
142

[Starting Line #]
11

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Change "successfully ranged," to "successfully ranged (Ranging request is
within tolerance of the BS),"

Remove first sentence on page 143.

[Reason for Edit]
Somehow the idea ended up out of context on the next page.

[Submitter's Last Name] 
Stanwood

[Submitter's First Name]
Ken

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
144

[Starting Line #]
1

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Combine the figures on page 144 and 145 and correct them.

[Reason for Edit]
They have situations where power is adjusted more often than it should be
and where fewer retries happen than should.  They also have redundant
sections.

[Submitter's Last Name] 
Stanwood

[Submitter's First Name]
Ken

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
146

[Starting Line #]
1

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
This drawing needs redrawn in a maintainable format rather than patched in
Framemaker.  This applies to all patched drawings.

[Reason for Edit]
It looks bad where patched.  Note 1 and 2 appear out of context and
unlabeled on the next page.

[Submitter's Last Name] 
Stanwood

[Submitter's First Name]
Ken

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
147

[Starting Line #]
12

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
replace "an" with "a".

[Reason for Edit]
typo

[Submitter's Last Name] 
Stanwood

[Submitter's First Name]
Ken

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
147

[Starting Line #]
36

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
This should happen on the secondary management CID. So should all the
actions through section 2.11.9.2.

[Reason for Edit]
This is the type of management task that CID is intended for.

[Submitter's Last Name] 
Stanwood

[Submitter's First Name]
Ken

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
148
[Starting Line #]
8

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Add RFC-868 to section 1.1.

[Reason for Edit]
That's where normative references are listed.

[Submitter's Last Name] 
Stanwood

[Submitter's First Name]
Ken

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
148

[Starting Line #]
45

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Change referenced section from 2.4 to 2.4.2.

[Reason for Edit]
More explicit reference to TLVs.

[Submitter's Last Name] 
Stanwood

[Submitter's First Name]
Ken

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
153

[Starting Line #]
43

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
G

[Detailed Description of Proposed Insertion, Deletion, Change]
The Basic CID and secondary management CID need to be returned in the
Ranging Response rather than a Temporary CID.  Additionally, we actually
have no current mechanism for getting the SS CIDs for the connections
established in the registration request/response.

[Reason for Edit]
The whole concept of TID and not needing CIDs for provisioned connections is
a hold over from DOCSIS where it was OK for all management and all best
effort user data to share 1 Ethernet flow devoid of any real QoS.  The Basic
CID and secondary management CID are intended to allow the entry into the
system of additional SSs without threatening the QoS of previously
established connections.

[Submitter's Last Name] 
Stanwood

[Submitter's First Name]
Ken

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
154

[Starting Line #]
16

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Insert space between sentences.

[Reason for Edit]
typo

[Submitter's Last Name] 
Stanwood

[Submitter's First Name]
Ken

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
155

[Starting Line #]
1

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
re-draw the Figure

[Reason for Edit]
ugly, patched figure.

[Submitter's Last Name] 
Stanwood

[Submitter's First Name]
Ken

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
158

[Starting Line #]
37

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

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

[Reason for Edit]
Out of date DOCSIS concept.

[Submitter's Last Name] 
Stanwood

[Submitter's First Name]
Ken

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
159

[Starting Line #]
26

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

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

[Reason for Edit]
typo

[Submitter's Last Name] 
Stanwood

[Submitter's First Name]
Ken

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
159

[Starting Line #]
53

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
G

[Detailed Description of Proposed Insertion, Deletion, Change]
We need to be able to change the provisioning of a CPE after the CPE is
operational.  We should add a standardized connection mib.

[Reason for Edit]
The customers behind CPEs may add services, delete services, and modify
services at the contract level.  While services may be added in the truly
dynamic case (probably more applicable to TG3 than TG1), these contractual
changes reflect a change in provisioning that would result in the updating
of a CPEs configuration file and its Provisioned QoS Parameter Sets.

[Submitter's Last Name] 
Stanwood

[Submitter's First Name]
Ken

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
161

[Starting Line #]
40

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Insert "or from a connection mib" after "configuration file"

[Reason for Edit]
The customers behind CPEs may add services, delete services, and modify
services at the contract level.  While services may be added in the truly
dynamic case (probably more applicable to TG3 than TG1), these contractual
changes reflect a change in provisioning that would result in the updating
of a CPEs configuration file and its Provisioned QoS Parameter Sets.

[Submitter's Last Name] 
Stanwood

[Submitter's First Name]
Ken

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
92

[Starting Line #]
6

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
The REG-RSP message must contain CIDs for the service flows.

[Reason for Edit]
There are no DSA messages sent for these flows to associate CIDs.
Prev by Date: stds-802-16: TG1 COMMENTS
Next by Date: stds-802-16: TG1 COMMENTS
Prev by thread: stds-802-16: TG1 COMMENTS
Next by thread: stds-802-16: TG1 COMMENTS
Index(es):
- Date
- Thread