Re: [dhcwg] configuring SOCKS(v5) via DHCP

"Ms. Li HUANG" <bleuoisou@gmail.com> Mon, 28 March 2022 23:53 UTC

Return-Path: <bleuoisou@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D8F13A08CF for <dhcwg@ietfa.amsl.com>; Mon, 28 Mar 2022 16:53:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 mHsggkAqV0Rs for <dhcwg@ietfa.amsl.com>; Mon, 28 Mar 2022 16:53:36 -0700 (PDT)
Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 783CD3A08A9 for <dhcwg@ietf.org>; Mon, 28 Mar 2022 16:53:36 -0700 (PDT)
Received: by mail-ej1-x636.google.com with SMTP id yy13so31828670ejb.2 for <dhcwg@ietf.org>; Mon, 28 Mar 2022 16:53:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=vkPB0V4ydIucKPfREv8bJqGavTPN1CxS/ufUc9q4gvo=; b=Q6e4hOZmKkBLHRYpWHcFAItTXGWGDyXBMMOlLoOxILwVMtlg3c9oWQqHfsa2tF2PTr VooT+5+90bLHAkOq+oEfpH6juXUuxM0+7BkokNY0LHt6bmdOnhuOqmXl4gkEPIKLUBxz mMnK5RTwlXZv5w8rv0lyF1XV1XR+Bj5+pg0ttyN5mz6E3kwX4D3E7vbg9ByRbvoVppbH BHY4nU9xxqfcjvK4d7HuwJMadWxAxmdvGjTCXYz0ZKgYyj4PXTXAcVhYnVWZg2QnITDl ae8GGRq6+CygW9LwHaJAOg4gE1pCtufRMNZfYANftt5S9+9mcEwrjZDwEk84gyv1pBvO lzOA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=vkPB0V4ydIucKPfREv8bJqGavTPN1CxS/ufUc9q4gvo=; b=VsL/dsQM12Q6AOn0V3lslcaLa06CYKxhRQR+SY2ZCmR+CdLEm324Vlfnk1cU5vVgVX xqpf7TOLQPdu8ubUH5hO1bQN5UyQv4qMRAcfIMsFOO3HwM/isMORt3AS/DA7dHPhV15X +VkPjk/XJtbzvVZoGt++5j1LDfXbOVlNj22Ot/VXZ3RfdvmUtcaK0q1T91vyQoHQcWmX kG5ocFBlNKavdVjdabQmUsCCJnhUwh5220jI9rIlul8Iw+0abiCBNuNbBVSipg64AU4Y c1oVKI9SpBapGgHDgnfDqACywqmBefCodGclRLet/UJHKBEbgtCpLQdCuV0SS5MUBsst 9rYg==
X-Gm-Message-State: AOAM531vRVV3X95khFuW2ypWWV5CJtvGo+YSSiJBvMzngTzZM3QuSlrs McyRkbxNccIsczYjgdn8D/klSd4HT+KmB07/QsI=
X-Google-Smtp-Source: ABdhPJzFz8nqOQDC+I68wIteSDFBWYDmbnPUsMZ1hA5xDoSET4LcWRRCEewIvAunXtYRf3TkYIIogHOfveOpovSxSJo=
X-Received: by 2002:a17:907:a422:b0:6e0:238c:4f44 with SMTP id sg34-20020a170907a42200b006e0238c4f44mr30791660ejc.257.1648511614596; Mon, 28 Mar 2022 16:53:34 -0700 (PDT)
MIME-Version: 1.0
References: <75372.1648314192@dooku> <19651_1648451170_62415E62_19651_399_1_f3c48b5795614a8181164612ae074bce@orange.com> <97763.1648473331@dooku>
In-Reply-To: <97763.1648473331@dooku>
From: "Ms. Li HUANG" <bleuoisou@gmail.com>
Date: Tue, 29 Mar 2022 07:53:22 +0800
Message-ID: <CAGGiuEbjH=wJ38OKfmPSK2DM-7c1m66-3L7hdyFhxj1Q6mhtUg@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: mohamed.boucadair@orange.com, dhcwg <dhcwg@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003238c705db50052c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/yoZS3Vb3MMqxn5UUBGSwVBlosA0>
Subject: Re: [dhcwg] configuring SOCKS(v5) via DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Dynamic Host Configuration <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Mar 2022 23:53:42 -0000

Mar 29 2022 07:40.hk S8


Good Day,



"If there was a way to learn if SOCKS was in use on a particular network,
such as via a DHCPv4 option, then devices could use it on networks where it
existed."


when the switch told from supplier that,  at dual stack, if isp not
allowing an  home.User to enough setting info such how many ip permitted,
public host etc., the home.user even could not do the configuration with
''permission'?!

Meanwhile the set up ipv6 prefix(s) ISP ever but not current using told was
not routing, then if, how the network before's events to be consistently
tracking , who caring them...?

WAN mostly related to sock layer,

since stranger switch appeared at between PCs ---(switch)---gateway---ISP
in 2013 to owning a switch in later 2019 as  PCs -----Switch
-----Gateway-----ISP
              |                       |
              -----(Switch)----

two of mach each, who knowing the events on them....? Ehat sock version
being used at dhcpv4 by when, and dhcpv6 since isp offering enterprise sort
of v6 in  Apt 2014 where ofca.gov.hk never clearly responded on these yet.



Regards
Li HUANG




On Tue, Mar 29, 2022, 05:43 Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> <mohamed.boucadair@orange.com> wrote:
>     > There is no such an option as far as I know.
>
>     > We published this spec:
>     >
> https://datatracker.ietf.org/doc/html/draft-boucadair-tcpm-dhc-converter-03
>     > to cover the discovery of a "converter".
>
> Thank you for confirming my investigation.
>
> --
> ]               Never tell me the odds!                 | ipv6 mesh
> networks [
> ]   Michael Richardson, Sandelman Software Works        | network
> architect  [
> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on
> rails    [
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>