IETF Logo Mail Archive

Re: [bfcpbis] Updates to draft-ietf-bfcpbis-rfc4583bis required to enable ICE

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Fri, 03 March 2017 15:18 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 83ABA12940F for <bfcpbis@ietfa.amsl.com>; Fri, 3 Mar 2017 07:18:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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, URIBL_BLOCKED=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 NVjuYj8WCg5E for <bfcpbis@ietfa.amsl.com>; Fri, 3 Mar 2017 07:18:52 -0800 (PST)
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 E4C771294BC for <bfcpbis@ietf.org>; Fri, 3 Mar 2017 07:18:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13608; q=dns/txt; s=iport; t=1488554331; x=1489763931; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=EanXCtCUggw5KaKBcd/AtdF6SSuNaK+vwwv9fMFgA6c=; b=S21ehPe4ksydNt5Yzsfq6KNHHV2qkYgdQsNip7L1Etb4ZkzN1bUtuxg7 un0poQ2HGPwWbT5AzTMiS9+8npuuNsDmeri9B32MvVlevEhoCrt/ysThH BShAMMsSCfp2J56oSirasadsTVsb8IpNl7sU61I5WVmqxzQsTwE/WbIgX w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DhAQDIiLlY/5JdJa1eGQEBAQEBAQEBAQEBBwEBAQEBgm45KWGBCQeDV4oKkScfiA2HfoUsgg2GIgIagkc/GAECAQEBAQEBAWIohHABAQEEI1YQAgEIDgMDAQIoAwICAh8RFAkIAgQOBYljAxWzCoImK4cIDYNHAQEBAQEBAQEBAQEBAQEBAQEBAQEBHYhTCIJiglGCChkWglAugjEFm3I6AY4JhCmBe48kiEOCEIhnAR84gQNWFVABhkB2AYhPgQ0BAQE
X-IronPort-AV: E=Sophos;i="5.35,237,1484006400"; d="scan'208,217";a="393041918"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Mar 2017 15:18:51 +0000
Received: from xch-rcd-011.cisco.com (xch-rcd-011.cisco.com [173.37.102.21]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id v23FIoKj000433 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 3 Mar 2017 15:18:50 GMT
Received: from xch-aln-018.cisco.com (173.36.7.28) by XCH-RCD-011.cisco.com (173.37.102.21) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 3 Mar 2017 09:18:50 -0600
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.1210.000; Fri, 3 Mar 2017 09:18:50 -0600
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Roman Shpount <rshpount@turbobridge.com>
Thread-Topic: Updates to draft-ietf-bfcpbis-rfc4583bis required to enable ICE
Thread-Index: AQHSk6JSUjB4HtjJ8UWHVVBUVasJT6GCEOkAgACLzQCAAELKgIAAOqaA
Date: Fri, 03 Mar 2017 15:18:49 +0000
Message-ID: <BFA9F0BB-3793-4409-9A30-D78B9F383227@cisco.com>
References: <CAD5OKxs9NN1CtNYaZEiGUxK-UUs=LwYq=A8n69LZ4REE80EzUQ@mail.gmail.com> <52AB0C16-BED7-4402-8368-3FAC4B3B64BB@cisco.com> <CAD5OKxtir5MYpSMhugr=kR3pKMLVsJew1MV5dvDiW=tWX+sg7A@mail.gmail.com> <CAD5OKxvmZ+mDNR9G=3ZiOeDAYHcHw=W=GHKp1H72JAW4Upq7VA@mail.gmail.com>
In-Reply-To: <CAD5OKxvmZ+mDNR9G=3ZiOeDAYHcHw=W=GHKp1H72JAW4Upq7VA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.1f.0.170216
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.20.182.35]
Content-Type: multipart/alternative; boundary="_000_BFA9F0BB379344099A30D78B9F383227ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/bfcpbis/lo_pEzN8gh7yXZ9oN-1stnjnKzY>
Cc: "Tom Kristensen (tomkrist)" <tomkrist@cisco.com>, Tom Kristensen <tomkri@ifi.uio.no>, "bfcpbis@ietf.org" <bfcpbis@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, "Paul E. Jones" <paulej@packetizer.com>, Christer Holmberg <christer.holmberg@ericsson.com>, Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: [bfcpbis] Updates to draft-ietf-bfcpbis-rfc4583bis required to enable ICE
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 03 Mar 2017 15:18:53 -0000

These additions look good to me.

Cheers,
Charles

From: Roman Shpount <rshpount@turbobridge.com>
Date: Thursday, March 2, 2017 at 7:49 PM
To: Charles Eckel <eckelcu@cisco.com>
Cc: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Tom Kristensen <tomkrist@cisco.com>, Christer Holmberg <christer.holmberg@ericsson.com>, Tom Kristensen <tomkri@ifi.uio.no>, Mary Barnes <mary.ietf.barnes@gmail.com>, Paul Jones <paulej@packetizer.com>, "bfcpbis@ietf.org" <bfcpbis@ietf.org>
Subject: Re: Updates to draft-ietf-bfcpbis-rfc4583bis required to enable ICE

I would like to make to additional corrections to my proposed text.

1. The text for seciton 3 should be update to mention that BFCP version for unreliable transports should be used in case of TCP/DTLS/BFCP:

TCP/DTLS/BFCP, which is realized by running BFCP for unreliable transports on top of DTLS as described in this specification and running DTLS on top of TCP is realized using the framing method defined in RFC4571, with DTLS packets being sent and received instead of RTP/RTCP packets using the shim defined in RFC4571 so that length field defined in RFC4571 precedes each DTLS message.

2. In ICE considerations, I would like to add:

Using ICE with protocols other then UDP/TLS/BFCP and TCP/DTLS/BFCP is outside of scope for this specification.

Thank You,

_____________
Roman Shpount

On Thu, Mar 2, 2017 at 6:49 PM, Roman Shpount <rshpount@turbobridge.com<mailto:rshpount@turbobridge.com>> wrote:
Charles,

On Thu, Mar 2, 2017 at 6:29 PM, Charles Eckel (eckelcu) <eckelcu@cisco.com<mailto:eckelcu@cisco.com>> wrote:
[cue] We define the proto field value UDP/TLS/BFCP in this draft for BFCP over DTLS. Would it not be more straightforward and consistent to define the new proto value as TCP/UDP/TLS/BFCP instead of TCP/DTLS/BFCP?


I am trying to keep proto names as close as possible to draft-ietf-mmusic-dtls-sdp. I understand that there are already implementations which use UDP/TLS/BFCP so we cannot change it to the technically correct value which is UDP/DTLS/BFCP. After all, we are using DTLS transport, which is different from TLS.

Since there are no implementations of TCP/DTLS/BFCP, we should use the technically correct protocol string. There is no UDP layer in TCP/DTLS/BFCP transport stack, since DTLS packets are passed directly to RFC4571 shim. Because of this I think TCP/DTLS/BFCP value is accurate and appropriate.

Regards,
_____________
Roman Shpount

v2.23.0 | Report a Bug | By Email