Re: [MMUSIC] [Ice] Updated charter

"Pal Martinsen (palmarti)" <> Tue, 22 September 2015 17:52 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 069BC1A9143; Tue, 22 Sep 2015 10:52:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Status: No, score=-14.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Qb0qLLeBNd_X; Tue, 22 Sep 2015 10:52:09 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6B6E91A9140; Tue, 22 Sep 2015 10:52:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=6188; q=dns/txt; s=iport; t=1442944329; x=1444153929; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=xwQum2biSnkfHKSZMGzLcbDIR64RaH9WE0f8cJWky44=; b=PYcpZGxEP+CZReDQxztq4Cd0WGZ9wf8OtKvFKAWmBCyPXzPyusRKTsM0 lAfEmPk03Xikssk9+WsXA0OJnKyfvM6V+5RaPdChVULIlWw8j+eqQerVH CRTNp6EQ/EPBk1XJm2Flyt4GPimj8EDm1Qdy/uKqfXYuo3aLczi58kjz8 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.17,574,1437436800"; d="scan'208";a="29216076"
Received: from ([]) by with ESMTP; 22 Sep 2015 17:51:47 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id t8MHplII001593 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 22 Sep 2015 17:51:47 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 22 Sep 2015 12:51:46 -0500
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1104.5 via Frontend Transport; Tue, 22 Sep 2015 12:51:46 -0500
Received: from ([]) by ([]) with mapi id 14.03.0248.002; Tue, 22 Sep 2015 12:51:46 -0500
From: "Pal Martinsen (palmarti)" <>
To: Ben Campbell <>
Thread-Topic: [Ice] Updated charter
Thread-Index: AQHQ8HmqCfVLzJlXnkSqQH7aqk8/F55JLbmAgAAD24A=
Date: Tue, 22 Sep 2015 17:51:46 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-ID: <>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <>
Cc: "" <>, mmusic <>, "" <>
Subject: Re: [MMUSIC] [Ice] Updated charter
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 22 Sep 2015 17:52:12 -0000

> On 22 Sep 2015, at 19:38, Ben Campbell <> wrote:
> Hi,
> If we hope to have ICE approved as a working group in time for Yokohama, we would need to start the IESG internal review by this Thursday. IMO, this language is about right. I think there's still an open issue about where the SDP bit lives. Can we close on that?

I think the arguments can be summarised as follows.

- Keeping SDP in MMUSIC helps ICE focus on core ICE things
- MMUSIC has a lot of SDP knowledge needed to get things right

I support keeping ICE in ICE and SDP in MMUSIC.


> Thanks!
> Ben.
> On 16 Sep 2015, at 7:17, Pal Martinsen (palmarti) wrote:
>> Hi,
>> Based on list discussion the charter is now updated.
>> For the github draft enthusiasts out there the pull request can be found at:
>> —————— Start —————-
>> Charter for Working Group
>> Interactive Connectivity Establishment was published as RFC 5245 in April 2010. Until recently the protocol had seen rather limited deployment. ICE was slow to achieve widespread adoption, as other mechanisms were already being used by the VoIP industry. This situation has changed drastically as ICE is mandatory to implement in WebRTC, a set of technologies developed at the IETF and W3C to standardize Real Time Communication on the Web.
>> Interactive Connectivity Establishment (ICE) is at the same time a NAT traversal technique, a multihomed address selection technique, and a dual stack address selection technique that works by including a multiplicity of IP addresses and ports in both the request and response messages of a connectivity establishment transaction.  The IP addresses and ports provided by each side are paired and tested by peer-to-peer connectivity checks until one of these pair is selected to transport data. ICE follows the end to end principle where the clients themselves discovers, test and choose the network path to use. It makes no assumptions regarding network topology on the local or remote side.
>> ICE was originally defined for the Offer-Answer (RFC 3264) protocol used by SIP (RFC 3261). Later XMPP (XEP-0176), RTSP (draft-ietf-mmusic-rtsp-nat), RTCWeb (draft-ietf-rtcweb-jsep) and other realtime media establishment protocol have used the protocol. ICE is also used by non-realtime media protocols, like HIP (RFC 5770) and RELOAD (RFC 6940).
>> The goal of the ICE Working Group is to consolidate the various initiatives to update ICE to make it more suitable for the WebRTC environment but also to all the current usages of ICE. Current work in this area includes an updated version of the ICE RFC (ICEbis), Trickle ICE and dualstack/multihomed fairness. It is worth noticing that this work will make ICE more flexible, robust and more suitable for changing mobile environments without major changes to the original ICE RFC. The ICE workgroup will consider new work items that follow this pattern.
>> ICE is an application controlled protocol that leverages a set of network defined protocols. The STUN (RFC 5389), TURN (RFC 5766) and related protocol work done in the TRAM working group must be closely synchronized with the work in this working group. To avoid interoperability issues and unwanted behavior it is desired to increase the interaction with other working groups dealing with network protocols closer to the wire. Example of such work may be, but not limited to; issues regarding multi-homing, multi subnet and prefixes, QoS, transport selection and congestion control. From the application side, the users of ICE, there is a need to make sure what is specified is actually usable. Getting input from the application working groups will be helpful (RTCWEB, HIP, MMUSIC, P2PSIP).
>> Milestones
>> - Jan 2016 Submit Dual-stack Fairness with ICE as Proposed Standard
>> draft-ietf-mmusic-ice-dualstack-fairness
>> - Apr 2016 Submit a revision of ICE (RFC 5245) as Proposed Standard
>> draft-ietf-mmusic-rfc5245bis
>> (draft-ietf-mmusic-ice-sip-sdp remains in MMUSIC)
>> - Jan 2016 Submit Trickle ICE as Proposed Standard
>> draft-ietf-mmusic-trickle-ice
>> (draft-ietf-mmusic-trickle-ice-sip remains in MMUSIC)
>> ————— STOP ———————
>> .-.
>> Pål-Erik
>> _______________________________________________
>> Ice mailing list