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

Harald Alvestrand <harald@alvestrand.no> Wed, 30 September 2015 15:04 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51B691B5E34; Wed, 30 Sep 2015 08:04:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 mXoCmFBplBvO; Wed, 30 Sep 2015 08:04:53 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) by ietfa.amsl.com (Postfix) with ESMTP id 50E4A1B5908; Wed, 30 Sep 2015 08:04:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id E69007C5CE1; Wed, 30 Sep 2015 17:04:51 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nkthpQhziYDu; Wed, 30 Sep 2015 17:04:50 +0200 (CEST)
Received: from [192.168.1.17] (unknown [188.113.88.47]) by mork.alvestrand.no (Postfix) with ESMTPSA id 943447C5CE0; Wed, 30 Sep 2015 17:04:50 +0200 (CEST)
To: "Pal Martinsen (palmarti)" <palmarti@cisco.com>, "ice@ietf.org" <ice@ietf.org>
References: <C5E17AE1-DDED-4FC1-8BA6-D2D811B77FFD@cisco.com>
From: Harald Alvestrand <harald@alvestrand.no>
Message-ID: <560BFA12.9060908@alvestrand.no>
Date: Wed, 30 Sep 2015 17:04:50 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <C5E17AE1-DDED-4FC1-8BA6-D2D811B77FFD@cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/SybeX7E9BvEbbPOnXSJiKSAPShQ>
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] [Ice] 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: Wed, 30 Sep 2015 15:04:56 -0000

I like this charter.

Only one linguistic comment:

"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."

Everything before "this work" is linguistic fluff. Can we simply say
"This work will make ICE ...."?



Den 25. sep. 2015 11:18, skrev Pal Martinsen (palmarti):
> Hi,
> 
> 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).
> 
> 
> .-.
> Pål-Erik
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Ice mailing list
> Ice@ietf.org
> https://www.ietf.org/mailman/listinfo/ice
>