Re: [rtcweb] [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:05 UTC

Return-Path: <fluffy@cisco.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65FD81A07C2; Tue, 25 Feb 2014 17:05:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.048
X-Spam-Level:
X-Spam-Status: No, score=-110.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 cxSYv_cbsDCK; Tue, 25 Feb 2014 17:05:42 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) by ietfa.amsl.com (Postfix) with ESMTP id D3B1C1A02B7; Tue, 25 Feb 2014 17:05:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=935; q=dns/txt; s=iport; t=1393376741; x=1394586341; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=yNIMfGZtx/M87S1vSY2rtv3mckbqwIPScAeDpkRjC0Q=; b=GNlDzGs3ZLtwtLpQkSTSFSBWU6QrKg2GDd0FWWw+swdfdJ7Io13j4q7n EYbUnI7XCpa/s14Q2pW1KeipCAw7n2bm1WcKDHvitntpt2XRhdZgQ7zGB EQKFMJxm8ghNBR6wNEKn4F1mKGPTgfWJe5DxYHHDN2T0g48sBUbgdKzNO s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhMFAKo8DVOtJV2Y/2dsb2JhbABZgwaBEsEAgRYWdIIlAQEBAwF5BQsCAQg7CzIlAgQBDQWHfQjITxeOHTMHgySBFAEDiRGPJZIogW+BPoIq
X-IronPort-AV: E=Sophos;i="4.97,543,1389744000"; d="scan'208";a="23188606"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-7.cisco.com with ESMTP; 26 Feb 2014 01:05:38 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s1Q15dO2015243 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 26 Feb 2014 01:05:39 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.205]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.03.0123.003; Tue, 25 Feb 2014 19:05:38 -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/e29IVb6Eq4DfCgCp5RAprHHxqA
Date: Wed, 26 Feb 2014 01:05:38 +0000
Message-ID: <AA208926-C949-4580-B20B-DCF172D3C21B@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>
In-Reply-To: <04ff01cf31b4$8eb73780$ac25a680$@stahl@intertex.se>
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: <92E892439623E54DB28673572FBE9B78@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/kvA0Z4KNuvUxIzJyUVPL5CcATiQ
Cc: "tram@ietf.org" <tram@ietf.org>, Spencer Dawkins <spencer@wonderhamster.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] [tram] [RTCWEB] [TRAM] Protesting: Requesting TRAM Charter Clarification regardig Milestone 3: TURN server auto-discovery mechanism for enterprise and ISPs
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 01:05:45 -0000

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.