Re: [Gen-art] [Gen-Art] LC Review: draft-ietf-tsvwg-emergency-rsvp-07.txt

Francois Le Faucheur IMAP <flefauch@cisco.com> Wed, 07 May 2008 07:47 UTC

Return-Path: <gen-art-bounces@ietf.org>
X-Original-To: gen-art-archive@optimus.ietf.org
Delivered-To: ietfarch-gen-art-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B880B28C71D; Wed, 7 May 2008 00:47:23 -0700 (PDT)
X-Original-To: gen-art@core3.amsl.com
Delivered-To: gen-art@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7628D28C6BA for <gen-art@core3.amsl.com>; Wed, 7 May 2008 00:46:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.339
X-Spam-Level:
X-Spam-Status: No, score=-6.339 tagged_above=-999 required=5 tests=[AWL=0.260, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 95C-2DmJfQY1 for <gen-art@core3.amsl.com>; Wed, 7 May 2008 00:45:01 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 48EC03A7114 for <gen-art@ietf.org>; Wed, 7 May 2008 00:35:20 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,446,1204498800"; d="scan'208";a="8217445"
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 07 May 2008 09:35:16 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m477ZGgB012958; Wed, 7 May 2008 09:35:16 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m477ZGlo027042; Wed, 7 May 2008 07:35:16 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 May 2008 09:35:16 +0200
Received: from [10.55.161.195] ([10.55.161.195]) by xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 May 2008 09:35:15 +0200
In-Reply-To: <E5D987A4-4E82-4917-ABDA-66F5CCE52BEB@g11.org.uk>
References: <481CE28F.4040007@joelhalpern.com> <4E91AE8C-1B9C-4360-BEBA-B654B56B7337@cisco.com> <E0C5EDE4-002D-4797-959D-8ABAB7C2DD88@cisco.com> <E5D987A4-4E82-4917-ABDA-66F5CCE52BEB@g11.org.uk>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <0BCA0DAE-313D-4E9A-A38C-11065DB620C3@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Date: Wed, 07 May 2008 09:35:11 +0200
To: "Joel M. Halpern" <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 07 May 2008 07:35:15.0981 (UTC) FILETIME=[E484EBD0:01C8B014]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1974; t=1210145716; x=1211009716; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=flefauch@cisco.com; z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco. com> |Subject:=20Re=3A=20[Gen-Art]=20LC=20Review=3A=20draft-ietf -tsvwg-emergency-rsvp-07.txt |Sender:=20; bh=ENpgly/CYFqsHx1vucF5eJ2lnCh189BjhKYUnV7ZZEE=; b=ggl+XkgZ2Jf5WsptZBFX5GPp7coxYjtpJDDbLtjSpl6Q0pI/HZHEFT/ZGc j6xcyHGggTnA0W1m1aXkg1bd5A2JAF6jik/ks2W4EVyLEpblb9MpcwL5znQO +UOGtS1btq;
Authentication-Results: ams-dkim-2; header.From=flefauch@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; );
Cc: Magnus Westerlun <magnus.westerlund@ericsson.com>, Francois Le Faucheur IMAP <flefauch@cisco.com>, General Review Team Area <gen-art@ietf.org>, ken carlberg <carlberg@g11.org.uk>, "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [Gen-art] [Gen-Art] LC Review: draft-ietf-tsvwg-emergency-rsvp-07.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: gen-art-bounces@ietf.org
Errors-To: gen-art-bounces@ietf.org

Hi Joel,

>
>>>>
>>>> Minor Comments:
>>>> 	My personal opinion is that using "call" to describe the  
>>>> sessions being established is probably not the best choice.  In  
>>>> many contexts which will need to reference this document, call  
>>>> has a much more specific meaning.  It is not clear why "session"  
>>>> is not sufficient.  (But I presume that the particular  
>>>> terminology is the result of significant consideration, and  
>>>> therefore my personal reaction is not a reason to hold up this  
>>>> document.)
>>>
>>> The rationale was that people were often more familiar with the  
>>> concept of "emergency" being associated to phone calls than to  
>>> multimedia sessions. So it helped initially to use the term  
>>> "call". We included a clarification note explaining that "call"  
>>> actually means "session".
>>> "Note: Below, this document references several examples of IP
>>>   telephony and its use of "calls", which is one form of the term
>>>   "sessions" (Video over IP and Instant Messaging being other  
>>> examples
>>>   that rely on session establishment).  For the sake of  
>>> simplicity, we
>>>   shall use the widely known term "call" for the remainder of this
>>>   document.
>>> "
>>> Now that the document has matured enough, I would be happy to  
>>> revert to a more generic "session" terminology. let's hear my co- 
>>> authors on this.
>
> I'm fine with this.  and in going back to the more generic  
> "session", we may simply want to do a total inversion of text.   
> where we start with "session" and stay with it through the entire  
> document, but note in the Intro that a more specific instance of a  
> session could be in the form of a "call".
>>>

We have agreement among co-authors, so next version will address your  
comment and :
	- use "session" throughout
	- have a note saying that a "call" is a more specific instance of a  
session.

Thanks

Francois
_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art