Re: [v6ops] Updating RFC 7084 - alternate logic

Ole Troan <otroan@employees.org> Wed, 30 November 2022 16:21 UTC

Return-Path: <otroan@employees.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EC08C1524B3 for <v6ops@ietfa.amsl.com>; Wed, 30 Nov 2022 08:21:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.205
X-Spam-Level:
X-Spam-Status: No, score=-1.205 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, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, MIME_HTML_ONLY_MULTI=0.001, MIME_QP_LONG_LINE=0.001, MPART_ALT_DIFF=0.79, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=employees.org
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 s_Yt1WR_ZaCP for <v6ops@ietfa.amsl.com>; Wed, 30 Nov 2022 08:21:11 -0800 (PST)
Received: from vesa03.kjsl.com (vesa03.kjsl.com [IPv6:2001:4830:c170::91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A6E1C1524B2 for <v6ops@ietf.org>; Wed, 30 Nov 2022 08:21:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=employees.org; i=@employees.org; q=dns/txt; s=vesa202009; t=1669825271; x=1701361271; h=content-transfer-encoding:from:mime-version:subject:date: message-id:references:cc:in-reply-to:to; bh=8fGOsu04pAgAszaDJtdpnzo+6dANJt36AWde32/iqL8=; b=RbRreqyEdY93mQo8YvRSoSp4psZo1ZnorYGITFyrOVAsFAb7WyZo2zor VaHFc5pMsM6HZqoXgSGCNTbypHMwPlpw7kT3nHfcOSuTe1vA/798qh7I1 5gOMzgGkp22V6sZyWg+PlXIbkMUpp5AOZ3+g0FsdgvI1prMjZC/5Jw+jG xQEIa96JdogVw0H/cnRd2u+tOoKRbCqcfnbSeRioaG7Q7DYMVMgWRDw+X kfvTRLIPmbazJm1yY8bbP4IPtj4M3kQLEe0aE7sE/irW0iOBaJvEiqKiQ LjAqlx087DMmqyDbyrwMtOK56/10wCpNgkCQQOGECQWB4vmRJW5q3y9+R w==;
Received: from clarinet.employees.org ([IPv6:2607:7c80:54:3::74]) by vesa03.kjsl.com with ESMTP; 30 Nov 2022 16:21:07 +0000
Received: from smtpclient.apple (unknown [IPv6:2a02:2121:655:57f2:5456:dd06:c06e:5671]) (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 clarinet.employees.org (Postfix) with ESMTPSA id 4FEDF4E11CDE; Wed, 30 Nov 2022 16:21:07 +0000 (UTC)
Content-Type: multipart/alternative; boundary="Apple-Mail-C882E41D-7307-4DBC-B17D-68BBD5F20757"
Content-Transfer-Encoding: 7bit
From: Ole Troan <otroan@employees.org>
Mime-Version: 1.0 (1.0)
Date: Wed, 30 Nov 2022 17:20:55 +0100
Message-Id: <2911756E-CEDD-4E37-A1A8-6B7735CD9099@employees.org>
References: <CAJgLMKt8uvW77QL5emk5fUq+k2osyn5AHka7ye2+vSZS5A5PFQ@mail.gmail.com>
Cc: Olorunloba Olopade <loba.olopade@virginmediao2.co.uk>, IPv6 Operations <v6ops@ietf.org>
In-Reply-To: <CAJgLMKt8uvW77QL5emk5fUq+k2osyn5AHka7ye2+vSZS5A5PFQ@mail.gmail.com>
To: Timothy Winters <tim@qacafe.com>
X-Mailer: iPhone Mail (20B101)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/cPBzKuaD8V1JUeufBV1r-tJl1Nc>
Subject: Re: [v6ops] Updating RFC 7084 - alternate logic
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Nov 2022 16:21:15 -0000

When there was interest in DHCP PD for prefix assignment, two models were proposed. One called hierarchical PD and the other flat assignment. 

In the flat mode a PD client can ask for multiple /64s. 
Which is the model I believe you suggest Tim. 

O

On 30 Nov 2022, at 16:56, Timothy Winters <tim@qacafe.com> wrote:


Hi Olorunloba,

I was aware of the requirements, there were a couple of things I was trying to avoid.   This model creates a tree that can lead to under utilized prefixes which was somehting I wanted to avoid.  Additionally, I'm aware that it's not widely implemented due to the complexity.   Do you know if all eRouters are required to support this?

~Tim
On Wed, Nov 30, 2022 at 10:16 AM Olorunloba Olopade <loba.olopade@virginmediao2.co.uk> wrote:

Hello,

 

Wile RFC7084 doesn’t cover the DHCP requirements, there are other spec (e.g. cablelabs) that does. And we have implementation of this.

 

I agree that we should support DHCP on the CE, but don’t support limiting the sub-delegation to /64, which would make some of the current implementations non-compliant. I will suggest something like the following, which is an amendment of the cablelabs spec

 

• If the Topology mode is set to “favor config”, then divide the delegated prefix into sizes specified by the CE config.

• If the provisioned MSO assigned IA_PD is smaller than a /56 (e.g., a /60) and the Topology mode is set to "favor depth", the CE MUST divide the delegated prefix on two (2)-bit boundaries into four (4) sub[1]prefixes by default.

• If the provisioned MSO assigned IA_PD is smaller than a /56 (e.g., a /60) and the Topology mode is set to "favor width", the CE MUST divide the delegated prefix on three (3)-bit boundaries into eight (8) sub[1]prefixes by default.

• If the provisioned MSO assigned IA_PD is a /56 or larger and the Topology mode is set to "favor depth", the CE MUST divide the delegated prefix on three (3)-bit boundaries into eight (8) sub-prefixes by default.

• If the provisioned MSO assigned IA_PD is a /56 or larger and the Topology mode is set to "favor width", the CE MUST divide the delegated prefix on four (4)-bit boundaries into sixteen (16) sub-prefixes by default.

• If the provisioned MSO assigned IA_PD is too small to divide in the manner described, the CE MUST divide the delegated prefix into as many /64 sub-prefixes as possible and log an error message indicating the fault

 

 

From: v6ops <v6ops-bounces@ietf.org> On Behalf Of Timothy Winters
Sent: 18 November 2022 14:47
To: IPv6 Operations <v6ops@ietf.org>
Subject: [v6ops] Updating RFC 7084

 

Hello,

 

I've started a draft to update RFC 7084 to support prefix delegation on the LAN interfaces.  The current state of IPv6 in home networks is ISP are assigning prefixes of appropriate sizes but they currently are under utilized due to the lack of prefix delegation on LAN interfaces.  

 

This draft is an attempt to add that support to the draft.

 

 

This is only an update to 7084 at the moment, there has been some discussion on the snac working group about leveraging this work as well.

 

One item being discussed is this currently doesn't solve multi-homed networks. 

 

I welcome any feedback about the proposal.

 

~Tim



 

Save Paper - Do you really need to print this e-mail?

 

This email contains information from Virgin Media and/or Telefonica UK Limited (O2) and may be confidential and legally privileged. Statements and opinions expressed in this email or any attachment may not represent either those of Virgin Media or Telefonica UK Limited. Any representations or commitments in this email or any attachment are subject to contract.  The information in this email is intended solely for the attention of the addressee(s) and if you are not the intended recipient please delete it (including any attachment) from your system, and be aware that any disclosure, copying distribution or use of any of this information is not permitted.

 

If you are in receipt of a suspicious email or you have received an email in error from Virgin Media, please report it to http://www.virginmedia.com/netreport" target="_blank" rel="nofollow">www.virginmedia.com/netreport, or for Telefonica UK Limited (O2), please report it to http://www.o2.co.uk/help/safety-and-security" target="_blank" rel="nofollow">www.o2.co.uk/help/safety-and-security

 

 Registered offices:

 

 Virgin Media Limited, 500 Brook Drive, Reading, RG2 6UU. Registered in England and Wales: 2591237

 

 Telefonica UK Limited, 260 Bath Road, Slough, Berkshire SL1 4DX. Registered in England and Wales: 1743099

 

 VMED O2 UK Limited, Griffin House, 161 Hammersmith Road, London, United Kingdom, W6 8BS. Registered in England and Wales: 12580944

_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops