A00-20120416-039Br0 _CTC_ VnV Comments A.S0022 by gegouzhen12

VIEWS: 0 PAGES: 2

									A.S0022-B v1.0 V&V Comments

1.    ##. DO NOT number your comments (leave column 1 blank).
2.    Page. Include a single number for the section, a dash and three digits for the page number (or complete Roman numeral for introduction). E.g., 0-iii, 2-001.
3.    Line. Include a two digit line number. E.g., 01, 19, 00 (if it pertains to the whole page). Do not use “*”, etc as they do not always sort well.
4.    Type. Use only T for Technical change (may require discussion), or E for Editorial change (e.g. grammar, spelling, format).
5.    Bug. Indicate if this is a bug fix to text that was included in a previous revision (V&V only).
6.    Result. Completed by the Editor in review.
7.    DO NOT, UNDER ANY CIRCUMSTANCES, ADJUST THE WIDTHS OF THE COLUMNS!
8.    Basic comment guidelines:
      a. USE strikeout and underscore in the comment form for showing changes. DO NOT use change bars in the comment form: it is not possible to cut and
          paste them into the master. If you want to show changes to a section using change bars, submit a Supporting File.
      b. For extended comments, attach a file with comment. Use: SF-xxx-RnF-CO-name. Where CO = company & xxx = comment number (when available).
9.    For detailed guidelines on generation of comments and SFs, refer to accepted contribution A00-20071203-016r0.

###     Source           Page Line      Section        Type Bug        Results A.S0022-B v1.0 V&V Comments
        CT               1-020 12       1.14.1.14        t                     The capability already exists for an eAN to use the radio resources of a legacy
                                                                               AN, through the use of A17, A18, and A19, and vice-versa. No new protocols
                                                                               need to be written to support this. This capability should be declared in section
                                                                               1.14.1 as a new subsection. Declaring this capability is also aligned with the text
                                                                               at lines 36-37 on page 1-18: “The following subsections identify the features
                                                                               explicitly supported by standalone eHRPD systems for eHRPD – HRPD
                                                                               interconnectivity and by eHRPD systems for E-UTRAN – eHRPD
                                                                               interconnectivity.”

                                                                                 See the supporting file:
                                                                                 SF-xxx-VnV-CTC+ALU+HW -- IWK A17-A18-A19 between eHRPD and
                                                                                 HRPD.docx




                                                                            Page 1 of 2
A.S0022-B v1.0 V&V Comments

###   Source    Page   Line   Section   Type Bug   Results A.S0022-B v1.0 V&V Comments




                                                      Page 2 of 2

								
To top