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 497F9129612 for <bfcpbis@ietfa.amsl.com>; Fri, 3 Mar 2017 07:18:13 -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 33xLwZC02d-1 for <bfcpbis@ietfa.amsl.com>; Fri, 3 Mar 2017 07:18:11 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8C511295C4 for <bfcpbis@ietf.org>; Fri, 3 Mar 2017 07:18:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9530; q=dns/txt; s=iport; t=1488554291; x=1489763891; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=O5Nv8HzXRYoB5I2C+wzxIc5XkMueACjBAcP3vlXBCfw=; b=fb0h09sxlxWgIpzNESJ+n/o2hlfHaTi6lpEIoZMgFj9pOefOKwjf17/4 sZm3ldDSIv1LsGJu6FS/RSD6KCC16/32KVoNJ34sR/KZEh0EBhcpKTCan y2wTOIFLQuPY3XPg7BLkkQ669XVecJG9lsk2kYsHmulqySzu859K6Juhk E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DSAQBJiLlY/4MNJK1eGQEBAQEBAQEBAQEBBwEBAQEBgm5iYYEJB4NXigqRRogNh36FLIINhiICGoJHPxgBAgEBAQEBAQFiKIRwAQEBBCNWEAIBCA4DAwECKAMCAgIfERQJCAIEDgUbiUgDFbMJgiYrhwgNg0cBAQEBAQEBAQEBAQEBAQEBAQEBAQEdiFOCaoJRgiMWglAugjEFm3I6AY4JhCmRH4pTiGcBHziBA1YVUAGGQHYBiE+BDQEBAQ
X-IronPort-AV: E=Sophos;i="5.35,237,1484006400"; d="scan'208,217";a="213509830"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 03 Mar 2017 15:18:10 +0000
Received: from XCH-ALN-014.cisco.com (xch-aln-014.cisco.com [173.36.7.24]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v23FIAa6025599 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 3 Mar 2017 15:18:10 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.1210.3; Fri, 3 Mar 2017 09:18:10 -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:10 -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: AQHSk6JSUjB4HtjJ8UWHVVBUVasJT6GCEOkAgACLzQCAAH1AgA==
Date: Fri, 03 Mar 2017 15:18:10 +0000
Message-ID: <FF99D985-DB93-4F29-8E7F-DD420B3BE98A@cisco.com>
References: <CAD5OKxs9NN1CtNYaZEiGUxK-UUs=LwYq=A8n69LZ4REE80EzUQ@mail.gmail.com> <52AB0C16-BED7-4402-8368-3FAC4B3B64BB@cisco.com> <CAD5OKxtir5MYpSMhugr=kR3pKMLVsJew1MV5dvDiW=tWX+sg7A@mail.gmail.com>
In-Reply-To: <CAD5OKxtir5MYpSMhugr=kR3pKMLVsJew1MV5dvDiW=tWX+sg7A@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_FF99D985DB934F298E7FDD420B3BE98Aciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/bfcpbis/hmSUQnBHgMQEec5xv9HmhTra__I>
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:13 -0000

There is no perfect solution given the mismatch in approach taken originally within rfc4583bis and in draft-ietf-mmusic-dtls-sdp. Your proposal is acceptable to me, and does have the benefit of being both forward and backward compatible.

Cheers,
Charles

From: Roman Shpount <rshpount@turbobridge.com>
Date: Thursday, March 2, 2017 at 3: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

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