Re: [bfcpbis] TBD issue #1: Subsequent

Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Tue, 13 November 2012 08:29 UTC

Return-Path: <gonzalo.camarillo@ericsson.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 A62D621F8449 for <bfcpbis@ietfa.amsl.com>; Tue, 13 Nov 2012 00:29:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.967
X-Spam-Level:
X-Spam-Status: No, score=-105.967 tagged_above=-999 required=5 tests=[AWL=0.282, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 lRFZDwlxatiF for <bfcpbis@ietfa.amsl.com>; Tue, 13 Nov 2012 00:29:46 -0800 (PST)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id BA47521F841F for <bfcpbis@ietf.org>; Tue, 13 Nov 2012 00:29:40 -0800 (PST)
X-AuditID: c1b4fb30-b7f936d0000018b3-4d-50a204f3beca
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 3C.BF.06323.3F402A05; Tue, 13 Nov 2012 09:29:39 +0100 (CET)
Received: from [131.160.36.86] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.3.279.1; Tue, 13 Nov 2012 09:29:39 +0100
Message-ID: <50A204F3.8000809@ericsson.com>
Date: Tue, 13 Nov 2012 10:29:39 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Tom Kristensen <tomkrist@cisco.com>
References: <50A20368.9050408@cisco.com>
In-Reply-To: <50A20368.9050408@cisco.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprALMWRmVeSWpSXmKPExsUyM+Jvje5nlkUBBo9OW1n8W3eUyeLKkV9s DkweU35vZPVYsuQnUwBTFJdNSmpOZllqkb5dAlfG3Y477AVX2CvWNp9na2D8xdrFyMkhIWAi MenuDShbTOLCvfVsXYxcHEICJxkl5l85zgjhrGaUaD/6hKWLkYODV0BbYtopJpAGFgFVif79 K9hAbDYBC4ktt+6zgNiiAlEShzYeZAexeQUEJU7OfAIWFxFQl+jb+x0sziygKHGlqxcsLgw0 5+6ff2C2kICGRPPpr8wgNqeApsTl369YII6TlHj7/hUzRK+exJSrLYwQtrzE9rdzmCF6tSWW P2thmcAoNAvJ6llIWmYhaVnAyLyKkT03MTMnvdx8EyMwVA9u+W2wg3HTfbFDjNIcLErivHqq +/2FBNITS1KzU1MLUovii0pzUosPMTJxcEo1MK7edPdYyAQZcb8zTl0zFp4PrPAq8yrrUPtx fYHIn7lLOTZ8Ffk4dfmJvTPfLJz5ZBdf1M/F4v8dO+c+VDpyLG7frdNVKVoTXzCrNW6cs89V Nb/zVUWvuXn/sQsHblpsMna+fSOtufpDcIL4pnkyWu8ndur+e9R8/3+HnrW/tNG0TRXtan6b dj9WYinOSDTUYi4qTgQAE1qBxiMCAAA=
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:29:46 -0000

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