[tram] IPv4 and IPv6 allocations

Mallinath Bareddy <mallinath@google.com> Wed, 19 February 2014 15:32 UTC

Return-Path: <mallinath@google.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 2A75C1A04F7 for <tram@ietfa.amsl.com>; Wed, 19 Feb 2014 07:32:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.926
X-Spam-Level:
X-Spam-Status: No, score=-1.926 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] 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 Pm5zFrExfH-6 for <tram@ietfa.amsl.com>; Wed, 19 Feb 2014 07:32:08 -0800 (PST)
Received: from mail-oa0-x22b.google.com (mail-oa0-x22b.google.com [IPv6:2607:f8b0:4003:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 718CA1A05CB for <tram@ietf.org>; Wed, 19 Feb 2014 07:32:08 -0800 (PST)
Received: by mail-oa0-f43.google.com with SMTP id h16so590046oag.30 for <tram@ietf.org>; Wed, 19 Feb 2014 07:32:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=pVhegDc6v13WyNuVfd23+JrpeW5+2pTPE5z4xWPLGk8=; b=M0sPsqvX1OYWBS5mODi9xonT613Vit/a6c8S3QFPEoNzuv1bU6AULFK/fY9/Px7Edl JeO/F0XS/3ivXSWHejw482Rga62Pyy/zkfv1r7nN34mz3cVWqLd4tAFX7cCIP025I9QH ytRPbd2h6sM9lza8W4lT+Hmde0teIj75XR+G9bj4XqODU+oop0wtE5Fb3kT1se3+4lDF QkLy7IjjqZvge+aZMMQXZEl3rwaqY9pGdaFKQr5J1MlpaPomMrPgGXRMNPazQlCcFXET Ab284vsi/Hyvkkmld751xpNP4WV970WA6ZIDoEHTKldtpilVCDlnRjYuradYiyiwlqV4 3UUw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=pVhegDc6v13WyNuVfd23+JrpeW5+2pTPE5z4xWPLGk8=; b=doV7rtOWU5rci3PCD/KyAGcfDBMUaORKMUgiRgrfSsc9kFPVJVusjzgfE/ciW4hpO/ 7gU4YT5PCjwbIDhkzIteIvOpQsxuerG0dJUz+lF/OD3NslKogSFH9ywxf7aCF2sMEo7Y PWMhcFfhWrIyc3vb/t5fAkgfZ4JCyKC2G7VT0t0tefARodHzUErB4QgE4Tc75zJrPwxb gOHOSzuUH+uaBKzSRaHntE9o2zb0QJdPcoCm01+el2hqXN7rUetqjgnhFhUJZbz7QRgM 19U1Ha2UXEAlAm8L9JMiysOf0ZrLWbZRzfIP/GYKmX++sBKBPJyvvJG87m7KXJrlQFLH RxjQ==
X-Gm-Message-State: ALoCoQnYqtTnZkVAzV9OSU8GL9QWB408ds4MZXB6pB7hY1irx6FDTiEDMuaUOdisNH5le/PKaW2DITfTiQTW0ySpxZo2izVqqryh3AtvWDFcI3vzKZrYf7fZUQ7wu7zq/eWI8mr+JBxPeqBSaYKuAZ9Zy7oxDHJcsYYSSx4amX1SrUPJSblfiFxvfuf6GTryvoOyjWhM1ZHX
X-Received: by 10.60.52.101 with SMTP id s5mr32060732oeo.7.1392823925099; Wed, 19 Feb 2014 07:32:05 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.246.102 with HTTP; Wed, 19 Feb 2014 07:31:44 -0800 (PST)
From: Mallinath Bareddy <mallinath@google.com>
Date: Wed, 19 Feb 2014 07:31:44 -0800
Message-ID: <CAJjP_Q9qQ-o=q+UVo=3Q2w2mnUpOG=ihPiGDMRPfrDNhzpiTNg@mail.gmail.com>
To: tram@ietf.org
Content-Type: multipart/alternative; boundary="001a11330d544a663904f2c41759"
Archived-At: http://mailarchive.ietf.org/arch/msg/tram/ooLHQihvM7eXquHbfu6EpTxo14o
Subject: [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 15:32:10 -0000

Hi All,

>From RFC 5766,
     Both the server and client keep track of a value known as the

   5-TUPLE.  At the client, the 5-tuple consists of the client's host
   transport address, the server transport address, and the transport
   protocol used by the client to communicate with the server.  At the
   server, the 5-tuple value is the same except that the client's host
   transport address is replaced by the client's server-reflexive
   address, since that is the client's address as seen by the server.


I have a scenario where Turn client is sending IPv4 and a IPv6 (using
REQUESTED-ADDRESS-FAMILY attribute) allocation requests from the same
host transport address. The reason to send IPv6 allocation request is
to connect to a IPv6 only client.


>From above definition both allocation requests will result in same
5-tuple at the server. How does TURN server demux requests from
client, leading to the proper allocation object?


Regards,

Mallinath