Re: [sip-clf] draft-ietf-sipclf-problem-statement-05 Reason-Phrase

Anders Nygren <anders.nygren@gmail.com> Tue, 15 March 2011 21:30 UTC

Return-Path: <anders.nygren@gmail.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 44AE93A6D54 for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 14:30:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.39
X-Spam-Level:
X-Spam-Status: No, score=-3.39 tagged_above=-999 required=5 tests=[AWL=0.209, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cxuGNu-0V5yU for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 14:30:37 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 2A4D53A6C81 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 14:30:37 -0700 (PDT)
Received: by wwa36 with SMTP id 36so870483wwa.13 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 14:32:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=WCZnNzR1PAPtyQIj/BOvNkrA0x5Jcl4x/27tFIhk3mg=; b=UcTJ0FnAN/PbW1hlE6xsHBWoWSkquVjyIAD6UImitkTlbA0IKs+xY9kp3cE6WbWOvY yzzhsNOA/SnzUnTVfF+/0r5oZ62GT7VaJrzSUuiZygomINKUf6Gdeps1WtyRxWLn/DnF Qhi0Z52HFcesCMoAYDipGBnJUHr6EqbWfAUfA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=be9Ys8zz0efu+yoYJz8FU2BwwcGMK/dHtfQFurye02jZY4hU3BLAheiRVsZzL2Ru6j aMYUh7oFJ8ohkpW55/R4bTq/TNN2zVzYHcLwa/gNxsJ6czbxxgRCR7uCuR0F9NpB6/31 ed3SEMvO7Rnn4VKkbq3mE7bc1ikBF5dTkAmTI=
MIME-Version: 1.0
Received: by 10.216.145.90 with SMTP id o68mr4021612wej.77.1300224721883; Tue, 15 Mar 2011 14:32:01 -0700 (PDT)
Received: by 10.216.25.17 with HTTP; Tue, 15 Mar 2011 14:32:01 -0700 (PDT)
In-Reply-To: <41DAD933-6D4A-43EE-B817-23B6795748B8@magorcorp.com>
References: <AANLkTinnyWJ1wDzZdsW9PzyO+xTSSiy_pjm+JLs9ADyi@mail.gmail.com> <41DAD933-6D4A-43EE-B817-23B6795748B8@magorcorp.com>
Date: Tue, 15 Mar 2011 15:32:01 -0600
Message-ID: <AANLkTi=HDJkBphTg6jGCrZaWKi8M16M+n_Mz5rY10Ubx@mail.gmail.com>
From: Anders Nygren <anders.nygren@gmail.com>
To: Peter Musgrave <peter.musgrave@magorcorp.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] draft-ietf-sipclf-problem-statement-05 Reason-Phrase
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-clf>
List-Post: <mailto:sip-clf@ietf.org>
List-Help: <mailto:sip-clf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2011 21:30:38 -0000

On Tue, Mar 15, 2011 at 3:23 PM, Peter Musgrave
<peter.musgrave@magorcorp.com> wrote:
> I think as a predefined option field Reason Phrase makes sense.
>
> It may be worth thinking about other optional header fields people might want...Refer, History-Info, Session-ID - might become a bit of a long list. Would this be viewed as useful?
>

I don't have a list of header fields that I want to add, but I think
it may be good
to define most SIP headers as optional field just to prevent too many
vendors from
defining their own extensions for standard sip headers.

/Anders

> Peter (as individual)
>
> On 2011-03-15, at 5:10 PM, Anders Nygren wrote:
>
>> Hi
>> The list of mandatory fields includes Status-Code but not Reason-Phrase.
>> Wouldn't it be useful to have Reason-Phrase also since RFC3261
>>
>> 21.1.5 183 Session Progress
>>
>>   The 183 (Session Progress) response is used to convey information
>>   about the progress of the call that is not otherwise classified.  The
>>   Reason-Phrase, header fields, or message body MAY be used to convey
>>   more details about the call progress.
>>
>> 21.4.1 400 Bad Request
>>
>>   The request could not be understood due to malformed syntax.  The
>>   Reason-Phrase SHOULD identify the syntax problem in more detail, for
>>   example, "Missing Call-ID header field".
>>
>> So at times Reason-Phrase gives some additional information that can not be
>> obtained from just the Status-Code. Maybe as an optional field.
>>
>> /Anders
>> _______________________________________________
>> sip-clf mailing list
>> sip-clf@ietf.org
>> https://www.ietf.org/mailman/listinfo/sip-clf
>
>