Re: [netmod] rfc6991bis: loopback addresses

Kent Watsen <kent@watsen.net> Thu, 30 July 2020 20:55 UTC

Return-Path: <01000173a181be4b-3cb4eb13-5e3d-470c-9fc7-894a5db71272-000000@amazonses.watsen.net>
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 BADDE3A0CB9 for <netmod@ietfa.amsl.com>; Thu, 30 Jul 2020 13:55:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.com
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 UGiE7s9jfS0h for <netmod@ietfa.amsl.com>; Thu, 30 Jul 2020 13:55:03 -0700 (PDT)
Received: from a8-33.smtp-out.amazonses.com (a8-33.smtp-out.amazonses.com [54.240.8.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 605033A0CB4 for <netmod@ietf.org>; Thu, 30 Jul 2020 13:55:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1596142502; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:Feedback-ID; bh=m0tLPnSkapHcgBq+NfrIcN8lMiGvNUslOhMo5shsw+c=; b=HPRj1oeyXndusvrBBDubYg4TkmuBrNORb9XxfwAjSYB0qFKS6GWQMux0dGD/qJBH 4hl4pVypRRIEdfaYY4MeWYTvidh9549drCk9742iCtvEdyesC/Yc8dGgI+jjcbuXgkA p0XQc92NDZFh2hlbCMtEopCYIXJy9w4AGYnMHbag=
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Kent Watsen <kent@watsen.net>
In-Reply-To: <20200730134715.otyb4e6uqjylszdg@anna.jacobs.jacobs-university.de>
Date: Thu, 30 Jul 2020 20:55:01 +0000
Cc: "Nagendra Kumar Nainar (naikumar)" <naikumar@cisco.com>, "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, "netmod@ietf.org" <netmod@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <01000173a181be4b-3cb4eb13-5e3d-470c-9fc7-894a5db71272-000000@us-east-1.amazonses.com>
References: <20200717192556.63e7gfbbrn2qyqzo@anna.jacobs.jacobs-university.de> <AM6PR07MB52220AD16FAC337D4F89A674A07B0@AM6PR07MB5222.eurprd07.prod.outlook.com> <64A58592-5FD0-4752-8069-E59E62C3F699@cisco.com> <AM6PR07MB5222C7EC1927B652D7C7389DA07B0@AM6PR07MB5222.eurprd07.prod.outlook.com> <A27BF4C9-FD50-46C0-8D95-36BD778EBAC6@cisco.com> <7D333828-EF9E-4786-B820-5B4A29B37440@cisco.com> <20200730134715.otyb4e6uqjylszdg@anna.jacobs.jacobs-university.de>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-SES-Outgoing: 2020.07.30-54.240.8.33
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/4skf8hiBMNqAK8TW_1Lr0WxGbSE>
Subject: Re: [netmod] rfc6991bis: loopback addresses
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, 30 Jul 2020 20:55:05 -0000

> Thanks for pointing to the definitions in draft-nainar-mpls-lsp-ping-yang.
> With that, your request is relatively clear now

Looking at draft-nainar-mpls-lsp-ping-yang, the proposal is a “typedef” that constrains inet:ipv[46]-address so that it can only contain loopback address values.


> and the question the WG
> needs to answer is whether these types are common enough to warrant being
> part of inet-types, i.e., are there any other places where these types
> may be useful?

I don’t think so, but I’m not a routing person.


> /js

K.  // contributor