Re: [tram] IPv4 and IPv6 allocations

Oleg Moskalenko <mom040267@gmail.com> Wed, 19 February 2014 20:18 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 CA6A81A022E for <tram@ietfa.amsl.com>; Wed, 19 Feb 2014 12:18:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 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, 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 WHvrHACEkUBH for <tram@ietfa.amsl.com>; Wed, 19 Feb 2014 12:18:26 -0800 (PST)
Received: from mail-pd0-x233.google.com (mail-pd0-x233.google.com [IPv6:2607:f8b0:400e:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 14D431A0527 for <tram@ietf.org>; Wed, 19 Feb 2014 12:18:26 -0800 (PST)
Received: by mail-pd0-f179.google.com with SMTP id fp1so833662pdb.10 for <tram@ietf.org>; Wed, 19 Feb 2014 12:18:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=to+vMwf/F7wpC+EYb8EjytJ12rRxYtzlUyAsuWU9+JY=; b=Int97zw4gA3ZsdHQFA++gLjF+YZNH9YbzviLo/Y+yCUv/Isg5NFfI0YBGvHzI/pEnp ySMPEnuC22jYkPkopXmr/kkMff/ZF7mxXU81+Bfwa3e3umcDqrA1cJwzryyU+haaURUC EXL8ye52k7qhTkDG+7vjLkqaNyG6V54H0H3kV7yJaQOxLfrvznNWztG6DrgnvsHrAdnK eQDr9CsETWMDrfpylge+YzXZEqEADBK4Fw3DrBCBcPGL70bdKsrdrxjWA6iFsqFSnE0v miv+UeRvUtGJE8n8XqxOX5UVBQ/66xPsb64oSUKfdn/z/0YjzyxCB00uTGfps74mrLsY 4UGg==
X-Received: by 10.68.212.10 with SMTP id ng10mr4513674pbc.95.1392841102896; Wed, 19 Feb 2014 12:18:22 -0800 (PST)
Received: from ?IPv6:2001:4998:effd:600:4979:a525:6699:cd73? ([2001:4998:effd:600:4979:a525:6699:cd73]) by mx.google.com with ESMTPSA id ix5sm3397949pbd.36.2014.02.19.12.18.22 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 19 Feb 2014 12:18:22 -0800 (PST)
References: <CAJjP_Q9qQ-o=q+UVo=3Q2w2mnUpOG=ihPiGDMRPfrDNhzpiTNg@mail.gmail.com> <5304D0CA.9020201@viagenie.ca> <E836DCC6-A996-4201-A160-C9B2CC60B830@cisco.com> <5304DF60.7020200@viagenie.ca> <C7690C6E-9B85-4F0F-920B-446263D34D06@cisco.com> <5304E60F.1020807@viagenie.ca> <5304E9AE.5070202@viagenie.ca> <93BEDDC39A54294B9E78C7860516FA4724AA3FB7@AZ-US1EXMB06.global.avaya.com> <CAJjP_Q9F7bbP_ag3ask5v-ikR1Jh4vBUHuB7J+XQxZsUnzG3dQ@mail.gmail.com> <E38E346C-2AEE-4524-B99D-832337B6B678@cisco.com> <53050EBC.3040903@viagenie.ca>
Mime-Version: 1.0 (1.0)
In-Reply-To: <53050EBC.3040903@viagenie.ca>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-Id: <74E1C6E2-E63E-4AB0-B085-30350A6B467C@gmail.com>
X-Mailer: iPhone Mail (10B350)
From: Oleg Moskalenko <mom040267@gmail.com>
Date: Wed, 19 Feb 2014 12:18:22 -0800
To: Simon Perreault <simon.perreault@viagenie.ca>
Archived-At: http://mailarchive.ietf.org/arch/msg/tram/CfR2af0DIjgjnmoIEyBjrddpYwA
Cc: "Pal Martinsen (palmarti)" <palmarti@cisco.com>, Mallinath Bareddy <mallinath@google.com>, "tram@ietf.org" <tram@ietf.org>, "Yoakum, John H (John)" <yoakum@avaya.com>
Subject: Re: [tram] IPv4 and IPv6 allocations
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, 19 Feb 2014 20:18:28 -0000

If the client explicitly requested an ip family - why the server must waste resources and allocated a useless (possibly) socket of a different family ?

The server resources must be taken into account, too.

Sent from my iPhone

On Feb 19, 2014, at 12:06 PM, Simon Perreault <simon.perreault@viagenie.ca> wrote:

> Le 2014-02-19 14:58, Pal Martinsen (palmarti) a Ă©crit :
>> Reading RFC5766 they use language that indicates that you will only
>> receive one XOR-RELAYED-ADDRESS attribute. An old client that receives
>> two might pick the wrong one, and get confused since he asked for a IPv4
>> address and got a IPv6 address. There is no way for the client to get
>> out of that situation. (Furiously checking my own TURN client
>> implementation…)
> 
> Backwards compatibility is why we can't have nice things... ;)
> 
> How about we specify which XOR-RELAYED-ADDRESS parameter goes first? We
> can expect older clients to only look at the first one. So if you don't
> include REQUESTED-ADDRESS-FAMILY, the server returns both IPv4 and IPv6,
> and puts IPv4 first. If you do include REQUESTED-ADDRESS-FAMILY, the
> server still allocates two, the requested family is first in the
> response. If that works with existing clients (and it would be easy to
> try those we know), then we can have our cake and it it too!
> 
>> I think it would be better for the client to include two
>> REQUESTED-ADDRESS-FAMILY attributes in the allocation request instead.
>> If the server supports that everything is fine. If the TURN server
>> responds with only one RELAY address, the client would notice and could
>> easily request the other address family on a different 5-tuple. Same
>> goes if the TURN server return an error, the client can go back to old
>> behaviour. 
> 
> That's a fine workaround.
> 
> Simon
> -- 
> DTN made easy, lean, and smart --> http://postellation.viagenie.ca
> NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
> STUN/TURN server               --> http://numb.viagenie.ca
> 
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram