IETF Logo Mail Archive

Re: [bfcpbis] WGLC comments on draft-ietf-bfcpbis-rfc4583bis-17

"Tom Kristensen (tomkrist)" <tomkrist@cisco.com> Tue, 18 July 2017 13:57 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 E6C5512785F for <bfcpbis@ietfa.amsl.com>; Tue, 18 Jul 2017 06:57:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level:
X-Spam-Status: No, score=-14.523 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 LfDBhq5-QvLM for <bfcpbis@ietfa.amsl.com>; Tue, 18 Jul 2017 06:57:27 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 843FA126CB6 for <bfcpbis@ietf.org>; Tue, 18 Jul 2017 06:57:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2292; q=dns/txt; s=iport; t=1500386247; x=1501595847; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=qNOb0OMHuINZGA9mZziU+lWOhzIJkbRurFaMh21LthI=; b=MhSgmDBbYO5bptF04WhgXz00c+Bxsh/jCfuVtYnqyG72YxnVkUQUDMww uXHUDNS2G6lwSs5cIeHe4B1vKkDvY6ZU17KgX4ir8bH4QytAeshee4Pk4 nhvdEmqIjvas7XRN0qC9V0WFVBor+W6txORQjzdb/KcKP5GCM5V60Ueza 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DVAAB5E25Z/5BdJa1cGgEBAQECAQEBAQgBAQEBg1pkgRQHhjeHTZV1AQORcIIRIQuETE8Cg1E/GAECAQEBAQEBAWsohRkCAQMBAWUHCxACASklDxgLJQIEAQ0Fii8QsHSLDAEBAQEBAQEBAQEBAQEBAQEBAQEBARgFgyiDTYFhh3iGCgWfNAKUFJIvlVYBHziBCnUVSYcWdodLgQ0BAQE
X-IronPort-AV: E=Sophos;i="5.40,378,1496102400"; d="scan'208";a="275081888"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Jul 2017 13:57:20 +0000
Received: from XCH-RTP-019.cisco.com (xch-rtp-019.cisco.com [64.101.220.159]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id v6IDvKXn013437 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 18 Jul 2017 13:57:20 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-019.cisco.com (64.101.220.159) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 18 Jul 2017 09:57:19 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Tue, 18 Jul 2017 09:57:19 -0400
From: "Tom Kristensen (tomkrist)" <tomkrist@cisco.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "bfcpbis@ietf.org" <bfcpbis@ietf.org>
CC: Tom Kristensen <2mkristensen@gmail.com>
Thread-Topic: WGLC comments on draft-ietf-bfcpbis-rfc4583bis-17
Thread-Index: AQHS/u8RWy/WH/x8I0ykG34nrHqsz6JZnTwm
Date: Tue, 18 Jul 2017 13:57:19 +0000
Message-ID: <1500386249900.83625@cisco.com>
References: <E536B846-B992-48C7-B1A6-4134C58C9B43@cisco.com>
In-Reply-To: <E536B846-B992-48C7-B1A6-4134C58C9B43@cisco.com>
Accept-Language: nb-NO, en-US
Content-Language: nb-NO
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.244.90]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/bfcpbis/ZkWRLYhTJVA0s3VZUPli_Y0sEmI>
Subject: Re: [bfcpbis] WGLC comments on draft-ietf-bfcpbis-rfc4583bis-17
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 18 Jul 2017 13:57:29 -0000

Yes, I agree with all of the editorial fixes, language clarifications and also the MUST added on page 6.

Is incorporated if no objections or other input are received here.

-- Tom
________________________________________
Fra: bfcpbis <bfcpbis-bounces@ietf.org> på vegne av Charles Eckel (eckelcu)
Sendt: 17. juli 2017 13:23
Til: bfcpbis@ietf.org
Emne: [bfcpbis] WGLC comments on draft-ietf-bfcpbis-rfc4583bis-17

(as an individual)

I have reviewed the draft. I do not have any technical or major issues with it.
I do have some editorial comments and suggestions.

Globally
Use reestablish or re-establish but not both.

Pg 1.
s/ Changes from RFC 4583 are summarized in Section 14/ Changes from RFC 4583 are summarized in Section 15

Pg 4.
s/ both the offerer and the answerer act/ both endpoints act

Pg 6.
s/ When this attribute appears in an answer, it only carries one role/ When a “floorctrl” attribute appears in an answer, it MUST include one and only role

Pg 9.
s/ the answerer which may be the client or the floorcontrol server acts/ the answerer, which may be the client or the floorcontrol server, acts

Pg 10.
s/ same BFCP session and DTLS associations/ same BFCP session and DTLS association

Pg 11.
s/ the SDP 'fingerprint' attribute [7], if the endpoint supports, and is willing to use, a cipher suite with an associated certificate./ the SDP 'fingerprint' attribute [10].

Pg 14.
s/ If the BFCP connection is carried on top of TCP, and unless the offerer wants to re-establish an existing TCP connection, the offerer MUST associate an SDP connection attribute, with an 'existing' value, with the 'm' line/ If the BFCP connection is carried on top of TCP and the offerer does not want to re-establish an existing TCP connection, the offerer MUST associate an SDP connection attribute with an 'existing' value with the 'm' line

Cheers,
Charles



_______________________________________________
bfcpbis mailing list
bfcpbis@ietf.org
https://www.ietf.org/mailman/listinfo/bfcpbis

v2.23.0 | Report a Bug | By Email