Re: [dispatch] Comment on draft-hanes-dispatch-fax-capability-03

"Hutton, Andrew" <andrew.hutton@siemens-enterprise.com> Tue, 30 October 2012 13:36 UTC

Return-Path: <andrew.hutton@siemens-enterprise.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C403A21F84C2 for <dispatch@ietfa.amsl.com>; Tue, 30 Oct 2012 06:36:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 rb-KnxVfu+aR for <dispatch@ietfa.amsl.com>; Tue, 30 Oct 2012 06:36:51 -0700 (PDT)
Received: from senmx11-mx.siemens-enterprise.com (senmx11-mx.siemens-enterprise.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id B796021F84C1 for <dispatch@ietf.org>; Tue, 30 Oct 2012 06:36:50 -0700 (PDT)
Received: from MCHP01HTC.global-ad.net (unknown [172.29.42.234]) by senmx11-mx.siemens-enterprise.com (Server) with ESMTP id 0EAB61EB8422; Tue, 30 Oct 2012 14:36:49 +0100 (CET)
Received: from MCHP04MSX.global-ad.net ([169.254.1.76]) by MCHP01HTC.global-ad.net ([172.29.42.234]) with mapi id 14.02.0318.001; Tue, 30 Oct 2012 14:36:39 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>, DISPATCH <dispatch@ietf.org>
Thread-Topic: [dispatch] Comment on draft-hanes-dispatch-fax-capability-03
Thread-Index: AQHNssfdTBUhy/7z0UKwFjs7nAex45fR4XJQ
Date: Tue, 30 Oct 2012 13:36:39 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF0131B2BC@MCHP04MSX.global-ad.net>
References: <508914D1.60207@ericsson.com> <CAHBDyN5p4tmmBZ0EYjAwoQt0cTk8mPmeAxum+e0PdtTw41xhQg@mail.gmail.com>
In-Reply-To: <CAHBDyN5p4tmmBZ0EYjAwoQt0cTk8mPmeAxum+e0PdtTw41xhQg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.29.42.225]
Content-Type: multipart/alternative; boundary="_000_9F33F40F6F2CD847824537F3C4E37DDF0131B2BCMCHP04MSXglobal_"
MIME-Version: 1.0
Cc: Cullen Jennings <fluffy@cisco.com>, "draft-hanes-dispatch-fax-capability@tools.ietf.org" <draft-hanes-dispatch-fax-capability@tools.ietf.org>
Subject: Re: [dispatch] Comment on draft-hanes-dispatch-fax-capability-03
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Oct 2012 13:36:51 -0000

I support the draft moving forward by whatever means possible.

Regards
Andy

From: dispatch-bounces@ietf.org [mailto:dispatch-bounces@ietf.org] On Behalf Of Mary Barnes
Sent: 25 October 2012 16:46
To: DISPATCH
Cc: Cullen Jennings; draft-hanes-dispatch-fax-capability@tools.ietf.org
Subject: Re: [dispatch] Comment on draft-hanes-dispatch-fax-capability-03

Gonzalo has agreed to AD sponsor this document pending feedback from the WG.  If anyone has any concerns about progressing this document as such please respond on the list, giving your reasons no later than Nov 1st, 2012. I you agree on the progression of this document, it would also be helpful to reply indicating such.

Thanks,
Mary Barnes
DISPATCH WG co-chair
On Thu, Oct 25, 2012 at 5:30 AM, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com<mailto:Gonzalo.Camarillo@ericsson.com>> wrote:
Hi,

the draft below looks good in general. I only have a very minor comment:

http://tools.ietf.org/html/draft-hanes-dispatch-fax-capability-03

When the draft talks about "call setup", it refers to the process
whereby an INVITE request is routed to the appropriate user agent. The
thing is that some readers will probably think about call set up as the
offer/answer exchange. Keeping this in mind, the two first sentences of
Section 3 may result confusing for some readers.

Even though this is a minor comment, clarifying it should be a matter of
editing a few sentences. It should not take long at all.

Thanks,

Gonzalo

_______________________________________________
dispatch mailing list
dispatch@ietf.org<mailto:dispatch@ietf.org>
https://www.ietf.org/mailman/listinfo/dispatch