[MMUSIC] ICE WG Charter version 2 (Proposed changes)

"Pal Martinsen (palmarti)" <palmarti@cisco.com> Fri, 25 September 2015 09:18 UTC

Return-Path: <palmarti@cisco.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 04B7F1A026C; Fri, 25 Sep 2015 02:18:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Status: No, score=-14.51 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id eSjeiSk1n--g; Fri, 25 Sep 2015 02:18:33 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF8AD1A026A; Fri, 25 Sep 2015 02:18:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11514; q=dns/txt; s=iport; t=1443172712; x=1444382312; h=from:to:cc:subject:date:message-id:mime-version; bh=36ziwXjCVJyYcm/SsKusABQutoTKv62Y1v7eQNuVNjw=; b=FjPbMTUKGPTjX3jQ/rn6U8QoQWS7Z/GIf5nyPlzXoJqavGdwTTx7dqht wvgAlHq5iaiZInc6FQBRVMnaA+6ft0sHBXNAOqHLgp71LXv4/v/AesFmc KgXzcykltVOxXu8RbNBOPnpdsJeBEl3UwBQEwRjINZUQdCoWxPRdWSRwn 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos; i="5.17,585,1437436800"; d="scan'208,217"; a="30093669"
Received: from alln-core-2.cisco.com ([]) by rcdn-iport-8.cisco.com with ESMTP; 25 Sep 2015 09:18:31 +0000
Received: from XCH-ALN-016.cisco.com (xch-aln-016.cisco.com []) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t8P9IVnq020310 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 25 Sep 2015 09:18:31 GMT
Received: from xch-rcd-019.cisco.com ( by XCH-ALN-016.cisco.com ( with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 25 Sep 2015 04:18:31 -0500
Received: from xch-rcd-019.cisco.com ([]) by XCH-RCD-019.cisco.com ([]) with mapi id 15.00.1104.000; Fri, 25 Sep 2015 04:18:30 -0500
From: "Pal Martinsen (palmarti)" <palmarti@cisco.com>
To: "ice@ietf.org" <ice@ietf.org>
Thread-Topic: ICE WG Charter version 2 (Proposed changes)
Thread-Index: AQHQ93MlxzAmLp9sPUWiA0FY3Fud+Q==
Date: Fri, 25 Sep 2015 09:18:30 +0000
Message-ID: <C5E17AE1-DDED-4FC1-8BA6-D2D811B77FFD@cisco.com>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_C5E17AE1DDED4FC18BA6D2D811B77FFDciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/xd5QetKkCaaimrOtsq8NDdAEagY>
Cc: mmusic <mmusic@ietf.org>
Subject: [MMUSIC] ICE WG Charter version 2 (Proposed changes)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 25 Sep 2015 09:18:35 -0000


Based on mailing-list discussions i propose the following changes:
(A pull request can be found at: https://github.com/petithug/icewg/pull/5)

- Merge section 1 and 3. Moved former 2 to 1.
Better introduction to what ICE is and having all the history in the same section. The intended effect of the edit is to emphasise the versatility of ICE and maybe attract more “network” people to attend join the wg.

- Rewrote the start of the goal section to pass strict parsers.
“The goal of the ICE Working Group is to consolidate the various initiatives to update and improve ICE, and to help ensure suitability and consistency in the environments ICE operates in.”

I wanted to remove webRTC from the sentence. If WG FOO comes with the same amount of positive energy to help improve ICE  I think it would deserve to get the same amount of attention.

The charter would then look like:

Charter for Working Group

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. It makes no assumptions regarding network topology on the local or remote side.

Interactive Connectivity Establishment was published as RFC 5245 in April 2010. Until recently the protocol had seen rather limited deployment. 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. 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 and improve ICE, and to help ensure suitability and consistency in the environments ICE operates in. 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, PPSP).