IETF Logo Mail Archive

Re: [quicwg/base-drafts] SOCKS over QUIC (#2518)

madhanraj <notifications@github.com> Sun, 07 April 2019 06:55 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1D521201D8 for <quic-issues@ietfa.amsl.com>; Sat, 6 Apr 2019 23:55:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Level:
X-Spam-Status: No, score=-6.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
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 Dt_YZ6UsJ596 for <quic-issues@ietfa.amsl.com>; Sat, 6 Apr 2019 23:55:18 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A677F1201C3 for <quic-issues@ietf.org>; Sat, 6 Apr 2019 23:55:17 -0700 (PDT)
Date: Sat, 06 Apr 2019 23:55:16 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1554620116; bh=eC5fHq+33ehl+WDvaf+7NUv6vCDVGv777gyvGh+9RSA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mh3PAU5wsCt8dePAK0ZsW+ktv6vdDwvAeJFHBIHSdlXLu1o2qAvAZjJ1mi0rZRMdo jip6IYebsMCEHuwrdjhOP8fa8BGoNibpzQipHI+XCewlPBqTByG55Q8NJva4ZWfEP+ iUh311eeK7svggkY5f495sQJoWsnKk4MMrvmapPY=
From: madhanraj <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abab6edda169bc1c7026b36ec45e97e855764d381192cf0000000118c160d492a169ce19071b33@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2518/480564454@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2518@github.com>
References: <quicwg/base-drafts/issues/2518@github.com>
Subject: Re: [quicwg/base-drafts] SOCKS over QUIC (#2518)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ca99ed42e641_6ad33f9723cd45c080262f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: madhanraj
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/LtsLYplcX8rTVE-xIEnltQRooFc>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Apr 2019 06:55:20 -0000

Thanks .. I missed it as it was labelled closed. We have designed and experimented in our Samsung Lab and find the solution promising from the legacy. Will share the draft and all the results shortly. 
Also why socks and quic ?
If we have to make a proxy solution for all the application (non http too) and if it has to be application agnostic . We have already deployed a similar approach for MPTCP. Hence SOCKS+QUIC would be a interesting use case 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/2518#issuecomment-480564454

v2.23.0 | Report a Bug | By Email