Re: [netmod] Changes to IPv6 zone definition in draft-ietf-netmod-rfc6991-bis-15

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 07 April 2024 19:58 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FB64C14F6AD for <netmod@ietfa.amsl.com>; Sun, 7 Apr 2024 12:58:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 5fGvKaw-i6fx for <netmod@ietfa.amsl.com>; Sun, 7 Apr 2024 12:58:29 -0700 (PDT)
Received: from mail-pj1-x1029.google.com (mail-pj1-x1029.google.com [IPv6:2607:f8b0:4864:20::1029]) (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 4D66DC14F600 for <netmod@ietf.org>; Sun, 7 Apr 2024 12:58:24 -0700 (PDT)
Received: by mail-pj1-x1029.google.com with SMTP id 98e67ed59e1d1-2a2d0ca3c92so2379821a91.0 for <netmod@ietf.org>; Sun, 07 Apr 2024 12:58:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712519903; x=1713124703; darn=ietf.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=Zi2okfLxowRuZ4Wj6feEP/IGTIRofP4VGlRMfBh6yGc=; b=QOla8FWs6k6a3g5KpyJoMeEHW7/vAhO+AenGH5Zxy+Cv2L+PXP4q+JP8jFvKRsjj6v CPxDYK+1FcRcc/xMe+6jMwoo9d7Vq6x1Wg44bsctSwWnrbFpugJqAUx3/NmNqERKs8dp m8kcLbSkrO+2WfxWWFeiiw9ogCcOmXlkUb17+8yrsSPc5g/PaeqKcv2PVRIMjwhGLQX+ Exr9CPlLQB6gz3ydal5Q9BSXenAcjJnJrFrLjrFmvzuMgdgFaAkHqEYVD2EXKftPZQOu o0u4dqb0WCbjfcViEbunGHtR4mvnszEvH8bMi8s703MtkMWgTjtcb/P4W08DrzEPs4x0 RJ1A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712519903; x=1713124703; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Zi2okfLxowRuZ4Wj6feEP/IGTIRofP4VGlRMfBh6yGc=; b=GFZ9l52JQ5knTmnE6hYciHp9IvqX2hmhHQf17R8hagQMdqa7KR2x+hFhqKKMVnZMT6 wI3tXkOmzxHfEN7pSwdGfuG261lyoC9QSGr6cZyHCW8Sh2Mp0WV5r8m21hWNJ3gFVWa/ DT2rFyA+qdL37kdugT906LUtYd0TP2AVd/P+q2oPBZyrRTXx4e1WHcBMqAiEk4w9t3nn H6JT/pmVUAaUt29UBGbMsJYi84jmrbSrT6h1+LVt6QqwR06cX/GTWAKsev1Qx7RPkcER x62S6E7M/gzuH/1BE6GuE1ceTaQfWGyt/UN3X6l6l8Iq/Jp8DUdQBkWEG2+x2JB1mik3 qQRg==
X-Gm-Message-State: AOJu0YzaQAHN8A27cZWnpDFOP6XT/eLbTEaRnBws8FwyEPfRNZlx50qb QCo6VP08idJg4yEG782hKwQhwaGH8+55IEMlln+E1JKxNgo6gCGPYtJeHpuf1KA=
X-Google-Smtp-Source: AGHT+IHnId5as3DxBUvzmHboOCr9rLgYh9LkMRWGsJ3La3rHxVQPVR9fRA/X+kXbLnuUV4MRoVrZsg==
X-Received: by 2002:a17:90a:178b:b0:29f:76d4:306a with SMTP id q11-20020a17090a178b00b0029f76d4306amr8419037pja.24.1712519903396; Sun, 07 Apr 2024 12:58:23 -0700 (PDT)
Received: from ?IPV6:2404:4400:541d:a600:44b7:2c2e:2bc6:8707? ([2404:4400:541d:a600:44b7:2c2e:2bc6:8707]) by smtp.gmail.com with ESMTPSA id s63-20020a17090a69c500b002a51dcecc49sm422544pjj.38.2024.04.07.12.58.21 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 07 Apr 2024 12:58:23 -0700 (PDT)
Message-ID: <466c7dcd-2038-47bf-b662-3b6635cccf89@gmail.com>
Date: Mon, 08 Apr 2024 07:58:20 +1200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Jürgen Schönwälder <jschoenwaelder@constructor.university>
Cc: NETMOD Working Group <netmod@ietf.org>
References: <BY5PR11MB41966FD2ECEFB84708C5A325B5869@BY5PR11MB4196.namprd11.prod.outlook.com> <16d6f918-ea40-3596-9292-d2656eec8ad4@gmail.com> <8d491135-c720-228c-efad-f1f3fa113545@gmail.com> <B655FE46-F8B9-4BAD-A4AF-7E6E2627ACE9@gmail.com> <24f6a539-3abd-4d30-afd0-bc976ccbbd8d@constructor.university> <9d40a5bb-02cb-414b-9aa5-acc532cb6786@gmail.com> <619d6dfb-b852-4efb-93f8-05e1381979e4@constructor.university>
Content-Language: en-US
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <619d6dfb-b852-4efb-93f8-05e1381979e4@constructor.university>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/SOYX6VapU4gWMG9FeA2QDPR_ST8>
Subject: Re: [netmod] Changes to IPv6 zone definition in draft-ietf-netmod-rfc6991-bis-15
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Apr 2024 19:58:33 -0000

On 08-Apr-24 04:59, Jürgen Schönwälder wrote:
> 
> On 06.04.24 22:57, Brian E Carpenter wrote:
>> On 06-Apr-24 19:52, Jürgen Schönwälder wrote:
>>
>>> I believe numeric zone identifiers were always supported so they
>>> always work as a fallback.
>>
>> Correct, but do all network elements actually support RFC4007? Maybe
>> there are devices where interfaces do not have a simple sequential
>> numbering.
>>
> 
> There is nothing that says sequential. And the native identifier for
> an interface used to be a number (and text about using the number as
> the canonical format is not new either).

That's all true, but I could imagine a device which by design requires
(say) two numbers to identify an interface (e.g. interface 3 in row 2).
That might simply be out of scope for your model, as it is for RFC 4007.

    Brian

>