Re: [bfcpbis] Can not find Transaction ID 154 in Figure 48 in draft-ietf-bfcpbis-rfc4582bis-16 Appendix A.

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Wed, 26 September 2018 11:04 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 CDAC4130E82 for <bfcpbis@ietfa.amsl.com>; Wed, 26 Sep 2018 04:04:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.956
X-Spam-Level:
X-Spam-Status: No, score=-14.956 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 xVMefAgizgwh for <bfcpbis@ietfa.amsl.com>; Wed, 26 Sep 2018 04:04:25 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 180A3130E84 for <bfcpbis@ietf.org>; Wed, 26 Sep 2018 04:04:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=20906; q=dns/txt; s=iport; t=1537959862; x=1539169462; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=5Q3MKK44WAcBg2J6xIGaOWoxqX+sCfQW0OX+huEAlXE=; b=GSuA8q4GNqvmNbtNinHG8dmKeVVx4eL6FCzbD0YHgd3cV253xcqNNxp0 6Ol6W7v+JnCTNZ3JbohEqtkventgObUjimBVHW8Zd8XXxGtIKvvovN5gh pehL5/78Y6sbIvGt7bDPVtfA5wEM65I+RNuXUZp15CmyfQ7uazUUPN+fv w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AGAACcZqtb/5tdJa1ZGQEBAQEBAQEBAQEBAQcBAQEBAQGBUYEXd2V/KAqDaogVjC+BaCWRE4U8gXoLhGwCF4NjITQYAQMBAQIBAQJtKIU4AQEBAQMjCkwQAgEIEQMBAisCAgIwHQgCBAENBYMhAYEdZKJugS6KHIp6F4IAgTkME4IeLoFBgyc2gmExgiYCjWyFd4kkCQKQKxePNIcbjU8CERSBJR04J4EucBU7KgGCQYIxHI4Hb4wkgR4BAQ
X-IronPort-AV: E=Sophos;i="5.54,306,1534809600"; d="scan'208,217";a="176299713"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Sep 2018 11:04:21 +0000
Received: from XCH-ALN-014.cisco.com (xch-aln-014.cisco.com [173.36.7.24]) by rcdn-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id w8QB4LmO018786 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 26 Sep 2018 11:04:21 GMT
Received: from xch-aln-018.cisco.com (173.36.7.28) by XCH-ALN-014.cisco.com (173.36.7.24) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 26 Sep 2018 06:04:20 -0500
Received: from xch-aln-018.cisco.com ([173.36.7.28]) by XCH-ALN-018.cisco.com ([173.36.7.28]) with mapi id 15.00.1395.000; Wed, 26 Sep 2018 06:04:20 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Tom Kristensen (tomkrist)" <tomkrist@cisco.com>, bianxg <bianxg@agilevideo.net>, "gonzalo.camarillo" <gonzalo.camarillo@ericsson.com>
CC: drage <drage@alcatel-lucent.com>, tomkri <tomkri@ifi.uio.no>, jo <jo@comnet.tkk.fi>, "bfcpbis@ietf.org" <bfcpbis@ietf.org>
Thread-Topic: Can not find Transaction ID 154 in Figure 48 in draft-ietf-bfcpbis-rfc4582bis-16 Appendix A.
Thread-Index: AQHUT4+PKeJI6eZfkkOfa5npRP/cTKUC55IA
Date: Wed, 26 Sep 2018 11:04:20 +0000
Message-ID: <28F5806F-9060-4616-86CF-04F5354064F2@cisco.com>
References: <tencent_79242B4D742614286A826752@qq.com> <1537180475733.38859@cisco.com> <2E668E1E-0D49-49AD-930D-F9A97A953160@cisco.com>
In-Reply-To: <2E668E1E-0D49-49AD-930D-F9A97A953160@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.2.180910
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.204.1]
Content-Type: multipart/alternative; boundary="_000_28F5806F9060461686CF04F5354064F2ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.24, xch-aln-014.cisco.com
X-Outbound-Node: rcdn-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/bfcpbis/yTX_VLxPcXwXygm4Qg7-3z14Sao>
Subject: Re: [bfcpbis] Can not find Transaction ID 154 in Figure 48 in draft-ietf-bfcpbis-rfc4582bis-16 Appendix A.
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 26 Sep 2018 11:04:29 -0000

Adding the list to verify if the proposed change is correct and sufficient.

Cheers,
Charles

From: Charles Eckel <eckelcu@cisco.com>
Date: Tuesday, September 18, 2018 at 10:38 PM
To: Tom Kristensen <tomkrist@cisco.com>, bianxg <bianxg@agilevideo.net>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Cc: Keith Drage <drage@alcatel-lucent.com>, Tom Kristensen <tomkri@ifi.uio.no>, Joerg Ott <jo@comnet.tkk.fi>
Subject: Re: Can not find Transaction ID 154 in Figure 48 in draft-ietf-bfcpbis-rfc4582bis-16 Appendix A.

Isn’t it implicitly ack-ing transaction ID 126?
I believe the information in the figure is correct. The text description following the figure would need to be updated as follows:

OLD:
   Note that in Figure 48, the FloorRequestStatus message from the floor
   control server to the floor participant is a transaction-closing
   message as a response to the client-initiated transaction with
   Transaction ID 154.
NEW:
   Note that in Figure 48, the FloorRequestStatus message from the floor
   control server to the floor participant is a transaction-closing
   message as a response to the client-initiated transaction with
   Transaction ID 126.



Tom, Bian, do you agree?

Thanks,
Charles

From: Tom Kristensen <tomkrist@cisco.com>
Date: Monday, September 17, 2018 at 3:34 AM
To: bianxg <bianxg@agilevideo.net>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Cc: Keith Drage <drage@alcatel-lucent.com>, Tom Kristensen <tomkri@ifi.uio.no>, Joerg Ott <jo@comnet.tkk.fi>, Charles Eckel <eckelcu@cisco.com>
Subject: SV: Can not find Transaction ID 154 in Figure 48 in draft-ietf-bfcpbis-rfc4582bis-16 Appendix A.


Good catch!

So yes, you are right and this is wrong - from what I can understand too.



The FloorRequestStatus​ that is implicitly ack-ing has transaction ID 123, the same as the initial FloorRequest.



-- Tom

________________________________
Fra: bianxg <bianxg@agilevideo.net>
Sendt: 17. september 2018 12:15
Til: gonzalo.camarillo
Kopi: drage; Tom Kristensen (tomkrist); tomkri; jo; Charles Eckel (eckelcu)
Emne: Can not find Transaction ID 154 in Figure 48 in draft-ietf-bfcpbis-rfc4582bis-16 Appendix A.


Hi,

I can not find  Transaction ID 154 in Figure 48 in draft-ietf-bfcpbis-rfc4582bis-16 Appendix A. Or my wrong understand. Thanks.

Note that in Figure 48, the FloorRequestStatus message from the floor

   control server to the floor participant is a transaction-closing

   message as a response to the client-initiated transaction with

   Transaction ID 154.  As such, it is not followed by a

   FloorRequestStatusAck message from the floor participant to the floor

   control server.

Bian