IETF Logo Mail Archive

Re: [tram] [RTCWEB] [TRAM] Protesting: Requesting TRAM Charter Clarification regardig Milestone 3: TURN server auto-discovery mechanism for enterprise and ISPs

"Cullen Jennings (fluffy)" <fluffy@cisco.com> Wed, 26 February 2014 01:08 UTC

Return-Path: <fluffy@cisco.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65E781A081D; Tue, 25 Feb 2014 17:08:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.048
X-Spam-Level:
X-Spam-Status: No, score=-115.048 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, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] 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 FyYRhFPCjTe1; Tue, 25 Feb 2014 17:08:10 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 250671A07E6; Tue, 25 Feb 2014 17:08:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1168; q=dns/txt; s=iport; t=1393376889; x=1394586489; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=4Qs9+nTll9I033HCkpX0hQUbPUAzdcmj8dLGg2AZ5uE=; b=N5lGxS8zpkIFbHbCUFYd+v7U/1mYWf32n1gXsCgZfXKDOysGUH9sib60 KWJxF0meuqoJbBT3kVG+tsnqGXrIQa3KYAm4I+cePd0xzcZiZ3hCsgYTw T+1FC7kb7WLNwEvpXGGsjTB7/tqA8Zwsby52lSYZBL4Xdb7xhuAAJAaeQ M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag4FAIo9DVOtJV2Z/2dsb2JhbABZgwiBDbx7gRcWAXSDfQEBAQMBeRACAQgYIwsyJQIEAQ0Fh3wIwCUXjkEBARwzB4MjgRMBA4kLjwuSFIFtgT6BcTk
X-IronPort-AV: E=Sophos;i="4.97,863,1389744000"; d="scan'208";a="303476557"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-9.cisco.com with ESMTP; 26 Feb 2014 01:08:09 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s1Q188Jb029714 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 26 Feb 2014 01:08:09 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.205]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0123.003; Tue, 25 Feb 2014 19:08:08 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Karl Stahl <karl.stahl@intertex.se>, IESG IESG <iesg@ietf.org>
Thread-Topic: [tram] [RTCWEB] [TRAM] Protesting: Requesting TRAM Charter Clarification regardig Milestone 3: TURN server auto-discovery mechanism for enterprise and ISPs
Thread-Index: AQHPMbSdf/e29IVb6Eq4DfCgCp5RAprHHxqAgAAAs4A=
Date: Wed, 26 Feb 2014 01:08:08 +0000
Message-ID: <6031F972-6ECA-4E56-A36C-E2F4A336B718@cisco.com>
References: <20140214030712.30321.21888.idtracker@ietfa.amsl.com> <CAKhHsXGzA=ZTFGTK7ht9hQbfG70iqKrDtxrZCdQNNMzBYZCk8A@mail.gmail.com> <530604ea.c5bf440a.5cfd.ffffde18SMTPIN_ADDED_BROKEN@mx.google.com> <CAKhHsXGsp6ma6Ko9op+YFRqSGM_Ex-jFo_fjz69rN0SEHfNK2A@mail.gmail.com> <CALDtMrKb3_38Rs0vaGnpEvNvTYz8YUTo89STvLJNXfkfdipDSQ@mail.gmail.com> <93BEDDC39A54294B9E78C7860516FA4724AA4422@AZ-US1EXMB06.global.avaya.com> <B7FA2629-6D48-4569-BB62-56395C3EE4BC@cisco.com> <04ff01cf31b4$8eb73780$ac25a680$@stahl@intertex.se> <AA208926-C949-4580-B20B-DCF172D3C21B@cisco.com>
In-Reply-To: <AA208926-C949-4580-B20B-DCF172D3C21B@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.66.247.131]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <8A70C41710040141BF2BD55E91D0D999@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/tram/m0JfsyWIeCUTZUOHaUs1Brrrd9k
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, "tram@ietf.org" <tram@ietf.org>, Spencer Dawkins <spencer@wonderhamster.org>
Subject: Re: [tram] [RTCWEB] [TRAM] Protesting: Requesting TRAM Charter Clarification regardig Milestone 3: TURN server auto-discovery mechanism for enterprise and ISPs
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 01:08:15 -0000

resend because the IETF mail lists said I had to many people in the to line 


On Feb 26, 2014, at 9:05 AM, Cullen Jennings <fluffy@cisco.com> wrote:

> 
> 
> On Feb 25, 2014, at 7:02 AM, Karl Stahl <karl.stahl@intertex.se> wrote:
> 
>> To the TRAM WG and RTCWEB WG and ADs:
>> 
>> It must be a clear objective of the TRAM WG that ISPs/NSPs are allowed and encouraged to route quality demanding WebRTC media into their IP pipes that are capable of transporting real-time traffic without quality issues, using TURN servers.
>> 
> 
> Reading the charter, the above is *not* at all a clear objective of the WG (note I am not the chair of this WG or the responsible AD). 
> 
> That said, I think you have pointed out this charter is abysmally vague - it does not say what the WG is not going to do. If I decided to do BGP for routing updates over TURN it would be within the scope of this charter. 
> 
> My advice to the responsible AD is recharter this WG before IETF 90 or close it. I would be glad to help write a charter that is not an infinite blank cheque. 
> 
> 
> 
> 
> 
>

v2.23.0 | Report a Bug | By Email