[v6ops] Re: [IPv6]Re: Is the P flag even necessary? M flag already does enough (Re: Re: A detail review of draft-ietf-6man-pio-pflag-04)

Daryll Swer <contact@daryllswer.com> Tue, 06 August 2024 16:04 UTC

Return-Path: <contact@daryllswer.com>
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 0712DC1519B0 for <v6ops@ietfa.amsl.com>; Tue, 6 Aug 2024 09:04:28 -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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=daryllswer.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 L8ajruwr941N for <v6ops@ietfa.amsl.com>; Tue, 6 Aug 2024 09:04:23 -0700 (PDT)
Received: from mail-pf1-x42a.google.com (mail-pf1-x42a.google.com [IPv6:2607:f8b0:4864:20::42a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CAE00C1519AF for <v6ops@ietf.org>; Tue, 6 Aug 2024 09:04:23 -0700 (PDT)
Received: by mail-pf1-x42a.google.com with SMTP id d2e1a72fcca58-70eae5896bcso614158b3a.2 for <v6ops@ietf.org>; Tue, 06 Aug 2024 09:04:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=daryllswer.com; s=google; t=1722960262; x=1723565062; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=J1WC/iWk8OMDAGDDSidy+X02trWqLvh0hmZ43E4N1W4=; b=V4tq8B+DXXv3L8nxWPZAFNFR3CK8j9LQ99NmAos5a8+Oh969F0DaWlfnq/mQ+JAZqZ 7uZHEFAdxuuaw9CFexubH99s5JABX7be+norQXmg6XLZo2I208FXAPxGsUp//VMhjHHU NuCTtY89RZ8kqRZ1sZD0wZvOyYIrzWvm4hoXhxZk6q7x/GSbfxQPvpaou+RbL5Uo+mWf J0haD9/NsA7cmVnXWaY03v4cI+JoYKvVU14VgrcD3ky9R5vh/h5RO6VopRzoekLlprJC gQByu/wbjaq0egaWuQ4Ph+nlyyQIdIuZnHJa1JVJ65v8NusXSYV3zJa+jqjG2GfxJLPz qw9g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722960262; x=1723565062; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=J1WC/iWk8OMDAGDDSidy+X02trWqLvh0hmZ43E4N1W4=; b=PSQnyLlcD6RS1arx9vdar8gQHlkwl827EafjvvPZXrLnTSo4X2TV2BEG63p1CgMRra AkOAHDTgktOjeqdHPNee/kmAJ5ROV3TA/a6pgVnWly8wmNobyogZcSvkCMk5+bP6JWEE eHHWWt+Dr61AAsnTOfUELF/Mhi8cBmD3OQ3O6YB9gc4eCKSvmE6QlOM/NEWEOGHgs2Ux StQ10HF9w0GdNQ2n7How7RXoKZXFp0mv1GK+9CvhdiORoyGLWe0d2f6QoLiZhIBkHqBZ gxtkNsB0/G3ANyh5f1gP69VmQAJHmwdxLToDbG3ozhj3NWbkGM2gcal1j8Xi21pokbR2 YrZw==
X-Forwarded-Encrypted: i=1; AJvYcCVE3LcHUqYF04RVeCn8JV+RVGP7iSW5iOAVH7poDj46fOwfvcoCYzXNBc/Pa0Eqz2XN+qad49sGP/jY1JxigA==
X-Gm-Message-State: AOJu0YzvgLy2yICbrCvvejxFuX9yZAQ0kcv0tjEDzIDAJKmcElYGoZfe CZFdDvbyEmX8kbjLyM1cFA0N1y36e+nMqERfIIZcA0zl9zFwC2+kg6Yb+G8bpgfRxgG9gdElLEb Mq3U=
X-Google-Smtp-Source: AGHT+IFdN+GmOsUTTvSxQTGO/afOz1BOFcaYiNh8EUyKufUsn0LtMbJREC73D6TbtVI3/S8xY7F+KA==
X-Received: by 2002:a05:6a20:2589:b0:1c0:e728:a99e with SMTP id adf61e73a8af0-1c6995aa86amr24672328637.26.1722960262257; Tue, 06 Aug 2024 09:04:22 -0700 (PDT)
Received: from mail-pl1-f179.google.com (mail-pl1-f179.google.com. [209.85.214.179]) by smtp.gmail.com with ESMTPSA id 41be03b00d2f7-7b764fb7072sm7007467a12.61.2024.08.06.09.04.21 for <v6ops@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 06 Aug 2024 09:04:21 -0700 (PDT)
Received: by mail-pl1-f179.google.com with SMTP id d9443c01a7336-1fc569440e1so8419765ad.3 for <v6ops@ietf.org>; Tue, 06 Aug 2024 09:04:21 -0700 (PDT)
X-Forwarded-Encrypted: i=1; AJvYcCVnMxu+lV7cOSX0tkuSXRe1iYLqZT64GuPttjMfldcUrzvWbN4HopDTdyb6D5CtjpPqswifaItqLynBN/fhwQ==
X-Received: by 2002:a17:902:e541:b0:1fd:ae10:7242 with SMTP id d9443c01a7336-1ff572b9e3emr215923365ad.32.1722960261440; Tue, 06 Aug 2024 09:04:21 -0700 (PDT)
MIME-Version: 1.0
References: <CAN-Dau1R=oszbFx40a2U+Cnx354vi44Osk4ruuGcGDodzYKo7A@mail.gmail.com> <CAFU7BASyraNzL3htxxGkbeo5akCS-fLeH8_49GFb-fTc4TB0fQ@mail.gmail.com> <CAN-Dau2wNs=6QO6+vHHb0OQj2GV1HRe76BHo4rdomjCFUBES_g@mail.gmail.com> <CAPt1N1=NaGHxwQ29Z_Uk2royyb-Nix21kcY+12JC9=FDHtOQ+A@mail.gmail.com> <CAN-Dau1+WyvDyxXZBEKFVQ=Pjf38-ku_V9WbmLRBuys5v2R3Pg@mail.gmail.com> <CAPt1N1=1bXJrUNvSOe322SdTHGfe-Odw67NSnTE4NY0ZGyqJ8g@mail.gmail.com> <CAN-Dau3WdgCQFurWJjiC-Tr4a5hj25pjOvhNG8O=tne=JwA0eA@mail.gmail.com> <CAPt1N1nKo2b1XyW1-bBvAk9N2DuDkqbury6d+z900P+FxQTzrg@mail.gmail.com> <CAN-Dau2vMX4-6BD-SLQYk-DDj8ia3ySSLwLdMrRAU1canMjJsw@mail.gmail.com> <CAFU7BARVGGCaD-aO2Y+tE0c=JDY0kCjxmfZ-yUeSuR8S554omg@mail.gmail.com> <CAO42Z2w9PcN4ej6_Ly-jLoKcMeWP+-UA00xGHPG9jm2dz4_F2A@mail.gmail.com> <CAPt1N1nmk9+G_QadBV8D=Ty_0sxMFNYxijd+CERr7w8YWhJaxQ@mail.gmail.com> <CAO42Z2wAjamRg4sNnpAF0KBB5SrHgJUxcoy1rXvdrR3SWC3xog@mail.gmail.com> <CAKD1Yr33a9LZ4A0UZsFUMsR-SZ2GfO1q-2Cifts+KsAd_g5ObQ@mail.gmail.com> <CAO42Z2z8S426+G+AbpPDjrLdbmYDsArXaoAFMRuSbx41weWoHw@mail.gmail.com> <DB9PR07MB77717BE049C3B0DA943F19CCD6BE2@DB9PR07MB7771.eurprd07.prod.outlook.com> <CAPt1N1nNC0HEGOxP3-8-G+wdLxGywCOH-_4W7fodM+0YmtLcRA@mail.gmail.com> <CAJgLMKuwtpSpF2JnR5dYfh6hmo+-LunbJxe7Z6WTTaNh=nAtVw@mail.gmail.com> <CAPt1N1kx79vyHnU-=tfGLrRDgiRiKTu0D1aYdYn_vYTQUMK99w@mail.gmail.com> <CAJgLMKtCxh=H+bt7c9F9nn0XhLFDvhvshvu6Jp6CqN3NbK8D-g@mail.gmail.com> <CAPt1N1kDk=gbCeO7_bSsiROUC4BfKCGZhTaQyJp0Ez_G3nG0MQ@mail.gmail.com> <CAJgLMKu6-oQ20TX1V_topdiEwX-Ps4PnxS-G1TKYNoA_yeB4vA@mail.gmail.com> <CAPt1N1nNrmgY9FH06zwMZCRLqMfnzcsKjDHFjTrkxadRA7fa-Q@mail.gmail.com> <CAJgLMKs=FpqWyu_UXukAMJ+PCZ_-yXyFfqTVsU8KR329PxdVmw@mail.gmail.com>
In-Reply-To: <CAJgLMKs=FpqWyu_UXukAMJ+PCZ_-yXyFfqTVsU8KR329PxdVmw@mail.gmail.com>
From: Daryll Swer <contact@daryllswer.com>
Date: Tue, 06 Aug 2024 21:33:45 +0530
X-Gmail-Original-Message-ID: <CACyFTPFBAt-bQ=oQiP9n8LCDHSpK8gZRhFf+A713j=cNVWL0gw@mail.gmail.com>
Message-ID: <CACyFTPFBAt-bQ=oQiP9n8LCDHSpK8gZRhFf+A713j=cNVWL0gw@mail.gmail.com>
To: Timothy Winters <tim@qacafe.com>
Content-Type: multipart/alternative; boundary="0000000000005876e0061f05f2aa"
Message-ID-Hash: P6WQVYA6SICJRWHQWBTML7V7GXYFNK4D
X-Message-ID-Hash: P6WQVYA6SICJRWHQWBTML7V7GXYFNK4D
X-MailFrom: contact@daryllswer.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-v6ops.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: IPv6 Ops WG <v6ops@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [v6ops] Re: [IPv6]Re: Is the P flag even necessary? M flag already does enough (Re: Re: A detail review of draft-ietf-6man-pio-pflag-04)
List-Id: v6ops discussion list <v6ops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/enXHBBmpKdcjyL1JsHzMOn151YI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Owner: <mailto:v6ops-owner@ietf.org>
List-Post: <mailto:v6ops@ietf.org>
List-Subscribe: <mailto:v6ops-join@ietf.org>
List-Unsubscribe: <mailto:v6ops-leave@ietf.org>

Why not:

LPD-8: The IPv6 CE Router MUST provision IA_PD prefixes with a
prefix-length of *60* unless configured to different prefix-length by the
user.

Assuming, we want to force CPEs (in turn forcing ISPs) vendors to normalise
BCOP-690 (/56 ia_pd minimum for home networks).

*--*
Best Regards
Daryll Swer
Website: daryllswer.com
<https://mailtrack.io/l/1be637bce3a03573f0aba79c5b508ea9c46d50f0?url=https%3A%2F%2Fwww.daryllswer.com&u=2153471&signature=9e0cfb1d70527150>


On Tue, 6 Aug 2024 at 21:04, Timothy Winters <tim@qacafe.com> wrote:

> Hi Ted,
>
> I almost made that modification and can't think of a great reason not to.
>
> OLD:
> LPD-8: The IPv6 CE Router SHOULD by default provision IA_PD IA prefixes
> with a prefix-length of 64.
>
> New:
> LPD-8: The IPv6 CE Router MUST provision IA_PD prefixes with a
> prefix-length of 64 unless configured to different prefix-length by the
> user.
>
> ~Tim
>
> On Tue, Aug 6, 2024 at 11:32 AM Ted Lemon <mellon@fugue.com> wrote:
>
>> Yes, much better. Thanks!
>>
>> Why SHOULD and not MUST?  What is the case where they would not do this?
>>
>> Op di 6 aug 2024 om 11:26 schreef Timothy Winters <tim@qacafe.com>
>>
>>> Hi Ted,
>>>
>>> How about this:
>>>
>>> OLD:
>>> LPD-8: The IPv6 CE Router SHOULD by default provision IA_PD IA prefixes
>>> with a prefix-length of 64.
>>>
>>> New:
>>> LPD-8: The IPv6 CE Router SHOULD provision IA_PD prefixes with a
>>> prefix-length of 64 unless configured to different prefix-length by the
>>> user.
>>>
>>> I'll make this change in the next revision.
>>>
>>> ~Tim
>>>
>>> On Tue, Aug 6, 2024 at 10:49 AM Ted Lemon <mellon@fugue.com> wrote:
>>>
>>>> What I’m saying is that the text is ambiguous because you don’t say
>>>> what “by default” means. I am one of the people who wants to get rid of the
>>>> hierarchical model.
>>>>
>>>> Op di 6 aug 2024 om 09:05 schreef Timothy Winters <tim@qacafe.com>
>>>>
>>>>> Hi Ted,
>>>>>
>>>>> On Mon, Aug 5, 2024 at 2:30 PM Ted Lemon <mellon@fugue.com> wrote:
>>>>>
>>>>>> On Mon, Aug 5, 2024 at 11:16 AM Timothy Winters <tim@qacafe.com>
>>>>>> wrote:
>>>>>>
>>>>>>> v6ops has a draft for PD on the LAN to improve this situation.
>>>>>>>
>>>>>>> https://datatracker.ietf.org/doc/draft-ietf-v6ops-cpe-lan-pd/
>>>>>>>
>>>>>>> Please feel free to send comments, we are about to do WGLC on it.
>>>>>>>
>>>>>>
>>>>>> Hey, Tim. I hadn't read the document in a while. I see this text in
>>>>>> the last requirement:
>>>>>>
>>>>>> The IPv6 CE Router SHOULD by default provision IA_PD IA prefixes with
>>>>>> a prefix-length of 64.
>>>>>>
>>>>>> I read this as "if the DHCP client doesn't specify a narrower prefix,
>>>>>> the CE router SHOULD .. 64"
>>>>>>
>>>>>> Is that what you intended? If not, I think you need to say more. If
>>>>>> that is what you intended, this won't work, because if we stack CE routers,
>>>>>> I expect every CE router to ask for a /48, rather than not specifying, and
>>>>>> that would mean that we'd always delegate the narrowest remaining subset of
>>>>>> the outer CE router's delegation to the first inner router that makes a
>>>>>> request.
>>>>>>
>>>>> That's what the working group wanted.  The original version of this
>>>>> document had more text about how to support hierarchical or flat models.
>>>>> After a round or two discussion what came out of that was routers behind a
>>>>> CE Router are no longer a CE Router as they aren't at the customer edge.
>>>>>  The draft reflects that general consensus, that leans towards deploying a
>>>>> flat model as opposed to hierarchical, which is where the /64 length
>>>>> derives from.
>>>>>
>>>>> I think it may be time for another document to specify what to do if
>>>>> you're a Internal Router (but not SNAC).  We could include all the flat
>>>>> model text for becoming a DHCP Relay and giving out IA_PD with /64 from the
>>>>> customer edge.
>>>>>
>>>>>>
>>>>>>
>>>>> _______________________________________________
> v6ops mailing list -- v6ops@ietf.org
> To unsubscribe send an email to v6ops-leave@ietf.org
>