Document:draft-dcsgroup-sipping-arch-01.txt
Reviewer: Lucy Lynch
Date: 	19 augusti 2004


Architectural Considerations for Providing Carrier Class Telephony
Services Utilizing Session Initiation Protocol (SIP)-based
Distributed Call Control Mechanisms
Document: <draft-dcsgroup-sipping-arch-01.txt>
Category: Informational

No Objection

Comments:
While this document seems very straight forward, I'll note that at
just over 20 pages it doesn't begin to address the scope of the
PacketCable document (400+ pages)
ftp://ftp.cablelabs.com/pub/pkt-sp-dcs-d03-000428.pdf

and the figure provided:
"Figure 1: A Simple view of Components of an IP Telephony
           Architecture used in a HFC Cable Environment."

doesn't give any indication of how much more complex problems
like security/privacy/QOS can be, see:

surveillance - see figures on pages 328/332/338
privacy -see page 343
QOS - see pages 360/363/364

reads a bit like a marketing doc.
--------------------------------------------------------------------
idnits 1.34 (28 Jul 2004)

draft-dcsgroup-sipping-arch-01.txt:

  Looks like you're using RFC 2026 boilerplate. Better change to RFC
3667/3668.
  The document seems to lack an 2026 Section 10.4(C) Copyright Notice
  -- however, there's a paragraph with a matching beginning. Boilerplate
error?
  The document seems to lack an RFC 2026 Section 10.4(C) Permission Grants
Notice
  The document seems to lack an RFC 2026 Section 10.4(C) Disclaimer

  Warnings:
    There are 21 instances of lines with hyphenated line breaks in the
document.

    Line 57 has weird spacing: '...S Group   Cate...'
    Line 115 has weird spacing: '...S Group   Cate...'
    Line 173 has weird spacing: '...S Group   Cate...'
    Line 231 has weird spacing: '...S Group   Cate...'
    Line 288 has weird spacing: '...S Group   Cate...'