IETF Logo Mail Archive

Re: [bfcpbis] TBD issue #1: Subsequent

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Thu, 13 December 2012 16:25 UTC

Return-Path: <eckelcu@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 A4C7421F8B1B for <bfcpbis@ietfa.amsl.com>; Thu, 13 Dec 2012 08:25:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[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 hu-RPrl0Qb59 for <bfcpbis@ietfa.amsl.com>; Thu, 13 Dec 2012 08:25:42 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 2E41821F8B1A for <bfcpbis@ietf.org>; Thu, 13 Dec 2012 08:25:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2505; q=dns/txt; s=iport; t=1355415942; x=1356625542; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=wvqipHV/3btHuEyaTMVMKjjRXbZ9oPxn1Kwbr4aOQug=; b=ZYF6ywnoO9O+mMW1vswXpTOzz6X/HDH2IAHDT/VKYVj7CPIAiEKqZ4+k OG2Hf8eA8wLsYrUnilCJp+5qgKYG5K+gsKItnOhKTKgiY1K4K6z/8IP0C 7KfzpzstiKBIRkU3+Ph3TQnTw/urBRbhP2HACx2Q4KrM5lo9tgG42EpD9 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAIcAylCtJV2Z/2dsb2JhbABFvm4Wc4IeAQEBBAEBATc0CwwEAgEIEQQBAQEKFAkHJwsUCQgCBAENBQiICwy9KQSMVwuDV2EDplGCc4FtNQ
X-IronPort-AV: E=Sophos;i="4.84,274,1355097600"; d="scan'208";a="152616619"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-6.cisco.com with ESMTP; 13 Dec 2012 16:25:41 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id qBDGPfda031339 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 13 Dec 2012 16:25:41 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.169]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.02.0318.004; Thu, 13 Dec 2012 10:25:40 -0600
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Tom Kristensen (tomkrist)" <tomkrist@cisco.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Thread-Topic: [bfcpbis] TBD issue #1: Subsequent
Thread-Index: AQHNwXgfBEoaZUqxBUaUB8/PFHBDIJfn06+AgAAHPgCALBVZAIADKZ9g
Date: Thu, 13 Dec 2012 16:25:40 +0000
Message-ID: <92B7E61ADAC1BB4F941F943788C08828046EB378@xmb-aln-x08.cisco.com>
References: <50A20368.9050408@cisco.com> <50A204F3.8000809@ericsson.com> <50A20B06.9080902@cisco.com> <50C705DC.5090208@cisco.com>
In-Reply-To: <50C705DC.5090208@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.154.128.80]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: BFCPbis WG <bfcpbis@ietf.org>, 'Tom Kristensen' <2mkristensen@gmail.com>
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: Thu, 13 Dec 2012 16:25:43 -0000

Works for me.

Cheers,
Charles (as an individual)

> -----Original Message-----
> From: bfcpbis-bounces@ietf.org [mailto:bfcpbis-bounces@ietf.org] On
> Behalf Of Tom Kristensen (tomkrist)
> Sent: Tuesday, December 11, 2012 2:07 AM
> To: Gonzalo Camarillo
> Cc: BFCPbis WG; 'Tom Kristensen'
> Subject: Re: [bfcpbis] TBD issue #1: Subsequent
> 
> In Sections 5.3.14/5.3.15 I'll simply add a reference to the sections
> describing the generation of these subsequent messages from the server
> (Sections 13.1.2 and 13.5.2 respectively). This way:
> 
>      "When communicating over an unreliable transport, floor
>       participants and chairs acknowledge the receipt of a
>       subsequent FloorRequestStatus message from the floor
>       control server (cf. Section 13.1.2) by sending a
>       FloorRequestStatusAck message."
> 
> -- Tom
> 
> On 11/13/2012 09:55 AM, Tom Kristensen wrote:
> > 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
> >
> > _______________________________________________
> > bfcpbis mailing list
> > bfcpbis@ietf.org
> > https://www.ietf.org/mailman/listinfo/bfcpbis
> >
> 
> _______________________________________________
> bfcpbis mailing list
> bfcpbis@ietf.org
> https://www.ietf.org/mailman/listinfo/bfcpbis

v2.16.0 | Report a Bug | By Email