Re: [netmod] draft-ietf-netmod-rfc6991-bis - ipv6-link-local address?
Jeffrey Haas <jhaas@pfrc.org> Thu, 13 January 2022 12:43 UTC
Return-Path: <jhaas@pfrc.org>
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 39AC73A0CCD; Thu, 13 Jan 2022 04:43:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tE50NHnf57a4; Thu, 13 Jan 2022 04:43:17 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id AE5853A0CCF; Thu, 13 Jan 2022 04:43:17 -0800 (PST)
Received: from smtpclient.apple (99-59-193-67.lightspeed.livnmi.sbcglobal.net [99.59.193.67]) by slice.pfrc.org (Postfix) with ESMTPSA id 7BEA51E31E; Thu, 13 Jan 2022 07:43:16 -0500 (EST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <20220113104912.qbdgqcejnl3vrvxf@anna>
Date: Thu, 13 Jan 2022 07:43:15 -0500
Cc: draft-ietf-netmod-rfc6991-bis@ietf.org, netmod@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5777291-9E22-40BF-B8FC-2389B4E103DC@pfrc.org>
References: <93C5BEE7-4AF6-49D6-9DAB-28209B87A634@pfrc.org> <20220113104912.qbdgqcejnl3vrvxf@anna>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/5LF5-O5lo9OBhYcPuZbMbT7ICUw>
Subject: Re: [netmod] draft-ietf-netmod-rfc6991-bis - ipv6-link-local address?
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 13 Jan 2022 12:43:22 -0000
Jürgen, > On Jan 13, 2022, at 5:49 AM, Jürgen Schönwälder <j.schoenwaelder@jacobs-university.de> wrote: > > As pointed out by others, this is what I proposed back in July '21: > > typedef ipv6-address-link-local { > type ipv6-address; > pattern '[fF][eE]80:.*'; > description > "A link-local IPv6 address in the prefix fe80::/10 as defined > in section 2.5.6. of RFC 4291."; > reference > "RFC 4291: IP Version 6 Addressing Architecture"; > } > > If this serves the purpose, I can add this definition to the > inet-types module. This example had been the first time I'd seen a pattern on top of a typedef with its own pattern. That said, it seems to be what I would expect. > > Will there also be a need to have an IPv4 equivalent? For most of the routing technologies I have worked on, it's not a requirement. But it's an appropriate gap to fill and will potentially be useful for other technologies. E.g. BRAS. > > typedef ipv4-address-link-local { > type ipv4-address; > pattern '169\.254\..*'; > description > "A link-local IPv4 address in the prefix 169.254.0.0/16 as > defined in section 2.1. of RFC 3927."; > reference > "RFC 3927: Dynamic Configuration of IPv4 Link-Local Addresses"; > } -- Jeff
- [netmod] draft-ietf-netmod-rfc6991-bis - ipv6-lin… Jeffrey Haas
- Re: [netmod] draft-ietf-netmod-rfc6991-bis - ipv6… Reshad Rahman
- Re: [netmod] draft-ietf-netmod-rfc6991-bis - ipv6… Jeffrey Haas
- Re: [netmod] draft-ietf-netmod-rfc6991-bis - ipv6… Reshad Rahman
- Re: [netmod] draft-ietf-netmod-rfc6991-bis - ipv6… Jeffrey Haas
- Re: [netmod] draft-ietf-netmod-rfc6991-bis - ipv6… Jürgen Schönwälder