IETF Logo Mail Archive

Re: [Snac] Router using Ipv6 prefix length = 67

Kiran Makhijani <kiran.ietf@gmail.com> Wed, 07 June 2023 18:36 UTC

Return-Path: <kiran.ietf@gmail.com>
X-Original-To: snac@ietfa.amsl.com
Delivered-To: snac@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68628C151099 for <snac@ietfa.amsl.com>; Wed, 7 Jun 2023 11:36:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 qVxW9trhiuUf for <snac@ietfa.amsl.com>; Wed, 7 Jun 2023 11:36:57 -0700 (PDT)
Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (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 BED1CC151065 for <snac@ietf.org>; Wed, 7 Jun 2023 11:36:57 -0700 (PDT)
Received: by mail-pg1-x532.google.com with SMTP id 41be03b00d2f7-53fbb3398c8so646384a12.1 for <snac@ietf.org>; Wed, 07 Jun 2023 11:36:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686163017; x=1688755017; h=mime-version:content-language:accept-language:in-reply-to :references:message-id:date:thread-index:thread-topic:subject:cc:to :from:from:to:cc:subject:date:message-id:reply-to; bh=wtPhy3uZVhUUqYZ8Fc2JZRfBgxX5K8g/7MW+br56Rn0=; b=pyI1OufPdhc9rykzp/ykvRRypiLNE53vkFTzoJr3IzesrzfFQazgplWoFZG7FsL+PG 4O35hcaynKRS1t8bTwimhBx/0v1nOtN0WJXF8bCS9krUMsA0OPr+32IF1gu/QteqDZAm 3WyVBs0gp0CImSzrLQnPv3jk7wvx/tXekYGyyVIVqWMk+wklg/hOJ9dk+FRI5+QJWNBT 9tfriHwpKFeyFi7JZhYmOx2Hr/xOoCIUQc0Pa9HQjm3sICKmUj2LKT9QDWBgfi1MV/ZI DPhRtnfKofPIE2onTTVtkqfXRvnBMWDXPjYCGiyH3h7vnlTQAI4sFC5apUtfp/uYIC9O rCRg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686163017; x=1688755017; h=mime-version:content-language:accept-language:in-reply-to :references:message-id:date:thread-index:thread-topic:subject:cc:to :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=wtPhy3uZVhUUqYZ8Fc2JZRfBgxX5K8g/7MW+br56Rn0=; b=eUX8tcngr0MN2+jm8gKGmiYAZ6KZkb84jbxQ/oPUWi3nyAhb0Re5yObCdQeB27Ek1p Ar+mY+nPjyHmln0F1rGKWdLfHt+aZHBRroDTZuefdSTr7e8GMd28EsRaLq+gWL7l6KoE VNyN4P1jhF6XR5tztya4fjH6AMnn5tlbiv2oIVyuItH5ts3RHVRerqQb3fZmVnGbIhGJ oCNvu5LvJrEKMYg/S9j8TtITE6j6qKlFLFFplV1KFpphBi6lwk4S5Y2evmIYClUl2QPf pXI+Bi3AQipcxybHAgsnnx8ddEd5Bvyemjxep2fb/WnKoTjPwOFJPyuIDMGp+HWob9mE rN+g==
X-Gm-Message-State: AC+VfDyvkfC09GUOBzAuvBU52XdhuERK0qv4/qpBHYNhb7XFSJtY2IEi OULE03dRQK/aLBnOwcVUJQkwFB0jbTo=
X-Google-Smtp-Source: ACHHUZ5Ubrbp8gDT5ly2vuF3XwBDiR9pnCUhm73zdLcwSRzaK4Rsijyj3RFqZ8vECEVssxdJ0rxcQg==
X-Received: by 2002:a17:902:ea01:b0:1af:b80a:b964 with SMTP id s1-20020a170902ea0100b001afb80ab964mr6715443plg.5.1686163016832; Wed, 07 Jun 2023 11:36:56 -0700 (PDT)
Received: from SJ0PR03MB6469.namprd03.prod.outlook.com ([2603:1036:307:490e::5]) by smtp.gmail.com with ESMTPSA id x10-20020a170902ec8a00b001ac8e0ea157sm10715270plg.144.2023.06.07.11.36.56 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 07 Jun 2023 11:36:56 -0700 (PDT)
From: Kiran Makhijani <kiran.ietf@gmail.com>
To: Ted Lemon <mellon@fugue.com>, Michael Richardson <mcr+ietf@sandelman.ca>
CC: "snac@ietf.org" <snac@ietf.org>
Thread-Topic: [Snac] Router using Ipv6 prefix length = 67
Thread-Index: AQHZlWhSi1+2QKWeDUOfJ7mKiUdmMa96dSmAgAJZGQCAAa3yAIAAAneAgAEwgpk=
X-MS-Exchange-MessageSentRepresentingType: 1
Date: Wed, 07 Jun 2023 18:36:55 +0000
Message-ID: <SJ0PR03MB6469F578812A680E7F29B961F753A@SJ0PR03MB6469.namprd03.prod.outlook.com>
References: <39BE8173-F4D2-4B8C-A136-A5A7F441B3BF@amazon.com> <10B44E76-01E1-4A09-881D-2228B4E07508@amazon.com> <CAGwZUDvWAnFJO4KJCyd0k_ydxzZaxEZ+D9-WXFCb_gfOHWOPwA@mail.gmail.com> <786.1686096218@localhost> <CAPt1N1mqY=Psp0NN2MRd-UA9rgECiN_y-+NVA_sq=AA6FFLzzw@mail.gmail.com>
In-Reply-To: <CAPt1N1mqY=Psp0NN2MRd-UA9rgECiN_y-+NVA_sq=AA6FFLzzw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator:
X-MS-Exchange-Organization-RecordReviewCfmType: 0
Content-Type: multipart/alternative; boundary="_000_SJ0PR03MB6469F578812A680E7F29B961F753ASJ0PR03MB6469namp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/snac/M8prtykUgaXExoTj7OsUpT28IAk>
Subject: Re: [Snac] Router using Ipv6 prefix length = 67
X-BeenThere: snac@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Mailing list for discussing problems relating to the automatic connection of stub networks to existing infrastructure networks. " <snac.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/snac>, <mailto:snac-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/snac/>
List-Post: <mailto:snac@ietf.org>
List-Help: <mailto:snac-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/snac>, <mailto:snac-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jun 2023 18:36:58 -0000

Hi,
Just to clarify,

  1.  besides defining the usable prefix with prefix-length 64 bits, does it make sense to add reference to 7084 section 4.3 as suggested? (I think I’d prefer that but then I had assumed prefix will always be /64).
  2.  Second question Alan asked was about BR’s (stub-router’s) robustness. So, nothing else to be specified for that. Right?
Cheers,
Kiran (as a WG member)

From: Snac <snac-bounces@ietf.org> on behalf of Ted Lemon <mellon@fugue.com>
Date: Tuesday, June 6, 2023 at 5:12 PM
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: snac@ietf.org <snac@ietf.org>
Subject: Re: [Snac] Router using Ipv6 prefix length = 67
I think it makes sense to have the definition of “usable prefix” specify that the length needs to be 64 bits. Otherwise this turns into a DoS attack.

On Tue, 6 Jun 2023 at 20:03, Michael Richardson <mcr+ietf@sandelman.ca<mailto:mcr%2Bietf@sandelman.ca>> wrote:

I couldn't understand all of this thread.
Is this WNP3000 receiving a plen=67 prefix from upstream and doing the wrong thing?

Or is this WNP3000 receiving a plen=64 prefix from upstream, and then
splitting it up into 8 unuseable prefixes of len=67?
Or ???

I agree that the SNAC Stub router needs to defend against unuseable prefixes.
(It seems like it should be a call home and report situation, since nobody
local will know what to do.  But that's not subject to standardization)

--
Michael Richardson <mcr+IETF@sandelman.ca<mailto:mcr%2BIETF@sandelman.ca>>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide




--
Snac mailing list
Snac@ietf.org<mailto:Snac@ietf.org>
https://www.ietf.org/mailman/listinfo/snac

v2.23.0 | Report a Bug | By Email