Re: [homenet] ISPs using DHCP for individual clients

Daniel Migault <mglt.ietf@gmail.com> Sun, 22 November 2020 02:11 UTC

Return-Path: <mglt.ietf@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 227D43A0C37 for <homenet@ietfa.amsl.com>; Sat, 21 Nov 2020 18:11:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, 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 yVvIMDjyOkL4 for <homenet@ietfa.amsl.com>; Sat, 21 Nov 2020 18:11:40 -0800 (PST)
Received: from mail-vk1-xa32.google.com (mail-vk1-xa32.google.com [IPv6:2607:f8b0:4864:20::a32]) (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 3E3CC3A0C36 for <homenet@ietf.org>; Sat, 21 Nov 2020 18:11:40 -0800 (PST)
Received: by mail-vk1-xa32.google.com with SMTP id i62so3183683vkb.7 for <homenet@ietf.org>; Sat, 21 Nov 2020 18:11:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=c1BR0e5ty1QYIfI/2eiS7B+8yr6rygJyu/WpjCSKaXY=; b=XIA9Cxj4JPtKD0VxEhtvaOhLv9mKDQSGLotG2sjT8sQlyl/BoLckcnqoDYRj336R9s TXNMIyhp/oNIjwCjHx85BFjV/RbVunefc1+m1vlT5WKf2SvenvfPKVle8uS+DQfemItK RPPjILD607iCiK77a7zOntmm1gjGM7IxVZYLcbCra7LIrqBcUKZGc0NnIQdLgoRhD8zO NeZXUtmPblDzn8S6kE9NcwDxXvG4GwoA7lr9YX9O4Q2IyUw/WBZnkD0HWOLZ0Ld3hmRR jH6ZupfoTtpHcNNnJh2nLYPlPKRx9KcmV4c2uUKxFWPV7pqQlbeYkKIkgytiw675NRnd 0rgg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=c1BR0e5ty1QYIfI/2eiS7B+8yr6rygJyu/WpjCSKaXY=; b=IC1lS1b5njr1KQ5noWK/GSm+jVBiMdlFi75cDyf2DjespXL/hvWP/e4n5++cieFLHv 07W2AawSnSo0EX/rzTtn4RKa6BGP2vJxdxnt3GZkLBIJ0tx9cgl9MDoZt/fplkD+d6Rd Ge667BFlToGVAl0pFDRc2X3WQ63PDCCwWxWC9qN+s4xdEKpMb2O3i1OBLFxeiIJAMqrj 4yMt1bBw66k4EiU2jTx9KhpfMu1ORcjvJyq7qtgU9PLBD94w8bMNQ4N0lsPyuf34H5kM s8QSANStORsQolhA+XjRms7aXlc9Qd26a20/DAA0Ivq/0pgU8X9GSaq3VvFdVR7Q6Bbi Yksg==
X-Gm-Message-State: AOAM533xUy82YxK0557h8NsCiDoIXixVHftspLu2ObvN3JMfuooWtGSS /XYI9FySdBFQsz73voqXZamHqDkIVh0VG5U2IWc4vcF+
X-Google-Smtp-Source: ABdhPJy5lqXT352KFLZsU5JGHmb4oD89UtcYE/V9sj9ZIgSm9qjrwjYPUrYXwS7WOYUPtTwUfmNjxYCGb7rJkML2PXE=
X-Received: by 2002:a1f:4601:: with SMTP id t1mr16822772vka.6.1606011099183; Sat, 21 Nov 2020 18:11:39 -0800 (PST)
MIME-Version: 1.0
References: <CADZyTkn5nFDwNZev1ggj2do7uLcr=M9EKT8mmaiFPXhPaObBwg@mail.gmail.com> <alpine.DEB.2.20.2011201000000.26384@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.20.2011201000000.26384@uplift.swm.pp.se>
From: Daniel Migault <mglt.ietf@gmail.com>
Date: Sat, 21 Nov 2020 21:11:28 -0500
Message-ID: <CADZyTk=+md66abyB9w1XPG999YTmW=RoB6-ciNDA6MbEhJ2f2Q@mail.gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: homenet <homenet@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000127fd805b4a89918"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/GX6wbqQW8qKsrQezJmIuSwxQCik>
Subject: Re: [homenet] ISPs using DHCP for individual clients
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Nov 2020 02:11:42 -0000

Thanks for the response Mikael,

In this case, I have the impression the L2 switch uses the MAC address to
determine what type of devices is initiating the DHCP request and orient
the DHCP request to the appropriated VLN and DHCP server. I suspect that
the type of device is determined the OUIs and the switch has a table of the
corresponding OUI and the potential HWG MAC address and that such table is
loaded as part of the configuration of switch.

If my understanding is correct, this is a bit different from our use case.
I think the situation I was describing would have been closer to the HGW
sends in a DHCP request its MAC address and the MAC address is registered
into the end user account. But that is a useful feedback though, as it
chose having a portal and expecting the end user to provision the CPE is
something common. This will relax the purpose of zero configuration but
sounds more in line with what is currently deployed.

Yours,
Daniel

On Fri, Nov 20, 2020 at 4:06 AM Mikael Abrahamsson <swmike@swm.pp.se> wrote:

> On Fri, 20 Nov 2020, Daniel Migault wrote:
>
> > Hi,
> >
> > While designing the DHCP options to configure the HNA we asked ourselves
> > how likely ISP are:
> >
> > A) How an ISP is likely to perform an action that is user specific based
> on
> > a DHCP request. In our case the HNA sends to the DHCP server the
> > certificate it will use to authenticate itself to a server the ISP has
> > control on. The action is that the ISP will need to provision the server
> > with that certificate.
> >
> > B) How an ISP is likely to provide a DHCP response that is specific to an
> > individual user. The specific information is typically expected to be
> > something provisioned for that user.
>
> I'm not 100% sure I understand your question but let me write some text
> and see if it helps.
>
> In Sweden, ETTH is often delivered with an L2 switch of some kind, can be
> media converter or just CPE. Into this, you can connect a router, an ATA
> (PSTN box), a TV STB, and based on the MAC address and possibly the
> contents of the DHCP request, you'll get different responses, possibly
> even that the device reconfigures ports into different VLANs etc. The term
> used is called "free seating" (I have no idea where this came from) and
> the idea is to reduce customer support calls when customers plug in
> equipment into the "wrong" port, so instead just let customers plug into
> any port and it just works. The DHCP responses might also be different
> depending on type of device etc.
>
> We also have cases where you register your HGW MAC address in a portal and
> depending on this MAC address, your HGW will either receive IPv4 GUA or
> end up behind CGN. So this differentiation is done on MAC address. Don't
> know if you consider this "part of DHCP request" or not.
>
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se
>


-- 
Daniel Migault
Ericsson