Re: [bfcpbis] TBD issue #1: Subsequent

Tom Kristensen <tomkrist@cisco.com> Tue, 13 November 2012 08:55 UTC

Return-Path: <tomkrist@cisco.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCE5C21F85EB for <bfcpbis@ietfa.amsl.com>; Tue, 13 Nov 2012 00:55:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.099
X-Spam-Level:
X-Spam-Status: No, score=-10.099 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 tSv6MxDn4e3F for <bfcpbis@ietfa.amsl.com>; Tue, 13 Nov 2012 00:55:41 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 36D8321F865D for <bfcpbis@ietf.org>; Tue, 13 Nov 2012 00:55:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1198; q=dns/txt; s=iport; t=1352796938; x=1354006538; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=mQ3s8TlpUhK+Zff/mYEOfK6rPx0TbQLeBhGN7GVjoMw=; b=daE8ObLMK4tcdy9TMrTzjY/WGLhsltQ+m2QnQwas6YHWbxYBXdMSayuK 8Esi8aiCk6jdjzMVngy3W4IVEjy8HO3ohKxsBJjDcfvfzpCF+BygZ1kG1 muZGYaMEzPstec2vq6wKrk6KYAV6v9T25LP9zti9CA30aPFvofDNo0lgc s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag4FAKAIolCQ/khM/2dsb2JhbABEwC6DRYEIgh4BAQEEEgElQAEQCxgJFg8JAwIBAgFFBg0BBwEBHodomiuPZZA4jCGGVAOVfIVriG2Ba4JwgWM
X-IronPort-AV: E=McAfee;i="5400,1158,6894"; a="78188776"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 13 Nov 2012 08:55:35 +0000
Received: from [10.54.86.33] (dhcp-10-54-86-33.cisco.com [10.54.86.33]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id qAD8tZ7r029167; Tue, 13 Nov 2012 08:55:35 GMT
Message-ID: <50A20B06.9080902@cisco.com>
Date: Tue, 13 Nov 2012 09:55:34 +0100
From: Tom Kristensen <tomkrist@cisco.com>
Organization: Cisco
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.15) Gecko/20101027 Fedora/3.0.10-1.fc12 Lightning/1.0b2pre Thunderbird/3.0.10
MIME-Version: 1.0
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
References: <50A20368.9050408@cisco.com> <50A204F3.8000809@ericsson.com>
In-Reply-To: <50A204F3.8000809@ericsson.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: BFCPbis WG <bfcpbis@ietf.org>
Subject: Re: [bfcpbis] TBD issue #1: Subsequent
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bfcpbis>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Nov 2012 08:55:42 -0000

I see your point. I'll reread the text once more and find out what to do!

-- Tom

On 11/13/2012 09:29 AM, Gonzalo Camarillo wrote:
> Hi Tom,
>
> thanks for initiating the discussion on the points you identified in
> your other email.
>
> With respect to this one, the important issue is not whether or not we
> keep "subsequent" in those sentences. The issue is that the text needs
> to be clear about what it means. So, if you prefer to explain the
> meaning of the sentence instead of removing the word, that would
> certainly be OK.
>
> Cheers,
>
> Gonzalo
>
>
> On 13/11/2012 10:23 AM, Tom Kristensen wrote:
>    
>> Minor issue. Anyway, here we go:
>>
>> Gonzalo:
>>      
>>> Sections 5.3.14 and 5.3.15 talk about acknowledging a "subsequent"
>>> message. Why is it a subsequent message? Maybe we can delete that
>>> word.
>>>        
>> Tom:
>> | It is subsequent in that it's not the initial FloorRequestStatus
>> | acknowleding the associated FloorRequest. The word might not
>> | be needed in Sections 5.3.14 and 5.3.15, but I'll remove it just if
>> | it is really confusing!?!
>>
>> Should it stay or should it go?
>>
>> -- Tom
>>      
>