IETF Logo Mail Archive

Re: [MMUSIC] m= line protocol in case of ICE

Paul Kyzivat <paul.kyzivat@comcast.net> Thu, 17 November 2016 16:24 UTC

Return-Path: <paul.kyzivat@comcast.net>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B25971296E0 for <mmusic@ietfa.amsl.com>; Thu, 17 Nov 2016 08:24:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
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 orTSvBnKtHY6 for <mmusic@ietfa.amsl.com>; Thu, 17 Nov 2016 08:23:58 -0800 (PST)
Received: from resqmta-ch2-01v.sys.comcast.net (resqmta-ch2-01v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49CA1129601 for <mmusic@ietf.org>; Thu, 17 Nov 2016 08:23:58 -0800 (PST)
Received: from resomta-ch2-19v.sys.comcast.net ([69.252.207.115]) by resqmta-ch2-01v.sys.comcast.net with SMTP id 7PSvcUZYgTaLw7PThcoi1n; Thu, 17 Nov 2016 16:23:57 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1479399837; bh=VcCyOI6HZzZTBF7pJuvhwKHF/+n0seUoGq+lTq10IA4=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=fDgqlOWLtVCIKZnfj6Qi7cYP9q3vAGpjj3yulSylaqkFNdktegAMyztC7VzBW3tEU vFDnrdq95ceHYAoQ4yFDbxc8cCovAujBkVTKwjYrIH/ZT5nOxtjb+HYvhL6lQKJYCA GxLIj+CNW0YVviF+islLvnXTKXzjYluCLIiyEeOD0WlCd+gTkeOkC4a/8+FfNpDv1d 7YDB2JO4TKw1xD+FkJpAMGrq2Rs3U15ag1Bw5NqE4FxDewEe9hDKlFxGJBVH6qZSlM D1YaZeRbm12Z6LQGLDlY5hZsB1x3wZxAdbqZuWHdVHI+n+AfaTwEFhPRvU8wmpa7df uWy7zliVV6EHw==
Received: from [192.168.1.110] ([73.186.127.100]) by resomta-ch2-19v.sys.comcast.net with SMTP id 7PTgc2FWGdc0A7PTgc7YQp; Thu, 17 Nov 2016 16:23:57 +0000
To: mmusic@ietf.org
References: <CAD5OKxuhvCz82+7JK8QrArtrYcjV9+b7vWMpWRnCjNbrL++srA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BE3AE83@ESESSMB209.ericsson.se>
From: Paul Kyzivat <paul.kyzivat@comcast.net>
Message-ID: <e775cc43-2903-f70a-5a54-273365d47f1f@comcast.net>
Date: Thu, 17 Nov 2016 11:23:56 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BE3AE83@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfHuy/QyQhZssuMManIPuZHPF/x0MpfrKUm1uNw02awR5AHyTTzsUKlwIV7XlgN94WQQ7j46sstrHs2SUdvadp7xgjgbFWMCbzWA3JoD9367O9qVFS0JC EMdk734Fn5v6lNXMCbGZp1tzLVAeJ1y+/ldLtq3MVfLMlZNp/yRMhOYrTgDIlqU7nshQdxKx7ZI6Vw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/FTPBP8-2jyLnbS7Hy8VLQiciWk0>
Subject: Re: [MMUSIC] m= line protocol in case of ICE
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Nov 2016 16:24:03 -0000

On 11/16/16 8:44 PM, Christer Holmberg wrote:

> If we decide to move forward with such approach, we need to ask
> ourselves whether must-support-UDP should be an ICE requirement (in
> which case the suggestion should be brought to the ICE WG) or whether it
> should only be an ICE-using-SIP-SDP requirement.

If it were solely an ICE-using-SIP-SDP requirement, then that would 
limit interoperability between a sip endpoint and a non-sip endpoint. 
That would be unfortunate.

	Thanks,
	Paul

v2.23.0 | Report a Bug | By Email