Re: [sipcore] I-D Action: draft-ietf-sipcore-rfc4244bis-callflows-08.txt

OKUMURA Shinji <shinji.okumura@softfront.jp> Thu, 05 December 2013 10:38 UTC

Return-Path: <shinji.okumura@softfront.jp>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 382F61ADEA3 for <sipcore@ietfa.amsl.com>; Thu, 5 Dec 2013 02:38:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.17
X-Spam-Level:
X-Spam-Status: No, score=-97.17 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RELAY_IS_221=2.222, SPF_HELO_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xlzryYHyIgCP for <sipcore@ietfa.amsl.com>; Thu, 5 Dec 2013 02:38:02 -0800 (PST)
Received: from softfront.co.jp (rt1.softfront.co.jp [221.186.247.166]) by ietfa.amsl.com (Postfix) with ESMTP id 45E391ADE72 for <sipcore@ietf.org>; Thu, 5 Dec 2013 02:38:00 -0800 (PST)
Received: from localhost (sf-mail [127.0.0.1]) by sf-mail.softfront.co.jp (Postfix) with ESMTP id 17C2B4280B9 for <sipcore@ietf.org>; Thu, 5 Dec 2013 19:37:56 +0900 (JST)
X-Virus-Scanned: amavisd-new at softfront.co.jp
Received: from softfront.co.jp ([127.0.0.1]) by localhost (sf-mail.softfront.co.jp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LmoYFme4BsRG for <sipcore@ietf.org>; Thu, 5 Dec 2013 19:37:55 +0900 (JST)
Received: from softfront.jp (sf-pc-111.softfront.local [172.16.33.39]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by sf-mail.softfront.co.jp (Postfix) with ESMTP id B284D4280B8 for <sipcore@ietf.org>; Thu, 5 Dec 2013 19:37:54 +0900 (JST)
From: OKUMURA Shinji <shinji.okumura@softfront.jp>
To: sipcore@ietf.org
Date: Thu, 05 Dec 2013 19:37:53 +0900
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="Boundary-TYzhXHhK5unLiPxPYvbGj"
X-Mailer: HidemaruMail 6.01 (WinNT,601)
In-Reply-To: <20131107182721.8391.35063.idtracker@ietfa.amsl.com>
References: <20131107182721.8391.35063.idtracker@ietfa.amsl.com>
Message-Id: <9CCEF1A60DA830shinji.okumura@softfront.jp>
Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-rfc4244bis-callflows-08.txt
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Dec 2013 10:38:04 -0000

Hi,

I attach diff files.
Please reflect a new version, if correct.

And one question.
Is it correct certainly that the index-val of rc/np parameter is a just parent of hi-index at all times?
i.e.
 History-Info: <sip:xxx>;index=x.y.z;rc=x.y

Or case by case?

Regards
Shinji

internet-drafts@ietf.org
Thu, 07 Nov 2013 10:27:21 -0800
>
>A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Session Initiation Protocol Core Working Group of the IETF.
>
>	Title           : Session Initiation Protocol (SIP) History-Info Header Call Flow Examples
>	Author(s)       : Mary Barnes
>                          Francois Audet
>                          Shida Schubert
>                          Hans Erik van Elburg
>                          Christer Holmberg
>	Filename        : draft-ietf-sipcore-rfc4244bis-callflows-08.txt
>	Pages           : 48
>	Date            : 2013-11-07
>
>Abstract:
>   This document describes use cases and documents call flows which
>   require the History-Info header field to capture the Request-URIs as
>   a Session Initiation Protocol (SIP) Request is retargeted.  The use
>   cases are described along with the corresponding call flow diagrams
>   and messaging details.
>
>
>The IETF datatracker status page for this draft is:
>https://datatracker.ietf.org/doc/draft-ietf-sipcore-rfc4244bis-callflows
>
>There's also a htmlized version available at:
>http://tools.ietf.org/html/draft-ietf-sipcore-rfc4244bis-callflows-08
>
>A diff from the previous version is available at:
>http://www.ietf.org/rfcdiff?url2=draft-ietf-sipcore-rfc4244bis-callflows-08
>
>
>Please note that it may take a couple of minutes from the time of submission
>until the htmlized version and diff are available at tools.ietf.org.
>
>Internet-Drafts are also available by anonymous FTP at:
>ftp://ftp.ietf.org/internet-drafts/