[Sip] RAI-ART review of draft-ietf-sip-hitchhikers-guide-03

Joerg Ott <jo@netlab.tkk.fi> Sun, 04 November 2007 14:31 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IogVV-0007Em-9A; Sun, 04 Nov 2007 09:31:21 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1InCxY-0003Gr-Qs for sip-confirm+ok@megatron.ietf.org; Wed, 31 Oct 2007 08:46:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1InCxY-0003F4-6F; Wed, 31 Oct 2007 08:46:12 -0400
Received: from keskus.netlab.hut.fi ([130.233.154.176] helo=smtp.netlab.hut.fi) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1InCxL-0003AJ-Un; Wed, 31 Oct 2007 08:46:06 -0400
Received: from localhost (webserver.netlab.hut.fi [130.233.154.187]) by smtp.netlab.hut.fi (Postfix) with ESMTP id 6160EC50E5; Wed, 31 Oct 2007 14:45:38 +0200 (EET)
X-Virus-Scanned: Debian amavisd-new at TKK Netlab
Received: from smtp.netlab.hut.fi ([130.233.154.176]) by localhost (webserver.netlab.hut.fi [130.233.154.187]) (amavisd-new, port 10024) with ESMTP id etSUWyIti1mV; Wed, 31 Oct 2007 14:45:31 +0200 (EET)
Received: from [127.0.0.1] (keskus.netlab.hut.fi [130.233.154.176]) by smtp.netlab.hut.fi (Postfix) with ESMTP id 44BC8C50E2; Wed, 31 Oct 2007 14:45:31 +0200 (EET)
Message-ID: <472878ED.9070009@netlab.hut.fi>
Date: Wed, 31 Oct 2007 14:45:33 +0200
From: Joerg Ott <jo@netlab.tkk.fi>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@cisco.com>, sip ietf <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>, drage@alcatel-lucent.com, rai@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
X-Mailman-Approved-At: Sun, 04 Nov 2007 09:31:19 -0500
Cc:
Subject: [Sip] RAI-ART review of draft-ietf-sip-hitchhikers-guide-03
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

Hi,

I am the assigned RAI-ART reviewer for draft-ietf-sip-hitchhikers-guide-03

For background on RAI-ART, please see the FAQ at 
<http://www.softarmor.com/rai/art/rai-art-FAQ.html>.

Please resolve the comments below along with any other
Last Call comments you may receive.

It may be worthwhile to include the advice in the beginning:

"Do not print all the specs cited here at once, as they
might share the fate of the rules of Brockian Ultracricket
when bound together: collapse under their own gravity and
form a black hole. [42]"

Joerg


Review of draft-ietf-sip-hitchhikers-guide-03:


This draft is ready for publication as an Informational RFC.
Please consider the suggestions and nits listed below.


Observations and suggestions:

Sect. 5, p10, RFC4244:

     "Its primary purpose _was_ in support of voicemail services."

     This reads like the document became obsolete already.
     Is this intentional?  If so, would it be useful to also
     indicate which other purposes it now serves (or none
     at all)?


Sect. 7, p13, RFC4583:

     This should go to the conferencing section (sect. 8).


Sect. 7, p13, RFCXXXX [59]:

     This should explicitly state that it builds upon the general
     mechanisms of RFC 3312 (which only is described later).


Sect. 9, p14, RFC3515:

     It may be useful to add a warning clause concerning REFER,
     e.g., along the following lines:

     "Beware that not all potential uses of REFER (neither for all
      methods nor for all URI schemes) are well defined.  Be advised
      to use only the well-defined ones and not to second guess or
      freely assume behavior for the others to avoid unexpected
      behavior of remote UAs, interoperability issues, and other
      bad surprises."



Nits:

Sect. 9, p14, RFC3515:

     2nd sentence: "Its" -> "It is"




_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip