Re: [tram] ALPN identifiers for STUN and TURN
Oleg Moskalenko <mom040267@gmail.com> Thu, 31 July 2014 18:26 UTC
Return-Path: <mom040267@gmail.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 93C871A011D for <tram@ietfa.amsl.com>; Thu, 31 Jul 2014 11:26:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 k4qTveSLQcjL for <tram@ietfa.amsl.com>; Thu, 31 Jul 2014 11:26:19 -0700 (PDT)
Received: from mail-pd0-x231.google.com (mail-pd0-x231.google.com [IPv6:2607:f8b0:400e:c02::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56F921A0314 for <tram@ietf.org>; Thu, 31 Jul 2014 11:26:19 -0700 (PDT)
Received: by mail-pd0-f177.google.com with SMTP id p10so3946252pdj.22 for <tram@ietf.org>; Thu, 31 Jul 2014 11:26:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=CSRz41HxKmfxkDch1qteUargOC0qwkdgoIyBGKfGP4I=; b=b/hCxoh1EDLoS7yhJNRtIqs1nvQe8CfB8taokjQN4i2RDvSH696Oaj2z4PkYeAVer5 kGn66DR/hX2a7zYkjR/L6Hkxrs0za5lWKPwsq/dmqJnt2I3JOPUsiv/JJAaunnd3MGII zIUvkSAlrW2L+oO0ap82g81kzxkHU0yTLuXX1Pg1nB1Ec8p0Wc66yQQTDB9KavfMUUUI mAJqFBZBnHY0VOalIy8DHlD74NmIq5fszyj4CMdZfdf5XLaFRk3vv0Pcp+90grcIWWFX es0JmblkuJQTFHHuJ7eaJ97/7Rn2ph+ndfaEEgTh+MHc5shd2HFc6umCCuUbXfDRPTSp DQ9Q==
X-Received: by 10.66.174.17 with SMTP id bo17mr6519124pac.98.1406831178925; Thu, 31 Jul 2014 11:26:18 -0700 (PDT)
Received: from vpn-pool-10-72-117-65.corp.yahoo.com (nat-dip6.cfw-a-gci.corp.yahoo.com. [209.131.62.115]) by mx.google.com with ESMTPSA id xy4sm21599691pac.19.2014.07.31.11.26.17 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 31 Jul 2014 11:26:18 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_5510735C-2C91-4598-9C2D-C20CD6CECEC9"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Oleg Moskalenko <mom040267@gmail.com>
In-Reply-To: <D0008149.45B7F%praspati@cisco.com>
Date: Thu, 31 Jul 2014 11:26:19 -0700
Message-Id: <1A0EA14B-C138-48DC-9B79-7ECEDB50942C@gmail.com>
References: <D0008149.45B7F%praspati@cisco.com>
To: "Prashanth Patil (praspati)" <praspati@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/tram/VX1PcLcyFdnQ_RWNKeXjyKsn-88
Cc: "tram@ietf.org" <tram@ietf.org>
Subject: Re: [tram] ALPN identifiers for STUN and TURN
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: Thu, 31 Jul 2014 18:26:20 -0000
I am not sure that having separate ALPNs for STUN and TURN is a very good idea. Both are using the same binary protocol, and both are used in similar situations and the boundary between them is rather artificial. Oleg On Jul 31, 2014, at 10:57 AM, Prashanth Patil (praspati) <praspati@cisco.com> wrote: > There was some discussion on the need for separate STUN and TURN identifiers during the TRAM session. Separate identifiers could be useful when middle boxes such as a firewall want protocol identification e.g as described in http://tools.ietf.org/html/draft-hutton-httpbis-connect-protocol-00#section-1. > > Thoughts? > > draft-ietf-tram-alpn-00 currently defines both identifiers. > > -Prashanth > _______________________________________________ > tram mailing list > tram@ietf.org > https://www.ietf.org/mailman/listinfo/tram
- [tram] ALPN identifiers for STUN and TURN Prashanth Patil (praspati)
- Re: [tram] ALPN identifiers for STUN and TURN Oleg Moskalenko
- Re: [tram] ALPN identifiers for STUN and TURN Martin Thomson
- Re: [tram] ALPN identifiers for STUN and TURN Justin Uberti
- Re: [tram] ALPN identifiers for STUN and TURN Martin Thomson
- Re: [tram] ALPN identifiers for STUN and TURN - w… Paul Kyzivat
- Re: [tram] ALPN identifiers for STUN and TURN Brandon Williams
- Re: [tram] ALPN identifiers for STUN and TURN Brandon Williams
- Re: [tram] ALPN identifiers for STUN and TURN Prashanth Patil (praspati)
- Re: [tram] ALPN identifiers for STUN and TURN Martin Thomson
- Re: [tram] ALPN identifiers for STUN and TURN Tirumaleswar Reddy (tireddy)