Re: Last Call: <draft-hanes-dispatch-fax-capability-06.txt> (Indicating Fax over IP Capability in the Session Initiation Protocol (SIP)) to Proposed Standard

Hadriel Kaplan <HKaplan@acmepacket.com> Fri, 21 December 2012 18:28 UTC

Return-Path: <btv1==702717fa800==HKaplan@acmepacket.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C80821F853C for <ietf@ietfa.amsl.com>; Fri, 21 Dec 2012 10:28:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.216
X-Spam-Level:
X-Spam-Status: No, score=-2.216 tagged_above=-999 required=5 tests=[AWL=-0.217, BAYES_00=-2.599, J_CHICKENPOX_44=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 79Gfa3B6hoZi for <ietf@ietfa.amsl.com>; Fri, 21 Dec 2012 10:28:34 -0800 (PST)
Received: from mx2.acmepacket.com (mx2.acmepacket.com [216.41.24.99]) by ietfa.amsl.com (Postfix) with ESMTP id 9DF9521F84FD for <ietf@ietf.org>; Fri, 21 Dec 2012 10:28:34 -0800 (PST)
X-ASG-Debug-ID: 1356114507-03fc2110a84b3ec0001-h9jmKw
Received: from Mail1.acmepacket.com (mail1.acmepacket.com [10.0.0.21]) by mx2.acmepacket.com with ESMTP id 4D73hYgiL0wICG89 (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO); Fri, 21 Dec 2012 13:28:27 -0500 (EST)
X-Barracuda-Envelope-From: HKaplan@acmepacket.com
Received: from MAIL2.acmepacket.com ([169.254.2.174]) by Mail1.acmepacket.com ([169.254.1.77]) with mapi id 14.02.0283.003; Fri, 21 Dec 2012 13:28:26 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "<ietf@ietf.org>" <ietf@ietf.org>
Subject: Re: Last Call: <draft-hanes-dispatch-fax-capability-06.txt> (Indicating Fax over IP Capability in the Session Initiation Protocol (SIP)) to Proposed Standard
Thread-Topic: Last Call: <draft-hanes-dispatch-fax-capability-06.txt> (Indicating Fax over IP Capability in the Session Initiation Protocol (SIP)) to Proposed Standard
X-ASG-Orig-Subj: Re: Last Call: <draft-hanes-dispatch-fax-capability-06.txt> (Indicating Fax over IP Capability in the Session Initiation Protocol (SIP)) to Proposed Standard
Thread-Index: AQHN36j3dhbE+IfSw0qrFP0DgKbkhA==
Date: Fri, 21 Dec 2012 18:28:26 +0000
Message-ID: <CD38BBC6-1E84-4AF6-913B-BABE1BDFC6E0@acmepacket.com>
References: <20121129144602.12454.60016.idtracker@ietfa.amsl.com>
In-Reply-To: <20121129144602.12454.60016.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.0.0.30]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <45941797CD49A842BB3A53CA7943ED57@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Barracuda-Connect: mail1.acmepacket.com[10.0.0.21]
X-Barracuda-Start-Time: 1356114507
X-Barracuda-Encrypted: AES128-SHA
X-Barracuda-URL: http://216.41.24.99:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at acmepacket.com
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using per-user scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests=BSF_SC0_MISMATCH_TO
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.117670 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.00 BSF_SC0_MISMATCH_TO Envelope rcpt doesn't match header
Cc: "draft-hanes-dispatch-fax-capability@tools.ietf.org" <draft-hanes-dispatch-fax-capability@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Dec 2012 18:29:03 -0000

Howdy,
I've read the draft and overall it looks good.  

Some minor comments:
The examples in section 5 of the draft repeatedly show a Via header as follows:
Via: SIP/2.0/TCP bob-TP@example.com;branch=z9hG4bK309475a2
This is not a legal Via header format, since the sent-by field cannot contain a '@'.  It's meant to be a host or host:port, not a user@host... and more likely a host:port since this is TCP for this example.

Also, the examples show a Contact URI host of the domain in the REGISTER request, the same as the target request-URI.  While not technically illegal I guess, it's extremely unusual - the purpose of a REGISTER is to register the Contact URI as the reachable target for the Address of Record, and thus the Contact URI should indicate the specific host registering.  I suggest changing it to:
Contact: <sip:bob-tp@pc33.example.com;transport=tcp>;+sip.fax="t38"

Lastly, the example INVITE at the end of section 5 is malformed, both because it's missing mandatory headers, and because the From header has no tag param.

-hadriel


On Nov 29, 2012, at 9:46 AM, The IESG <iesg-secretary@ietf.org> wrote:

> 
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Indicating Fax over IP Capability in the Session Initiation Protocol
>   (SIP)'
>  <draft-hanes-dispatch-fax-capability-06.txt> as Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-12-27. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>   This document defines and registers with IANA the new 'fax' media
>   feature tag for use with SIP.  Currently, fax calls are
>   indistinguishable from voice at call initiation.  Consequently, fax
>   calls can be routed to SIP user agents that are not fax capable.  A
>   'fax' media feature tag implemented in conjunction with caller
>   preferences allows for more accurate fax call routing.
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-hanes-dispatch-fax-capability/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-hanes-dispatch-fax-capability/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
>