Re: [sipcore] I-D Action:draft-ietf-sipcore-rfc4244bis-callflows-08.txt
Mary Barnes <mary.ietf.barnes@gmail.com> Fri, 06 December 2013 14:11 UTC
Return-Path: <mary.ietf.barnes@gmail.com>
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 982D51ADFB5 for <sipcore@ietfa.amsl.com>; Fri, 6 Dec 2013 06:11:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 iManXRYAhTy3 for <sipcore@ietfa.amsl.com>; Fri, 6 Dec 2013 06:11:30 -0800 (PST)
Received: from mail-we0-x22d.google.com (mail-we0-x22d.google.com [IPv6:2a00:1450:400c:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id C2FF41ADF43 for <sipcore@ietf.org>; Fri, 6 Dec 2013 06:11:29 -0800 (PST)
Received: by mail-we0-f173.google.com with SMTP id u57so714303wes.32 for <sipcore@ietf.org>; Fri, 06 Dec 2013 06:11:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=PBQ6LyXvb13rFSNLJ5c+x/jCNQnPreOGneDnNiOcl2E=; b=0gdnruhClpPFiFt0Ax4nPnhPaVQa4TVo3scvdAc9jPpX4O897stkuwRfn+ynlqP3Bg n1tVodzhGviwqz9CO0VVi2efb1eirhsVCywUWGsMrX7ulglxnVMTNOlKtDrpHiE+KfOv xOYOc2dsfBHuK5oIxQR7U+dliY7XOfJ44mi4IVVnwQWczqjFpkSUXAQEoOvzFWroHhkm PRrfLu9ve1XAEGfLPHGH3hnFAFB4O+qvMOxR1BBV20Jho0MSu8onQTc2BIysRmg/YcoE i+HYUPfDSTwEWUwSg2fWW0om+P9CIOp8rio3SrWw+lI5a4yB2l03545VFIseE2WPaSvA 2eCA==
MIME-Version: 1.0
X-Received: by 10.180.206.41 with SMTP id ll9mr2608610wic.7.1386339085496; Fri, 06 Dec 2013 06:11:25 -0800 (PST)
Received: by 10.216.172.9 with HTTP; Fri, 6 Dec 2013 06:11:25 -0800 (PST)
In-Reply-To: <BBCEF2718D634Ashinji.okumura@softfront.jp>
References: <20131107182721.8391.35063.idtracker@ietfa.amsl.com> <9CCEF1A60DA830shinji.okumura@softfront.jp> <52A0AB71.3030204@alum.mit.edu> <CAHBDyN6kiePw6_0p+jrHb7mmdqdnR2LaPqgd8f6W6cy8W8i4rw@mail.gmail.com> <BBCEF2718D634Ashinji.okumura@softfront.jp>
Date: Fri, 06 Dec 2013 08:11:25 -0600
Message-ID: <CAHBDyN6tmaJzdUsahcgMCQJDaPipuPMALQAcO0Y6n2_TM5M3aA@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: OKUMURA Shinji <shinji.okumura@softfront.jp>
Content-Type: multipart/alternative; boundary="001a11c38882bab56704ecde3857"
Cc: "draft-ietf-sipcore-rfc4244bis-callflows@tools.ietf.org" <draft-ietf-sipcore-rfc4244bis-callflows@tools.ietf.org>, SIPCORE <sipcore@ietf.org>
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: Fri, 06 Dec 2013 14:11:32 -0000
We will review your comments and get back to you shortly (we won't ignore your input that may be valid). Thanks, Mary. On Fri, Dec 6, 2013 at 4:54 AM, OKUMURA Shinji <shinji.okumura@softfront.jp>wrote: > Paul and Mary, > > As you say, my comment is too late, sorry. > > But I just want to know which are my comment and question valid or not? > > Regards > Shinji > > Mary Barnes <mary.ietf.barnes@gmail.com> > Thu, 5 Dec 2013 10:44:59 -0600 > >My preference is for individuals to send the comments in line in the email > >(as we do for all official reviews). It's very tedious to expect authors > >to sift through a diff and more importantly it makes any of the details > >impossible to find if you're googling. > > > >As you note, the changes are very late in the process. > > > >Mary. > > > > > >On Thu, Dec 5, 2013 at 10:36 AM, Paul Kyzivat <pkyzivat@alum.mit.edu> > wrote: > > > >> Authors - please look at these and comment if you believe they are > valid. > >> > >> Comments from others are also welcome on this. > >> > >> I'll note that it is very late in the process to get changes. > Potentially > >> there is an opportunity during AUTH48. > >> > >> Thanks, > >> Paul > >> > >> > >> On 12/5/13 5:37 AM, OKUMURA Shinji wrote: > >> > >>> 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/ >
- [sipcore] I-D Action: draft-ietf-sipcore-rfc4244b… internet-drafts
- Re: [sipcore] I-D Action: draft-ietf-sipcore-rfc4… OKUMURA Shinji
- Re: [sipcore] I-D Action: draft-ietf-sipcore-rfc4… Paul Kyzivat
- Re: [sipcore] I-D Action: draft-ietf-sipcore-rfc4… Mary Barnes
- Re: [sipcore] I-D Action:draft-ietf-sipcore-rfc42… OKUMURA Shinji
- Re: [sipcore] I-D Action:draft-ietf-sipcore-rfc42… Mary Barnes