[MMUSIC] Fwd: [dispatch] New version of the proposed charter

[Forwarding just to MMUSIC to account for mail filters]

-------- Forwarded Message --------
Subject: 	[dispatch] New version of the proposed charter
Date: 	Wed, 2 Sep 2015 06:21:02 -0600
From: 	Marc Petit-Huguenin <petithug@acm.org>
To: 	ice@ietf.org
CC: 	DISPATCH list <dispatch@ietf.org>, mmusic@ietf.org <mmusic@ietf.org>
Followup-To: 	ice@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Please find below a new version of the proposed charter, trying to take in account all the comments so far.

The discussions are taking place in the ice mailing-list, please do not cross-post.

Thanks.

- ---------------------------------------------------------------------------------

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. 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 synchronised with the work in this working group. Synching with other network related working groups to make sure existing mechanisms like QoS, congestion control and other networking mechanisms still work would be essential if we want to improve how ICE works (MIF, TAPS, TSWG, HOMENET, etc...). 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 essential (RTCWEB, HIP, MMUSIC, P2PSIP).

Milestones

     Jun 2016 Submit Dual-stack Fairness with ICE as Proposed Standard
     Apr 2016 Submit a revision of ICE (RFC 5245) as Proposed Standard
     Jan 2016 Submit Trickle ICE as Proposed Standard

- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJV5umuAAoJECnERZXWan7Ec9AQANIImmE2JC98QoBfq5MEGa01
w8gfLivIXT/Vx5BW3sGHQTv24dznMbwhMGKGwlizGYU0olgxGqc2VasogmvNrD5J
9PwMOHPzPxJe5rIVHMseiN8mk8DtPKVPmDoBZZt1T9ehP2yajYjRys9uFKwZiqhx
+WJF6rxl/eRxmV6oF41m4VSs/UiN7inTMc8mnKvfi6TLdpInELiKHgnb6VxeW1N+
N6JU7TnG4MVYzUVTLPh5Di8BTCWVthOTqFEwJaGw8gcNA8ATDtx+XbTR2dAv3u0x
WLzNep25LRcukn7UyPQaCZWaptIlqJJzzPit3w+oCuJlc5KTRv/SoODJuR1j4pS9
Lxj0ShAMwSCSfFg3MWIUP19+iE7QZcibh9WWHCY3LZWzOMD2uqLiIuH/OcJbwoIE
c7kcd/m9oOxU0NWYNUYBIhFWbX5fg/bIeW+D3uQN9P9HDscs2XpWlwsL1M6ad2mC
YtA0Mzd4E7PT18Q37eRcVcVeUBF+AF1gpqkUoBXKnZUTiUxIs8nORP9cLpywFaBz
JhjganbYvvgDbPS6gnCSlQbMDlofpTWygfA8FT1FJ94wolv2pcPIH09ofDRYO8zM
5fqZuDkD9BFCKCuFzm/hxyeZTaHDB0pfe+wLN5Eccll06G7pOcMjR/8Q4SiR1l3Q
LCNPefFKYJgT/SFpbL6k
=3YsX
-----END PGP SIGNATURE-----

_______________________________________________
dispatch mailing list
dispatch@ietf.org
https://www.ietf.org/mailman/listinfo/dispatch
.