Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notification - Respond by December 11, 2023

Bernie Volz <bevolz@gmail.com> Tue, 26 December 2023 23:26 UTC

Return-Path: <bevolz@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 C3916C14F60B for <dhcwg@ietfa.amsl.com>; Tue, 26 Dec 2023 15:26:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 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, MIME_QP_LONG_LINE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cfYvbQZiYfRR for <dhcwg@ietfa.amsl.com>; Tue, 26 Dec 2023 15:26:21 -0800 (PST)
Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01EEEC14F5EC for <dhcwg@ietf.org>; Tue, 26 Dec 2023 15:26:20 -0800 (PST)
Received: by mail-qt1-x82b.google.com with SMTP id d75a77b69052e-427b3bad08fso23729511cf.1 for <dhcwg@ietf.org>; Tue, 26 Dec 2023 15:26:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1703633179; x=1704237979; darn=ietf.org; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=bUqaYKOOzMvATd3mNuDA6tSwQmbCLwaeAEnxbVtkhEg=; b=hZwUHjZK2IfgzkHgs9dCrj8UtOnwIPHtipn9xkthaP9qUfCvCWX9e0yNBxYsHV1a4U /9A0UHBUxZ730nyO6rNxTcnxGe44NIfsBQsm17s/q7nvDvPt5VF2qdbh6FMj+xnI8TAN 4shaYgYi5kliH3ExGrE5QVT/MztorMWZ+PGHX92yb7UvCvjLzqzEZ8iXAHp2kakfNMnr hH+mm4GLSABxJaP6aEb0nrq28K/3PhLC/Q+72DFqXABfy7A2uCesIfN9ZyYpAO4xw6DF kBJKVK3M8Noof6Y/IeUrYlzfy6ttMtgRLGANmFqNDIWekZ0g+aiGx094xpHzTXBQPDUq 2U1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703633179; x=1704237979; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=bUqaYKOOzMvATd3mNuDA6tSwQmbCLwaeAEnxbVtkhEg=; b=pNYjZk84rRJMB04GJfsb+EW9/ZJc9Mw5ets6L/JD1Dx1lIx2RgyCwbx/swmv0arltn 4GHxlXhBRl3YXDLRV4eZSAhAKFu6yQHj94roYV2efrV9/ywWtrSke7JSPGY0Mf2MBIhW YSFrJOgZwXd5AIRMKZWR0ilYWeh+RF4Ivz6XNvM0dbX0s8NQPIlebnDktkvtlcPqepEt O8S8ptED6J6x+5le5ajD/3m6rmFdiePbM1mykgptZnQId8fQbr8vWry4PML6lTWKkUTE vYwqvzMvaRYFkBM+/WgfOd1x9gLmKkKl8JVHsFWmu9iChP/ASVgKpHCqfeAQWd52Q84d r85w==
X-Gm-Message-State: AOJu0Yzsxn1oygoULiRXwlAvrWjwAOZBEzhfsscFKMP/zGDeWYsYup56 5v3GGKIwdu8+iBCKtaeumHuxIkwjxw==
X-Google-Smtp-Source: AGHT+IHAyYBx6CZ5a3s8QQ8fC8YOL1gTOl7YQjCFfV99bAD4NrcdRi/IJm9EdjTU/d2iZkrnQa/gtA==
X-Received: by 2002:ad4:594c:0:b0:67f:457c:21ac with SMTP id eo12-20020ad4594c000000b0067f457c21acmr12627229qvb.48.1703633179461; Tue, 26 Dec 2023 15:26:19 -0800 (PST)
Received: from smtpclient.apple (d-24-233-121-124.nh.cpe.atlanticbb.net. [24.233.121.124]) by smtp.gmail.com with ESMTPSA id v3-20020a0ccd83000000b0067f8e291f13sm4372139qvm.69.2023.12.26.15.26.18 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 26 Dec 2023 15:26:18 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail-F14EDE39-55E2-47B0-AEDA-1B6BE6B5E2DF"
Content-Transfer-Encoding: 7bit
From: Bernie Volz <bevolz@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Tue, 26 Dec 2023 18:26:07 -0500
Message-Id: <02118B61-0D84-4181-A124-517EC213BEDC@gmail.com>
References: <23757.1703631874@localhost>
Cc: Daryll Swer <contact@daryllswer.com>, dhcwg@ietf.org
In-Reply-To: <23757.1703631874@localhost>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: iPad Mail (21B101)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/1TiUqJ0UY6tUcESXtYnzv56IMkQ>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notification - Respond by December 11, 2023
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 26 Dec 2023 23:26:24 -0000

>> I'm still not clear overall, how the configuration of this addr-info on
>> server side would look like, while I understand the M flag, should my link
>> prefix /64 still be "autonomous" or not though?

If SLAAC not enabled on prefix in router advertisement, you would not need address notification.

For the DHCP server, you would configure the prefix to send the addr notification option when requested and record and monitor the reported address assignments.

- Bernie

> On Dec 26, 2023, at 6:04 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> 
> Daryll Swer <contact@daryllswer.com> wrote:
>> In a service provider network, we definitely don't care what host or
>> anything else that's happens beyond the customer router, regardless if it's
>> enterprise or residential. Our legal liability stops at customer KYC,
>> meaning, if my router gives them a /56 or /48 PD, and this PD information
>> is logged via AAA/RADIUS, that's enough for an SP to comply with the
>> law.
> 
> Yes, but it still might not solve the problem of "printing is broken"
> 
>> However, you're right that there are some enterprises that use stock random
>> CPEs for branches etc. And this is where we'll run into problems. If there
>> are say n number of hierarchical routers, that are doing exactly what
> 
> There are many hosted service providers where it's a top to bottom service,
> and they actually need to know all the details of what happens in each
> "store"
> 
> (at the ISPs I've worked for in the previous decade: we had drug stores,
> supermarkets, shoe stores and optical stores.  We had several hundred of
> each, all on fiber with DSL backup.  We pushed v6 wherever we could, but too
> many PoS systems were... PoS..  [haha] However, we could/did easily have
> overridden a local default about reporting)
> 
>> I'm still not clear overall, how the configuration of this addr-info on
>> server side would look like, while I understand the M flag, should my link
>> prefix /64 still be "autonomous" or not though?
> 
> which server?
> 
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
>           Sandelman Software Works Inc, Ottawa and Worldwide
> 
> 
> 
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg