
From nobody Sat Jan  2 21:06:57 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: v6ops@ietf.org
Delivered-To: v6ops@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CD6D3A13E3; Sat,  2 Jan 2021 21:06:51 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: v6ops@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: v6ops@ietf.org
Message-ID: <160965041135.14198.13421107884813288365@ietfa.amsl.com>
Date: Sat, 02 Jan 2021 21:06:51 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Qw9AHGZsKrRTNz56vrQ-8SBrRuw>
Subject: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-ehs-packet-drops-03.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jan 2021 05:06:52 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IPv6 Operations WG of the IETF.

        Title           : Operational Implications of IPv6 Packets with Extension Headers
        Authors         : Fernando Gont
                          Nick Hilliard
                          Gert Doering
                          Warren Kumari
                          Geoff Huston
                          Will (Shucheng) Liu
	Filename        : draft-ietf-v6ops-ipv6-ehs-packet-drops-03.txt
	Pages           : 20
	Date            : 2021-01-02

Abstract:
   This document summarizes the operational implications of IPv6
   extension headers specified in the IPv6 protocol specification
   (RFC8200), and attempts to analyze reasons why packets with IPv6
   extension headers are often dropped in the public Internet.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-v6ops-ipv6-ehs-packet-drops/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-v6ops-ipv6-ehs-packet-drops-03
https://datatracker.ietf.org/doc/html/draft-ietf-v6ops-ipv6-ehs-packet-drops-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-v6ops-ipv6-ehs-packet-drops-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Mon Jan  4 09:17:48 2021
Return-Path: <rbonica@juniper.net>
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 D47C63A0EA4; Mon,  4 Jan 2021 09:17:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.447
X-Spam-Level: 
X-Spam-Status: No, score=-0.447 tagged_above=-999 required=5 tests=[DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net header.b=2CWqSPUV; dkim=pass (1024-bit key) header.d=juniper.net header.b=LpNv6Oaj
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 5PJM1HqeVAe4; Mon,  4 Jan 2021 09:17:45 -0800 (PST)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A67C3A0E9F; Mon,  4 Jan 2021 09:17:42 -0800 (PST)
Received: from pps.filterd (m0108159.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 104HFHwN002402; Mon, 4 Jan 2021 09:17:42 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : content-type : mime-version; s=PPS1017; bh=Do4a/tjUy/k5CpIk9d2PYNnvZ8JklT0SJqjgYncEMms=; b=2CWqSPUVMRkEYw4U3KSY6SnWet8UmJ0o93EiHGYMmJ3Ci/7RkzTdj/mZMLMXg4Vg1N1f fvg31lq7qpkBBTeS50grlJwS4WygiSdG4u8PkIUhoFwdjue7+Q3tGfQdcaRJuSZICYcb RBJBexMKqHDm/WB7b7ztvmB/ZaaIHUw41Nz90Hqpv5nyQqmI4omOR3ZrA4GSlkZpIM6P YKCpAAEuGexHkYBK5tTsVSvZmHYuiXvks9fmJdD0S0jG1lrxtk4gehnhJRuo3cstEAI9 768Ez/UHE9xzgYkBdQrpdipYtzeHUnKymhSsokfJ8H9zuUfNd8zIdbLf2aT+B0VRRnyZ Fw== 
Received: from nam12-dm6-obe.outbound.protection.outlook.com (mail-dm6nam12lp2168.outbound.protection.outlook.com [104.47.59.168]) by mx0a-00273201.pphosted.com with ESMTP id 35tqp2j74m-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 04 Jan 2021 09:17:42 -0800
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Up9ZYp8wIAIY/g8njY5ZRrjJey0w7Yfl4psxwVQfp1G4tVCJe2bfuCHpU/mX3fkCYOemzM3CwfeJ41c4lnuEEAA5MDxraVSxDELmEssDsIRdwk0fNlwBlkEgu2lTZfziN2oOZ7uTtSH+lrmORFbwAWz8DN7HOWjqHqNn1zPddl/4sj7HW0txIC3mFCpmoYZww5HK8NgjmHk5GrcBt3+yWfaJA3JnVbl3yEiXxUdYueY3225OsL1o0g33kD/lj9EfTbZbmRfQNT98boUsB772M4oavvcGAJtsYES+tOh8JXrM05bLTXulrbbrWFFGVB8MfHzDdUDXb61BzI46BZ/X5Q==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Do4a/tjUy/k5CpIk9d2PYNnvZ8JklT0SJqjgYncEMms=; b=Bix4rJgeAursFV6IhkbQfZjnJFqG3PtHCVIpySbBhJnlG49pJiW2JWUb14yI28H9cK93quGosxgkqW+s2FYHrDHtFgLKiHiJN+4bKeNsYUHC/0SYYNNyGSM+aSUISyXpQyAZN5e6kV+XMnh+rFi8hXkVCXKJIYik3pB69czxP8zkURSoMhUz1Wvr1cnt5O7Jv1i8OOpQiDbASx1QE6zMGohUmgJfUiF0Fv6+yJ8pLyQTlHlEi0KHtHLy0cE3rVVz7vfxg7fxc+qaGrwf1VnD29ghnmrky9uDMrQewhwTxKyofqMUnB+pqz3iL4uB2RFZGgyAp/9HiDVKiIBdnB6NCg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=juniper.net; dmarc=pass action=none header.from=juniper.net; dkim=pass header.d=juniper.net; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Do4a/tjUy/k5CpIk9d2PYNnvZ8JklT0SJqjgYncEMms=; b=LpNv6Oajh0Gq9rWQOxZX1DbsHTrTiKWsW9Gy2k3Qc87evDgTEnTJvzzNJY1ShRTm9S1cKYGr+24Qjvy/yiW1B0b8Fz/PXll8psK/yFrCttcGEWIZru5aco78Y18rGcDrmB345LdjBrMqblJ1lHvTMKQhh8/yRs4Cs74ygD6z2xI=
Received: from DM6PR05MB6348.namprd05.prod.outlook.com (2603:10b6:5:122::15) by DM5PR0501MB3832.namprd05.prod.outlook.com (2603:10b6:4:7b::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3742.4; Mon, 4 Jan 2021 17:17:40 +0000
Received: from DM6PR05MB6348.namprd05.prod.outlook.com ([fe80::a435:88ed:7e2a:4fe6]) by DM6PR05MB6348.namprd05.prod.outlook.com ([fe80::a435:88ed:7e2a:4fe6%5]) with mapi id 15.20.3742.006; Mon, 4 Jan 2021 17:17:40 +0000
From: Ron Bonica <rbonica@juniper.net>
To: "draft-ietf-v6ops-ipv6-ehs-packet-drops@ietf.org" <draft-ietf-v6ops-ipv6-ehs-packet-drops@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: IPR Inquiry: draft-ietf-v6ops-ipv6-ehs-packet-drops
Thread-Index: AdbivVnXb70xoZs9SUiiR3TptTIRGA==
Date: Mon, 4 Jan 2021 17:17:40 +0000
Message-ID: <DM6PR05MB6348B66B60C6E34D06351077AED20@DM6PR05MB6348.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
dlp-product: dlpe-windows
dlp-version: 11.5.0.60
dlp-reaction: no-action
msip_labels: MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Enabled=true; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SetDate=2021-01-04T17:17:39Z;  MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Method=Standard; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Name=0633b888-ae0d-4341-a75f-06e04137d755; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SiteId=bea78b3c-4cdb-4130-854a-1d193232e5f4; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ActionId=3d19e375-8d73-45b3-b3d8-d971ffc8dbc3; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ContentBits=2
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=juniper.net;
x-originating-ip: [173.79.115.7]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 20556580-ba2b-4cb5-ebc3-08d8b0d4a41b
x-ms-traffictypediagnostic: DM5PR0501MB3832:
x-microsoft-antispam-prvs: <DM5PR0501MB38320027FCEF04B26EC1E5B6AED20@DM5PR0501MB3832.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6790;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 9hPMazcjgwLrIMneQqgd5eH9f949QuvkcjGVp9T6cQ4QWFSAikr5TZvpVzBw9hG0/BrfRowsD/VawFwKSCNcLKrjUTBWYY9BtSovRvQUY8md6O7s/XrfoDMMm7jP+hWAlOQINYd5eOrjOoP5uVK5xA7oTMPfSynlln8G+BaNA0JK+r/gVUJR3GhDLtPyzYx+CoFwqLXtXAU9X8Ds9KV5K1WriKAO5r3HwMuyWAmajAEX/2dVGMoSsP4pVPUO1LOnoxmuhBHQIT1ypT4N+GobKPWZc6Xc/YmnGFvIsJHD6zEQ73jK8konB31bkKIynN2AO90rD23DnB6nh064UeKMCzl7k1hiM6FvVPw/HF/YprKXYv7z/CQpDLHpcDop3ZWq9O9sj0HV0i6HCwx8t/Nfzg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DM6PR05MB6348.namprd05.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(396003)(366004)(136003)(346002)(376002)(39860400002)(66476007)(76116006)(52536014)(66556008)(64756008)(66446008)(66946007)(316002)(9686003)(8676002)(478600001)(33656002)(7696005)(5660300002)(110136005)(2906002)(86362001)(450100002)(8936002)(186003)(558084003)(55016002)(6506007)(26005)(71200400001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?upR5//ek+DPY68Dxiyd4BqasDGJ0ZvB0n8JwZkAl6lm62Ar780hv2juNoPQO?= =?us-ascii?Q?lzysXMMO9KApU1HDIwhPfebX9bcO4c23ZBTYl8xKCIogFLvYDrfXcVrmCLH+?= =?us-ascii?Q?QLSMftpOCfVRHbhrrIme0aRqe5xndpEBOVSKnKKGvk/x5Sb8mhxIC02lK7Zv?= =?us-ascii?Q?9eebt1t3t3V1u49PNtTw4e3Lkg64G4B2sosA2dsySj2ubjgP1mKRc+5coU9e?= =?us-ascii?Q?dp4JU5ux1FVNEeQZ5IAF8lHypG/yAx4FYZc74osjRBtMsHjckdBkkTHcBPH1?= =?us-ascii?Q?tux+kTfa9FbfYyN6ZeAPW1TxpmFGHVM8X338jxfxpJXmLRhS+NQH8AObkHx3?= =?us-ascii?Q?h0VhWAhkTwbgK1ugeOx38ZXXOfHUZLO1tZHWBRE17scOBgHoi02MOBxJfsR4?= =?us-ascii?Q?JB1Ed92fikvMZZaqkK3xPlkCw/MMWLDJa0vrM/ZvVFj54iW2WM0qHBs59SL8?= =?us-ascii?Q?x1xbuL6BmpXvEk07J3NPasOaTRABQDJlaaKgpdIWtmhOcqIH9StXmZeIUtQN?= =?us-ascii?Q?T4EzAiAt5ErrZjDysxUPOANNJIRX7uSQqJIjewDoTu6W6oKZL7NHLM2YaOTX?= =?us-ascii?Q?f36uiV+d/V2FrNUiI4+hNok5tIcuwgjd1NBsHaPYPHljlByoiye14MTcKDpa?= =?us-ascii?Q?1F4uhJhA6ErMhteFru62UqDhQd0Cc02eREGWLZXRonoWiGhL0f5MsSiN0bMH?= =?us-ascii?Q?sCj3HdbJO7YlD3bnjbKSg8H1NZPVQxKIarKNZa+md9+Q4GXLz+wi7RDvZv63?= =?us-ascii?Q?wW8/ZF4vVf4adX8myNJrzzQZA+8iIOndApV7ZcYI4q3H+5qYaQ+zfOxzi70G?= =?us-ascii?Q?cOVZlLjhoLYQgXgFe4QDyCnRU8oyWBMhveglcKR7tlHDaDfjY8yhQsJWQD0O?= =?us-ascii?Q?baNQ7lmPqDp7maaUmvOHKqR5KXmnDeFjDeqBBb/WQxOXT2wgYJleL7V/IbKF?= =?us-ascii?Q?4t2LN6WRtNtnJDllFiIb06+/kjjU0yKtK/eQNLsi7Mc=3D?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_DM6PR05MB6348B66B60C6E34D06351077AED20DM6PR05MB6348namp_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR05MB6348.namprd05.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 20556580-ba2b-4cb5-ebc3-08d8b0d4a41b
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Jan 2021 17:17:40.4194 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: tMDRWwgLVwiaB7cU5r1kOx2KL0qYYSp+CLoqdYpZB35r31oeTdUiqjW3vOvhpeYzurstj3yU8R49za5ywgtu1Q==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR0501MB3832
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-04_11:2021-01-04, 2021-01-04 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 adultscore=0 impostorscore=0 bulkscore=0 spamscore=0 clxscore=1011 malwarescore=0 mlxscore=0 suspectscore=0 phishscore=0 mlxlogscore=657 lowpriorityscore=0 priorityscore=1501 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101040112
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/dWhdSUkZhj_pSmj-aV7SNqmp9cA>
Subject: [v6ops] IPR Inquiry: draft-ietf-v6ops-ipv6-ehs-packet-drops
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jan 2021 17:17:47 -0000

--_000_DM6PR05MB6348B66B60C6E34D06351077AED20DM6PR05MB6348namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Co-Authors,

Could the co-authors of draft-ietf-v6ops-ipv6-ehs-packet-drops please respo=
nd to this email indicating whether they know of any IPR associated with th=
e draft.

                                                                           =
                                                    Ron



Juniper Business Use Only

--_000_DM6PR05MB6348B66B60C6E34D06351077AED20DM6PR05MB6348namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72" style=3D"word-wrap:=
break-word">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Co-Authors,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Could the co-authors of draft-ietf-v6ops-ipv6-ehs-pa=
cket-drops please respond to this email indicating whether they know of any=
 IPR associated with the draft.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Ron<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<br>
<p class=3D"msipfooter30b3d538" align=3D"Center" style=3D"margin:0"><span s=
tyle=3D"font-size:7.0pt;font-family:Calibri;color:#000000">Juniper Business=
 Use Only</span></p>
</div>
</body>
</html>

--_000_DM6PR05MB6348B66B60C6E34D06351077AED20DM6PR05MB6348namp_--


From nobody Mon Jan  4 09:20:18 2021
Return-Path: <gert@space.net>
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 C8BA63A0EA8 for <v6ops@ietfa.amsl.com>; Mon,  4 Jan 2021 09:20:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.188
X-Spam-Level: 
X-Spam-Status: No, score=-0.188 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=space.net
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 TkkdiOITLlcB for <v6ops@ietfa.amsl.com>; Mon,  4 Jan 2021 09:20:13 -0800 (PST)
Received: from gatekeeper1-relay.space.net (gatekeeper1-relay.space.net [IPv6:2001:608:3:85::38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2EB93A0EAC for <v6ops@ietf.org>; Mon,  4 Jan 2021 09:20:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=space.net; i=@space.net; q=dns/txt; s=esa; t=1609780813; x=1641316813; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=YwzdoY1pUfwBXhMiofHX9LVie4jGs1Vqj4Cf0todttE=; b=hejBnwuwZFVO0k8kJWWGTMcdPpX4TQDM47fwKmNVMgOmSrJIPdonJfWO IGtHq6WeG/K4H//1lRYZBmb+pkyghA/a7penw+o2QKzQOJBIHL7I918TE /YqWIyzGFDOXObkEj6mxlr04K5ToAPoAo0Wwwb7M1JqYKI/k3BEh1loNg 5TRgAN3Js9FFsQyMSsqEh5L93Fm3JU++i6XO9QmU+OuFehb0NBSUYTgE+ BShOyjC4rvL/qxFikQbH47xib3mcNZalR8k4qDX8nWyu/1DLdnDKrq0Xd 9sJ8TV9r4XFNBjPdv9hI9iB+2VEb77WwL6CWHBvW098vRd3bZF2KhYpkw g==;
IronPort-SDR: X/kzHWXeeASK/pJTNT0OC6sNgdwE62yBMBSabDG1XFlcXg9hBDCr+W/uD8Q6AwczwEB6s0w8F9 VmF+u7cRvaciYESrnZt5JQGI27HkseWM17A9QkjLG3xCCRIQc2zDcEwoXw6Eb6/FUWemK21xnQ uB8EFfYnblEXqtSNhDfcnK52o3XgXuNq4LoeEUQLfmzTOO+GJX7l3uvxki51VcBuMoucUPTXTS qiRrbHhbI57zTk+7+2DH4Dk1reBUVe3RF7NzepkQEnpXonzea/Cyo/8azIgMLGm+ieHl/yE1Zl ueA=
X-SpaceNet-SBRS: None
Received: from mobil.space.net ([195.30.115.67]) by gatekeeper1-relay.space.net with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Jan 2021 18:20:10 +0100
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 5B1C541C82 for <v6ops@ietf.org>; Mon,  4 Jan 2021 18:20:10 +0100 (CET)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 4B50F40B9E; Mon,  4 Jan 2021 18:20:10 +0100 (CET)
Received: by moebius4.space.net (Postfix, from userid 1007) id 3F008A8E9C; Mon,  4 Jan 2021 18:20:10 +0100 (CET)
Date: Mon, 4 Jan 2021 18:20:10 +0100
From: Gert Doering <gert@space.net>
To: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>
Cc: "draft-ietf-v6ops-ipv6-ehs-packet-drops@ietf.org" <draft-ietf-v6ops-ipv6-ehs-packet-drops@ietf.org>,  "v6ops@ietf.org" <v6ops@ietf.org>
Message-ID: <20210104172010.GL13005@Space.Net>
References: <DM6PR05MB6348B66B60C6E34D06351077AED20@DM6PR05MB6348.namprd05.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <DM6PR05MB6348B66B60C6E34D06351077AED20@DM6PR05MB6348.namprd05.prod.outlook.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/zmLx1h2TCdH8LOyQ4bRDZZhrv5I>
Subject: Re: [v6ops] IPR Inquiry: draft-ietf-v6ops-ipv6-ehs-packet-drops
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jan 2021 17:20:18 -0000

Hi,

On Mon, Jan 04, 2021 at 05:17:40PM +0000, Ron Bonica wrote:
> Could the co-authors of draft-ietf-v6ops-ipv6-ehs-packet-drops please respond to this email indicating whether they know of any IPR associated with the draft.

I am not aware of any IPR.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279


From nobody Mon Jan  4 09:59:52 2021
Return-Path: <nick@foobar.org>
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 78CE53A0ED2; Mon,  4 Jan 2021 09:59:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.262
X-Spam-Level: 
X-Spam-Status: No, score=-0.262 tagged_above=-999 required=5 tests=[NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-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 dGKg90a7efZn; Mon,  4 Jan 2021 09:59:49 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [46.182.8.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30C783A0EC6; Mon,  4 Jan 2021 09:59:47 -0800 (PST)
X-Envelope-To: draft-ietf-v6ops-ipv6-ehs-packet-drops@ietf.org
Received: from crumpet.local (admin.ibn.ie [46.182.8.8]) (authenticated bits=0) by mail.netability.ie (8.16.1/8.16.1) with ESMTPSA id 104Hximq002119 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Jan 2021 17:59:44 GMT (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host admin.ibn.ie [46.182.8.8] claimed to be crumpet.local
To: Ron Bonica <rbonica@juniper.net>
Cc: "draft-ietf-v6ops-ipv6-ehs-packet-drops@ietf.org" <draft-ietf-v6ops-ipv6-ehs-packet-drops@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
References: <DM6PR05MB6348B66B60C6E34D06351077AED20@DM6PR05MB6348.namprd05.prod.outlook.com>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <a8d57faf-4cc9-a523-5ca1-e2054ea453d3@foobar.org>
Date: Mon, 4 Jan 2021 17:59:42 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:52.0) Gecko/20100101 PostboxApp/7.0.43
MIME-Version: 1.0
In-Reply-To: <DM6PR05MB6348B66B60C6E34D06351077AED20@DM6PR05MB6348.namprd05.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/gerasGs1NUy5zBIhXhx97mOcol0>
Subject: Re: [v6ops] IPR Inquiry: draft-ietf-v6ops-ipv6-ehs-packet-drops
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jan 2021 17:59:51 -0000

Ron Bonica wrote on 04/01/2021 17:17:
> Could the co-authors of draft-ietf-v6ops-ipv6-ehs-packet-drops please 
> respond to this email indicating whether they know of any IPR associated 
> with the draft.

I'm not aware of any IPR associated with this draft.

Nick


From nobody Mon Jan  4 11:28:13 2021
Return-Path: <gih@apnic.net>
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 63E7B3A0E87; Mon,  4 Jan 2021 11:28:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level: 
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=apnic.net
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 BZKKfsEZgPk6; Mon,  4 Jan 2021 11:28:10 -0800 (PST)
Received: from APC01-PU1-obe.outbound.protection.outlook.com (mail-eopbgr1320045.outbound.protection.outlook.com [40.107.132.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B8FE3A1071; Mon,  4 Jan 2021 11:27:58 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=U20omP5qZzWgNduymq0fG+Qj5dEx6G3Uns2rDNRz+Pud7+GLelMA9alysdEXv7e7Wn/ZK+JfUllZqGWdeMpjgpv+5Z+P8mkqixMyeh1QF5z9IolJdxJBps/zd/auI5i1fd6/uaFhCF7w27EA2vJq2FxvRixp3RwH1uUPC0lWwUzIZMHxaAczUEryQAPtQ/5P/AarSWD5WzACMkxt95343v1xYudS7tHHP4kAK/z4Nx8PrctpD5urQ5p/LV33xGD8gqEsqLXOlwq2Im6xQ9bhlwnV1188cO20e0jPmdgoXMw8BMpnk65ZE366RpbPYz+REfoif3sKjWU9Qy8NLfHmcg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=1Q/9ef5mEmvu6tYccKscGbQ5YHCQc3PnVHehE3Dgwek=; b=mpJnlqXnA8bn+t856Wn0EGi/rrPziP2kEqCEe/jDJGwii/RuniJNCpy7UiPP9lU6MXSAMXg3JJlI1SgWewerEkKsxyneXiKydn5gw0G+mgah0T4THaPd2VfHOrasUQFc6RsD5i+x8qhCYaewDEiQejFCRHJ7jEkSh/Ru+QDLX8cESiA56Y1sVB7LOYyKs2oUBTIhkSJrUy29j5yI9vgMjYmLdVLKaizsL9QNC068gj7Ni6uIbjShGVwQ84oEfeTk90bgoywT6m3KKL/cZ7+qdwpIrq+3bF/tAZxskk+tFfQtIwlHLjybOAPKhbU0IyVXfICOgL5Z9O44NaDyhMy/JQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=apnic.net; dmarc=pass action=none header.from=apnic.net; dkim=pass header.d=apnic.net; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apnic.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=1Q/9ef5mEmvu6tYccKscGbQ5YHCQc3PnVHehE3Dgwek=; b=abDmFU9jg6L4MtjxLuWhKNAf6BuYf+lr/GAD7nOal1hHsFsuStI/rNam37jD5lUzpFP53yHE9/maoLZevLhDM9FDhI8jayufZcdso2/coRD58+cQUlmudp5vVFsbV/BliQ9LvvSqYoWX6FQsnh0l0fVonKvtAwljeF2Vh1U/5Yw=
Authentication-Results: juniper.net; dkim=none (message not signed) header.d=none;juniper.net; dmarc=none action=none header.from=apnic.net;
Received: from TYAPR04MB2286.apcprd04.prod.outlook.com (2603:1096:404:24::20) by TY2PR04MB4031.apcprd04.prod.outlook.com (2603:1096:404:8012::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3721.22; Mon, 4 Jan 2021 19:27:48 +0000
Received: from TYAPR04MB2286.apcprd04.prod.outlook.com ([fe80::3522:57e6:9766:4d5c]) by TYAPR04MB2286.apcprd04.prod.outlook.com ([fe80::3522:57e6:9766:4d5c%6]) with mapi id 15.20.3721.024; Mon, 4 Jan 2021 19:27:48 +0000
Content-Type: text/plain; charset=us-ascii
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <a8d57faf-4cc9-a523-5ca1-e2054ea453d3@foobar.org>
Date: Tue, 5 Jan 2021 06:27:40 +1100
Cc: "draft-ietf-v6ops-ipv6-ehs-packet-drops@ietf.org" <draft-ietf-v6ops-ipv6-ehs-packet-drops@ietf.org>,  "v6ops@ietf.org" <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <81EA50C8-7B1D-4E56-BE37-6F8900F53167@apnic.net>
References: <DM6PR05MB6348B66B60C6E34D06351077AED20@DM6PR05MB6348.namprd05.prod.outlook.com> <a8d57faf-4cc9-a523-5ca1-e2054ea453d3@foobar.org>
To: Ron Bonica <rbonica@juniper.net>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
X-Originating-IP: [2001:44b8:110b:5100:440:191b:b1e3:3449]
X-ClientProxiedBy: SYAPR01CA0025.ausprd01.prod.outlook.com (2603:10c6:1:1::13) To TYAPR04MB2286.apcprd04.prod.outlook.com (2603:1096:404:24::20)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from 2001-44b8-110b-5100-0440-191b-b1e3-3449.static.ipv6.internode.on.net (2001:44b8:110b:5100:440:191b:b1e3:3449) by SYAPR01CA0025.ausprd01.prod.outlook.com (2603:10c6:1:1::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3721.19 via Frontend Transport; Mon, 4 Jan 2021 19:27:47 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 40272312-ebfb-4f02-5f51-08d8b0e6d1f2
X-MS-TrafficTypeDiagnostic: TY2PR04MB4031:
X-Microsoft-Antispam-PRVS: <TY2PR04MB4031DE7C848A25DBA3A13719B8D20@TY2PR04MB4031.apcprd04.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:8882;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: Fr9XHGioEQhABK9wBaCJj9fd0XoqmEiWBoaoWhoUTvsV8mNKX8GkYfQ4F9/VJPQvD0GSkEHOl+Ka4mPuacp/Mc1fwauBT5aAzwtZIMfluUvMx0KCUT0hbJqcQJ+Kh1Q1E2DTF42KACbYFxih6G6y7LhjB7SNSGIBN8lBe5/+9t9wW+CPICqHPOKijl74g50SzFSmrY66GVeRpTM1SzWw9ZCEXFsHKYG8Gb/kmrG1DbOuCGzLUminHYZUKFAtO7VtL8OUZgpD6vHSVxE2r0Mcb0oeHj4bjccql0YBJETvJKl+XSPGItoK6HVsVnPYhcBMjeTWqalhndeHpGtRSHgU93Mw0LrGLNcdahseX3AjMDrjoqD0wdxmFfL3b4J+4pxO9ZaQQZQajkl34QWz62095ruhmcL/CLkIN8IYInQKV8Im3LvFFzUPdYAeAcLlEPLO
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:TYAPR04MB2286.apcprd04.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(136003)(376002)(346002)(396003)(39840400004)(366004)(8676002)(2906002)(6486002)(316002)(6916009)(2616005)(54906003)(86362001)(66946007)(66556008)(66476007)(6666004)(8936002)(36756003)(4744005)(5660300002)(33656002)(16526019)(186003)(52116002)(4326008)(6506007)(6512007)(53546011)(478600001)(45980500001); DIR:OUT; SFP:1101; 
X-MS-Exchange-AntiSpam-MessageData: =?us-ascii?Q?zRuCUYbNrwC9RwRs7cHo1iD4d9S4SF8ClIeFw84Ayfg3wI75D1sAFDGuw249?= =?us-ascii?Q?/bD8ZOQ5jgDstfJEt1mA970Gf0CB/Twm0GfELyH/pUPPD08+xBAV8Lyz8BGF?= =?us-ascii?Q?KyYZiDOnbeY3BpTbe/NcKCgHaOafdTPjOm4sVsoOFap39C2rcqRrTmwMl7m9?= =?us-ascii?Q?2T6gIdnqbIgpa4TAwmueSHXzc3vwGsWg6NxMHFu0KkazFj/apOJwTN/hbH+M?= =?us-ascii?Q?zkhGFWM82HKsEsBQBoxTLR+maqA+o5DYqS2/n+suLxsXEGEsiYraWuGP9iRY?= =?us-ascii?Q?tPYBJrBkW23xYEehp5NSKvHtLSUpJKoQGOnOscboqNX9tshadl4PioXgsanV?= =?us-ascii?Q?HMyNvwiYazPY+U9WTJT6uYvEzh4Oh4LGbGFfgAbM3TXIhtqV7v2gqPAspDus?= =?us-ascii?Q?697oyySf0VjLbxdSO+Ag3mqlg3s56vcwsdxEgDkyLlQFXRaRPCfFsQ8q3GLM?= =?us-ascii?Q?zXMQtuoWJ7PjtNcEm/IcVhJSuNNPPMOPisz1JgY9xsX6jG864U8WTkW1unej?= =?us-ascii?Q?3J5taQ10PsOruC9YFUGkGiB6Q3Yi2EyZrHP4sXfZvKqfRSqXgtVbtsEURw0N?= =?us-ascii?Q?GDqDg+wAxJyj449xhKtQaPRUWuhwhRF6CDAzPCD7czhKntZ+dZe3Mz1ZCD3x?= =?us-ascii?Q?RpUYGTBQFRyxf4C6Xmh1B5GsT6sx78z4S15wwG2p7vlFA+9p+52HrUuhtvo8?= =?us-ascii?Q?MhgvAT811KNb/VeOnbWOlmVAFK9iXlJUQiHMN+f/fMA2GCAZ88EGckOmqhaT?= =?us-ascii?Q?+WvhwfTIxupIUstDne+k3KW/WEMFAW01DEhQQIFznBLYo8BLTgzfzBWxsqQS?= =?us-ascii?Q?nMyu/KH6KemqvZ2BghMbepBP/xo0hzIPm3jd57HpXIq3df34hVaDWupKkTYl?= =?us-ascii?Q?aXa2cMSH2+3GA0BM8M720Ru6pHtMlQoEVOrurafDaaRFeqdl5zvod3X16GE8?= =?us-ascii?Q?Mjvi5PCnijBB+mgZRx6V+F/SvpH2Q3qw9yrfAguUDs9LpdiH6qEmqrumyYio?= =?us-ascii?Q?u2hkoXcqfDFJG7UDrvBsbKsXDmi4UCjVJDnAbArOSE6JrVPQfeM7dST7R6uf?= =?us-ascii?Q?ENKNx/rS?=
X-OriginatorOrg: apnic.net
X-MS-Exchange-CrossTenant-AuthSource: TYAPR04MB2286.apcprd04.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 04 Jan 2021 19:27:48.1955 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 127d8d0d-7ccf-473d-ab09-6e44ad752ded
X-MS-Exchange-CrossTenant-Network-Message-Id: 40272312-ebfb-4f02-5f51-08d8b0e6d1f2
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: ShA2409qj3wFI+blJASbVaNWAgaaHlGYgl5fCoqMWZPffyERfBTQTT461dh+hCy2
X-MS-Exchange-Transport-CrossTenantHeadersStamped: TY2PR04MB4031
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/jA-DT27PmaR5ZmU9bzQkRsD2nHg>
Subject: Re: [v6ops] IPR Inquiry: draft-ietf-v6ops-ipv6-ehs-packet-drops
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jan 2021 19:28:12 -0000

nor am I

Geoff


> On 5 Jan 2021, at 4:59 am, Nick Hilliard <nick@foobar.org> wrote:
>=20
> Ron Bonica wrote on 04/01/2021 17:17:
>> Could the co-authors of draft-ietf-v6ops-ipv6-ehs-packet-drops please re=
spond to this email indicating whether they know of any IPR associated with=
 the draft.
>=20
> I'm not aware of any IPR associated with this draft.
>=20
> Nick
>=20


From nobody Mon Jan  4 15:08:36 2021
Return-Path: <warren@kumari.net>
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 A765D3A09FA for <v6ops@ietfa.amsl.com>; Mon,  4 Jan 2021 15:08:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.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 GSYInU-0Luly for <v6ops@ietfa.amsl.com>; Mon,  4 Jan 2021 15:08:31 -0800 (PST)
Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F6993A0A26 for <v6ops@ietf.org>; Mon,  4 Jan 2021 15:08:28 -0800 (PST)
Received: by mail-lf1-x12f.google.com with SMTP id b26so68395780lff.9 for <v6ops@ietf.org>; Mon, 04 Jan 2021 15:08:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=egJ/XtgnX+chrXmXsgBzuouwhuOyFeOSdYW3Pn3DB00=; b=f9zpA9RUdDraf45KleLxavuk7GdDIRZNyOg1di0goUkLO0HPdVS2h6iP7blxkPT9nM jsTmqNnTny9RMh012Z5H6mNSjMh2AufjUlFVvs8q0f2bcAhrQwzFpihENrGhrnfXwMW5 Z7jIyiKOsO899V4RXjZU2TGpviLWfwNUe6X7M1z8DqxC2LOyqM+aL/FpByGEzyjnCFI4 gN21PN2ICIPnhq9GdVo2dwc5fpU81MrjKEGSgmfjjxwP9313vvXlxQuKVrxFtvuh1jnu WAoHVdjfkNwjK6gm3bGqRnQziOoxqwaUhzTQ/I2xL9SmCyfBd1dwgbgFJ3CKoX7d6dLD PkGg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=egJ/XtgnX+chrXmXsgBzuouwhuOyFeOSdYW3Pn3DB00=; b=gRSYZWENThVLqE7yNX99xr+VMCetIZ0Zgk14wL8UjD9qoBjPOlPS8YaYRHaids7z5m wcVLJHRVdQ2MxQSJfhcEedV8noSfSLBNBl+BXoZOHsFS8yXUlAA0RjxqtHFKExJOmBht sYwq/+CKhZZw8gRU0LOdRPUfH1PSoxDNvxaRB5Ngm7zHWk5+GegE8DgfyCI7t5iSDSrY ZhG48BkAx/TyUOUA+NeEaH6ZhTRQBhahrRiBjvQwc0JslTn7mRzzibYXHKiX6rriHPiU w5gU56HANON7bfpVZ9YacjqJVWnk1inrZkSy6OMYLsYO4OzT7xexjrC2AugfWLelshkS vz4w==
X-Gm-Message-State: AOAM531r+nWEjPnl/+niU+YYTniY6jCaV5/Qyhyk/YaC0pEsaQYEqRX5 iBdKxO5C4kdxpvSoiWYY2a34cn+SKMoeD992zzGijQ==
X-Google-Smtp-Source: ABdhPJyrOGz7QS2Rbk0zoeJsWB/bJQmekzeEAgqkMjkxe6jneIdB08U1GUkW9vrS6JgeU1wkGo3fz8p8/lciYl5cTIA=
X-Received: by 2002:a2e:9b8a:: with SMTP id z10mr34439635lji.126.1609801706678;  Mon, 04 Jan 2021 15:08:26 -0800 (PST)
MIME-Version: 1.0
References: <DM6PR05MB6348B66B60C6E34D06351077AED20@DM6PR05MB6348.namprd05.prod.outlook.com> <a8d57faf-4cc9-a523-5ca1-e2054ea453d3@foobar.org> <81EA50C8-7B1D-4E56-BE37-6F8900F53167@apnic.net>
In-Reply-To: <81EA50C8-7B1D-4E56-BE37-6F8900F53167@apnic.net>
From: Warren Kumari <warren@kumari.net>
Date: Mon, 4 Jan 2021 18:07:50 -0500
Message-ID: <CAHw9_iKjxwsoY8tDbHxyC=0t7tRshZwsPC_Zm5guJ_RWxgch8w@mail.gmail.com>
To: Geoff Huston <gih@apnic.net>
Cc: Ron Bonica <rbonica@juniper.net>,  "draft-ietf-v6ops-ipv6-ehs-packet-drops@ietf.org" <draft-ietf-v6ops-ipv6-ehs-packet-drops@ietf.org>,  "v6ops@ietf.org" <v6ops@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/onFFZMVTNnmjBBGo9wsygLWKMD4>
Subject: Re: [v6ops] IPR Inquiry: draft-ietf-v6ops-ipv6-ehs-packet-drops
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jan 2021 23:08:35 -0000

On Mon, Jan 4, 2021 at 2:28 PM Geoff Huston <gih@apnic.net> wrote:
>
> nor am I
>
> Geoff

Nor I...

W

>
>
> > On 5 Jan 2021, at 4:59 am, Nick Hilliard <nick@foobar.org> wrote:
> >
> > Ron Bonica wrote on 04/01/2021 17:17:
> >> Could the co-authors of draft-ietf-v6ops-ipv6-ehs-packet-drops please =
respond to this email indicating whether they know of any IPR associated wi=
th the draft.
> >
> > I'm not aware of any IPR associated with this draft.
> >
> > Nick
> >
>


--=20
The computing scientist=E2=80=99s main challenge is not to get confused by =
the
complexities of his own making.
  -- E. W. Dijkstra


From nobody Tue Jan  5 05:24:30 2021
Return-Path: <etmetz@gmail.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 135C13A0E9F; Tue,  5 Jan 2021 05:24:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v5lt7vzrECca; Tue,  5 Jan 2021 05:24:27 -0800 (PST)
Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 219223A0EA0; Tue,  5 Jan 2021 05:24:26 -0800 (PST)
Received: by mail-lf1-x12f.google.com with SMTP id m12so72511578lfo.7; Tue, 05 Jan 2021 05:24:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1SQgl1XLTSw1VjLcpmH5efHx0gFWWCCKuW9qAlluYJE=; b=gSU72xZH7COxCmLrtlFKpYwc6nf2Hak0ks8yA6HFOSZoqkBzUvcVvr6WJFAkkNpC5w ku/Ps3NhOZOIU/DoSBuUQJE5VYFhw8GJoo/FEUCfu1+E1z9mhnuPIfMlAfqLGNMPZzuS rngLWIg7Lddqwj6rgaLsGAus0Ws+xOzljFZrJO42TluAW4zjFIs0oPzXhH/gVzKiErsD OfOQCPNgZFMN09ZqS14Dm6dq+TED7ZDYwKqa8LV1XI730wBNZrUNwykIWxCnSh4ZqY0W v9FvWRudpxWZEND8TMkl8ZUJpIAPJFUzywfZq6BDSF8Gz2aTv8XMnEwi1OOGyYNpSS2G +L+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1SQgl1XLTSw1VjLcpmH5efHx0gFWWCCKuW9qAlluYJE=; b=FnoAcgx0isLRAEknfs4qYOvnG77rACVKwXzL3uvg5FLyTJkAEerVxLZOh1YZy1mYXb 4anLY5uXBmQOX76Mhe9vGydeF7MYOPVnTQNzwr3NeXUgVnhOh1/bvBlaIbXa8JuNpJbx ajEpJUwETM2Ls5+jaheD7yleqjDZ6GB2frnrjLUj0/8JqRL5sRPcYAgplrd3JpVODJ4O bth9aMtnXKUs3hTatygJ3xdZl17ND+SnPgsAz+PBRZyR1LrikH/pZ9XkgBmb10hUecsZ j0sRkPUBDT2Gj0jPNq20BLWJaXjQFa8iWnRacCIFO+rjVwTY7sTI3al/7e5dljnQF9lR 8jJA==
X-Gm-Message-State: AOAM530bwHpj417gqgcmbPJyHfAqJT/DMc5qu8b8Zs/WARlJyzp1TRP3 6EodDQySrLTsqPBn5Mbe/dFNPY26CEjp4dPmIEo=
X-Google-Smtp-Source: ABdhPJy7Qa4lLDorvXA0BQsAr4jZyAyFkCPyFAYFZnA8q/Gc/WEI3Wcw9LnhU3ZHyhOthuu7QCI+AiYdSELYa6FksdI=
X-Received: by 2002:a19:c650:: with SMTP id w77mr32343768lff.107.1609853064998;  Tue, 05 Jan 2021 05:24:24 -0800 (PST)
MIME-Version: 1.0
References: <160770241261.18071.12524922630334294118@ietfa.amsl.com> <fb832698-039e-baa5-ed6f-4d5a97e7b354@gmail.com> <299f492f-4cb7-fa9d-967f-b2a5df49034e@si6networks.com> <759efdb1-a59c-788c-0c7a-5a8ca2ced904@gmail.com> <b20425a3-8069-3823-4610-79c93714ad2f@si6networks.com> <fa8c56d3-5d64-ae55-5be1-a3ec7d8f130d@gmail.com> <20201231103010.GL13005@Space.Net> <47fb8588-98ee-bf50-b377-921f75dc72e0@gmail.com>
In-Reply-To: <47fb8588-98ee-bf50-b377-921f75dc72e0@gmail.com>
From: Eduard Metz <etmetz@gmail.com>
Date: Tue, 5 Jan 2021 14:24:14 +0100
Message-ID: <CAG=3OHf5jSPgr-R8Ny=uHQi4exSEf7x-QVNDjePO59314NtoYg@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Gert Doering <gert@space.net>, Fernando Gont <fgont@si6networks.com>,  IPv6 Operations <v6ops@ietf.org>, draft-gont-v6ops-ipv6-addressing-considerations@ietf.org
Content-Type: multipart/alternative; boundary="0000000000001473eb05b82720f6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/xFcBv35KAn8FuMOya3bwrbbFMH4>
Subject: Re: [v6ops] I-D Action: draft-gont-v6ops-ipv6-addressing-considerations-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jan 2021 13:24:29 -0000

--0000000000001473eb05b82720f6
Content-Type: text/plain; charset="UTF-8"

Maybe the last column should be "Applicable to Internet" (no / no / yes)
or something along these lines. I assume the point here is to indicate that
link-local and ULA cannot be used on the Internet.

cheers,
  Eduard

On Thu, Dec 31, 2020 at 8:48 PM Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> Gert,
>
> On 31-Dec-20 23:30, Gert Doering wrote:
> > Hi,
> >
> > On Thu, Dec 31, 2020 at 02:00:33PM +1300, Brian E Carpenter wrote:
> >> 4. The following table attempts to show some of the distinctions
> >> involved (simplified). View in a fixed-width font. You may not
> >> agree with it...
> >>
> >> Unicast       Prefix      IID        Routeable   Announced
> >> address       assigned    assigned
> >> types         by          by
> >> -----------------------------------------------------------
> >> Link-local    fixed       host       no          no
> >>               by RFC
> >>
> >> ULA           user/RA     host or    yes         IGP only
> >>               (random)    DHCPv6
> >>
> >> GUA           IANA/RIR/   host or    yes         IGP,
> >>               ISP/user/RA DHCPv6                 BGP4 by policy
> >
> > Indeed, I am not agreeing - as there is nothing that prevents ULAs from
> > being transported by BGP.
>
> Indeed, nothing in the laws of physics, but it's default-forbidden by
> an RFC ;-). Exactly how to express that in a short table is tricky.
>
> I think we all agree about this; what Fernando's draft shows is that it
> is quite hard to describe, and the word "global" is confusing.
> (Really for the same reason that URLs were renamed from "universal"
> to "uniform" in 1994. But renaming "global" at this stage seems almost
> impossible.)
>
>    Brian
>
> >
> > We use ULAs for "services that must never reachable from the Internet",
> > and our routing being what it is, everything is transported by BGP - only
> > loopbacks in OSPF.  The difference is "do we announce it to other ASes?"
> >
> > So maybe this should be "generally expected to be visible by other
> > networks on the Internet" (ULA: no, GUA: yes).
> >
> > But that's neither precise nor does "expected" mandate anything - I might
> > want to announce our ULA prefix to our sister company, using eBGP, and
> > I might decide to not announce our GUA IPv6 PI /48 that we use for our
> > backbone infra "because people are not supposed to send packets there"...
> >
> > Gert Doering
> >         -- NetMaster
> >
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

--0000000000001473eb05b82720f6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Maybe the last column should be &quot;App=
licable to Internet&quot; (no / no / yes)=C2=A0 or something along these li=
nes. I assume the point here is to indicate that link-local and ULA cannot =
be used on the Internet.</div><div dir=3D"ltr"><br></div><div>cheers,</div>=
<div>=C2=A0 Eduard</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">On Thu, Dec 31, 2020 at 8:48 PM Brian E Carpenter &lt;<a =
href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a>=
&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Gert=
,<br>
<br>
On 31-Dec-20 23:30, Gert Doering wrote:<br>
&gt; Hi,<br>
&gt; <br>
&gt; On Thu, Dec 31, 2020 at 02:00:33PM +1300, Brian E Carpenter wrote:<br>
&gt;&gt; 4. The following table attempts to show some of the distinctions<b=
r>
&gt;&gt; involved (simplified). View in a fixed-width font. You may not<br>
&gt;&gt; agree with it...<br>
&gt;&gt;<br>
&gt;&gt; Unicast=C2=A0 =C2=A0 =C2=A0 =C2=A0Prefix=C2=A0 =C2=A0 =C2=A0 IID=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Routeable=C2=A0 =C2=A0Announced<br>
&gt;&gt; address=C2=A0 =C2=A0 =C2=A0 =C2=A0assigned=C2=A0 =C2=A0 assigned<b=
r>
&gt;&gt; types=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0by=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 by<br>
&gt;&gt; -----------------------------------------------------------<br>
&gt;&gt; Link-local=C2=A0 =C2=A0 fixed=C2=A0 =C2=A0 =C2=A0 =C2=A0host=C2=A0=
 =C2=A0 =C2=A0 =C2=A0no=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 no<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0by RFC<br>
&gt;&gt;=C2=A0 =C2=A0<br>
&gt;&gt; ULA=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0user/RA=C2=A0 =C2=A0 =
=C2=A0host or=C2=A0 =C2=A0 yes=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0IGP only<br=
>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0(random)=C2=
=A0 =C2=A0 DHCPv6<br>
&gt;&gt;<br>
&gt;&gt; GUA=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0IANA/RIR/=C2=A0 =C2=A0=
host or=C2=A0 =C2=A0 yes=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0IGP,<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0ISP/user/RA =
DHCPv6=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0BGP4 by=
 policy<br>
&gt; <br>
&gt; Indeed, I am not agreeing - as there is nothing that prevents ULAs fro=
m <br>
&gt; being transported by BGP.<br>
<br>
Indeed, nothing in the laws of physics, but it&#39;s default-forbidden by<b=
r>
an RFC ;-). Exactly how to express that in a short table is tricky.<br>
<br>
I think we all agree about this; what Fernando&#39;s draft shows is that it=
<br>
is quite hard to describe, and the word &quot;global&quot; is confusing.<br=
>
(Really for the same reason that URLs were renamed from &quot;universal&quo=
t;<br>
to &quot;uniform&quot; in 1994. But renaming &quot;global&quot; at this sta=
ge seems almost<br>
impossible.)<br>
<br>
=C2=A0 =C2=A0Brian<br>
<br>
&gt; <br>
&gt; We use ULAs for &quot;services that must never reachable from the Inte=
rnet&quot;,<br>
&gt; and our routing being what it is, everything is transported by BGP - o=
nly<br>
&gt; loopbacks in OSPF.=C2=A0 The difference is &quot;do we announce it to =
other ASes?&quot;<br>
&gt; <br>
&gt; So maybe this should be &quot;generally expected to be visible by othe=
r<br>
&gt; networks on the Internet&quot; (ULA: no, GUA: yes).<br>
&gt; <br>
&gt; But that&#39;s neither precise nor does &quot;expected&quot; mandate a=
nything - I might<br>
&gt; want to announce our ULA prefix to our sister company, using eBGP, and=
<br>
&gt; I might decide to not announce our GUA IPv6 PI /48 that we use for our=
<br>
&gt; backbone infra &quot;because people are not supposed to send packets t=
here&quot;...<br>
&gt; <br>
&gt; Gert Doering<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0-- NetMaster<br>
&gt; <br>
<br>
_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6ops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a><br>
</blockquote></div></div>

--0000000000001473eb05b82720f6--


From nobody Tue Jan  5 08:08:25 2021
Return-Path: <gert@space.net>
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 6EE313A0DE4 for <v6ops@ietfa.amsl.com>; Tue,  5 Jan 2021 08:08:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=space.net
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 Li3M_LW6J9pe for <v6ops@ietfa.amsl.com>; Tue,  5 Jan 2021 08:08:22 -0800 (PST)
Received: from gatekeeper1-relay.space.net (gatekeeper1-relay.space.net [IPv6:2001:608:3:85::38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3B563A0E4C for <v6ops@ietf.org>; Tue,  5 Jan 2021 08:08:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=space.net; i=@space.net; q=dns/txt; s=esa; t=1609862902; x=1641398902; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=W5ZpPEc6Tua61m1v/fqBiw6Vsy6oE7oAY6reUpdyNuw=; b=h6ZVDIZEXSpEaqjJxihhZhfSNcOMSRm8nDnm5Wv4LvLnVi+nHhYTKCKP lwm9xvUWhRC7F8t+yDYhlhxlqKq+FkupiJA0Sa9RDI9iDXl9jl89HBznH BPbHXs/qh7uYGn9B8Yh70sU4bXqFeBE8tSp6fhLidE4mRcwGNBchsyozJ kHyfkw3Eu6U04UUL6J9p7jvlmu/rW8XF+NcWPB0Oi9ukUDv0FrXz9WNsl fBIgBV/x9lit1yD8qv7fVIearHgdc6WD3EkBKmXLJMCrVcpf176eZpt1K b2+/X2cAn3HoBFMl5ckMpU2noAECpiiRCff/panlFXJIHJudAHI8p7u9o Q==;
IronPort-SDR: +4iHf5s8yEwc5yheWWuliTKBCRdpwI68wJVVtQpiVAE1OnKVxY1hgozp/+OjNdxXZ3N0Z9Rvas 2gp2WJ1txnp+bKD5B7uG+DVdnK3byllBlBxy2Pde03Lr4og1NATptwZSohkAZacT+XLF9z5/J1 nW3mata4y7GBn5HH4BYo/0EVZCy0rFAxR2IXY2aSTqCSSH67nwSI9QXnNQi7FRFlZeLRKJCZQp P+WXuYFBCGrtgFmnLsV7qbtcdCuEym/t9/aXqbbaamRINNClUzyGoSuE4riy+Ay/e/lxCivHVo STY=
X-SpaceNet-SBRS: None
Received: from mobil.space.net ([195.30.115.67]) by gatekeeper1-relay.space.net with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Jan 2021 17:08:15 +0100
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id A3E4E427F9 for <v6ops@ietf.org>; Tue,  5 Jan 2021 17:08:15 +0100 (CET)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 2942041144; Tue,  5 Jan 2021 17:08:15 +0100 (CET)
Received: by moebius4.space.net (Postfix, from userid 1007) id 238D1AAAA7; Tue,  5 Jan 2021 17:08:15 +0100 (CET)
Date: Tue, 5 Jan 2021 17:08:15 +0100
From: Gert Doering <gert@space.net>
To: Eduard Metz <etmetz@gmail.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, Gert Doering <gert@space.net>, Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>, draft-gont-v6ops-ipv6-addressing-considerations@ietf.org
Message-ID: <20210105160815.GQ13005@Space.Net>
References: <160770241261.18071.12524922630334294118@ietfa.amsl.com> <fb832698-039e-baa5-ed6f-4d5a97e7b354@gmail.com> <299f492f-4cb7-fa9d-967f-b2a5df49034e@si6networks.com> <759efdb1-a59c-788c-0c7a-5a8ca2ced904@gmail.com> <b20425a3-8069-3823-4610-79c93714ad2f@si6networks.com> <fa8c56d3-5d64-ae55-5be1-a3ec7d8f130d@gmail.com> <20201231103010.GL13005@Space.Net> <47fb8588-98ee-bf50-b377-921f75dc72e0@gmail.com> <CAG=3OHf5jSPgr-R8Ny=uHQi4exSEf7x-QVNDjePO59314NtoYg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="r9rt257+ZOQamewJ"
Content-Disposition: inline
In-Reply-To: <CAG=3OHf5jSPgr-R8Ny=uHQi4exSEf7x-QVNDjePO59314NtoYg@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/UjPzNZSVSJmUgCP3jK841XgLiIo>
Subject: Re: [v6ops] I-D Action: draft-gont-v6ops-ipv6-addressing-considerations-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jan 2021 16:08:24 -0000

--r9rt257+ZOQamewJ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Tue, Jan 05, 2021 at 02:24:14PM +0100, Eduard Metz wrote:
> Maybe the last column should be "Applicable to Internet" (no / no / yes)
> or something along these lines. I assume the point here is to indicate th=
at
> link-local and ULA cannot be used on the Internet.

What is "the Internet"?

We're an ISP, so if we use ULAs on our infrastructure, outside any
firewalls (but not announcing to other ASes, or leaking packets) - is
that "used on the Internet" or not?

Gert Doering
        -- NetMaster
--=20
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Em=
mer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279

--r9rt257+ZOQamewJ
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEruB5jRHVM+CjiYD131bAZeTOf8UFAl/0juwACgkQ31bAZeTO
f8W6iA//TVCp0MfnNKsPi1kwcqarrqWzDo8MDuvWwPGp5BuKqfl+sNENix6j3up0
U9oKSxuFBgRhU5BmYnpJP5NwVOppRYBKK8MnCgPVWhXH39COsU2c72A9R8i8G97n
I41aY63nfiAvovhSznYg8u8DlwKzCdIlINpa4GrAXGbb3lT8YUGMQzsmMJNQzJu2
HVpQt+ATiqbL9bxipN63ks4Rp93VQ3jJzKWCxq/gEwS/OpT5HoRQ5chpNL6buYmf
keBEgKCVypGEUQMRirPPGICy2vRz6P23vmYz81gZX7+srp/IeYuaxF6zL2+Ec7V0
8ovBcQyw2Kx+2vpxufLqmtxPPOWhU0hDtV/uuSPboaWCIi9RLhi67hTx3WE8UuUU
WjOsaKpjef8nMkyvfDBsfUKdMv3yLsStER+ludcyuV49BtbXhofzbxZd3aj67cZM
2PiOl1kVZ+Ikq6oHk43Nm+AQtNLo3wIxXXt22MsbtGwgRQehAdgJbizcgvsigAdh
cc+fh4saBfOlDGXn7iUcjt1m2MBlHCv+4wunWkVkVeQgSzaTh/5WRMofw+LHgmef
HV43/c8LjqmjN2N4erovTLu2zDbgeDrz2Tn5l3PNPauug/ISS2ZD4sWSWCLC3nJt
nFvPNU/64ivHUXi9AlQCToOXkAxa/0N3A+fqnnIm7i09nCNkaPA=
=T3i9
-----END PGP SIGNATURE-----

--r9rt257+ZOQamewJ--


From nobody Tue Jan  5 16:22:38 2021
Return-Path: <fgont@si6networks.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 EE11C3A0E94; Tue,  5 Jan 2021 16:22:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.162
X-Spam-Level: 
X-Spam-Status: No, score=-2.162 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-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 b3oMYKPL1rTs; Tue,  5 Jan 2021 16:22:34 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D4EE3A0CE5; Tue,  5 Jan 2021 16:22:31 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id AE74B283B8F; Wed,  6 Jan 2021 00:22:27 +0000 (UTC)
To: Ron Bonica <rbonica@juniper.net>, "draft-ietf-v6ops-ipv6-ehs-packet-drops@ietf.org" <draft-ietf-v6ops-ipv6-ehs-packet-drops@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
References: <DM6PR05MB6348B66B60C6E34D06351077AED20@DM6PR05MB6348.namprd05.prod.outlook.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <036305eb-8e33-67e8-c6c7-4ddeb5b1751e@si6networks.com>
Date: Tue, 5 Jan 2021 21:21:50 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <DM6PR05MB6348B66B60C6E34D06351077AED20@DM6PR05MB6348.namprd05.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/kZPTvTxXfh0YkCVGrl8r4LfRdPw>
Subject: Re: [v6ops] IPR Inquiry: draft-ietf-v6ops-ipv6-ehs-packet-drops
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 00:22:37 -0000

Hi, Ron,

I'm not aware of any IPR associated with this document.

Thanks!
Fernando




On 4/1/21 14:17, Ron Bonica wrote:
> Co-Authors,
> 
> Could the co-authors of draft-ietf-v6ops-ipv6-ehs-packet-drops please 
> respond to this email indicating whether they know of any IPR associated 
> with the draft.
> 
>                                                                    
>                                                               Ron
> 
> 
> Juniper Business Use Only
> 


-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Tue Jan  5 17:21:23 2021
Return-Path: <fgont@si6networks.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 B5AD03A108E; Tue,  5 Jan 2021 17:21:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, 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 4bnZu7Xtp6RO; Tue,  5 Jan 2021 17:21:17 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A96D3A0FB3; Tue,  5 Jan 2021 17:21:13 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id B48A8284516; Wed,  6 Jan 2021 01:21:06 +0000 (UTC)
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com>
To: "6man@ietf.org" <6man@ietf.org>, IPv6 Operations <v6ops@ietf.org>
From: Fernando Gont <fgont@si6networks.com>
X-Forwarded-Message-Id: <160989494094.6024.7402128068704112703@ietfa.amsl.com>
Message-ID: <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com>
Date: Tue, 5 Jan 2021 22:20:55 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <160989494094.6024.7402128068704112703@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Kt7dNn0ds9HOgQp9GY4-rNchS3U>
Subject: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 01:21:22 -0000

Folks,

Based on the recent discussion on the v6ops list 
(https://mailarchive.ietf.org/arch/msg/v6ops/b7r35HgOb-6dfxsDoW8c4FtGnZo//), 
I've posted this new I-D, meant to discuss the scope of ULAs:

Title: "Scope of Unique Local IPv6 Unicast Addresses"
I-D: https://tools.ietf.org/id/draft-gont-6man-ipv6-ula-scope-00.txt


Short version of the story:

ULAs are formally part of the GUA space. However, the characteristics of 
ULAs do not seem to match the definition of global scope from RFC4007 
(IPv6 Scope Addr Architecture). ULA seem to have a scope of 
scope(link-local) < scope(ULA) < scope(GUA).

This is not only a terminology thing (which I think is nevertheless 
important to get right) but also has practical implications. For 
example, there's a python library that considers ULAs as "not global", 
and "private" -- contradicting the current RFC4291/RFC4193 specs.

Prior to posting this document, we had some on-list discussion (on the 
v6ops list) and also some off-list discussion with some of you (bcc'ed).

The opinions have been in one of these camps:

1) the current specs are coherent and there's no problem

2) There's a problem with the definition of "global scope" -- so ULAs 
*are* global scope, but global scope does not really stand for the 
definition in RFC4007.

3) The definitions in RFC4007 are correct, and thus the scope of ULAs is 
not really global, but scopee(link-local) < scope(ULAs) < scope(global)


While this document does propose a way out (it assumes #3 above, and 
acts accordingly), I believe the first step is to agree on what "global 
scope" means and, subsequently, whether ULAs are really "global scope" 
or not. Since opinions on the topic have vary a lot (as noted above), 
I've posted this I-D and I'm sending this note for further input from 
the WG.

Thanks!

Regards,
Fernando




-------- Forwarded Message --------
Subject: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt
Date: Tue, 05 Jan 2021 17:02:20 -0800
From: internet-drafts@ietf.org
To: Fernando Gont <fgont@si6networks.com>


A new version of I-D, draft-gont-6man-ipv6-ula-scope-00.txt
has been successfully submitted by Fernando Gont and posted to the
IETF repository.

Name:		draft-gont-6man-ipv6-ula-scope
Revision:	00
Title:		Scope of Unique Local IPv6 Unicast Addresses
Document date:	2021-01-05
Group:		Individual Submission
Pages:		8
URL: 
https://www.ietf.org/archive/id/draft-gont-6man-ipv6-ula-scope-00.txt
Status: 
https://datatracker.ietf.org/doc/draft-gont-6man-ipv6-ula-scope/
Htmlized: 
https://datatracker.ietf.org/doc/html/draft-gont-6man-ipv6-ula-scope
Htmlized: 
https://tools.ietf.org/html/draft-gont-6man-ipv6-ula-scope-00


Abstract:
    Unique Local IPv6 Unicast Addresses (ULAs) are formally part of the
    IPv6 Global Unicast address space.  However, the semantics of ULAs
    clearly contradict the definition of "global scope".  This document
    discusses the why the terminology employed for the specification of
    ULAs is problematic, along with some practical consequences of the
    current specification of ULAs.  Finally, it formally updates RFC4291
    and RFC4193 such that the scope of ULAs is defined as "local".

 


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat




From nobody Tue Jan  5 18:01:14 2021
Return-Path: <markzzzsmith@gmail.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 278643A0D2A; Tue,  5 Jan 2021 18:01:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.598
X-Spam-Level: 
X-Spam-Status: No, score=-0.598 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.998, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Y16jCpfkva-F; Tue,  5 Jan 2021 18:01:05 -0800 (PST)
Received: from mail-ot1-x329.google.com (mail-ot1-x329.google.com [IPv6:2607:f8b0:4864:20::329]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF7EC3A0D05; Tue,  5 Jan 2021 18:01:04 -0800 (PST)
Received: by mail-ot1-x329.google.com with SMTP id b24so1736552otj.0; Tue, 05 Jan 2021 18:01:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=e4jNDger57+idXBpKrmMk9dDH+WVc4CyfDfylyy4sug=; b=BQKN9NXIyYRfowfpSyBWnB/ohkc3fPsZ3xjqyDTw683Ihcuveo0SaApAIwCZybUSEw cMbp+oN/k0zP+9aU9WpEJwqXz0i15gWBSWWHwfMk0+/U0mWVgiZPdKm/GwVuVjiAuVIR Z80guenFHgQkEIuu4oB8it3wvGcVtYd36jUhmh5XFXSttTWQ5Iu+CAELoaeH7oCz3xA4 JSUnQQAVR3I2czWH9sDzswuqH/SpEfDc7IJlYBDRp2FYPEao9i1DgRrDLWXXseP4o581 vp7W2zeWCMFZEJn6iyqYNjsoU5kOQaRW7zEKbPWPEGTc5q8ERcFcj8PJyjVWv7LAT5HY 85Sw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=e4jNDger57+idXBpKrmMk9dDH+WVc4CyfDfylyy4sug=; b=Rjt+ThZ2YcYyIcJ+yP39R/exsoNmAa7mGjJG7RolSXQHa3ySDAKDkzO0WTptnumCL8 BTWcUZJjm0LvNMEErRJwM7Fe+D9BRP1ljRwahsnbGNTOuKwek1CEwnyRTN+d9W4sGtJe tUzCKoW54HyGNwE2ktAMjlmpnb8IMVt5mvlFrVvUBQhRF2IN1vnjMX2KmdOuq5mJDwuA LHW0MLTrXwQuj9IWgZJARx6xqUdApKXxe6UlJrsBUdXFu3lyPy9zH1w6oDWSjufO2KWT Oask+2837ssVBVv2gGdaGI2/ahMNkjAuYslGfAzOZDtydJURQpdPnAoAwlqZdLt/pUgD fM0w==
X-Gm-Message-State: AOAM533u6dl1JIKCjZ6+SbL9/XwELyEFqM5NOqt6MwFtxz3qoreheTWP CoR4I/SyvHC9WtZg8vrQd+6W92tstFwYMeMU8BA3ZquqD8c=
X-Google-Smtp-Source: ABdhPJxt0J/YTR1O6MDJhBVf4VyZ1drSlq6xj6jnuf/HH8KCcakN++ZC7ZebtIrOcgALUG24d66cKNQa9j5P6lHlLIM=
X-Received: by 2002:a05:6830:1517:: with SMTP id k23mr1740995otp.348.1609898464162;  Tue, 05 Jan 2021 18:01:04 -0800 (PST)
MIME-Version: 1.0
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com>
In-Reply-To: <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Wed, 6 Jan 2021 13:00:36 +1100
Message-ID: <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Cc: 6MAN <6man@ietf.org>, IPv6 Operations <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000014b8c605b831b23b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/9aqmowgPACvYJf6_G03I5NRKXgM>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 02:01:09 -0000

--00000000000014b8c605b831b23b
Content-Type: text/plain; charset="UTF-8"

On Wed, 6 Jan 2021, 12:21 Fernando Gont, <fgont@si6networks.com> wrote:

> Folks,
>
> Based on the recent discussion on the v6ops list
> (https://mailarchive.ietf.org/arch/msg/v6ops/b7r35HgOb-6dfxsDoW8c4FtGnZo//),
>
> I've posted this new I-D, meant to discuss the scope of ULAs:
>
> Title: "Scope of Unique Local IPv6 Unicast Addresses"
> I-D: https://tools.ietf.org/id/draft-gont-6man-ipv6-ula-scope-00.txt
>
>
> Short version of the story:
>
> ULAs are formally part of the GUA space. However, the characteristics of
> ULAs do not seem to match the definition of global scope from RFC4007
> (IPv6 Scope Addr Architecture). ULA seem to have a scope of
> scope(link-local) < scope(ULA) < scope(GUA).
>
> This is not only a terminology thing (which I think is nevertheless
> important to get right) but also has practical implications. For
> example, there's a python library that considers ULAs as "not global",
> and "private" -- contradicting the current RFC4291/RFC4193 specs.
>
> Prior to posting this document, we had some on-list discussion (on the
> v6ops list) and also some off-list discussion with some of you (bcc'ed).
>
> The opinions have been in one of these camps:
>
> 1) the current specs are coherent and there's no problem
>
> 2) There's a problem with the definition of "global scope" -- so ULAs
> *are* global scope, but global scope does not really stand for the
> definition in RFC4007.


> 3) The definitions in RFC4007 are correct, and thus the scope of ULAs is
> not really global, but scopee(link-local) < scope(ULAs) < scope(global)
>

The thing that is really missing from "global scope" is what scope or
domain is being described? Forwarding scope? Uniqueness scope? Some other
scope (DNS visibility is probably another one). All of them?

ULAs are intended to be globally unique addresses, but not to be globally
(Internet) forwardable. Their forwarding scope is limited to non-global,
either within a single local network, or between a set of local networks
that have agreed to forward their respective ULA /48 prefixes between each
other, overriding the default of local networks only forwarding scope.
(Ethernet addresses are a similar example, globally unique addresses, link
only forwarding scope.)

GUAs also are intended to be globally unique addresses, but are intended to
be globally (Internet) forwardable.

There isn't really a ULA equivalent in IPv4, although I think a lot of the
arguments in RFC1627, "Network 10 Considered Harmful (Some Practices
Shouldn't be Codified)" would have been arguments for one e.g, "The lesson
that we learned was that every IP address ought to be globally unique,
independent of its attachment to the Internet." (There is a statement about
effectively everything attached to the Internet too, however that's 1994
Internet naivety, before DDoSes and Internet wide scanning for and
exploiting of vulnerabilities were much of a thing.)

Regards,
Mark.


>
> While this document does propose a way out (it assumes #3 above, and
> acts accordingly), I believe the first step is to agree on what "global
> scope" means and, subsequently, whether ULAs are really "global scope"
> or not. Since opinions on the topic have vary a lot (as noted above),
> I've posted this I-D and I'm sending this note for further input from
> the WG.
>
> Thanks!
>
> Regards,
> Fernando
>
>
>
>
> -------- Forwarded Message --------
> Subject: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt
> Date: Tue, 05 Jan 2021 17:02:20 -0800
> From: internet-drafts@ietf.org
> To: Fernando Gont <fgont@si6networks.com>
>
>
> A new version of I-D, draft-gont-6man-ipv6-ula-scope-00.txt
> has been successfully submitted by Fernando Gont and posted to the
> IETF repository.
>
> Name:           draft-gont-6man-ipv6-ula-scope
> Revision:       00
> Title:          Scope of Unique Local IPv6 Unicast Addresses
> Document date:  2021-01-05
> Group:          Individual Submission
> Pages:          8
> URL:
> https://www.ietf.org/archive/id/draft-gont-6man-ipv6-ula-scope-00.txt
> Status:
> https://datatracker.ietf.org/doc/draft-gont-6man-ipv6-ula-scope/
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-gont-6man-ipv6-ula-scope
> Htmlized:
> https://tools.ietf.org/html/draft-gont-6man-ipv6-ula-scope-00
>
>
> Abstract:
>     Unique Local IPv6 Unicast Addresses (ULAs) are formally part of the
>     IPv6 Global Unicast address space.  However, the semantics of ULAs
>     clearly contradict the definition of "global scope".  This document
>     discusses the why the terminology employed for the specification of
>     ULAs is problematic, along with some practical consequences of the
>     current specification of ULAs.  Finally, it formally updates RFC4291
>     and RFC4193 such that the scope of ULAs is defined as "local".
>
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

--00000000000014b8c605b831b23b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"auto"><div><br><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Wed, 6 Jan 2021, 12:21 Fernando Go=
nt, &lt;<a href=3D"mailto:fgont@si6networks.com" rel=3D"noreferrer" target=
=3D"_blank">fgont@si6networks.com</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">Folks,<br>
<br>
Based on the recent discussion on the v6ops list <br>
(<a href=3D"https://mailarchive.ietf.org/arch/msg/v6ops/b7r35HgOb-6dfxsDoW8=
c4FtGnZo//" rel=3D"noreferrer noreferrer noreferrer" target=3D"_blank">http=
s://mailarchive.ietf.org/arch/msg/v6ops/b7r35HgOb-6dfxsDoW8c4FtGnZo//</a>),=
 <br>
I&#39;ve posted this new I-D, meant to discuss the scope of ULAs:<br>
<br>
Title: &quot;Scope of Unique Local IPv6 Unicast Addresses&quot;<br>
I-D: <a href=3D"https://tools.ietf.org/id/draft-gont-6man-ipv6-ula-scope-00=
.txt" rel=3D"noreferrer noreferrer noreferrer" target=3D"_blank">https://to=
ols.ietf.org/id/draft-gont-6man-ipv6-ula-scope-00.txt</a><br>
<br>
<br>
Short version of the story:<br>
<br>
ULAs are formally part of the GUA space. However, the characteristics of <b=
r>
ULAs do not seem to match the definition of global scope from RFC4007 <br>
(IPv6 Scope Addr Architecture). ULA seem to have a scope of <br>
scope(link-local) &lt; scope(ULA) &lt; scope(GUA).<br>
<br>
This is not only a terminology thing (which I think is nevertheless <br>
important to get right) but also has practical implications. For <br>
example, there&#39;s a python library that considers ULAs as &quot;not glob=
al&quot;, <br>
and &quot;private&quot; -- contradicting the current RFC4291/RFC4193 specs.=
<br>
<br>
Prior to posting this document, we had some on-list discussion (on the <br>
v6ops list) and also some off-list discussion with some of you (bcc&#39;ed)=
.<br>
<br>
The opinions have been in one of these camps:<br>
<br>
1) the current specs are coherent and there&#39;s no problem<br>
<br>
2) There&#39;s a problem with the definition of &quot;global scope&quot; --=
 so ULAs <br>
*are* global scope, but global scope does not really stand for the <br>
definition in RFC4007.</blockquote></div></div><div dir=3D"auto"><div class=
=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
3) The definitions in RFC4007 are correct, and thus the scope of ULAs is <b=
r>
not really global, but scopee(link-local) &lt; scope(ULAs) &lt; scope(globa=
l)<br></blockquote></div></div><div dir=3D"auto"><br></div><div dir=3D"auto=
">The thing that is really missing from &quot;global scope&quot; is what sc=
ope or domain is being described? Forwarding scope? Uniqueness scope? Some =
other scope (DNS visibility is probably another one). All of them?</div><di=
v dir=3D"auto"><br></div><div dir=3D"auto">ULAs are intended to be globally=
 unique addresses, but not to be globally (Internet) forwardable. Their for=
warding scope is limited to non-global, either within a single local networ=
k, or between a set of local networks that have agreed to forward their res=
pective ULA /48 prefixes between each other, overriding the default of loca=
l networks only forwarding scope. (Ethernet addresses are a similar example=
, globally unique addresses, link only forwarding scope.)</div><div dir=3D"=
auto"><br></div><div dir=3D"auto">GUAs also are intended to be globally uni=
que addresses, but are intended to be globally (Internet) forwardable.</div=
><div dir=3D"auto"><br></div><div></div><div>There isn&#39;t really a ULA e=
quivalent in IPv4, although I think a lot of the arguments in RFC1627, &quo=
t;<span style=3D"color:rgb(0,0,0);white-space:pre-wrap">Network 10 Consider=
ed Harmful </span><span style=3D"color:rgb(0,0,0);white-space:pre-wrap">(So=
me Practices Shouldn&#39;t be Codified)&quot; would have been arguments for=
 one e.g, &quot;</span>The lesson that we learned was that every IP address=
 ought to be globally unique, independent of its attachment to the Internet=
.&quot; (There is a statement about effectively everything attached to the =
Internet too, however that&#39;s 1994 Internet naivety, before DDoSes and I=
nternet wide scanning for and exploiting of vulnerabilities were much of a =
thing.)</div><div><span style=3D"color:rgb(0,0,0);white-space:pre-wrap"><br=
></span></div><div><span style=3D"color:rgb(0,0,0);white-space:pre-wrap">Re=
gards,</span></div><div><span style=3D"color:rgb(0,0,0);white-space:pre-wra=
p">Mark.</span></div><div dir=3D"auto"><br></div><div dir=3D"auto"><div cla=
ss=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
While this document does propose a way out (it assumes #3 above, and <br>
acts accordingly), I believe the first step is to agree on what &quot;globa=
l <br>
scope&quot; means and, subsequently, whether ULAs are really &quot;global s=
cope&quot; <br>
or not. Since opinions on the topic have vary a lot (as noted above), <br>
I&#39;ve posted this I-D and I&#39;m sending this note for further input fr=
om <br>
the WG.<br>
<br>
Thanks!<br>
<br>
Regards,<br>
Fernando<br>
<br>
<br>
<br>
<br>
-------- Forwarded Message --------<br>
Subject: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt=
<br>
Date: Tue, 05 Jan 2021 17:02:20 -0800<br>
From: <a href=3D"mailto:internet-drafts@ietf.org" rel=3D"noreferrer norefer=
rer" target=3D"_blank">internet-drafts@ietf.org</a><br>
To: Fernando Gont &lt;<a href=3D"mailto:fgont@si6networks.com" rel=3D"noref=
errer noreferrer" target=3D"_blank">fgont@si6networks.com</a>&gt;<br>
<br>
<br>
A new version of I-D, draft-gont-6man-ipv6-ula-scope-00.txt<br>
has been successfully submitted by Fernando Gont and posted to the<br>
IETF repository.<br>
<br>
Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-gont-6man-ipv6-ula-scop=
e<br>
Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A000<br>
Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Scope of Unique Local IPv6 Unicast=
 Addresses<br>
Document date:=C2=A0 2021-01-05<br>
Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Individual Submission<br>
Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 8<br>
URL: <br>
<a href=3D"https://www.ietf.org/archive/id/draft-gont-6man-ipv6-ula-scope-0=
0.txt" rel=3D"noreferrer noreferrer noreferrer" target=3D"_blank">https://w=
ww.ietf.org/archive/id/draft-gont-6man-ipv6-ula-scope-00.txt</a><br>
Status: <br>
<a href=3D"https://datatracker.ietf.org/doc/draft-gont-6man-ipv6-ula-scope/=
" rel=3D"noreferrer noreferrer noreferrer" target=3D"_blank">https://datatr=
acker.ietf.org/doc/draft-gont-6man-ipv6-ula-scope/</a><br>
Htmlized: <br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-gont-6man-ipv6-ula-s=
cope" rel=3D"noreferrer noreferrer noreferrer" target=3D"_blank">https://da=
tatracker.ietf.org/doc/html/draft-gont-6man-ipv6-ula-scope</a><br>
Htmlized: <br>
<a href=3D"https://tools.ietf.org/html/draft-gont-6man-ipv6-ula-scope-00" r=
el=3D"noreferrer noreferrer noreferrer" target=3D"_blank">https://tools.iet=
f.org/html/draft-gont-6man-ipv6-ula-scope-00</a><br>
<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0 Unique Local IPv6 Unicast Addresses (ULAs) are formally part =
of the<br>
=C2=A0 =C2=A0 IPv6 Global Unicast address space.=C2=A0 However, the semanti=
cs of ULAs<br>
=C2=A0 =C2=A0 clearly contradict the definition of &quot;global scope&quot;=
.=C2=A0 This document<br>
=C2=A0 =C2=A0 discusses the why the terminology employed for the specificat=
ion of<br>
=C2=A0 =C2=A0 ULAs is problematic, along with some practical consequences o=
f the<br>
=C2=A0 =C2=A0 current specification of ULAs.=C2=A0 Finally, it formally upd=
ates RFC4291<br>
=C2=A0 =C2=A0 and RFC4193 such that the scope of ULAs is defined as &quot;l=
ocal&quot;.<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer noreferrer noreferrer" target=3D"_blank">tool=
s.ietf.org</a>.<br>
<br>
The IETF Secretariat<br>
<br>
<br>
<br>
_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org" rel=3D"noreferrer noreferrer" target=3D"_=
blank">v6ops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferrer n=
oreferrer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listin=
fo/v6ops</a><br>
</blockquote></div></div></div>
</div>

--00000000000014b8c605b831b23b--


From nobody Tue Jan  5 18:10:40 2021
Return-Path: <fgont@si6networks.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 46E633A10EB; Tue,  5 Jan 2021 18:10:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.161
X-Spam-Level: 
X-Spam-Status: No, score=-2.161 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, 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 gqzm64xGl0_X; Tue,  5 Jan 2021 18:10:35 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 013253A10E9; Tue,  5 Jan 2021 18:10:34 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 85F232837B6; Wed,  6 Jan 2021 02:10:30 +0000 (UTC)
To: Gert Doering <gert@space.net>, Eduard Metz <etmetz@gmail.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, IPv6 Operations <v6ops@ietf.org>, draft-gont-v6ops-ipv6-addressing-considerations@ietf.org
References: <160770241261.18071.12524922630334294118@ietfa.amsl.com> <fb832698-039e-baa5-ed6f-4d5a97e7b354@gmail.com> <299f492f-4cb7-fa9d-967f-b2a5df49034e@si6networks.com> <759efdb1-a59c-788c-0c7a-5a8ca2ced904@gmail.com> <b20425a3-8069-3823-4610-79c93714ad2f@si6networks.com> <fa8c56d3-5d64-ae55-5be1-a3ec7d8f130d@gmail.com> <20201231103010.GL13005@Space.Net> <47fb8588-98ee-bf50-b377-921f75dc72e0@gmail.com> <CAG=3OHf5jSPgr-R8Ny=uHQi4exSEf7x-QVNDjePO59314NtoYg@mail.gmail.com> <20210105160815.GQ13005@Space.Net>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <f7974fc1-28da-34c4-b8d6-b1d88d6ec73a@si6networks.com>
Date: Tue, 5 Jan 2021 23:09:25 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <20210105160815.GQ13005@Space.Net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ZA9Mks7kgj_FkvFQmKedJt2r0as>
Subject: Re: [v6ops] I-D Action: draft-gont-v6ops-ipv6-addressing-considerations-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 02:10:38 -0000

On 5/1/21 13:08, Gert Doering wrote:
> Hi,
> 
> On Tue, Jan 05, 2021 at 02:24:14PM +0100, Eduard Metz wrote:
>> Maybe the last column should be "Applicable to Internet" (no / no / yes)
>> or something along these lines. I assume the point here is to indicate that
>> link-local and ULA cannot be used on the Internet.
> 
> What is "the Internet"?
> 
> We're an ISP, so if we use ULAs on our infrastructure, outside any
> firewalls (but not announcing to other ASes, or leaking packets) - is
> that "used on the Internet" or not?

Agreed that "Applicable to Internet" is probably not a good taxonomy.

The proper (and useful) taxonomy is that of "scope". ULAs clearly don't 
have a global scope (as per the definition in RFC4007).

Given a ULA prefix (say, fd12:3456:7890:abcd::/64), it doesn't globally 
(and uniquely) identify a link. Similarly, nobody is in the position of 
publishing a ROA or restricting which AS can originate packets from such 
prefix.

IMO, generating the "Global ID" of ULAs from a PRNG does reduce the 
possibility of collisions *when a limited number of ULA-based networks 
are interconnected* -- but the birthday paradox tells you can't expect 
the ULA prefixes to be globally unique. There's more to "global scope" 
than simply asserting that if you interconnect, say, two networks the 
chances of colliding prefixes will be small.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Tue Jan  5 18:45:09 2021
Return-Path: <fgont@si6networks.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 3648A3A0418; Tue,  5 Jan 2021 18:45:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.16
X-Spam-Level: 
X-Spam-Status: No, score=-2.16 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, 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 gLkHb31cw-vY; Tue,  5 Jan 2021 18:45:03 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F27EA3A040B; Tue,  5 Jan 2021 18:45:02 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 438632837EF; Wed,  6 Jan 2021 02:44:57 +0000 (UTC)
To: Mark Smith <markzzzsmith@gmail.com>
Cc: 6MAN <6man@ietf.org>, IPv6 Operations <v6ops@ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <2e80ec51-ec66-16c7-7c9e-a6e8d632c5de@si6networks.com>
Date: Tue, 5 Jan 2021 23:44:49 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/aGUXkDtKuaLhntlSeR2cGNkir4M>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 02:45:07 -0000

Hi, Mark,

Thanks a lot for your comments! In-line....

On 5/1/21 23:00, Mark Smith wrote:
[...]
>     Prior to posting this document, we had some on-list discussion (on the
>     v6ops list) and also some off-list discussion with some of you (bcc'ed).
> 
>     The opinions have been in one of these camps:
> 
>     1) the current specs are coherent and there's no problem
> 
>     2) There's a problem with the definition of "global scope" -- so ULAs
>     *are* global scope, but global scope does not really stand for the
>     definition in RFC4007.
> 
> 
>     3) The definitions in RFC4007 are correct, and thus the scope of
>     ULAs is
>     not really global, but scopee(link-local) < scope(ULAs) < scope(global)
> 
> The thing that is really missing from "global scope" is what scope or 
> domain is being described? Forwarding scope? Uniqueness scope? Some 
> other scope (DNS visibility is probably another one). All of them?

FWIW, the definition of "scope" as per RFC4007 has to do with being able 
to being able to uniquely identify an interface. i.e., "uniqueness" from 
your list.

As such, forwarding scope should always be smaller than that (i.e., 
address: where the thing is, route: how to get there).



> ULAs are intended to be globally unique addresses, but not to be 
> globally (Internet) forwardable.

The math in RFC4193 for "uniqueness" considers *only a reduced number of 
uLA-based networks being inter-connected*. So, when computing global 
uniqueness, you should consider *all ULA prefixes in use*, not just 
those of networks you are interconnecting. And when you do that, you get 
a very high probability of collisions (~1).



> Their forwarding scope is limited to 
> non-global, either within a single local network, or between a set of 
> local networks that have agreed to forward their respective ULA /48 
> prefixes between each other, overriding the default of local networks 
> only forwarding scope. (Ethernet addresses are a similar example, 
> globally unique addresses, link only forwarding scope.)

Not really: Ethernet Addresses (when "U/L" bit set) are centrally 
assigned. When not set, they only have local significance, and are not 
globally unique.  The analogy is that ULAs are like local Ethernet 
addresses, whereas ULA-C would be similar to Universal/global Ethernet 
addresses.


> GUAs also are intended to be globally unique addresses, but are intended 
> to be globally (Internet) forwardable.

The birthday paradox tells you that with a 40-bit Global ID, you cannot 
really expect ULA prefixes to be globally-unique.



> There isn't really a ULA equivalent in IPv4,

ULAs are the equivalent of RFC1918, with the addition of:

1) More bits for the addresses (both the prefix, subnet id, and 
interface ID)

2) A requirement to generate ULA prefixes from a PRNG -- something that 
wouldn't have made sense for RFC1918, anyway, because you only have a 
limited number of bits for the addresses.



> although I think a lot of 
> the arguments in RFC1627, "Network 10 Considered Harmful (Some Practices 
> Shouldn't be Codified)" would have been arguments for one e.g, "The 
> lesson that we learned was that every IP address ought to be globally 
> unique, independent of its attachment to the Internet." 

How could you possibly achieve that without a central registry, and only 
40 bits (think birthday paradox)?


Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Tue Jan  5 20:38:31 2021
Return-Path: <farmer@umn.edu>
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 F32F63A0F0F for <v6ops@ietfa.amsl.com>; Tue,  5 Jan 2021 20:38:30 -0800 (PST)
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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
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 BZ6P8mCzrr5R for <v6ops@ietfa.amsl.com>; Tue,  5 Jan 2021 20:38:28 -0800 (PST)
Received: from mta-p7.oit.umn.edu (mta-p7.oit.umn.edu [134.84.196.207]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D16CD3A0F02 for <v6ops@ietf.org>; Tue,  5 Jan 2021 20:38:28 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mta-p7.oit.umn.edu (Postfix) with ESMTP id 4D9c7R6NpZz9vbK2 for <v6ops@ietf.org>; Wed,  6 Jan 2021 04:38:27 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p7.oit.umn.edu ([127.0.0.1]) by localhost (mta-p7.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id brB_O7hEApbw for <v6ops@ietf.org>; Tue,  5 Jan 2021 22:38:27 -0600 (CST)
Received: from mail-ej1-f70.google.com (mail-ej1-f70.google.com [209.85.218.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p7.oit.umn.edu (Postfix) with ESMTPS id 4D9c7R2qtyz9vZ5D for <v6ops@ietf.org>; Tue,  5 Jan 2021 22:38:27 -0600 (CST)
DMARC-Filter: OpenDMARC Filter v1.3.2 mta-p7.oit.umn.edu 4D9c7R2qtyz9vZ5D
DKIM-Filter: OpenDKIM Filter v2.11.0 mta-p7.oit.umn.edu 4D9c7R2qtyz9vZ5D
Received: by mail-ej1-f70.google.com with SMTP id h17so833050ejk.21 for <v6ops@ietf.org>; Tue, 05 Jan 2021 20:38:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WQdUxq1ytyVplLkVJOIk96RjBVwPNCJ/nPb6Oz5naKQ=; b=inOgmPtwvtn0c/EEMLF9CblCHi8TRuviUFT48jETru4k8ENVbqIBuxUMDtu3EqV06B ovgYTkEez1sDb9jTAOGmUDZ0RSG3F2JcbqHYgiha8IwZVAm820KvtvZJIRxcFMpZ5PpE NZmr0hf3dNrbgNeD/sqlEu+jFqcWYIYEefr9us0kEi6Tgn60D44j4wm3ZlOMFFFViudu +ePilF6wmsupi80a1htqZPMoKyVRkcQxOGlPVmrw6fB+vzHis5h4Ad1bkjIz9kbtnzrC 5vUXUhjngF4EsfMkHPh5rfA1c/baFMPlcMFdMZoZHQBXEsdhotZ7zOudvU2tZPRyi6Hs TqXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WQdUxq1ytyVplLkVJOIk96RjBVwPNCJ/nPb6Oz5naKQ=; b=e3qs8sT5N9ZSbAjNcW5xLvIH6g2vLcF4Ba6CDIqNQahUUyLthUWRrwVLAT7uxb0WnG gRBKHAwpOTGdF5eExphlYbrPyrfjTzYHw6r3Joo2MCdtiXRm6B/14rsc/fMdt+xj0aR7 +7kYDlM9jNr4LZqW9kXMcqWZZIX+lsbd9jHtoHiuEjXfnMubR1yupvLhopwilZMfZU07 mtbAhhWTolc5Agwe5blU+pmeFzu8wxeitDv4IxUtNuwR20loTwGW18inEAv5oSAA+2v8 0orYSWCcoc+6B/ejwQ+7aQZGCTTkk9RcMbYJU0ojBsXaKNIbDw/pN67Tsp5FTSUXsFOH yrVg==
X-Gm-Message-State: AOAM530Dco4z47/Zz2n8kJE6CH2RsDJIMJ+tK27PEMZdtbd+uAPVBpDw BI3hsFz09XSLQ+3Y0iQlAn0SBBP0z8ZDkdRLN0KbOBbjNCtrko1FWcJR44X6zBhZg8vp2Ji5im0 g9BSW3kWTX1UnFYtnwsjGiNHelA==
X-Received: by 2002:a17:906:4fcc:: with SMTP id i12mr557830ejw.32.1609907905732;  Tue, 05 Jan 2021 20:38:25 -0800 (PST)
X-Google-Smtp-Source: ABdhPJyqcJbBLz5gh1h2Pe475I6c9jU6ucsqH5hGMVpZuszEadvlLI576eY0mtD5GybNRdG+jEmGZGK2c3wbVtWTeYo=
X-Received: by 2002:a17:906:4fcc:: with SMTP id i12mr557814ejw.32.1609907905388;  Tue, 05 Jan 2021 20:38:25 -0800 (PST)
MIME-Version: 1.0
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com>
In-Reply-To: <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com>
From: David Farmer <farmer@umn.edu>
Date: Tue, 5 Jan 2021 22:38:09 -0600
Message-ID: <CAN-Dau344H7xgD0Q_O54c=R08zFRFjToO8BHt=ssauxgEH7ynA@mail.gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Cc: "6man@ietf.org" <6man@ietf.org>, IPv6 Operations <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d27cd705b833e449"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/mgc5N74rqY9UFm1LR_5W4L1R7vY>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 04:38:31 -0000

--000000000000d27cd705b833e449
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I think this is the right direction the previous draft indirectly defined a
new scope "non-global", I much prefer explicitly defining a new local scope=
.

I would add something like the following to better define the relationship
between the three scopes;

The boundary of the link-local scope is strongly defined, limiting the
extent of the link-local scope to an individual link. However, in contrast,
the boundary of the local scope is weakly defined, it is amorphous and
imprecise. In some instances, the extent of the local scope can be a single
site, in other instances, a group of unrelated sites, a single
organization, or even a cooperating group of organizations. Furthermore,
the extent of an individual instance of the local scope doesn't necessarily
remain constant, it may expand or contract over time as the local situation
dictates, for example when two organizations merge. Nevertheless, the
extent of the local scope doesn=E2=80=99t encompass the entirety of the Int=
ernet
which the global scope does.


On Tue, Jan 5, 2021 at 7:21 PM Fernando Gont <fgont@si6networks.com> wrote:

> Folks,
>
> Based on the recent discussion on the v6ops list
> (https://mailarchive.ietf.org/arch/msg/v6ops/b7r35HgOb-6dfxsDoW8c4FtGnZo/=
/),
>
> I've posted this new I-D, meant to discuss the scope of ULAs:
>
> Title: "Scope of Unique Local IPv6 Unicast Addresses"
> I-D: https://tools.ietf.org/id/draft-gont-6man-ipv6-ula-scope-00.txt
>
>
> Short version of the story:
>
> ULAs are formally part of the GUA space. However, the characteristics of
> ULAs do not seem to match the definition of global scope from RFC4007
> (IPv6 Scope Addr Architecture). ULA seem to have a scope of
> scope(link-local) < scope(ULA) < scope(GUA).
>
> This is not only a terminology thing (which I think is nevertheless
> important to get right) but also has practical implications. For
> example, there's a python library that considers ULAs as "not global",
> and "private" -- contradicting the current RFC4291/RFC4193 specs.
>
> Prior to posting this document, we had some on-list discussion (on the
> v6ops list) and also some off-list discussion with some of you (bcc'ed).
>
> The opinions have been in one of these camps:
>
> 1) the current specs are coherent and there's no problem
>
> 2) There's a problem with the definition of "global scope" -- so ULAs
> *are* global scope, but global scope does not really stand for the
> definition in RFC4007.
>
> 3) The definitions in RFC4007 are correct, and thus the scope of ULAs is
> not really global, but scopee(link-local) < scope(ULAs) < scope(global)
>
>
> While this document does propose a way out (it assumes #3 above, and
> acts accordingly), I believe the first step is to agree on what "global
> scope" means and, subsequently, whether ULAs are really "global scope"
> or not. Since opinions on the topic have vary a lot (as noted above),
> I've posted this I-D and I'm sending this note for further input from
> the WG.
>
> Thanks!
>
> Regards,
> Fernando
>
>
>
>
> -------- Forwarded Message --------
> Subject: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.t=
xt
> Date: Tue, 05 Jan 2021 17:02:20 -0800
> From: internet-drafts@ietf.org
> To: Fernando Gont <fgont@si6networks.com>
>
>
> A new version of I-D, draft-gont-6man-ipv6-ula-scope-00.txt
> has been successfully submitted by Fernando Gont and posted to the
> IETF repository.
>
> Name:           draft-gont-6man-ipv6-ula-scope
> Revision:       00
> Title:          Scope of Unique Local IPv6 Unicast Addresses
> Document date:  2021-01-05
> Group:          Individual Submission
> Pages:          8
> URL:
> https://www.ietf.org/archive/id/draft-gont-6man-ipv6-ula-scope-00.txt
> Status:
> https://datatracker.ietf.org/doc/draft-gont-6man-ipv6-ula-scope/
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-gont-6man-ipv6-ula-scope
> Htmlized:
> https://tools.ietf.org/html/draft-gont-6man-ipv6-ula-scope-00
>
>
> Abstract:
>     Unique Local IPv6 Unicast Addresses (ULAs) are formally part of the
>     IPv6 Global Unicast address space.  However, the semantics of ULAs
>     clearly contradict the definition of "global scope".  This document
>     discusses the why the terminology employed for the specification of
>     ULAs is problematic, along with some practical consequences of the
>     current specification of ULAs.  Finally, it formally updates RFC4291
>     and RFC4193 such that the scope of ULAs is defined as "local".
>
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>


--=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

--000000000000d27cd705b833e449
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">I think this is the right direction the p=
revious draft indirectly defined a new scope &quot;non-global&quot;, I much=
 prefer explicitly=C2=A0defining a new local scope.<div><br></div><div>I wo=
uld add something like the following to better define the relationship betw=
een the three scopes;</div><div><br></div><blockquote style=3D"margin:0 0 0=
 40px;border:none;padding:0px"><div>The boundary of the link-local scope is=
 strongly defined, limiting the extent of the link-local scope to an indivi=
dual link. However, in contrast, the boundary of the local scope is weakly =
defined, it is amorphous and imprecise. In some instances, the extent of th=
e local scope can be a single site, in other instances, a group of unrelate=
d sites, a single organization, or even a cooperating group of organization=
s. Furthermore, the extent of an individual instance of the local scope doe=
sn&#39;t necessarily remain constant, it may expand or contract over time a=
s the local situation dictates, for example when two organizations merge. N=
evertheless, the extent of the local scope doesn=E2=80=99t encompass the en=
tirety of the Internet which the global scope does.</div></blockquote></div=
><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tu=
e, Jan 5, 2021 at 7:21 PM Fernando Gont &lt;<a href=3D"mailto:fgont@si6netw=
orks.com" target=3D"_blank">fgont@si6networks.com</a>&gt; wrote:<br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft:1px solid rgb(204,204,204);padding-left:1ex">Folks,<br>
<br>
Based on the recent discussion on the v6ops list <br>
(<a href=3D"https://mailarchive.ietf.org/arch/msg/v6ops/b7r35HgOb-6dfxsDoW8=
c4FtGnZo//" rel=3D"noreferrer" target=3D"_blank">https://mailarchive.ietf.o=
rg/arch/msg/v6ops/b7r35HgOb-6dfxsDoW8c4FtGnZo//</a>), <br>
I&#39;ve posted this new I-D, meant to discuss the scope of ULAs:<br>
<br>
Title: &quot;Scope of Unique Local IPv6 Unicast Addresses&quot;<br>
I-D: <a href=3D"https://tools.ietf.org/id/draft-gont-6man-ipv6-ula-scope-00=
.txt" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/id/draft-=
gont-6man-ipv6-ula-scope-00.txt</a><br>
<br>
<br>
Short version of the story:<br>
<br>
ULAs are formally part of the GUA space. However, the characteristics of <b=
r>
ULAs do not seem to match the definition of global scope from RFC4007 <br>
(IPv6 Scope Addr Architecture). ULA seem to have a scope of <br>
scope(link-local) &lt; scope(ULA) &lt; scope(GUA).<br>
<br>
This is not only a terminology thing (which I think is nevertheless <br>
important to get right) but also has practical implications. For <br>
example, there&#39;s a python library that considers ULAs as &quot;not glob=
al&quot;, <br>
and &quot;private&quot; -- contradicting the current RFC4291/RFC4193 specs.=
<br>
<br>
Prior to posting this document, we had some on-list discussion (on the <br>
v6ops list) and also some off-list discussion with some of you (bcc&#39;ed)=
.<br>
<br>
The opinions have been in one of these camps:<br>
<br>
1) the current specs are coherent and there&#39;s no problem<br>
<br>
2) There&#39;s a problem with the definition of &quot;global scope&quot; --=
 so ULAs <br>
*are* global scope, but global scope does not really stand for the <br>
definition in RFC4007.<br>
<br>
3) The definitions in RFC4007 are correct, and thus the scope of ULAs is <b=
r>
not really global, but scopee(link-local) &lt; scope(ULAs) &lt; scope(globa=
l)<br>
<br>
<br>
While this document does propose a way out (it assumes #3 above, and <br>
acts accordingly), I believe the first step is to agree on what &quot;globa=
l <br>
scope&quot; means and, subsequently, whether ULAs are really &quot;global s=
cope&quot; <br>
or not. Since opinions on the topic have vary a lot (as noted above), <br>
I&#39;ve posted this I-D and I&#39;m sending this note for further input fr=
om <br>
the WG.<br>
<br>
Thanks!<br>
<br>
Regards,<br>
Fernando<br>
<br>
<br>
<br>
<br>
-------- Forwarded Message --------<br>
Subject: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt=
<br>
Date: Tue, 05 Jan 2021 17:02:20 -0800<br>
From: <a href=3D"mailto:internet-drafts@ietf.org" target=3D"_blank">interne=
t-drafts@ietf.org</a><br>
To: Fernando Gont &lt;<a href=3D"mailto:fgont@si6networks.com" target=3D"_b=
lank">fgont@si6networks.com</a>&gt;<br>
<br>
<br>
A new version of I-D, draft-gont-6man-ipv6-ula-scope-00.txt<br>
has been successfully submitted by Fernando Gont and posted to the<br>
IETF repository.<br>
<br>
Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-gont-6man-ipv6-ula-scop=
e<br>
Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A000<br>
Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Scope of Unique Local IPv6 Unicast=
 Addresses<br>
Document date:=C2=A0 2021-01-05<br>
Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Individual Submission<br>
Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 8<br>
URL: <br>
<a href=3D"https://www.ietf.org/archive/id/draft-gont-6man-ipv6-ula-scope-0=
0.txt" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/archive/id=
/draft-gont-6man-ipv6-ula-scope-00.txt</a><br>
Status: <br>
<a href=3D"https://datatracker.ietf.org/doc/draft-gont-6man-ipv6-ula-scope/=
" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/dra=
ft-gont-6man-ipv6-ula-scope/</a><br>
Htmlized: <br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-gont-6man-ipv6-ula-s=
cope" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc=
/html/draft-gont-6man-ipv6-ula-scope</a><br>
Htmlized: <br>
<a href=3D"https://tools.ietf.org/html/draft-gont-6man-ipv6-ula-scope-00" r=
el=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft-gont-=
6man-ipv6-ula-scope-00</a><br>
<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0 Unique Local IPv6 Unicast Addresses (ULAs) are formally part =
of the<br>
=C2=A0 =C2=A0 IPv6 Global Unicast address space.=C2=A0 However, the semanti=
cs of ULAs<br>
=C2=A0 =C2=A0 clearly contradict the definition of &quot;global scope&quot;=
.=C2=A0 This document<br>
=C2=A0 =C2=A0 discusses the why the terminology employed for the specificat=
ion of<br>
=C2=A0 =C2=A0 ULAs is problematic, along with some practical consequences o=
f the<br>
=C2=A0 =C2=A0 current specification of ULAs.=C2=A0 Finally, it formally upd=
ates RFC4291<br>
=C2=A0 =C2=A0 and RFC4193 such that the scope of ULAs is defined as &quot;l=
ocal&quot;.<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
The IETF Secretariat<br>
<br>
<br>
<br>
_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6ops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>Da=
vid Farmer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 <a href=3D=
"mailto:Email%3Afarmer@umn.edu" target=3D"_blank">Email:farmer@umn.edu</a><=
br>Networking &amp; Telecommunication Services<br>Office of Information Tec=
hnology<br>University of Minnesota=C2=A0=C2=A0 <br>2218 University Ave SE=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Phone: 612-626-0815<br>Minneapolis, MN 55414-30=
29=C2=A0=C2=A0 Cell: 612-812-9952<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D </div>
</div>

--000000000000d27cd705b833e449--


From nobody Tue Jan  5 20:45:44 2021
Return-Path: <albert.e.manfredi@boeing.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 6EE5F3A0F47; Tue,  5 Jan 2021 20:45:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.419
X-Spam-Level: 
X-Spam-Status: No, score=-4.419 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=boeing.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 hK-NP-oEXSoQ; Tue,  5 Jan 2021 20:45:37 -0800 (PST)
Received: from clt-mbsout-02.mbs.boeing.net (clt-mbsout-02.mbs.boeing.net [130.76.144.163]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A12A3A0F46; Tue,  5 Jan 2021 20:45:36 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 1064jYYw006946; Tue, 5 Jan 2021 23:45:34 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1609908334; bh=Fa5HEr0ZJEwwtxRZXw3KErn8oaGeCdTLvf1KxX6DwJc=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=PjEj8Of0qd9fV+hP1A/p9YcVmvdwkShSfW14NT9InaHrhAIB+HBOWtMPTudcYl4HL lFhmm2nGuviXOnLN8RvEM1QPzhgxIm66S/A1GH5muFM13V+uSkgWza9bLpPeI4/GUs lyuwtkwPkLFAAAmDfemj1su0cCHXppnaFFmLtl84PDg834Z3wFSHGOk9XmbMqY0fom ccL20KusX26qAxB5a9BGjvP3HDsNTRq+t9mJMOX8SHFCEaqYPGpFn3EgT9VSPl4QIq /KWZoB5dy7OVG/jhCDCD7jtVokEtDvGlTTn+DHleaXQkY1aJ9254lX46OXzLtnVqCR fLHAWqp5PPAJQ==
Received: from XCH16-01-07.nos.boeing.com (xch16-01-07.nos.boeing.com [144.115.65.217]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 1064jN73006891 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Tue, 5 Jan 2021 23:45:23 -0500
Received: from XCH16-01-11.nos.boeing.com (144.115.66.39) by XCH16-01-07.nos.boeing.com (144.115.65.217) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2044.4; Tue, 5 Jan 2021 20:45:21 -0800
Received: from XCH16-01-11.nos.boeing.com ([fe80::c57c:39bc:4c0a:384b]) by XCH16-01-11.nos.boeing.com ([fe80::c57c:39bc:4c0a:384b%4]) with mapi id 15.01.2044.004; Tue, 5 Jan 2021 20:45:21 -0800
From: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>
To: Fernando Gont <fgont@si6networks.com>
CC: IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
Thread-Topic: [EXTERNAL]  Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
Thread-Index: AQHW48/q6MYge4t1TkCUP2ZIbkIFhaoaakmA//+V2PA=
Date: Wed, 6 Jan 2021 04:45:21 +0000
Message-ID: <91dd34c29aa64a5d80f64bd0a4370dcc@boeing.com>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <2e80ec51-ec66-16c7-7c9e-a6e8d632c5de@si6networks.com>
In-Reply-To: <2e80ec51-ec66-16c7-7c9e-a6e8d632c5de@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [144.115.204.6]
x-tm-snts-smtp: 6474391E86DD1113A4A3D58B79511EA11C1EF70C24971B184B223E004BA848792000:8
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/9Yt-CFauOB3HVT-81Z0J-YYukd8>
Subject: Re: [v6ops] [EXTERNAL] Re: Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 04:45:39 -0000

-----Original Message-----
From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Fernando Gont

> The math in RFC4193 for "uniqueness" considers *only a reduced number of=
=20
uLA-based networks being inter-connected*. So, when computing global=20
uniqueness, you should consider *all ULA prefixes in use*, not just=20
those of networks you are interconnecting. And when you do that, you get=20
a very high probability of collisions (~1).

This is getting unnecessarily complicated, IMO. ULAs are more than just lin=
k-local, because an administrative domain, such as even an enterprise net, =
can use them, throughout that network. Within such a domain, the top /48 ca=
n be guaranteed to be unique, because the same admin computes those 40 rand=
om Global ID bits. Not so? Such as, use the same PRNG, document the seed, t=
hen pick your five random bytes to use for each site, from the long random =
sequence.

Now you can organize that enterprise net into separate /48 networks, or for=
 that matter, even link various geo-separated sites, through tunnels, where=
 each site gets one or more of those random /48 prefixes. The important poi=
nt being, only route inside that enterprise, and use a consistent method to=
 compute the Global ID bits.

I just object to equating this with link-local. It's way more than that.

Bert


From nobody Tue Jan  5 21:10:46 2021
Return-Path: <fgont@si6networks.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 15D7C3A1034; Tue,  5 Jan 2021 21:10:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.161
X-Spam-Level: 
X-Spam-Status: No, score=-2.161 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, 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 hXJN1GtZtBQD; Tue,  5 Jan 2021 21:10:41 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2850F3A102D; Tue,  5 Jan 2021 21:10:39 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id D70CD28462F; Wed,  6 Jan 2021 05:10:33 +0000 (UTC)
To: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>
Cc: IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <2e80ec51-ec66-16c7-7c9e-a6e8d632c5de@si6networks.com> <91dd34c29aa64a5d80f64bd0a4370dcc@boeing.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <02c4c5bd-5a49-81f3-4379-c71dbb252112@si6networks.com>
Date: Wed, 6 Jan 2021 02:10:13 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <91dd34c29aa64a5d80f64bd0a4370dcc@boeing.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/up5vjRrcKyd3raPwvXJyXesHh48>
Subject: Re: [v6ops] [EXTERNAL] Re: Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 05:10:45 -0000

Hello, Bert,

On 6/1/21 01:45, Manfredi (US), Albert E wrote:
> -----Original Message----- From: ipv6 <ipv6-bounces@ietf.org> On
> Behalf Of Fernando Gont
> 
>> The math in RFC4193 for "uniqueness" considers *only a reduced
>> number of
> uLA-based networks being inter-connected*. So, when computing global 
> uniqueness, you should consider *all ULA prefixes in use*, not just 
> those of networks you are interconnecting. And when you do that, you
> get a very high probability of collisions (~1).
> 
> This is getting unnecessarily complicated, IMO. ULAs are more than
> just link-local, 

Indeed, my draft argues that the scope of ULAs is larger than that of 
link-locals. They key point is that it also argues that scope(ULAs) < 
scope(GUAs).



> because an administrative domain, such as even an
> enterprise net, can use them, throughout that network. Within such a
> domain, the top /48 can be guaranteed to be unique,

How could you possibly guaranteed that if you're selecting the ULA 
prefix with a PRNG? Probabilities don't buy you any guarantees, except 
if P=1 or P=0, which is clearly not the case here.

Additionally, there's a difference between "the ULA prefix is 
probabilistically unique if you connect a limited number of networks" -- 
which is the math in Section 3.2.3 of RFC4193 -- versus being globally 
unique, which implies that the ULA prefix is unique among or ULA-based 
networks, whether you interconnected them or not.



> because the same
> admin computes those 40 random Global ID bits. Not so? Such as, use
> the same PRNG, document the seed, then pick your five random bytes to
> use for each site, from the long random sequence.

RFC4193 does not mandate a specific algorithm, but rather specified the 
requirements for the PRNG (good for the RFC4193 authors!). So, 
documenting the seed will serve no purpose, because other 
implementations might use a completely different algorithm for 
generating the ULA prefix.



> Now you can organize that enterprise net into separate /48 networks,
> or for that matter, even link various geo-separated sites, through
> tunnels, where each site gets one or more of those random /48
> prefixes. The important point being, only route inside that
> enterprise, 

This one seems, already, an indication of prefixes being non-global.



> and use a consistent method to compute the Global ID bits.

An this one is obviously non-enforceable, for multiple reasons, 
including the fact that RFC4193 doesn't mandate any specific algorithm.



> I just object to equating this with link-local. It's way more than
> that.

I don't think anybody has equated ULAs with link-locals. The argument 
has been, instead, that: scope(link-local) < scope(ULA) < scope(GUA)

In a way, the expectation of ULAs to be global-scope is probably what 
drove the recent discussion on the 6man list about a ULA registry -- 
which yes, is probably the only way in which ULAs could actually be GUAs 
(except that unless you can enforce the use of such registry, having a 
non-enforceable partial registry won't make the ULA prefixes global scope).

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Tue Jan  5 21:28:57 2021
Return-Path: <fgont@si6networks.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 EBFDF3A1071; Tue,  5 Jan 2021 21:28:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.161
X-Spam-Level: 
X-Spam-Status: No, score=-2.161 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, 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 RKvpnrfTuANd; Tue,  5 Jan 2021 21:28:48 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8A423A1070; Tue,  5 Jan 2021 21:28:48 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id DD53E284635; Wed,  6 Jan 2021 05:28:44 +0000 (UTC)
To: David Farmer <farmer@umn.edu>
Cc: "6man@ietf.org" <6man@ietf.org>, IPv6 Operations <v6ops@ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAN-Dau344H7xgD0Q_O54c=R08zFRFjToO8BHt=ssauxgEH7ynA@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <df1d4c9d-cc02-7eaa-9d40-f1fc45aa8f9c@si6networks.com>
Date: Wed, 6 Jan 2021 02:28:36 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CAN-Dau344H7xgD0Q_O54c=R08zFRFjToO8BHt=ssauxgEH7ynA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/s7nQN_rcRUWE3BsY6ab8GN6VXDA>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 05:28:52 -0000

Hello, David,

Thanks a lot for your feedback! In-line....

On 6/1/21 01:38, David Farmer wrote:
> I think this is the right direction the previous draft indirectly 
> defined a new scope "non-global", I much prefer explicitly defining a 
> new local scope.

Good point.



> I would add something like the following to better define the 
> relationship between the three scopes;
> 
>     The boundary of the link-local scope is strongly defined, limiting
>     the extent of the link-local scope to an individual link. However,
>     in contrast, the boundary of the local scope is weakly defined, it
>     is amorphous and imprecise. In some instances, the extent of the
>     local scope can be a single site, in other instances, a group of
>     unrelated sites, a single organization, or even a cooperating group
>     of organizations. Furthermore, the extent of an individual instance
>     of the local scope doesn't necessarily remain constant, it may
>     expand or contract over time as the local situation dictates, for
>     example when two organizations merge. 

Following the terminology in RFC4007, I wonder if this last bit should 
be expressed as:
"the extent of an individual instantiation of a local scope (i.e., a 
zone), does not necessarily remain constant..."?


>     Nevertheless, the extent of
>     the local scope doesn’t encompass the entirety of the Internet which
>     the global scope does.

A remaining item to figure out here is:

According to RFC4007, you can't have to instantiations of the same 
scope. One way to analyze this is

1) that this doesn't apply to ULAs, or,

2) That it's impossible to tell the specific extent of a local scope. As 
a result, all instantiations of local scopes are considered to be 
different zones, and hence you are free to have as many instantiations 
of "local scope" as you wish.

(RFC4007 defines "zone" to be an instantiation of "scope").

Thoughts?

Thanks!

Regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Tue Jan  5 21:54:03 2021
Return-Path: <albert.e.manfredi@boeing.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 51E2B3A10B0; Tue,  5 Jan 2021 21:54:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 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, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=boeing.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 xtis1i2_kBJR; Tue,  5 Jan 2021 21:53:59 -0800 (PST)
Received: from clt-mbsout-02.mbs.boeing.net (clt-mbsout-02.mbs.boeing.net [130.76.144.163]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 502093A10A9; Tue,  5 Jan 2021 21:53:58 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 1065rsuf011035; Wed, 6 Jan 2021 00:53:55 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1609912435; bh=hVTCdQ8W6Bi5oftCoJck+M9/zAiFptEjpuL3xw6rPac=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=AQiFXsMMc2Tvj6XMBaMjAIsBPB8SJ2YRGZuIKlynE2fa+27kfhbqXDB/566yBN7/l cz2tFfiLJ08OLyS75UA6PGE/yYCRAie+lKTGp/rZCUlKqdhsChx3qp7mJEWG+bq2MF F51JToVu/fV4SlqwUT0UtfnalUExHI7iulQsZMVPhR3B9szZZQs1fxh1uaChA34Pwn 9jQ0Z2eJUn6yqSFIqqGUb/Y9qcAQN9Rff9gpkZo9oAyjnyXLEbt1rqFFOj+wDYhpqM RUFN3jiEiRwrCoyzW1ud4JmtKOungCXMZp7PhvEcf/UQ7iFeKkZanMC6F4xdw0AZ1y WO0FMk9gul7uQ==
Received: from XCH16-01-09.nos.boeing.com (xch16-01-09.nos.boeing.com [144.115.65.234]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 1065rkWp010903 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Wed, 6 Jan 2021 00:53:47 -0500
Received: from XCH16-01-11.nos.boeing.com (144.115.66.39) by XCH16-01-09.nos.boeing.com (144.115.65.234) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2044.4; Tue, 5 Jan 2021 21:53:45 -0800
Received: from XCH16-01-11.nos.boeing.com ([fe80::c57c:39bc:4c0a:384b]) by XCH16-01-11.nos.boeing.com ([fe80::c57c:39bc:4c0a:384b%4]) with mapi id 15.01.2044.004; Tue, 5 Jan 2021 21:53:45 -0800
From: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>
To: Fernando Gont <fgont@si6networks.com>
CC: IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
Thread-Topic: [EXTERNAL] Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
Thread-Index: AQHW4+pOG7wrQgzUhUyECNniNFZ8MKoaEugA
Date: Wed, 6 Jan 2021 05:53:45 +0000
Message-ID: <da9fabb091294fc6bf55184f1cce5d61@boeing.com>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <2e80ec51-ec66-16c7-7c9e-a6e8d632c5de@si6networks.com> <91dd34c29aa64a5d80f64bd0a4370dcc@boeing.com> <02c4c5bd-5a49-81f3-4379-c71dbb252112@si6networks.com>
In-Reply-To: <02c4c5bd-5a49-81f3-4379-c71dbb252112@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [144.115.204.6]
x-tm-snts-smtp: ACB09E3227197A01887590E975206EC663A8A91DCF7408D9619DBC18429613CB2000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/GYPNOs0h1QaZvrqJJrQBu1unFOs>
Subject: Re: [v6ops] [EXTERNAL] Re: Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 05:54:01 -0000

SGkgRmVybmFuZG8sIGxldCdzIGZvbGxvdyB0aGUgS0lTUyBwcmluY2lwbGUuDQoNCi0tLS0tT3Jp
Z2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBGZXJuYW5kbyBHb250IDxmZ29udEBzaTZuZXR3b3Jr
cy5jb20+IA0KDQo+IFJGQzQxOTMgZG9lcyBub3QgbWFuZGF0ZSBhIHNwZWNpZmljIGFsZ29yaXRo
bSwgYnV0IHJhdGhlciBzcGVjaWZpZWQgdGhlIA0KcmVxdWlyZW1lbnRzIGZvciB0aGUgUFJORyAo
Z29vZCBmb3IgdGhlIFJGQzQxOTMgYXV0aG9ycyEpLiBTbywgDQpkb2N1bWVudGluZyB0aGUgc2Vl
ZCB3aWxsIHNlcnZlIG5vIHB1cnBvc2UsIGJlY2F1c2Ugb3RoZXIgDQppbXBsZW1lbnRhdGlvbnMg
bWlnaHQgdXNlIGEgY29tcGxldGVseSBkaWZmZXJlbnQgYWxnb3JpdGhtIGZvciANCmdlbmVyYXRp
bmcgdGhlIFVMQSBwcmVmaXguDQoNCldpdGhpbiBhbiBlbnRlcnByaXNlLCB0aGUgYWRtaW4gaGFz
IGEgY2hvaWNlIG9mIHdoaWNoIFBSTkcgdG8gdXNlLCBhbmQgd2hhdCBzZWVkIHRvIHVzZS4gVGhp
bmsgaW4gdGVybXMgb2Ygb25lIGd1eSwgbWFraW5nIHRoYXQgZGVjaXNpb24sIGFuZCB0aGVuIGRv
Y3VtZW50aW5nIGFsbCB0aGUgR2xvYmFsIElEIDQwLWJpdCBzZXF1ZW5jZXMgaW4gdXNlLCBpbiB0
aGUgdmFyaW91cyBuZXRzIG9mIHRoZSBlbnRlcnByaXNlLiBUaGUgZ3V5IHdpdGggdGhpcyByZXNw
b25zaWJpbGl0eSBjYW4gY2VydGFpbmx5IGRlY2lkZSBvbiB3aGljaCBhbGdvcml0aG0gdG8gdXNl
IQ0KDQpJdCBpcyBlYXN5IGVub3VnaCB0byBndWFyYW50ZWUgdW5pcXVlbmVzcywgaW4gdGhpcyBj
YXNlLg0KDQo+IEFuIHRoaXMgb25lIGlzIG9idmlvdXNseSBub24tZW5mb3JjZWFibGUsIGZvciBt
dWx0aXBsZSByZWFzb25zLCANCmluY2x1ZGluZyB0aGUgZmFjdCB0aGF0IFJGQzQxOTMgZG9lc24n
dCBtYW5kYXRlIGFueSBzcGVjaWZpYyBhbGdvcml0aG0uDQoNCkkgYW0gdGhlIGVudGVycHJpc2Ug
YWRtaW4sIEknbSB0YXNrZWQgd2l0aCBhZG1pbmlzdGVyaW5nIHRoZSBVTEFzIGZvciB0aGUgZW50
ZXJwcmlzZSwgYW5kIEkgZW5mb3JjZSB0aGUgcnVsZS4gVGhlIGFkbWluIG9mIG9uZSBlbnRlcnBy
aXNlIG5ldHdvcmsgaGFzIG5vIHNheSBpbiB3aGF0IG90aGVyIGFkbWlucywgb2Ygb3RoZXIgZW50
ZXJwcmlzZSBuZXR3b3Jrcywgd2FudCB0byBkby4gTm9yIGlzIHRoZXJlIGFueSByZXF1aXJlbWVu
dCBmb3IgVUxBcyBvZiBkaWZmZXJlbnQgZW50ZXJwcmlzZSBuZXRzIHRvIGJlIG11dHVhbGx5IHVu
aXF1ZS4NCg0KPiBJIGRvbid0IHRoaW5rIGFueWJvZHkgaGFzIGVxdWF0ZWQgVUxBcyB3aXRoIGxp
bmstbG9jYWxzLiBUaGUgYXJndW1lbnQgDQpoYXMgYmVlbiwgaW5zdGVhZCwgdGhhdDogc2NvcGUo
bGluay1sb2NhbCkgPCBzY29wZShVTEEpIDwgc2NvcGUoR1VBKQ0KDQpTb21ldGhpbmcgbGlrZSAi
c2luZ2xlIGFkbWluaXN0cmF0aXZlIGRvbWFpbiBzY29wZSwiIGlmIHRoYXQgZXhpc3RlZCwgbWFr
ZXMgc2Vuc2UgdG8gbWUuIEkgdGhpbmsgdGhlIHByb2JsZW0gaXMgdGhhdCB0b2RheSwgaXQncyBl
aXRoZXIgbGluayBsb2NhbCBvciBnbG9iYWwgc2NvcGU/DQoNCj4gSW4gYSB3YXksIHRoZSBleHBl
Y3RhdGlvbiBvZiBVTEFzIHRvIGJlIGdsb2JhbC1zY29wZSBpcyBwcm9iYWJseSB3aGF0IA0KZHJv
dmUgdGhlIHJlY2VudCBkaXNjdXNzaW9uIG9uIHRoZSA2bWFuIGxpc3QgYWJvdXQgYSBVTEEgcmVn
aXN0cnkgLS0NCg0KVG8gbWUsIHRoYXQncyBhIGRpZmZlcmVudCBkaXNjdXNzaW9uLiBUaGF0IHJl
Z2lzdHJ5IGlkZWEgd291bGQgcHJvYmFibHkgYmUgYSBuZWNlc3NpdHksIGJ1dCBvbmx5IGZvciB0
aGUgZmMwMDo6LzggVUxBcywgd2hpY2ggYXJlIGZvciBmdXR1cmUgdXNlLiBXaGVuIFVMQXMgYXJl
IG5vdCBhc3NpZ25lZCBieSBhbiBpbmRpdmlkdWFsIGFkbWluLCB0aGUgcHJvYmxlbSBvZiB1bmlx
dWVuZXNzIGlzIGRpZmZlcmVudCwgbm8/IFRvIG1lLCB0aGF0IHJlZ2lzdHJ5IHByb2JsZW0gaXMg
YSBub24taXNzdWUsIHVubGVzcyBhbmQgdW50aWwgd2Ugc3RhcnQgdXNpbmcgdGhlIGZjMDA6Oi84
IGFkZHJlc3Nlcy4gQXMgb2Ygbm93LCBvbmx5IGZkMDA6Oi84IGFyZSBiZWluZyBkaXNjdXNzZWQu
DQoNCkJlcnQNCg0K


From nobody Tue Jan  5 22:32:56 2021
Return-Path: <fgont@si6networks.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 351403A106F; Tue,  5 Jan 2021 22:32:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level: 
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, 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 wpPOcDwNfiZm; Tue,  5 Jan 2021 22:32:50 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A37C3A103F; Tue,  5 Jan 2021 22:32:49 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id EE92E283BB4; Wed,  6 Jan 2021 06:32:44 +0000 (UTC)
To: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>
Cc: IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <2e80ec51-ec66-16c7-7c9e-a6e8d632c5de@si6networks.com> <91dd34c29aa64a5d80f64bd0a4370dcc@boeing.com> <02c4c5bd-5a49-81f3-4379-c71dbb252112@si6networks.com> <da9fabb091294fc6bf55184f1cce5d61@boeing.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <31ab1e02-ea3c-08db-20be-83576afa5b7a@si6networks.com>
Date: Wed, 6 Jan 2021 03:32:32 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <da9fabb091294fc6bf55184f1cce5d61@boeing.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/0Zh2tcoNrkdoW6_WSIKYpYkyfHk>
Subject: Re: [v6ops] [EXTERNAL] Re: Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 06:32:54 -0000

Hi, Bert,

On 6/1/21 02:53, Manfredi (US), Albert E wrote:
> Hi Fernando, let's follow the KISS principle.

KISS *and* real, please ;-)



> -----Original Message----- From: Fernando Gont
> <fgont@si6networks.com>
> 
>> RFC4193 does not mandate a specific algorithm, but rather specified
>> the
> requirements for the PRNG (good for the RFC4193 authors!). So, 
> documenting the seed will serve no purpose, because other 
> implementations might use a completely different algorithm for 
> generating the ULA prefix.
> 
> Within an enterprise, the admin has a choice of which PRNG to use,
> and what seed to use. Think in terms of one guy, making that
> decision, and then documenting all the Global ID 40-bit sequences in
> use, in the various nets of the enterprise. The guy with this
> responsibility can certainly decide on which algorithm to use!
> 
> It is easy enough to guarantee uniqueness, in this case.

Please do the math.

Being able to connect a few networks together does not mean the addreses
are unique. You can't normally connect  several 10.0.0.0/8 nets, too.

Global-scope, as per RFC4007 would imply that *the ULA prefixes are
globally unique*. *All, at the same time*.




>> An this one is obviously non-enforceable, for multiple reasons,
> including the fact that RFC4193 doesn't mandate any specific
> algorithm.
> 
> I am the enterprise admin, I'm tasked with administering the ULAs for
> the enterprise, and I enforce the rule. The admin of one enterprise
> network has no say in what other admins, of other enterprise
> networks, want to do. Nor is there any requirement for ULAs of
> different enterprise nets to be mutually unique.

Indeed, "global scope" would imply exactly that. Please check my I-D, 
which quotes the relevant text from RFC4193.



>> I don't think anybody has equated ULAs with link-locals. The
>> argument
> has been, instead, that: scope(link-local) < scope(ULA) < scope(GUA)
> 
> Something like "single administrative domain scope," if that existed,
> makes sense to me. I think the problem is that today, it's either
> link local or global scope?

Exactly!  ULAs are not link-local, but not "global", either. They have a 
scope that lies somewhere in between link-local and global.

In my I-D, I called the ULA scope "local", but I don't mind changing 
that to "single administrative domain scope", "private scope", or 
anything else.

The point is, indeed, that ULAs are currently defined as global. BUt 
they are not -- their scope is certainly smaller than global.




>> In a way, the expectation of ULAs to be global-scope is probably
>> what
> drove the recent discussion on the 6man list about a ULA registry --
> 
> To me, that's a different discussion. That registry idea would
> probably be a necessity, but only for the fc00::/8 ULAs, which are
> for future use. When ULAs are not assigned by an individual admin,
> the problem of uniqueness is different, no? 

Indeed. When they are not centrally assigned, or not assigned by the 
same admin, you cannot expect them to be unique across different 
administrative domains. You can expect the probability of collisions 
*when interconnecting a reduced number of ULA-based networks* to be 
small.  But you can certainly not expect the ULA prefixes to be unique 
at a global scale. when you consider ~1M networks (not a big deal if you 
e.g. expect that each home will generate a ULA prefix) you actually have 
almost certainty that there's a collision.



> To me, that registry
> problem is a non-issue, unless and until we start using the fc00::/8
> addresses. As of now, only fd00::/8 are being discussed.

To me, it's also a non issue. But it looks like the proposal for a 
registry has been motivated by the expectation of ULAs being *globally 
unique* (as opposed to "unlikely to collide if you interconnect a 
handful of ULA-based networks").

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Tue Jan  5 23:08:05 2021
Return-Path: <lorenzo@google.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 6D4593A11A9 for <v6ops@ietfa.amsl.com>; Tue,  5 Jan 2021 23:08:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.971
X-Spam-Level: 
X-Spam-Status: No, score=-17.971 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.373, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 uLmdHBzBgMnA for <v6ops@ietfa.amsl.com>; Tue,  5 Jan 2021 23:08:03 -0800 (PST)
Received: from mail-il1-x12e.google.com (mail-il1-x12e.google.com [IPv6:2607:f8b0:4864:20::12e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1752F3A11A8 for <v6ops@ietf.org>; Tue,  5 Jan 2021 23:08:03 -0800 (PST)
Received: by mail-il1-x12e.google.com with SMTP id 2so2240023ilg.9 for <v6ops@ietf.org>; Tue, 05 Jan 2021 23:08:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rVuMKwVhqknYlyoyBH1sSDT7zjC+qLgw3QlWEuB09Jg=; b=Izyh5WctGCr1TgY/OsGfiBiGYBJMFAMgz9P54e8BkUIF6koXWuDe090zukLxWsOglW TnlOJdqO6U6z/j6aQfelA5ArpVifUQOkwFmvZ+KBSc3XxS0i/2gdXMt73NgkFTYSWs5k qvwPyN/tNPeyQTKG0oxOPJhFCX2teyjpoYhoj42gkEZVvfqbBwS8QH5ihLfGSsCzzAPd sw/GibJ6B9+s13Z+LnFnXYU21NIT/eZ42VXCt+DoxPpUmTN2edgic4vka+TRkTA3iXbm uhP6UlqQaqrG7SJNXomdGplT9CWvb8XXaG6jtmlQKMrudUUMfgzL361FqP+SMbIOszqM 7vJA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rVuMKwVhqknYlyoyBH1sSDT7zjC+qLgw3QlWEuB09Jg=; b=th7OenIa8C+DdoFjHepeREISsDOMA3FQaS2UMnVYGB+1sshYEMC/PYXnW3X1SxLmja /Fojpij3nPPjjMXfYS8fVqWfZwcchqgsYn6d0CaE4Qni2FYbWpBPnh7kCTv704wfcdro altJ/3k+2TcaXw0LEiKhBvvQIf2NHS5oU0aBbCNsbwaAQLCwNUgzS8duj4CpuGiz5ESX +vpOQ9ApwXw/VqTDM6ms02YMzpuIfX6+LgpCFbyujTwQrCe8o//+05G+y0JYtX8Ydra+ NYQlqiwo0GBTiWySrAu2cEcrr3v4zsSnyGINo7MfKUS8gqESkGnYWvi5vE5u161JXGLR vcyQ==
X-Gm-Message-State: AOAM530HZ5n9MN2aStqL4Le7n+uv6MfFYZDt2LOvsaHVawBwNnscv1MQ WdU0Xwranh10ngomh5Qon/kI4Al/+1H0EooHp5UztA==
X-Google-Smtp-Source: ABdhPJzjvyQrMUrRQ17bv+gnWQ5o9NZiAPCSyewUuXIlQL/eqx9H7bajk7AswrT+9p7Uuvw8KxOJGGtcI2WqE7DKVXw=
X-Received: by 2002:a05:6e02:85:: with SMTP id l5mr3004120ilm.187.1609916882175;  Tue, 05 Jan 2021 23:08:02 -0800 (PST)
MIME-Version: 1.0
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com>
In-Reply-To: <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 6 Jan 2021 16:07:51 +0900
Message-ID: <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com>
To: Mark Smith <markzzzsmith@gmail.com>
Cc: Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e1b9f005b835fbc9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/VKNbBpNHUX7lnsyg4qJ12JuRZ0k>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 07:08:04 -0000

--000000000000e1b9f005b835fbc9
Content-Type: text/plain; charset="UTF-8"

On Wed, Jan 6, 2021 at 11:01 AM Mark Smith <markzzzsmith@gmail.com> wrote:

> ULAs are intended to be globally unique addresses, but not to be globally
> (Internet) forwardable. Their forwarding scope is limited to non-global,
> either within a single local network, or between a set of local networks
> that have agreed to forward their respective ULA /48 prefixes between each
> other, overriding the default of local networks only forwarding scope.
> (Ethernet addresses are a similar example, globally unique addresses, link
> only forwarding scope.)
>

IMO defining ULAs as they are was a mistake. Global scope implies unique.
But probabilistic uniqueness doesn't work because humans choose ULAs
instead of generating them manually. Registry-based uniqueness doesn't work
(and, to be fair, was never tried by the IETF) because there is no registry
that has jurisdiction. Even if there were, there is no reason to keep
addresses unique if they don't have global reachability.

So I guess I'm somewhere between 1) and 3). The specs are consistent but
they fail to consider human behaviour, so they don't actually work in
practice. I don't know what to do about this though. If we say they're
non-global scope, then they are going to be the exact equivalent of RFC1918
addresses, with all the problems that that causes. If we continue to say
they're global scope, then the specs don't match reality. :-(

--000000000000e1b9f005b835fbc9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Wed, Jan 6, 2021 at 11:01 AM Mark Smit=
h &lt;<a href=3D"mailto:markzzzsmith@gmail.com">markzzzsmith@gmail.com</a>&=
gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"auto"><div>ULAs are inte=
nded to be globally unique addresses, but not to be globally (Internet) for=
wardable. Their forwarding scope is limited to non-global, either within a =
single local network, or between a set of local networks that have agreed t=
o forward their respective ULA /48 prefixes between each other, overriding =
the default of local networks only forwarding scope. (Ethernet addresses ar=
e a similar example, globally unique addresses, link only forwarding scope.=
)</div></div></div></blockquote><div><br></div><div>IMO defining ULAs as th=
ey are was a mistake. Global scope implies unique. But probabilistic unique=
ness doesn&#39;t work because humans choose ULAs instead of generating them=
 manually. Registry-based uniqueness doesn&#39;t work (and, to be fair, was=
 never tried by the IETF) because there is no registry that has jurisdictio=
n. Even if there were, there is no reason to keep addresses unique if they =
don&#39;t have global reachability.</div><div><br></div><div>So I guess I&#=
39;m somewhere between 1) and 3). The specs are consistent but they fail to=
 consider human behaviour, so they don&#39;t actually work in practice. I d=
on&#39;t know what to do about this though. If we say they&#39;re non-globa=
l scope, then they are going to be the exact equivalent of RFC1918 addresse=
s, with all the problems that that causes. If we continue to say they&#39;r=
e global scope, then the specs don&#39;t match reality. :-(</div></div></di=
v>

--000000000000e1b9f005b835fbc9--


From nobody Tue Jan  5 23:30:51 2021
Return-Path: <christopher.morrow@gmail.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 B63C83A11C2; Tue,  5 Jan 2021 23:30:45 -0800 (PST)
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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 hLA3otnRg3Hl; Tue,  5 Jan 2021 23:30:43 -0800 (PST)
Received: from mail-qt1-x82a.google.com (mail-qt1-x82a.google.com [IPv6:2607:f8b0:4864:20::82a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B052B3A11BE; Tue,  5 Jan 2021 23:30:43 -0800 (PST)
Received: by mail-qt1-x82a.google.com with SMTP id c14so1579942qtn.0; Tue, 05 Jan 2021 23:30:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=B09ywsGA62ENIR/fCzCVsO5C/xl/SVDxSOe5Op63kOM=; b=ek75tAkOEp1cEBeq53fFrxWr9c071vLaQoToXCIAhBTuCmFeqDcBUyYb2ir2ByXVun ud7glL3nWg9Zr0HFZeAej8ceLBhGh2PI3gMZqWzeKiMaGrF7Nxv7Tq2NHVJBOLrxa+yJ kS/yoymsUi2zmwUK+OEBqjRAOamJWi8f0m9+G/f8FDyowWJCJwtGEx+/BzH1NndVGThp LtdKpeh469NmumxnKkGH/RiSiVq5kLxJX4i/W4iI7EccGy3ptDrVKgkNNIPsa71paAqs mAooYzwzw3r90p2Nrhoh+r6qLkPVUQGqreNMZxATASSP0hndY7QcP8pNNJ4u/e4xV3Zu vLUw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=B09ywsGA62ENIR/fCzCVsO5C/xl/SVDxSOe5Op63kOM=; b=fZZR+/mEQfx5lQsCTaAnUM7PoFi6tIHTNJbkjGd0geuTLwdyGSlw+tNVdVb5EPRzgB Q3NnpwP2Ia8tVbThKHLud3QDZ2u6aCKN6t/ejqiePofsy7iD/ikajQgC3SM/s1qmSYdG WIXwjOUMEG3C9eJwf74sf4CpBnmz7XLIFfV7zHFodohe5gVAMnLDI8G4jb2qri3SiRMn AVn1AQlq1SAKmLuH25DNl+hzMTHnBMKeoMriJvTyeXXSoifwmMVmqe1w+8X+nkdlj/Z6 ol3/FsJFQ5X2JYl4BGTXxyP+gG428WDqRp9l+S7LM8WCseeysUEOKT+JPKx73WPDYWoJ w0fA==
X-Gm-Message-State: AOAM530Ji3DjkUh1t6flZNoYnJtfF3JpHThulmMzMW3O4/m94EmCndaI cSRO38SnB49SNTTBWKt96XFfH25Z4E3BmfPBagM=
X-Google-Smtp-Source: ABdhPJzwDFeCmWmM9ZD7yWv4vgyfvQZotdId8kM9jYQduV27QvVKSUQ2RILMrf7FlNgdOh1LMctQ3lOiYNdv/dcVgWc=
X-Received: by 2002:aed:2e63:: with SMTP id j90mr3043667qtd.338.1609918242587;  Tue, 05 Jan 2021 23:30:42 -0800 (PST)
MIME-Version: 1.0
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com>
In-Reply-To: <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
Date: Wed, 6 Jan 2021 02:30:31 -0500
Message-ID: <CAL9jLaZA4y+9bdvzq5r4V=B6580ZnsdwYyvQ4nzjdeccMsM4Tg@mail.gmail.com>
To: Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>
Cc: Mark Smith <markzzzsmith@gmail.com>, Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Sh0wNAPMITuuYAqzAoDn8Ub0HfU>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 07:30:46 -0000

On Wed, Jan 6, 2021 at 2:09 AM Lorenzo Colitti
<lorenzo=3D40google.com@dmarc.ietf.org> wrote:
>
> On Wed, Jan 6, 2021 at 11:01 AM Mark Smith <markzzzsmith@gmail.com> wrote=
:
>>
>> ULAs are intended to be globally unique addresses, but not to be globall=
y (Internet) forwardable. Their forwarding scope is limited to non-global, =
either within a single local network, or between a set of local networks th=
at have agreed to forward their respective ULA /48 prefixes between each ot=
her, overriding the default of local networks only forwarding scope. (Ether=
net addresses are a similar example, globally unique addresses, link only f=
orwarding scope.)
>
>
> IMO defining ULAs as they are was a mistake. Global scope implies unique.=
 But probabilistic uniqueness doesn't work because humans choose ULAs inste=
ad of generating them manually. Registry-based uniqueness doesn't work (and=
, to be fair, was never tried by the IETF) because there is no registry tha=
t has jurisdiction. Even if there were, there is no reason to keep addresse=
s unique if they don't have global reachability.
>
> So I guess I'm somewhere between 1) and 3). The specs are consistent but =
they fail to consider human behaviour, so they don't actually work in pract=
ice. I don't know what to do about this though. If we say they're non-globa=
l scope, then they are going to be the exact equivalent of RFC1918 addresse=
s, with all the problems that that causes. If we continue to say they're gl=
obal scope, then the specs don't match reality. :-(

option 4, deprecate ULA.
the best option (tm).


From nobody Tue Jan  5 23:38:45 2021
Return-Path: <fgont@si6networks.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 F20B63A08E7; Tue,  5 Jan 2021 23:38:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.161
X-Spam-Level: 
X-Spam-Status: No, score=-2.161 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, 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 bJhZi8F01NB9; Tue,  5 Jan 2021 23:38:41 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF3763A095E; Tue,  5 Jan 2021 23:38:40 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id A4256283A88; Wed,  6 Jan 2021 07:38:36 +0000 (UTC)
To: Lorenzo Colitti <lorenzo@google.com>, Mark Smith <markzzzsmith@gmail.com>
Cc: IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <3e8a9ff3-ac2b-988b-8517-fbbdcff9ff9e@si6networks.com>
Date: Wed, 6 Jan 2021 04:38:23 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/uz4CKYd8J627tV1N6LbmO0JCkII>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 07:38:44 -0000

On 6/1/21 04:07, Lorenzo Colitti wrote:
> On Wed, Jan 6, 2021 at 11:01 AM Mark Smith <markzzzsmith@gmail.com 
> <mailto:markzzzsmith@gmail.com>> wrote:
> 
>     ULAs are intended to be globally unique addresses, but not to be
>     globally (Internet) forwardable. Their forwarding scope is limited
>     to non-global, either within a single local network, or between a
>     set of local networks that have agreed to forward their respective
>     ULA /48 prefixes between each other, overriding the default of local
>     networks only forwarding scope. (Ethernet addresses are a similar
>     example, globally unique addresses, link only forwarding scope.)
> 
> 
> IMO defining ULAs as they are was a mistake. Global scope implies 
> unique. But probabilistic uniqueness doesn't work because humans choose 
> ULAs instead of generating them manually.

Not only that. At a global scale, the Birthday problem tells you that 
the ULA prefixes will also be non-unique. ~1.2M of house-hods generating 
their ULA prefixes already gives you P~1 that you have a collision at 
the global level. Indeed, the math in 
https://tools.ietf.org/html/rfc4193#section-3.2.3 already implicitly 
acknowledges this fact, because the probability of collision is computed 
on the basis of how many networks you interconnect -- that's certainly 
not what "global scope" means.



> Registry-based uniqueness 
> doesn't work (and, to be fair, was never tried by the IETF) because 
> there is no registry that has jurisdiction. Even if there were, there is 
> no reason to keep addresses unique if they don't have global reachability.

Fully agreed.



> So I guess I'm somewhere between 1) and 3). The specs are consistent but 
> they fail to consider human behaviour, so they don't actually work in 
> practice.

If you look at the definition of scope and global scope from RFC4007, 
it's inconsistent with employing it for defining ULAs as global.

(Indeed, the *L* in ULA says it all ;-) )



> I don't know what to do about this though. If we say they're 
> non-global scope, then they are going to be the exact equivalent of 
> RFC1918 addresses, with all the problems that that causes. If we 
> continue to say they're global scope, then the specs don't match 
> reality. :-(

One can say that they are local scope, with the expectation that since 
the ULA prefix is meant to be randomly generated, then sites that comply 
with such requirement will have a small probability of prefix collisions 
if two ULA-based sites were to be merged/interconnected.

I think that's as real and factually correct as it can get.

Besides, this also means that libraries such as ipaddress match the 
specs. -- right now, they don't. And it would be hard to argue that 
libraries such as Python's ipaddress should be changed such that ULAs 
are flagged as both "global" and "public". -- something that would not 
only be wrong, but that can also not be done in a backwards compatible 
manner.  Also, if apps, for some reason, are checking such address 
attributes, it's certainly better that the attributes are set in an 
intuitive way (the current one, which doesn't match the specs), in the 
hopes that they can make something useful out of differentiating IPv6 
address properties.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan  6 00:16:43 2021
Return-Path: <markzzzsmith@gmail.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 055433A11E8; Wed,  6 Jan 2021 00:16:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.598
X-Spam-Level: 
X-Spam-Status: No, score=-0.598 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.998, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 m0RMNszsbVGm; Wed,  6 Jan 2021 00:16:40 -0800 (PST)
Received: from mail-oo1-xc2e.google.com (mail-oo1-xc2e.google.com [IPv6:2607:f8b0:4864:20::c2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90A233A08A9; Wed,  6 Jan 2021 00:16:40 -0800 (PST)
Received: by mail-oo1-xc2e.google.com with SMTP id j21so573577oou.11; Wed, 06 Jan 2021 00:16:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Hv+z6C8N/8tsSlNhDQeWDtom18SNWfr6ue8W5TflGHw=; b=HHmc7Ql0Qv9HTgFtHYREXql30u4OCb3SCUNPyVVd3Xci+vguMgsuzZGRtPRzego6cZ 1SuyFa3LJsOLJ3N8tNjI+gKhRdk5v9tcTMrlWrgQ+W+Tyq0eZmGMWYYKca4BifWewGPH GaNjs5YuvMXYNlrHHo6GeTUbpvm/yiWPTXJvzqN6oxxBtPtmQmznvLW+nFQGyj8un7xp ZfS6F3udTR2YO8pobxvjPJoS6X6KGictxIforODtWbocsWgjcVEULMIlRcVknFfx3fnT YJOQj+G/K2TVgfCTHArVjUMMgDwlbwTrxSAe6Jf6d7dg6l0WMvTIM1ZCzw/qY0f83MGU aHBw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Hv+z6C8N/8tsSlNhDQeWDtom18SNWfr6ue8W5TflGHw=; b=lVDWBMfYrH4ZOqwUrATXXzw+RdZvs9NANyH5UD6Fs8i7gxQp4ibRIQhfQtLlcWTrNM tly5TMXGzusspL68J3StKsyn8cAtbwcB96w8KbKlmdR5aC8Lxk6A2sIohN1rGprzJMDe 22unXUJ1IV/CRduxam5zHn5LeYVLNzki9sLts1t256tbgN6uKKmAz0ryN6wLzMfMCWvv Br2jJmbbOqZivpM+x/UNEFGuWqrF6CHVLCr1tnYmXCwG7PvWMe4Gq9V0SSzwuyfL4lsk pZODR7rRCl5DQ//WmNTkAsnXndILI15hDCoNXhLNziXw4tifpRDKL+2Dc3s5UB/0Ot0B xrrQ==
X-Gm-Message-State: AOAM532x4m2MXQCgKGXJBUrnluqVRgeCxIxZJZftmpsj7G47hB2edg+f eMps9VUbAt6m/G4JeQuLkDeEDBkRPIftSdGIrBk=
X-Google-Smtp-Source: ABdhPJzeupSNH2bYv620WA0DLsyOvzEKoG67i4LT3+Er3myuU6xXXaaYl/MJDPwLj3P+PBPhQZrY9NpYi4uV1DejZGY=
X-Received: by 2002:a4a:520f:: with SMTP id d15mr1995880oob.29.1609920999896;  Wed, 06 Jan 2021 00:16:39 -0800 (PST)
MIME-Version: 1.0
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com> <CAL9jLaZA4y+9bdvzq5r4V=B6580ZnsdwYyvQ4nzjdeccMsM4Tg@mail.gmail.com>
In-Reply-To: <CAL9jLaZA4y+9bdvzq5r4V=B6580ZnsdwYyvQ4nzjdeccMsM4Tg@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Wed, 6 Jan 2021 19:16:27 +1100
Message-ID: <CAO42Z2yUEUJ5K15zdGaO6e9LneUK-Q8pSbZ0dwjQbhi=UCHJTQ@mail.gmail.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
Cc: Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>,  Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000050b8a705b836f140"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/d1tOlhA-iNCw2rzq1aaCR8O6d9Y>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 08:16:42 -0000

--00000000000050b8a705b836f140
Content-Type: text/plain; charset="UTF-8"

On Wed, 6 Jan 2021, 18:30 Christopher Morrow, <christopher.morrow@gmail.com>
wrote:

> On Wed, Jan 6, 2021 at 2:09 AM Lorenzo Colitti
> <lorenzo=40google.com@dmarc.ietf.org> wrote:
> >
> > On Wed, Jan 6, 2021 at 11:01 AM Mark Smith <markzzzsmith@gmail.com>
> wrote:
> >>
> >> ULAs are intended to be globally unique addresses, but not to be
> globally (Internet) forwardable. Their forwarding scope is limited to
> non-global, either within a single local network, or between a set of local
> networks that have agreed to forward their respective ULA /48 prefixes
> between each other, overriding the default of local networks only
> forwarding scope. (Ethernet addresses are a similar example, globally
> unique addresses, link only forwarding scope.)
> >
> >
> > IMO defining ULAs as they are was a mistake. Global scope implies
> unique. But probabilistic uniqueness doesn't work because humans choose
> ULAs instead of generating them manually. Registry-based uniqueness doesn't
> work (and, to be fair, was never tried by the IETF) because there is no
> registry that has jurisdiction. Even if there were, there is no reason to
> keep addresses unique if they don't have global reachability.
> >
> > So I guess I'm somewhere between 1) and 3). The specs are consistent but
> they fail to consider human behaviour, so they don't actually work in
> practice. I don't know what to do about this though. If we say they're
> non-global scope, then they are going to be the exact equivalent of RFC1918
> addresses, with all the problems that that causes. If we continue to say
> they're global scope, then the specs don't match reality. :-(
>
> option 4, deprecate ULA.
> the best option (tm).
>


If you want to destroy IPv6 by causing enterprises to replicate RFC1918s
via site-locals and use NAT66, do that.

ULAs exist because site-locals would have created that problem.

People are already deploying ULAs mostly correctly - I know of 4
electricity smart meter networks that have more than 2 million meters
attached that are using ULA addressing. The only relatively minor mistake
made was that the smartmeter vendor took the 4 network's ULA spaces out of
a single /48, using /52s if I recall correctly, rather than generating a
/48 for each one.

While probably prohibited by government, if any if those networks merged,
routing between them will be as simple as linking them together and trading
/52 routes.

If they'd used site-locals, merging would instead be either as complex as
renumbering, or as bad as NAT66, the latter being most likely.

--00000000000050b8a705b836f140
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><br><br><div class=3D"gmail_quote"><div dir=3D"ltr" =
class=3D"gmail_attr">On Wed, 6 Jan 2021, 18:30 Christopher Morrow, &lt;<a h=
ref=3D"mailto:christopher.morrow@gmail.com">christopher.morrow@gmail.com</a=
>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, Jan 6, 2021 at=
 2:09 AM Lorenzo Colitti<br>
&lt;lorenzo=3D<a href=3D"mailto:40google.com@dmarc.ietf.org" target=3D"_bla=
nk" rel=3D"noreferrer">40google.com@dmarc.ietf.org</a>&gt; wrote:<br>
&gt;<br>
&gt; On Wed, Jan 6, 2021 at 11:01 AM Mark Smith &lt;<a href=3D"mailto:markz=
zzsmith@gmail.com" target=3D"_blank" rel=3D"noreferrer">markzzzsmith@gmail.=
com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; ULAs are intended to be globally unique addresses, but not to be g=
lobally (Internet) forwardable. Their forwarding scope is limited to non-gl=
obal, either within a single local network, or between a set of local netwo=
rks that have agreed to forward their respective ULA /48 prefixes between e=
ach other, overriding the default of local networks only forwarding scope. =
(Ethernet addresses are a similar example, globally unique addresses, link =
only forwarding scope.)<br>
&gt;<br>
&gt;<br>
&gt; IMO defining ULAs as they are was a mistake. Global scope implies uniq=
ue. But probabilistic uniqueness doesn&#39;t work because humans choose ULA=
s instead of generating them manually. Registry-based uniqueness doesn&#39;=
t work (and, to be fair, was never tried by the IETF) because there is no r=
egistry that has jurisdiction. Even if there were, there is no reason to ke=
ep addresses unique if they don&#39;t have global reachability.<br>
&gt;<br>
&gt; So I guess I&#39;m somewhere between 1) and 3). The specs are consiste=
nt but they fail to consider human behaviour, so they don&#39;t actually wo=
rk in practice. I don&#39;t know what to do about this though. If we say th=
ey&#39;re non-global scope, then they are going to be the exact equivalent =
of RFC1918 addresses, with all the problems that that causes. If we continu=
e to say they&#39;re global scope, then the specs don&#39;t match reality. =
:-(<br>
<br>
option 4, deprecate ULA.<br>
the best option (tm).<br></blockquote></div></div><div dir=3D"auto"><br></d=
iv><div dir=3D"auto"><br></div><div dir=3D"auto">If you want to destroy IPv=
6 by causing enterprises to replicate RFC1918s via site-locals and use NAT6=
6, do that.</div><div dir=3D"auto"><br></div><div dir=3D"auto">ULAs exist b=
ecause site-locals would have created that problem.=C2=A0</div><div dir=3D"=
auto"><br></div><div dir=3D"auto">People are already deploying ULAs mostly =
correctly - I know of 4 electricity smart meter networks that have more tha=
n 2 million meters attached that are using ULA addressing. The only relativ=
ely minor mistake made was that the smartmeter vendor took the 4 network&#3=
9;s ULA spaces out of a single /48, using /52s if I recall correctly, rathe=
r than generating a /48 for each one.</div><div dir=3D"auto"><br></div><div=
 dir=3D"auto">While probably prohibited by government, if any if those netw=
orks merged, routing between them will be as simple as linking them togethe=
r and trading /52 routes.</div><div dir=3D"auto"><br></div><div dir=3D"auto=
">If they&#39;d used site-locals, merging would instead be either as comple=
x as renumbering, or as bad as NAT66, the latter being most likely.</div><d=
iv dir=3D"auto"><br></div><div dir=3D"auto"><br></div><div dir=3D"auto"><br=
></div><div dir=3D"auto"><div class=3D"gmail_quote"><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">
</blockquote></div></div></div>

--00000000000050b8a705b836f140--


From nobody Wed Jan  6 02:54:53 2021
Return-Path: <gert@space.net>
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 96BD13A12CD for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 02:54:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=space.net
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 2Ng1M_T7NFo5 for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 02:54:49 -0800 (PST)
Received: from gatekeeper1-relay.space.net (gatekeeper1-relay.space.net [IPv6:2001:608:3:85::38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D4213A12CE for <v6ops@ietf.org>; Wed,  6 Jan 2021 02:54:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=space.net; i=@space.net; q=dns/txt; s=esa; t=1609930489; x=1641466489; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=qGqVBzIEllYOVbK2HCRYQOQdY8WzeMK7J3U2WgaSOoE=; b=Xc2MimeD0avSIm5Pk6l8NorlcSgLvD6mGUE7zx3Ggbn7foTJ8N4GzGTW Q/vDsWpTajBcZnMZg7UgQKXsjlKKOyTEnXCpCKn2kBBGrTMSSSBkAfBEi 1cErstXPznLVhi2KgSTr8W+TleKwU8gCar5pki0p84Oa6avrA2BwiP3J9 e57BMooa8/S5LV812Fz4bwqfNLWZca/faHxu6hwH6MUNycWOL3JFVo4ZZ hcaHnlJv5cWdC153i1wBrtTarUjEdjOrCeGOKKWhuA/bLvepVKxAOypuR 2k/VqeIu3iGxnIRwpdZDFXEZB2Whv7jWai6Li7YadF1FhjCv6EyaTCSIF g==;
IronPort-SDR: kBK2ih51NNAN88n+9x17u1zrZNdL+G3BEoMTuKrq5Tvcg+1h2pGXh+phKII5iUB6l/10/Ff56/ v3PuXBrBbyRxSsJoC1aG7EioRGQU/AMcq8GjLuSoGj3EIsRxadCGPZbOBKQryvB6UZGwFOAMhK yR9iSguTS249ttF4dlCLD4h/RyFu+Y7s8YQyd271AZvp7a6yjwEX/mejhX8frlyV2mDfnCtpEa hWyzx9kAsJ/FMWUCJu1m3cuITPtB3VALsTj8YP1Cj6wy6XF+jsZyDtjDznvUhDxUBO0TR5AsgM 3kk=
X-SpaceNet-SBRS: None
Received: from mobil.space.net ([195.30.115.67]) by gatekeeper1-relay.space.net with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Jan 2021 11:54:45 +0100
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 82F6843AD0 for <v6ops@ietf.org>; Wed,  6 Jan 2021 11:54:45 +0100 (CET)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 18B60427F9; Wed,  6 Jan 2021 11:54:45 +0100 (CET)
Received: by moebius4.space.net (Postfix, from userid 1007) id 0F741DDC86; Wed,  6 Jan 2021 11:54:45 +0100 (CET)
Date: Wed, 6 Jan 2021 11:54:45 +0100
From: Gert Doering <gert@space.net>
To: Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>
Cc: Mark Smith <markzzzsmith@gmail.com>, Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
Message-ID: <20210106105445.GU13005@Space.Net>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/cjU1ts56rdG4ioZ1cM6q3LIXO18>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 10:54:52 -0000

Hi,

On Wed, Jan 06, 2021 at 04:07:51PM +0900, Lorenzo Colitti wrote:
> Registry-based uniqueness doesn't work
> (and, to be fair, was never tried by the IETF) because there is no registry
> that has jurisdiction. 

ULA-C was abandoned.  But that could be revived...

Find a registry is not hard.  Anyone could be the registry, if IETF gives
their blessing and says "there's a machine that spits out a guaranteeed 
unique ULA /48s for each $20 you feed in"...

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279


From nobody Wed Jan  6 04:17:44 2021
Return-Path: <mellon@fugue.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 8E44B3A03EB for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 04:17:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 BbUnPtAD1NHu for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 04:17:37 -0800 (PST)
Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCB003A03EC for <v6ops@ietf.org>; Wed,  6 Jan 2021 04:17:37 -0800 (PST)
Received: by mail-io1-xd2c.google.com with SMTP id m23so2541641ioy.2 for <v6ops@ietf.org>; Wed, 06 Jan 2021 04:17:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=4LlZbIUceEaVckEvBwddjJ9hRtWzsxnSprME/90jWOA=; b=uTdOfJ1HYvu8mCXpj+YDIp4V+Z5+qJD6mieOhxjFl7snIlTbXS+0rxTYIvtlrr1W3T +W+kdQX7tIDMffJ8KGSKzAYYtguoZDJ+sZu+iWBg3lRLmzHER9QSDi6fFGDZLhFDAwlg kANkkZ1BIyZgdyXRiaMqGaiNbWKGiWbXw83q4a5GaB8kDNNJXW8Rg7e98IIShpbjR14D RBWo/s2uD6hwRGj6eW+okdfBrd1ozxrZgtK3es1unD4REMliZyfpGkZh/GUPwjVq8ujy Z1cQW+jOlmd1tOiVtQQZaWauraHpIMJmoKGc+G+sAln/RXf2/6OyL8I7VAYGBt+GTOPN M2fg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=4LlZbIUceEaVckEvBwddjJ9hRtWzsxnSprME/90jWOA=; b=odz84gPkWTmbYTWKWO5j4mGjKANzA+VfrzynyKDEneRdOtkCdEnHy4pz7wcGd2XGiY Oj2qJNA/sUaGaWW8qnY9CR77VrEA/L5JVa9+XpbdRDFoh6yqQkfBpiTdBSy2tqcyJyfu QRwsZNig1uPef/sScyT6jYL6ENP39z9ZmR3/E2zUkVhVwMQx6kQm0rdtbIhpFoOVvTRj ix42WKutdWDvbXphUqr+QG1sxQo5fD+bncuwJQawlYaa7x6YVoR7sl16xbI32XavYMCE fTJbMq65lIZLeSu9GtAYgZax4ijqq2nfJTV8VbWkvGTwLTpNH29jofQVj70EJKoFfG+c ejNw==
X-Gm-Message-State: AOAM533L7CwjYnEVWKi5+4s03jfgV9b6iGXbun2OpcoJdg8KpTTF2iam K8lPaR/S49MJh65UfJkd5rR+ZVSrCY+mNQ==
X-Google-Smtp-Source: ABdhPJxJsngGd9akaIiVZjq97k/GB1FRzARSuG/2+EZ86+DgDmsLhhGWtnEG9h9rNJ5O7GqCt5bu2A==
X-Received: by 2002:a6b:4f13:: with SMTP id d19mr2603904iob.121.1609935456681;  Wed, 06 Jan 2021 04:17:36 -0800 (PST)
Received: from mithrandir.lan (c-24-91-177-160.hsd1.nh.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id r12sm1908049ile.59.2021.01.06.04.17.35 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Jan 2021 04:17:35 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <EFF2CF9D-147B-4E7F-9080-633A24FDA666@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_10497EDE-6AC7-4BB4-BBC2-0FE624F2F492"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.2\))
Date: Wed, 6 Jan 2021 07:17:33 -0500
In-Reply-To: <CAN-Dau344H7xgD0Q_O54c=R08zFRFjToO8BHt=ssauxgEH7ynA@mail.gmail.com>
Cc: Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
To: David Farmer <farmer=40umn.edu@dmarc.ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAN-Dau344H7xgD0Q_O54c=R08zFRFjToO8BHt=ssauxgEH7ynA@mail.gmail.com>
X-Mailer: Apple Mail (2.3654.60.0.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/X4sAxUYoqoEZKdsFXxMYj30Nemw>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 12:17:40 -0000

--Apple-Mail=_10497EDE-6AC7-4BB4-BBC2-0FE624F2F492
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Jan 5, 2021, at 11:38 PM, David Farmer =
<farmer=3D40umn.edu@dmarc.ietf.org> wrote:
> I think this is the right direction the previous draft indirectly =
defined a new scope "non-global", I much prefer explicitly defining a =
new local scope.

Actually, I think you=E2=80=99ve got it right here: the scope is =
=E2=80=9Cnon-global.=E2=80=9D

> I would add something like the following to better define the =
relationship between the three scopes;
>=20
> The boundary of the link-local scope is strongly defined, limiting the =
extent of the link-local scope to an individual link. However, in =
contrast, the boundary of the local scope is weakly defined, it is =
amorphous and imprecise. In some instances, the extent of the local =
scope can be a single site, in other instances, a group of unrelated =
sites, a single organization, or even a cooperating group of =
organizations. Furthermore, the extent of an individual instance of the =
local scope doesn't necessarily remain constant, it may expand or =
contract over time as the local situation dictates, for example when two =
organizations merge. Nevertheless, the extent of the local scope =
doesn=E2=80=99t encompass the entirety of the Internet which the global =
scope does.

There is at least one obvious problem with this definition: the term =
=E2=80=9Clocal.=E2=80=9D ULAs aren=E2=80=99t really local, despite the =
name. Using the name =E2=80=9Clocal=E2=80=9D is what leads to this =
confusion. Consider this taxonomy:

GUA: =E2=80=9Cvalid everywhere on the internet scope=E2=80=9D
ULA: =E2=80=9Cnot valid everywhere scope=E2=80=9D
LLA: =E2=80=9Cvalid only on this link scope=E2=80=9D

Of course these names are awkward, but I hope they are clarifying. A ULA =
is =E2=80=9Cnot valid everywhere.=E2=80=9D That=E2=80=99s really all you =
can say about it. You can=E2=80=99t put a ULA prefix in a global routing =
domain. You can put it in a site routing domain. You can put it in a =
multi-site routing domain. You can not route it at all. All these uses =
are valid.

So I don=E2=80=99t really object to your text, but I do object to the =
name =E2=80=9Clocal.=E2=80=9D How about =E2=80=9Cexplicit=E2=80=9D? That =
is, the scope of a ULA is explicit, in the sense that it must be _made_ =
explicit by the user(s) of the ULA? If that doesn=E2=80=99t work, I=E2=80=99=
m sure we can come up with a more agreeable term, but please let it not =
be =E2=80=9Clocal.=E2=80=9D Sorry to be a sticky wicket. :)


--Apple-Mail=_10497EDE-6AC7-4BB4-BBC2-0FE624F2F492
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">On =
Jan 5, 2021, at 11:38 PM, David Farmer &lt;<a =
href=3D"mailto:farmer=3D40umn.edu@dmarc.ietf.org" =
class=3D"">farmer=3D40umn.edu@dmarc.ietf.org</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><meta =
charset=3D"UTF-8" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">I think this is the right direction the previous draft =
indirectly defined a new scope "non-global", I much prefer =
explicitly&nbsp;defining a new local =
scope.</span></div></blockquote><div><br class=3D""></div>Actually, I =
think you=E2=80=99ve got it right here: the scope is =
=E2=80=9Cnon-global.=E2=80=9D</div><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div style=3D"caret-color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D"">I would add something like the =
following to better define the relationship between the three =
scopes;</div><div style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><br class=3D""></div><blockquote style=3D"caret-color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; margin: 0px 0px 0px 40px; border: none; padding: =
0px;" class=3D""><div class=3D"">The boundary of the link-local scope is =
strongly defined, limiting the extent of the link-local scope to an =
individual link. However, in contrast, the boundary of the local scope =
is weakly defined, it is amorphous and imprecise. In some instances, the =
extent of the local scope can be a single site, in other instances, a =
group of unrelated sites, a single organization, or even a cooperating =
group of organizations. Furthermore, the extent of an individual =
instance of the local scope doesn't necessarily remain constant, it may =
expand or contract over time as the local situation dictates, for =
example when two organizations merge. Nevertheless, the extent of the =
local scope doesn=E2=80=99t encompass the entirety of the Internet which =
the global scope does.</div></blockquote></div></blockquote></div><br =
class=3D""><div class=3D"">There is at least one obvious problem with =
this definition: the term =E2=80=9Clocal.=E2=80=9D ULAs aren=E2=80=99t =
really local, despite the name. Using the name =E2=80=9Clocal=E2=80=9D =
is what leads to this confusion. Consider this taxonomy:</div><div =
class=3D""><br class=3D""></div><div class=3D"">GUA: =E2=80=9Cvalid =
everywhere on the internet scope=E2=80=9D</div><div class=3D"">ULA: =
=E2=80=9Cnot valid everywhere scope=E2=80=9D</div><div class=3D"">LLA: =
=E2=80=9Cvalid only on this link scope=E2=80=9D</div><div class=3D""><br =
class=3D""></div><div class=3D"">Of course these names are awkward, but =
I hope they are clarifying. A ULA is =E2=80=9Cnot valid everywhere.=E2=80=9D=
 That=E2=80=99s really all you can say about it. You can=E2=80=99t put a =
ULA prefix in a global routing domain. You can put it in a site routing =
domain. You can put it in a multi-site routing domain. You can not route =
it at all. All these uses are valid.</div><div class=3D""><br =
class=3D""></div><div class=3D"">So I don=E2=80=99t really object to =
your text, but I do object to the name =E2=80=9Clocal.=E2=80=9D How =
about =E2=80=9Cexplicit=E2=80=9D? That is, the scope of a ULA is =
explicit, in the sense that it must be _made_ explicit by the user(s) of =
the ULA? If that doesn=E2=80=99t work, I=E2=80=99m sure we can come up =
with a more agreeable term, but please let it not be =E2=80=9Clocal.=E2=80=
=9D Sorry to be a sticky wicket. :)</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_10497EDE-6AC7-4BB4-BBC2-0FE624F2F492--


From nobody Wed Jan  6 04:33:19 2021
Return-Path: <mellon@fugue.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 F20963A048B for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 04:33:17 -0800 (PST)
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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 9knDcIOcN9Uw for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 04:33:16 -0800 (PST)
Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69CFA3A046B for <v6ops@ietf.org>; Wed,  6 Jan 2021 04:33:16 -0800 (PST)
Received: by mail-io1-xd31.google.com with SMTP id t8so2546869iov.8 for <v6ops@ietf.org>; Wed, 06 Jan 2021 04:33:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=YNFQP3IieN1wBTliOwkbOYceBsMswg28OVyh1Bd9XMI=; b=lCZZkPEzd8QpbwjAUI/SPu5MqQOE57j+H69ehwn1yfVj8dmNNAZk72Di9qd1UOeQ24 XDysbCGHX5CR4hBwNPlDABvqoNQohEeIGa0S9qTd5fPtVl3lY9ATsQJqFX18lYgA/IBp vxyB4JqX4Mk8cWnuMSRHC+CIrCywgsk/LTQGrOx7wh80DiVqFoWYqX8CUDZvVHzG7lRg o5MnFfKRr20YiGxMURapA5oDvRgh50ffJ5fyvmw1gR3SLTnf0nZpftWD52ArQUHqAJFb A/sz56ot+cWu0RDMGdhZmCeGrCvNW3/1xMOGUEbcrR/m1UFPQdcdnmP7aX4JVoiOM0bo 6jIA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=YNFQP3IieN1wBTliOwkbOYceBsMswg28OVyh1Bd9XMI=; b=RvxONGcolVJi3ysyfwYQracOFDUcMusidQzonjckYyatjIoMcbGljg/M2PMTS7woRR e0HqqH20x20sKGH+ptlWX7LYYtzeZ/IHcGyVB+Wiw6dcEZJOfJxOTeW+p3dhjoQNRh6u ySOExXQTWV5r4VEOCsnSqsNGMCM4R/UQLOwKk/cKvYCVx1jDQ7geK9amab88pMc/oeDZ rSXjZR5CMl6WUv+MI2VrW/3G8w4Mr0P6MzhFrDDaZBFn0wTzvTH/UAqIoQj8dQZDY22C kxoKtFRipaAUw5W0joQhNax3nvyAQ9t0rvxq9kAHECrZdG2K5LJcD4mfG8vW1vhQ0I/D 9VaA==
X-Gm-Message-State: AOAM531xrjF5/WQ7/Y2taFdblBwKq+xvMAie5uzRXdjc0CLjkiOv0OwP mquvCBcEirIjHjGtmaiiYMTTBw==
X-Google-Smtp-Source: ABdhPJxr8ZJETE76M+MTzT3RPk0K8vGIXr/kjPegBYf6a6UpufGRoF0ReqUoG8GTB8HPaFcQQTAYew==
X-Received: by 2002:a02:a417:: with SMTP id c23mr3539867jal.42.1609936395443;  Wed, 06 Jan 2021 04:33:15 -0800 (PST)
Received: from mithrandir.lan (c-24-91-177-160.hsd1.nh.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id m19sm1905214ila.81.2021.01.06.04.33.14 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Jan 2021 04:33:14 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <735226B9-5A0E-48AE-8B9A-CCDC5ED8C3ED@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_13BF4F69-5645-4479-9094-BEEE0BA2F6FD"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.2\))
Date: Wed, 6 Jan 2021 07:33:12 -0500
In-Reply-To: <CAL9jLaZA4y+9bdvzq5r4V=B6580ZnsdwYyvQ4nzjdeccMsM4Tg@mail.gmail.com>
Cc: Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>, Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
To: Christopher Morrow <christopher.morrow@gmail.com>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com> <CAL9jLaZA4y+9bdvzq5r4V=B6580ZnsdwYyvQ4nzjdeccMsM4Tg@mail.gmail.com>
X-Mailer: Apple Mail (2.3654.60.0.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/2WAPEwgfRWoJ1-qhZdUGAHjzHHA>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 12:33:18 -0000

--Apple-Mail=_13BF4F69-5645-4479-9094-BEEE0BA2F6FD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Jan 6, 2021, at 2:30 AM, Christopher Morrow =
<christopher.morrow@gmail.com> wrote:
> option 4, deprecate ULA.
> the best option (tm).

If that were an option, we wouldn=E2=80=99t be having this =
argument=E2=80=94nobody would care about ULAs. ULAs are a good idea. The =
terminology around them needs work, that=E2=80=99s all.=20

For example, we use ULAs in the HomePod Mini to route between adjacent =
network links where IPv6 GUA delegation isn=E2=80=99t available. The ULA =
never winds up in the global routing topology. The Mini chooses it using =
a secure RNG, so the likelihood of collision is vanishingly small. ULAs =
are _much_ more flexible than RFC1918 addresses, simply by virtue of the =
process by which the /48 prefix is chosen.

I would have major wibbles about using RFC1918 addresses in the Mini the =
way we currently use ULAs, because we=E2=80=99d have (at best!) eight =
bits of randomness, and a strong likelihood of collisions with competing =
private network uses of the 10.0/8 space. Because ULA is specific about =
each prefix being a /48, and because a /48 is most likely enough for =
most use cases, the worries about this sort of collision are =
nonexistent: nobody is going to allocate the whole ULA space to a single =
site, and if they do, we can legitimately say that they are at fault for =
things not working.

We can=E2=80=99t and shouldn=E2=80=99t deprecate ULAs. I think =
clarifying what the name means makes sense, though, and perhaps the term =
should be CUA (collision-unlikely address) prefix rather than ULA =
prefix.


--Apple-Mail=_13BF4F69-5645-4479-9094-BEEE0BA2F6FD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">On =
Jan 6, 2021, at 2:30 AM, Christopher Morrow &lt;<a =
href=3D"mailto:christopher.morrow@gmail.com" =
class=3D"">christopher.morrow@gmail.com</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"caret-color: =
rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">option 4, deprecate ULA.</span><br style=3D"caret-color: =
rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Menlo-Regular; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">the best option (tm).</span></div></blockquote></div><br =
class=3D""><div class=3D"">If that were an option, we wouldn=E2=80=99t =
be having this argument=E2=80=94nobody would care about ULAs. ULAs are a =
good idea. The terminology around them needs work, that=E2=80=99s =
all.&nbsp;</div><div class=3D""><br class=3D""></div><div class=3D"">For =
example, we use ULAs in the HomePod Mini to route between adjacent =
network links where IPv6 GUA delegation isn=E2=80=99t available. The ULA =
never winds up in the global routing topology. The Mini chooses it using =
a secure RNG, so the likelihood of collision is vanishingly small. ULAs =
are _much_ more flexible than RFC1918 addresses, simply by virtue of the =
process by which the /48 prefix is chosen.</div><div class=3D""><br =
class=3D""></div><div class=3D"">I would have major wibbles about using =
RFC1918 addresses in the Mini the way we currently use ULAs, because =
we=E2=80=99d have (at best!) eight bits of randomness, and a strong =
likelihood of collisions with competing private network uses of the =
10.0/8 space. Because ULA is specific about each prefix being a /48, and =
because a /48 is most likely enough for most use cases, the worries =
about this sort of collision are nonexistent: nobody is going to =
allocate the whole ULA space to a single site, and if they do, we can =
legitimately say that they are at fault for things not =
working.</div><div class=3D""><br class=3D""></div><div class=3D"">We =
can=E2=80=99t and shouldn=E2=80=99t deprecate ULAs. I think clarifying =
what the name means makes sense, though, and perhaps the term should be =
CUA (collision-unlikely address) prefix rather than ULA =
prefix.</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_13BF4F69-5645-4479-9094-BEEE0BA2F6FD--


From nobody Wed Jan  6 04:34:57 2021
Return-Path: <fgont@si6networks.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 226ED3A0596; Wed,  6 Jan 2021 04:34:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.16
X-Spam-Level: 
X-Spam-Status: No, score=-2.16 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 RKhNJ8nCvw9r; Wed,  6 Jan 2021 04:34:48 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D65363A048B; Wed,  6 Jan 2021 04:34:47 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id C71C7284516; Wed,  6 Jan 2021 12:34:42 +0000 (UTC)
To: Gert Doering <gert@space.net>, Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>
Cc: Mark Smith <markzzzsmith@gmail.com>, IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com> <20210106105445.GU13005@Space.Net>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <fd52e497-ac21-c0b5-6962-d8aca3ed0657@si6networks.com>
Date: Wed, 6 Jan 2021 08:47:23 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <20210106105445.GU13005@Space.Net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/8remdSARPKJdJdD0YyOOeM2YkSo>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 12:34:51 -0000

On 6/1/21 07:54, Gert Doering wrote:
> Hi,
> 
> On Wed, Jan 06, 2021 at 04:07:51PM +0900, Lorenzo Colitti wrote:
>> Registry-based uniqueness doesn't work
>> (and, to be fair, was never tried by the IETF) because there is no registry
>> that has jurisdiction.
> 
> ULA-C was abandoned.  But that could be revived...
> 
> Find a registry is not hard.  Anyone could be the registry, if IETF gives
> their blessing and says "there's a machine that spits out a guaranteeed
> unique ULA /48s for each $20 you feed in"...

Given what seems to be the fee for a /48 (not to mention that you can 
also get a /48 for free), not sure if such a registry would ever be 
attractive.

Anyway, that would still leave as with ULAs, as currently specified, 
marked as "global scope"...

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan  6 04:46:48 2021
Return-Path: <richard@helix.net.nz>
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 2C3053A0800 for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 04:46:47 -0800 (PST)
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, HTML_MESSAGE=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=helix-net-nz.20150623.gappssmtp.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 bLp8qJdvampP for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 04:46:45 -0800 (PST)
Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E1313A07EA for <v6ops@ietf.org>; Wed,  6 Jan 2021 04:46:45 -0800 (PST)
Received: by mail-io1-xd31.google.com with SMTP id r9so2583663ioo.7 for <v6ops@ietf.org>; Wed, 06 Jan 2021 04:46:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=helix-net-nz.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Xt+DFGaVFCABlwXAJA9vbnTxHsQdfnWceh+GcUIyTeE=; b=1z9JA0aoSuQX5dsOuOm92qouVykl7KixTA3fWSiGO5OuVBDiXyi+U3Z+slL7DlPytW YeHxHd4K7e1WrbsljF/OAPQgXcsVma9bP23c3XjdGDLK9qX1+aa1PijqJXL0B2njqHpz peZyyhmMiwN4eOnz1iZzfxEag2Tea4FdvNYqFFCGdlzzXgDNDK66ogUGvFj+EDE1n4S7 TxWGRo2iHGXv2szThRQPITdmjT4BWZ/u59V6cxgeaniRqZf8+qAtTHpQs6qEI1y9dJkt oRqvrYtOg/8ltIDI+Fa6eVq6nhWyx5kXB6b0kDkbHIby2Khl5/fgnZyHq34Bijv+Y+wC 9WuQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Xt+DFGaVFCABlwXAJA9vbnTxHsQdfnWceh+GcUIyTeE=; b=V6Sy1Iopof9DQCfdG567ETDdv1vwQmqu615c71bvabcVxMHIGvdEeSCiKi6cYMzD3g B0cZnvB45hdg4jGKfByVoz8fPEq1lA/ywmzYLV7yHQT64zZwUXz9SrWfxSZlra/L/d+2 54yW7SA7gXxbHWjyk6JHo3CAFgbPub3YeE5z3qMHAcCMnrO1QW9QvygplDwqprAirI0t 4brTJUnXAdQLB4lP95VvBcrovuT0G+vi5pQj9OZy2j7lcscITLvX41Z6Ydmthj9O/uRO POCBJbC8WRD+8KCrX94uQvoJn0OiSFc4Gyo3qisDY17v9i4aTvYbTemf+1xNFj7qeeCo SC8w==
X-Gm-Message-State: AOAM5319s3M/ckf+q1XyZ8dbvgh3GwH4SdL1mM4IkbYMumGHUvLmtBOW we/gcX9ZVefUq4fxS0sMPe5BrKtz87ibwg==
X-Google-Smtp-Source: ABdhPJwAa7Kvh+nHS0cPCplnRaoSowOFq4QnPSN86oxXEzl5QzTYeayQzC6O54xAhT8aRQLDfFufdw==
X-Received: by 2002:a02:778f:: with SMTP id g137mr207980jac.41.1609937204153;  Wed, 06 Jan 2021 04:46:44 -0800 (PST)
Received: from mail-io1-f49.google.com (mail-io1-f49.google.com. [209.85.166.49]) by smtp.gmail.com with ESMTPSA id s17sm1850265ilj.25.2021.01.06.04.46.42 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 06 Jan 2021 04:46:43 -0800 (PST)
Received: by mail-io1-f49.google.com with SMTP id u26so2602752iof.3; Wed, 06 Jan 2021 04:46:42 -0800 (PST)
X-Received: by 2002:a6b:b5d2:: with SMTP id e201mr2630790iof.111.1609937202742;  Wed, 06 Jan 2021 04:46:42 -0800 (PST)
MIME-Version: 1.0
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com> <CAL9jLaZA4y+9bdvzq5r4V=B6580ZnsdwYyvQ4nzjdeccMsM4Tg@mail.gmail.com>
In-Reply-To: <CAL9jLaZA4y+9bdvzq5r4V=B6580ZnsdwYyvQ4nzjdeccMsM4Tg@mail.gmail.com>
From: Richard Patterson <richard@helix.net.nz>
Date: Wed, 6 Jan 2021 12:46:31 +0000
X-Gmail-Original-Message-ID: <CAHL_VyCmYQ_X9FckY0Fem2Cq-zaDQ6e=WPxsHJP6LXKGksnU6A@mail.gmail.com>
Message-ID: <CAHL_VyCmYQ_X9FckY0Fem2Cq-zaDQ6e=WPxsHJP6LXKGksnU6A@mail.gmail.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
Cc: IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001489b805b83ab735"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/RSlwRpC6nxSkGu4nSZTOR4oRzb4>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 12:46:47 -0000

--0000000000001489b805b83ab735
Content-Type: text/plain; charset="UTF-8"

On Wed, 6 Jan 2021 at 07:31, Christopher Morrow <
christopher.morrow@gmail.com> wrote:

>
> option 4, deprecate ULA.
> the best option (tm).
>

Strongly disagree.
I think defining a new scope for ULA is a good idea and will help to
demystify and improve their use in the real world.

--0000000000001489b805b83ab735
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Wed, 6 Jan 2021 at 07:31, Christopher =
Morrow &lt;<a href=3D"mailto:christopher.morrow@gmail.com">christopher.morr=
ow@gmail.com</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex"><br>
option 4, deprecate ULA.<br>
the best option (tm).<br></blockquote><div><br></div><div>Strongly disagree=
.</div><div>I think defining a new scope for ULA is a good idea and will he=
lp to demystify and improve their use in the real world.</div></div></div>

--0000000000001489b805b83ab735--


From nobody Wed Jan  6 06:19:39 2021
Return-Path: <jtk@dataplane.org>
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 49C1D3A0EE1; Wed,  6 Jan 2021 06:19:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 oOktExs6kDsv; Wed,  6 Jan 2021 06:19:27 -0800 (PST)
Received: from dataplane.org (dataplane.org [IPv6:2001:49f0:d0c4:3::2]) by ietfa.amsl.com (Postfix) with ESMTP id A4DE83A0E1D; Wed,  6 Jan 2021 06:19:27 -0800 (PST)
Received: from p50.localdomain (localhost [127.0.0.1]) by dataplane.org (Postfix) with ESMTP id DA6E0688051C; Wed,  6 Jan 2021 14:19:26 +0000 (UTC)
Date: Wed, 6 Jan 2021 08:19:26 -0600
From: John Kristoff <jtk@dataplane.org>
To: Gert Doering <gert@space.net>
Cc: Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>, Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
Message-ID: <20210106081926.2ddcd33e@p50.localdomain>
In-Reply-To: <20210106105445.GU13005@Space.Net>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com> <20210106105445.GU13005@Space.Net>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Y99NicIYG_EeCkatLe4kw8LKk6g>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 14:19:35 -0000

On Wed, 6 Jan 2021 11:54:45 +0100
Gert Doering <gert@space.net> wrote:

> Find a registry is not hard.  Anyone could be the registry, if IETF gives
> their blessing and says "there's a machine that spits out a guaranteeed 
> unique ULA /48s for each $20 you feed in"...

This reminds me of IEEE OUIs.  You would want a price high enough that
would provide some disincentive to having anyone and everyone
registering for one or multiple assignments just because they can.  In
addition, not every one or every organization will want to publicly
listed in a registry. akin to LAAs, I don't have a strong opinion on
the matter, but a prefix for locally assigned addresses aren't all bad
until they either leak or must join another network that may have
conflicting practices.  That seems like an operational problem that can
be dealt with in a fairly straightforward way.

John


From nobody Wed Jan  6 06:27:33 2021
Return-Path: <fgont@si6networks.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 439233A0CDC; Wed,  6 Jan 2021 06:27:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.161
X-Spam-Level: 
X-Spam-Status: No, score=-2.161 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, 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 28YBZkPX-0Pq; Wed,  6 Jan 2021 06:27:24 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 043F73A0CC7; Wed,  6 Jan 2021 06:27:23 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id C1567284F4D; Wed,  6 Jan 2021 14:27:18 +0000 (UTC)
To: Ted Lemon <mellon@fugue.com>, David Farmer <farmer=40umn.edu@dmarc.ietf.org>
Cc: IPv6 Operations <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAN-Dau344H7xgD0Q_O54c=R08zFRFjToO8BHt=ssauxgEH7ynA@mail.gmail.com> <EFF2CF9D-147B-4E7F-9080-633A24FDA666@fugue.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <684e3296-a9d9-c899-9964-d80d693c1971@si6networks.com>
Date: Wed, 6 Jan 2021 11:04:43 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <EFF2CF9D-147B-4E7F-9080-633A24FDA666@fugue.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/M38r2Bb4FjMspkDy3XiWkLzY4Ns>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 14:27:27 -0000

Hi, Ted,

On 6/1/21 09:17, Ted Lemon wrote:
> On Jan 5, 2021, at 11:38 PM, David Farmer 
> <farmer=40umn.edu@dmarc.ietf.org 
> <mailto:farmer=40umn.edu@dmarc.ietf.org>> wrote:
>> I think this is the right direction the previous draft indirectly 
>> defined a new scope "non-global", I much prefer explicitly defining a 
>> new local scope.
> 
> Actually, I think you’ve got it right here: the scope is “non-global.”

Indeed. But then, link-locals are non-global, too.



>> I would add something like the following to better define the 
>> relationship between the three scopes;
>>
>>     The boundary of the link-local scope is strongly defined, limiting
>>     the extent of the link-local scope to an individual link. However,
>>     in contrast, the boundary of the local scope is weakly defined, it
>>     is amorphous and imprecise. In some instances, the extent of the
>>     local scope can be a single site, in other instances, a group of
>>     unrelated sites, a single organization, or even a cooperating
>>     group of organizations. Furthermore, the extent of an individual
>>     instance of the local scope doesn't necessarily remain constant,
>>     it may expand or contract over time as the local situation
>>     dictates, for example when two organizations merge. Nevertheless,
>>     the extent of the local scope doesn’t encompass the entirety of
>>     the Internet which the global scope does.
> 
> There is at least one obvious problem with this definition: the term 
> “local.” ULAs aren’t really local, despite the name. 

FWIW, I suggested "local" as the scope as given the "L" in "ULA", it was 
the obvious choice. I don't mind using any other term. What really 
matters is to use consistent terminology.

So I guess possible options (other than "local scope") are:

* private scope?
* organizational scope?
* administrative scope?



> So I don’t really object to your text, but I do object to the name 
> “local.” How about “explicit”? That is, the scope of a ULA is explicit, 
> in the sense that it must be _made_ explicit by the user(s) of the ULA? 

mm.. not really. As a user of ULAs, it's impossible to tell if the scope 
ends up being just one link (think a CPE that locally generates a ULA 
prefix and advertises it in the only internal net/link), or multisite.


If not "local" or "explicit", maybe one of the others suggestions above 
would work?

Thanks!

Regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan  6 06:27:47 2021
Return-Path: <fgont@si6networks.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 77B463A0E12; Wed,  6 Jan 2021 06:27:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.161
X-Spam-Level: 
X-Spam-Status: No, score=-2.161 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, 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 7jPvMtMvwmP4; Wed,  6 Jan 2021 06:27:32 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 857A73A0EA0; Wed,  6 Jan 2021 06:27:32 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 157C0284F20; Wed,  6 Jan 2021 14:27:27 +0000 (UTC)
To: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, ipv6@ietf.org
Cc: IPv6 Operations <v6ops@ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com>
Date: Wed, 6 Jan 2021 11:26:57 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <m1kx98E-0000EhC@stereo.hq.phicoh.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/IN9kXTOjszmlhke4zuqXING3QjE>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 14:27:41 -0000

Hi, Philip,

On 6/1/21 10:45, Philip Homburg wrote:
[...]
>> While this document does propose a way out (it assumes #3 above, and
>> acts accordingly), I believe the first step is to agree on what "global
>> scope" means and, subsequently, whether ULAs are really "global scope"
>> or not. Since opinions on the topic have vary a lot (as noted above),
>> I've posted this I-D and I'm sending this note for further input from
>> the WG.
> 
> In my opinion we should leave scope the way it is. 

The current definition of global scope as per RFC4007 doesn't match the 
definition of ULAs as being global scope. Both of them can't be right.



> Scope has a specific
> meaning for link local. In the past we tried to define local scope similar
> to how link-local scope is defined and it failed.
> 
> 'local' scope is an operational reality. You don't see it at the protocol
> level. So we need to keep it clearly separate from link-local where we do have
> quite a bit of protocol and API specification.

"scope" and "zone" are part of the architecture. So we have a IPv6 
Scoped Addressing Architecture, and then a definition ULAs that doesn't 
really comply with that definition.



[...]
> 
> Of cource with badly chosen ULAs, then chance is higher. But then again, does
> calling ULAs 'local' solve anything?

Changing the formal scope of ULAs does change the expectation when it 
comes to their usage: i.e., ULAs are not expected to be globally unique. 
They are just expected to have small chances of collision if you 
connected a limited number of ULA-based networks.

Besides, this does have an impact on current libraries (such as Python's 
ipaddress) and other libraries or macros that may have been defined for 
other languages, or that may be defined in the future.

This in turn probably affects the use such apps make of a list of 
addresses, when more than one is available.



> I don't see an immediate technical problem with ULAs, certainly not one that
> needs to be addressed with a standards track document.
> 
> A practical point that is mentioned in Section 5.1 is what to call ULAs.
> For example, we could call them 'private'. I think there is a need to
> the group of addresses that includes both rfc1918 and ULA. A short
> informational draft that addresses that point could be useful.

The problem is that for ULAs to be marked as "non-global" (whatever we 
call that), RFC4291 needs to be updated. Also, at least a part of 
RFC4193 needs to be updated.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan  6 06:37:01 2021
Return-Path: <mellon@fugue.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 80DAC3A0D07 for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 06:36:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 D4lkjQ5IUIxv for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 06:36:58 -0800 (PST)
Received: from mail-il1-x136.google.com (mail-il1-x136.google.com [IPv6:2607:f8b0:4864:20::136]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 457A53A0ADE for <v6ops@ietf.org>; Wed,  6 Jan 2021 06:36:58 -0800 (PST)
Received: by mail-il1-x136.google.com with SMTP id r17so3337950ilo.11 for <v6ops@ietf.org>; Wed, 06 Jan 2021 06:36:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=18gTR4klejsgf9D8zlgLaKC/yvmobUF0sw7dbBHOzDY=; b=fGdC6F2CVoGpyhe6+Bm6F20i3in+HnDu31XwB58lDvBxV6P98IFIvyTHXZyM6izLjc wRMmzBS12uW3va5qGqQr+vpgRYtBk/WTqzgLsIn4/4Cfhl/Jyrzq51bFY4m1Pqb3VRQD ruc6zcpGCpquJQ69mWXXvz0vba/+THILukG8BNY2w9dQDe9Ovkd+1MF0Jos+j0t/5c59 d+2hzKEN9xmfNOjl6Kl1YV9RAyYOSTe0NMT1/G7KIU78ML0zrkj4g5Ixs5M9Fcw4w0DG wCVaRKhRsjwNjTSmiU/OR0v68qa+PxiDqI8K5xw9df8DMUdERieS69aeKo+TAkRAE3z7 2TKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=18gTR4klejsgf9D8zlgLaKC/yvmobUF0sw7dbBHOzDY=; b=dt1LiF/975V4VMnWRKY4UQoiVqrVMVtHux9J/pNEwzU6iN7ESO0DkMfQA51xW+lmb5 9UQNF8T6PdPQFVr+Rq/O2L8vk3ZJTfHA/RGx3TSwZSh7nwljiBoeqU+UdUCaYzbCqTWf e8w+8KR642YNSw6LzkfgUy/vAO7PfKUGxahu5g38na8M/FUTN8ev0w3RDLvoYrb3eBbR +6Kul0bcYh1znmhGjp9DQCF+HCDt8gNrrGsNGmJiP4/+VDz+YJ16ArA00d0xHzhWZMCn d/g+78O/U/hi3ij9ZOF1JQ0+dfiTTywsVYZxsHGOTPNljYGRZnBh7hRiQseys+TouoT0 JUXg==
X-Gm-Message-State: AOAM530NIGuIQKxZ5Fbkn5pRQyV2Y2fYFfAhupcou2hzNyof6V0txxk6 1bBMw0o4ZElb6mAi1LtN1A+6dFdBN7gwoA==
X-Google-Smtp-Source: ABdhPJyQHgfBwOuxZe4jKbPW8Bh6p+5oyRfIuZ01yS2OUqW5IGG4LU5OzH1m8zljmYNdkq6n40Doew==
X-Received: by 2002:a05:6e02:1545:: with SMTP id j5mr4392513ilu.168.1609943817372;  Wed, 06 Jan 2021 06:36:57 -0800 (PST)
Received: from mithrandir.lan (c-24-91-177-160.hsd1.nh.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id k5sm1674989ioa.27.2021.01.06.06.36.56 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Jan 2021 06:36:56 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <C56C1843-ABE3-475A-B006-10879E29309F@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_ACEB3287-069E-4D89-A7CE-9505EF43AFB7"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.2\))
Date: Wed, 6 Jan 2021 09:36:54 -0500
In-Reply-To: <684e3296-a9d9-c899-9964-d80d693c1971@si6networks.com>
Cc: David Farmer <farmer=40umn.edu@dmarc.ietf.org>, IPv6 Operations <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
To: Fernando Gont <fgont@si6networks.com>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAN-Dau344H7xgD0Q_O54c=R08zFRFjToO8BHt=ssauxgEH7ynA@mail.gmail.com> <EFF2CF9D-147B-4E7F-9080-633A24FDA666@fugue.com> <684e3296-a9d9-c899-9964-d80d693c1971@si6networks.com>
X-Mailer: Apple Mail (2.3654.60.0.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/fcxwTzuoiQ3TNenf4vLQ6VUCuOs>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 14:37:00 -0000

--Apple-Mail=_ACEB3287-069E-4D89-A7CE-9505EF43AFB7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Jan 6, 2021, at 9:04 AM, Fernando Gont <fgont@si6networks.com> wrote:
> If not "local" or "explicit", maybe one of the others suggestions =
above would work?

=E2=80=9Cprivate=E2=80=9D isn=E2=80=99t bad.


--Apple-Mail=_ACEB3287-069E-4D89-A7CE-9505EF43AFB7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">On =
Jan 6, 2021, at 9:04 AM, Fernando Gont &lt;<a =
href=3D"mailto:fgont@si6networks.com" =
class=3D"">fgont@si6networks.com</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"caret-color: =
rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">If not "local" or "explicit", maybe one of the others =
suggestions above would work?</span><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Menlo-Regular; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""></div></blockquote></div><br =
class=3D""><div class=3D"">=E2=80=9Cprivate=E2=80=9D isn=E2=80=99t =
bad.</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_ACEB3287-069E-4D89-A7CE-9505EF43AFB7--


From nobody Wed Jan  6 07:30:04 2021
Return-Path: <richard@helix.net.nz>
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 B0B533A0EBE for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 07:30:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=helix-net-nz.20150623.gappssmtp.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 gcufr-325IPY for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 07:30:00 -0800 (PST)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C14D53A0EA4 for <v6ops@ietf.org>; Wed,  6 Jan 2021 07:30:00 -0800 (PST)
Received: by mail-io1-xd32.google.com with SMTP id i18so3115897ioa.1 for <v6ops@ietf.org>; Wed, 06 Jan 2021 07:30:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=helix-net-nz.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=O7L9LgvfK4hgI5B/LXK8N1uy/dWphdiXI5FDOydoy04=; b=OrlGgfBIWTreWb9phjW2WEFAH8BthF/m3q4GZOu6sSj1qLbEbQGSPEa86IFny7q5pn 7A330dkL7wPNwM/ofDBrvxA4UPehCP0PklTQZUzrvVsDeR7fhpIAow+KUKaq1wbEwqwH Go+4j/fAJUga24LQi8QhmD0kKx9Toq27jFgKIGdjUuzgvzGobkO16Hj/qPWUNc7xyR9C +utRSvgEhNcQIcMSAz5yrB+eSY9ugCFRmDW+C9ZOSQSl1ADQIiI+AOQCwb4HPB44hPHI XZ4wS+f1/eVJfynWaM+6iI17RhfID1QjUJz98V0A11jxz+tGiN5KUEz/gAHY4X3lE4xK 6Dxg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=O7L9LgvfK4hgI5B/LXK8N1uy/dWphdiXI5FDOydoy04=; b=hqhnkmfwgqN41sQ/tTZA21Yl1zxfIobvzcAr/6xy9iMHCYzNVLLLFbfe2K6oYZB/Fa QE+1bhuEKAizovXNdRsfgz69ay0LBs0oOc+LwvSwEQAl15y5YgOIzc9dN16jYk+uu86u 3jH2i7C5CRxPXkB81BPMEhH5WMbfW9MRUM4EfzgE9tB2Ociqz9bfTYf/ajuo3IuFm/NO OmFa6sKzA8DXyf52wxWd2to8I9wqWATrUjLPVWuuAndavGVcDB6lOKJOHNBR3L6SM/PJ smYikIhT+2nNovNLgW6rENxeOq5vpnPHldz8QEh96jDbV0RIAznH6pYqv+Jx48wEJwnK cpvg==
X-Gm-Message-State: AOAM532YPn23RyfGpd3xU+1aAOR2OYyTzm5ywuJMrigqRYE5l+FmgQSo ZKqz7b0mqLMvDYEPX+h+s9Q4AQ==
X-Google-Smtp-Source: ABdhPJw10KMDlSVnigRnEPGKbTVZC0oDFX2T6VN1zCLrd4/58k0zz0sOC3V+kvnJRBG/pmjOtjCr/A==
X-Received: by 2002:a02:3541:: with SMTP id y1mr4044875jae.66.1609946999621; Wed, 06 Jan 2021 07:29:59 -0800 (PST)
Received: from mail-io1-f51.google.com (mail-io1-f51.google.com. [209.85.166.51]) by smtp.gmail.com with ESMTPSA id a15sm2286379ilh.10.2021.01.06.07.29.58 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 06 Jan 2021 07:29:59 -0800 (PST)
Received: by mail-io1-f51.google.com with SMTP id d9so3090202iob.6; Wed, 06 Jan 2021 07:29:58 -0800 (PST)
X-Received: by 2002:a05:6638:2243:: with SMTP id m3mr4107610jas.115.1609946998679;  Wed, 06 Jan 2021 07:29:58 -0800 (PST)
MIME-Version: 1.0
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net>
In-Reply-To: <m1kxAVC-0000KhC@stereo.hq.phicoh.net>
From: Richard Patterson <richard@helix.net.nz>
Date: Wed, 6 Jan 2021 15:29:47 +0000
X-Gmail-Original-Message-ID: <CAHL_VyD85e9=taY1XENf7hc=BXRyD_7JJFDCW2Oq_a0z3hYqUA@mail.gmail.com>
Message-ID: <CAHL_VyD85e9=taY1XENf7hc=BXRyD_7JJFDCW2Oq_a0z3hYqUA@mail.gmail.com>
To: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>
Cc: 6man WG <ipv6@ietf.org>, Fernando Gont <fgont@si6networks.com>,  IPv6 Operations <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f6af3405b83cfe1e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/-xLmBIwRTrF62gd2mtlgZ1OL0K8>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 15:30:03 -0000

--000000000000f6af3405b83cfe1e
Content-Type: text/plain; charset="UTF-8"

On Wed, 6 Jan 2021 at 15:14, Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>
wrote:

>
> Applications should not do widely different things if they encouter a ULA.
>
>
But they do.
Some OSes will see the presence of a ULA address on an interface, and start
sending AAAA queries, some will not.
Some applications will see a ULA destination address and simply ignore it,
preferring the IPv4 destination address returned.

We need to ask the question why this is happening, and if the answer is
"They're doing it wrong", great, let's point them at the existing RFCs and
educate them, but if not...... we need to do something, and I think this
I-D is a good starting point for WG discussion at least.


We have policy tables for source and destination address selection. Those
> should be used to decide what to do.


As above, it's not just about simple routing table lookups, or source
address selection. But I do also think there's room for improvement here as
well, with a new scope for ULA.

--000000000000f6af3405b83cfe1e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Wed, 6 Jan 2021 at 15:14, Philip Hombu=
rg &lt;<a href=3D"mailto:pch-ipv6-ietf-7@u-1.phicoh.com">pch-ipv6-ietf-7@u-=
1.phicoh.com</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex"><br>
Applications should not do widely different things if they encouter a ULA.<=
br><br></blockquote><div><br></div><div>But they do.</div><div>Some OSes wi=
ll see the presence of a ULA address on an interface, and start sending AAA=
A queries, some will not.</div><div>Some applications will see a ULA destin=
ation address and simply ignore it, preferring the IPv4 destination address=
 returned.=C2=A0</div><div><br></div><div>We need to ask the question why t=
his is happening, and if the answer is &quot;They&#39;re doing it wrong&quo=
t;, great, let&#39;s point them at the existing RFCs and educate them, but =
if not...... we need to do something, and I think this I-D is a good starti=
ng=C2=A0point for WG discussion at least.<br></div><div><br></div><div><br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex">We have policy tabl=
es for source and destination address selection. Those<br>should be used to=
 decide what to do.</blockquote><div><br></div><div>As above, it&#39;s not =
just about simple routing=C2=A0table lookups, or source address selection. =
But I do also think there&#39;s room for improvement here as well, with a n=
ew=C2=A0scope for ULA.</div><div><br></div><div></div><div><br></div></div>=
</div>

--000000000000f6af3405b83cfe1e--


From nobody Wed Jan  6 07:42:44 2021
Return-Path: <fgont@si6networks.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 A6EE43A0F01; Wed,  6 Jan 2021 07:42:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.161
X-Spam-Level: 
X-Spam-Status: No, score=-2.161 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, 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 rPzbZjXLLcte; Wed,  6 Jan 2021 07:42:39 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93D903A0FF3; Wed,  6 Jan 2021 07:42:36 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 186EA283833; Wed,  6 Jan 2021 15:42:32 +0000 (UTC)
To: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, ipv6@ietf.org
Cc: IPv6 Operations <v6ops@ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <c236e635-518b-fb51-5024-901ec4677c5d@si6networks.com>
Date: Wed, 6 Jan 2021 12:42:13 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <m1kxAVC-0000KhC@stereo.hq.phicoh.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/PmI0onLU3NvAwtOyHwZXNJ43-jo>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 15:42:43 -0000

On 6/1/21 12:13, Philip Homburg wrote:
>>> In my opinion we should leave scope the way it is.
>>
>> The current definition of global scope as per RFC4007 doesn't match the
>> definition of ULAs as being global scope. Both of them can't be right.
> 
> Some things don't need fixing even if they are not 100% correct.

There's an architecture document, and a spec that doesn't follow it.

That's a bug. I don't know if that means 45% correct or 95.4% correct. 
But it does mean that we have defined terms, and that we don't use them 
in a consistent manner.

If we expect people to read our specs, and make sense out of them, we 
have fix them if we find issues.

And, as noted, there are concrete implications:
RFC4007 says ULAs are non-global, RFC4193 says that ULAs are global, and 
a Python library says ULAs are non-global. I don't think we want that.



>> "scope" and "zone" are part of the architecture. So we have a IPv6
>> Scoped Addressing Architecture, and then a definition ULAs that doesn't
>> really comply with that definition.
> 
> Effectively we have only two scopes: link-local and 'other'. What we need to
> do is simply things, not create a bigger mess.
> 
> We don't need zone IDs that try to identify the scope of a ULA. All of this
> was part of attempts to define local addresses. It didn't work.
> 
> We need to redefine zone IDs as interface IDs and clean up a lot of that
> stuff.

You mean use interface IDs as zone IDs?



>> Changing the formal scope of ULAs does change the expectation when it
>> comes to their usage: i.e., ULAs are not expected to be globally unique.
>> They are just expected to have small chances of collision if you
>> connected a limited number of ULA-based networks.
> 
> Networks don't just connect by themselves. Networks admins who connect two
> networks are not going the read RFC 4007 and conclude from the definition of
> scope that is safe to connect the networks.

It must be clear what ULAs are, and what they are not. Part of that is 
acknowledging that their scope is not global.



[...]
>> Besides, this does have an impact on current libraries (such as Python's
>> ipaddress) and other libraries or macros that may have been defined for
>> other languages, or that may be defined in the future.
> 
> The IETF does not define APIs for Python libraries, so I don't see why we would
> need to change the scope of ULA to accomodate them.

You seem to be missing my original point:
The definition of ULAs as "global scope" contradicts the definition of 
"global scope" from RFC4007.

We don't need to change the scope of ULAs to accommodate them. We need 
to change the scope of ULAs such that we don't have specs that 
contradict with each other (consistency). Most likely, when we have 
that, we'll end up accommodating the Python library as a side effect.
They got it right, and we didn't.



> We could call ULA 'private' if that would help python devs. But they can just
> well call ULA 'private' without involving the IETF.

So.. from the pov of RFC4007 ULAs are non-global.
 From the pov of RFC4193 ULAs are global.

... and you don't mean to fix that, but still expect devolopers from 
multiple languages to get that right, and programmers to make sense out 
of the outcome?



>> This in turn probably affects the use such apps make of a list of
>> addresses, when more than one is available.
> 
> Applications should not do widely different things if they encouter a ULA.
> 
> We have policy tables for source and destination address selection. Those
> should be used to decide what to do.

That's a "one size fits all". There are valid reasons for which you 
mihgt *not* want to do that, (including using ULAs for services that are 
expected to be local-only, not binding temporary addresses to listening 
sockets, etc., etc., etc.)



>> The problem is that for ULAs to be marked as "non-global" (whatever we
>> call that), RFC4291 needs to be updated. Also, at least a part of
>> RFC4193 needs to be updated.
> 
> They don't need to be marked 'non-global'. Changing the scope of ULA serves
> no purpose.

So what we do here is specifying protocols, and you argue that fixing 
inconsistencies when specs have conflicting definitions and usages serve 
no purpose?

Me, that's the least I'd expect from us....


-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan  6 07:45:39 2021
Return-Path: <fgont@si6networks.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 784B43A0F01; Wed,  6 Jan 2021 07:45:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.161
X-Spam-Level: 
X-Spam-Status: No, score=-2.161 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, 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 AB0enQhHquVK; Wed,  6 Jan 2021 07:45:34 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 223163A0F02; Wed,  6 Jan 2021 07:45:33 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id B78BD283833; Wed,  6 Jan 2021 15:45:27 +0000 (UTC)
To: Richard Patterson <richard@helix.net.nz>, Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>
Cc: 6man WG <ipv6@ietf.org>, IPv6 Operations <v6ops@ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net> <CAHL_VyD85e9=taY1XENf7hc=BXRyD_7JJFDCW2Oq_a0z3hYqUA@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <bc29edad-b57b-bb53-141b-8f58c5ca2526@si6networks.com>
Date: Wed, 6 Jan 2021 12:45:18 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CAHL_VyD85e9=taY1XENf7hc=BXRyD_7JJFDCW2Oq_a0z3hYqUA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/mZ6vDPQA8Nhas4ImLagcTZ46uCc>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 15:45:38 -0000

On 6/1/21 12:29, Richard Patterson wrote:
> On Wed, 6 Jan 2021 at 15:14, Philip Homburg 
> <pch-ipv6-ietf-7@u-1.phicoh.com <mailto:pch-ipv6-ietf-7@u-1.phicoh.com>> 
> wrote:
> 
> 
>     Applications should not do widely different things if they encouter
>     a ULA.
> 
> 
> But they do.

And good for them that they do. The ones that don't are the ones that 
end up e.g. posting ULAs and link-locals on the public-facing DNS.

(I've had to do it myself when using dynamic DNS updates, for instance)

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan  6 07:57:01 2021
Return-Path: <gert@space.net>
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 6C7433A105C for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 07:56:50 -0800 (PST)
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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=space.net
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 MFLcUAe971Sd for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 07:56:47 -0800 (PST)
Received: from gatekeeper1-relay.space.net (gatekeeper1-relay.space.net [IPv6:2001:608:3:85::38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C93DE3A0FDA for <v6ops@ietf.org>; Wed,  6 Jan 2021 07:56:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=space.net; i=@space.net; q=dns/txt; s=esa; t=1609948606; x=1641484606; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=tPRDX7gtq+Z2TcN2QbW8MiDW495QusQdssI4UBiHxNk=; b=WUZCu/c9eaYLm9z0Z7l2pz1IJfVffKUkZkdRHuyJ+3ejKmJAgc33fWlM vN8t/dOkcBs5NIFDq4xlmB1YKmzNDgcqZwfRNAK+CSlDlayyiGt07ofmR 2zTUCSep/3sDimT6tRg35Y9Yy//cb0Ay28BzbcliH5z/dXzzu0kPJECCK j4PRJaDswa+IVDECBE5IAnGFWVkDZcp2Zcw4gdf1uzyPGefl77sn2jzBv XdkErdB/H+lqhYICQu4WArwYjvcfAOq36My3R6n7S6TtbK14J1S7ECIMJ MoGy9VIKuevKkBnUngavnB53Ftx21y+SgU53wdb4SHnOlITOm0boCoTeT A==;
IronPort-SDR: kobeYs+uH4ugwEp0mhhAQTyhkqYmuiE1HGfg+Bqlk1Uxpyan9WmL/8X3OpPZ0HoyL8DkWsdApq jmB5oN3u+A/qiIoKECnXsBNA+KaSAB0hW/eb1p7E/nWI/948otOXiTuHVXS3mhNKW4IQuJB+EE ZITFT/xjGT2caOVLptpSiN1zjfNXvB42biffvushm9gubbzIPEPNbrog4lQvWMsNURFWYnAtu5 SM1JUCyhQA0dE0E8NhigxM1/gm2zih143iF7AO7LeDXLJDXtGNXa/l0sa+KxMlgcLy+MGnGXWG JKM=
X-SpaceNet-SBRS: None
Received: from mobil.space.net ([195.30.115.67]) by gatekeeper1-relay.space.net with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Jan 2021 16:56:42 +0100
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id C668E43AD0 for <v6ops@ietf.org>; Wed,  6 Jan 2021 16:56:42 +0100 (CET)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 6E10A427F9; Wed,  6 Jan 2021 16:56:42 +0100 (CET)
Received: by moebius4.space.net (Postfix, from userid 1007) id 6D65DDB2A; Wed,  6 Jan 2021 16:56:42 +0100 (CET)
Date: Wed, 6 Jan 2021 16:56:42 +0100
From: Gert Doering <gert@space.net>
To: Ted Lemon <mellon@fugue.com>
Cc: David Farmer <farmer=40umn.edu@dmarc.ietf.org>, Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Message-ID: <20210106155642.GW13005@Space.Net>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAN-Dau344H7xgD0Q_O54c=R08zFRFjToO8BHt=ssauxgEH7ynA@mail.gmail.com> <EFF2CF9D-147B-4E7F-9080-633A24FDA666@fugue.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <EFF2CF9D-147B-4E7F-9080-633A24FDA666@fugue.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/N7FZPahjK7dzcymjvp5hkjN62zA>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 15:56:56 -0000

Hi,

On Wed, Jan 06, 2021 at 07:17:33AM -0500, Ted Lemon wrote:
> On Jan 5, 2021, at 11:38 PM, David Farmer <farmer=40umn.edu@dmarc.ietf.org> wrote:
> > I think this is the right direction the previous draft indirectly defined a new scope "non-global", I much prefer explicitly defining a new local scope.
> 
> Actually, I think you???ve got it right here: the scope is ???non-global.???

Indeed.  This sounds like a nice way to express the intended usage.

"It is not link-local, but definitely not intended or usable for global
usage, thus: 'non-global scope'"

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279


From nobody Wed Jan  6 07:58:55 2021
Return-Path: <fernando@gont.com.ar>
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 AFE783A1262; Wed,  6 Jan 2021 07:58:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.161
X-Spam-Level: 
X-Spam-Status: No, score=-2.161 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, 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 caYxS2B-TAAU; Wed,  6 Jan 2021 07:58:43 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D031A3A1267; Wed,  6 Jan 2021 07:58:04 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 8089E2845F0; Wed,  6 Jan 2021 15:58:01 +0000 (UTC)
To: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, ipv6@ietf.org
Cc: IPv6 Operations <v6ops@ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net> <CAHL_VyD85e9=taY1XENf7hc=BXRyD_7JJFDCW2Oq_a0z3hYqUA@mail.gmail.com> <m1kxB6c-00007tC@stereo.hq.phicoh.net>
From: Fernando Gont <fernando@gont.com.ar>
Message-ID: <127fd75f-eead-ba5c-ca4f-d9608246c73b@gont.com.ar>
Date: Wed, 6 Jan 2021 12:57:21 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <m1kxB6c-00007tC@stereo.hq.phicoh.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/O9yPMmLnUEqAbUEpJ2Kb8xCDNcI>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 15:58:50 -0000

On 6/1/21 12:52, Philip Homburg wrote:
>> We need to ask the question why this is happening, and if the answer is
>> "They're doing it wrong", great, let's point them at the existing RFCs and
>> educate them, but if not...... we need to do something, and I think this
>> I-D is a good starting point for WG discussion at least.
> 
> This I-D doesn't seem to list anything that goes wrong in applications,
> let alone how applications are following the specs and getting it wrong.

Isn't it clear enough that the definition of ULAs as "global scope" 
contradicts the definition of global scope from RFC4007?

That, from starters, needs to be fixed.

Any library or macro that follows the definition of ULAs as being 
"global scope" will lead to ULAs leaking out of their zone, as e.g., 
posting them in the DNS. Because they are defined as "global scope", 
when they are not.


-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From nobody Wed Jan  6 08:09:32 2021
Return-Path: <fgont@si6networks.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 1C99B3A0F44; Wed,  6 Jan 2021 08:09:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.161
X-Spam-Level: 
X-Spam-Status: No, score=-2.161 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 wwwKb6JASzus; Wed,  6 Jan 2021 08:09:23 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A61973A10EB; Wed,  6 Jan 2021 08:09:15 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id CC83C2845F0; Wed,  6 Jan 2021 16:09:10 +0000 (UTC)
To: Gert Doering <gert@space.net>, Ted Lemon <mellon@fugue.com>
Cc: David Farmer <farmer=40umn.edu@dmarc.ietf.org>, IPv6 Operations <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAN-Dau344H7xgD0Q_O54c=R08zFRFjToO8BHt=ssauxgEH7ynA@mail.gmail.com> <EFF2CF9D-147B-4E7F-9080-633A24FDA666@fugue.com> <20210106155642.GW13005@Space.Net>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <49520404-ff67-ed9d-eb8e-c90491ae965e@si6networks.com>
Date: Wed, 6 Jan 2021 13:01:59 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <20210106155642.GW13005@Space.Net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/_vE_J2bWIlN4izRd4z6vv-N7ACc>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 16:09:27 -0000

On 6/1/21 12:56, Gert Doering wrote:
> Hi,
> 
> On Wed, Jan 06, 2021 at 07:17:33AM -0500, Ted Lemon wrote:
>> On Jan 5, 2021, at 11:38 PM, David Farmer <farmer=40umn.edu@dmarc.ietf.org> wrote:
>>> I think this is the right direction the previous draft indirectly defined a new scope "non-global", I much prefer explicitly defining a new local scope.
>>
>> Actually, I think you???ve got it right here: the scope is ???non-global.???
> 
> Indeed.  This sounds like a nice way to express the intended usage.
> 
> "It is not link-local, but definitely not intended or usable for global
> usage, thus: 'non-global scope'"

The only issue with using this term (non-global) is that it also applies 
to link-locals...


-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan  6 08:26:59 2021
Return-Path: <gert@space.net>
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 C738B3A0FC4 for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 08:26:57 -0800 (PST)
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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=space.net
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 O6kYx4zcKcXH for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 08:26:55 -0800 (PST)
Received: from gatekeeper1-relay.space.net (gatekeeper1-relay.space.net [IPv6:2001:608:3:85::38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D4B93A0FC2 for <v6ops@ietf.org>; Wed,  6 Jan 2021 08:26:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=space.net; i=@space.net; q=dns/txt; s=esa; t=1609950415; x=1641486415; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=ca8JMmgl+idm3kxJhO5x4N/rOegglqWBI+42lAtFmgE=; b=R1FBdNqpfvqDLKVYiPr0IUyRLEAuMf1iKliCzMdD5Ufc+WifOJGshYDx mV/dedyc3N4oKxLXYlTBXIvUvp31s8Dv+5QhCMEGk4wkwbYT1kFIrS/D5 hknTbcvLWjN5xKjaBvZZi77P1ouuFrvpOXfe3NemPsPPc+oSbDdMKAnKP l5KlRZa1Et4Z0N6LL+oq3VeMnrpc2VIPbFU4vhM4JpqdZoAMFevFbSQZK 3nvYGST+FRBQN/wAwSCWzibFXXopYKLhbxysqxuklnAMM9jbAW9y/5CX9 SMJg0ylXqUjDTSaTRS8hXGprZ9wnjNmp/SfbvI2k9E2/7niBlYP+QXyut Q==;
IronPort-SDR: TcVPQjj4Y5KNQjpzi5elUlkfZBNgH/BxtGuFCB/OuKxqwvuh9btDrT71bFWpmHtuCdP5jw81Qi 2X2/R5+i3KAusYJ4JXSZc2CGDN8AerYJbQz50kEKOZF5mrD0gnnz9m1g6i7NjCT8fuSEEGQVcV QWJRI3wGwx/zSXe82O6zEeJlpbMyn/7JdGMWQDnPXgn/BorLDm4YxyG/LHpHJPAuBpeVXeGamK crYkQ5c5lXM2VXsrLpGCfH0NReibzDnjgqf7o1tK+TzqxJjEF2imYREdUlfXqRSp2ZQgBEYOSq 5Z8=
X-SpaceNet-SBRS: None
Received: from mobil.space.net ([195.30.115.67]) by gatekeeper1-relay.space.net with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Jan 2021 17:26:52 +0100
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id C3E9043ACF for <v6ops@ietf.org>; Wed,  6 Jan 2021 17:26:52 +0100 (CET)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 8611943AC3; Wed,  6 Jan 2021 17:26:52 +0100 (CET)
Received: by moebius4.space.net (Postfix, from userid 1007) id 80A80E7EF; Wed,  6 Jan 2021 17:26:52 +0100 (CET)
Date: Wed, 6 Jan 2021 17:26:52 +0100
From: Gert Doering <gert@space.net>
To: Fernando Gont <fgont@si6networks.com>
Cc: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, ipv6@ietf.org, IPv6 Operations <v6ops@ietf.org>
Message-ID: <20210106162652.GX13005@Space.Net>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net> <c236e635-518b-fb51-5024-901ec4677c5d@si6networks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <c236e635-518b-fb51-5024-901ec4677c5d@si6networks.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/tWf-mYKppbiWI-jKVdNLxr6mRHM>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 16:26:58 -0000

HI,

On Wed, Jan 06, 2021 at 12:42:13PM -0300, Fernando Gont wrote:
> And, as noted, there are concrete implications:
> RFC4007 says ULAs are non-global, RFC4193 says that ULAs are global, and 
> a Python library says ULAs are non-global. I don't think we want that.

On a tangent, I wonder why this is relevant at all.

Why should applications, or anything that is not an admin, care if an
address is a ULA or a GUA?

(I can see the bit about "tools that enter GUAs in the global DNS",
but this is very special anyway - because "DNS" might not be "global",
so general "refuse to put ULA into DNS" is not correct behaviour either)


Consistent terminology is important, true, and if we just want to make
sure that something can properly flag a ULA different than a GUA, we
could just introduce

  "mid-range scoped"

or rename the scopes to be 0 (link-local), 5 (mid-range), 10 (global)...

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279


From nobody Wed Jan  6 08:51:59 2021
Return-Path: <fgont@si6networks.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 AF3273A0FE8; Wed,  6 Jan 2021 08:51:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.161
X-Spam-Level: 
X-Spam-Status: No, score=-2.161 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, 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 e8a5tmgnpUa6; Wed,  6 Jan 2021 08:51:50 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E25B03A0DDD; Wed,  6 Jan 2021 08:51:49 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 5EDC8284F56; Wed,  6 Jan 2021 16:51:45 +0000 (UTC)
To: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, ipv6@ietf.org
Cc: IPv6 Operations <v6ops@ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net> <c236e635-518b-fb51-5024-901ec4677c5d@si6networks.com> <m1kxBRZ-0000INC@stereo.hq.phicoh.net>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <1beb9c59-28ef-ac69-d5d3-7bfba0f70606@si6networks.com>
Date: Wed, 6 Jan 2021 13:36:10 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <m1kxBRZ-0000INC@stereo.hq.phicoh.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/tu-rd6NorRbqbEj5j9MO3KFFW5Y>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 16:51:53 -0000

On 6/1/21 13:13, Philip Homburg wrote:
>> And, as noted, there are concrete implications:
>> RFC4007 says ULAs are non-global, RFC4193 says that ULAs are global, and
>> a Python library says ULAs are non-global. I don't think we want that.
> 
> RFC 4007 does not mention ULA. 

RFC4007 defines what "scope" and "global scope" are.

RFC4193 defines ULAs to be global scope.

But ULAs (defined in RFC4193 as global scope) contradict the definition 
of global scope from RFC4007.

Hence the connection between the two.




>>> We need to redefine zone IDs as interface IDs and clean up a lot of that
>>> stuff.
>>
>> You mean use interface IDs as zone IDs?
> 
> No, rewrite RFC 4007 and get rid of zone IDs. And the introduce interface IDs
> to select the interface of an outgoing packet, whether link-local or global.

At the end of the day, when you do that, the interface is being employed 
as the zone ID.



>> It must be clear what ULAs are, and what they are not. Part of that is
>> acknowledging that their scope is not global.
> 
> ULAs are not link-local addressses. That's the only thing we need to know.

*That is not how they are specified in RFC4193*!



[...]
>> We don't need to change the scope of ULAs to accommodate them. We need
>> to change the scope of ULAs such that we don't have specs that
>> contradict with each other (consistency). Most likely, when we have
>> that, we'll end up accommodating the Python library as a side effect.
>> They got it right, and we didn't.
> 
> Like I said, the definition of global scope in RFC 4007 can be fixed if we
> would care enough.

It's the definition of ULAs as global scope that is incorrect. NOt the 
other way around.



>> ... and you don't mean to fix that, but still expect devolopers from
>> multiple languages to get that right, and programmers to make sense out
>> of the outcome?
> 
> Developers should not use scope to mean anything. Maybe some applications
> need to do something special when they encouter certain addresses. In that
> case they can directly list the prefixes that need special treatment.

Applications should deal with prefixes. If anything, they should deal 
with address properties.



> There is no need to come up with convoluted library schemes that try to
> classify addresses. That only causes operational nightmares.

You get operational nightmares when you get multi-scoped addresses and 
you have no clue about the differences and what to do with them.

Crawl Alexa's Top-1M sites, and look at the IPv6 addresses. You find 
anything from loopback, to unspecified address, to link-locals, and ULAs.




>>> We have policy tables for source and destination address selection. Those
>>> should be used to decide what to do.
>>
>> That's a "one size fits all". There are valid reasons for which you
>> mihgt *not* want to do that, (including using ULAs for services that are
>> expected to be local-only, not binding temporary addresses to listening
>> sockets, etc., etc., etc.)
> 
> Do you propose to introduce new scopes for temporary addresses?

Huh?

I'm saying:
"There are valid reasons for which you mihgt *not* want to do that, 
(including using ULAs for services that are expected to be local-only, 
not binding temporary addresses to listening sockets, etc., etc., etc.)"

that is: given a bunch of addresses with different properties, most 
likely applications do need to look at their properties to make 
appropriate use for them.

We're talking about the ULA scope being in contradiction with the 
"global scope definition".




> The I-D we are discussion doesn't describe these issues in the problem
> statement.

Problem #1:
The IETF publishes protocol specifications.
We have two protocol specifications that contradict each other.

Someone that reads both RFC4007 and RFC4193 will have an interesting WTH 
moments. For the rest of the stuff, I said it already. THere's no point 
in re-hashing the same arguments over and over again.



> Maybe you want to go back to the problem statement and describe what you
> really want to solve.

---- cut here ----
5.1.  Address Attributes in Programming Languages

    Python's ipaddress library [Python-ipaddr] defines 'IPv6Address'
    objects that have a number of attributes, including:

    o  'True' if the address is allocated for private networks.

    o  'True' if the address is allocated for public networks.

    For ULAs, the is_private attribute is 'True', while the is_global
    attribute is 'False'.  This contradicts the definition of ULAs as
    having "global scope" [RFC4291] [RFC4193], but is in line with the
    specification update performed by this document (see Section 6).
---- cut here ----

This will be faced by every other library or macro in every other language.


---- cut here ----
6.  Specification Updates

    The ultimate goal is to employ coherent terminology and definitions
    throughout the relevant protocol specifications.  Probably the only
    option to achieve this goal is update the definition of ULAs as
    having "local scope", with "local scope" defined as "larger than
    link-local, and smaller than global" (based on ULAs being defined as
    "local addresses").
---- cut here ----

The least we can aim at is consistency among our own specs, right?


... and one should also add to the list "a clarification of the 
expectations regarding ULAs. Because many (including myself in the very 
recent past) had the assumption that ULAs are globally-unique, when they 
are not.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan  6 08:52:06 2021
Return-Path: <fgont@si6networks.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 35C4F3A105E; Wed,  6 Jan 2021 08:51:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.16
X-Spam-Level: 
X-Spam-Status: No, score=-2.16 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, 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 1iWwMfJTDdwR; Wed,  6 Jan 2021 08:51:54 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB1893A0FE8; Wed,  6 Jan 2021 08:51:54 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 2841E284F56; Wed,  6 Jan 2021 16:51:50 +0000 (UTC)
To: Gert Doering <gert@space.net>
Cc: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, ipv6@ietf.org, IPv6 Operations <v6ops@ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net> <c236e635-518b-fb51-5024-901ec4677c5d@si6networks.com> <20210106162652.GX13005@Space.Net>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <1ddf8850-a8cb-53a7-31bc-7433d5a984f2@si6networks.com>
Date: Wed, 6 Jan 2021 13:46:51 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <20210106162652.GX13005@Space.Net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/RIvxU95MNStOk7-R6EX2ml4l-Ws>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 16:52:01 -0000

Hi, Gert,

On 6/1/21 13:26, Gert Doering wrote:
> HI,
> 
> On Wed, Jan 06, 2021 at 12:42:13PM -0300, Fernando Gont wrote:
>> And, as noted, there are concrete implications:
>> RFC4007 says ULAs are non-global, RFC4193 says that ULAs are global, and
>> a Python library says ULAs are non-global. I don't think we want that.
> 
> On a tangent, I wonder why this is relevant at all.
> 
> Why should applications, or anything that is not an admin, care if an
> address is a ULA or a GUA?

I can report on my own case:

I have Raspberry Pis that deploy here and there. In order to be able to 
access them, they use dynamic DNS to post their addresses on their DNS.
If I don't look at the properties of the addresses, then I end up puting 
crap on the DNS. One straightforward consequence is that many apps that 
don't do Happy Eyeballs end up having an insane connection-establishment 
period, if they happen to try the unusable addresses first.

So "find all your IPv6 addresses and post them to the DNS" doesn't work.




> (I can see the bit about "tools that enter GUAs in the global DNS",
> but this is very special anyway - because "DNS" might not be "global",
> so general "refuse to put ULA into DNS" is not correct behaviour either)

What I do is:
For each node, I have one domain name for global addresses, and another 
for non-globals.



> Consistent terminology is important, true, and if we just want to make
> sure that something can properly flag a ULA different than a GUA, we
> could just introduce
> 
>    "mid-range scoped"
> 
> or rename the scopes to be 0 (link-local), 5 (mid-range), 10 (global)...

Any of those options are totally fine. The point is that ULAs don't have 
the "global scope" properties described in RFC4007.

It is not acceptable to have folks that do their homework and read 
RFC4291/RFC4007, and then read other documents and are left scratching 
their heads.

If we can't fix specs when we have inconsistencies, I don't think we can 
expect people to make sense out of them.

-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan  6 09:06:46 2021
Return-Path: <mellon@fugue.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 41F293A1016 for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 09:06:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 fHVLLs1SbC7y for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 09:06:44 -0800 (PST)
Received: from mail-io1-xd33.google.com (mail-io1-xd33.google.com [IPv6:2607:f8b0:4864:20::d33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED1D73A1010 for <v6ops@ietf.org>; Wed,  6 Jan 2021 09:06:43 -0800 (PST)
Received: by mail-io1-xd33.google.com with SMTP id i18so3410331ioa.1 for <v6ops@ietf.org>; Wed, 06 Jan 2021 09:06:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=g3ZhDyVo/k42I6I/PMldshUEnV86D5MYCjlxBflZFOg=; b=OX8kEYr2tIktHcDv2DhyOCtBn0Ndl3jDaQWjWj+3/4BUxT83EFPP+c2UB4dr6gGAqq DlIX9kaGxhtbldkdYJMpsRUvXYAYQ00NRS2rd105Rdby8KN43X+nNTJdXdwLjdtMjtJc WJZp97kBBuF1rPa0POO8BeHVswEvwTfJOAa3YgclQQ4+vabFFmeDYdZZ7rbVGNxvAH7F aJYDjDjBzWc1MOzeyTI7BN6tcngX1/ParQaYol3SPsf43ZZ/yGY42O3noDWwCd/KCBrF TirYwU+Tqq72/TDj9PDczrXT5wStsLPfA2H7XNtBrMV15/elly/XNVOaZhIYCtZlIkc2 SUpw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=g3ZhDyVo/k42I6I/PMldshUEnV86D5MYCjlxBflZFOg=; b=hFpFi+MyO50+xYlQjuu2yTSCSy2h3r//K5qRHi1HHAwPWlvxQOhYF3BsieuLhONKtj yuLPUZgU1cI9cCjfx9ejWLNHUASkJbq0HHVuSEhn5LVZes9bhsYCQxkneWrtbv2OUytv GGr1KG1yhgHRnnEhBYBtGxfzW7gVpneCW9Vz1CDqLq0bhIfoa7fLPDCTuA+f2BToXl93 ENXNGEGjf5SbIIsZ6k9+Bdqp6A6n1Ugo8oI32YQpM107IhfAdiUipYiaYbnzbJf2Lgtq ZLh+oqK5tg07TfvZBxrScg3xXj7yqGpWesQvRVuKBGs3hi5Rg8pupyBsFHlvXG6P8Ehk dtrg==
X-Gm-Message-State: AOAM533yyGxEuBD9AtfWaDR+Fh8Vz9kfKJFoxJlvX601Kp6Fr5hyzUrH d6l0mM1IIMGgyBjtD4Az5wmdUQ==
X-Google-Smtp-Source: ABdhPJw6TcUNiaKcZaFq7wC7T4VUNmBJapk03H1FzkD0vbFFeE9ACmITw4Nc/BHFNMMB58AFy82cuw==
X-Received: by 2002:a02:b011:: with SMTP id p17mr4484495jah.55.1609952803332;  Wed, 06 Jan 2021 09:06:43 -0800 (PST)
Received: from mithrandir.lan (c-24-91-177-160.hsd1.ma.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id i6sm2249819ilm.70.2021.01.06.09.06.41 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Jan 2021 09:06:42 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <88297320-9516-4627-A673-FBFDA6A10B0C@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_BA223DAC-C9A6-4053-8D2A-5D3045ED3765"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.2\))
Date: Wed, 6 Jan 2021 12:06:39 -0500
In-Reply-To: <20210106162652.GX13005@Space.Net>
Cc: Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>, Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, ipv6@ietf.org
To: Gert Doering <gert@space.net>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net> <c236e635-518b-fb51-5024-901ec4677c5d@si6networks.com> <20210106162652.GX13005@Space.Net>
X-Mailer: Apple Mail (2.3654.60.0.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ULkIBJA9FWJYG8b_sDrf5AD72x4>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 17:06:45 -0000

--Apple-Mail=_BA223DAC-C9A6-4053-8D2A-5D3045ED3765
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Jan 6, 2021, at 11:26 AM, Gert Doering <gert@space.net> wrote:
> or rename the scopes to be 0 (link-local), 5 (mid-range), 10 =
(global)=E2=80=A6


This implies concentric circles, which isn=E2=80=99t really valid. =
Different ULAs can have disjoint or overlapping applicability. I agree =
with a previous comment that talking about this in terms of scope =
doesn=E2=80=99t make much sense. I don=E2=80=99t know how to write code =
that takes into account the difference in scope between ULA and GUA, =
other than perhaps in routing protocols.


--Apple-Mail=_BA223DAC-C9A6-4053-8D2A-5D3045ED3765
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">On =
Jan 6, 2021, at 11:26 AM, Gert Doering &lt;<a =
href=3D"mailto:gert@space.net" class=3D"">gert@space.net</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; =
font-size: 14px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">or rename the =
scopes to be 0 (link-local), 5 (mid-range), 10 =
(global)=E2=80=A6</span></div></blockquote></div><div class=3D""><br =
class=3D""></div>This implies concentric circles, which isn=E2=80=99t =
really valid. Different ULAs can have disjoint or overlapping =
applicability. I agree with a previous comment that talking about this =
in terms of scope doesn=E2=80=99t make much sense. I don=E2=80=99t know =
how to write code that takes into account the difference in scope =
between ULA and GUA, other than perhaps in routing protocols.<br =
class=3D""><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_BA223DAC-C9A6-4053-8D2A-5D3045ED3765--


From nobody Wed Jan  6 09:10:32 2021
Return-Path: <mellon@fugue.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 747763A1016 for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 09:10:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 uqRCv0PT8lrw for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 09:10:30 -0800 (PST)
Received: from mail-qv1-xf2d.google.com (mail-qv1-xf2d.google.com [IPv6:2607:f8b0:4864:20::f2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 098313A1014 for <v6ops@ietf.org>; Wed,  6 Jan 2021 09:10:29 -0800 (PST)
Received: by mail-qv1-xf2d.google.com with SMTP id d11so1499953qvo.11 for <v6ops@ietf.org>; Wed, 06 Jan 2021 09:10:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=yt0ZHOktr4ML5Bf/HT33ja6/SmubbXEHNR3xroi0C9I=; b=aHAqRW0AYIzhoCCN7rAUqyOILKC6TvSWWpOdGclj1XR7fInSpCy2YlrLM5e3DimzaK wpkxQXr2mFr8mx/xGqGbRL0flnufZvXfq+9DP4dwOE1PUxJZrv1YSqgbdAmsH7N0Z4gK 7wARfnQhiQmFNMjyR1xD0c3crDzoDg2DL0zYiChwXg7HoaSwLlIpw50RJ0J2GyuIHSjf WJpuT8hxhbRX0cEYphwSy5YGVtagbsJNZ8TrA1OP6giTAtA2oH6BfSNGpmym29/ETRUI EpcZ6BAYro9Wd6dDJJFMDZo25o3NP3tuDqcejg9nTYTZYnEmWA8wjVZmSQqRm13q876Q QvqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=yt0ZHOktr4ML5Bf/HT33ja6/SmubbXEHNR3xroi0C9I=; b=e48dVtG46/dWk24o6QhfeHioPtkIAQoT8iOupCKN/iUUDxjqkn/q5UPx0GAfztxMhr GxBepSYBitBRPieLZHHa1YG3S7N7vdr+5nTI4SJNoG9b5vlfGIDLkVg+9fccW36nGD3R VBJ2J8rdtLc0ujn2MwXGqBW6qqYe/Ivg4BuESVo9pAUbERRnOZEFSqKsYYcnjx5KdMhQ HjV71SKgo9KJ9BRX0ryonDhCQ4O20AJ6cDYhg4YcyNIGkx3T+cJ8r3Ckgt84UmZUHxJK nsRonPRiI391gNHKhpuPOv7gwaoJsI4wAA+n4xGcZI8/UeYMcoqVzZ/8IfqTEdG1wR8Q UOZg==
X-Gm-Message-State: AOAM530mNYG5QKXud4HIn9G4jmbW+Tx52Zq13o6bx/ievwAL4RT2/6q6 A+9WoLrcm68vPO3oPIsg4Uc/WQ==
X-Google-Smtp-Source: ABdhPJwfBN5Q4ugTr51+dHCH70g66tSA+6GVvO2bXXYDoDhL+XFGOOTMmn3vOBYs9E4NZfRHl0lVfA==
X-Received: by 2002:a05:6214:487:: with SMTP id ay7mr4705144qvb.37.1609953029088;  Wed, 06 Jan 2021 09:10:29 -0800 (PST)
Received: from mithrandir.lan (c-24-91-177-160.hsd1.ma.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id r22sm1607040qkk.67.2021.01.06.09.10.28 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Jan 2021 09:10:28 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <1089BC1B-A8E6-4BF5-BB3E-FD440181DB56@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_709B8E6A-B91B-489C-92F8-A4AD0698AE32"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.2\))
Date: Wed, 6 Jan 2021 12:10:26 -0500
In-Reply-To: <1ddf8850-a8cb-53a7-31bc-7433d5a984f2@si6networks.com>
Cc: Gert Doering <gert@space.net>, IPv6 Operations <v6ops@ietf.org>, Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, ipv6@ietf.org
To: Fernando Gont <fgont@si6networks.com>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net> <c236e635-518b-fb51-5024-901ec4677c5d@si6networks.com> <20210106162652.GX13005@Space.Net> <1ddf8850-a8cb-53a7-31bc-7433d5a984f2@si6networks.com>
X-Mailer: Apple Mail (2.3654.60.0.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/OJXT9TLfhb3jqHfWEAiwOHW6j-4>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 17:10:31 -0000

--Apple-Mail=_709B8E6A-B91B-489C-92F8-A4AD0698AE32
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Jan 6, 2021, at 11:46 AM, Fernando Gont <fgont@si6networks.com> =
wrote:
> I have Raspberry Pis that deploy here and there. In order to be able =
to access them, they use dynamic DNS to post their addresses on their =
DNS.
> If I don't look at the properties of the addresses, then I end up =
puting crap on the DNS. One straightforward consequence is that many =
apps that don't do Happy Eyeballs end up having an insane =
connection-establishment period, if they happen to try the unusable =
addresses first.
>=20
> So "find all your IPv6 addresses and post them to the DNS" doesn't =
work.

It is of course not even obvious how to solve this, because sometimes =
you do want ULA in DNS, and sometimes you don=E2=80=99t. And it depends =
on what DNS. If you are doing split DNS, then you can scope the DNS that =
advertises ULAs only to serve those networks where those ULAs are =
in-scope. The DNS that is advertised globally would of course contain no =
ULAs. How this is arranged is either a matter of local configuration or =
an interesting topic of future work, depending on how you look at it.


--Apple-Mail=_709B8E6A-B91B-489C-92F8-A4AD0698AE32
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">On =
Jan 6, 2021, at 11:46 AM, Fernando Gont &lt;<a =
href=3D"mailto:fgont@si6networks.com" =
class=3D"">fgont@si6networks.com</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"caret-color: =
rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">I have Raspberry Pis that deploy here and there. In order to =
be able to access them, they use dynamic DNS to post their addresses on =
their DNS.</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">If I don't =
look at the properties of the addresses, then I end up puting crap on =
the DNS. One straightforward consequence is that many apps that don't do =
Happy Eyeballs end up having an insane connection-establishment period, =
if they happen to try the unusable addresses first.</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; =
font-size: 14px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">So "find all =
your IPv6 addresses and post them to the DNS" doesn't =
work.</span></div></blockquote></div><br class=3D""><div class=3D"">It =
is of course not even obvious how to solve this, because sometimes you =
do want ULA in DNS, and sometimes you don=E2=80=99t. And it depends on =
what DNS. If you are doing split DNS, then you can scope the DNS that =
advertises ULAs only to serve those networks where those ULAs are =
in-scope. The DNS that is advertised globally would of course contain no =
ULAs. How this is arranged is either a matter of local configuration or =
an interesting topic of future work, depending on how you look at =
it.</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_709B8E6A-B91B-489C-92F8-A4AD0698AE32--


From nobody Wed Jan  6 09:12:01 2021
Return-Path: <mcr+ietf@sandelman.ca>
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 901623A100F; Wed,  6 Jan 2021 09:11:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, 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 l1XyCEExApZz; Wed,  6 Jan 2021 09:11:54 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D80C3A11A8; Wed,  6 Jan 2021 09:11:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 61B12389AF; Wed,  6 Jan 2021 12:12:39 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id KEdkm-ER0ceQ; Wed,  6 Jan 2021 12:12:39 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id F08C6389AE; Wed,  6 Jan 2021 12:12:38 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 7705B240; Wed,  6 Jan 2021 12:11:32 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Fernando Gont <fgont@si6networks.com>
cc: Gert Doering <gert@space.net>, IPv6 Operations <v6ops@ietf.org>, ipv6@ietf.org
In-Reply-To: <1ddf8850-a8cb-53a7-31bc-7433d5a984f2@si6networks.com>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net> <c236e635-518b-fb51-5024-901ec4677c5d@si6networks.com> <20210106162652.GX13005@Space.Net> <1ddf8850-a8cb-53a7-31bc-7433d5a984f2@si6networks.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Wed, 06 Jan 2021 12:11:32 -0500
Message-ID: <1169.1609953092@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/O5jF11p9FjbOZ7YL1nIbmUSPWqs>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 17:11:57 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Fernando Gont <fgont@si6networks.com> wrote:
    > On 6/1/21 13:26, Gert Doering wrote:
    >> HI,
    >>
    >> On Wed, Jan 06, 2021 at 12:42:13PM -0300, Fernando Gont wrote:
    >>> And, as noted, there are concrete implications:
    >>> RFC4007 says ULAs are non-global, RFC4193 says that ULAs are global=
, and
    >>> a Python library says ULAs are non-global. I don't think we want th=
at.
    >>
    >> On a tangent, I wonder why this is relevant at all.
    >>
    >> Why should applications, or anything that is not an admin, care if an
    >> address is a ULA or a GUA?

    > I can report on my own case:

    > I have Raspberry Pis that deploy here and there. In order to be able =
to
    > access them, they use dynamic DNS to post their addresses on their DN=
S.
    > If I don't look at the properties of the addresses, then I end up put=
ing crap
    > on the DNS. One straightforward consequence is that many apps that do=
n't do
    > Happy Eyeballs end up having an insane connection-establishment perio=
d, if
    > they happen to try the unusable addresses first.

    > So "find all your IPv6 addresses and post them to the DNS" doesn't wo=
rk.

And, yet, for the case where some device is doing dynamic DNS update to a D=
NS
server that is within some ULA scope, posting the ULA to the DNS is actually
correct.
But, it's hard to know that without knowing what clients are expected to co=
nnect.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide





--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl/170QACgkQgItw+93Q
3WX1Hwf+P4UUyzktb1Z1VEOErPH0H7cGHcq3bIYXcN6+3+paw2fGIui4tD6RIeDt
2fIU+bfW5djoS6SPGnx3BJ6RnbRlifexrxNFs+6cZdrG/f5DcOk78rfAvx7YUWEr
jDOJcUa+yFuhFb+aTLqiWNZAehZaTVfiP6ond8M16zNdg/cU8o1IoxKfZR33lt0C
TFEqxkYcUjFSQL9FFRot1Pebx+MS+LRDg5nzGHByqxWswNcT/1zx+RKY563aT5gL
2M2ekeU3OCccK6aujSMIsSKkV+XWIQoZcGLOmMYNBLUBgAFn+h73A47Pethv4iYG
62i7kSVuMjypJbloH0kXHFDjdptFZA==
=N3el
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Jan  6 09:21:03 2021
Return-Path: <mellon@fugue.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 B495A3A103F for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 09:21:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 TkYdb2Nap-QU for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 09:20:59 -0800 (PST)
Received: from mail-qk1-x732.google.com (mail-qk1-x732.google.com [IPv6:2607:f8b0:4864:20::732]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C8A43A103D for <v6ops@ietf.org>; Wed,  6 Jan 2021 09:20:59 -0800 (PST)
Received: by mail-qk1-x732.google.com with SMTP id w79so3101820qkb.5 for <v6ops@ietf.org>; Wed, 06 Jan 2021 09:20:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=hVhd3Mrd/3yE9Sf4MQ+Yg3zxjyIot/MsStZtU4gZcmc=; b=j2Ab9R1ZE/UdQMQMmz+256www/3e9BX0lr6wUXWj2NVAE8r3QRQ9LE/dXEqcad4X+X N86SY+4S20RpaaoK1G/79MDueObyXb45eVMWfsIj0BuGlGmln3H9/fM+hpO1Qkl86brq BrGSl8jz6VHqTLoyRi5VsqFIxuIvmUotsQ1p7VkURMpc7ygAh5/Y5ORiWd2EWibVDEPe vll4lmA9bgSFbuQZ7qBmnyhAfsJO1MpkllRmKkJzvHezkNEtnZ4swzBUWcb/PnaFGvB5 uWMOhHT3fMQ5TlCtON24/o2KBKLWdorZrkAxcehpFDQCf2FZDY4x4hKLgd3a6mVy9oMD axFA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=hVhd3Mrd/3yE9Sf4MQ+Yg3zxjyIot/MsStZtU4gZcmc=; b=RCccGl3hiUkwAc5TCvqqVqY4Jap6SmtB+sF/JWyQYQWRmvcdAfmpDQKKDXFXTYvbmI gnIPo9cB61PYmagt4Cqa6r5AjNwYUyXd1oGpQC2af/eXsjQFNCII1LfJ39s/X0yh9FNh 1swRJzV5VlqGNL16zrsFgy6Z0vpPQ0KRSC+w5reILReDNbX+l5t1c3iEM9HNItb5nOHq skrPugV9G/CJz5cX/XIdyVm1cq6loETvMiqs5u+NxvkYa2bbJzkQWyZohgDRUKOzXKfW thQnN7K16AWJW3+K69/Du6xK1lcqphrIsLEXO73eaA0NhixtH80FICKy0D1o2LBTuupb JfEw==
X-Gm-Message-State: AOAM531iWNLXaFBZOdbyLPBZZ8vsnt3x1T54/gBtUpqSak6KvvJ+/Snd mZGh5iA9HwOf/Y1juRDVwl5Y/Wda8SW+Mw==
X-Google-Smtp-Source: ABdhPJy/inGdaceZXDRkkj+2dMwblA7gSIz4BtbfDAyJvmWlbHsOrRDQzDk9mQ7IINPqR8DyWNnTsQ==
X-Received: by 2002:a37:642:: with SMTP id 63mr5308505qkg.123.1609953658182; Wed, 06 Jan 2021 09:20:58 -0800 (PST)
Received: from mithrandir.lan (c-24-91-177-160.hsd1.ma.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id c136sm1700371qkg.71.2021.01.06.09.20.57 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Jan 2021 09:20:57 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <FA6275FF-E148-46DC-BCFD-987315765873@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A28683EA-943E-4F3B-BAD2-FAC9C11F86EE"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.2\))
Date: Wed, 6 Jan 2021 12:20:54 -0500
In-Reply-To: <1169.1609953092@localhost>
Cc: Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>, ipv6@ietf.org, Gert Doering <gert@space.net>
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net> <c236e635-518b-fb51-5024-901ec4677c5d@si6networks.com> <20210106162652.GX13005@Space.Net> <1ddf8850-a8cb-53a7-31bc-7433d5a984f2@si6networks.com> <1169.1609953092@localhost>
X-Mailer: Apple Mail (2.3654.60.0.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/9gMeAV6TI-Ho4Z-0t1Uynito3NE>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 17:21:01 -0000

--Apple-Mail=_A28683EA-943E-4F3B-BAD2-FAC9C11F86EE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jan 6, 2021, at 12:11 PM, Michael Richardson <mcr+ietf@sandelman.ca> =
wrote:
> And, yet, for the case where some device is doing dynamic DNS update =
to a DNS
> server that is within some ULA scope, posting the ULA to the DNS is =
actually
> correct.
> But, it's hard to know that without knowing what clients are expected =
to connect.

It seems straightforward that the client should send all the addresses =
it wants to advertise, and the DNS server should decide which ones to =
advertise in what scopes.


--Apple-Mail=_A28683EA-943E-4F3B-BAD2-FAC9C11F86EE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">On =
Jan 6, 2021, at 12:11 PM, Michael Richardson &lt;<a =
href=3D"mailto:mcr+ietf@sandelman.ca" =
class=3D"">mcr+ietf@sandelman.ca</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"caret-color: =
rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">And, yet, for the case where some device is doing dynamic DNS =
update to a DNS</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Menlo-Regular; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Menlo-Regular; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">server that is within some ULA scope, posting the ULA to the =
DNS is actually</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Menlo-Regular; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Menlo-Regular; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">correct.</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Menlo-Regular; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Menlo-Regular; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">But, it's hard to know that without knowing what clients are =
expected to connect.</span></div></blockquote></div><br class=3D""><div =
class=3D"">It seems straightforward that the client should send all the =
addresses it wants to advertise, and the DNS server should decide which =
ones to advertise in what scopes.</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_A28683EA-943E-4F3B-BAD2-FAC9C11F86EE--


From nobody Wed Jan  6 09:29:23 2021
Return-Path: <fgont@si6networks.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 810A43A1049; Wed,  6 Jan 2021 09:29:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.161
X-Spam-Level: 
X-Spam-Status: No, score=-2.161 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, 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 hKbDBDPRtvRy; Wed,  6 Jan 2021 09:29:16 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F2213A0FFD; Wed,  6 Jan 2021 09:29:15 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 117482839E5; Wed,  6 Jan 2021 17:29:10 +0000 (UTC)
To: Ted Lemon <mellon@fugue.com>, Gert Doering <gert@space.net>
Cc: IPv6 Operations <v6ops@ietf.org>, Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, ipv6@ietf.org
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net> <c236e635-518b-fb51-5024-901ec4677c5d@si6networks.com> <20210106162652.GX13005@Space.Net> <88297320-9516-4627-A673-FBFDA6A10B0C@fugue.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <035a725a-19bf-efae-bf13-15e8dae4cc97@si6networks.com>
Date: Wed, 6 Jan 2021 14:26:56 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <88297320-9516-4627-A673-FBFDA6A10B0C@fugue.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/HIb0ZZygjfGZfNcWTQpyr_FONrw>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 17:29:19 -0000

On 6/1/21 14:06, Ted Lemon wrote:
> On Jan 6, 2021, at 11:26 AM, Gert Doering <gert@space.net 
> <mailto:gert@space.net>> wrote:
>> or rename the scopes to be 0 (link-local), 5 (mid-range), 10 (global)…
> 
> This implies concentric circles, which isn’t really valid. Different 
> ULAs can have disjoint or overlapping applicability. I agree with a 
> previous comment that talking about this in terms of scope doesn’t make 
> much sense. I don’t know how to write code that takes into account the 
> difference in scope between ULA and GUA, other than perhaps in routing 
> protocols.

e.g., for thinks like mDNS, you'd only bind() and listen on your ULAs, 
if any.


-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan  6 09:33:07 2021
Return-Path: <mellon@fugue.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 965193A106F for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 09:33:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 VhBlYgMKoomo for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 09:33:04 -0800 (PST)
Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0ED293A1062 for <v6ops@ietf.org>; Wed,  6 Jan 2021 09:33:03 -0800 (PST)
Received: by mail-qk1-x72a.google.com with SMTP id p14so3132670qke.6 for <v6ops@ietf.org>; Wed, 06 Jan 2021 09:33:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=M6VBounNQZWk7Kr83wg0AHKe8/bRAnAILERIUROwyDc=; b=byFRFHrHBcxfFZJ6XGMhA/Zx++sf1XXyAPJ21/3/77tk3OfbBs3or/bE4WSxwGRAi/ ZOa+Uc3AdIZy3uOPDNydqu4Y+YEovwsjdHZQYzPzfBr7dw1653MSC/WfEBohv/Lk7dru UuerMXfvsLDwsFXIcBNQ9TRD5faPy6sVCvtpxuYHnTvH43uOFj0Iuehw03YdrtiUEVHD JkavVi63eVIqaR9MqJfBq3gbPgM/pj31/qnLuRGdN5tucQ0LAJus1uhuS4MoDNJ7LDeP BO4U3QkOzkA80mMAnFeOs5O5kdjTKL5Meh0QbsOfTWxTkjlkj8RSNrCMKsVp/I2Dp5v0 BsTA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=M6VBounNQZWk7Kr83wg0AHKe8/bRAnAILERIUROwyDc=; b=sOXgKmL19/1ju01Nbb+QGM0sJK5k3Fnbh7y4KF1gbktOXNW+Rjtl2Ilm4Lim6Iy6WO WAlh2CDFLEqASGrpbUGTPrDizcjb15sMrScM1aS6ej7Ofj5CekSmNoCoxsjO8HMe1sAZ UDS07Y1XuL6Nwy9HxV/NsHH7ZW9Bv8BABhmkKaptZj7QsTGMicuDAe4kHME3wchNwwUf pwj0XK7hthwq/sfL2PZjCYeKFl1mpO06tRlard+jDtoSO326LhRhKCHrbha4w6UARNyh MGBUXfnSXyivUFEFt/sk3qynLB+hnVM6D6xKWOlR4QAuMWPQwq/TJF8D9zqu0rji5M6G ZyjA==
X-Gm-Message-State: AOAM530kSKND/EQ0rlCVzYjx+BJvoyVah2Hz3hvPRl5EcVDTWTXzsZn0 CZ3y3r5mBt4P0+FUZ/3kfhMjUw==
X-Google-Smtp-Source: ABdhPJwinEpfM5OkcDadF+Nabzqk3QWs/H3zBBcTXLazcUQHiLKTDLdliVPYa6TP3smX0VEfZ1wATA==
X-Received: by 2002:a37:4ecd:: with SMTP id c196mr5339208qkb.264.1609954382938;  Wed, 06 Jan 2021 09:33:02 -0800 (PST)
Received: from mithrandir.lan (c-24-91-177-160.hsd1.nh.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id x47sm1422398qtb.86.2021.01.06.09.33.02 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Jan 2021 09:33:02 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <184A442D-53F0-4B21-B094-779A1F66AD39@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_53341688-AB71-480F-88E9-B6A66985680D"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.2\))
Date: Wed, 6 Jan 2021 12:33:00 -0500
In-Reply-To: <035a725a-19bf-efae-bf13-15e8dae4cc97@si6networks.com>
Cc: Gert Doering <gert@space.net>, IPv6 Operations <v6ops@ietf.org>, Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, ipv6@ietf.org
To: Fernando Gont <fgont@si6networks.com>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net> <c236e635-518b-fb51-5024-901ec4677c5d@si6networks.com> <20210106162652.GX13005@Space.Net> <88297320-9516-4627-A673-FBFDA6A10B0C@fugue.com> <035a725a-19bf-efae-bf13-15e8dae4cc97@si6networks.com>
X-Mailer: Apple Mail (2.3654.60.0.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/d-PcFFyabcNXQwbVE4VhC4JWr14>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 17:33:06 -0000

--Apple-Mail=_53341688-AB71-480F-88E9-B6A66985680D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jan 6, 2021, at 12:26 PM, Fernando Gont <fgont@si6networks.com> =
wrote:
> e.g., for thinks like mDNS, you'd only bind() and listen on your ULAs, =
if any.

mDNS is link-local, so you can actually use your LLA for that (and we =
do). But e.g. if you are using SRP =
(https://tools.ietf.org/html/draft-ietf-dnssd-srp-07), then it makes =
sense to push your GUA and your ULA and bind to both, or to INADDR_ANY =
(if you want to be globally reachable). I would expect the SRP server to =
do the work of figuring out on which DNS server to publish the ULA and =
on which to publish the GUA.


--Apple-Mail=_53341688-AB71-480F-88E9-B6A66985680D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">On =
Jan 6, 2021, at 12:26 PM, Fernando Gont &lt;<a =
href=3D"mailto:fgont@si6networks.com" =
class=3D"">fgont@si6networks.com</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"caret-color: =
rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">e.g., for thinks like mDNS, you'd only bind() and listen on =
your ULAs, if any.</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Menlo-Regular; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""></div></blockquote></div><br =
class=3D""><div class=3D"">mDNS is link-local, so you can actually use =
your LLA for that (and we do). But e.g. if you are using SRP (<a =
href=3D"https://tools.ietf.org/html/draft-ietf-dnssd-srp-07" =
class=3D"">https://tools.ietf.org/html/draft-ietf-dnssd-srp-07</a>), =
then it makes sense to push your GUA and your ULA and bind to both, or =
to INADDR_ANY (if you want to be globally reachable). I would expect the =
SRP server to do the work of figuring out on which DNS server to publish =
the ULA and on which to publish the GUA.</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_53341688-AB71-480F-88E9-B6A66985680D--


From nobody Wed Jan  6 09:48:57 2021
Return-Path: <mcr+ietf@sandelman.ca>
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 1DA253A108E; Wed,  6 Jan 2021 09:48:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, 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 NEy4LoReysU6; Wed,  6 Jan 2021 09:48:54 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6E293A107E; Wed,  6 Jan 2021 09:48:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 9EFC9389A8; Wed,  6 Jan 2021 12:49:58 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id HyHH_lKGjd31; Wed,  6 Jan 2021 12:49:58 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 35C88389A7; Wed,  6 Jan 2021 12:49:58 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 97603240; Wed,  6 Jan 2021 12:48:51 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ted Lemon <mellon@fugue.com>
cc: Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>, ipv6@ietf.org, Gert Doering <gert@space.net>
In-Reply-To: <1089BC1B-A8E6-4BF5-BB3E-FD440181DB56@fugue.com>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net> <c236e635-518b-fb51-5024-901ec4677c5d@si6networks.com> <20210106162652.GX13005@Space.Net> <1ddf8850-a8cb-53a7-31bc-7433d5a984f2@si6networks.com> <1089BC1B-A8E6-4BF5-BB3E-FD440181DB56@fugue.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Wed, 06 Jan 2021 12:48:51 -0500
Message-ID: <12491.1609955331@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/P2_OdaitPNcIaXYTVPTYrGbnEhI>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 17:48:56 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Ted Lemon <mellon@fugue.com> wrote:
    > It is of course not even obvious how to solve this, because sometimes
    > you do want ULA in DNS, and sometimes you don=E2=80=99t. And it depen=
ds on what
    > DNS.
    > If you are doing split DNS, then you can scope the DNS that
    > advertises ULAs only to serve those networks where those ULAs are
    > in-scope.

Ideally.... but that's a lot of policy stuff to put into DNS.
I think that geolocated answers in DNS is already a bad thing.
We should be using a better anycast.

    > The DNS that is advertised globally would of course contain
    > no ULAs.

I'm not sure that I agree!  I think that ULAs often do belong.

There are potentially many GUA (2000::/3) addresses that could be in DNS,
which would not work for some originators due to ACLs, and yet a different
entry might work just fine.  Why would ULA be any different?

I think that happy eyeballs and source address selection ought to cut out
many possibilities.
It's just too bad that libcurl doesn't implement Happy Eyeballs...
     {ideally in a system-wide, privacy-preserving, maybe even LAN-wide
     [RFC2186-like] way}

(I also lament shim6, but feel that MPTCP and QUIC might give us something
equivalent.  Again... anycast)

    > How this is arranged is either a matter of local configuration
    > or an interesting topic of future work, depending on how you look at
    > it.

Also, is this an operational or architectural issue?

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide





--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl/1+AMACgkQgItw+93Q
3WW0Cwf/TdUl/zbPO8IZgOPJ/M9sgsVmqpcxtXjxlteQhNm1i3RSAdNGnY0yoF1k
QSK2TbsEWGz+3PIBjiTNLfu+KP/Qdz9agEXxvNbqaw6weChMxd4hcO1MOlBVfzCZ
ZPIGOoCnDhsoEVQh2bnKKLswyMuMyNHxuXOO94mjtAtvTyZT9eIOvmVQM/9eRB73
uz8jxuq5ukzjmywUO5jJp/yRXEro4b5R95AgdgsyWZSlYG0AamC+Z3M1fvf5FV3J
6dTLzNmwPYOJkK4QhjBW39rXWpNptd5o/JlnQgnPKeeeFOV1v8RNQmIsl4OIxgid
0fV8nHnO4GDvWtd5wpAl9EZtZsG5Rw==
=WJ7A
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Jan  6 09:51:18 2021
Return-Path: <mcr+ietf@sandelman.ca>
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 7A19F3A108E; Wed,  6 Jan 2021 09:51:16 -0800 (PST)
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, SPF_HELO_NONE=0.001, 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 bnTGYKDwE7TN; Wed,  6 Jan 2021 09:51:14 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCF8E3A106E; Wed,  6 Jan 2021 09:51:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id A6318389A3; Wed,  6 Jan 2021 12:52:19 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ZLaPCX_DohRe; Wed,  6 Jan 2021 12:52:17 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id B9BED389A0; Wed,  6 Jan 2021 12:52:17 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 259B0240; Wed,  6 Jan 2021 12:51:11 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ted Lemon <mellon@fugue.com>
cc: Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>, ipv6@ietf.org, Gert Doering <gert@space.net>
In-Reply-To: <FA6275FF-E148-46DC-BCFD-987315765873@fugue.com>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net> <c236e635-518b-fb51-5024-901ec4677c5d@si6networks.com> <20210106162652.GX13005@Space.Net> <1ddf8850-a8cb-53a7-31bc-7433d5a984f2@si6networks.com> <1169.1609953092@localhost> <FA6275FF-E148-46DC-BCFD-987315765873@fugue.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Wed, 06 Jan 2021 12:51:11 -0500
Message-ID: <13054.1609955471@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/YRyaxamjxlm0jlhODZAXtUQajM8>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 17:51:17 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Ted Lemon <mellon@fugue.com> wrote:
    > On Jan 6, 2021, at 12:11 PM, Michael Richardson <mcr+ietf@sandelman.c=
a> wrote:
    >> And, yet, for the case where some device is doing dynamic DNS update=
 to a DNS
    >> server that is within some ULA scope, posting the ULA to the DNS is =
actually
    >> correct.
    >> But, it's hard to know that without knowing what clients are expecte=
d to connect.

    > It seems straightforward that the client should send all the addresses
    > it wants to advertise, and the DNS server should decide which ones to
    > advertise in what scopes.

Ideally, yes.
If you ask from ULA xyz, and there is a ULA xyz answer, then clearly it
should be included.

But... caching and outsourcing of DNS servers and outsourcing of DNS resolv=
ers.
I hate all of that: except for simpler (IoT) devices, which should always u=
se
local DNS server to get local policy,  all this policy should be in the
client, not the server.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide





--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl/1+I4ACgkQgItw+93Q
3WV9IQf+JSn8ik56ogTeoUQlw6YPg3JjKK4nPlF/V1C/6KVzaoP1fjyKG9sS6dod
mT+Z6XgZ9Yb3ESDuLQI48m9anapX1Q9HVPq83FkmjP86y0sN9irCGyVAlQ4QVx/z
s7LAX7aPLI0awwz0dI+S4lY3WZUTsOWSz8OKsKxOtrj/+9EzmOkHJpz/NkZWAv1p
NK5nItV4R9IAsSMqEhuxQDDGNZWvzRLpiwhGwAnToKynoGNKgG3FxRvEuX7Usg1w
kBWDosrX+Zv00xSLOGudRWBh0s4IGZ3l0eivipoDuMycneBcxcTwkg6j9X7YbX1k
BzATNCcWzRqRCFKpZQ3+EH7XCMJLcg==
=+jQd
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Jan  6 10:04:46 2021
Return-Path: <mellon@fugue.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 E5C5B3A1093 for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 10:04:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 ioB6IGniGNde for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 10:04:35 -0800 (PST)
Received: from mail-qv1-xf2c.google.com (mail-qv1-xf2c.google.com [IPv6:2607:f8b0:4864:20::f2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE1D73A10DF for <v6ops@ietf.org>; Wed,  6 Jan 2021 10:04:34 -0800 (PST)
Received: by mail-qv1-xf2c.google.com with SMTP id h16so1599052qvu.8 for <v6ops@ietf.org>; Wed, 06 Jan 2021 10:04:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Ev2ewpUTRjo6okUM8t5+VYmznhPRQ2qdHAqyRUjQQ3o=; b=udUGF4n0DNj+VnKT8nt8zsmrU4za/D0djSo40ZfiQSkLuqmxG2HS5O9pHiKPsSK6E9 0ZqjhrUQf2MeUmTjCiDQ3kRVP9Ka9s3FbJTsv9UtgPH6Rfqcv7JTUbqBoOstSysrwgjS wCis8EiSNjAyO/i6+w4tLc7kDFChivjvYutqj/jQryfOkln8dZTxCMVA2dCdqLDes7aU Rr2O4gz+6KjSto3vIECewJ+gKIq5Hi6CFkxaD+yxR3LFDgwFSWhm5pBQxqpFT30GQbjW kKtx22d+rMcj3mXatGgLktqrgcPJZW1Co3SBbOirGwEKah8F/WY5kcjQZ1RrnHp3QpMK yMJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=Ev2ewpUTRjo6okUM8t5+VYmznhPRQ2qdHAqyRUjQQ3o=; b=ta6bAUiOk/LKo50oe8dLrh60legz1xE5qZnCbDLdRovKIXpS6mD4+//xT3Hq6h4Wns VRUo4r9jRQNxYvo8OuhWyHkTEfB/KcD1mnKNZXZzpMavBnSrG9S8jG1gk92t8043ulOe pXMYEPRSj2Q0jaZAAvxJk0DTaHFdaW36lraVZGfEt2NrjoFOmUgdE60AtMmlt5dhziKN mCmgPBmSdr7IIYs6voQetQT6zz94+EvLqlZ/6EoBpOnqpZcAXqbJ54VYKpCPCP64fTxC Z/jbhuPobGdLf77aMWkQIm6W3lQ9gzc0fvlzAX6HyK9cfqDXazRjs/81VDAc0jJQQfhy HCNg==
X-Gm-Message-State: AOAM532xOC7C+LAymsDlORzWo7utlN/6+MdXBvCmA8b4aSeQbefmoc97 a8C3DxN73ZKCNpSrESDEVrwGaA==
X-Google-Smtp-Source: ABdhPJxlJ/OHKMDkwBP/pwqInoLhNbDCiu77FB9ZmeMI+7XHCKRFE0SpNmws7k9Faip3JGwizgN14w==
X-Received: by 2002:ad4:4643:: with SMTP id y3mr5086140qvv.3.1609956273821; Wed, 06 Jan 2021 10:04:33 -0800 (PST)
Received: from mithrandir.lan (c-24-91-177-160.hsd1.ma.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id f134sm1752619qke.23.2021.01.06.10.04.32 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Jan 2021 10:04:33 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <FDE6D153-2EE9-4790-8D07-48236513DCB7@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4A9A3EC7-1DF5-4FF5-BADC-4F63CD8F2DAE"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.2\))
Date: Wed, 6 Jan 2021 13:04:30 -0500
In-Reply-To: <12491.1609955331@localhost>
Cc: Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>, ipv6@ietf.org, Gert Doering <gert@space.net>
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net> <c236e635-518b-fb51-5024-901ec4677c5d@si6networks.com> <20210106162652.GX13005@Space.Net> <1ddf8850-a8cb-53a7-31bc-7433d5a984f2@si6networks.com> <1089BC1B-A8E6-4BF5-BB3E-FD440181DB56@fugue.com> <12491.1609955331@localhost>
X-Mailer: Apple Mail (2.3654.60.0.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/iioGeFQ90QcQLz6SJU92LliVsIc>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 18:04:37 -0000

--Apple-Mail=_4A9A3EC7-1DF5-4FF5-BADC-4F63CD8F2DAE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Jan 6, 2021, at 12:48 PM, Michael Richardson <mcr+ietf@sandelman.ca> =
wrote:
> There are potentially many GUA (2000::/3) addresses that could be in =
DNS,
> which would not work for some originators due to ACLs, and yet a =
different
> entry might work just fine.  Why would ULA be any different?

The usual case here would be through a VPN; in that case the VPN will =
specify some set of domains that should be resolved through the VPN=E2=80=99=
s name servers. You really don=E2=80=99t want the ULA advertised =
globally.


--Apple-Mail=_4A9A3EC7-1DF5-4FF5-BADC-4F63CD8F2DAE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">On =
Jan 6, 2021, at 12:48 PM, Michael Richardson &lt;<a =
href=3D"mailto:mcr+ietf@sandelman.ca" =
class=3D"">mcr+ietf@sandelman.ca</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><meta charset=3D"UTF-8" =
class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">There are =
potentially many GUA (2000::/3) addresses that could be in =
DNS,</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">which would =
not work for some originators due to ACLs, and yet a different</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; =
font-size: 14px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">entry might =
work just fine. &nbsp;Why would ULA be any =
different?</span></div></blockquote></div><br class=3D""><div =
class=3D"">The usual case here would be through a VPN; in that case the =
VPN will specify some set of domains that should be resolved through the =
VPN=E2=80=99s name servers. You really don=E2=80=99t want the ULA =
advertised globally.</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_4A9A3EC7-1DF5-4FF5-BADC-4F63CD8F2DAE--


From nobody Wed Jan  6 10:09:07 2021
Return-Path: <mellon@fugue.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 EADEC3A10E6 for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 10:09:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 J4gl6BasOXCQ for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 10:09:03 -0800 (PST)
Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 607543A10DA for <v6ops@ietf.org>; Wed,  6 Jan 2021 10:09:03 -0800 (PST)
Received: by mail-qt1-x835.google.com with SMTP id g24so2579327qtq.12 for <v6ops@ietf.org>; Wed, 06 Jan 2021 10:09:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=lI1K76zbEooCB95VgnJbDrPuqokTja1trr1xk39pa1s=; b=QnivyyyFbBGERu1GRNI3VNflNZXxtGnBZcQhHzEFUwsAu2lV7TJRpquD10JIrRyj5I KDCpSignmzDYEhMmqKK1aniXtngFa2j00zA/cYtikBIIynAgIOFygeGv1nqKbJsB9/sN 2J/4J6WSXPQPo/sFPoqt7V88A9aBhy/tXAzezHVeKyV3BBt+8wN+PrJ46yinEuRxCD9r adconG4kStQF7se7THxvNnuKBOZucTF0VxUsAGtbnuSsa3+zAlRmbhf0aKXpcoyBxK6o Fn2I9Yrj2MpA4lrcQ0spNu4x75m81WjUoKQlo4EJm346cecYCfdpjLpKj16OfwD5TqBt lFyQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=lI1K76zbEooCB95VgnJbDrPuqokTja1trr1xk39pa1s=; b=SMlHzvmMpXqVu7R0P90iTG6d616Hrv9fgZt3kgVwGd0s47egiVNYQlIWy/HarXqS8x WxVM3ZBX60phBpUTgnLOAJWYYAyTdcSlUXm8iQvTu4tYLUdES+myL0VHpmpExKbRn6ql NI5J6bB2EV0YadWM9W+YxdPzJwKIlFltuqxJvk9eS+M6hMX04ltWBjFFAgw17ygskRK3 seZ+PhdgtbS1WleEGAiaVukrwFNQXzsFs4WjLxgLsndm8hhxteoPcEjDHFisqwybx9Ci c897O2S4WpQ4w8f3y7/9gPnl+aM12ai9fNmoapD2pjqULuaSbXgDTeix7cmMWgVHYf1J 8q8g==
X-Gm-Message-State: AOAM530oUBZA5rr/VJ+snHLSW5W3sZp6ejXkxfVfpadW+8+3InK8dC2s gEPvyfjJbjceWDG4fcH/KCKjpg==
X-Google-Smtp-Source: ABdhPJwUR9nH81OHF6GjmKiSG7V4owprwzPWlVhI90JlwEgm0OMlTB12U4gy5rrkwArcs2lKJqjavg==
X-Received: by 2002:ac8:5a90:: with SMTP id c16mr5070025qtc.331.1609956542471;  Wed, 06 Jan 2021 10:09:02 -0800 (PST)
Received: from mithrandir.lan (c-24-91-177-160.hsd1.nh.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id q32sm1591342qtb.0.2021.01.06.10.09.01 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Jan 2021 10:09:01 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <26933B3A-039C-4418-A1FF-5EFD5FC92523@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_47C06E68-CF31-4E53-A189-1212BBB9B1C3"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.2\))
Date: Wed, 6 Jan 2021 13:08:59 -0500
In-Reply-To: <13054.1609955471@localhost>
Cc: Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>, ipv6@ietf.org, Gert Doering <gert@space.net>
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net> <c236e635-518b-fb51-5024-901ec4677c5d@si6networks.com> <20210106162652.GX13005@Space.Net> <1ddf8850-a8cb-53a7-31bc-7433d5a984f2@si6networks.com> <1169.1609953092@localhost> <FA6275FF-E148-46DC-BCFD-987315765873@fugue.com> <13054.1609955471@localhost>
X-Mailer: Apple Mail (2.3654.60.0.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/EVLWLWL-kKk7nv6OUPIXXqUwQsA>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 18:09:05 -0000

--Apple-Mail=_47C06E68-CF31-4E53-A189-1212BBB9B1C3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Jan 6, 2021, at 12:51 PM, Michael Richardson <mcr+ietf@sandelman.ca> =
wrote:
> But... caching and outsourcing of DNS servers and outsourcing of DNS =
resolvers.
> I hate all of that: except for simpler (IoT) devices, which should =
always use
> local DNS server to get local policy,  all this policy should be in =
the
> client, not the server.

Okay, if that=E2=80=99s possible, sure, but the way to do that sort of =
policy would be to say what server to contact for what domain. The VPN =
example is just one example; you could certainly also do this without a =
VPN. It=E2=80=99s pretty easy to do on the Mac=E2=80=94just add a scoped =
DNS resolver; not sure how hard it is on Linux.

The thing is, though, that somebody has to provide the intelligence to =
decide either who to ask or what address to use. I think that by default =
you should never see a ULA other than from the local resolver, because =
there=E2=80=99s just no way for someone who _doesn=E2=80=99t_ know that =
ULA to know whether it would work or not. So if there are some domains =
that you want treated specially, the easiest way to do that is to have a =
different resolver for those domains (a scoped resolver).


--Apple-Mail=_47C06E68-CF31-4E53-A189-1212BBB9B1C3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">On =
Jan 6, 2021, at 12:51 PM, Michael Richardson &lt;<a =
href=3D"mailto:mcr+ietf@sandelman.ca" =
class=3D"">mcr+ietf@sandelman.ca</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><meta charset=3D"UTF-8" =
class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">But... =
caching and outsourcing of DNS servers and outsourcing of DNS =
resolvers.</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">I hate all of =
that: except for simpler (IoT) devices, which should always =
use</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">local DNS =
server to get local policy, &nbsp;all this policy should be in =
the</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">client, not =
the server.</span></div></blockquote></div><br class=3D""><div =
class=3D"">Okay, if that=E2=80=99s possible, sure, but the way to do =
that sort of policy would be to say what server to contact for what =
domain. The VPN example is just one example; you could certainly also do =
this without a VPN. It=E2=80=99s pretty easy to do on the Mac=E2=80=94just=
 add a scoped DNS resolver; not sure how hard it is on Linux.</div><div =
class=3D""><br class=3D""></div><div class=3D"">The thing is, though, =
that somebody has to provide the intelligence to decide either who to =
ask or what address to use. I think that by default you should never see =
a ULA other than from the local resolver, because there=E2=80=99s just =
no way for someone who _doesn=E2=80=99t_ know that ULA to know whether =
it would work or not. So if there are some domains that you want treated =
specially, the easiest way to do that is to have a different resolver =
for those domains (a scoped resolver).</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_47C06E68-CF31-4E53-A189-1212BBB9B1C3--


From nobody Wed Jan  6 10:56:14 2021
Return-Path: <fgont@si6networks.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 5961C3A1143; Wed,  6 Jan 2021 10:56:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.161
X-Spam-Level: 
X-Spam-Status: No, score=-2.161 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, 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 fc_re41DPrij; Wed,  6 Jan 2021 10:56:08 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 977013A1135; Wed,  6 Jan 2021 10:56:08 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 6744E2838B1; Wed,  6 Jan 2021 18:56:04 +0000 (UTC)
To: Ted Lemon <mellon@fugue.com>
Cc: Gert Doering <gert@space.net>, IPv6 Operations <v6ops@ietf.org>, Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, ipv6@ietf.org
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net> <c236e635-518b-fb51-5024-901ec4677c5d@si6networks.com> <20210106162652.GX13005@Space.Net> <1ddf8850-a8cb-53a7-31bc-7433d5a984f2@si6networks.com> <1089BC1B-A8E6-4BF5-BB3E-FD440181DB56@fugue.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <b24b2ebf-e836-adf2-401e-07be96df6deb@si6networks.com>
Date: Wed, 6 Jan 2021 14:34:13 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <1089BC1B-A8E6-4BF5-BB3E-FD440181DB56@fugue.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/QEEUzBzAlJSrMG4sRrE1Ns4m-DY>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 18:56:12 -0000

On 6/1/21 14:10, Ted Lemon wrote:
> On Jan 6, 2021, at 11:46 AM, Fernando Gont <fgont@si6networks.com 
> <mailto:fgont@si6networks.com>> wrote:
>> I have Raspberry Pis that deploy here and there. In order to be able 
>> to access them, they use dynamic DNS to post their addresses on their DNS.
>> If I don't look at the properties of the addresses, then I end up 
>> puting crap on the DNS. One straightforward consequence is that many 
>> apps that don't do Happy Eyeballs end up having an insane 
>> connection-establishment period, if they happen to try the unusable 
>> addresses first.
>>
>> So "find all your IPv6 addresses and post them to the DNS" doesn't work.
> 
> It is of course not even obvious how to solve this, because sometimes 
> you do want ULA in DNS, and sometimes you don’t. And it depends on what 
> DNS. If you are doing split DNS, then you can scope the DNS that 
> advertises ULAs only to serve those networks where those ULAs are 
> in-scope. The DNS that is advertised globally would of course contain no 
> ULAs. How this is arranged is either a matter of local configuration or 
> an interesting topic of future work, depending on how you look at it.

What I do is set up to different names. e.g.:

node.mydomain,com  for the global addresses, and,
node-local.mydomain.com for the non-global addresses.

In the case of apps that are expected to be available only to local 
nodes (e.g., mDNS) the daemon might want to explicitly bind() a ULA, 
rather than bind() the wildcard "address". So the app gets an extra 
layer of isolation as a result of the address scope. And probably also 
gets more stability, since in most cases the ULA prefix will be 
generated by the local router and thus be stable, while the global 
prefix may end up being dynamic.


-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan  6 10:56:24 2021
Return-Path: <fgont@si6networks.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 A676D3A1200; Wed,  6 Jan 2021 10:56:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.161
X-Spam-Level: 
X-Spam-Status: No, score=-2.161 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, 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 lvQeLHdaGQkr; Wed,  6 Jan 2021 10:56:15 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1D913A114A; Wed,  6 Jan 2021 10:56:14 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 126AA283A88; Wed,  6 Jan 2021 18:56:10 +0000 (UTC)
To: Ted Lemon <mellon@fugue.com>, Michael Richardson <mcr+ietf@sandelman.ca>
Cc: IPv6 Operations <v6ops@ietf.org>, ipv6@ietf.org, Gert Doering <gert@space.net>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net> <c236e635-518b-fb51-5024-901ec4677c5d@si6networks.com> <20210106162652.GX13005@Space.Net> <1ddf8850-a8cb-53a7-31bc-7433d5a984f2@si6networks.com> <1169.1609953092@localhost> <FA6275FF-E148-46DC-BCFD-987315765873@fugue.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <dda7dd99-7eda-4c17-cd17-b3e86d42a30d@si6networks.com>
Date: Wed, 6 Jan 2021 14:35:29 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <FA6275FF-E148-46DC-BCFD-987315765873@fugue.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/kro7QDbCbCIUmL7gAbieHQQreIE>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 18:56:21 -0000

On 6/1/21 14:20, Ted Lemon wrote:
> On Jan 6, 2021, at 12:11 PM, Michael Richardson <mcr+ietf@sandelman.ca 
> <mailto:mcr+ietf@sandelman.ca>> wrote:
>> And, yet, for the case where some device is doing dynamic DNS update 
>> to a DNS
>> server that is within some ULA scope, posting the ULA to the DNS is 
>> actually
>> correct.
>> But, it's hard to know that without knowing what clients are expected 
>> to connect.
> 
> It seems straightforward that the client should send all the addresses 
> it wants to advertise, and the DNS server should decide which ones to 
> advertise in what scopes.

FWIW, I didn't find that magic in BIND (even if it's there), so I had to 
deal with it on the client side.


-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan  6 10:56:46 2021
Return-Path: <fgont@si6networks.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 D40803A138C; Wed,  6 Jan 2021 10:56:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.15
X-Spam-Level: 
X-Spam-Status: No, score=-2.15 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, 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 YRI3J9mAODNh; Wed,  6 Jan 2021 10:56:33 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D1793A1179; Wed,  6 Jan 2021 10:56:22 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 6F12F284F56; Wed,  6 Jan 2021 18:56:17 +0000 (UTC)
To: Ted Lemon <mellon@fugue.com>
Cc: Gert Doering <gert@space.net>, IPv6 Operations <v6ops@ietf.org>, Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, ipv6@ietf.org
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net> <c236e635-518b-fb51-5024-901ec4677c5d@si6networks.com> <20210106162652.GX13005@Space.Net> <88297320-9516-4627-A673-FBFDA6A10B0C@fugue.com> <035a725a-19bf-efae-bf13-15e8dae4cc97@si6networks.com> <184A442D-53F0-4B21-B094-779A1F66AD39@fugue.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <42ebf28f-ea1e-9650-f84f-c561a673720e@si6networks.com>
Date: Wed, 6 Jan 2021 14:46:04 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <184A442D-53F0-4B21-B094-779A1F66AD39@fugue.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/sTQsmCoOOrQpNtEzOorkCbSkD2U>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 18:56:42 -0000

On 6/1/21 14:33, Ted Lemon wrote:
> On Jan 6, 2021, at 12:26 PM, Fernando Gont <fgont@si6networks.com 
> <mailto:fgont@si6networks.com>> wrote:
>> e.g., for thinks like mDNS, you'd only bind() and listen on your ULAs, 
>> if any.
> 
> mDNS is link-local, so you can actually use your LLA for that (and we 
> do). 

The problem with link-locals is that having to specify the "zone id" 
with the "Addr%iface" thing at times is nto friendly with some apps.



> But e.g. if you are using SRP 
> (https://tools.ietf.org/html/draft-ietf-dnssd-srp-07), then it makes 
> sense to push your GUA and your ULA and bind to both, or to INADDR_ANY 
> (if you want to be globally reachable). I would expect the SRP server to 
> do the work of figuring out on which DNS server to publish the ULA and 
> on which to publish the GUA.

... in which case the server would have to be able to infer address 
properties, using macros or libraries such as the one in 
https://tools.ietf.org/html/draft-gont-6man-ipv6-ula-scope-00#section-5.1


-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan  6 10:59:50 2021
Return-Path: <noreply@ietf.org>
X-Original-To: v6ops@ietf.org
Delivered-To: v6ops@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CCAAF3A1241; Wed,  6 Jan 2021 10:59:49 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ron Bonica via Datatracker <noreply@ietf.org>
To: <warren@kumari.net>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Cc: iesg-secretary@ietf.org, rbonica@juniper.net, v6ops-chairs@ietf.org, v6ops@ietf.org
Message-ID: <160995958981.18142.6020938447571101340@ietfa.amsl.com>
Date: Wed, 06 Jan 2021 10:59:49 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/guyUyBP8tOL8dP-VzwK92rjj-g0>
Subject: [v6ops] Publication has been requested for draft-ietf-v6ops-ipv6-ehs-packet-drops-03
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 18:59:50 -0000

Ron Bonica has requested publication of draft-ietf-v6ops-ipv6-ehs-packet-drops-03 as Informational on behalf of the V6OPS working group.

Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-v6ops-ipv6-ehs-packet-drops/



From nobody Wed Jan  6 11:04:39 2021
Return-Path: <albert.e.manfredi@boeing.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 1A21E3A113B; Wed,  6 Jan 2021 11:04:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 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, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=boeing.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 eW3RAcWb2nxz; Wed,  6 Jan 2021 11:04:36 -0800 (PST)
Received: from clt-mbsout-02.mbs.boeing.net (clt-mbsout-02.mbs.boeing.net [130.76.144.163]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F0913A1135; Wed,  6 Jan 2021 11:04:36 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 106J4X6m032398; Wed, 6 Jan 2021 14:04:33 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1609959873; bh=LB9t1eHnYXeiQTDPm9Eki2k4TemLD87tkA0BbWoYDE8=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=BmTYpgccygxJdVNNnQbAC2NwV0tkFxsqCL9ad+xzcrt3aJNuY3lY2n2Vw1mGKnjg7 ebzTIgi4+K6IpDfPBuVav5kyojoITuvm53R6zJf3SEceiQrwXm+bzrvGAcv3FsQhM3 tbwNWUgNokWsISGqimn07KamnmDuOeL37Jn7DhZRHmBZ5yFSqiko1MYhAlb3AO6clY 1/qX9U4VXLAerqVPUcSocu3AMX0+zYdxhzQ4ViNRsXWL0u/0BqaYXm0tMBXv2lPJ+y KEk9Z6540lXbBYmHqWuXctt1oe7hw2Q+LAttPxa4lSZZBsmYUL60ogr07RwJORLrzk a/Yw3n+tIsyEQ==
Received: from XCH16-01-10.nos.boeing.com (xch16-01-10.nos.boeing.com [144.115.66.5]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 106J4MEN032297 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Wed, 6 Jan 2021 14:04:23 -0500
Received: from XCH16-01-11.nos.boeing.com (144.115.66.39) by XCH16-01-10.nos.boeing.com (144.115.66.5) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2044.4; Wed, 6 Jan 2021 11:04:21 -0800
Received: from XCH16-01-11.nos.boeing.com ([fe80::c57c:39bc:4c0a:384b]) by XCH16-01-11.nos.boeing.com ([fe80::c57c:39bc:4c0a:384b%4]) with mapi id 15.01.2044.004; Wed, 6 Jan 2021 11:04:21 -0800
From: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>
To: Richard Patterson <richard@helix.net.nz>
CC: IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
Thread-Topic: [EXTERNAL]  Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
Thread-Index: AQHW48/q6MYge4t1TkCUP2ZIbkIFhaoas8eAgAAGVYCAAFhKgP//4oMg
Date: Wed, 6 Jan 2021 19:04:21 +0000
Message-ID: <5074034efaf04777be2517645c1c4630@boeing.com>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com> <CAL9jLaZA4y+9bdvzq5r4V=B6580ZnsdwYyvQ4nzjdeccMsM4Tg@mail.gmail.com> <CAHL_VyCmYQ_X9FckY0Fem2Cq-zaDQ6e=WPxsHJP6LXKGksnU6A@mail.gmail.com>
In-Reply-To: <CAHL_VyCmYQ_X9FckY0Fem2Cq-zaDQ6e=WPxsHJP6LXKGksnU6A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [144.115.204.6]
x-tm-snts-smtp: 4557121A5A16E431CFCA3671F83E7FDE93A4DF79B10CCC59715DE3B668D8A3232000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/QrNUomNoPLFCBIraXTvbmQ47dv0>
Subject: Re: [v6ops] [EXTERNAL] Re: Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 19:04:38 -0000

RnJvbTogaXB2NiA8aXB2Ni1ib3VuY2VzQGlldGYub3JnPiBPbiBCZWhhbGYgT2YgUmljaGFyZCBQ
YXR0ZXJzb24NCg0KPj4gT24gV2VkLCA2IEphbiAyMDIxIGF0IDA3OjMxLCBDaHJpc3RvcGhlciBN
b3Jyb3cgPG1haWx0bzpjaHJpc3RvcGhlci5tb3Jyb3dAZ21haWwuY29tPiB3cm90ZToNCj4+DQo+
PiBvcHRpb24gNCwgZGVwcmVjYXRlIFVMQS4NCj4+IHRoZSBiZXN0IG9wdGlvbiAodG0pLg0KPg0K
PiBTdHJvbmdseSBkaXNhZ3JlZS4NCj4gSSB0aGluayBkZWZpbmluZyBhIG5ldyBzY29wZSBmb3Ig
VUxBIGlzIGEgZ29vZCBpZGVhIGFuZCB3aWxsIGhlbHAgdG8gZGVteXN0aWZ5IGFuZCBpbXByb3Zl
IHRoZWlyIHVzZSBpbiB0aGUgcmVhbCB3b3JsZC4NCg0KKzEuIEVtcGhhdGljYWxseS4gQW5kLCB0
aGUgc2FtZSB3b3VsZCBhbHNvIGFwcGx5IHRvIFJGQyAxOTE4Lg0KDQpCZXJ0DQoNCg==


From nobody Wed Jan  6 11:46:52 2021
Return-Path: <markzzzsmith@gmail.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 907AC3A1188; Wed,  6 Jan 2021 11:46:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.599
X-Spam-Level: 
X-Spam-Status: No, score=-0.599 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.998, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 BkONk5ccEK6K; Wed,  6 Jan 2021 11:46:50 -0800 (PST)
Received: from mail-ot1-x32a.google.com (mail-ot1-x32a.google.com [IPv6:2607:f8b0:4864:20::32a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16E883A1102; Wed,  6 Jan 2021 11:46:50 -0800 (PST)
Received: by mail-ot1-x32a.google.com with SMTP id d8so4116581otq.6; Wed, 06 Jan 2021 11:46:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=a0KX+rMiBdbGde6DZlSiPYYZyPtyoAQSf5pMHGhu6ng=; b=gRjfRqPbTPH9DS3l7benl8KLf7OZGN0P9+cF5SZIv320DDX376qyUBl7yNX2wJ9+jL 9JDbXgpD/8qnEtIWGpURdLFMyfit6lls9LtYIX0FYBxuVMMAcYznST/d0NcrV9n7n/9q gu1wRA5eEvFz/BqmcUXNjQjhp0+7J+Z8OUYO4ThfpoEd681gnXYfj4WCMpyG1XqLoMzP RgZW+9RIME9LnvL2deCXKUaBFZb18LDf68MB8Q/GV1q+1t24g4ZuryEX08F0RKGEZsLm oFmPUXKJk0BP6v2rhFhaMkjHQx160JXlmY+dWmLC91vYJkjJBaNsXPgmsqqpXAB5OV5R iO0w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=a0KX+rMiBdbGde6DZlSiPYYZyPtyoAQSf5pMHGhu6ng=; b=QiwKAiecDysgafJjZVJrM4vuPYsj4malu6BZlZPK1y8jC7N6254wIf0cAeplaSQaOK Mkifx2TDEe0qG53SsEHrPzgxkOuJhuOEQNxZV6XOxGAvbP2g16t40tl/ziSlvGBu3mZh k41gK6rSdX3QDVexriPbPwhcPzxC2cv0LGNtoHwz+Bbw470Mo9cyT10z8SAQDFxTzuPk s1b6RwuFRgWewaAyBwhL02UjDK3hFPCYj7yY5chvjH8Q1F6cNPDtb6r6QFV9bGU3Vv+n xiaYyysvkwQK3jTsYOWyNHGIOPNrJeU4ZfuD2oyJYEKQBcjVtPvs8owPdYrO1JA1trR8 NADQ==
X-Gm-Message-State: AOAM531XHMZqA1MY6Y8ml4rf0G1yvszaq4i9ZlgyHeErqWILtrAF8udC L+y5lpmTGaz0DqssHFMYzQD6JTnyAj7fh6of1V8=
X-Google-Smtp-Source: ABdhPJz7e0bY7uqnU4rhILeeIOXzWZVK74LZJimeR72vkb30Nx973X6Ba/xEyTS697ReCwwYLF2ebh2cSB38wTMl+fw=
X-Received: by 2002:a9d:602:: with SMTP id 2mr4305378otn.153.1609962409393; Wed, 06 Jan 2021 11:46:49 -0800 (PST)
MIME-Version: 1.0
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAN-Dau344H7xgD0Q_O54c=R08zFRFjToO8BHt=ssauxgEH7ynA@mail.gmail.com> <EFF2CF9D-147B-4E7F-9080-633A24FDA666@fugue.com>
In-Reply-To: <EFF2CF9D-147B-4E7F-9080-633A24FDA666@fugue.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Thu, 7 Jan 2021 06:46:22 +1100
Message-ID: <CAO42Z2xmP1CFWsDKQJ35wuNjjdZdyimZN=5j2h9rGbcZjkeHZA@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
Cc: David Farmer <farmer=40umn.edu@dmarc.ietf.org>, Fernando Gont <fgont@si6networks.com>,  IPv6 Operations <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/53p1Pjkz26fcKzpqXi999m-9q9Y>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 19:46:52 -0000

On Wed, 6 Jan 2021 at 23:18, Ted Lemon <mellon@fugue.com> wrote:
>
> On Jan 5, 2021, at 11:38 PM, David Farmer <farmer=3D40umn.edu@dmarc.ietf.=
org> wrote:
>
> I think this is the right direction the previous draft indirectly defined=
 a new scope "non-global", I much prefer explicitly defining a new local sc=
ope.
>
>
> Actually, I think you=E2=80=99ve got it right here: the scope is =E2=80=
=9Cnon-global.=E2=80=9D

I







>
> I would add something like the following to better define the relationshi=
p between the three scopes;
>
> The boundary of the link-local scope is strongly defined, limiting the ex=
tent of the link-local scope to an individual link. However, in contrast, t=
he boundary of the local scope is weakly defined, it is amorphous and impre=
cise. In some instances, the extent of the local scope can be a single site=
, in other instances, a group of unrelated sites, a single organization, or=
 even a cooperating group of organizations. Furthermore, the extent of an i=
ndividual instance of the local scope doesn't necessarily remain constant, =
it may expand or contract over time as the local situation dictates, for ex=
ample when two organizations merge. Nevertheless, the extent of the local s=
cope doesn=E2=80=99t encompass the entirety of the Internet which the globa=
l scope does.
>
>
> There is at least one obvious problem with this definition: the term =E2=
=80=9Clocal.=E2=80=9D ULAs aren=E2=80=99t really local, despite the name. U=
sing the name =E2=80=9Clocal=E2=80=9D is what leads to this confusion. Cons=
ider this taxonomy:
>
> GUA: =E2=80=9Cvalid everywhere on the internet scope=E2=80=9D
> ULA: =E2=80=9Cnot valid everywhere scope=E2=80=9D
> LLA: =E2=80=9Cvalid only on this link scope=E2=80=9D
>
> Of course these names are awkward, but I hope they are clarifying. A ULA =
is =E2=80=9Cnot valid everywhere.=E2=80=9D That=E2=80=99s really all you ca=
n say about it. You can=E2=80=99t put a ULA prefix in a global routing doma=
in. You can put it in a site routing domain. You can put it in a multi-site=
 routing domain. You can not route it at all. All these uses are valid.
>
> So I don=E2=80=99t really object to your text, but I do object to the nam=
e =E2=80=9Clocal.=E2=80=9D How about =E2=80=9Cexplicit=E2=80=9D? That is, t=
he scope of a ULA is explicit, in the sense that it must be _made_ explicit=
 by the user(s) of the ULA? If that doesn=E2=80=99t work, I=E2=80=99m sure =
we can come up with a more agreeable term, but please let it not be =E2=80=
=9Clocal.=E2=80=9D Sorry to be a sticky wicket. :)
>

I think "local" is close to, if not the right word.

I consider anything that is non-global or smaller than global to be "local"=
.

I think "local" is a word that has the word's user's perspective and
the context of its use as part of its semantics. The perspective and
context defines what the "local" domain boundary is, and it is
possible that different people might have different definitions,
although they'll probably be pretty similar. People have their own
local perspective on the definition of the word "local" ;-)

When I'm at home, my "local" network is my home network.

When I'm at work, my "local" network is the ISP I work at's network. I
don't consider our customers' home networks "local" though, even
though they're all part of the network with the same AS number.

Some examples of "local" outside of networking.

I go for walks around my local neighbourhood. I ride my bike around
the local neighbourhood. As I can ride further than I can walk, my
local neighbourhood in the context of being on my bike is a greater
geographical area than my local neighbourhood when I walk.



> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Wed Jan  6 13:03:53 2021
Return-Path: <warren@kumari.net>
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 1A7003A1299 for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 13:03:46 -0800 (PST)
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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.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 UZnwvsENMVYB for <v6ops@ietfa.amsl.com>; Wed,  6 Jan 2021 13:03:44 -0800 (PST)
Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1197F3A1277 for <v6ops@ietf.org>; Wed,  6 Jan 2021 13:03:43 -0800 (PST)
Received: by mail-lf1-x12b.google.com with SMTP id x20so9621910lfe.12 for <v6ops@ietf.org>; Wed, 06 Jan 2021 13:03:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=kLbvBp37eOJr3XOhqPdWDBU3A2YfyICaHaN4qgiPfjg=; b=GRK99/hdE1UsIcPhi+hCsJtle6uLvUFtU2t26+cNqjfBcVXpRpFYToH91HvLQY1mkh 4n91m6ZxWTl3YCEX1BiccnTPjVS4TeIJ+fpMzuRAZet25nqcCrLYvWpJvE+O8TCViXf8 6KeqEDnJFHy6RUB3dknx3zDmzMTxSao+4POvNsS002EWQXo00XCyQ/yxJO1XU5zuxKrB zAj8df5Ilz5FHyIm6ib/t7MSvAj8K7WAfVeH/w2RojnmODFMYXlw2Y+4KjdNyHyc1KH4 bmVD0mo7sQxTx0Raa9TuNh6msLjgs36l+ZfMFINbdoRLjVMXICZgGQ+J7P6uMC5miakf ksdg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=kLbvBp37eOJr3XOhqPdWDBU3A2YfyICaHaN4qgiPfjg=; b=QpuMIgl5F2k0/MhJf4CEUGQJTNEvSQ58QavEr5bMlb97y8C6L7PIwzsmgGhVGq8tfb fGLKKtUnFVm6PC1j/pr5zjtfO92Kj0ESKG2lwhN+J6cJ8nSVYsVhH4soCt3EfBaBuWa9 BLha+lLPWr2OpBW6R92IzlPCk51glgL5ekc8EWfcLi6Mz0q4sLrow3vwBXhOuqZTul+z hZ5XxGFbKdKb1kbHmINAbseReO+ykjPrC7XZpUYIHedL/SPuH3AzA6Y/Gd0pqbGzcNCv oCjL5B827xasf/sOU8Ko75cPdhB7noJeYpcJO6AuBeMXDZZIOdmG9VDyMwOc7yNsmCJ+ 7TGA==
X-Gm-Message-State: AOAM533OYfem5XEtPfpjJKJERU92Rl3GPl+1CbEPYmwgx1cclJZWIKkr RwFcbG3M4G0KbSc3QELrzwq9TRDtK+ibX7mTUZZPIw==
X-Google-Smtp-Source: ABdhPJw4G6neXDrz0mJw/Q2NoGZXVjB3O4lK8SiTj2Ooj7+33Bu+T1ALyoiuLk8uWMfIOT1ZBb4jdnnmOEE/NNZ3O/w=
X-Received: by 2002:a19:5f19:: with SMTP id t25mr2427169lfb.464.1609967021711;  Wed, 06 Jan 2021 13:03:41 -0800 (PST)
MIME-Version: 1.0
References: <160995958981.18142.6020938447571101340@ietfa.amsl.com>
In-Reply-To: <160995958981.18142.6020938447571101340@ietfa.amsl.com>
From: Warren Kumari <warren@kumari.net>
Date: Wed, 6 Jan 2021 16:03:05 -0500
Message-ID: <CAHw9_iJw-v-yvr7FhJ0uQH16i_ZX9FKeNNPbRnhJQ9wgqR5R8Q@mail.gmail.com>
To: Ron Bonica via Datatracker <noreply@ietf.org>, IPv6 Operations <v6ops@ietf.org>
Cc: "Ronald P. Bonica" <rbonica@juniper.net>, V6Ops-Chairs <v6ops-chairs@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/0x6ARRrCOKiyfGV7Yb8jZxIyzJ4>
Subject: Re: [v6ops] Publication has been requested for draft-ietf-v6ops-ipv6-ehs-packet-drops-03
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 21:03:52 -0000

[ - Secretariat, for clutter ]

Hi all,

Just FYI, as I'm an author, Rob Wilton will be the responsible AD for
this document, and I will recuse from balloting....

Thanks WG and Rob,
W


On Wed, Jan 6, 2021 at 2:00 PM Ron Bonica via Datatracker
<noreply@ietf.org> wrote:
>
> Ron Bonica has requested publication of draft-ietf-v6ops-ipv6-ehs-packet-=
drops-03 as Informational on behalf of the V6OPS working group.
>
> Please verify the document's state at https://datatracker.ietf.org/doc/dr=
aft-ietf-v6ops-ipv6-ehs-packet-drops/
>
>


--
The computing scientist=E2=80=99s main challenge is not to get confused by =
the
complexities of his own making.
  -- E. W. Dijkstra


From nobody Wed Jan  6 13:30:56 2021
Return-Path: <brian.e.carpenter@gmail.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 BB4053A1320; Wed,  6 Jan 2021 13:30:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.36
X-Spam-Level: 
X-Spam-Status: No, score=-2.36 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, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 qWsUfmKOqwEG; Wed,  6 Jan 2021 13:30:42 -0800 (PST)
Received: from mail-pl1-x631.google.com (mail-pl1-x631.google.com [IPv6:2607:f8b0:4864:20::631]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2DED3A1332; Wed,  6 Jan 2021 13:30:41 -0800 (PST)
Received: by mail-pl1-x631.google.com with SMTP id x12so2199860plr.10; Wed, 06 Jan 2021 13:30:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=sDkEyE+FbLEVswaEdAeRtvWNY5jlhRPI34LVCkuErN0=; b=qrUDy0PF9T2NyNbe6hnDXRibVufsKsQ7HMWlif1BchBBJUY7pAc6FkY4Eq/xwi14AB ZZfnYiGLAOrF8KPsNSC792KzWrxrsWYKEIiGNhuhxwRaNRRF6F8orLQAlcfFUlufPXuT o29PYJaZ7aIMccMPqmKEuyb6A6bMEas24J7ybbPqI7jUiZjDYD714HsnsjLLw2WKvnAi PtBkPmeAsXm4/Tys0PkNuw2vlFSiDXwIGPIsusDYdAePrSP6PzQK2qLgtRy2DYRAl8j+ 486sPM59UgeFMahHWIUIewMAoLwrEHJX2dX7bdQ3pGPZpOmq/awlF3vikuB31IodkdWX TvVA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=sDkEyE+FbLEVswaEdAeRtvWNY5jlhRPI34LVCkuErN0=; b=iOnjeRr4OzulSVq3fwzt9sOOc8CEAhKgcX/D78wGhvwcKJP8mbix4MYX3QJoM7jZu5 lKYCvmMgQEYMETl34so1FfqDelXgYBL1g7xJPLaRY6JPX7Tu4ffGM4Gm+fFqLtWlF8v9 GhnbwsbXGx2hIvaXryY4k2st6HYQ1YTJ3a2Ri/yybyVlB8qQ31glMpIJYSEp3+mcDnnA 0uDsrgx7J8xADVTLwMmfpZhFOciuxFC3Eh/BBcS5r2hXFkkoyWxwCq6GotnbDFc3zynY TDn+wdNN+owEpFUV7rPicbiHLewKufYp33LMLj2+TOw0YLUSR9pNVqYpWn97aSLJJwli Raqw==
X-Gm-Message-State: AOAM532fQ+owaCKcZjkryMHSF+vr08C3q2b9STxl9pdN2VoUloovGmbq Xr2Hke35kNLuF+0psQRnRbPy3SOt4XBOAQ==
X-Google-Smtp-Source: ABdhPJzL0elJfnYbv+Ik5uRx+JzATNfkKiiqF9YhLMzIEoaeL+uYQiE9K/MhwJh/9U2cmeAPQ2H9tA==
X-Received: by 2002:a17:902:8483:b029:dc:3e69:4095 with SMTP id c3-20020a1709028483b02900dc3e694095mr6188436plo.66.1609968640690;  Wed, 06 Jan 2021 13:30:40 -0800 (PST)
Received: from [192.168.178.20] ([151.210.131.28]) by smtp.gmail.com with ESMTPSA id q6sm3109412pfu.23.2021.01.06.13.30.37 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Jan 2021 13:30:39 -0800 (PST)
To: Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>, Mark Smith <markzzzsmith@gmail.com>
Cc: Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <44e7ac61-523a-d35e-9024-7e6df81e4226@gmail.com>
Date: Thu, 7 Jan 2021 10:30:35 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/LPE-wlpK5vKiX4PtEMq88MjAydM>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 21:30:50 -0000

Portmanteau reply to multiple messages:

On 06-Jan-21 20:07, Lorenzo Colitti wrote:
=2E..
> So I guess I'm somewhere between 1) and 3). The specs are consistent bu=
t they fail to consider human behaviour, so they don't actually work in p=
ractice.

I disagree. They work fine in practice.  The smart meter example is a goo=
d one. The ANIMA autonomic control plane is another. My TV has a ULA addr=
ess. I have no idea whether it's used when I control it from my Android p=
hone, because address selection does its job.

The problem is largely theoretical, and educational for people who train =
IPv4 users in IPv6 terminology and practices. As Fernando has pointed out=
, the use of the word "global" is confusing for something that has L for =
"local" in its name.

On 06-Jan-21 20:30, Christopher Morrow wrote:
=2E..
> option 4, deprecate ULA.
> the best option (tm).

I can't see the least argument for that (no proven damage) and very stron=
g arguments against (running code and operational deployments).

On 07-Jan-21 01:17, Ted Lemon wrote:
=2E..
> GUA: =E2=80=9Cvalid everywhere on the internet scope=E2=80=9D
> ULA: =E2=80=9Cnot valid everywhere scope=E2=80=9D
> LLA: =E2=80=9Cvalid only on this link scope=E2=80=9D

Friendly amendment:

GUA: valid everywhere
ULA: Unique Limited-domain Address
LLA: valid only on this link

("scope" is really a noise word, and "Internet" is too restrictive.)

On 07-Jan-21 02:45, Philip Homburg wrote:
=2E..
> 'local' scope is an operational reality. You don't see it at the protoc=
ol
> level. So we need to keep it clearly separate from link-local where we =
do have
> quite a bit of protocol and API specification.

That's why using "scope" is a noise word. It isn't an abstract property. =
Try to draw it and you get a mess. This really hasn't changed since https=
://tools.ietf.org/html/rfc3879. Or see https://www.cs.auckland.ac.nz/~bri=
an/scope6.pdf.

On 07-Jan-21 04:13, Philip Homburg wrote:
=2E..
> Some things don't need fixing even if they are not 100% correct.

+1

On 07-Jan-21 04:29, Richard Patterson wrote:
>>     Applications should not do widely different things if they encoute=
r a ULA.
>=20
> But they do.
> Some OSes will see the presence of a ULA address on an interface, and s=
tart sending AAAA queries, some will not.
> Some applications will see a ULA destination address and simply ignore =
it, preferring the IPv4 destination address returned.=20
>=20
> We need to ask the question why this is happening, and if the answer is=
 "They're doing it wrong", great, let's point them at the existing RFCs a=
nd educate them, but if not...... we need to do something, and I think th=
is I-D is a good starting point for WG discussion at least.

FYI, we tried 6 years ago, but draft-ietf-v6ops-ula-usage-recommendations=
 stalled.

On 07-Jan-21 05:13, Philip Homburg wrote:
=2E..
>> You mean use interface IDs as zone IDs?
>=20
> No, rewrite RFC 4007 and get rid of zone IDs. And the introduce interfa=
ce IDs
> to select the interface of an outgoing packet, whether link-local or gl=
obal.

Effectively that's what RFC3879 did. RFC4007 was a bit behind the curve. =
As far as I know, zone IDs and interface IDs are exactly equivalent (at l=
east in POSIX and WinSock environments). IMHO this is *only* a terminolog=
y question.

> It doesn't change anything in practice, because that is what existing c=
ode
> does.

Really? Using the interface ID for non-link-local addresses?

On 07-Jan-21 05:26, Gert Doering wrote:
=2E..
> Why should applications, or anything that is not an admin, care if an
> address is a ULA or a GUA?

It depends on what you mean by "application". I've written code that expl=
icitly prefers a ULA, and I could imagine a security spec saying "prefer =
ULA". But anyway, it's not really a problem, is it? (It's annoying to me =
that in Python, a ULA has .is_global =3D=3D False, but I managed to code =
round that error.)

On 07-Jan-21 06:06, Ted Lemon wrote:
=2E..
>> or rename the scopes to be 0 (link-local), 5 (mid-range), 10 (global)=E2=
=80=A6
>=20
> This implies concentric circles, which isn=E2=80=99t really valid.

It really, really, really isn't valid. That's where we went wrong in 1995=
=2E Once the mid-range scopes start to overlap, the concentric circles mo=
del fails completely. That's the main reason we scrapped site-local.

On 07-Jan-21 07:04, Ted Lemon wrote:
=2E..
>> There are potentially many GUA (2000::/3) addresses that could be in D=
NS,
>> which would not work for some originators due to ACLs, and yet a diffe=
rent
>> entry might work just fine.  Why would ULA be any different?
>=20
> The usual case here would be through a VPN; in that case the VPN will s=
pecify some set of domains that should be resolved through the VPN=E2=80=99=
s name servers. You really don=E2=80=99t want the ULA advertised globally=
=2E

But neither do you want private-use 2000::/3 addresses advertised globall=
y. I really don't see a difference between RIR-assigned and self-assigned=
 (ULA) prefixes in this respect.

Regards
    Brian





From nobody Wed Jan  6 14:24:51 2021
Return-Path: <fgont@si6networks.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 180523A133D; Wed,  6 Jan 2021 14:24:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.161
X-Spam-Level: 
X-Spam-Status: No, score=-2.161 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 9GxGEiAuJ1Ff; Wed,  6 Jan 2021 14:24:48 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 106DE3A133F; Wed,  6 Jan 2021 14:24:42 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 06155280A8E; Wed,  6 Jan 2021 22:24:37 +0000 (UTC)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>, Mark Smith <markzzzsmith@gmail.com>
Cc: IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com> <44e7ac61-523a-d35e-9024-7e6df81e4226@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <be92f523-eeaa-8ed4-afdf-4a537f53748c@si6networks.com>
Date: Wed, 6 Jan 2021 19:23:49 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <44e7ac61-523a-d35e-9024-7e6df81e4226@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/zPGh-rkvf3pJYAIfLi5SEspDQtE>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 22:24:51 -0000

On 6/1/21 18:30, Brian E Carpenter wrote:
> Portmanteau reply to multiple messages:
> 
> On 06-Jan-21 20:07, Lorenzo Colitti wrote: ...
>> So I guess I'm somewhere between 1) and 3). The specs are
>> consistent but they fail to consider human behaviour, so they don't
>> actually work in practice.
> 
[...]
> 
> The problem is largely theoretical, and educational for people who
> train IPv4 users in IPv6 terminology and practices. As Fernando has
> pointed out, the use of the word "global" is confusing for something
> that has L for "local" in its name.

There is indeed a terminology issue, which ends up making it complicated 
to explain e.g. the concept of "scope" as a result.



> On 07-Jan-21 01:17, Ted Lemon wrote: ...
>> GUA: “valid everywhere on the internet scope” ULA: “not valid
>> everywhere scope” LLA: “valid only on this link scope”
> 
> Friendly amendment:
> 
> GUA: valid everywhere ULA: Unique Limited-domain Address LLA: valid
> only on this link

Would certainly also work.


> On 07-Jan-21 04:13, Philip Homburg wrote: ...
>> Some things don't need fixing even if they are not 100% correct.
> 
> +1

My take is that if the topics is confusing for us, we cannot expect it 
to be any better for others.



> On 07-Jan-21 05:26, Gert Doering wrote: ...
>> Why should applications, or anything that is not an admin, care if
>> an address is a ULA or a GUA?
> 
> It depends on what you mean by "application". I've written code that
> explicitly prefers a ULA, and I could imagine a security spec saying
> "prefer ULA". But anyway, it's not really a problem, is it? (It's
> annoying to me that in Python, a ULA has .is_global == False, but I
> managed to code round that error.)

The question is: Is it an error?

I've just checked the most "up to date" textbook that I have at hand on 
IPv6. Page 335 has a subsection entitled "Global addresses versus ULAs".
The discussion in the textbook is indeed fine.

Could one actually make the case that e.g. Python's library should 
change? If it did, it would be counter intuitive. It would match 
RFC4193/4291, but not RFC4007, e.g. the textbook I've checked, and the 
intuitive meaning of private/global.

FWIW, I don't think there's a problem with how ULAs work. But I do think 
that the terminology problem does have ramifications.

-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan  6 18:51:37 2021
Return-Path: <brian.e.carpenter@gmail.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 4B1343A1466; Wed,  6 Jan 2021 18:51:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.361
X-Spam-Level: 
X-Spam-Status: No, score=-2.361 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, NICE_REPLY_A=-0.262, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Nk7zQNkHuFPd; Wed,  6 Jan 2021 18:51:30 -0800 (PST)
Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F34E53A1290; Wed,  6 Jan 2021 18:51:29 -0800 (PST)
Received: by mail-pg1-x532.google.com with SMTP id n10so3776321pgl.10; Wed, 06 Jan 2021 18:51:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=MjSqEhTYe1vxKIVIBvOA0nU2xqkroFuWVOMOrhqZrF8=; b=pfKxrkkGSrh6u54LS3Z56aA3ebPneo9lcaRcdFjLdSzczDGXrTajOe46nnVNSe/3VL YAcsFYS8Tdr3GzasBUbgwLu/3DAccNGDUfoCIGknLMoCGZxxCYJ9AOuklJspdtEqWa9x 6UPegYD6yMTGkI7uRZR048BWZcdTXmD8pO/Zx5J2c0hPERHb11wTVAHtHQeg3V0lc/Rk y+JmRtniROAwkGuV8pqUkjIyg6z2i7zu5YmvWm0fHbHxI4O6CXQruuOXGzcWZEhYigNZ QvUus4b7ud4/mMeSDNi4GNe+60iPsVkGfdEBgFAKRQ8qNtPm+J+XpCI/Za5yDvPR5+bt or4Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=MjSqEhTYe1vxKIVIBvOA0nU2xqkroFuWVOMOrhqZrF8=; b=XPnTgXp78gwEmaGLFT5jD2yiwTfEsSCD7XhjhNgJ3RkbMzrL6WfyGFHjRb0rY62qg6 Ykd1waAGdIfTl3i7EiduWRp+DIREiTuKRH+C3/rZMokxYqur30yG8t6/vlLpF/WZ1Rhu B5jsl9bJgT+KsT9o2+wgXqpO1MEeYXJSJD3PafpAkxPUfZ6IugyhCCURbR9dIjUPM5qw WMr1Fdi8QUTRoXuq3Z++mqiW4nKbfsEIn0J29/kLXX9Mu1o48SXdPlsOr2Uw3k8pJSmv LFH9x7WHuvxplWKTA41Nzdcy3GMNFrpQC4hf6he4QCCyAXZO9ZK6lpqKvqczyZfLQ9RF +xWA==
X-Gm-Message-State: AOAM532yaT+egs47YX592PrMCMORnZlWDaVumcDmY1754NIC1CFyJYp7 tl3vEileTR8vMXta4XkzNajC8O80uxAg3A==
X-Google-Smtp-Source: ABdhPJyURsbqfGBfI1Lxv4Iy0mxzcxiFO4J5qOgZiAq9FXzt9ELy/gWQwjX1twdd9pbYG770pac4cA==
X-Received: by 2002:a63:1863:: with SMTP id 35mr7710055pgy.191.1609987889112;  Wed, 06 Jan 2021 18:51:29 -0800 (PST)
Received: from [192.168.178.20] ([151.210.131.28]) by smtp.gmail.com with ESMTPSA id p16sm3381582pju.47.2021.01.06.18.51.25 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Jan 2021 18:51:28 -0800 (PST)
To: Fernando Gont <fgont@si6networks.com>, Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>, Mark Smith <markzzzsmith@gmail.com>
Cc: IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com> <44e7ac61-523a-d35e-9024-7e6df81e4226@gmail.com> <be92f523-eeaa-8ed4-afdf-4a537f53748c@si6networks.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <7b3809f0-2db4-bcff-b669-66911ee9c087@gmail.com>
Date: Thu, 7 Jan 2021 15:51:23 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <be92f523-eeaa-8ed4-afdf-4a537f53748c@si6networks.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/cvsO3LIvEtE_XH-oV_J_KKYFRgw>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2021 02:51:31 -0000

On 07-Jan-21 11:23, Fernando Gont wrote:
> On 6/1/21 18:30, Brian E Carpenter wrote:
>> Portmanteau reply to multiple messages:
>>
>> On 06-Jan-21 20:07, Lorenzo Colitti wrote: ...
>>> So I guess I'm somewhere between 1) and 3). The specs are
>>> consistent but they fail to consider human behaviour, so they don't
>>> actually work in practice.
>>
> [...]
>>
>> The problem is largely theoretical, and educational for people who
>> train IPv4 users in IPv6 terminology and practices. As Fernando has
>> pointed out, the use of the word "global" is confusing for something
>> that has L for "local" in its name.
>=20
> There is indeed a terminology issue, which ends up making it complicate=
d=20
> to explain e.g. the concept of "scope" as a result.
>=20
>=20
>=20
>> On 07-Jan-21 01:17, Ted Lemon wrote: ...
>>> GUA: =E2=80=9Cvalid everywhere on the internet scope=E2=80=9D ULA: =E2=
=80=9Cnot valid
>>> everywhere scope=E2=80=9D LLA: =E2=80=9Cvalid only on this link scope=
=E2=80=9D
>>
>> Friendly amendment:
>>
>> GUA: valid everywhere ULA: Unique Limited-domain Address LLA: valid
>> only on this link
>=20
> Would certainly also work.
>=20
>=20
>> On 07-Jan-21 04:13, Philip Homburg wrote: ...
>>> Some things don't need fixing even if they are not 100% correct.
>>
>> +1
>=20
> My take is that if the topics is confusing for us, we cannot expect it =

> to be any better for others.
>=20
>=20
>=20
>> On 07-Jan-21 05:26, Gert Doering wrote: ...
>>> Why should applications, or anything that is not an admin, care if
>>> an address is a ULA or a GUA?
>>
>> It depends on what you mean by "application". I've written code that
>> explicitly prefers a ULA, and I could imagine a security spec saying
>> "prefer ULA". But anyway, it's not really a problem, is it? (It's
>> annoying to me that in Python, a ULA has .is_global =3D=3D False, but =
I
>> managed to code round that error.)
>=20
> The question is: Is it an error?

According to the addressing architecture and the ULA definition, it's
an error. It's also a tricky one to fix, because who knows what running
code might depend on it?

A test for ULA-ness in Python, using only the address properties that the=

ipaddress module already defines, is:

def is_ula(a):
    """Test for ULA"""
    return (a.is_private and not a.is_link_local
             and not a.is_loopback
             and not a.is_unspecified)

which also, not coincidentally, returns True for RFC1918 addresses.
(Of course you could equally well do a bit-mask test.)

> I've just checked the most "up to date" textbook that I have at hand on=
=20
> IPv6. Page 335 has a subsection entitled "Global addresses versus ULAs"=
=2E
> The discussion in the textbook is indeed fine.
>=20
> Could one actually make the case that e.g. Python's library should=20
> change? If it did, it would be counter intuitive. It would match=20
> RFC4193/4291, but not RFC4007, e.g. the textbook I've checked, and the =

> intuitive meaning of private/global.

That's of course exactly why the term "globally reachable" was added
by RFC8190. My objection to the Python library is not that it provides
the property .is_private, which is very clear, but that it asserts that
ipaddress.IPv6Address("fd63:45eb:dc14:0:8546:6ab7:1529:b435").is_global
is False. Because according to the Proposed Standard RFCs,
ULAs are both private and global.

Unfortunately I don't think it's reasonable to ask for a non-backwards-
compatible change in the Python library. If you were maintaining such
a widely used library, would you want to break compatibility?
=20
> FWIW, I don't think there's a problem with how ULAs work. But I do thin=
k=20
> that the terminology problem does have ramifications.

Yes.
   Brian


From nobody Wed Jan  6 20:01:02 2021
Return-Path: <fgont@si6networks.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 C56793A14E8; Wed,  6 Jan 2021 20:01:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.161
X-Spam-Level: 
X-Spam-Status: No, score=-2.161 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 AsvTBPYXXi7U; Wed,  6 Jan 2021 20:00:58 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B75F3A14EC; Wed,  6 Jan 2021 20:00:49 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id A62272846D0; Thu,  7 Jan 2021 04:00:44 +0000 (UTC)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>, Mark Smith <markzzzsmith@gmail.com>
Cc: IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com> <44e7ac61-523a-d35e-9024-7e6df81e4226@gmail.com> <be92f523-eeaa-8ed4-afdf-4a537f53748c@si6networks.com> <7b3809f0-2db4-bcff-b669-66911ee9c087@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <8345b02d-4c26-d5d8-7d85-1e85f3b15642@si6networks.com>
Date: Thu, 7 Jan 2021 01:00:29 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <7b3809f0-2db4-bcff-b669-66911ee9c087@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/1-A9YmMaFv0qrfcFJRfNXdMO0eI>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2021 04:01:01 -0000

Hi, Brian,

On 6/1/21 23:51, Brian E Carpenter wrote:
[...]
>>
>>> On 07-Jan-21 05:26, Gert Doering wrote: ...
>>>> Why should applications, or anything that is not an admin, care if
>>>> an address is a ULA or a GUA?
>>>
>>> It depends on what you mean by "application". I've written code that
>>> explicitly prefers a ULA, and I could imagine a security spec saying
>>> "prefer ULA". But anyway, it's not really a problem, is it? (It's
>>> annoying to me that in Python, a ULA has .is_global == False, but I
>>> managed to code round that error.)
>>
>> The question is: Is it an error?
> 
> According to the addressing architecture and the ULA definition, it's
> an error. 

But this is where we go back to the original question:
* RFC4007 says that global scope addresses are globally unique.

* RFC4193 aims to reduce the collision fo a number of ULA prefixes when 
grouped together, but certainly does *not* result in globally-unique 
prefixes. Still, RFC4193 claims that ULAs globals.


So from the pov of RFC4193, ULAs are globals. From the pov of RFC4007, 
they are not.

Which of the two (RFC4007 vs RFC4193) takes precedence?



> It's also a tricky one to fix, because who knows what running
> code might depend on it?
> 
> A test for ULA-ness in Python, using only the address properties that the
> ipaddress module already defines, is:
> 
> def is_ula(a):
>      """Test for ULA"""
>      return (a.is_private and not a.is_link_local
>               and not a.is_loopback
>               and not a.is_unspecified)
> 
> which also, not coincidentally, returns True for RFC1918 addresses.
> (Of course you could equally well do a bit-mask test.)
> 
>> I've just checked the most "up to date" textbook that I have at hand on
>> IPv6. Page 335 has a subsection entitled "Global addresses versus ULAs".
>> The discussion in the textbook is indeed fine.
>>
>> Could one actually make the case that e.g. Python's library should
>> change? If it did, it would be counter intuitive. It would match
>> RFC4193/4291, but not RFC4007, e.g. the textbook I've checked, and the
>> intuitive meaning of private/global.
> 
> That's of course exactly why the term "globally reachable" was added
> by RFC8190. My objection to the Python library is not that it provides
> the property .is_private, which is very clear, but that it asserts that
> ipaddress.IPv6Address("fd63:45eb:dc14:0:8546:6ab7:1529:b435").is_global
> is False. Because according to the Proposed Standard RFCs,
> ULAs are both private and global.

    [RFC4007] defines the scope of an address as:

       "[the] topological span within which the address may be used as a
       unique identifier for an interface or set of interfaces"

    And defines the "global scope" to be used for:

       "uniquely identifying interfaces anywhere in the Internet"

Given ~1.2M ULA prefixes, you have a probability P~1 that there's a 
collision.

In that light, it's hard to assert that they are globally unique, and 
hence that they have global scope....

-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan  6 21:22:33 2021
Return-Path: <mcr+ietf@sandelman.ca>
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 702BE3A0418; Wed,  6 Jan 2021 21:22:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, 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 r7CZBK4Dv6rO; Wed,  6 Jan 2021 21:22:24 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A0E63A0408; Wed,  6 Jan 2021 21:22:22 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id F101D389AD; Thu,  7 Jan 2021 00:23:29 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Q5XRtFHrXu5J; Thu,  7 Jan 2021 00:23:28 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 950C4389AC; Thu,  7 Jan 2021 00:23:28 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id C1DAF591; Thu,  7 Jan 2021 00:22:19 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
In-Reply-To: <8345b02d-4c26-d5d8-7d85-1e85f3b15642@si6networks.com>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com> <44e7ac61-523a-d35e-9024-7e6df81e4226@gmail.com> <be92f523-eeaa-8ed4-afdf-4a537f53748c@si6networks.com> <7b3809f0-2db4-bcff-b669-66911ee9c087@gmail.com> <8345b02d-4c26-d5d8-7d85-1e85f3b15642@si6networks.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Thu, 07 Jan 2021 00:22:19 -0500
Message-ID: <27939.1609996939@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/mLl7__3H_TNJUvP15LgSGkk5zH8>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2021 05:22:27 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Fernando Gont <fgont@si6networks.com> wrote:
    > But this is where we go back to the original question:
    > * RFC4007 says that global scope addresses are globally unique.

    > * RFC4193 aims to reduce the collision fo a number of ULA prefixes wh=
en
    > grouped together, but certainly does *not* result in globally-unique
    > prefixes. Still, RFC4193 claims that ULAs globals.

    > So from the pov of RFC4193, ULAs are globals. From the pov of RFC4007=
, they
    > are not.

    > Which of the two (RFC4007 vs RFC4193) takes precedence?

It really doesn't matter, because Global has many terms.

ULAs are globally unique (ideally), but are not globally routable.

Their lack of routability is not an architectural consideration, but a
bureaucratic RIR-based concern.  They don't get RPSL, RPKI, whois or revers=
e DNS.

{Whether you are convinced of the statistics of ULA-R being unique or not,
does not change the goal that they be unique}

RFC4007 defines a Global Scope. (Not Global Routing)
ULAs have Global Scope, and I see nothing in RFC4007 that contradicts that.

Unless, you live in IPv4 land, and think that everything that isn't RFC1918
must be routable. And I'm sure that you don't think that way.

This python library you mention is wrong, but being a python library, is
probably too opinionate to listen to reason.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl/2mosACgkQgItw+93Q
3WVVLggAtK0rkDtcqgj64CHq9DV1V/Udsw2Pz0iM0k0B/USXl+rXpZArpMgCCbT5
JDSPoGPyGdHx8yIVsWUnoSbnuppcX+a8ZCTgYAb6OmYKChxX5QWeDCgW0v+nsGIw
BUwBto+px2NzNn7Ehma879Q5WtErS++guDaD/grmhbXPuPIPW1F3YnrN0K4V9UVt
fBvZp7Up/BH6m5cyhAOMjZwQQ6ufXCjjqf8qdH8MkvO+hhMMDuIwEyItwigB1nkB
AbOOCL9pWb+n9ZsaTzUbRZFq7e3oiB298EydYg6tCIyhlsRNrMdU9p6s/g1V82yj
K6cgit6eYh8pz4pjap1K6ca1o/Qk/Q==
=Lxev
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Jan  6 22:11:11 2021
Return-Path: <fgont@si6networks.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 F27523A091C; Wed,  6 Jan 2021 22:11:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.161
X-Spam-Level: 
X-Spam-Status: No, score=-2.161 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, 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 sF3jNnFGP0Fc; Wed,  6 Jan 2021 22:11:03 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10A413A08B7; Wed,  6 Jan 2021 22:11:02 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 08B94280899; Thu,  7 Jan 2021 06:10:58 +0000 (UTC)
To: Michael Richardson <mcr+ietf@sandelman.ca>, IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com> <44e7ac61-523a-d35e-9024-7e6df81e4226@gmail.com> <be92f523-eeaa-8ed4-afdf-4a537f53748c@si6networks.com> <7b3809f0-2db4-bcff-b669-66911ee9c087@gmail.com> <8345b02d-4c26-d5d8-7d85-1e85f3b15642@si6networks.com> <27939.1609996939@localhost>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <9ce92832-e698-a66a-58b3-28e6ab5e00d1@si6networks.com>
Date: Thu, 7 Jan 2021 03:03:36 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <27939.1609996939@localhost>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ftQGmLGz25xi-lUEAv05PO3n6eM>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2021 06:11:06 -0000

On 7/1/21 02:22, Michael Richardson wrote:
> 
> Fernando Gont <fgont@si6networks.com> wrote:
>      > But this is where we go back to the original question:
>      > * RFC4007 says that global scope addresses are globally unique.
> 
>      > * RFC4193 aims to reduce the collision fo a number of ULA prefixes when
>      > grouped together, but certainly does *not* result in globally-unique
>      > prefixes. Still, RFC4193 claims that ULAs globals.
> 
>      > So from the pov of RFC4193, ULAs are globals. From the pov of RFC4007, they
>      > are not.
> 
>      > Which of the two (RFC4007 vs RFC4193) takes precedence?
> 
> It really doesn't matter, because Global has many terms.

It does. RFC 4193 claims that they have global scope.

Global scope does have a meaning.




> ULAs are globally unique (ideally), but are not globally routable.

THey can't be globally routable, because they can't be globally unique.



> Their lack of routability is not an architectural consideration, but a
> bureaucratic RIR-based concern.  They don't get RPSL, RPKI, whois or reverse DNS.
> 
> {Whether you are convinced of the statistics of ULA-R being unique or not,
> does not change the goal that they be unique}

But this is a key thing:
10-1000 nets with no ULAs -> low probability of colission != global scope!



> RFC4007 defines a Global Scope. (Not Global Routing)
> ULAs have Global Scope, and I see nothing in RFC4007 that contradicts that.

  [RFC4007] defines the scope of an address as:

       "[the] topological span within which the address may be used as a
       unique identifier for an interface or set of interfaces"

    And defines the "global scope" to be used for:

       "uniquely identifying interfaces anywhere in the Internet"


You have 40 bits for the "global ID" -- how many networks before 
collisions?  And, at the global level, do you expet to be above or 
bellow that number of networks? If above, you won't have unique 
prefixes, and hence, per the definition of RFC4007, you don't hable 
global scope.



> Unless, you live in IPv4 land, and think that everything that isn't RFC1918
> must be routable. And I'm sure that you don't think that way.

They *can't* be globally routeable, because they are not globally unique.

Similarly, even if you removed bogon filters etc, you cannot use 
10.0.0.0/8 globally because they mean different things for each of us. 
-- they are not global scope.

ULAs are just bigger (and yes, have a recommended algorithm for 
generating prefixes) such that if you grab a few ULA prefixes together, 
it's unlikely that there will be collisions.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan  6 23:38:25 2021
Return-Path: <marka@isc.org>
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 5FCDC3A03F1; Wed,  6 Jan 2021 23:38:19 -0800 (PST)
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, SPF_HELO_NONE=0.001, 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 IhJrYFSe2FVV; Wed,  6 Jan 2021 23:38:17 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0DDC3A03EF; Wed,  6 Jan 2021 23:38:17 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 5AD873BD545; Thu,  7 Jan 2021 07:38:17 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id B4E9B16005A; Thu,  7 Jan 2021 07:38:16 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id A2AA9160080; Thu,  7 Jan 2021 07:38:16 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id sFq10-aUek07; Thu,  7 Jan 2021 07:38:16 +0000 (UTC)
Received: from [172.30.42.68] (n114-75-149-106.bla4.nsw.optusnet.com.au [114.75.149.106]) by zmx1.isc.org (Postfix) with ESMTPSA id 86E1E16005A; Thu,  7 Jan 2021 07:38:15 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.7\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <bc29edad-b57b-bb53-141b-8f58c5ca2526@si6networks.com>
Date: Thu, 7 Jan 2021 18:38:12 +1100
Cc: Richard Patterson <richard@helix.net.nz>, Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, IPv6 Operations <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <91424EEE-EF12-4B5B-ADE4-38230E049290@isc.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net> <CAHL_VyD85e9=taY1XENf7hc=BXRyD_7JJFDCW2Oq_a0z3hYqUA@mail.gmail.com> <bc29edad-b57b-bb53-141b-8f58c5ca2526@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.3445.9.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/PeD2wRjYgGYpaZGkzRajy_MLpMU>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2021 07:38:20 -0000

> On 7 Jan 2021, at 02:45, Fernando Gont <fgont@si6networks.com> wrote:
>=20
> On 6/1/21 12:29, Richard Patterson wrote:
>> On Wed, 6 Jan 2021 at 15:14, Philip Homburg =
<pch-ipv6-ietf-7@u-1.phicoh.com <mailto:pch-ipv6-ietf-7@u-1.phicoh.com>> =
wrote:
>>    Applications should not do widely different things if they =
encouter
>>    a ULA.
>> But they do.
>=20
> And good for them that they do. The ones that don't are the ones that =
end up e.g. posting ULAs and link-locals on the public-facing DNS.

Really AAAA records need to be replaced with something that identifies =
the zone the IPv6 address is applicable to.
A 128bit followed by a domain name would work.  System would need to =
which domain names where applicable to which links.  I would expect the =
could be done with a RA option.

e.g.
	www.andrews.example.id.au. SA 2001:DB8::1c59:17c:a2ce:e9ee .
	www.andrews.example.id.au. SA fd37:287a:df67::1 =
dv.andrews.example.id.au.
        www.andrews.example.id.au. SA fe80::14f4:ff53:6bfa:960b =
link1.dv.andrews.example.id.au.
	www.andrews.example.id.au. SA ::ffff:10.0.0.1 =
dv.andrews.example.id.au.

The above has global, ULA, link-local and RFC 1918 addresses for a =
fictional web server. =20

> (I've had to do it myself when using dynamic DNS updates, for =
instance)
>=20
> Cheers,
> --=20
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>=20
>=20
>=20
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org


From nobody Thu Jan  7 00:48:21 2021
Return-Path: <etmetz@gmail.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 A10133A0AA1; Thu,  7 Jan 2021 00:48:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mqGUSUOFS5UK; Thu,  7 Jan 2021 00:48:17 -0800 (PST)
Received: from mail-lf1-x12c.google.com (mail-lf1-x12c.google.com [IPv6:2a00:1450:4864:20::12c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 676A43A0A9E; Thu,  7 Jan 2021 00:48:17 -0800 (PST)
Received: by mail-lf1-x12c.google.com with SMTP id o10so1903679lfl.13; Thu, 07 Jan 2021 00:48:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PLXpCWK1eq/moBDsDu0Qsx45djkmTIfS5geWEdEA78I=; b=MtO++4ESOW2JQtf3Rl3D2r8ttXTDn5TaGWZ0/qqhKqI0g1V0BtRAb2v28gtzVz/Kbv ii/oF6MiTZMemaU4cSQY/uxSMIHPoQX37LTVkKKhpawNPDgc1c5EaNGyuCaKSDkCLXRk A8KQ5KmnJ+hKlzDCQ7BstIjyDSfNNAGVUgpBNa7T1VCSE1JRL321pMr/IGIaUYnTJ5p4 y+Q5nRKA/foFT1d7hnGlywbzAl/hVycEM/CV/VO/ngEY2wbTrjAe9c6hqwBf8Tk4OiqE QK7+J2kX6bFG5ZmbB8dsVaXoyqI3tLEe/2gwM13OyufW5Bt3syQ32HrPZLQmw2dSUztu 0bdQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PLXpCWK1eq/moBDsDu0Qsx45djkmTIfS5geWEdEA78I=; b=QP/OYLfBZWSRYswM+Y3BeTvQyxTBm6MpPsj/n4SVRrgkMK3fhWp/nbrze7Wj+rbDAs tDD9yhx0ynCe55bG0QxlNjAAqw1HeDdn4Qf4lISxMSSKbrZLavhYK2XEvihZVpaV0caz Mug6aMt2kHAblcfxdzjA3vllguuBI8+U8DIQSSQ+XolIsn3N49GMNNyncclONKR0pzPS vhJaB7GuUR6QjhDrHcVWcfBQgPC95htXEgg8q40oaqcAEpxd3YHoqcm7YK0nSrEz0cv1 XoB/NN5R9a1PvtUDwZ/5cyMK7GIe60V2TyXV85r8gs6B8pK9mH3ORx1G1oF4JK05kFea lKXQ==
X-Gm-Message-State: AOAM533QiRh9Ix9DbkVO5dYZAGBJ5sC25I0v0I5a5zE4JbKTgVZLvvaB b/9+H25YKABWPGs2qJmhgErgVa0lnBzQohbiC1M=
X-Google-Smtp-Source: ABdhPJzV9Bt0NdAZJtIv3CY6cz6clMbY4KPkX5Z1cwna4BBEht5DVBakJG1OtXTt1xu23IcD3BjP5WAV7x46mt0bPX4=
X-Received: by 2002:a05:651c:1341:: with SMTP id j1mr3990418ljb.216.1610009295263;  Thu, 07 Jan 2021 00:48:15 -0800 (PST)
MIME-Version: 1.0
References: <160770241261.18071.12524922630334294118@ietfa.amsl.com> <fb832698-039e-baa5-ed6f-4d5a97e7b354@gmail.com> <299f492f-4cb7-fa9d-967f-b2a5df49034e@si6networks.com> <759efdb1-a59c-788c-0c7a-5a8ca2ced904@gmail.com> <b20425a3-8069-3823-4610-79c93714ad2f@si6networks.com> <fa8c56d3-5d64-ae55-5be1-a3ec7d8f130d@gmail.com> <20201231103010.GL13005@Space.Net> <47fb8588-98ee-bf50-b377-921f75dc72e0@gmail.com> <CAG=3OHf5jSPgr-R8Ny=uHQi4exSEf7x-QVNDjePO59314NtoYg@mail.gmail.com> <20210105160815.GQ13005@Space.Net> <f7974fc1-28da-34c4-b8d6-b1d88d6ec73a@si6networks.com>
In-Reply-To: <f7974fc1-28da-34c4-b8d6-b1d88d6ec73a@si6networks.com>
From: Eduard Metz <etmetz@gmail.com>
Date: Thu, 7 Jan 2021 09:48:05 +0100
Message-ID: <CAG=3OHem5dNJoHNvMSZ4+Ct1=Vts8g8f5E2wD0rFG6mfqXQvcw@mail.gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Cc: Gert Doering <gert@space.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>,  IPv6 Operations <v6ops@ietf.org>, draft-gont-v6ops-ipv6-addressing-considerations@ietf.org
Content-Type: multipart/alternative; boundary="000000000000211a5e05b84b8094"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Xi19vczFYLWli22oYpEXhAR7lPA>
Subject: Re: [v6ops] I-D Action: draft-gont-v6ops-ipv6-addressing-considerations-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2021 08:48:20 -0000

--000000000000211a5e05b84b8094
Content-Type: text/plain; charset="UTF-8"

It's indeed about the uniqueness of the prefix.
In terms of RFC4007 ULAs do not have a global scope, but are (or may be)
unique beyond link-local scope. There is not really a label for this it
seems

Apart from that ULA is hard to catch in terminology, I don't think there is
any disagreement

On Wed, Jan 6, 2021 at 3:10 AM Fernando Gont <fgont@si6networks.com> wrote:

> On 5/1/21 13:08, Gert Doering wrote:
> > Hi,
> >
> > On Tue, Jan 05, 2021 at 02:24:14PM +0100, Eduard Metz wrote:
> >> Maybe the last column should be "Applicable to Internet" (no / no / yes)
> >> or something along these lines. I assume the point here is to indicate
> that
> >> link-local and ULA cannot be used on the Internet.
> >
> > What is "the Internet"?
> >
> > We're an ISP, so if we use ULAs on our infrastructure, outside any
> > firewalls (but not announcing to other ASes, or leaking packets) - is
> > that "used on the Internet" or not?
>
> Agreed that "Applicable to Internet" is probably not a good taxonomy.
>
> The proper (and useful) taxonomy is that of "scope". ULAs clearly don't
> have a global scope (as per the definition in RFC4007).
>
> Given a ULA prefix (say, fd12:3456:7890:abcd::/64), it doesn't globally
> (and uniquely) identify a link. Similarly, nobody is in the position of
> publishing a ROA or restricting which AS can originate packets from such
> prefix.
>
> IMO, generating the "Global ID" of ULAs from a PRNG does reduce the
> possibility of collisions *when a limited number of ULA-based networks
> are interconnected* -- but the birthday paradox tells you can't expect
> the ULA prefixes to be globally unique. There's more to "global scope"
> than simply asserting that if you interconnect, say, two networks the
> chances of colliding prefixes will be small.
>
> Thanks,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>
>
>
>
>

--000000000000211a5e05b84b8094
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">It&#39;s indeed about the uniqueness of the prefix.=C2=A0<=
div>In terms of RFC4007 ULAs do not have a global scope, but are (or may be=
) unique beyond link-local scope. There is not really a label for this it s=
eems</div><div><br></div><div>Apart from that ULA is hard to catch in termi=
nology, I don&#39;t think there is any disagreement</div></div><br><div cla=
ss=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jan 6, 202=
1 at 3:10 AM Fernando Gont &lt;<a href=3D"mailto:fgont@si6networks.com">fgo=
nt@si6networks.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote=
" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);=
padding-left:1ex">On 5/1/21 13:08, Gert Doering wrote:<br>
&gt; Hi,<br>
&gt; <br>
&gt; On Tue, Jan 05, 2021 at 02:24:14PM +0100, Eduard Metz wrote:<br>
&gt;&gt; Maybe the last column should be &quot;Applicable to Internet&quot;=
 (no / no / yes)<br>
&gt;&gt; or something along these lines. I assume the point here is to indi=
cate that<br>
&gt;&gt; link-local and ULA cannot be used on the Internet.<br>
&gt; <br>
&gt; What is &quot;the Internet&quot;?<br>
&gt; <br>
&gt; We&#39;re an ISP, so if we use ULAs on our infrastructure, outside any=
<br>
&gt; firewalls (but not announcing to other ASes, or leaking packets) - is<=
br>
&gt; that &quot;used on the Internet&quot; or not?<br>
<br>
Agreed that &quot;Applicable to Internet&quot; is probably not a good taxon=
omy.<br>
<br>
The proper (and useful) taxonomy is that of &quot;scope&quot;. ULAs clearly=
 don&#39;t <br>
have a global scope (as per the definition in RFC4007).<br>
<br>
Given a ULA prefix (say, fd12:3456:7890:abcd::/64), it doesn&#39;t globally=
 <br>
(and uniquely) identify a link. Similarly, nobody is in the position of <br=
>
publishing a ROA or restricting which AS can originate packets from such <b=
r>
prefix.<br>
<br>
IMO, generating the &quot;Global ID&quot; of ULAs from a PRNG does reduce t=
he <br>
possibility of collisions *when a limited number of ULA-based networks <br>
are interconnected* -- but the birthday paradox tells you can&#39;t expect =
<br>
the ULA prefixes to be globally unique. There&#39;s more to &quot;global sc=
ope&quot; <br>
than simply asserting that if you interconnect, say, two networks the <br>
chances of colliding prefixes will be small.<br>
<br>
Thanks,<br>
-- <br>
Fernando Gont<br>
SI6 Networks<br>
e-mail: <a href=3D"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si=
6networks.com</a><br>
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492<br>
<br>
<br>
<br>
<br>
</blockquote></div>

--000000000000211a5e05b84b8094--


From nobody Thu Jan  7 03:09:07 2021
Return-Path: <farmer@umn.edu>
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 C1AC93A0F7F for <v6ops@ietfa.amsl.com>; Thu,  7 Jan 2021 03:09:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.398
X-Spam-Level: 
X-Spam-Status: No, score=-4.398 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, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
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 kz7A81vrTu1m for <v6ops@ietfa.amsl.com>; Thu,  7 Jan 2021 03:09:04 -0800 (PST)
Received: from mta-p8.oit.umn.edu (mta-p8.oit.umn.edu [134.84.196.208]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D733E3A0F4D for <v6ops@ietf.org>; Thu,  7 Jan 2021 03:09:03 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mta-p8.oit.umn.edu (Postfix) with ESMTP id 4DBNlg0jhMz9vC9X for <v6ops@ietf.org>; Thu,  7 Jan 2021 11:09:03 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p8.oit.umn.edu ([127.0.0.1]) by localhost (mta-p8.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BdKbju726QRx for <v6ops@ietf.org>; Thu,  7 Jan 2021 05:09:02 -0600 (CST)
Received: from mail-ej1-f72.google.com (mail-ej1-f72.google.com [209.85.218.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p8.oit.umn.edu (Postfix) with ESMTPS id 4DBNlf4TqYz9vC9L for <v6ops@ietf.org>; Thu,  7 Jan 2021 05:09:01 -0600 (CST)
DMARC-Filter: OpenDMARC Filter v1.3.2 mta-p8.oit.umn.edu 4DBNlf4TqYz9vC9L
DKIM-Filter: OpenDKIM Filter v2.11.0 mta-p8.oit.umn.edu 4DBNlf4TqYz9vC9L
Received: by mail-ej1-f72.google.com with SMTP id y14so2280094ejf.11 for <v6ops@ietf.org>; Thu, 07 Jan 2021 03:09:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=cNrAGB4aYnFMnsAbLDyZ5/GVegnHYRzuUqOFB4yRgkQ=; b=qqlhBzf+KT04Qe9xb2DlAGvcQx+btPA4eGB4mPiIdp60WvYHaC80jiMg2qyIPPu3FP T0rVyQrBBWJ3GT32t28f/5w8entD0cSWztwY9Uv3fsNm9pUnurmOhLxDjpNEBhL3nBO+ BYpQNupWfxarJDRcmZa9ezaO/0jLQ8lULGEQzmxp6rUNZoag9z9Tptc6OmfVi+v9OMUE G+uzkqea2M+QE2Vu7S65z1HNGFGIH+WFrBu79ooOAiD27vbj32nWB7AsE0nsTVzwTKEL SS9aroClu2G3GzFbR4Ee8SYbgEa/S2q5WA00i0niPp5Qpa7Wa45oGncEGSKo+8KX2Hcl mauA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=cNrAGB4aYnFMnsAbLDyZ5/GVegnHYRzuUqOFB4yRgkQ=; b=t7D9c4WKpYxmMLyI+TeQ6uNDnML3FEauLBJDbKaBlZ7D9l0MeOjJsQN+eYNDvt55J/ NcWjnYLXTUz2zz5fx3njti3mLm0kJ03JlTbxU6Ug1z7pY9R+lXJitemEwPu4D10vyVkP V+vFL6TqN0ZAuBXu6IC8FvHXOT0g1T6ya50X+23LwLbpeaFs+YfrlqILaYMP+PUa01v0 pDHRguIV4V0tmCnlE8+KStkW1YnIWS1tDIwy4dKkgibFRJ0f2Y4vjPc+S8Jx+E7AoX5K uAWkGir0DNYKL0rGHQkpoHWQ6eRpSY3PdNENJkm21VIzvGDhKuwFdQYZKFe7XY6K3ZQd UPIA==
X-Gm-Message-State: AOAM533sxT6UudIzDhLtMVnVc7Ix/fi1jTjR/D4EDWPYAdCrpkIdoV0h iRqwefIvQRsqtAieM+51Mbrc2Y8A2CtREMeiKSiTlPkC1wqd2BaZLgo/P6MHsj1xgRAwOUlg1xq ARHSbggLLRp6MQLVm1Yqfp2EikA==
X-Received: by 2002:a05:6402:2041:: with SMTP id bc1mr1250142edb.369.1610017739866;  Thu, 07 Jan 2021 03:08:59 -0800 (PST)
X-Google-Smtp-Source: ABdhPJxM1qdJpl0fuqwZuE9ZLpjcN6nuTXgCy0HLPb7zag0jFyD5HuQzvaQQa3ZzKYJMGSO5xcPN/mFjkjZteWOgJkU=
X-Received: by 2002:a05:6402:2041:: with SMTP id bc1mr1250115edb.369.1610017739457;  Thu, 07 Jan 2021 03:08:59 -0800 (PST)
MIME-Version: 1.0
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com> <44e7ac61-523a-d35e-9024-7e6df81e4226@gmail.com> <be92f523-eeaa-8ed4-afdf-4a537f53748c@si6networks.com>
In-Reply-To: <be92f523-eeaa-8ed4-afdf-4a537f53748c@si6networks.com>
From: David Farmer <farmer@umn.edu>
Date: Thu, 7 Jan 2021 05:08:43 -0600
Message-ID: <CAN-Dau2S9pXYAwrRbfT9aMyXPw-NYaOxKF+nXRg_14zqTr8F0g@mail.gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>,  Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>, Mark Smith <markzzzsmith@gmail.com>,  IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007164cf05b84d7792"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/e2KAJSHgbl_8YCUFUrRvWo3gxik>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2021 11:09:06 -0000

--0000000000007164cf05b84d7792
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Sorry for the top post.

Fernando, you are correct that by the definition of global scope in
RFC4007, ULA is not global scope.

However, Brian and RFC4139 are also correct, given the intended
reachability domain for ULA, it has a uniqueness that is many many orders
of magnitude greater than is necessary for the task. So, while not
technically global scope as defined in RFC4007 it is effectively global
scope in any way that matters.

I have an idea for what to call ULA's scope without redefining global scope
in RFC4007, how about we call ULA's scope "pseudo-global" scope.

This gives us;

Link-Local > Site-Local >>>>>> Pseudo-Global > Global

Yes, Site-Local is deprecated, it is just there for comparison. I'm trying
to show that Link-Local and Site-Local are in the same neighborhood, and
pseudo-global and global are in a completely different neighborhood.

Calling ULA pseudo-global scope I believe conveys RFC4139's original intent
without conflicting with the definition of global scope in RFC4007, while
still allowing it to be treated effectively as if it is global scope.

What do other people think?

Thanks.

On Wed, Jan 6, 2021 at 4:24 PM Fernando Gont <fgont@si6networks.com> wrote:

> On 6/1/21 18:30, Brian E Carpenter wrote:
> > Portmanteau reply to multiple messages:
> >
> > On 06-Jan-21 20:07, Lorenzo Colitti wrote: ...
> >> So I guess I'm somewhere between 1) and 3). The specs are
> >> consistent but they fail to consider human behaviour, so they don't
> >> actually work in practice.
> >
> [...]
> >
> > The problem is largely theoretical, and educational for people who
> > train IPv4 users in IPv6 terminology and practices. As Fernando has
> > pointed out, the use of the word "global" is confusing for something
> > that has L for "local" in its name.
>
> There is indeed a terminology issue, which ends up making it complicated
> to explain e.g. the concept of "scope" as a result.
>
>
>
> > On 07-Jan-21 01:17, Ted Lemon wrote: ...
> >> GUA: =E2=80=9Cvalid everywhere on the internet scope=E2=80=9D ULA: =E2=
=80=9Cnot valid
> >> everywhere scope=E2=80=9D LLA: =E2=80=9Cvalid only on this link scope=
=E2=80=9D
> >
> > Friendly amendment:
> >
> > GUA: valid everywhere ULA: Unique Limited-domain Address LLA: valid
> > only on this link
>
> Would certainly also work.
>
>
> > On 07-Jan-21 04:13, Philip Homburg wrote: ...
> >> Some things don't need fixing even if they are not 100% correct.
> >
> > +1
>
> My take is that if the topics is confusing for us, we cannot expect it
> to be any better for others.
>
>
>
> > On 07-Jan-21 05:26, Gert Doering wrote: ...
> >> Why should applications, or anything that is not an admin, care if
> >> an address is a ULA or a GUA?
> >
> > It depends on what you mean by "application". I've written code that
> > explicitly prefers a ULA, and I could imagine a security spec saying
> > "prefer ULA". But anyway, it's not really a problem, is it? (It's
> > annoying to me that in Python, a ULA has .is_global =3D=3D False, but I
> > managed to code round that error.)
>
> The question is: Is it an error?
>
> I've just checked the most "up to date" textbook that I have at hand on
> IPv6. Page 335 has a subsection entitled "Global addresses versus ULAs".
> The discussion in the textbook is indeed fine.
>
> Could one actually make the case that e.g. Python's library should
> change? If it did, it would be counter intuitive. It would match
> RFC4193/4291, but not RFC4007, e.g. the textbook I've checked, and the
> intuitive meaning of private/global.
>
> FWIW, I don't think there's a problem with how ULAs work. But I do think
> that the terminology problem does have ramifications.
>
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>
>
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>


--=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

--0000000000007164cf05b84d7792
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Sorry for the top post.<div><br></div><div>Fernando, you a=
re correct that by the definition=C2=A0of global scope in RFC4007, ULA is n=
ot global scope.</div><div><br></div><div>However, Brian and RFC4139 are al=
so correct, given the intended reachability=C2=A0domain for ULA, it has a u=
niqueness=C2=A0that is many many orders of magnitude=C2=A0greater than is n=
ecessary for the task. So, while not technically=C2=A0global scope as defin=
ed in RFC4007 it is effectively global scope in any way that matters.=C2=A0=
</div><div><br></div><div>I have an idea for what to call ULA&#39;s scope w=
ithout redefining global scope in RFC4007, how about we call ULA&#39;s scop=
e &quot;pseudo-global&quot; scope.</div><div><br></div><div>This gives us;<=
/div><div><br></div><div>Link-Local &gt; Site-Local &gt;&gt;&gt;&gt;&gt;&gt=
; Pseudo-Global &gt; Global</div><div><br></div><div>Yes, Site-Local is dep=
recated, it is just there for comparison. I&#39;m trying to show that Link-=
Local and Site-Local are in the same neighborhood, and pseudo-global=C2=A0a=
nd global are in a completely=C2=A0different=C2=A0neighborhood.</div><div><=
br></div><div>Calling ULA pseudo-global scope I believe conveys RFC4139&#39=
;s original=C2=A0intent without conflicting with the definition=C2=A0of glo=
bal scope in RFC4007, while still allowing it to be treated effectively as =
if it is global scope.</div><div><br></div><div>What do other people=C2=A0t=
hink?</div><div><br></div><div>Thanks.</div></div><br><div class=3D"gmail_q=
uote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jan 6, 2021 at 4:24 PM =
Fernando Gont &lt;<a href=3D"mailto:fgont@si6networks.com">fgont@si6network=
s.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex">On 6/1/21 18:30, Brian E Carpenter wrote:<br>
&gt; Portmanteau reply to multiple messages:<br>
&gt; <br>
&gt; On 06-Jan-21 20:07, Lorenzo Colitti wrote: ...<br>
&gt;&gt; So I guess I&#39;m somewhere between 1) and 3). The specs are<br>
&gt;&gt; consistent but they fail to consider human behaviour, so they don&=
#39;t<br>
&gt;&gt; actually work in practice.<br>
&gt; <br>
[...]<br>
&gt; <br>
&gt; The problem is largely theoretical, and educational for people who<br>
&gt; train IPv4 users in IPv6 terminology and practices. As Fernando has<br=
>
&gt; pointed out, the use of the word &quot;global&quot; is confusing for s=
omething<br>
&gt; that has L for &quot;local&quot; in its name.<br>
<br>
There is indeed a terminology issue, which ends up making it complicated <b=
r>
to explain e.g. the concept of &quot;scope&quot; as a result.<br>
<br>
<br>
<br>
&gt; On 07-Jan-21 01:17, Ted Lemon wrote: ...<br>
&gt;&gt; GUA: =E2=80=9Cvalid everywhere on the internet scope=E2=80=9D ULA:=
 =E2=80=9Cnot valid<br>
&gt;&gt; everywhere scope=E2=80=9D LLA: =E2=80=9Cvalid only on this link sc=
ope=E2=80=9D<br>
&gt; <br>
&gt; Friendly amendment:<br>
&gt; <br>
&gt; GUA: valid everywhere ULA: Unique Limited-domain Address LLA: valid<br=
>
&gt; only on this link<br>
<br>
Would certainly also work.<br>
<br>
<br>
&gt; On 07-Jan-21 04:13, Philip Homburg wrote: ...<br>
&gt;&gt; Some things don&#39;t need fixing even if they are not 100% correc=
t.<br>
&gt; <br>
&gt; +1<br>
<br>
My take is that if the topics is confusing for us, we cannot expect it <br>
to be any better for others.<br>
<br>
<br>
<br>
&gt; On 07-Jan-21 05:26, Gert Doering wrote: ...<br>
&gt;&gt; Why should applications, or anything that is not an admin, care if=
<br>
&gt;&gt; an address is a ULA or a GUA?<br>
&gt; <br>
&gt; It depends on what you mean by &quot;application&quot;. I&#39;ve writt=
en code that<br>
&gt; explicitly prefers a ULA, and I could imagine a security spec saying<b=
r>
&gt; &quot;prefer ULA&quot;. But anyway, it&#39;s not really a problem, is =
it? (It&#39;s<br>
&gt; annoying to me that in Python, a ULA has .is_global =3D=3D False, but =
I<br>
&gt; managed to code round that error.)<br>
<br>
The question is: Is it an error?<br>
<br>
I&#39;ve just checked the most &quot;up to date&quot; textbook that I have =
at hand on <br>
IPv6. Page 335 has a subsection entitled &quot;Global addresses versus ULAs=
&quot;.<br>
The discussion in the textbook is indeed fine.<br>
<br>
Could one actually make the case that e.g. Python&#39;s library should <br>
change? If it did, it would be counter intuitive. It would match <br>
RFC4193/4291, but not RFC4007, e.g. the textbook I&#39;ve checked, and the =
<br>
intuitive meaning of private/global.<br>
<br>
FWIW, I don&#39;t think there&#39;s a problem with how ULAs work. But I do =
think <br>
that the terminology problem does have ramifications.<br>
<br>
-- <br>
Fernando Gont<br>
SI6 Networks<br>
e-mail: <a href=3D"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si=
6networks.com</a><br>
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6ops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D<br>David Farmer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0=C2=A0 <a href=3D"mailto:Email%3Afarmer@umn.edu" target=3D"_blank">E=
mail:farmer@umn.edu</a><br>Networking &amp; Telecommunication Services<br>O=
ffice of Information Technology<br>University of Minnesota=C2=A0=C2=A0 <br>=
2218 University Ave SE=C2=A0 =C2=A0 =C2=A0 =C2=A0 Phone: 612-626-0815<br>Mi=
nneapolis, MN 55414-3029=C2=A0=C2=A0 Cell: 612-812-9952<br>=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D </div>

--0000000000007164cf05b84d7792--


From nobody Thu Jan  7 03:27:02 2021
Return-Path: <nick@foobar.org>
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 CBEF33A0FB8; Thu,  7 Jan 2021 03:26:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.162
X-Spam-Level: 
X-Spam-Status: No, score=-2.162 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-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 9hZcOI2iCbIa; Thu,  7 Jan 2021 03:26:54 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [46.182.8.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D011A3A0FB6; Thu,  7 Jan 2021 03:26:53 -0800 (PST)
X-Envelope-To: v6ops@ietf.org
Received: from crumpet.local (admin.ibn.ie [46.182.8.8]) (authenticated bits=0) by mail.netability.ie (8.16.1/8.16.1) with ESMTPSA id 107BQne7079755 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Jan 2021 11:26:50 GMT (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host admin.ibn.ie [46.182.8.8] claimed to be crumpet.local
To: David Farmer <farmer=40umn.edu@dmarc.ietf.org>
Cc: Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com> <44e7ac61-523a-d35e-9024-7e6df81e4226@gmail.com> <be92f523-eeaa-8ed4-afdf-4a537f53748c@si6networks.com> <CAN-Dau2S9pXYAwrRbfT9aMyXPw-NYaOxKF+nXRg_14zqTr8F0g@mail.gmail.com>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <73bd1a42-d9e7-2d24-9689-e053f11a3a0e@foobar.org>
Date: Thu, 7 Jan 2021 11:26:48 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:52.0) Gecko/20100101 PostboxApp/7.0.43
MIME-Version: 1.0
In-Reply-To: <CAN-Dau2S9pXYAwrRbfT9aMyXPw-NYaOxKF+nXRg_14zqTr8F0g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/3V3WLnALruRJG0j47x-oVrMzZzE>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2021 11:26:57 -0000

David Farmer wrote on 07/01/2021 11:08:
> What do other people think?

that ULA is a poor idea to start with, and that attempting to 
encapsulate its scope characteristics within 1, or 2, or even 3 words is 
unlikely to succeed in a way which encompasses its full subtlety.  We 
are better off sticking with a particular phrase (the exact choice of 
which will end up disappointing some or maybe lots of people) and then 
defining what that means in free-text.  This seems to be what 
draft-gont-6man-ipv6-ula-scope is attempting to do.

Nick


From nobody Thu Jan  7 05:08:22 2021
Return-Path: <mellon@fugue.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 B99C83A1086 for <v6ops@ietfa.amsl.com>; Thu,  7 Jan 2021 05:08:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 8hupmRw9y1IN for <v6ops@ietfa.amsl.com>; Thu,  7 Jan 2021 05:08:14 -0800 (PST)
Received: from mail-il1-x12d.google.com (mail-il1-x12d.google.com [IPv6:2607:f8b0:4864:20::12d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F8D03A1085 for <v6ops@ietf.org>; Thu,  7 Jan 2021 05:08:09 -0800 (PST)
Received: by mail-il1-x12d.google.com with SMTP id t3so2507716ilh.9 for <v6ops@ietf.org>; Thu, 07 Jan 2021 05:08:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=HXOk9zpsltNr56BSv3WdZM/7EMy6eG3cO3azLkmWbzY=; b=s8YRhV7SLLm9qvgFs6GUhYBRTymnT0yIh1Or4NWHi0udhXxcNk1mc3evc4usppEWkl sRfjJ0VcNLjYSHjjnyBiFCHXWPJ6dBIbPOpGcWPHzLdZVHRIRuNJOl+Yv8dOtuIbnOIa Kh/fuD2fH7Xmdg+Vz5n2YNCR9sTzmTz22RDNUFmNXR7BIIFs0kXdoCVab/uKwEjOKNyD xsp/utOsazpAk69scWFLeDimROC+Fq77gvfTyir+vulYcNjB4hMD+JwsD8XmpsIggUhT hClFAKzfON6aXTNfXVJ8dHVUEvHwvhoagZxWGDeSdh/iAwBm+ybgagm8tT1GhuJhjpbQ 6/sA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=HXOk9zpsltNr56BSv3WdZM/7EMy6eG3cO3azLkmWbzY=; b=Yjqa0OyMRa8FhMZ/bkwQqxCGJ1JtfaBFvCkpTCFHulki1NIHhS5KymZbvFAnlmhl+4 61oeyTVIvUDIwptz2enh74FvRiEk38ZuUwX8kxXwuxshEiq98q7L3UD4XPBPT+0D0NdJ 4YcCNt+V1PRiC7xCASk5qIflAzKAifGuX2sf+ihSE1jdp+I3Qm+v+DNRSi9UvKhPv9bT /9lusQnn38XzeFspYW52RTTGfLYHJZtIcJkAmo0/mWuIi7h59yI9rj8Z14IxATX5PN+l ZZ3ZBOW0/2Ocs7KlXmmKrBfWGg4f12fg9iVsipBf/H0ZYiT4p+3eRDATvKRj+s1JVChh 95RQ==
X-Gm-Message-State: AOAM530O80pRBud4cJUC8JC8TrTKfHNotsIOQJvfHCCrqm0IoPnJmMWs OWO7DVxDcv187cc55+56FLkXOA==
X-Google-Smtp-Source: ABdhPJyexQvE2MSBunyO7opsHvBakyZHb+8tHdWd7Tful9L20a26Xbb237Tj1iv9VYJg0zhhQFYVIg==
X-Received: by 2002:a05:6e02:20cc:: with SMTP id 12mr9134824ilq.91.1610024888499;  Thu, 07 Jan 2021 05:08:08 -0800 (PST)
Received: from [192.168.4.70] (c-24-91-177-160.hsd1.nh.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id f20sm4442509ilj.14.2021.01.07.05.08.07 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Jan 2021 05:08:07 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <6F3726EE-F089-4F26-BB30-F22686617C03@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_DC93ABDD-F5B5-405A-BCB2-0DC40F61D11C"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.2\))
Date: Thu, 7 Jan 2021 08:08:05 -0500
In-Reply-To: <m1kxTmy-0000KhC@stereo.hq.phicoh.net>
Cc: IPv6 List <ipv6@ietf.org>, IPv6 Operations <v6ops@ietf.org>, Mark Andrews <marka@isc.org>
To: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net> <CAHL_VyD85e9=taY1XENf7hc=BXRyD_7JJFDCW2Oq_a0z3hYqUA@mail.gmail.com> <bc29edad-b57b-bb53-141b-8f58c5ca2526@si6networks.com> <91424EEE-EF12-4B5B-ADE4-38230E049290@isc.org> <m1kxTmy-0000KhC@stereo.hq.phicoh.net>
X-Mailer: Apple Mail (2.3654.60.0.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/tpYBZAJfBdA_2W7J_vDhCaD8Qt4>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2021 13:08:18 -0000

--Apple-Mail=_DC93ABDD-F5B5-405A-BCB2-0DC40F61D11C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Jan 7, 2021, at 6:49 AM, Philip Homburg =
<pch-ipv6-ietf-7@u-1.phicoh.com> wrote:
> This looks nice, but I wonder how hard it is for this to get traction.

And for that matter how hard it would be to implement, and what the =
benefit would be, versus the drawbacks. Most of the time when people do =
split DNS, it=E2=80=99s because they want information behind the =
firewall to be invisible globally not so much for operational reasons =
(because they wouldn=E2=80=99t work) but because they don=E2=80=99t want =
to reveal the inner workings of the network behind the firewall. So even =
if this feature Mark=E2=80=99s proposing were widely implemented in host =
resolvers (which it would have to be to be useful), and even if we had =
the technology to actually populate this sort of information accurately =
in the DNS, I think most people who operate DNS servers that could in =
principle advertise non-global addresses this way would choose not to. =
So yeah, I=E2=80=99d predict not much uptake.

On Jan 7, 2021, at 6:26 AM, Nick Hilliard <nick@foobar.org> wrote:
> that ULA is a poor idea to start with, and that attempting to =
encapsulate its scope characteristics within 1, or 2, or even 3 words is =
unlikely to succeed in a way which encompasses its full subtlety.  We =
are better off sticking with a particular phrase (the exact choice of =
which will end up disappointing some or maybe lots of people) and then =
defining what that means in free-text.  This seems to be what =
draft-gont-6man-ipv6-ula-scope is attempting to do.


If you mean =E2=80=9Cthe name ULA is a poor idea=E2=80=9D then I would =
tend to agree, although not vehemently. I definitely agree that trying =
to mechanically define the scope of a ULA is impossible.

On Jan 6, 2021, at 9:51 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>> I've just checked the most "up to date" textbook that I have at hand =
on=20
>> IPv6. Page 335 has a subsection entitled "Global addresses versus =
ULAs".
>> The discussion in the textbook is indeed fine.
>>=20
>> Could one actually make the case that e.g. Python's library should=20
>> change? If it did, it would be counter intuitive. It would match=20
>> RFC4193/4291, but not RFC4007, e.g. the textbook I've checked, and =
the=20
>> intuitive meaning of private/global.
>=20
> That's of course exactly why the term "globally reachable" was added
> by RFC8190. My objection to the Python library is not that it provides
> the property .is_private, which is very clear, but that it asserts =
that
> =
ipaddress.IPv6Address("fd63:45eb:dc14:0:8546:6ab7:1529:b435").is_global
> is False. Because according to the Proposed Standard RFCs,
> ULAs are both private and global.
>=20
> Unfortunately I don't think it's reasonable to ask for a =
non-backwards-
> compatible change in the Python library. If you were maintaining such
> a widely used library, would you want to break compatibility?

I=E2=80=99d be really curious to know how this is used, and whether it =
works. I suspect it works poorly, and hence backwards compatibility is =
not an issue, but without knowing how it=E2=80=99s actually used, who =
can really say? What does my code do if is_global is false? If it is =
true? Is it possible that because of this library, connections that =
could be made aren=E2=80=99t being made, because a valid, usable address =
is being ignored?=

--Apple-Mail=_DC93ABDD-F5B5-405A-BCB2-0DC40F61D11C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><font=
 face=3D"PalatinoLinotype-Roman" class=3D"">On Jan 7, 2021, at 6:49 AM, =
Philip Homburg &lt;<a href=3D"mailto:pch-ipv6-ietf-7@u-1.phicoh.com" =
class=3D"">pch-ipv6-ietf-7@u-1.phicoh.com</a>&gt; =
wrote:</font><div><blockquote type=3D"cite" class=3D""><div =
class=3D""><font face=3D"PalatinoLinotype-Roman" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">This looks nice, but I wonder how hard it is for this to get =
traction.</span><br style=3D"caret-color: rgb(0, 0, 0); font-size: 14px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D""></font></div></blockquote></div><font =
face=3D"PalatinoLinotype-Roman" class=3D""><br class=3D""></font><div =
class=3D""><font face=3D"PalatinoLinotype-Roman" class=3D"">And for that =
matter how hard it would be to implement, and what the benefit would be, =
versus the drawbacks. Most of the time when people do split DNS, it=E2=80=99=
s because they want information behind the firewall to be invisible =
globally not so much for operational reasons (because they wouldn=E2=80=99=
t work) but because they don=E2=80=99t want to reveal the inner workings =
of the network behind the firewall. So even if this feature Mark=E2=80=99s=
 proposing were widely implemented in host resolvers (which it would =
have to be to be useful), and even if we had the technology to actually =
populate this sort of information accurately in the DNS, I think most =
people who operate DNS servers that could in principle advertise =
non-global addresses this way would choose not to. So yeah, I=E2=80=99d =
predict not much uptake.</font></div><div class=3D""><font =
face=3D"PalatinoLinotype-Roman" class=3D""><br =
class=3D""></font></div><div class=3D""><font =
face=3D"PalatinoLinotype-Roman" class=3D"">On Jan 7, 2021, at 6:26 AM, =
Nick Hilliard &lt;<a href=3D"mailto:nick@foobar.org" =
class=3D"">nick@foobar.org</a>&gt; wrote:</font></div><div =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><span =
class=3D"" style=3D"float: none; display: inline !important;"><font =
face=3D"PalatinoLinotype-Roman" class=3D"">that ULA is a poor idea to =
start with, and that attempting to encapsulate its scope characteristics =
within 1, or 2, or even 3 words is unlikely to succeed in a way which =
encompasses its full subtlety. &nbsp;We are better off sticking with a =
particular phrase (the exact choice of which will end up disappointing =
some or maybe lots of people) and then defining what that means in =
free-text. &nbsp;This seems to be what draft-gont-6man-ipv6-ula-scope is =
attempting to do.</font></span></div></blockquote></div><div =
class=3D""><div class=3D""><span class=3D"" style=3D"float: none; =
display: inline !important;"><font face=3D"PalatinoLinotype-Roman" =
class=3D""><br class=3D""></font></span></div></div><div class=3D""><span =
class=3D"" style=3D"float: none; display: inline !important;"><font =
face=3D"PalatinoLinotype-Roman" class=3D"">If you mean =E2=80=9Cthe name =
ULA is a poor idea=E2=80=9D then I would tend to agree, although not =
vehemently. I definitely agree that trying to mechanically define the =
scope of a ULA is impossible.</font></span></div><div class=3D""><span =
class=3D"" style=3D"float: none; display: inline !important;"><font =
face=3D"PalatinoLinotype-Roman" class=3D""><br =
class=3D""></font></span></div><div class=3D""><span class=3D"" =
style=3D"float: none; display: inline !important;"><div class=3D""><font =
face=3D"PalatinoLinotype-Roman" class=3D"">On Jan 6, 2021, at 9:51 PM, =
Brian E Carpenter &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" =
class=3D"">brian.e.carpenter@gmail.com</a>&gt; =
wrote:</font></div><blockquote type=3D"cite" class=3D""><div =
class=3D""><blockquote type=3D"cite" class=3D""><font =
face=3D"PalatinoLinotype-Roman" class=3D"">I've just checked the most =
"up to date" textbook that I have at hand on&nbsp;<br class=3D"">IPv6. =
Page 335 has a subsection entitled "Global addresses versus ULAs".<br =
class=3D"">The discussion in the textbook is indeed fine.<br =
class=3D""><br class=3D"">Could one actually make the case that e.g. =
Python's library should&nbsp;<br class=3D"">change? If it did, it would =
be counter intuitive. It would match&nbsp;<br class=3D"">RFC4193/4291, =
but not RFC4007, e.g. the textbook I've checked, and the&nbsp;<br =
class=3D"">intuitive meaning of private/global.<br =
class=3D""></font></blockquote><font face=3D"PalatinoLinotype-Roman" =
class=3D""><br class=3D""><span class=3D"" style=3D"float: none; =
display: inline !important;">That's of course exactly why the term =
"globally reachable" was added</span><br class=3D""><span class=3D"" =
style=3D"float: none; display: inline !important;">by RFC8190. My =
objection to the Python library is not that it provides</span><br =
class=3D""><span class=3D"" style=3D"float: none; display: inline =
!important;">the property .is_private, which is very clear, but that it =
asserts that</span><br class=3D""><span class=3D"" style=3D"float: none; =
display: inline =
!important;">ipaddress.IPv6Address("fd63:45eb:dc14:0:8546:6ab7:1529:b435")=
.is_global</span><br class=3D""><span class=3D"" style=3D"float: none; =
display: inline !important;">is False. Because according to the Proposed =
Standard RFCs,</span><br class=3D""><span class=3D"" style=3D"float: =
none; display: inline !important;">ULAs are both private and =
global.</span><br class=3D""><br class=3D""><span class=3D"" =
style=3D"float: none; display: inline !important;">Unfortunately I don't =
think it's reasonable to ask for a non-backwards-</span><br =
class=3D""><span class=3D"" style=3D"float: none; display: inline =
!important;">compatible change in the Python library. If you were =
maintaining such</span><br class=3D""><span class=3D"" style=3D"float: =
none; display: inline !important;">a widely used library, would you want =
to break compatibility?</span><br =
class=3D""></font></div></blockquote><div class=3D""><div class=3D""><span=
 class=3D"" style=3D"font-family: UbuntuMono-Regular; float: none; =
display: inline !important;"><br class=3D""></span></div></div><div =
class=3D""><span class=3D"" style=3D"font-family: UbuntuMono-Regular; =
float: none; display: inline !important;">I=E2=80=99d be really curious =
to know how this is used, and whether it works. I suspect it works =
poorly, and hence backwards compatibility is not an issue, but without =
knowing how it=E2=80=99s actually used, who can really say? What does my =
code do if is_global is false? If it is true? Is it possible that =
because of this library, connections that could be made aren=E2=80=99t =
being made, because a valid, usable address is being =
ignored?</span></div></span></div></body></html>=

--Apple-Mail=_DC93ABDD-F5B5-405A-BCB2-0DC40F61D11C--


From nobody Thu Jan  7 07:09:08 2021
Return-Path: <mellon@fugue.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 C54543A11FC for <v6ops@ietfa.amsl.com>; Thu,  7 Jan 2021 07:09:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 Da9HP5do_7wQ for <v6ops@ietfa.amsl.com>; Thu,  7 Jan 2021 07:09:00 -0800 (PST)
Received: from mail-qt1-x836.google.com (mail-qt1-x836.google.com [IPv6:2607:f8b0:4864:20::836]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2227F3A11EF for <v6ops@ietf.org>; Thu,  7 Jan 2021 07:09:00 -0800 (PST)
Received: by mail-qt1-x836.google.com with SMTP id b9so4410415qtr.2 for <v6ops@ietf.org>; Thu, 07 Jan 2021 07:09:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=i/xEVBkSieHZArJg8d3oJd2WhMQxpjhvY8+lzHUpDWg=; b=NEYlJ1RT9rcLO8WdESHVD5gmEiSPslWDLLKDVneWUICINTMP2W0BVS8o9K/oWGd04X bNvHxElMhwV7Wj5nA3dya+P6X00Z5XMuyJ1wGZUpLXPKzsZL+61lmBLr+VpkWKEr10zX B3Zf5uLBOpl1VC4SGn4OaWV2Bw7q5zcprtTN8qVhRs4IgAq4/YmGH+YCPGKdTnFaeO94 dQmfcBpmdCfSu8LwtT5lee3faKO67EHdp8yi4uvu9MTJD1f2h6AHKFb2arbGTDdPlwju npjcl5mv6mJLwqDSs+SRrQsLT1dxbp/iWzb5netN+JC9CZ+rmpRHtkkwkhKaaJuwbWz2 zQLQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=i/xEVBkSieHZArJg8d3oJd2WhMQxpjhvY8+lzHUpDWg=; b=Pw6jctNJBZkbh+8JYR+lWTJNPtzxDfCPXFW4Ksz/gVE5Y9V9JqhfH/MK2BjyiPL2pv IZ8yIktMxQ+m1/0qDi2ozyn8Exts5NyvhSJhRv+NWEF4KaeDi8lYgrU9rDK3cDN/iyii 65Lx/JFD0NVcazS+73Hxl9X/bBIUMMzS18DeJmsQHEmwrEI1BXVx8/Wy+nHzDelK5XtK 4svegMw/SLNzQ6iLomakninocC658tzo2zOP66NQiuOffuJs0HK6L3Wscrt1NfJMtixa g4MOgxLhBIzsetCQv+TQ3q3q6mvIi76vHIqa4Ks0LnUZdEjhbnJVAIvxeEgdUeU7ZTGU 6LEA==
X-Gm-Message-State: AOAM531xX6P6QdiQaK/6OLazvs06IAHAGH1SPYg0G0dPMmO0NoZXYc/b 2YAh1z6X9rMxCAuz3CqjCAPLHoHtnn8sFQ==
X-Google-Smtp-Source: ABdhPJxJZ5tXCkLrHP76EIBlwK0wUSI3A6bNT2GfpPFHwIQ+sKAjRYCGWKaBargVi/6VvzVHrLGFQA==
X-Received: by 2002:ac8:47da:: with SMTP id d26mr8681000qtr.4.1610032139164; Thu, 07 Jan 2021 07:08:59 -0800 (PST)
Received: from mithrandir.lan (c-24-91-177-160.hsd1.nh.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id c2sm3196157qke.109.2021.01.07.07.08.58 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Jan 2021 07:08:58 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <BE6C041F-94B2-400D-B114-A76962190660@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_6C76C077-BFCE-4960-8931-385B55739E09"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.2\))
Date: Thu, 7 Jan 2021 10:08:56 -0500
In-Reply-To: <m1kxWh9-0000ImC@stereo.hq.phicoh.net>
Cc: IPv6 List <ipv6@ietf.org>, IPv6 Operations <v6ops@ietf.org>
To: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net> <CAHL_VyD85e9=taY1XENf7hc=BXRyD_7JJFDCW2Oq_a0z3hYqUA@mail.gmail.com> <bc29edad-b57b-bb53-141b-8f58c5ca2526@si6networks.com> <91424EEE-EF12-4B5B-ADE4-38230E049290@isc.org> <m1kxTmy-0000KhC@stereo.hq.phicoh.net> <6F3726EE-F089-4F26-BB30-F22686617C03@fugue.com> <m1kxWh9-0000ImC@stereo.hq.phicoh.net>
X-Mailer: Apple Mail (2.3654.60.0.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/kJwWWszFotOg3v0t5UYqYGIzens>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2021 15:09:04 -0000

--Apple-Mail=_6C76C077-BFCE-4960-8931-385B55739E09
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Jan 7, 2021, at 9:55 AM, Philip Homburg =
<pch-ipv6-ietf-7@u-1.phicoh.com> wrote:
> I can see a few benefits of Mark's proposal. One is that it is good to
> have a standard representation of information. In particular,
> Mark's proposal would make it possible to have a master zone file that =
has
> both public and private DNS entries. Then a split-DNS server could =
serve
> only the public data to the outside world.=20

That=E2=80=99s a good point, although it would still be a good point if =
this were just a feature of the zone file and not of the wire format.

> At the same time, I think it would be great if we can put link-local =
addresses
> in DNS.=20

That sounds like a really heavy lift.

> It may tie in nicely with scope IDs in socket addresses. If a DNS
> record specifies that is valid only on a VPN link, then maybe we can =
already
> tie the address to that link. No need to change applications, it can =
be
> hidden in the stub resolver.

Now we need to standardize a way to identify links. This is a Hard =
Problem. I say this based on experience, not supposition. HNCP tried to =
do this, not as successfully as I=E2=80=99d hoped. I=E2=80=99ve been =
working on it for the Thread Border Router work, and haven=E2=80=99t =
come up with a general solution. Sure, if you have a data center and a =
managed multi-subnet LAN, and you can just type in configurations, this =
works, but most networks aren=E2=80=99t like that.  I think the VPN case =
is probably tractable, but it=E2=80=99s really hard to see a path to =
broad adoption for this idea.

If there is a path to broad adoption, it probably involves bottom-up =
work, not top-down design. Most of the ideas I=E2=80=99ve had about this =
that I think are practicable are very context-dependent. E.g., you can =
identify that you are on the same link because you received a =
link-scoped multicast.


--Apple-Mail=_6C76C077-BFCE-4960-8931-385B55739E09
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">On =
Jan 7, 2021, at 9:55 AM, Philip Homburg &lt;<a =
href=3D"mailto:pch-ipv6-ietf-7@u-1.phicoh.com" =
class=3D"">pch-ipv6-ietf-7@u-1.phicoh.com</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><meta charset=3D"UTF-8" =
class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">I can see a =
few benefits of Mark's proposal. One is that it is good to</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; =
font-size: 14px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">have a =
standard representation of information. In particular,</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; =
font-size: 14px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">Mark's =
proposal would make it possible to have a master zone file that =
has</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">both public =
and private DNS entries. Then a split-DNS server could serve</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; =
font-size: 14px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">only the =
public data to the outside world.<span =
class=3D"Apple-converted-space">&nbsp;</span></span></div></blockquote></d=
iv><br class=3D""><div class=3D"">That=E2=80=99s a good point, although =
it would still be a good point if this were just a feature of the zone =
file and not of the wire format.</div><div class=3D""><br =
class=3D""></div><div class=3D""><blockquote type=3D"cite" =
class=3D""><span style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0); font-family: Menlo-Regular;" class=3D"">At the same time, I think it =
would be great if we can put link-local addresses</span><br =
style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: =
Menlo-Regular;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); =
color: rgb(0, 0, 0); font-family: Menlo-Regular;" class=3D"">in =
DNS.&nbsp;</span></blockquote><br class=3D""></div><div class=3D"">That =
sounds like a really heavy lift.</div><div class=3D""><br =
class=3D""></div><div class=3D""><blockquote type=3D"cite" =
class=3D""><span style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0); font-family: Menlo-Regular;" class=3D"">It may tie in nicely with =
scope IDs in socket addresses. If a DNS</span><br style=3D"caret-color: =
rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Menlo-Regular;" =
class=3D""><span style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0); font-family: Menlo-Regular;" class=3D"">record specifies that is =
valid only on a VPN link, then maybe we can already</span><br =
style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: =
Menlo-Regular;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); =
color: rgb(0, 0, 0); font-family: Menlo-Regular;" class=3D"">tie the =
address to that link. No need to change applications, it can =
be</span><br style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); =
font-family: Menlo-Regular;" class=3D""><span style=3D"caret-color: =
rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Menlo-Regular;" =
class=3D"">hidden in the stub resolver.</span></blockquote><br =
class=3D""></div><div class=3D"">Now we need to standardize a way to =
identify links. This is a Hard Problem. I say this based on experience, =
not supposition. HNCP tried to do this, not as successfully as I=E2=80=99d=
 hoped. I=E2=80=99ve been working on it for the Thread Border Router =
work, and haven=E2=80=99t come up with a general solution. Sure, if you =
have a data center and a managed multi-subnet LAN, and you can just type =
in configurations, this works, but most networks aren=E2=80=99t like =
that. &nbsp;I think the VPN case is probably tractable, but it=E2=80=99s =
really hard to see a path to broad adoption for this idea.</div><div =
class=3D""><br class=3D""></div><div class=3D"">If there is a path to =
broad adoption, it probably involves bottom-up work, not top-down =
design. Most of the ideas I=E2=80=99ve had about this that I think are =
practicable are very context-dependent. E.g., you can identify that you =
are on the same link because you received a link-scoped =
multicast.</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_6C76C077-BFCE-4960-8931-385B55739E09--


From nobody Thu Jan  7 08:03:21 2021
Return-Path: <mcr+ietf@sandelman.ca>
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 1E2DC3A12C0; Thu,  7 Jan 2021 08:03:09 -0800 (PST)
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, SPF_HELO_NONE=0.001, 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 bicmG910BXzH; Thu,  7 Jan 2021 08:03:07 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0B593A12AE; Thu,  7 Jan 2021 08:03:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 294EB389B1; Thu,  7 Jan 2021 11:04:14 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id v9VENTIA8t2c; Thu,  7 Jan 2021 11:04:13 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id B013A389B0; Thu,  7 Jan 2021 11:04:13 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 99BB864F; Thu,  7 Jan 2021 11:03:03 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ted Lemon <mellon@fugue.com>, IPv6 Operations <v6ops@ietf.org>, IPv6 List <ipv6@ietf.org>
In-Reply-To: <BE6C041F-94B2-400D-B114-A76962190660@fugue.com>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net> <CAHL_VyD85e9=taY1XENf7hc=BXRyD_7JJFDCW2Oq_a0z3hYqUA@mail.gmail.com> <bc29edad-b57b-bb53-141b-8f58c5ca2526@si6networks.com> <91424EEE-EF12-4B5B-ADE4-38230E049290@isc.org> <m1kxTmy-0000KhC@stereo.hq.phicoh.net> <6F3726EE-F089-4F26-BB30-F22686617C03@fugue.com> <m1kxWh9-0000ImC@stereo.hq.phicoh.net> <BE6C041F-94B2-400D-B114-A76962190660@fugue.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Thu, 07 Jan 2021 11:03:03 -0500
Message-ID: <21510.1610035383@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/uI4LjDSKT_tiuWCc2CWbfZ9FIhE>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2021 16:03:15 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Ted Lemon <mellon@fugue.com> wrote:
    > On Jan 7, 2021, at 9:55 AM, Philip Homburg <pch-ipv6-ietf-7@u-1.phico=
h.com> wrote:
    >> I can see a few benefits of Mark's proposal. One is that it is good =
to
    >> have a standard representation of information. In particular,
    >> Mark's proposal would make it possible to have a master zone file th=
at has
    >> both public and private DNS entries. Then a split-DNS server could s=
erve
    >> only the public data to the outside world.

    > That=E2=80=99s a good point, although it would still be a good point =
if this
    > were just a feature of the zone file and not of the wire format.

No, it has to get into the wire format, and it has to be cachable on the
client, and it has to evaluated on the client as close to the application as
possible.

Why? because caching is good, and throwing away your cache each time you ha=
ve
a link up/down is dumb in my opinion.

Having said that, I think it's mostly too late to make a change like this.
Convince me wrong with deployed code :-)

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide





--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl/3MLcACgkQgItw+93Q
3WUZNAgAmRcfDoJPKptPZRSx1TbWMgnd9pO7ZTw3alYeIYRVpdA8HaPuA5IMUzN1
AzvpilgTH53W+k/fn3B841UGGZSLfnaM5RqDFD4wpnM978dyN8/uMhMRZ//aBiGU
4OKr5PnMgUTrbEpmq0tsN2tXYY3zeOggLlnuyVektp8nbUpCouEkhnblS2iDwnVT
3jAcZIYos8OtFgECH2Ev2TVZflRFG+L9VlcIllhIQVtsDLF9uUEaJ0NYPbQlw1Q7
PmSrSSYaNqjiqNYR9TAAQ3lI9ahX1FQaHrR7/0GIhTJ5eUIqsDh2f6pcx2Jg9BzE
U5+qYXT7/7uqcWJqZxuvkYJUCokJ0w==
=6HWX
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Jan  7 09:00:54 2021
Return-Path: <mellon@fugue.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 D58023A129F for <v6ops@ietfa.amsl.com>; Thu,  7 Jan 2021 09:00:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 OalOb_Qxpwox for <v6ops@ietfa.amsl.com>; Thu,  7 Jan 2021 09:00:45 -0800 (PST)
Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AC733A1294 for <v6ops@ietf.org>; Thu,  7 Jan 2021 09:00:44 -0800 (PST)
Received: by mail-qk1-x736.google.com with SMTP id 186so6050402qkj.3 for <v6ops@ietf.org>; Thu, 07 Jan 2021 09:00:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=0zjDd9zBeMMx7wlSt7B/rMozcs8c0Djrh+/nOzBJwcM=; b=fxveEez1yVPCpFfGoEB6M6EJQz6smV8H2ZvSp03zyCpdWQFU8JuAu+2tb2fKHWD+Pw h2K/Kk5wbM/RIbG5b27HIleoISs6MrVK8wGdRqeg7nM4LnEAZFsFzRrgSQxKPfaRqIiD zyRGwaYBbZxf9zqYFYEbzWvY+mopHgkdOxGgmYrE6bWGXgP9oP1cH3ihgJfE/yzZQJqM BcXpX0JUsZRgvNjkLSIsBXRJU2qLUP5ehAtiDQ/YnlGwLvTLlBuo4fikn0H+E+rOazpJ IllnMy6zfI0ILucGIPvHawRuZaC0pW5HMjHhqtbscj/OIwd9jMAFF7/13UolbXb9tiq3 skXQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=0zjDd9zBeMMx7wlSt7B/rMozcs8c0Djrh+/nOzBJwcM=; b=ZgH9KgcmQ2MvfjwbjXtyUFvZtcGItgnwiPRmF4s1EMfm3RYLSfhX54TkPEvKuOaXrS NjAlVkp+wFZ1sYkDgZsIJQ21TbU1M6jUpl66W7JGFJeYEt05CeXxUEbeN7nqoNYJLLhv Nw1IppIaqMbpV/M+Q/MymD7Gh7jR11c8MpK8JvppFXWykqnFOkBue5DvVqG6e8j1S0HF P3jT2jd8QoarrZXZNyvPA3cTaCnew24WRUZJmKq8XNZ2mSOpDK4EyxFtFqMdJO5zyvun Hj30/xxA/a3FEBfsIVyOSQmgFzhBGC4yUwTpI4ErjQ91V9WkkHxz3wHsxP7stIZ3IkPL eZ6A==
X-Gm-Message-State: AOAM532Ic7HsuOfaPMWPI/OJNFcSblQx8ERQ1g02NtgqaBwiI1Qg9ff/ wEhVvCSp6iRHp9LnWLuApIOpcA==
X-Google-Smtp-Source: ABdhPJyKLEZDW5P8ewdnNcg/RMV+RD28BFdoK91zy6NfGsWC/sYybnLtrOWO5kkIfMAfwJj/j8cJiw==
X-Received: by 2002:a05:620a:2297:: with SMTP id o23mr10099066qkh.149.1610038843972;  Thu, 07 Jan 2021 09:00:43 -0800 (PST)
Received: from mithrandir.lan (c-24-91-177-160.hsd1.nh.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id p15sm3356844qke.11.2021.01.07.09.00.42 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Jan 2021 09:00:42 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <48FF13BF-D878-4706-BB62-429273AD0EBE@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4CCC9A5D-F6AB-494A-AFDD-6B29A4F37DAF"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.2\))
Date: Thu, 7 Jan 2021 12:00:42 -0500
In-Reply-To: <21510.1610035383@localhost>
Cc: IPv6 Operations <v6ops@ietf.org>, IPv6 List <ipv6@ietf.org>
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net> <CAHL_VyD85e9=taY1XENf7hc=BXRyD_7JJFDCW2Oq_a0z3hYqUA@mail.gmail.com> <bc29edad-b57b-bb53-141b-8f58c5ca2526@si6networks.com> <91424EEE-EF12-4B5B-ADE4-38230E049290@isc.org> <m1kxTmy-0000KhC@stereo.hq.phicoh.net> <6F3726EE-F089-4F26-BB30-F22686617C03@fugue.com> <m1kxWh9-0000ImC@stereo.hq.phicoh.net> <BE6C041F-94B2-400D-B114-A76962190660@fugue.com> <21510.1610035383@localhost>
X-Mailer: Apple Mail (2.3654.60.0.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/PfUbEOYun29FqNBTQOWC-BXN-xw>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2021 17:00:48 -0000

--Apple-Mail=_4CCC9A5D-F6AB-494A-AFDD-6B29A4F37DAF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Jan 7, 2021, at 11:03 AM, Michael Richardson <mcr+ietf@sandelman.ca> =
wrote:
> No, it has to get into the wire format, and it has to be cachable on =
the
> client, and it has to evaluated on the client as close to the =
application as
> possible.
>=20
> Why? because caching is good, and throwing away your cache each time =
you have
> a link up/down is dumb in my opinion.

I don=E2=80=99t think this would help, because you=E2=80=99re assuming =
that the data would be correct, and that the host would be able to tell =
which view to use. This is Really Hard. I don=E2=80=99t think that =
relying on this operationally could ever be a good tradeoff to save a =
few round trips to the nearest cache.

Since we don=E2=80=99t have a way to reliably identify links, and for =
that matter to tell which link is in which zone, we can=E2=80=99t do the =
efficient thing you are talking about. In practice, all resolvers that I =
know of (admittedly, this is just one, mDNSResponder) do in fact throw =
away the cache whenever the link changes, for exactly the reason we are =
talking about: just because the info I got from the resolver was valid =
on the link I was previously on, doesn=E2=80=99t mean it=E2=80=99s valid =
on the link I=E2=80=99m currently on.

Remember, just because something is efficient in principle, doesn=E2=80=99=
t mean that it=E2=80=99s efficient in practice. :)


--Apple-Mail=_4CCC9A5D-F6AB-494A-AFDD-6B29A4F37DAF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">On =
Jan 7, 2021, at 11:03 AM, Michael Richardson &lt;<a =
href=3D"mailto:mcr+ietf@sandelman.ca" =
class=3D"">mcr+ietf@sandelman.ca</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"caret-color: =
rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">No, it has to get into the wire format, and it has to be =
cachable on the</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Menlo-Regular; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Menlo-Regular; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">client, and it has to evaluated on the client as close to the =
application as</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Menlo-Regular; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Menlo-Regular; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">possible.</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Menlo-Regular; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Menlo-Regular; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Menlo-Regular; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">Why? because caching is good, and throwing away your cache =
each time you have</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Menlo-Regular; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Menlo-Regular; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">a link up/down is dumb in my =
opinion.</span></div></blockquote></div><br class=3D""><div class=3D"">I =
don=E2=80=99t think this would help, because you=E2=80=99re assuming =
that the data would be correct, and that the host would be able to tell =
which view to use. This is Really Hard. I don=E2=80=99t think that =
relying on this operationally could ever be a good tradeoff to save a =
few round trips to the nearest cache.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Since we don=E2=80=99t have a way to =
reliably identify links, and for that matter to tell which link is in =
which zone, we can=E2=80=99t do the efficient thing you are talking =
about. In practice, all resolvers that I know of (admittedly, this is =
just one, mDNSResponder) do in fact throw away the cache whenever the =
link changes, for exactly the reason we are talking about: just because =
the info I got from the resolver was valid on the link I was previously =
on, doesn=E2=80=99t mean it=E2=80=99s valid on the link I=E2=80=99m =
currently on.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Remember, just because something is efficient in principle, =
doesn=E2=80=99t mean that it=E2=80=99s efficient in practice. =
:)</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_4CCC9A5D-F6AB-494A-AFDD-6B29A4F37DAF--


From nobody Thu Jan  7 11:38:25 2021
Return-Path: <albert.e.manfredi@boeing.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 1E0D23A0BF8; Thu,  7 Jan 2021 11:38:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 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, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=boeing.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 UVqK8kUeci20; Thu,  7 Jan 2021 11:38:17 -0800 (PST)
Received: from ewa-mbsout-02.mbs.boeing.net (ewa-mbsout-02.mbs.boeing.net [130.76.20.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA8223A0BEB; Thu,  7 Jan 2021 11:38:17 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by ewa-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 107JcBLi057436; Thu, 7 Jan 2021 11:38:12 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1610048292; bh=DhKPi46UG75O1o0z72eQJVOWVovpntI2h/kBwmAJb9U=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=ir8zsbxCuf72GnOf7XCo94F2kR9oC9mW06MN1ybmQtfYKQUEy6gwqxN4DYp0/ikZu e9i117mDYSRmeCH2EN4zzr4BgqWX6X0rIACrPpnzPW6/VVN3vkqH/lifXlcO1hGZs/ y8cIsrmskSlqnpCzdKX0nKMftjuXD8FoikgFnm/OZfctc3ejGmS0pHBN+O7YvOYrXY Da6Z05IuPLlrZQvBpUb323mivNUgShmQn7LqPW/PNNEmaIJTbRN1DVePbbwJNnlvQf cfPecQG4XnyRrzgOtlPaMmCxkk5ZWwzYZw//WW50NMz6WpRBwfXMSKdeSZ+45bK2TW 5tVENo2h4raBw==
Received: from XCH16-01-10.nos.boeing.com (xch16-01-10.nos.boeing.com [144.115.66.5]) by ewa-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 107JbvPQ057227 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Thu, 7 Jan 2021 11:37:58 -0800
Received: from XCH16-01-11.nos.boeing.com (144.115.66.39) by XCH16-01-10.nos.boeing.com (144.115.66.5) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2044.4; Thu, 7 Jan 2021 11:37:56 -0800
Received: from XCH16-01-11.nos.boeing.com ([fe80::c57c:39bc:4c0a:384b]) by XCH16-01-11.nos.boeing.com ([fe80::c57c:39bc:4c0a:384b%4]) with mapi id 15.01.2044.004; Thu, 7 Jan 2021 11:37:56 -0800
From: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>
To: David Farmer <farmer=40umn.edu@dmarc.ietf.org>
CC: IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
Thread-Topic: [EXTERNAL]  Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
Thread-Index: AQHW5OW4RQf5NbyGPUqPbrUftFxb3qocjLcA
Date: Thu, 7 Jan 2021 19:37:56 +0000
Message-ID: <80c00c12156342db8933e4ee564a6c59@boeing.com>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com> <44e7ac61-523a-d35e-9024-7e6df81e4226@gmail.com> <be92f523-eeaa-8ed4-afdf-4a537f53748c@si6networks.com> <CAN-Dau2S9pXYAwrRbfT9aMyXPw-NYaOxKF+nXRg_14zqTr8F0g@mail.gmail.com>
In-Reply-To: <CAN-Dau2S9pXYAwrRbfT9aMyXPw-NYaOxKF+nXRg_14zqTr8F0g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [144.115.204.6]
x-tm-snts-smtp: D13308FB146C7B3BADBB05843D1758714BA0B6FF69747169BDE9AB32818E5C9B2000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/uSyKsfMzrXmpuy6n5JJQ6tYTFj0>
Subject: Re: [v6ops] [EXTERNAL] Re: Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2021 19:38:19 -0000

RnJvbTogaXB2NiA8aXB2Ni1ib3VuY2VzQGlldGYub3JnPiBPbiBCZWhhbGYgT2YgRGF2aWQgRmFy
bWVyDQoNCj4gTGluay1Mb2NhbCA+IFNpdGUtTG9jYWwgPj4+Pj4+IFBzZXVkby1HbG9iYWwgPiBH
bG9iYWwNCg0KU29tZXRoaW5nIGxpa2UgdGhhdCwgc3VyZSwgYWx0aG91Z2ggSSB3b3VsZCBub3Qg
dXNlIHRoYXQgdGVybS4NCg0KPiBXaGF0IGRvIG90aGVyIHBlb3BsZcKgdGhpbms/DQoNClJGQyAy
MzY1IGRlZmluZXMgc29tZXRoaW5nIGV4YWN0bHkgYWxvbmcgdGhlc2Ugc2FtZSBsaW5lcywgZm9y
IElQdjQgbXVsdGljYXN0IGFkZHJlc3NlcyB0aGF0IGFyZSBtZWFudCB0byBiZSB1c2VkIG9ubHkg
aW5zaWRlIGEgcGFydGljdWxhciBkb21haW4uIFNvLCB0aGVyZSBpcyBhdCBsZWFzdCB0aGlzIG9u
ZSBwcmVjZWRlbnQsIGFuZCBJIGRvbuKAmXQga25vdyB0aGF0IGl0IGNhdXNlcyBhbnkgY29uZnVz
aW9uLiBSRkMgMjM2NSBpcyB0aXRsZWQgIkFkbWluaXN0cmF0aXZlbHkgU2NvcGVkIElQIE11bHRp
Y2FzdC4iDQoNCkluIG15IHZpZXcsIHRoZXJlJ3Mgbm8gdXJnZW50IG5lZWQgdG8gbWFrZSBhbnkg
Y2hhbmdlcy4gQnV0IGlmIHBlb3BsZSBmZWVsIHRoaXMgaXMganVzdCB0b28gY29uZnVzaW5nLCB0
aGVuIHdlIGNhbiBkZWZpbmUgdGhpcyAiYWRtaW4gc2NvcGUiIGZvciBJUHY2IFVMQXMuDQoNCklu
IHByYWN0aWNlLCBSRkMgMTkxOCBhZGRyZXNzZXMgYXJlIHRoZSBzYW1lIHRoaW5nLiBBZG1pbmlz
dHJhdGl2ZWx5IHNjb3BlZCwgYW5kIHRoZXkgZG8gbm90IG5lZWQgdG8gYmUgbGltaXRlZCB0byBq
dXN0IG9uZSBsaW5rLg0KDQpCZXJ0DQoNCg==


From nobody Thu Jan  7 12:24:00 2021
Return-Path: <brian.e.carpenter@gmail.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 688353A0DFF; Thu,  7 Jan 2021 12:23:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.361
X-Spam-Level: 
X-Spam-Status: No, score=-2.361 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, NICE_REPLY_A=-0.262, RCVD_IN_DNSWL_NONE=-0.0001, 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0WD1aekJoXSz; Thu,  7 Jan 2021 12:23:57 -0800 (PST)
Received: from mail-pf1-x42d.google.com (mail-pf1-x42d.google.com [IPv6:2607:f8b0:4864:20::42d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F0343A0DFC; Thu,  7 Jan 2021 12:23:57 -0800 (PST)
Received: by mail-pf1-x42d.google.com with SMTP id a188so4566596pfa.11; Thu, 07 Jan 2021 12:23:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=FpewZUbjm+wz7zAp0M8DPi5D6AOxjcwSMl9eiDAMKqs=; b=BifO5rTA+Q4qO55UshAzWWFQ9Q3geCdoUyfGmSEvHCjweGaPr+NGXrkDoUh1eZu6xg JzSPMhmLAMKh5XDYFWh/D09OHIl/iYTtu7fk+T5+Y5v3tK+s9IxyaLii5NBNXuOV6/S7 ZybwVPNGdusmxxvjR0SHsWc+Q0bOMoBxl/Uvn/mVxKWpNb0l0rBkhq7SusDb1Fzst+bm DOjuIS6F1HY91qnxxKltWS6i1zGamGZx2AfJhEHlPqMgVk7Wv5/a7uX9F8/mm4rEDgRl uBC2fdvVSmJ/cuZEwrlc+lCiVEMDzgJ7FY+sHiJm9o5B4KUNtjuSUKcLNdssTGNqYRhx PJ0A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=FpewZUbjm+wz7zAp0M8DPi5D6AOxjcwSMl9eiDAMKqs=; b=Pu5EHKGMCr/bghO375oGL6eoDeeZZ3/3CGI0/wZxM4W87BqqsvtVzPs9R+9n3jK14Y 1ZY7CZA0iTC2NDw1diGvpVJNJNqlYPr214eLkOeft3MNBJkXak36oLMlugVEfldMqq97 DcHXiM9LN4pp0d7p+US/8z+XsSciM9RRjGBHHX3j07v4GCvqWHnK+sm7eEA73ncOGysF kDU9U7UUUteYKmLc79SZoThRlm0oqYn+bcvDPJPfRoV1b53YZHR+dHjOmho6RfdibSMq 1CIOZxdsO/a1OWoF7dFF+ZnazvvSreAK2DcbtGa72jpUI+0E/jwrGbwPcYio+cmWK23N YZDw==
X-Gm-Message-State: AOAM5302IrhP04YlZrJPed7l7xbymGwU2vSfyrzuPDYoNITwT9NrJ+Lf OdmYcCer3TgIhdnFffcluKG1bjQ0gu7hxg==
X-Google-Smtp-Source: ABdhPJxr3FyH4yPJyNDHDQnGoFg2HcodvJZcrkjja+r1+xwES7Oiblh8wYn0GndFHMd2ZuWK9qGPqg==
X-Received: by 2002:a63:804a:: with SMTP id j71mr3507284pgd.307.1610051036219;  Thu, 07 Jan 2021 12:23:56 -0800 (PST)
Received: from [192.168.178.20] ([151.210.131.28]) by smtp.gmail.com with ESMTPSA id d4sm2857337pjz.28.2021.01.07.12.23.53 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Jan 2021 12:23:55 -0800 (PST)
To: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, ipv6@ietf.org
Cc: IPv6 Operations <v6ops@ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com> <44e7ac61-523a-d35e-9024-7e6df81e4226@gmail.com> <m1kxTfc-0000M9C@stereo.hq.phicoh.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <7a61fb44-b5f1-9601-4fab-5b676f0cad83@gmail.com>
Date: Fri, 8 Jan 2021 09:23:51 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <m1kxTfc-0000M9C@stereo.hq.phicoh.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/o7kXl9ObQD2GDnc1jZqmwBMtbxE>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2021 20:23:58 -0000

On 08-Jan-21 00:41, Philip Homburg wrote:
>>> No, rewrite RFC 4007 and get rid of zone IDs. And the introduce interface I
>> Ds
>>> to select the interface of an outgoing packet, whether link-local or global
>> .
>>
>> Effectively that's what RFC3879 did. RFC4007 was a bit behind the
>> curve. As far as I know, zone IDs and interface IDs are exactly
>> equivalent (at least in POSIX and WinSock environments). IMHO this
>> is *only* a terminology question.
>>
>>> It doesn't change anything in practice, because that is what existing code
>>> does.
>>
>> Really? Using the interface ID for non-link-local addresses?
> 
> It works on Linux and MacOS. On freebsd I get
> '2001:67c:2e8:3::c100:a4%re0: Name does not resolve'
> which suggests that they do an extra check in a library. I didn't check
> if the kernel handles it.

Thanks. It doesn't work on Winsock (Windows 10 version) either. It assigns
interface index 0 to all global addresses (including ULAs) regardless of
which physical interface they are on. There is no interface 0 on Windows;
it amounts to being the "default zone" defined by RFC4007.

There's nothing in RFC4007 suggesting that a non-default zone applies
to global addresses. Rather the opposite:

"And, when supported, the index value zero at each
scope SHOULD be reserved to mean "use the default zone"...
Those default indices can also be used
as the zone qualifier for an address for which the node is attached
to only one zone; e.g., when using global addresses."

So I'd say that Linux and MacOS have got it wrong, and FreeBSD
and Windows are right. Portable code certainly can't assume that
the interface ID can be used for global unicast.

    Brian





From nobody Thu Jan  7 12:31:56 2021
Return-Path: <brian.e.carpenter@gmail.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 5060E3A0E21; Thu,  7 Jan 2021 12:31:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.361
X-Spam-Level: 
X-Spam-Status: No, score=-2.361 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, NICE_REPLY_A=-0.262, 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0CR-0on6eDR1; Thu,  7 Jan 2021 12:31:53 -0800 (PST)
Received: from mail-pl1-x62f.google.com (mail-pl1-x62f.google.com [IPv6:2607:f8b0:4864:20::62f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40CAF3A0E1C; Thu,  7 Jan 2021 12:31:53 -0800 (PST)
Received: by mail-pl1-x62f.google.com with SMTP id y8so4205560plp.8; Thu, 07 Jan 2021 12:31:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=4JvQYBclq92wXI+R9T0jU8fYttpS6UVDl3e04m2bbdw=; b=PI208p0nSHZsqbqRETaOU4qHfrgzwurIQjocAO8EwfPc4yfNPDvgIZvW8xp5i0ydYn LuIQI+SqfIabbzHGTZ60Z+jBPI/DN72s1OORTENhI16qzW0kLOawvI0vMYdNILrzHvHj X/g5CcRVss1NcnKqcu1yolmXjEXRe0WKx2Oep/90PUsafRBwckcJPMNgfXHmaFJQhrQQ 6PQ7bnAJKbLeyKJUuDPgaJdNg4xfZohYLDVgKkEn16UxM9cjjL4kkbC5tjMZV3r4AOvM /YVkLM0NPYYiFKsaO4HVbTtqSmwQUlPAF9Rb0YjXOdR6tqSH88iZ6VpB3q405cI97P5t JmcQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=4JvQYBclq92wXI+R9T0jU8fYttpS6UVDl3e04m2bbdw=; b=h2z1s+eeqVGv+qp+7nCT/ZXKpBEvTapy7WOEjOAZdo4JWyai6AWDmIaAdJy/1PieLY W3qpo4L4xFnqBS60AkaVDrAmZvpdArHMgmykNdxg6bbxYd2lNLopFBYemw23Su76TVAa s1Mi6Esl4/D0qT7UuS+DIFeNzSGRDxHlFe1m3MK3vN/2DD2dP6NMDMvOYdLmqu38nZIQ yyoXU3288png5pzAAQlF8cUfL3BOUuWJFktevk3aaPF9YawI0zC7CJFeZ0OnEDD3Nbap m9IQY/xCxOFYAx868pNBfv3pMCQYs7DVbJimZqFulACfFLhN9qjqnC6e/GSjo4A/F3ax eh4A==
X-Gm-Message-State: AOAM532YPUQjy4mzKexrIoETGYc14OGKj2/s/mZLYMPiwIsjHlvWIGm2 1V3onGaMg6jj26sfIySqUtaqD/UWppjioQ==
X-Google-Smtp-Source: ABdhPJy75w4Eap5cmN73xCOEBjneJZapYDVO5aNLGgy7DHAk1D37H4VNAQtXFLKXHdMFkv1r1EnGyg==
X-Received: by 2002:a17:90a:474c:: with SMTP id y12mr220156pjg.175.1610051512675;  Thu, 07 Jan 2021 12:31:52 -0800 (PST)
Received: from [192.168.178.20] ([151.210.131.28]) by smtp.gmail.com with ESMTPSA id t135sm6347436pfc.39.2021.01.07.12.31.49 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Jan 2021 12:31:51 -0800 (PST)
To: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, ipv6@ietf.org
Cc: IPv6 Operations <v6ops@ietf.org>, David Farmer <farmer=40umn.edu@dmarc.ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com> <44e7ac61-523a-d35e-9024-7e6df81e4226@gmail.com> <be92f523-eeaa-8ed4-afdf-4a537f53748c@si6networks.com> <CAN-Dau2S9pXYAwrRbfT9aMyXPw-NYaOxKF+nXRg_14zqTr8F0g@mail.gmail.com> <m1kxTpt-0000CxC@stereo.hq.phicoh.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <2faf76fd-1393-5bc5-52bf-9ee4ba3167a8@gmail.com>
Date: Fri, 8 Jan 2021 09:31:48 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <m1kxTpt-0000CxC@stereo.hq.phicoh.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/RjZlesBuzT_5So5SDqdZadGROGQ>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2021 20:31:54 -0000

On 08-Jan-21 00:52, Philip Homburg wrote:
>> I have an idea for what to call ULA's scope without redefining global scope
>> in RFC4007, how about we call ULA's scope "pseudo-global" scope.
> 
>> What do other people think?
> 
> In my opinion we need to kill the RFC 4007 scope concept. 
> 
> We can define for example 'address types' that have no scope, but as a way
> to label different types of addresses.

This.

Link-local needs an interface ID or interface index, which is meaningless outside the host.

All other unicast addresses are routeable, and do not require an associated interface ID. The range of reachability is always administratively defined, with default behaviours (ULA = limited domain reachability, GUA = global reachability).

We could have a greatly simplified RFC4007bis in that case.

    Brian


From nobody Thu Jan  7 13:23:13 2021
Return-Path: <markzzzsmith@gmail.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 DCAD83A0F00; Thu,  7 Jan 2021 13:23:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.598
X-Spam-Level: 
X-Spam-Status: No, score=-0.598 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.998, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 SkjxExMW65yJ; Thu,  7 Jan 2021 13:23:05 -0800 (PST)
Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D0973A0F02; Thu,  7 Jan 2021 13:23:05 -0800 (PST)
Received: by mail-pg1-x52e.google.com with SMTP id c22so6001275pgg.13; Thu, 07 Jan 2021 13:23:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=yLHL/6r2ceLElJ3/aMhrKLKEDWKfvWlsget+FmAVz3o=; b=YHSEGI1Yca9TPA4zardYUNxyJaC3bqLELwSDYYBgovEGUiL8h41k007NmB6VVOYDgP AVi8rySv7ziUdcGKSmSbGoaZJobfEXT4zzYjHGKr5CMJmsWRUj8ei+YHflmQYkPSz4Fr 1AdKMMmZnCfPumsa1B8w6RI86lEDmIyD7HP3/rfeOq24BfUzasEU7ZIuTFL0zGv0IOl9 M8fGr3VzCV264tKi4qzCL9tPRbYYKc2gIZ4Be9EZNB2b0k7dMmIMu6B8Hb1/NEih8prd 8JHJfNvWL7riSR0cATbVZbMy6GpFQWS3PBvcaP/Ax8GHBmzHDGRDsNK/XYxGtJqifcWa Fz2A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=yLHL/6r2ceLElJ3/aMhrKLKEDWKfvWlsget+FmAVz3o=; b=Ek+kvowIFE00xMLOR1NL4f7d8wp+UPBOJTNI4u91dc1NsGyip+R0Idd14rFsHb7iA3 GW6c0Xjun/GLp3FjVAInDbr/zp8eRAtVmdmeWpTJvbZAxapASAIwZ1vkOqqOF/Bv9UCU 78x+sdksFODkJ/zBvq3VoWOshTOF8pgAJXwSFXIPYYIcUAyczkYy42+IgtbEb1hbLnB/ ubrvvAguVeIKyBTxdvQZb8jPcAJ37qYILfdc2FigPvEpKD/yUemu3F9MW+jGJa3ikzuh KNGwl8Q6CXOJjA8vDYH9hy0Z00uvSPjk/mEbeHUBDhQrjln50htMNGDbtRFZRnCwg6HV eKRg==
X-Gm-Message-State: AOAM531MSn8y9M6aEVnJGycDMqDAJCo9OWyOAzzytvodT9oitizS9At0 TxZrsv2Nd213tbYSReaWsqYmtEGzdT4N9e1sTa0=
X-Google-Smtp-Source: ABdhPJxTHRfwmwXEOqUhU44yD0uaKzlsXUp83PZ26ISxFAyUUOOKXdEuxgFojr3fsRK3gEXmh86fiAnjGSo5IsANuXA=
X-Received: by 2002:a63:574c:: with SMTP id h12mr3683393pgm.79.1610054584947;  Thu, 07 Jan 2021 13:23:04 -0800 (PST)
MIME-Version: 1.0
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com> <44e7ac61-523a-d35e-9024-7e6df81e4226@gmail.com> <be92f523-eeaa-8ed4-afdf-4a537f53748c@si6networks.com> <CAN-Dau2S9pXYAwrRbfT9aMyXPw-NYaOxKF+nXRg_14zqTr8F0g@mail.gmail.com> <m1kxTpt-0000CxC@stereo.hq.phicoh.net> <2faf76fd-1393-5bc5-52bf-9ee4ba3167a8@gmail.com>
In-Reply-To: <2faf76fd-1393-5bc5-52bf-9ee4ba3167a8@gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Fri, 8 Jan 2021 08:22:38 +1100
Message-ID: <CAO42Z2xBhipQJxX7aauHO7-Y+d0bUhdAxM2OcBxWWi1pGPJ=Vg@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, 6man WG <ipv6@ietf.org>,  IPv6 Operations <v6ops@ietf.org>, David Farmer <farmer=40umn.edu@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009ad5f305b8560b9e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/tUXPY8YPuu3z5sjffWsGsPZhPgc>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2021 21:23:07 -0000

--0000000000009ad5f305b8560b9e
Content-Type: text/plain; charset="UTF-8"

Hi Brian,

On Fri, 8 Jan 2021, 07:32 Brian E Carpenter, <brian.e.carpenter@gmail.com>
wrote:

> On 08-Jan-21 00:52, Philip Homburg wrote:
> >> I have an idea for what to call ULA's scope without redefining global
> scope
> >> in RFC4007, how about we call ULA's scope "pseudo-global" scope.
> >
> >> What do other people think?
> >
> > In my opinion we need to kill the RFC 4007 scope concept.
> >
> > We can define for example 'address types' that have no scope, but as a
> way
> > to label different types of addresses.
>
> This.
>
> Link-local needs an interface ID or interface index, which is meaningless
> outside the host.
>

While I do agree that interface ID is much more closer to the truth, it
seems that one reason for zone rather than interface ID for link-locals in
RFC 4007 was to inform a multi-interface node that it had multiple
interfaces attached to the same link, informing it that the corresponding
interface link-local addresses are attached to the same link.

I don't know what the use case for that is or was expected to be (layer 3
inbound/outbound load balancing or redundancy?), however it sounds like it
would be useful for a host to continue to have the knowledge. It would be
lost with pure IPv6 interface enabled IDs. I don't think shared GUA/ULA
prefixes across interfaces could be entirely relied on to determine that,
as it is theoretically possible for multiple interfaces on the same host
attached to the same link to have different GUA and/or ULA prefixes
(perhaps by manual configuration because the received RAs don't PIOs with
the A bit enabled, or any PIOs).

Perhaps preserve the idea of a zone, that in most but not all cases would
also be the same as interface ID, but only for the link-local unicast
prefix (and for all scopes of multicast addresses).

Regards,
Mark.


> All other unicast addresses are routeable, and do not require an
> associated interface ID. The range of reachability is always
> administratively defined, with default behaviours (ULA = limited domain
> reachability, GUA = global reachability).
>
> We could have a greatly simplified RFC4007bis in that case.
>
>     Brian
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

--0000000000009ad5f305b8560b9e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"auto"><div>Hi Brian,<br><br><div class=3D"gmai=
l_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, 8 Jan 2021, 07:32 Br=
ian E Carpenter, &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=
=3D"_blank">brian.e.carpenter@gmail.com</a>&gt; wrote:<br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">On 08-Jan-21 00:52, Philip Homburg wrote:<br>
&gt;&gt; I have an idea for what to call ULA&#39;s scope without redefining=
 global scope<br>
&gt;&gt; in RFC4007, how about we call ULA&#39;s scope &quot;pseudo-global&=
quot; scope.<br>
&gt; <br>
&gt;&gt; What do other people think?<br>
&gt; <br>
&gt; In my opinion we need to kill the RFC 4007 scope concept. <br>
&gt; <br>
&gt; We can define for example &#39;address types&#39; that have no scope, =
but as a way<br>
&gt; to label different types of addresses.<br>
<br>
This.<br>
<br>
Link-local needs an interface ID or interface index, which is meaningless o=
utside the host.<br></blockquote></div></div><div dir=3D"auto"><br></div><d=
iv dir=3D"auto">While I do agree that interface ID is much more closer to t=
he truth, it seems that one reason for zone rather than interface ID for li=
nk-locals in RFC 4007 was to inform a multi-interface node that it had mult=
iple interfaces attached to the same link, informing it that the correspond=
ing interface link-local addresses are attached to the same link.</div><div=
 dir=3D"auto"><br></div><div>I don&#39;t know what the use case for that is=
 or was expected to be (layer 3 inbound/outbound load balancing or redundan=
cy?), however it sounds like it would be useful for a host to continue to h=
ave the knowledge. It would be lost with pure IPv6 interface enabled IDs. I=
 don&#39;t think shared GUA/ULA prefixes across interfaces could be entirel=
y relied on to determine that, as it is theoretically possible for multiple=
 interfaces on the same host attached to the same link to have different GU=
A and/or ULA prefixes (perhaps by manual configuration because the received=
 RAs don&#39;t PIOs with the A bit enabled, or any PIOs).</div><div><br></d=
iv><div>Perhaps preserve the idea of a zone, that in most but not all cases=
 would also be the same as interface ID, but only for the link-local unicas=
t prefix (and for all scopes of multicast addresses).</div><div><br></div><=
div>Regards,<br></div><div>Mark.</div><div dir=3D"auto"><br></div><div dir=
=3D"auto"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
All other unicast addresses are routeable, and do not require an associated=
 interface ID. The range of reachability is always administratively defined=
, with default behaviours (ULA =3D limited domain reachability, GUA =3D glo=
bal reachability).<br>
<br>
We could have a greatly simplified RFC4007bis in that case.<br>
<br>
=C2=A0 =C2=A0 Brian<br>
<br>
_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org" rel=3D"noreferrer" target=3D"_blank">v6op=
s@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferrer n=
oreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a=
><br>
</blockquote></div></div></div>
</div>

--0000000000009ad5f305b8560b9e--


From nobody Thu Jan  7 13:36:14 2021
Return-Path: <fgont@si6networks.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 6AEBE3A00C9; Thu,  7 Jan 2021 13:36:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.161
X-Spam-Level: 
X-Spam-Status: No, score=-2.161 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, 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 Uub-ntZFgPcf; Thu,  7 Jan 2021 13:36:03 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DC943A0062; Thu,  7 Jan 2021 13:36:01 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 7CEDA2845B1; Thu,  7 Jan 2021 21:35:53 +0000 (UTC)
To: David Farmer <farmer@umn.edu>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>, Mark Smith <markzzzsmith@gmail.com>, IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com> <44e7ac61-523a-d35e-9024-7e6df81e4226@gmail.com> <be92f523-eeaa-8ed4-afdf-4a537f53748c@si6networks.com> <CAN-Dau2S9pXYAwrRbfT9aMyXPw-NYaOxKF+nXRg_14zqTr8F0g@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <f85fce6f-3c99-caf0-82c7-fc8cf9858a42@si6networks.com>
Date: Thu, 7 Jan 2021 18:35:28 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CAN-Dau2S9pXYAwrRbfT9aMyXPw-NYaOxKF+nXRg_14zqTr8F0g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/X7K0dNaZHztwdcQhr-rXkkfWFm0>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2021 21:36:08 -0000

On 7/1/21 08:08, David Farmer wrote:
> Sorry for the top post.
> 
> Fernando, you are correct that by the definition of global scope in 
> RFC4007, ULA is not global scope.
> 
> However, Brian and RFC4139 are also correct, given the intended 
> reachability domain for ULA, it has a uniqueness that is many many 
> orders of magnitude greater than is necessary for the task. So, while 
> not technically global scope as defined in RFC4007 it is effectively 
> global scope in any way that matters.

BUt this is like a circular definition. Because it's kind of saying 
something like "ULAs are globally unique as long as the have local scope".

In order for them to have "global scope", they need to be globally 
unique. And you note that "they are essentially unique, gven an 
appropriate scope".




> I have an idea for what to call ULA's scope without redefining global 
> scope in RFC4007, how about we call ULA's scope "pseudo-global" scope.
> 
> This gives us;
> 
> Link-Local > Site-Local >>>>>> Pseudo-Global > Global

I don't think the site-local scope, in terms of network span, is 
necessarily larger than that of ULAs.



> Calling ULA pseudo-global scope I believe conveys RFC4139's 
> original intent without conflicting with the definition of global scope 
> in RFC4007, while still allowing it to be treated effectively as if it 
> is global scope.
> 
> What do other people think?

IMO, that'd keep the confusion. At the end of the day, if your nor going 
to call them "global scope", the specific name for the scope doesn't 
really matter... as long as it is properly defined, and used consistently.

-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Thu Jan  7 13:52:10 2021
Return-Path: <mellon@fugue.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 15E383A0332 for <v6ops@ietfa.amsl.com>; Thu,  7 Jan 2021 13:52:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 Q0ZugQX5tlKj for <v6ops@ietfa.amsl.com>; Thu,  7 Jan 2021 13:52:01 -0800 (PST)
Received: from mail-qt1-x82a.google.com (mail-qt1-x82a.google.com [IPv6:2607:f8b0:4864:20::82a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFF453A033F for <v6ops@ietf.org>; Thu,  7 Jan 2021 13:52:01 -0800 (PST)
Received: by mail-qt1-x82a.google.com with SMTP id v5so5334724qtv.7 for <v6ops@ietf.org>; Thu, 07 Jan 2021 13:52:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=Yah5BKzrZcY59QVoRtmh+zi4NMojLGjFgjlFn82oQ3A=; b=Q87eaywU9xqrQNb+UqMw+36lgQV2bBCxCmejCrHhFZXnk9O70TSJ8pETJFFQb9+xAO SNIxrx91IJbo6YTtmmdFkrwjddUX1EuGY+mx9t2Ksc/QFkaorgRAVoSBbG8YffoZFCIe /VM5uMZNK+IogMO6qOxowDNSqsaF1H5ORZQAoLHK+E/f8vlB6w2sTK9vUAr/Gc8DFujx fsuUGkZFB4nNUdzCqDPIMkpfRJQrheNW8n+hd5IfDMNp6Qoh7NBME2rbL5LAeRcCMjoa lI7NqAd0WYd+6YedvZIqOzbgzD2zbD9I1ugZV7rXAhdDg31C0qqYU2VG5wz+YS/AbiLF 281g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=Yah5BKzrZcY59QVoRtmh+zi4NMojLGjFgjlFn82oQ3A=; b=I7r/qVfRLC8ty1royD3yW5WswXyoNTuhtIoxpV/N5NF1JcEib0NVJhg750wDVIUsBq uZOnNAvWphB+BX5BbjXuz0pHu4ozd1c1Kvq2roVnEtZpc7IArPBR90KIJqREX4wSmsIA bC15xEpmupHzcGk22sVZS0fc+jtWyJt+MXOdzKgj9cCVAkKw1GUYU8DyRAA3Bz6zdTrB T5cNBf2XWhJRjcTAawfl/rqNhJ09snNRUd0aVgQEB5E3zWxrtQX1HAyUBtAlp3Uwtuhs AeCjP+HSfORfs0krQinoKR/Kb/2aK23m1XfUkKTd8yNoqcm8pxS8lOGxoaYTrzdCN40B EfdA==
X-Gm-Message-State: AOAM532Gw0uWIuq1ElF6M80phUTd3luiOeabS0NC05Z3B8dmTgqRYp/b fI2k9kcgO+z7r3ARkxEHMEn+3OwlbgsmtA==
X-Google-Smtp-Source: ABdhPJyIOnqRjl/Wc8VgHCyPO5OHpGatbxNOvAV3koFEiN+JuAa4u9mQnBvghDcdnzBULiGccZUwmg==
X-Received: by 2002:a05:622a:195:: with SMTP id s21mr682575qtw.53.1610056320340;  Thu, 07 Jan 2021 13:52:00 -0800 (PST)
Received: from mithrandir.lan (c-24-91-177-160.hsd1.nh.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id h22sm1076805qth.55.2021.01.07.13.51.59 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Jan 2021 13:51:59 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9B9E229B-E3CB-421A-BD3B-D84608B26E86"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.2\))
Date: Thu, 7 Jan 2021 16:51:57 -0500
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com> <44e7ac61-523a-d35e-9024-7e6df81e4226@gmail.com> <be92f523-eeaa-8ed4-afdf-4a537f53748c@si6networks.com> <CAN-Dau2S9pXYAwrRbfT9aMyXPw-NYaOxKF+nXRg_14zqTr8F0g@mail.gmail.com> <f85fce6f-3c99-caf0-82c7-fc8cf9858a42@si6networks.com>
To: IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
In-Reply-To: <f85fce6f-3c99-caf0-82c7-fc8cf9858a42@si6networks.com>
Message-Id: <F5A8AFF8-5235-41C0-A1E2-DCDD4922C872@fugue.com>
X-Mailer: Apple Mail (2.3654.60.0.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/MzjbIVFoJnKnu70bcsqz0RX0bYs>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2021 21:52:04 -0000

--Apple-Mail=_9B9E229B-E3CB-421A-BD3B-D84608B26E86
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Jan 7, 2021, at 4:35 PM, Fernando Gont <fgont@si6networks.com> wrote:
> In order for them to have "global scope", they need to be globally =
unique. And you note that "they are essentially unique, gven an =
appropriate scope=E2=80=9D.

I think the disconnect here is that RFC 4007=E2=80=99s definition of =
=E2=80=9Cglobal scope=E2=80=9D clearly contradicts the sense in which =
ULAs are =E2=80=9Cglobal.=E2=80=9D So that=E2=80=99s a real problem.

At the same time, the next question to ask is in what sense =E2=80=9Cgloba=
l scope=E2=80=9D is actionable. People have been talking about zone =
identifiers as a way to determine scope, but in practice the way we do =
this is with routing table entries. The reason you have to specify a =
zone ID for a link-local address is that the route to the link-local =
prefix is present on all interfaces, but the address is valid on only =
one interface.

So you specify that interface with the zone ID. I use the term interface =
loosely here=E2=80=94in principle you could have two interfaces =
connected to the same link, and that would notionally mean that they =
both have the same zone ID, but there=E2=80=99s no safe way to make this =
determination in practice, so in practice the =E2=80=9Czone IDs=E2=80=9D =
will always be different.

The same situation does not apply for ULAs. You can (almost) just use =
routing table entries to deliver ULAs. I say (almost) because of course =
if you don=E2=80=99t have an explicit route to the ULA prefix, you =
can=E2=80=99t send the packet. So there=E2=80=99s a tendency to want to =
send the packet to the default route, but that doesn=E2=80=99t work if =
you have two interfaces and two default routers. This is why it=E2=80=99s =
tempting to then use the =E2=80=9Czone ID=E2=80=9D to resolve this =
problem. But that doesn=E2=80=99t work, because the host has no way to =
know which zone ID to use.

So it=E2=80=99s the network=E2=80=99s responsibility to provide enough =
information that the ULA can be correctly routed. There are two ways to =
do this that spring to mind:
1. Make assumptions
2. Only send to a ULA if you have a specific non-global route that =
points to it.
3. Use provisioning domains (https://tools.ietf.org/html/rfc6418)

Option 2 is probably the safest solution. If the route is present on two =
interfaces, and you have a collision, and not just two valid ways of =
reaching the same destination, then you will have a problem. This is why =
ULAs aren=E2=80=99t as fabulous as we might wish. But in practice, =
it=E2=80=99s entirely safe to do this.

Option 1 could work pretty well, e.g. on a cell phone. Not so well on a =
host with two network interfaces. It=E2=80=99s unlikely that a ULA is =
going to work on the global internet, so you never send it on the =
cellular interface. Problem solved. This is the sense in which I think =
it=E2=80=99s tempting to say that the scope of a ULA is not global, =
because here you can make a purely mechanical decision.

Option 3 would work quite well. Presumably if the name server for a =
provisioning domain gives you a ULA, then you can use the default router =
for that provisioning domain to reach that ULA (if it=E2=80=99s not =
on-link). So here you have effectively an explicit scope, which really =
doesn=E2=80=99t play well with the meaning of =E2=80=9Cscope=E2=80=9D in =
RFC 4007.


--Apple-Mail=_9B9E229B-E3CB-421A-BD3B-D84608B26E86
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">On =
Jan 7, 2021, at 4:35 PM, Fernando Gont &lt;<a =
href=3D"mailto:fgont@si6networks.com" =
class=3D"">fgont@si6networks.com</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"caret-color: =
rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">In order for them to have "global scope", they need to be =
globally unique. And you note that "they are essentially unique, gven an =
appropriate scope=E2=80=9D.</span><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Menlo-Regular; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""></div></blockquote><br =
class=3D""></div><div>I think the disconnect here is that RFC 4007=E2=80=99=
s definition of =E2=80=9Cglobal scope=E2=80=9D clearly contradicts the =
sense in which ULAs are =E2=80=9Cglobal.=E2=80=9D So that=E2=80=99s a =
real problem.</div><div><br class=3D""></div><div>At the same time, the =
next question to ask is in what sense =E2=80=9Cglobal scope=E2=80=9D is =
actionable. People have been talking about zone identifiers as a way to =
determine scope, but in practice the way we do this is with routing =
table entries. The reason you have to specify a zone ID for a link-local =
address is that the route to the link-local prefix is present on all =
interfaces, but the address is valid on only one =
interface.</div><div><br class=3D""></div><div>So you specify that =
interface with the zone ID. I use the term interface loosely here=E2=80=94=
in principle you could have two interfaces connected to the same link, =
and that would notionally mean that they both have the same zone ID, but =
there=E2=80=99s no safe way to make this determination in practice, so =
in practice the =E2=80=9Czone IDs=E2=80=9D will always be =
different.</div><div><br class=3D""></div><div>The same situation does =
not apply for ULAs. You can (almost) just use routing table entries to =
deliver ULAs. I say (almost) because of course if you don=E2=80=99t have =
an explicit route to the ULA prefix, you can=E2=80=99t send the packet. =
So there=E2=80=99s a tendency to want to send the packet to the default =
route, but that doesn=E2=80=99t work if you have two interfaces and two =
default routers. This is why it=E2=80=99s tempting to then use the =
=E2=80=9Czone ID=E2=80=9D to resolve this problem. But that doesn=E2=80=99=
t work, because the host has no way to know which zone ID to =
use.</div><div><br class=3D""></div><div>So it=E2=80=99s the network=E2=80=
=99s responsibility to provide enough information that the ULA can be =
correctly routed. There are two ways to do this that spring to =
mind:</div><div>1. Make assumptions</div><div>2. Only send to a ULA if =
you have a specific non-global route that points to it.</div><div>3. Use =
provisioning domains (<a href=3D"https://tools.ietf.org/html/rfc6418" =
class=3D"">https://tools.ietf.org/html/rfc6418</a>)</div><div><br =
class=3D""></div><div>Option 2 is probably the safest solution. If the =
route is present on two interfaces, and you have a collision, and not =
just two valid ways of reaching the same destination, then you will have =
a problem. This is why ULAs aren=E2=80=99t as fabulous as we might wish. =
But in practice, it=E2=80=99s entirely safe to do this.</div><div><br =
class=3D""></div><div>Option 1 could work pretty well, e.g. on a cell =
phone. Not so well on a host with two network interfaces. It=E2=80=99s =
unlikely that a ULA is going to work on the global internet, so you =
never send it on the cellular interface. Problem solved. This is the =
sense in which I think it=E2=80=99s tempting to say that the scope of a =
ULA is not global, because here you can make a purely mechanical =
decision.</div><div><br class=3D""></div><div>Option 3 would work quite =
well. Presumably if the name server for a provisioning domain gives you =
a ULA, then you can use the default router for that provisioning domain =
to reach that ULA (if it=E2=80=99s not on-link). So here you have =
effectively an explicit scope, which really doesn=E2=80=99t play well =
with the meaning of =E2=80=9Cscope=E2=80=9D in RFC 4007.</div><div><br =
class=3D""></div></body></html>=

--Apple-Mail=_9B9E229B-E3CB-421A-BD3B-D84608B26E86--


From nobody Thu Jan  7 13:56:23 2021
Return-Path: <fgont@si6networks.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 D24423A0163; Thu,  7 Jan 2021 13:56:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.15
X-Spam-Level: 
X-Spam-Status: No, score=-2.15 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable 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 DSKI2qgSig7j; Thu,  7 Jan 2021 13:56:14 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9813C3A03C9; Thu,  7 Jan 2021 13:56:14 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 259702846ED; Thu,  7 Jan 2021 21:56:10 +0000 (UTC)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, ipv6@ietf.org
Cc: IPv6 Operations <v6ops@ietf.org>, David Farmer <farmer=40umn.edu@dmarc.ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com> <44e7ac61-523a-d35e-9024-7e6df81e4226@gmail.com> <be92f523-eeaa-8ed4-afdf-4a537f53748c@si6networks.com> <CAN-Dau2S9pXYAwrRbfT9aMyXPw-NYaOxKF+nXRg_14zqTr8F0g@mail.gmail.com> <m1kxTpt-0000CxC@stereo.hq.phicoh.net> <2faf76fd-1393-5bc5-52bf-9ee4ba3167a8@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <13bdd3ca-9b3d-8ce9-404d-12d508404fbd@si6networks.com>
Date: Thu, 7 Jan 2021 18:55:38 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <2faf76fd-1393-5bc5-52bf-9ee4ba3167a8@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/eRhpy_cE6IL9T0GKGwN2yOHVn3c>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2021 21:56:18 -0000

On 7/1/21 17:31, Brian E Carpenter wrote:
> On 08-Jan-21 00:52, Philip Homburg wrote:
>>> I have an idea for what to call ULA's scope without redefining global scope
>>> in RFC4007, how about we call ULA's scope "pseudo-global" scope.
>>
>>> What do other people think?
>>
>> In my opinion we need to kill the RFC 4007 scope concept.
>>
>> We can define for example 'address types' that have no scope, but as a way
>> to label different types of addresses.
> 
> This.

Me, as long as the outcome is clear, I'm fine.

("scope", as a conceptual property of addresses doesn't seem bad.  You 
can talk about the scope of IPv5 addresses (link-local, private/local, 
global) in IPv4, too).

That said, removing the concept of "scope" would probably need more 
things to be re-worked -- not necessarily bad, though.



> Link-local needs an interface ID or interface index, which is meaningless outside the host.
> 
> All other unicast addresses are routeable, and do not require an associated interface ID. The range of reachability is always administratively defined, with default behaviours (ULA = limited domain reachability, GUA = global reachability).

Me thinking out loud:
What about the case where you have a host with two interfaces, each with 
one different ULA prefix, and you need to send packets to a destination 
ULA prefix, that is totally different from the two you're using?

Another similar case would be a host with two interfaces, global 
addresses on each, that has to send packets to a ULA prefix.

It would seem to me that in wuch cases, you'd need a way to specify an 
interface.

(Not sure if, conceuptually speaking, not having an address configured 
for the ULA prefix you're trying to communicate with, means that you're 
not part of the "zone", and hence, that you're on your own)


-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Thu Jan  7 14:14:04 2021
Return-Path: <fgont@si6networks.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 3B5B73A093D; Thu,  7 Jan 2021 14:14:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.161
X-Spam-Level: 
X-Spam-Status: No, score=-2.161 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, 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 Bi3WhQZVexFp; Thu,  7 Jan 2021 14:13:59 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43AAB3A0902; Thu,  7 Jan 2021 14:13:59 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 46FAD283C00; Thu,  7 Jan 2021 22:13:56 +0000 (UTC)
To: Ted Lemon <mellon@fugue.com>, IPv6 Operations <v6ops@ietf.org>, 6MAN <6man@ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com> <44e7ac61-523a-d35e-9024-7e6df81e4226@gmail.com> <be92f523-eeaa-8ed4-afdf-4a537f53748c@si6networks.com> <CAN-Dau2S9pXYAwrRbfT9aMyXPw-NYaOxKF+nXRg_14zqTr8F0g@mail.gmail.com> <f85fce6f-3c99-caf0-82c7-fc8cf9858a42@si6networks.com> <F5A8AFF8-5235-41C0-A1E2-DCDD4922C872@fugue.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <b0778f92-2323-bff4-9ca0-522c543c7617@si6networks.com>
Date: Thu, 7 Jan 2021 19:13:36 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <F5A8AFF8-5235-41C0-A1E2-DCDD4922C872@fugue.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/K6ggbbZrlUZ8u6p4Vy4s5rap7q0>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2021 22:14:03 -0000

On 7/1/21 18:51, Ted Lemon wrote:
> On Jan 7, 2021, at 4:35 PM, Fernando Gont <fgont@si6networks.com 
> <mailto:fgont@si6networks.com>> wrote:
>> In order for them to have "global scope", they need to be globally 
>> unique. And you note that "they are essentially unique, gven an 
>> appropriate scope”.
> 
> I think the disconnect here is that RFC 4007’s definition of “global 
> scope” clearly contradicts the sense in which ULAs are “global.” So 
> that’s a real problem.

Indeed!



> At the same time, the next question to ask is in what sense “global 
> scope” is actionable. People have been talking about zone identifiers as 
> a way to determine scope, but in practice the way we do this is with 
> routing table entries. The reason you have to specify a zone ID for a 
> link-local address is that the route to the link-local prefix is present 
> on all interfaces, but the address is valid on only one interface.

Agreed. Or: the address is not globally-unique. So the same address is 
actually valid on all interfaces, most-likely corresponding to different 
nodes .. and thus you need to specify which of all those possible 
instances of address FE80::X you are referring to.




> The same situation does not apply for ULAs. You can (almost) just use 
> routing table entries to deliver ULAs. I say (almost) because of course 
> if you don’t have an explicit route to the ULA prefix, you can’t send 
> the packet.

As noted to Brian, the case that might need a zone-id is that where you 
have a host with two interfaces, each with one different ULA prefix, and 
you need to send packets to a destination ULA that belongs to a whole 
different prefix than the ones for which you have configured addresses 
for your two interfaces.

Another similar case would be a host with two interfaces, global 
addresses on each, that has to send packets to a ULA prefix.

Relying on your default route might not get your to where you want.

(Not sure if, conceptually speaking, not having an address configured 
for the ULA prefix you're trying to communicate with, means that you're 
not part of the "zone", and hence, that you're on your own)



> So there’s a tendency to want to send the packet to the 
> default route, but that doesn’t work if you have two interfaces and two 
> default routers. This is why it’s tempting to then use the “zone ID” to 
> resolve this problem. But that doesn’t work, because the host has no way 
> to know which zone ID to use.

That seems to be a similar case than the one I was noting above. I gues 
it could also be more complicate: even if you had a single interface, 
you might have multiple default routers. So rather than specifying an 
interface, you might actually need to specify "which next hope" to use.

Of course one cannot expect that.


> So it’s the network’s responsibility to provide enough information that 
> the ULA can be correctly routed. There are two ways to do this that 
> spring to mind:
> 1. Make assumptions
> 2. Only send to a ULA if you have a specific non-global route that 
> points to it.

#2 would probably make cases that are currently supported, unsupported. 
e.g.: think of a case where your local router advertises a /64 ULA 
prefix on the local link, and you want to send a packet to an address of 
a different subnet of the same Global-ID. -- most likely your router is 
not sending RIOs for the ULA prefix you're employing....




> Option 1 could work pretty well, e.g. on a cell phone. Not so well on a 
> host with two network interfaces. It’s unlikely that a ULA is going to 
> work on the global internet, so you never send it on the cellular 
> interface. Problem solved. This is the sense in which I think it’s 
> tempting to say that the scope of a ULA is not global, because here you 
> can make a purely mechanical decision.

Agreed on this one.


-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Thu Jan  7 14:40:36 2021
Return-Path: <brian.e.carpenter@gmail.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 A49B03A0B60; Thu,  7 Jan 2021 14:40:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.361
X-Spam-Level: 
X-Spam-Status: No, score=-2.361 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, NICE_REPLY_A=-0.262, 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hcMtVuIdNxpV; Thu,  7 Jan 2021 14:40:29 -0800 (PST)
Received: from mail-pf1-x42a.google.com (mail-pf1-x42a.google.com [IPv6:2607:f8b0:4864:20::42a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D0A33A0B58; Thu,  7 Jan 2021 14:40:29 -0800 (PST)
Received: by mail-pf1-x42a.google.com with SMTP id c79so4968114pfc.2; Thu, 07 Jan 2021 14:40:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=isJhehR/Lx5KryYWUyXiXdsKsDPxDqgzvGIQPqTi3a0=; b=TCnLCuj6XypXny9QhAp4KG7uxXxq2LKUHWkpBXUuJrBFpz623SeTF+7tuYqmhCIdYl cXRB+965PomLn4F+guY10jMpBK566tXDjE9QGHL8y580WWelfv7aWwaOwAghGiPI3fKl Rfm6fmDqQPoR31hBbbEX8sjjBn6moDIwyiWyGTUNErlH2obtfBjGCLZrYydo4lidS5c6 wWmtmMqMYDx0YLKon5MyLS0mxJ9+YEJ+qY4EAbVyf6i+bqHvMznRVL/mCk/zFWm67rHA ZgctE5sfUlZRH+PL369t1/vyW+fcB9rOxVIrvutHJrSKC5hQPsizNcd0DXV35WopGaJT dRZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=isJhehR/Lx5KryYWUyXiXdsKsDPxDqgzvGIQPqTi3a0=; b=mtGvG49fV6uyW2poL7+2Rlgd01sXBHEtfmDnyZa5wgRZ5Jn9L1lfQR6nIe5LkvxDmI SuHxH+2jSNm4iJjcIFIpFEFK34M/7p6078eaTQzntOUazh3MIDnJ0GqVsDwR0DN28RO4 M4CHpJUfYtfQgx/MmjiMPSaE+yQy36AB9nbHGblrBVPjczVq6T3pdBL8vuUBxlHspCD/ orZVDL7puyO4/+fjkdzvTftN6cBUdEi5gTaE99+G7lJSfO19AFPaBTgjet8LDRGG+By3 pdx5Rv61X75az3Or0DWrsTdeUy8Igzo2Dsg/Rsqol1JKUhy8JJwKWu1ppPuRNwPV47ua 9MLA==
X-Gm-Message-State: AOAM530OOgietRIo00/0qxTEoZm2XPEf8085zyasftLW5im87g++/WiZ YaOOayrquTVkfl11vgDJVefnQaOCBKu7Gg==
X-Google-Smtp-Source: ABdhPJyNV+n1dSlQDEBGCociFAQcqvS9f7dBhDRiI7burF6fKVV8kHGrORBX5d5Nkq8ODyfnsdEqJw==
X-Received: by 2002:a63:5023:: with SMTP id e35mr4007909pgb.56.1610059228561;  Thu, 07 Jan 2021 14:40:28 -0800 (PST)
Received: from [192.168.178.20] ([151.210.131.28]) by smtp.gmail.com with ESMTPSA id q35sm2924495pjh.38.2021.01.07.14.40.26 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Jan 2021 14:40:27 -0800 (PST)
To: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, ipv6@ietf.org
Cc: IPv6 Operations <v6ops@ietf.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAO42Z2wR-3vbHi-NrBBMmCTNDq5fgqvSmBUbYK7P+63QTNfxkg@mail.gmail.com> <CAKD1Yr014PzVJj9Y6O=PBGc_QSVtur-0wMpaNkFA0dqr8FHGuA@mail.gmail.com> <44e7ac61-523a-d35e-9024-7e6df81e4226@gmail.com> <be92f523-eeaa-8ed4-afdf-4a537f53748c@si6networks.com> <CAN-Dau2S9pXYAwrRbfT9aMyXPw-NYaOxKF+nXRg_14zqTr8F0g@mail.gmail.com> <m1kxTpt-0000CxC@stereo.hq.phicoh.net> <2faf76fd-1393-5bc5-52bf-9ee4ba3167a8@gmail.com> <CAO42Z2xBhipQJxX7aauHO7-Y+d0bUhdAxM2OcBxWWi1pGPJ=Vg@mail.gmail.com> <m1kxd1U-0000EhC@stereo.hq.phicoh.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <9677fd8c-a61c-3292-a21a-2f7a31072a74@gmail.com>
Date: Fri, 8 Jan 2021 11:40:23 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <m1kxd1U-0000EhC@stereo.hq.phicoh.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/5iGHtvgUIfxK19Ql2AZMxieg2m4>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2021 22:40:31 -0000

On 08-Jan-21 10:40, Philip Homburg wrote:
>> While I do agree that interface ID is much more closer to the truth, it
>> seems that one reason for zone rather than interface ID for link-locals in
>> RFC 4007 was to inform a multi-interface node that it had multiple
>> interfaces attached to the same link, informing it that the corresponding
>> interface link-local addresses are attached to the same link.
> 
> Are there any implementation that do this? And in particular how does
> that work with the socket interface? I.e., with if_nametoindex and
> if_indextoname.

The machine on which I am typing has interface 6 and interface 22
both up and running.
On interface 6,  the default router is fe80::2e3a:fdff:fea4:dde7%6
On interface 22, the default router is fe80::2e3a:fdff:fea4:dde7%22

Yes, they are the same thing because the default router is also a transparent
Ethernet-to-WiFi bridge. Interface 6 and interface 22 both connect to
the same LAN, but the IP stack has no way to know it.

The zone index as described in RFC4007 is a hallucination.

    Brian


From nobody Thu Jan  7 17:18:54 2021
Return-Path: <marka@isc.org>
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 275EF3A0FD5; Thu,  7 Jan 2021 17:18:53 -0800 (PST)
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, SPF_HELO_NONE=0.001, 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 mFRrgdCN9rEz; Thu,  7 Jan 2021 17:18:51 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78A443A0FD3; Thu,  7 Jan 2021 17:18:51 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id D98123AB0CD; Fri,  8 Jan 2021 01:18:50 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id C897F160051; Fri,  8 Jan 2021 01:18:50 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id AEA24160056; Fri,  8 Jan 2021 01:18:50 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id XKNsoYu0oYah; Fri,  8 Jan 2021 01:18:50 +0000 (UTC)
Received: from [172.30.42.68] (n114-75-149-106.bla4.nsw.optusnet.com.au [114.75.149.106]) by zmx1.isc.org (Postfix) with ESMTPSA id 92548160051; Fri,  8 Jan 2021 01:18:49 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.7\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <BE6C041F-94B2-400D-B114-A76962190660@fugue.com>
Date: Fri, 8 Jan 2021 12:18:46 +1100
Cc: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, IPv6 Operations <v6ops@ietf.org>, IPv6 List <ipv6@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <78D0D84C-53DB-4661-BA43-CFEB1F377BB4@isc.org>
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <m1kx98E-0000EhC@stereo.hq.phicoh.net> <b53b5d62-0334-f791-f56a-f2122767ecdb@si6networks.com> <m1kxAVC-0000KhC@stereo.hq.phicoh.net> <CAHL_VyD85e9=taY1XENf7hc=BXRyD_7JJFDCW2Oq_a0z3hYqUA@mail.gmail.com> <bc29edad-b57b-bb53-141b-8f58c5ca2526@si6networks.com> <91424EEE-EF12-4B5B-ADE4-38230E049290@isc.org> <m1kxTmy-0000KhC@stereo.hq.phicoh.net> <6F3726EE-F089-4F26-BB30-F22686617C03@fugue.com> <m1kxWh9-0000ImC@stereo.hq.phicoh.net> <BE6C041F-94B2-400D-B114-A76962190660@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3445.9.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/8E2XIsjHNX1qq1Bq6NlJ34G_8gA>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jan 2021 01:18:53 -0000

> On 8 Jan 2021, at 02:08, Ted Lemon <mellon@fugue.com> wrote:
>=20
> On Jan 7, 2021, at 9:55 AM, Philip Homburg =
<pch-ipv6-ietf-7@u-1.phicoh.com> wrote:
>> I can see a few benefits of Mark's proposal. One is that it is good =
to
>> have a standard representation of information. In particular,
>> Mark's proposal would make it possible to have a master zone file =
that has
>> both public and private DNS entries. Then a split-DNS server could =
serve
>> only the public data to the outside world.=20
>=20
> That=E2=80=99s a good point, although it would still be a good point =
if this were just a feature of the zone file and not of the wire format.
>=20
>> At the same time, I think it would be great if we can put link-local =
addresses
>> in DNS.=20
>=20
> That sounds like a really heavy lift.
>=20
>> It may tie in nicely with scope IDs in socket addresses. If a DNS
>> record specifies that is valid only on a VPN link, then maybe we can =
already
>> tie the address to that link. No need to change applications, it can =
be
>> hidden in the stub resolver.
>=20
> Now we need to standardize a way to identify links. This is a Hard =
Problem. I say this based on experience, not supposition. HNCP tried to =
do this, not as successfully as I=E2=80=99d hoped. I=E2=80=99ve been =
working on it for the Thread Border Router work, and haven=E2=80=99t =
come up with a general solution. Sure, if you have a data center and a =
managed multi-subnet LAN, and you can just type in configurations, this =
works, but most networks aren=E2=80=99t like that.  I think the VPN case =
is probably tractable, but it=E2=80=99s really hard to see a path to =
broad adoption for this idea.


My idea would be that there would also be a RA option(s) which =
advertised the names in the SA records that where applicable to the =
link.  Implicit to that is that there would be a API that allows =
getaddrinfo() to retrieve the
RA options for individual links and for all links on the node.  =
getaddrinfo() would use the later.  The former would be used to =
construct UPDATE requests for the DNS etc.  LLSANAME (link-local SA =
name), ULASANAM (ULA SA name), and perhaps others.

> If there is a path to broad adoption, it probably involves bottom-up =
work, not top-down design. Most of the ideas I=E2=80=99ve had about this =
that I think are practicable are very context-dependent. E.g., you can =
identify that you are on the same link because you received a =
link-scoped multicast.
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org


From nobody Thu Jan  7 17:43:37 2021
Return-Path: <mellon@fugue.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 7F5103A1003 for <v6ops@ietfa.amsl.com>; Thu,  7 Jan 2021 17:43:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 qShHz2wlAdeo for <v6ops@ietfa.amsl.com>; Thu,  7 Jan 2021 17:43:29 -0800 (PST)
Received: from mail-il1-x12d.google.com (mail-il1-x12d.google.com [IPv6:2607:f8b0:4864:20::12d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A2BF3A1009 for <v6ops@ietf.org>; Thu,  7 Jan 2021 17:43:29 -0800 (PST)
Received: by mail-il1-x12d.google.com with SMTP id w17so8724299ilj.8 for <v6ops@ietf.org>; Thu, 07 Jan 2021 17:43:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=8J5gFQ2761GivqJ2GMSAh8u54jZpfCOfPDNj0hNvxgs=; b=WsJnKYY0DrYgSvmaE+MGr20HwxywcxRHtOw/V7Xw69IsUgYvYp8AXAVfLE2KLNVhs0 no8R0ezHOy1CQvjzxySp3SkY9T4c+Zv3z9zsuQeT9mISj3QxDOWvZgpKefwUa2UaS3DY ifKxMY06QxxIUQwgv5tBQ5q4kAYuE+hwl8dPYWlf5P/1dyh1tmLtU3bwf9FNITiNGA8L ka7zQ5RlDrwFgmco366x59imGtr3PRENSzt+VqRa0951AChIELbsgPz/UOE+sF/lZTio /MGeg5TQlpONUOryTeFHbDc3ASY1SL7GM8kUu56ZI7Nr+sk8tzPt/J1ZXlOGDLsdsIkm qVLg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=8J5gFQ2761GivqJ2GMSAh8u54jZpfCOfPDNj0hNvxgs=; b=Qiqsfe+h6QEWGVQWOWh/2qyIbrO/mNZdcfRzWQpxVOxeH+0lpH97z+tM8TzCXJz3Wa deOPrkEXsY0izwzAeFthkM3d8zDCjdxjBNtiSOmwfu4FDAwjXdbu9lc+TWJGKPQ26b7A ggCKrm+gJhK37rKG50soDV+qvmi6i4sxwXwOjnbGrk3oS4iUPX+YbaXRZFRqfKOym8jN x6WCTzsHhWzWrcsT8gnfi4eQcfl0Rz14612NbME1L/kBua1oKMJBliC8KtV7TPJTvox8 xKpiEBa/lccIG2tbwufYXsZSN1zpBCW7xJidFmkYv4VUY/NcatulKMG9aUYlCgMv1G9p E1ZQ==
X-Gm-Message-State: AOAM533D1OQtWuIIKZ9JlZtI8hDfIoYjJmMSOyNWj+30QBjgGVJcxNTG VlnrmNxHCjsRZI7Hz5fkLBg+F+AQR9nggg==
X-Google-Smtp-Source: ABdhPJzPWzyTJgRE06yUBRz34bDK2tuahTAywlkfExpzpIxdEpp7oQqYlIaA4oncSpqjXV4b2qoZGA==
X-Received: by 2002:a92:9a42:: with SMTP id t63mr1713230ili.176.1610070208041;  Thu, 07 Jan 2021 17:43:28 -0800 (PST)
Received: from [192.168.4.114] (c-24-91-177-160.hsd1.nh.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id v3sm5655977ilj.28.2021.01.07.17.43.26 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 07 Jan 2021 17:43:27 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Ted Lemon <mellon@fugue.com>
Mime-Version: 1.0 (1.0)
Date: Thu, 7 Jan 2021 20:43:25 -0500
Message-Id: <AD20A505-14C4-4E8D-B28C-F237ECE55227@fugue.com>
References: <78D0D84C-53DB-4661-BA43-CFEB1F377BB4@isc.org>
Cc: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, IPv6 Operations <v6ops@ietf.org>, IPv6 List <ipv6@ietf.org>
In-Reply-To: <78D0D84C-53DB-4661-BA43-CFEB1F377BB4@isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: iPhone Mail (18E118)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/cO24QiiVg4mgqECVE7P7InSapRg>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jan 2021 01:43:32 -0000

Who determines what names to use?  What is the scope of the names? How is un=
iqueness guaranteed in that scope?

> On Jan 7, 2021, at 20:18, Mark Andrews <marka@isc.org> wrote:
>=20
> =EF=BB=BF
>=20
>> On 8 Jan 2021, at 02:08, Ted Lemon <mellon@fugue.com> wrote:
>>=20
>>> On Jan 7, 2021, at 9:55 AM, Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.c=
om> wrote:
>>> I can see a few benefits of Mark's proposal. One is that it is good to
>>> have a standard representation of information. In particular,
>>> Mark's proposal would make it possible to have a master zone file that h=
as
>>> both public and private DNS entries. Then a split-DNS server could serve=

>>> only the public data to the outside world.=20
>>=20
>> That=E2=80=99s a good point, although it would still be a good point if t=
his were just a feature of the zone file and not of the wire format.
>>=20
>>> At the same time, I think it would be great if we can put link-local add=
resses
>>> in DNS.=20
>>=20
>> That sounds like a really heavy lift.
>>=20
>>> It may tie in nicely with scope IDs in socket addresses. If a DNS
>>> record specifies that is valid only on a VPN link, then maybe we can alr=
eady
>>> tie the address to that link. No need to change applications, it can be
>>> hidden in the stub resolver.
>>=20
>> Now we need to standardize a way to identify links. This is a Hard Proble=
m. I say this based on experience, not supposition. HNCP tried to do this, n=
ot as successfully as I=E2=80=99d hoped. I=E2=80=99ve been working on it for=
 the Thread Border Router work, and haven=E2=80=99t come up with a general s=
olution. Sure, if you have a data center and a managed multi-subnet LAN, and=
 you can just type in configurations, this works, but most networks aren=E2=80=
=99t like that.  I think the VPN case is probably tractable, but it=E2=80=99=
s really hard to see a path to broad adoption for this idea.
>=20
>=20
> My idea would be that there would also be a RA option(s) which advertised t=
he names in the SA records that where applicable to the link.  Implicit to t=
hat is that there would be a API that allows getaddrinfo() to retrieve the
> RA options for individual links and for all links on the node.  getaddrinf=
o() would use the later.  The former would be used to construct UPDATE reque=
sts for the DNS etc.  LLSANAME (link-local SA name), ULASANAM (ULA SA name),=
 and perhaps others.
>=20
>> If there is a path to broad adoption, it probably involves bottom-up work=
, not top-down design. Most of the ideas I=E2=80=99ve had about this that I t=
hink are practicable are very context-dependent. E.g., you can identify that=
 you are on the same link because you received a link-scoped multicast.
>>=20
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>=20
> --=20
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742              INTERNET: marka@isc.org
>=20


From nobody Thu Jan  7 18:03:07 2021
Return-Path: <marka@isc.org>
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 6C2A83A1027; Thu,  7 Jan 2021 18:03:01 -0800 (PST)
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, SPF_HELO_NONE=0.001, 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 8moXa2OxbWJo; Thu,  7 Jan 2021 18:02:59 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8D753A1026; Thu,  7 Jan 2021 18:02:59 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 6C7B23AB0C8; Fri,  8 Jan 2021 02:02:59 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 5A633160051; Fri,  8 Jan 2021 02:02:59 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 46B65160056; Fri,  8 Jan 2021 02:02:59 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Q7PVha7OvWtH; Fri,  8 Jan 2021 02:02:59 +0000 (UTC)
Received: from [172.30.42.68] (n114-75-149-106.bla4.nsw.optusnet.com.au [114.75.149.106]) by zmx1.isc.org (Postfix) with ESMTPSA id 4CD9C160051; Fri,  8 Jan 2021 02:02:58 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.7\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <AD20A505-14C4-4E8D-B28C-F237ECE55227@fugue.com>
Date: Fri, 8 Jan 2021 13:02:54 +1100
Cc: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, IPv6 Operations <v6ops@ietf.org>, IPv6 List <ipv6@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <37D4E745-95A0-4B57-8FC7-D9DF0882FECF@isc.org>
References: <78D0D84C-53DB-4661-BA43-CFEB1F377BB4@isc.org> <AD20A505-14C4-4E8D-B28C-F237ECE55227@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3445.9.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/UigkeA-eTBQ4YkqDXIjgWGZvKCg>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jan 2021 02:03:02 -0000

> On 8 Jan 2021, at 12:43, Ted Lemon <mellon@fugue.com> wrote:
>=20
> Who determines what names to use?  What is the scope of the names? How =
is uniqueness guaranteed in that scope?

One would recommend using suffix names that are already registered to =
the organisation, individual in the DNS.
The example names I used where using the individuals suffix (id.au) but =
the idea is to leverage the existing global DNS to provide uniqueness.  =
If you don=E2=80=99t have a domain name generate a random 160 bit number =
and base32 encode it (like NSEC3) or similar and append .home.arpa to =
it.  If you are publishing into the global DNS you have a registered =
name to use as a suffix.  If you aren=E2=80=99t publishing into the =
global DNS you need to ensure the names don=E2=80=99t clash with any in =
the global DNS, <label>.home.arpa qualifies.   If you don=E2=80=99t like =
home.arpa, register a another name to be the default suffix labels.

>> On Jan 7, 2021, at 20:18, Mark Andrews <marka@isc.org> wrote:
>>=20
>> =EF=BB=BF
>>=20
>>> On 8 Jan 2021, at 02:08, Ted Lemon <mellon@fugue.com> wrote:
>>>=20
>>>> On Jan 7, 2021, at 9:55 AM, Philip Homburg =
<pch-ipv6-ietf-7@u-1.phicoh.com> wrote:
>>>> I can see a few benefits of Mark's proposal. One is that it is good =
to
>>>> have a standard representation of information. In particular,
>>>> Mark's proposal would make it possible to have a master zone file =
that has
>>>> both public and private DNS entries. Then a split-DNS server could =
serve
>>>> only the public data to the outside world.=20
>>>=20
>>> That=E2=80=99s a good point, although it would still be a good point =
if this were just a feature of the zone file and not of the wire format.
>>>=20
>>>> At the same time, I think it would be great if we can put =
link-local addresses
>>>> in DNS.=20
>>>=20
>>> That sounds like a really heavy lift.
>>>=20
>>>> It may tie in nicely with scope IDs in socket addresses. If a DNS
>>>> record specifies that is valid only on a VPN link, then maybe we =
can already
>>>> tie the address to that link. No need to change applications, it =
can be
>>>> hidden in the stub resolver.
>>>=20
>>> Now we need to standardize a way to identify links. This is a Hard =
Problem. I say this based on experience, not supposition. HNCP tried to =
do this, not as successfully as I=E2=80=99d hoped. I=E2=80=99ve been =
working on it for the Thread Border Router work, and haven=E2=80=99t =
come up with a general solution. Sure, if you have a data center and a =
managed multi-subnet LAN, and you can just type in configurations, this =
works, but most networks aren=E2=80=99t like that.  I think the VPN case =
is probably tractable, but it=E2=80=99s really hard to see a path to =
broad adoption for this idea.
>>=20
>>=20
>> My idea would be that there would also be a RA option(s) which =
advertised the names in the SA records that where applicable to the =
link.  Implicit to that is that there would be a API that allows =
getaddrinfo() to retrieve the
>> RA options for individual links and for all links on the node.  =
getaddrinfo() would use the later.  The former would be used to =
construct UPDATE requests for the DNS etc.  LLSANAME (link-local SA =
name), ULASANAM (ULA SA name), and perhaps others.
>>=20
>>> If there is a path to broad adoption, it probably involves bottom-up =
work, not top-down design. Most of the ideas I=E2=80=99ve had about this =
that I think are practicable are very context-dependent. E.g., you can =
identify that you are on the same link because you received a =
link-scoped multicast.
>>>=20
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>=20
>> --=20
>> Mark Andrews, ISC
>> 1 Seymour St., Dundas Valley, NSW 2117, Australia
>> PHONE: +61 2 9871 4742              INTERNET: marka@isc.org
>>=20

--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org


From nobody Thu Jan  7 18:04:47 2021
Return-Path: <mellon@fugue.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 527863A1027 for <v6ops@ietfa.amsl.com>; Thu,  7 Jan 2021 18:04:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 ctXIvac6cNGy for <v6ops@ietfa.amsl.com>; Thu,  7 Jan 2021 18:04:40 -0800 (PST)
Received: from mail-il1-x12c.google.com (mail-il1-x12c.google.com [IPv6:2607:f8b0:4864:20::12c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 054933A1026 for <v6ops@ietf.org>; Thu,  7 Jan 2021 18:04:30 -0800 (PST)
Received: by mail-il1-x12c.google.com with SMTP id q1so8803925ilt.6 for <v6ops@ietf.org>; Thu, 07 Jan 2021 18:04:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=ND8hyy8A9Mb25GbzYle6TeAyeFbUUn65EWqjONTG4Ow=; b=XKKY4f581FtqjZ9Y1VUxLbA11spisRaKCHbYuzz71aeZVELaszF0GLs317tk8FWKRQ AINcf34mtUWx/xe4pXv8GPQSxL+S25ts/SNZzmEWzCH9GzmiOO8+MlL6Dpe0kunKl0Uz I/DpebZaMe/yFc3ZxmVlM21rzMNDjTORjpz23FKhC0ZDT4KopeqcRuHhJ7NsiYDIvgx3 4U6aiFOvkUqNqbnshX39Qb2VRl5uVdkxuV9o1mc1QvTbxOamvxaFUWFchDdgiCxdyieH qVnIUc8vfF3gGnFl8CXEgCodVp7zFsnjueA1LHOxmwrL/e7SIWzC6LN5tVBcmJOLxEGt Lt1Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=ND8hyy8A9Mb25GbzYle6TeAyeFbUUn65EWqjONTG4Ow=; b=KhThEPckXQDT3Ank2syDj653sxp5Rr3JsFKd7YSDJLqkXmLRFvrmqbTImC34PrWkA6 ptwzaoqPRKWNxcas7Zj6Bj5MofGmWe7cVVV7jG+R2BbIJTdq8uNEBD8oX/fQWiTkm/kv nlLGsDTRcJQNs5XbH6EwsU7VieIP9vx1fX0G+7Fkgjk/Gx+U/mN2m7u1Kt1FQvVzhe27 d41eGjJuO4J0hlFZsvkzLDNsxdoeH2YHA0Z8gnRz7dBR4KkWSufiWj0wRd4uKcFscay2 FFEsDED05bEtClhW4V2sUlHe6ZbeFLfNm0aFN0YUA1LUGHO7nEb8OamsuykeYSIbiOnG bxNQ==
X-Gm-Message-State: AOAM530BR+gEzgYMv+gihA0+0ljy0jEI35S1UWkFvYm+IV/ns2UNJfH8 0PxjWhxGvvcLSqCxyM9lq0qgTw==
X-Google-Smtp-Source: ABdhPJxZZ4ZiMHc5gi+24Y7gmmcZYP8zVNoWv4zv+eoi0rTk2mwnqLjNT779BGqGAWaQxNHFZ5eGtg==
X-Received: by 2002:a05:6e02:68b:: with SMTP id o11mr1726318ils.237.1610071470285;  Thu, 07 Jan 2021 18:04:30 -0800 (PST)
Received: from [192.168.4.70] (c-24-91-177-160.hsd1.nh.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id y5sm5826021ilh.24.2021.01.07.18.04.29 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Jan 2021 18:04:29 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <5017FC11-7C58-4F56-AFAA-3D6BF5A2555C@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_34F12CE3-20CB-475C-9C88-EE1DA0E91BFF"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.2\))
Date: Thu, 7 Jan 2021 21:04:27 -0500
In-Reply-To: <37D4E745-95A0-4B57-8FC7-D9DF0882FECF@isc.org>
Cc: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, IPv6 Operations <v6ops@ietf.org>, IPv6 List <ipv6@ietf.org>
To: Mark Andrews <marka@isc.org>
References: <78D0D84C-53DB-4661-BA43-CFEB1F377BB4@isc.org> <AD20A505-14C4-4E8D-B28C-F237ECE55227@fugue.com> <37D4E745-95A0-4B57-8FC7-D9DF0882FECF@isc.org>
X-Mailer: Apple Mail (2.3654.60.0.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/si5xwmHY1dXvYGqvm_YIF2v2ILQ>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jan 2021 02:04:43 -0000

--Apple-Mail=_34F12CE3-20CB-475C-9C88-EE1DA0E91BFF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Jan 7, 2021, at 9:02 PM, Mark Andrews <marka@isc.org> wrote:
> The example names I used where using the individuals suffix (id.au =
<http://id.au/>) but the idea is to leverage the existing global DNS to =
provide uniqueness.=20

That works pretty well for ULAs, but not for LLAs. For LLAs you need to =
identify the link, and that=E2=80=99s just not a simple thing to do, as =
I explained earlier.


--Apple-Mail=_34F12CE3-20CB-475C-9C88-EE1DA0E91BFF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">On =
Jan 7, 2021, at 9:02 PM, Mark Andrews &lt;<a href=3D"mailto:marka@isc.org"=
 class=3D"">marka@isc.org</a>&gt; wrote:<div><blockquote type=3D"cite" =
class=3D""><div class=3D""><meta charset=3D"UTF-8" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: UbuntuMono-Regular; =
font-size: 14px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">The example =
names I used where using the individuals suffix (</span><a =
href=3D"http://id.au/" style=3D"font-family: UbuntuMono-Regular; =
font-size: 14px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">id.au</a><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: UbuntuMono-Regular; =
font-size: 14px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">) but the =
idea is to leverage the existing global DNS to provide uniqueness.<span =
class=3D"Apple-converted-space">&nbsp;</span></span></div></blockquote></d=
iv><br class=3D""><div class=3D"">That works pretty well for ULAs, but =
not for LLAs. For LLAs you need to identify the link, and that=E2=80=99s =
just not a simple thing to do, as I explained earlier.</div><div =
class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_34F12CE3-20CB-475C-9C88-EE1DA0E91BFF--


From nobody Thu Jan  7 18:48:33 2021
Return-Path: <marka@isc.org>
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 7BE153A00C4; Thu,  7 Jan 2021 18:48:27 -0800 (PST)
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, SPF_HELO_NONE=0.001, 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 tDGLuMHDWo9t; Thu,  7 Jan 2021 18:48:26 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39E603A0062; Thu,  7 Jan 2021 18:48:26 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 696193BD49A; Fri,  8 Jan 2021 02:48:24 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 4BF2B160051; Fri,  8 Jan 2021 02:48:24 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 1C10116005A; Fri,  8 Jan 2021 02:48:24 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 9R14mqQSDWJD; Fri,  8 Jan 2021 02:48:24 +0000 (UTC)
Received: from [172.30.42.68] (n114-75-149-106.bla4.nsw.optusnet.com.au [114.75.149.106]) by zmx1.isc.org (Postfix) with ESMTPSA id 1EE2D160056; Fri,  8 Jan 2021 02:48:22 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.7\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <5017FC11-7C58-4F56-AFAA-3D6BF5A2555C@fugue.com>
Date: Fri, 8 Jan 2021 13:48:18 +1100
Cc: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, IPv6 Operations <v6ops@ietf.org>, IPv6 List <ipv6@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E3625337-3A59-4F0A-9EEE-EC8F6B39C965@isc.org>
References: <78D0D84C-53DB-4661-BA43-CFEB1F377BB4@isc.org> <AD20A505-14C4-4E8D-B28C-F237ECE55227@fugue.com> <37D4E745-95A0-4B57-8FC7-D9DF0882FECF@isc.org> <5017FC11-7C58-4F56-AFAA-3D6BF5A2555C@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3445.9.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/5rEdsMRn-_U4B23yjYKxusqBoqM>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jan 2021 02:48:28 -0000

> On 8 Jan 2021, at 13:04, Ted Lemon <mellon@fugue.com> wrote:
>=20
> On Jan 7, 2021, at 9:02 PM, Mark Andrews <marka@isc.org> wrote:
>> The example names I used where using the individuals suffix (id.au) =
but the idea is to leverage the existing global DNS to provide =
uniqueness.=20
>=20
> That works pretty well for ULAs, but not for LLAs. For LLAs you need =
to identify the link, and that=E2=80=99s just not a simple thing to do, =
as I explained earlier.

Actually you haven=E2=80=99t explained.  You have stated.  You said it =
was hard.  Hard is not intractable.

If you are willing for a link to have multiple names just have reach =
router generate its own random 160 bit base32 encoded label for each =
interface, append the well know suffix and advertise it.  You will get =
multiple SA records for the same interface if there are multiple routers =
but that should not be a issue.  With 160 random bits the need to do =
collision detection is really non-existent.  We=E2=80=99ve resolved this =
for NSEC3 and DNS changes 15 years ago.  This will scale into millions =
of router interfaces.

If you want to have a single link name then we need to define a protocol =
for the routers on the link to select one of the names.  This may end up =
being technology linked.  Router with smallest L-L address wins would be =
one solution to this.

Yes, I really do expect every machine to update its own addresses in the =
DNS.  We do know how to do that securely with SIG(0).


--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org


From nobody Thu Jan  7 18:53:20 2021
Return-Path: <marka@isc.org>
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 C557A3A00D9; Thu,  7 Jan 2021 18:53:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 ljDQzJ3VYttH; Thu,  7 Jan 2021 18:53:12 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57F273A00D2; Thu,  7 Jan 2021 18:53:12 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 36E8E3AB0CD; Fri,  8 Jan 2021 02:53:12 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 2AA7A160051; Fri,  8 Jan 2021 02:53:12 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 195C2160056; Fri,  8 Jan 2021 02:53:12 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id zXQYhH1frFFX; Fri,  8 Jan 2021 02:53:12 +0000 (UTC)
Received: from [172.30.42.68] (n114-75-149-106.bla4.nsw.optusnet.com.au [114.75.149.106]) by zmx1.isc.org (Postfix) with ESMTPSA id 4A5C5160051; Fri,  8 Jan 2021 02:53:11 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.7\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <E3625337-3A59-4F0A-9EEE-EC8F6B39C965@isc.org>
Date: Fri, 8 Jan 2021 13:53:08 +1100
Cc: IPv6 Operations <v6ops@ietf.org>, IPv6 List <ipv6@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1A24DB0F-4173-4A3E-A706-B295BCCDDD5A@isc.org>
References: <78D0D84C-53DB-4661-BA43-CFEB1F377BB4@isc.org> <AD20A505-14C4-4E8D-B28C-F237ECE55227@fugue.com> <37D4E745-95A0-4B57-8FC7-D9DF0882FECF@isc.org> <5017FC11-7C58-4F56-AFAA-3D6BF5A2555C@fugue.com> <E3625337-3A59-4F0A-9EEE-EC8F6B39C965@isc.org>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3445.9.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/M77qBkeESmhhoPe1d61KZkBRVek>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jan 2021 02:53:14 -0000

> On 8 Jan 2021, at 13:48, Mark Andrews <marka@isc.org> wrote:
>=20
>=20
>=20
>> On 8 Jan 2021, at 13:04, Ted Lemon <mellon@fugue.com> wrote:
>>=20
>> On Jan 7, 2021, at 9:02 PM, Mark Andrews <marka@isc.org> wrote:
>>> The example names I used where using the individuals suffix (id.au) =
but the idea is to leverage the existing global DNS to provide =
uniqueness.=20
>>=20
>> That works pretty well for ULAs, but not for LLAs. For LLAs you need =
to identify the link, and that=E2=80=99s just not a simple thing to do, =
as I explained earlier.
>=20
> Actually you haven=E2=80=99t explained.  You have stated.  You said it =
was hard.  Hard is not intractable.
>=20
> If you are willing for a link to have multiple names just have reach =
router generate its own random 160 bit base32 encoded label for each =
interface, append the well know suffix and advertise it.  You will get =
multiple SA records for the same interface if there are multiple routers =
but that should not be a issue.  With 160 random bits the need to do =
collision detection is really non-existent.  We=E2=80=99ve resolved this =
for NSEC3 and DNS changes 15 years ago.  This will scale into millions =
of router interfaces.
>=20
> If you want to have a single link name then we need to define a =
protocol for the routers on the link to select one of the names.  This =
may end up being technology linked.  Router with smallest L-L address =
wins would be one solution to this.
>=20
> Yes, I really do expect every machine to update its own addresses in =
the DNS.  We do know how to do that securely with SIG(0).

For those playing along at home we are talking about link names like

	RBS4LI8FAPU7LSBL3TLC14T2A7L7DB66.home.arpa.

they aren=E2=80=99t pretty buy they work.

> --=20
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742              INTERNET: marka@isc.org
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org


From nobody Thu Jan  7 18:54:59 2021
Return-Path: <mellon@fugue.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 931B93A0813 for <v6ops@ietfa.amsl.com>; Thu,  7 Jan 2021 18:54:52 -0800 (PST)
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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 06WcTR2cEoHu for <v6ops@ietfa.amsl.com>; Thu,  7 Jan 2021 18:54:47 -0800 (PST)
Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EF3E3A00D8 for <v6ops@ietf.org>; Thu,  7 Jan 2021 18:54:42 -0800 (PST)
Received: by mail-io1-xd34.google.com with SMTP id m23so8407994ioy.2 for <v6ops@ietf.org>; Thu, 07 Jan 2021 18:54:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=i6mskdowgp5qEBZVis9gn+86uBTV0O13lViUq0qbFcw=; b=XwmvzTfHEwKYf7TxyB9jMeHIP9KEY96a5RHTTD52m9eE5+ifhQYZZdyLZNqf+lFeSV t9zdWATX9cwJl2C++CXDN1sp7aRr6UT7ZhZ8SgmxjnO+AYOkvLfUajcnNkWOnUA9cftq BQVdU0HCbs3ffDEDVY2Mx+E8MC84GV8joQatSBovAGnK0JxQk9nNC8KNZkcXO3EZ0Gp6 oIx2aJ5mTy8Xi5FvqJa0k7Pf/6bRyy8n2icGZmPyqRrdJZfbtBppc2qSv7KrQGjyji7m 9Ko5Oyz9nd+karrXvrhySJnKM4RegC/ky2qOPlFSAWVn0MZM/LeKQINsWz4KM1wMUieG XdlA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=i6mskdowgp5qEBZVis9gn+86uBTV0O13lViUq0qbFcw=; b=kphSSlut7d9L1F7nnpFmLf/7lvvVrCISJSPvydSnm5ZqgbBz/5t8Hgv1FlFg5FxUcr yH4qK8Rb7qneE/TMEl+8Snj37XJCpkyMFXRLg/3yjEelWOb0afFUQ2ZVTiuNpgnqzUuk UQJUNg7jX3uyeEIOkY3bOTjpOEd4mxqN3uv/OLKoDA6fYdjIOLjPA+krDURs8Jjs55B1 c20NHH+/0SsCHnqwPmsrgZiyTnnkh9PWkQPWSETMfzSFcunaM8tWcl1T885INz12MkNH /ha8EEwKng39TlCsH01yrh/Uz9GYfOjOAb2NNe80Ki6V31BZ0nmZsyXKjoIGZctP+YbV ZqLA==
X-Gm-Message-State: AOAM5320skStUGwEKG+VZqcs9L+A9WHm0/da8rpUrumAGTI9WNpIig8j 6bhfTSdEULeqSSoqyGMCbU7Ybx6wXczmpg==
X-Google-Smtp-Source: ABdhPJy8B6oNpZYhRLvBEWjnxB50XGHjFVmRFG4TD+SWPP71VBiUh0Iq/ty1kqXuu8Z5Hp5gd5CSow==
X-Received: by 2002:a02:b70d:: with SMTP id g13mr1522504jam.46.1610074481267;  Thu, 07 Jan 2021 18:54:41 -0800 (PST)
Received: from [192.168.4.114] (c-24-91-177-160.hsd1.ma.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id b6sm5796953ilv.79.2021.01.07.18.54.40 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 07 Jan 2021 18:54:40 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Ted Lemon <mellon@fugue.com>
Mime-Version: 1.0 (1.0)
Date: Thu, 7 Jan 2021 21:54:39 -0500
Message-Id: <537EBE5A-6554-4904-8701-03940C914FE3@fugue.com>
References: <E3625337-3A59-4F0A-9EEE-EC8F6B39C965@isc.org>
Cc: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, IPv6 Operations <v6ops@ietf.org>, IPv6 List <ipv6@ietf.org>
In-Reply-To: <E3625337-3A59-4F0A-9EEE-EC8F6B39C965@isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: iPhone Mail (18E118)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/JWQjWY8pHXpPWyjnBVQogb6-CnI>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jan 2021 02:54:58 -0000

Right. That=E2=80=99s how you do it. And then what happens with the topology=
 changes?  The random ids are no longer referring to the same links. Solving=
 this problem adequately is way more work than it=E2=80=99s worth. The thras=
hing in the database would be brutal.=20

> On Jan 7, 2021, at 21:48, Mark Andrews <marka@isc.org> wrote:
>=20
> =EF=BB=BF
>=20
>> On 8 Jan 2021, at 13:04, Ted Lemon <mellon@fugue.com> wrote:
>>=20
>>> On Jan 7, 2021, at 9:02 PM, Mark Andrews <marka@isc.org> wrote:
>>> The example names I used where using the individuals suffix (id.au) but t=
he idea is to leverage the existing global DNS to provide uniqueness.=20
>>=20
>> That works pretty well for ULAs, but not for LLAs. For LLAs you need to i=
dentify the link, and that=E2=80=99s just not a simple thing to do, as I exp=
lained earlier.
>=20
> Actually you haven=E2=80=99t explained.  You have stated.  You said it was=
 hard.  Hard is not intractable.
>=20
> If you are willing for a link to have multiple names just have reach route=
r generate its own random 160 bit base32 encoded label for each interface, a=
ppend the well know suffix and advertise it.  You will get multiple SA recor=
ds for the same interface if there are multiple routers but that should not b=
e a issue.  With 160 random bits the need to do collision detection is reall=
y non-existent.  We=E2=80=99ve resolved this for NSEC3 and DNS changes 15 ye=
ars ago.  This will scale into millions of router interfaces.
>=20
> If you want to have a single link name then we need to define a protocol f=
or the routers on the link to select one of the names.  This may end up bein=
g technology linked.  Router with smallest L-L address wins would be one sol=
ution to this.
>=20
> Yes, I really do expect every machine to update its own addresses in the D=
NS.  We do know how to do that securely with SIG(0).
>=20
>=20
> --=20
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742              INTERNET: marka@isc.org
>=20


From nobody Thu Jan  7 19:02:56 2021
Return-Path: <marka@isc.org>
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 6F4A63A0127; Thu,  7 Jan 2021 19:02:49 -0800 (PST)
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, SPF_HELO_NONE=0.001, 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 Q4Yf8dEE5_se; Thu,  7 Jan 2021 19:02:48 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9B173A011D; Thu,  7 Jan 2021 19:02:47 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 703543BD447; Fri,  8 Jan 2021 03:02:47 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 2AA3716005A; Fri,  8 Jan 2021 03:02:10 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 10FD7160056; Fri,  8 Jan 2021 03:02:10 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 8yG40Pm4Frfd; Fri,  8 Jan 2021 03:02:09 +0000 (UTC)
Received: from [172.30.42.68] (n114-75-149-106.bla4.nsw.optusnet.com.au [114.75.149.106]) by zmx1.isc.org (Postfix) with ESMTPSA id 12C85160051; Fri,  8 Jan 2021 03:02:08 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.7\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <537EBE5A-6554-4904-8701-03940C914FE3@fugue.com>
Date: Fri, 8 Jan 2021 14:02:06 +1100
Cc: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, IPv6 Operations <v6ops@ietf.org>, IPv6 List <ipv6@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5A9F034B-64AB-4A96-BB8C-7A9286EF2654@isc.org>
References: <E3625337-3A59-4F0A-9EEE-EC8F6B39C965@isc.org> <537EBE5A-6554-4904-8701-03940C914FE3@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3445.9.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/HoZCvlmQMDQsiUQU0Rw9TH50nlY>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jan 2021 03:02:50 -0000

> On 8 Jan 2021, at 13:54, Ted Lemon <mellon@fugue.com> wrote:
>=20
> Right. That=E2=80=99s how you do it. And then what happens with the =
topology changes?  The random ids are no longer referring to the same =
links. Solving this problem adequately is way more work than it=E2=80=99s =
worth. The thrashing in the database would be brutal.=20

You publish updated records.  If you are changing topology the addresses =
of the nodes are almost certainly changing anyway. Publishing new L-L SA =
records along with new ULA and GUA is minimal extra expense.

>> On Jan 7, 2021, at 21:48, Mark Andrews <marka@isc.org> wrote:
>>=20
>> =EF=BB=BF
>>=20
>>> On 8 Jan 2021, at 13:04, Ted Lemon <mellon@fugue.com> wrote:
>>>=20
>>>> On Jan 7, 2021, at 9:02 PM, Mark Andrews <marka@isc.org> wrote:
>>>> The example names I used where using the individuals suffix (id.au) =
but the idea is to leverage the existing global DNS to provide =
uniqueness.=20
>>>=20
>>> That works pretty well for ULAs, but not for LLAs. For LLAs you need =
to identify the link, and that=E2=80=99s just not a simple thing to do, =
as I explained earlier.
>>=20
>> Actually you haven=E2=80=99t explained.  You have stated.  You said =
it was hard.  Hard is not intractable.
>>=20
>> If you are willing for a link to have multiple names just have reach =
router generate its own random 160 bit base32 encoded label for each =
interface, append the well know suffix and advertise it.  You will get =
multiple SA records for the same interface if there are multiple routers =
but that should not be a issue.  With 160 random bits the need to do =
collision detection is really non-existent.  We=E2=80=99ve resolved this =
for NSEC3 and DNS changes 15 years ago.  This will scale into millions =
of router interfaces.
>>=20
>> If you want to have a single link name then we need to define a =
protocol for the routers on the link to select one of the names.  This =
may end up being technology linked.  Router with smallest L-L address =
wins would be one solution to this.
>>=20
>> Yes, I really do expect every machine to update its own addresses in =
the DNS.  We do know how to do that securely with SIG(0).
>>=20
>>=20
>> --=20
>> Mark Andrews, ISC
>> 1 Seymour St., Dundas Valley, NSW 2117, Australia
>> PHONE: +61 2 9871 4742              INTERNET: marka@isc.org
>>=20

--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org


From nobody Thu Jan  7 19:18:51 2021
Return-Path: <marka@isc.org>
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 6ED2A3A040B; Thu,  7 Jan 2021 19:18:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 kziSvSUlJkx4; Thu,  7 Jan 2021 19:18:43 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D42B63A03FC; Thu,  7 Jan 2021 19:18:43 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id D96BF3BD447; Fri,  8 Jan 2021 03:18:41 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id C806D160051; Fri,  8 Jan 2021 03:18:41 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id A5165160056; Fri,  8 Jan 2021 03:18:41 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id yNw8TR1kMBzp; Fri,  8 Jan 2021 03:18:41 +0000 (UTC)
Received: from [172.30.42.68] (n114-75-149-106.bla4.nsw.optusnet.com.au [114.75.149.106]) by zmx1.isc.org (Postfix) with ESMTPSA id 79D8E160051; Fri,  8 Jan 2021 03:18:40 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.7\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <5A9F034B-64AB-4A96-BB8C-7A9286EF2654@isc.org>
Date: Fri, 8 Jan 2021 14:18:38 +1100
Cc: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, IPv6 Operations <v6ops@ietf.org>, IPv6 List <ipv6@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <057ABF22-4C44-4EB7-8AF5-E9F173D67F2E@isc.org>
References: <E3625337-3A59-4F0A-9EEE-EC8F6B39C965@isc.org> <537EBE5A-6554-4904-8701-03940C914FE3@fugue.com> <5A9F034B-64AB-4A96-BB8C-7A9286EF2654@isc.org>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3445.9.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/GTM7Dml8HBSpbLct5yGM7Ev7kYA>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jan 2021 03:18:45 -0000

> On 8 Jan 2021, at 14:02, Mark Andrews <marka@isc.org> wrote:
>=20
>=20
>=20
>> On 8 Jan 2021, at 13:54, Ted Lemon <mellon@fugue.com> wrote:
>>=20
>> Right. That=E2=80=99s how you do it. And then what happens with the =
topology changes?  The random ids are no longer referring to the same =
links. Solving this problem adequately is way more work than it=E2=80=99s =
worth. The thrashing in the database would be brutal.=20
>=20
> You publish updated records.  If you are changing topology the =
addresses of the nodes are almost certainly changing anyway. Publishing =
new L-L SA records along with new ULA and GUA is minimal extra expense.

When you change topology the node will see new RAs and getaddrinfo() =
will filter out all the old addresses.  The node has a set of link =
identifiers for links it is attached to.  Remember machines don=E2=80=99t =
care about these names.  They are just ways to filter out the currently =
useful addresses.  Each node will maintain its own mapping from =
applicable names to sin6_scope_id which will be filled in by =
getaddrinfo() generated by the RAs it sees.

>>> On Jan 7, 2021, at 21:48, Mark Andrews <marka@isc.org> wrote:
>>>=20
>>> =EF=BB=BF
>>>=20
>>>> On 8 Jan 2021, at 13:04, Ted Lemon <mellon@fugue.com> wrote:
>>>>=20
>>>>> On Jan 7, 2021, at 9:02 PM, Mark Andrews <marka@isc.org> wrote:
>>>>> The example names I used where using the individuals suffix =
(id.au) but the idea is to leverage the existing global DNS to provide =
uniqueness.=20
>>>>=20
>>>> That works pretty well for ULAs, but not for LLAs. For LLAs you =
need to identify the link, and that=E2=80=99s just not a simple thing to =
do, as I explained earlier.
>>>=20
>>> Actually you haven=E2=80=99t explained.  You have stated.  You said =
it was hard.  Hard is not intractable.
>>>=20
>>> If you are willing for a link to have multiple names just have reach =
router generate its own random 160 bit base32 encoded label for each =
interface, append the well know suffix and advertise it.  You will get =
multiple SA records for the same interface if there are multiple routers =
but that should not be a issue.  With 160 random bits the need to do =
collision detection is really non-existent.  We=E2=80=99ve resolved this =
for NSEC3 and DNS changes 15 years ago. This will scale into millions of =
router interfaces.
>>>=20
>>> If you want to have a single link name then we need to define a =
protocol for the routers on the link to select one of the names.  This =
may end up being technology linked.  Router with smallest L-L address =
wins would be one solution to this.
>>>=20
>>> Yes, I really do expect every machine to update its own addresses in =
the DNS.  We do know how to do that securely with SIG(0).
>>>=20
>>>=20
>>> --=20
>>> Mark Andrews, ISC
>>> 1 Seymour St., Dundas Valley, NSW 2117, Australia
>>> PHONE: +61 2 9871 4742              INTERNET: marka@isc.org
>>>=20
>=20
> --=20
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742              INTERNET: marka@isc.org

--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org


From nobody Fri Jan  8 04:40:05 2021
Return-Path: <mellon@fugue.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 905E13A0C99 for <v6ops@ietfa.amsl.com>; Fri,  8 Jan 2021 04:40:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 y68qLcbgkE5l for <v6ops@ietfa.amsl.com>; Fri,  8 Jan 2021 04:40:01 -0800 (PST)
Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38D953A0C58 for <v6ops@ietf.org>; Fri,  8 Jan 2021 04:40:00 -0800 (PST)
Received: by mail-io1-xd2d.google.com with SMTP id q137so9562646iod.9 for <v6ops@ietf.org>; Fri, 08 Jan 2021 04:40:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=tWXBINd+2WSFdvxjA90D/T0UTJ8fb6qwJEt0W2fLYDw=; b=DKvHs19ln+Gq5xyx9R5hTQFRq1Hl5fxqqLhopNmIEdt/pVJJfMIAz3aX8lycS8S7+3 Vvc9GJBdB7CnaNWZx6VN/jjYwka8M9Nl4V//Kv14tg5QDevtGqRIHajo18ZhzBEyZcpk 35LUnCG9v1tzK7Lm/K1p/xJMU6hgr1XM9fschqcFC+ynwQP9ewfTA6d5h4tbN7s+BQpl Bfy5s0ALOZ3Brb6pMR4+8RxosOdAglwZWX+4JkNwlKFwSGy1C8lH+wmq1Qaz5BNGbj0+ Rqt/NX8ljxucN9M+1LoMm+jMDoq/6sIzngvg0nNFTmCHfW5yvt16O5VDSMLV49y0VUW+ u18w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=tWXBINd+2WSFdvxjA90D/T0UTJ8fb6qwJEt0W2fLYDw=; b=V614OrJ/rNOUBNl55Yi26sBNom+vb/WLZv5NdTeD2IFm80+u5fSjxpAuc1v4RhPAob h/fc+wZ+HavSObWNv1aC3oZLFWwR8M7N3MOtz8UrcxglTkMxw6/xlFmVAcsCHVNt4VEs ChuXzzwflDjELB5vSbZHFDh5lAqjSlMe4xFiROxh6f/X88E6v6qvaN8gt5/kQ+LBCJ7E l4t0DJYvNOdYPbZ5yv9cYN2yOZHINM98voh8h6JKERdYVK1s3w5NfmzFksi7DVaUsgjk CWq8xNc9RRpBNpKujqcDAJnJMfryhHqKURpi9IEpfgQRbgUXpPBUWgYAMvWOTBnlo3og zOBQ==
X-Gm-Message-State: AOAM532oAcp+zMgFjR6SxFlE14Vh1/NxPqlc0KxvcxlWcpPYwJLYJP3N hncKF5D7FOmA2adpGj3sAG8dVg==
X-Google-Smtp-Source: ABdhPJz1Ap8BbUJRE5Kja/50mZwzOGnf/aCaIPuRMcdpY4vqXqBL4KRfWAu8vfj5LzdYEe1jx4ntvw==
X-Received: by 2002:a02:354a:: with SMTP id y10mr3298201jae.126.1610109600139;  Fri, 08 Jan 2021 04:40:00 -0800 (PST)
Received: from mithrandir.lan (c-24-91-177-160.hsd1.nh.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id 9sm5248985iob.28.2021.01.08.04.39.59 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 08 Jan 2021 04:39:59 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <4E62C135-009D-409A-941C-E2F44C43759B@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F975737A-96B0-4BFE-87CC-9AFB3D766FAC"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.2\))
Date: Fri, 8 Jan 2021 07:39:57 -0500
In-Reply-To: <057ABF22-4C44-4EB7-8AF5-E9F173D67F2E@isc.org>
Cc: IPv6 Operations <v6ops@ietf.org>, IPv6 List <ipv6@ietf.org>
To: Mark Andrews <marka@isc.org>
References: <E3625337-3A59-4F0A-9EEE-EC8F6B39C965@isc.org> <537EBE5A-6554-4904-8701-03940C914FE3@fugue.com> <5A9F034B-64AB-4A96-BB8C-7A9286EF2654@isc.org> <057ABF22-4C44-4EB7-8AF5-E9F173D67F2E@isc.org>
X-Mailer: Apple Mail (2.3654.60.0.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/pzbsUL1WL6KEPGv3fPJsCVKeqWo>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jan 2021 12:40:04 -0000

--Apple-Mail=_F975737A-96B0-4BFE-87CC-9AFB3D766FAC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Jan 7, 2021, at 10:18 PM, Mark Andrews <marka@isc.org> wrote:
> When you change topology the node will see new RAs and getaddrinfo() =
will filter out all the old addresses.  The node has a set of link =
identifiers for links it is attached to.  Remember machines don=E2=80=99t =
care about these names.  They are just ways to filter out the currently =
useful addresses.  Each node
> will maintain its own mapping from applicable names to sin6_scope_id =
which will be filled in by getaddrinfo() generated by the RAs it sees.

I think link identifiers as you describe might be useful for some =
applications, but putting them in a database has a lot of issues. If =
every router on a link multicasts a link identifier to a link, then =
it=E2=80=99s not a link identifier=E2=80=94it=E2=80=99s a router =
interface identifier. That=E2=80=99s fine, but now my node has to track =
what router interface identifiers are present on the link, and publish =
its information on each identifier. Now suppose a router is unplugged =
from one link and plugged into another. It starts advertising its router =
interface identifier on the new link. Now you have stale information in =
the DNS, but the host doesn=E2=80=99t know, because there=E2=80=99s no =
positive indication that that router has gone.

You could track the router's reachability in the neighbor table, but now =
you have a different problem: it=E2=80=99s only going to be in the =
neighbor table if you=E2=80=99re using it, or if an RA has been received =
recently. So now you have a router link identifier that=E2=80=99s =
fluctuating. Do you update the database on every fluctuation?

Furthermore, DNS has TTLs. What=E2=80=99s the TTL on the data? How =
quickly does it fall out of your cache? Remember, you wanted to do this =
because Caching Is Good, so if you use a short TTL, your Good Caching =
isn=E2=80=99t happening.

What if you=E2=80=99re on an IPv4-only link? How do you publish your =
IPv6 LLA with a router link identifier? Your router isn=E2=80=99t giving =
you one. You can=E2=80=99t use the RFC1918 subnet prefix you got from =
DHCP as a link identifier, because they are non-unique.

This is what I mean when I say this isn=E2=80=99t practicable. Sure, =
it=E2=80=99s theoretically possible to imagine an environment where it =
would work. But it=E2=80=99s a tremendous amount of work that fails in =
ways that will create delay in many corner cases. And all it gets you is =
a hint from DNS as to which interface to use to communicate with a named =
host using its LLA. This isn=E2=80=99t much of a benefit.

If I just wanted hints, I could just do ND on every multicast-capable =
interface and get much more reliable hints: in most cases I=E2=80=99ll =
only get an answer on one interface, and then I can just send the packet =
on that interface and be much more assured of correctness than I could =
be based on stale data in the DNS.

Look at this from the other direction. A DNS full service resolver on =
your network can in many cases know where the query is coming from. BIND =
9 already does this=E2=80=94I can define a set of prefixes that are =
=E2=80=9Clocal=E2=80=9D and allow queries from those prefixes, but =
refuse queries from other prefixes.

This generalizes well: I can do the same thing for ULAs. I could very =
easily mark some set of ULA prefixes as =E2=80=9Creachable for hosts =
with addresses in prefixes on this list.=E2=80=9D And then when I get an =
AAAA record query that has both ULA and GUA addresses, I can return just =
the GUA address for queries from prefixes that aren=E2=80=99t on the =
list, and I can return the ULA only for queries from prefixes that are =
in the list. Or ULA+GUA.

This works well because minor changes in topology aren=E2=80=99t =
relevant. We know who owns the ULA prefix. We don=E2=80=99t need to know =
the details of where sub-prefixes of that ULA prefix are being =
advertised. We know what GUAs we have. If our upstream renumbers us, we =
need to update the prefix list, but this is a very lightweight change. =
And particularly if we _only_ return ULAs when the ULA is valid, this =
prefix change doesn=E2=80=99t affect any host that has the answer =
cached: our upstream GUA prefix change doesn=E2=80=99t affect our =
internal ULAs.

So from an operational perspective, this is a really useful =
feature=E2=80=94it=E2=80=99s one that I=E2=80=99d dearly love to see in =
BIND.


--Apple-Mail=_F975737A-96B0-4BFE-87CC-9AFB3D766FAC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">On =
Jan 7, 2021, at 10:18 PM, Mark Andrews &lt;<a =
href=3D"mailto:marka@isc.org" class=3D"">marka@isc.org</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><meta =
charset=3D"UTF-8" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); =
font-family: Menlo-Regular; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">When you change topology the node will see new RAs and =
getaddrinfo() will filter out all the old addresses. &nbsp;The node has =
a set of link identifiers for links it is attached to. &nbsp;Remember =
machines don=E2=80=99t care about these names. &nbsp;They are just ways =
to filter out the currently useful addresses. &nbsp;Each =
node</span></div></blockquote><blockquote type=3D"cite" class=3D""><div =
class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">will maintain =
its own mapping from applicable names to sin6_scope_id which will be =
filled in by getaddrinfo() generated by the RAs it sees.</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; =
font-size: 14px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""></div></blockquote></div><br class=3D""><div =
class=3D"">I think link identifiers as you describe might be useful for =
some applications, but putting them in a database has a lot of issues. =
If every router on a link multicasts a link identifier to a link, then =
it=E2=80=99s not a link identifier=E2=80=94it=E2=80=99s a router =
interface identifier. That=E2=80=99s fine, but now my node has to track =
what router interface identifiers are present on the link, and publish =
its information on each identifier. Now suppose a router is unplugged =
from one link and plugged into another. It starts advertising its router =
interface identifier on the new link. Now you have stale information in =
the DNS, but the host doesn=E2=80=99t know, because there=E2=80=99s no =
positive indication that that router has gone.</div><div class=3D""><br =
class=3D""></div><div class=3D"">You could track the router's =
reachability in the neighbor table, but now you have a different =
problem: it=E2=80=99s only going to be in the neighbor table if you=E2=80=99=
re using it, or if an RA has been received recently. So now you have a =
router link identifier that=E2=80=99s fluctuating. Do you update the =
database on every fluctuation?</div><div class=3D""><br =
class=3D""></div><div style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, =
0, 0);" class=3D"">Furthermore, DNS has TTLs. What=E2=80=99s the TTL on =
the data? How quickly does it fall out of your cache? Remember, you =
wanted to do this because Caching Is Good, so if you use a short TTL, =
your Good Caching isn=E2=80=99t happening.</div><div style=3D"caret-color:=
 rgb(0, 0, 0); color: rgb(0, 0, 0);" class=3D""><br class=3D""></div><div =
class=3D"">What if you=E2=80=99re on an IPv4-only link? How do you =
publish your IPv6 LLA with a router link identifier? Your router isn=E2=80=
=99t giving you one. You can=E2=80=99t use the RFC1918 subnet prefix you =
got from DHCP as a link identifier, because they are =
non-unique.</div><div class=3D""><br class=3D""></div><div class=3D"">This=
 is what I mean when I say this isn=E2=80=99t practicable. Sure, it=E2=80=99=
s theoretically possible to imagine an environment where it would work. =
But it=E2=80=99s a tremendous amount of work that fails in ways that =
will create delay in many corner cases. And all it gets you is a hint =
from DNS as to which interface to use to communicate with a named host =
using its LLA. This isn=E2=80=99t much of a benefit.</div><div =
class=3D""><br class=3D""></div><div class=3D"">If I just wanted hints, =
I could just do ND on every multicast-capable interface and get much =
more reliable hints: in most cases I=E2=80=99ll only get an answer on =
one interface, and then I can just send the packet on that interface and =
be much more assured of correctness than I could be based on stale data =
in the DNS.</div><div class=3D""><br class=3D""></div><div class=3D"">Look=
 at this from the other direction. A DNS full service resolver on your =
network can in many cases know where the query is coming from. BIND 9 =
already does this=E2=80=94I can define a set of prefixes that are =
=E2=80=9Clocal=E2=80=9D and allow queries from those prefixes, but =
refuse queries from other prefixes.</div><div class=3D""><br =
class=3D""></div><div class=3D"">This generalizes well: I can do the =
same thing for ULAs. I could very easily mark some set of ULA prefixes =
as =E2=80=9Creachable for hosts with addresses in prefixes on this =
list.=E2=80=9D And then when I get an AAAA record query that has both =
ULA and GUA addresses, I can return just the GUA address for queries =
from prefixes that aren=E2=80=99t on the list, and I can return the ULA =
only for queries from prefixes that are in the list. Or =
ULA+GUA.</div><div class=3D""><br class=3D""></div><div class=3D"">This =
works well because minor changes in topology aren=E2=80=99t relevant. We =
know who owns the ULA prefix. We don=E2=80=99t need to know the details =
of where sub-prefixes of that ULA prefix are being advertised. We know =
what GUAs we have. If our upstream renumbers us, we need to update the =
prefix list, but this is a very lightweight change. And particularly if =
we _only_ return ULAs when the ULA is valid, this prefix change =
doesn=E2=80=99t affect any host that has the answer cached: our upstream =
GUA prefix change doesn=E2=80=99t affect our internal ULAs.</div><div =
class=3D""><br class=3D""></div><div class=3D"">So from an operational =
perspective, this is a really useful feature=E2=80=94it=E2=80=99s one =
that I=E2=80=99d dearly love to see in BIND.</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_F975737A-96B0-4BFE-87CC-9AFB3D766FAC--


From nobody Sat Jan  9 10:15:55 2021
Return-Path: <fredbaker.ietf@gmail.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 572683A13F5 for <v6ops@ietfa.amsl.com>; Sat,  9 Jan 2021 10:15:53 -0800 (PST)
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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OnNvJnPHHUAh for <v6ops@ietfa.amsl.com>; Sat,  9 Jan 2021 10:15:52 -0800 (PST)
Received: from mail-pj1-x102f.google.com (mail-pj1-x102f.google.com [IPv6:2607:f8b0:4864:20::102f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C4D83A13F4 for <v6ops@ietf.org>; Sat,  9 Jan 2021 10:15:51 -0800 (PST)
Received: by mail-pj1-x102f.google.com with SMTP id iq13so5393192pjb.3 for <v6ops@ietf.org>; Sat, 09 Jan 2021 10:15:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:mime-version:subject:message-id:date:to; bh=XIQKiowrjERaXv6/e0bOHF/3DtriZd0ZUmCJEG4yoww=; b=C5UXyITqYMDvRCqAXmQcLf4ZlIz87dpu7AUPrYfe36UO8MxLEGps/5TLeGFHplfNzk 4C/7OyY7clZNlzWalxuTHz0GJRu7Yo86vAHxp0CFz4t/tO2cdP1fxeQ+c8s/zQxwhFGh ZiC+2Vp/kCSmmONkYMBTpG3CW1J59ygZMyCNlfX8LOeSxyiH8Wx01YRrlushs9tWsx5R ST7ZvOHkkDBlFRV2+piOai7o3h4wtIq/aYvVywTTVz+yDuLRxdpv3nxDp4CfhnL7J60t RrSEqgRbFdkIOsGJNbBDjo+n4IggzeIQSmJD8esGy0b2g84o5RwNJdRBhayi0NBpASQF 1HXg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:date:to; bh=XIQKiowrjERaXv6/e0bOHF/3DtriZd0ZUmCJEG4yoww=; b=GGUzWYzuH4XmdUMXruiTnT5Ddbb5NeTxqz2vqhFxM5Qhxe7rJFsGl7wtlqv8gtdnWo r5bJRSkn/SXhRKAlGCYdmG1ZMcolrOSJ7hwqGcybltWH2OYgNr+jmJ3DrnXvhjsNV7F6 mkV342FZ/930hJQpiq2htlXUcNR3XykUDodck9Dfdu0qK+WrQQqeQHXH69PzD3z7E92L tV7Dfsphh3yuhjmyElvl2rJ+cNdZzVojdyjf9JmRGCCT8WdBq/7X6BqXKwf1PidXt41E ZHU2rUxnnimrCEEl1bJhDFmgVT0wJUZWyGk1sO3xb2CDSfn7LmMcPDOYMu7QIcbiCEOC yzkg==
X-Gm-Message-State: AOAM532e3+kRQYjhBURONBxPjg3JRzT7JXLzxfLCsMjWFq+YbgzzNcbt dV+N3jfy8GccMzi8p1uEtnk/mujukFE=
X-Google-Smtp-Source: ABdhPJwBzPq2YCnyV9ANKnoZz1ojFMPTOTdXNpR273eN84+gcHp+KczyQH+3tD4Jo9kiDv1ZD5u1uQ==
X-Received: by 2002:a17:90a:c905:: with SMTP id v5mr9705022pjt.183.1610216151388;  Sat, 09 Jan 2021 10:15:51 -0800 (PST)
Received: from ?IPv6:2600:8802:5800:567::1023? ([2600:8802:5800:567::1023]) by smtp.gmail.com with ESMTPSA id b18sm13571208pfi.173.2021.01.09.10.15.50 for <v6ops@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 09 Jan 2021 10:15:50 -0800 (PST)
From: Fred Baker <fredbaker.ietf@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_E04E92D9-99B5-48B0-AF5D-09B5E5FBAFA8"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.2\))
Message-Id: <721A9345-0CDA-43A3-9E72-7CFB17797F41@gmail.com>
Date: Sat, 9 Jan 2021 10:15:49 -0800
To: IPv6 Operations <v6ops@ietf.org>
X-Mailer: Apple Mail (2.3654.60.0.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/uro8r8_Pljo5T1l9femSKboq7mY>
Subject: [v6ops] IETF 110 agenda development
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jan 2021 18:15:53 -0000

--Apple-Mail=_E04E92D9-99B5-48B0-AF5D-09B5E5FBAFA8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

You can find the important dates for IETF 110 at =
https://datatracker.ietf.org/meeting/important-dates/. It will be held =
virtually, as the last several have. It was intended to be held in =
Prague (and I was looking forward to Prague), and so will be timed as if =
it were in that timezone.

I mention the dates page, as that page indicates that the draft cut-off =
is 2021-02-22. If you want to get a document in to discuss in March, it =
needs to be in by then, and enough earlier to allow some discussion on =
the list prior to Ron and I having to concoct and agenda.

--Apple-Mail=_E04E92D9-99B5-48B0-AF5D-09B5E5FBAFA8
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEctjlJjQmVrp9uMq7EhdRnd2GP+AFAl/58tUACgkQEhdRnd2G
P+CJwg//eEP4G1J+tTMdoub6VCjYiusf2rNJF1zsCBczeBq1C6m1ordDHieFr1RB
+CVIq7lWVWswNNpPqFddAiccOwHzHcL1C7mJf4JTrdWZbpCOSSrLHmNmfJYFyJUC
l8eh4uiwBSjh/J47aKY4ADKUjx1msy0fxA1arqAKsmCOFdvadXpP5VUyXYCsz3y6
6T8I6GL+Jxf0DPBmeFFvkDb09S/43V63RGlPyPUM1X/tF/2y4PH12mWiYlZUtlQp
g03pj4x+9ufZ407coNiCFL9TfyXhzvF/uE7Wf+naTd4gLiCMCO7RPA0bSLVqqc99
3N6q/dfU7hd/kiQn/nPFtEyjXvRjCH3ibaAJlNAcehiUVVrw6XNCvFwskL6S0pf2
IyPXAZvflsq2tIaeMNmwULyaZ/dLRz2fhrA5GyRf8Y2TFpAPVK0SFzn2rJd0Sh1m
S1YO6l9CIVbUA2zwBE7JweB/MDPFCKL24JEFwptnqeltuPFcjXexilXLUcZUPsCZ
6840Z1Nq0OmOuOSnMNc/ElNSBULUbsrD2JlvQK+e+F5HTi6TE4A8QaazkqaxkPL6
MuKA7+N5ao+wTjdRz4LSwJoc8jAmL0fH6KjWZrN8vynKAW2rqKBmYFydxHpjhFMs
J/1fRimpIE6nO+Ndmf/IreeVquhy7Z3YRC6FM+GRciiMOBBTP5M=
=3Oeg
-----END PGP SIGNATURE-----

--Apple-Mail=_E04E92D9-99B5-48B0-AF5D-09B5E5FBAFA8--


From nobody Thu Jan 21 21:05:22 2021
Return-Path: <hayabusagsm@gmail.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 8D9073A10AB for <v6ops@ietfa.amsl.com>; Thu, 21 Jan 2021 21:05:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.086
X-Spam-Level: 
X-Spam-Status: No, score=-2.086 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_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id COqb46KAOHS0 for <v6ops@ietfa.amsl.com>; Thu, 21 Jan 2021 21:05:19 -0800 (PST)
Received: from mail-pj1-x102b.google.com (mail-pj1-x102b.google.com [IPv6:2607:f8b0:4864:20::102b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1BC6B3A10AA for <v6ops@ietf.org>; Thu, 21 Jan 2021 21:05:19 -0800 (PST)
Received: by mail-pj1-x102b.google.com with SMTP id kx7so3036124pjb.2 for <v6ops@ietf.org>; Thu, 21 Jan 2021 21:05:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HN75DA7H8oGS7gfhv3w7ILIwIedyDuz88aYqXy3FmgE=; b=vMF6S2ksgSW+pKPcDCR9eToq8MS62nV6i6XotplBFFzpb6vvs1IWwxyFPkU/pNheez SaRFmbPZwoLB/VG5k+gpzFrmwncJ54+XCVDxJC1sS8TOQAhvzlx/VTTlzoDVdZj155XD /VlWsPEesseO3Y3kuP3fmhQWYn/Q8xCleaB5kwmZ5QynqUVss6di9tgNWmwU9UFXWjI5 NqydmHQwj1fxpBOYJ5kn1rpWGittAAhJPl7oCEMFhr5SoRYHIs5i299eYCQFCnfvdv0a E3GyG2+jRBm9x1TQbwikvBTRw0Emg7oVEmuFMftSpfjV4FscqtlgTwCB77gWW0JKvpk3 LnGg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HN75DA7H8oGS7gfhv3w7ILIwIedyDuz88aYqXy3FmgE=; b=CRuYO/f7abbT6nspNom1vgr56ku2Q57rQteo+CswSQeJBSYkYSDJ4DUKQCiMG/+6Xi ubWkHaVWWZi/m9aQgVOlQS5gwxDF2ha9cGY0AkN8J9PiTV/rh1eG7BlvllBUoneAI/5b cbXKsDSeUp1VaYp2loTrU6ouO4JQe21q31hHWR/kOC4xoK4mX6pGtxb9GyU9orNJ4bKI jmQ60sym9HE9+I0dQaMDRZnETsxNB4SgprULfB9yMj9Mr/CQeC5sy5JhgIKXbTiReFXx sN8iQSu86R/W+2yCyImVCw4KtTZEIcP+YJIhXycU4oW8zIaW64foRIGi7ZO3RZkcMufK QH5w==
X-Gm-Message-State: AOAM5313BluioA7Lh1WcRXfAKucC4I4tpB7VveQKl2mWlrvmLS5A4wKe LERx7f6GLMJtPK0E5bWSkHMU9UQtILbEpog8Rug=
X-Google-Smtp-Source: ABdhPJzr9Sxu29FyhwGKURDkOC46pQOIAJhib09gIkeKjs4c5HHUv+ZM8pAR7jdCD/BYFhewXdlPgJVEdnszccsLDt4=
X-Received: by 2002:a17:90a:890a:: with SMTP id u10mr3337717pjn.215.1611291918602;  Thu, 21 Jan 2021 21:05:18 -0800 (PST)
MIME-Version: 1.0
References: <721A9345-0CDA-43A3-9E72-7CFB17797F41@gmail.com>
In-Reply-To: <721A9345-0CDA-43A3-9E72-7CFB17797F41@gmail.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Fri, 22 Jan 2021 00:05:08 -0500
Message-ID: <CABNhwV3wqYzG7=fxM-W8LgKYy+wsv=M5SR=3+iowRo8vyymJNw@mail.gmail.com>
To: Fred Baker <fredbaker.ietf@gmail.com>
Cc: IPv6 Operations <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007016d205b9762239"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/wpUHEOxdXadU2e8d5oNOugn4Zzc>
Subject: Re: [v6ops] IETF 110 agenda development
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 05:05:21 -0000

--0000000000007016d205b9762239
Content-Type: text/plain; charset="UTF-8"

Hi Fred

I would like to request a 10-15 minute time slot for
HBH draft below:

https://tools.ietf.org/html/draft-peng-v6ops-hbh-03

Thank you

Gyan


On Sat, Jan 9, 2021 at 1:16 PM Fred Baker <fredbaker.ietf@gmail.com> wrote:

> You can find the important dates for IETF 110 at
> https://datatracker.ietf.org/meeting/important-dates/. It will be held
> virtually, as the last several have. It was intended to be held in Prague
> (and I was looking forward to Prague), and so will be timed as if it were
> in that timezone.
>
> I mention the dates page, as that page indicates that the draft cut-off is
> 2021-02-22. If you want to get a document in to discuss in March, it needs
> to be in by then, and enough earlier to allow some discussion on the list
> prior to Ron and I having to concoct and agenda.
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *



*M 301 502-134713101 Columbia Pike *Silver Spring, MD

--0000000000007016d205b9762239
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Hi Fred</div><div dir=3D"auto"><br></div><div dir=3D"auto=
">I would like to request a 10-15 minute time slot for=C2=A0</div><div dir=
=3D"auto">HBH draft below:</div><div dir=3D"auto"><br></div><div dir=3D"aut=
o"><div><a href=3D"https://tools.ietf.org/html/draft-peng-v6ops-hbh-03">htt=
ps://tools.ietf.org/html/draft-peng-v6ops-hbh-03</a></div><br></div><div di=
r=3D"auto">Thank you=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"aut=
o">Gyan</div><div dir=3D"auto"><br></div><div dir=3D"auto"><br></div><div d=
ir=3D"auto"><div>On Sat, Jan 9, 2021 at 1:16 PM Fred Baker &lt;<a href=3D"m=
ailto:fredbaker.ietf@gmail.com">fredbaker.ietf@gmail.com</a>&gt; wrote:<br>=
</div></div><div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-styl=
e:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">You can find t=
he important dates for IETF 110 at <a href=3D"https://datatracker.ietf.org/=
meeting/important-dates/" rel=3D"noreferrer" target=3D"_blank">https://data=
tracker.ietf.org/meeting/important-dates/</a>. It will be held virtually, a=
s the last several have. It was intended to be held in Prague (and I was lo=
oking forward to Prague), and so will be timed as if it were in that timezo=
ne.<br>
<br>
I mention the dates page, as that page indicates that the draft cut-off is =
2021-02-22. If you want to get a document in to discuss in March, it needs =
to be in by then, and enough earlier to allow some discussion on the list p=
rior to Ron and I having to concoct and agenda.<br>
_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6ops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a><br>
</blockquote></div></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature" =
data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><div dir=3D"ltr"><div d=
ir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"l=
tr"><div><p style=3D"color:rgb(34,34,34)"><a href=3D"http://www.verizon.com=
/" style=3D"color:rgb(17,85,204);padding-bottom:1em;display:inline-block" t=
arget=3D"_blank"><img src=3D"http://ss7.vzw.com/is/image/VerizonWireless/vz=
-logo-email" width=3D"81" height=3D"18" style=3D"height:18px;width:81px"></=
a><br></p><p style=3D"font-size:1em;margin:0px;font-family:&quot;Verizon NH=
G DS&quot;,Arial,sans-serif;line-height:13px;color:black"><b>Gyan Mishra</b=
></p><p style=3D"color:rgb(34,34,34);margin:0px;line-height:13px"><font fac=
e=3D"georgia, serif" style=3D"color:black;font-size:1em"><i>Network Solutio=
ns A</i></font><font color=3D"#000000" face=3D"georgia, serif"><i>rchitect=
=C2=A0</i></font></p><p style=3D"font-size:1em;margin:0px;line-height:13px;=
color:black"><i><font face=3D"georgia, serif">M 301 502-1347<br>13101 Colum=
bia Pike=C2=A0<br></font></i>Silver Spring, MD</p></div><div><br></div></di=
v></div></div></div></div></div></div></div>

--0000000000007016d205b9762239--


From nobody Thu Jan 21 22:23:36 2021
Return-Path: <pengshuping@huawei.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 DE93E3A110A for <v6ops@ietfa.amsl.com>; Thu, 21 Jan 2021 22:23:34 -0800 (PST)
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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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 WaErI4FXwKjX for <v6ops@ietfa.amsl.com>; Thu, 21 Jan 2021 22:23:32 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62DB93A0E3B for <v6ops@ietf.org>; Thu, 21 Jan 2021 22:23:32 -0800 (PST)
Received: from fraeml741-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4DMTcP55Yzz67f71; Fri, 22 Jan 2021 14:19:17 +0800 (CST)
Received: from fraeml741-chm.china.huawei.com (10.206.15.222) by fraeml741-chm.china.huawei.com (10.206.15.222) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Fri, 22 Jan 2021 07:23:30 +0100
Received: from DGGEML401-HUB.china.huawei.com (10.3.17.32) by fraeml741-chm.china.huawei.com (10.206.15.222) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.2106.2 via Frontend Transport; Fri, 22 Jan 2021 07:23:30 +0100
Received: from DGGEML532-MBX.china.huawei.com ([169.254.8.117]) by DGGEML401-HUB.china.huawei.com ([fe80::89ed:853e:30a9:2a79%31]) with mapi id 14.03.0509.000; Fri, 22 Jan 2021 14:23:25 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: Gyan Mishra <hayabusagsm@gmail.com>, Fred Baker <fredbaker.ietf@gmail.com>
CC: IPv6 Operations <v6ops@ietf.org>
Thread-Topic: [v6ops] IETF 110 agenda development
Thread-Index: AQHW5rOTtYixpFfvk0CPfM66VamFYqoypMsAgACaKmA=
Date: Fri, 22 Jan 2021 06:23:25 +0000
Message-ID: <4278D47A901B3041A737953BAA078ADE198088F1@DGGEML532-MBX.china.huawei.com>
References: <721A9345-0CDA-43A3-9E72-7CFB17797F41@gmail.com> <CABNhwV3wqYzG7=fxM-W8LgKYy+wsv=M5SR=3+iowRo8vyymJNw@mail.gmail.com>
In-Reply-To: <CABNhwV3wqYzG7=fxM-W8LgKYy+wsv=M5SR=3+iowRo8vyymJNw@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.46.28.67]
Content-Type: multipart/related; boundary="_004_4278D47A901B3041A737953BAA078ADE198088F1DGGEML532MBXchi_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/PsnyYccXyP8nm1lCnhEgIPKe25A>
Subject: Re: [v6ops] IETF 110 agenda development
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 06:23:35 -0000

--_004_4278D47A901B3041A737953BAA078ADE198088F1DGGEML532MBXchi_
Content-Type: multipart/alternative;
 boundary="_000_4278D47A901B3041A737953BAA078ADE198088F1DGGEML532MBXchi_"

--_000_4278D47A901B3041A737953BAA078ADE198088F1DGGEML532MBXchi_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgRnJlZCwgYWxsLA0KDQpKdXN0IHRvIGFkZCBhIGJpdCBtb3JlIGluZm9ybWF0aW9uIGhlcmUu
DQoNClRoYW5rcyB0byBhbGwgdGhlIGZlZWRiYWNrIHdlIHJlY2VpdmVkIGFmdGVyIHRoZSBwcmVz
ZW50YXRpb24gaW4gSUVURjEwOSwgd2UgaGF2ZSB1cGRhdGVkIHRoZSBkcmFmdCB3aXRoIHRoZSBo
ZWxwIG9mIGFsbCB0aGUgY29hdXRob3JzIGFuZCBjb250cmlidXRvcnMuIFBsZWFzZSBmaW5kIHRo
ZSBkaWZmLCBodHRwczovL3Rvb2xzLmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1wZW5nLXY2
b3BzLWhiaC0wMy50eHQNCg0KSXQgd2lsbCBiZSBncmVhdCBpZiB3ZSBjb250aW51ZSB0byByZWNl
aXZpbmcgeW91ciBmZWVkYmFjayBhbmQgY29tbWVudHMgdG8gaW1wcm92ZSB0aGlzIHdvcmsgZnVy
dGhlci4NCg0KQmVzdCByZWdhcmRzLA0KU2h1cGluZw0KDQoNCg0KRnJvbTogdjZvcHMgW21haWx0
bzp2Nm9wcy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgR3lhbiBNaXNocmENClNlbnQ6
IEZyaWRheSwgSmFudWFyeSAyMiwgMjAyMSAxOjA1IFBNDQpUbzogRnJlZCBCYWtlciA8ZnJlZGJh
a2VyLmlldGZAZ21haWwuY29tPg0KQ2M6IElQdjYgT3BlcmF0aW9ucyA8djZvcHNAaWV0Zi5vcmc+
DQpTdWJqZWN0OiBSZTogW3Y2b3BzXSBJRVRGIDExMCBhZ2VuZGEgZGV2ZWxvcG1lbnQNCg0KSGkg
RnJlZA0KDQpJIHdvdWxkIGxpa2UgdG8gcmVxdWVzdCBhIDEwLTE1IG1pbnV0ZSB0aW1lIHNsb3Qg
Zm9yDQpIQkggZHJhZnQgYmVsb3c6DQoNCmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFm
dC1wZW5nLXY2b3BzLWhiaC0wMw0KDQpUaGFuayB5b3UNCg0KR3lhbg0KDQoNCk9uIFNhdCwgSmFu
IDksIDIwMjEgYXQgMToxNiBQTSBGcmVkIEJha2VyIDxmcmVkYmFrZXIuaWV0ZkBnbWFpbC5jb208
bWFpbHRvOmZyZWRiYWtlci5pZXRmQGdtYWlsLmNvbT4+IHdyb3RlOg0KWW91IGNhbiBmaW5kIHRo
ZSBpbXBvcnRhbnQgZGF0ZXMgZm9yIElFVEYgMTEwIGF0IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0
Zi5vcmcvbWVldGluZy9pbXBvcnRhbnQtZGF0ZXMvLiBJdCB3aWxsIGJlIGhlbGQgdmlydHVhbGx5
LCBhcyB0aGUgbGFzdCBzZXZlcmFsIGhhdmUuIEl0IHdhcyBpbnRlbmRlZCB0byBiZSBoZWxkIGlu
IFByYWd1ZSAoYW5kIEkgd2FzIGxvb2tpbmcgZm9yd2FyZCB0byBQcmFndWUpLCBhbmQgc28gd2ls
bCBiZSB0aW1lZCBhcyBpZiBpdCB3ZXJlIGluIHRoYXQgdGltZXpvbmUuDQoNCkkgbWVudGlvbiB0
aGUgZGF0ZXMgcGFnZSwgYXMgdGhhdCBwYWdlIGluZGljYXRlcyB0aGF0IHRoZSBkcmFmdCBjdXQt
b2ZmIGlzIDIwMjEtMDItMjIuIElmIHlvdSB3YW50IHRvIGdldCBhIGRvY3VtZW50IGluIHRvIGRp
c2N1c3MgaW4gTWFyY2gsIGl0IG5lZWRzIHRvIGJlIGluIGJ5IHRoZW4sIGFuZCBlbm91Z2ggZWFy
bGllciB0byBhbGxvdyBzb21lIGRpc2N1c3Npb24gb24gdGhlIGxpc3QgcHJpb3IgdG8gUm9uIGFu
ZCBJIGhhdmluZyB0byBjb25jb2N0IGFuZCBhZ2VuZGEuDQpfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXw0KdjZvcHMgbWFpbGluZyBsaXN0DQp2Nm9wc0BpZXRm
Lm9yZzxtYWlsdG86djZvcHNAaWV0Zi5vcmc+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL3Y2b3BzDQotLQ0KDQpb5Zu+5YOP5bey6KKr5Y+R5Lu25Lq65Yig6Zmk44CCXTxo
dHRwOi8vd3d3LnZlcml6b24uY29tLz4NCg0KR3lhbiBNaXNocmENCg0KTmV0d29yayBTb2x1dGlv
bnMgQXJjaGl0ZWN0DQoNCk0gMzAxIDUwMi0xMzQ3DQoxMzEwMSBDb2x1bWJpYSBQaWtlDQpTaWx2
ZXIgU3ByaW5nLCBNRA0KDQo=

--_000_4278D47A901B3041A737953BAA078ADE198088F1DGGEML532MBXchi_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPCEtLVtp
ZiAhbXNvXT48c3R5bGU+dlw6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kb1w6KiB7
YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kd1w6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0
I1ZNTCk7fQ0KLnNoYXBlIHtiZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9DQo8L3N0eWxlPjwh
W2VuZGlmXS0tPjxzdHlsZT48IS0tDQovKiBGb250IERlZmluaXRpb25zICovDQpAZm9udC1mYWNl
DQoJe2ZvbnQtZmFtaWx5OuWui+S9kzsNCglwYW5vc2UtMToyIDEgNiAwIDMgMSAxIDEgMSAxO30N
CkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0
IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJ
cGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWls
eTpHZW9yZ2lhOw0KCXBhbm9zZS0xOjIgNCA1IDIgNSA0IDUgMiAzIDM7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseToiXEDlrovkvZMiOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7
fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRp
di5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9u
dC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseTrlrovkvZM7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5
cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRl
Y29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dl
ZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3Jh
dGlvbjp1bmRlcmxpbmU7fQ0KcA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87DQoJbWFyZ2luLXJpZ2h0OjBjbTsNCgltc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0bzsNCgltYXJnaW4tbGVmdDowY207DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZh
bWlseTrlrovkvZM7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29u
YWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6IzFG
NDk3RDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglm
b250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7
c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA5MC4wcHQgNzIuMHB0IDkwLjBw
dDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+
PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBz
cGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4
bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIg
ZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4N
Cjxib2R5IGxhbmc9IlpILUNOIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xh
c3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPkhpIEZyZWQsIGFsbCwNCjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Zm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2Vy
aWY7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj5K
dXN0IHRvIGFkZCBhIGJpdCBtb3JlIGluZm9ybWF0aW9uIGhlcmUuDQo8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZv
bnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlm
O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+VGhh
bmtzIHRvIGFsbCB0aGUgZmVlZGJhY2sgd2UgcmVjZWl2ZWQgYWZ0ZXIgdGhlIHByZXNlbnRhdGlv
biBpbiBJRVRGMTA5LCB3ZSBoYXZlIHVwZGF0ZWQgdGhlIGRyYWZ0IHdpdGggdGhlIGhlbHAgb2Yg
YWxsIHRoZSBjb2F1dGhvcnMgYW5kIGNvbnRyaWJ1dG9ycy4NCiBQbGVhc2UgZmluZCB0aGUgZGlm
ZiwgPGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9yZmNkaWZmP3VybDI9ZHJhZnQtcGVu
Zy12Nm9wcy1oYmgtMDMudHh0Ij4NCmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvcmZjZGlmZj91cmwy
PWRyYWZ0LXBlbmctdjZvcHMtaGJoLTAzLnR4dDwvYT48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZTox
MC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMx
RjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+SXQgd2lsbCBiZSBn
cmVhdCBpZiB3ZSBjb250aW51ZSB0byByZWNlaXZpbmcgeW91ciBmZWVkYmFjayBhbmQgY29tbWVu
dHMgdG8gaW1wcm92ZSB0aGlzIHdvcmsgZnVydGhlci4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXpl
OjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6
IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj5CZXN0IHJlZ2Fy
ZHMsDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPlNodXBpbmcNCjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHls
ZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMt
c2VyaWY7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdE
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJs
dWUgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdCI+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0i
Ym9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6My4wcHQg
MGNtIDBjbSAwY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gbGFuZz0iRU4tVVMi
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
c2Fucy1zZXJpZiI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYi
PiB2Nm9wcyBbbWFpbHRvOnY2b3BzLWJvdW5jZXNAaWV0Zi5vcmddDQo8Yj5PbiBCZWhhbGYgT2Yg
PC9iPkd5YW4gTWlzaHJhPGJyPg0KPGI+U2VudDo8L2I+IEZyaWRheSwgSmFudWFyeSAyMiwgMjAy
MSAxOjA1IFBNPGJyPg0KPGI+VG86PC9iPiBGcmVkIEJha2VyICZsdDtmcmVkYmFrZXIuaWV0ZkBn
bWFpbC5jb20mZ3Q7PGJyPg0KPGI+Q2M6PC9iPiBJUHY2IE9wZXJhdGlvbnMgJmx0O3Y2b3BzQGll
dGYub3JnJmd0Ozxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogW3Y2b3BzXSBJRVRGIDExMCBhZ2Vu
ZGEgZGV2ZWxvcG1lbnQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+
SGkgRnJlZDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+
SSB3b3VsZCBsaWtlIHRvIHJlcXVlc3QgYSAxMC0xNSBtaW51dGUgdGltZSBzbG90IGZvciZuYnNw
OzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5IQkggZHJhZnQgYmVsb3c6PG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PGEgaHJlZj0iaHR0cHM6Ly90
b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LXBlbmctdjZvcHMtaGJoLTAzIj5odHRwczovL3Rvb2xz
LmlldGYub3JnL2h0bWwvZHJhZnQtcGVuZy12Nm9wcy1oYmgtMDM8L2E+PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPlRoYW5rIHlvdSZuYnNwOzxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9
IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+R3lhbjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxh
bmc9IkVOLVVTIj5PbiBTYXQsIEphbiA5LCAyMDIxIGF0IDE6MTYgUE0gRnJlZCBCYWtlciAmbHQ7
PGEgaHJlZj0ibWFpbHRvOmZyZWRiYWtlci5pZXRmQGdtYWlsLmNvbSI+ZnJlZGJha2VyLmlldGZA
Z21haWwuY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRl
ci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJn
aW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIGxhbmc9IkVOLVVTIj5Zb3UgY2FuIGZpbmQgdGhlIGltcG9ydGFudCBkYXRlcyBmb3IgSUVU
RiAxMTAgYXQNCjxhIGhyZWY9Imh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvbWVldGluZy9p
bXBvcnRhbnQtZGF0ZXMvIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRm
Lm9yZy9tZWV0aW5nL2ltcG9ydGFudC1kYXRlcy88L2E+LiBJdCB3aWxsIGJlIGhlbGQgdmlydHVh
bGx5LCBhcyB0aGUgbGFzdCBzZXZlcmFsIGhhdmUuIEl0IHdhcyBpbnRlbmRlZCB0byBiZSBoZWxk
IGluIFByYWd1ZSAoYW5kIEkgd2FzIGxvb2tpbmcgZm9yd2FyZCB0bw0KIFByYWd1ZSksIGFuZCBz
byB3aWxsIGJlIHRpbWVkIGFzIGlmIGl0IHdlcmUgaW4gdGhhdCB0aW1lem9uZS48YnI+DQo8YnI+
DQpJIG1lbnRpb24gdGhlIGRhdGVzIHBhZ2UsIGFzIHRoYXQgcGFnZSBpbmRpY2F0ZXMgdGhhdCB0
aGUgZHJhZnQgY3V0LW9mZiBpcyAyMDIxLTAyLTIyLiBJZiB5b3Ugd2FudCB0byBnZXQgYSBkb2N1
bWVudCBpbiB0byBkaXNjdXNzIGluIE1hcmNoLCBpdCBuZWVkcyB0byBiZSBpbiBieSB0aGVuLCBh
bmQgZW5vdWdoIGVhcmxpZXIgdG8gYWxsb3cgc29tZSBkaXNjdXNzaW9uIG9uIHRoZSBsaXN0IHBy
aW9yIHRvIFJvbiBhbmQgSSBoYXZpbmcgdG8gY29uY29jdA0KIGFuZCBhZ2VuZGEuPGJyPg0KX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQp2Nm9wcyBt
YWlsaW5nIGxpc3Q8YnI+DQo8YSBocmVmPSJtYWlsdG86djZvcHNAaWV0Zi5vcmciIHRhcmdldD0i
X2JsYW5rIj52Nm9wc0BpZXRmLm9yZzwvYT48YnI+DQo8YSBocmVmPSJodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Y2b3BzIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby92Nm9wczwvYT48bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gbGFuZz0iRU4tVVMiPi0tIDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8ZGl2Pg0K
PGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iY29sb3I6IzIyMjIyMiI+PGEgaHJlZj0iaHR0cDovL3d3dy52
ZXJpem9uLmNvbS8iIHRhcmdldD0iX2JsYW5rIj48c3BhbiBzdHlsZT0iY29sb3I6IzExNTVDQzti
b3JkZXI6c29saWQgd2luZG93dGV4dCAxLjBwdDtwYWRkaW5nOjBjbTt0ZXh0LWRlY29yYXRpb246
bm9uZSI+PGltZyBib3JkZXI9IjAiIHdpZHRoPSI4MSIgaGVpZ2h0PSIxOCIgaWQ9Il94MDAwMF9p
MTAyNSIgc3JjPSJjaWQ6aW1hZ2UwMDEuanBnQDAxRDZGMEM5LkRFQkFERkQwIiBhbHQ9IuWbvuWD
j+W3suiiq+WPkeS7tuS6uuWIoOmZpOOAgiI+PC9zcGFuPjwvYT48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBzdHlsZT0ibWFyZ2luOjBjbTttYXJnaW4tYm90dG9tOi4wMDAxcHQ7bXNvLWxpbmUt
aGVpZ2h0LWFsdDo5Ljc1cHQiPjxiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1p
bHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+R3lhbiBNaXNocmE8
L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJp
YWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+PG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgc3R5bGU9Im1hcmdpbjowY207bWFyZ2luLWJvdHRvbTouMDAwMXB0O21zby1saW5lLWhlaWdo
dC1hbHQ6OS43NXB0Ij48aT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZx
dW90O0dlb3JnaWEmcXVvdDssc2VyaWY7Y29sb3I6YmxhY2siPk5ldHdvcmsgU29sdXRpb25zIEFy
Y2hpdGVjdCZuYnNwOzwvc3Bhbj48L2k+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjoj
MjIyMjIyIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBzdHlsZT0ibWFyZ2luOjBjbTttYXJn
aW4tYm90dG9tOi4wMDAxcHQ7bXNvLWxpbmUtaGVpZ2h0LWFsdDo5Ljc1cHQiPjxpPjxzcGFuIGxh
bmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7R2VvcmdpYSZxdW90OyxzZXJpZjtj
b2xvcjpibGFjayI+TSAzMDEgNTAyLTEzNDc8YnI+DQoxMzEwMSBDb2x1bWJpYSBQaWtlJm5ic3A7
PGJyPg0KPC9zcGFuPjwvaT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOmJsYWNrIj5T
aWx2ZXIgU3ByaW5nLCBNRDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1s
Pg0K

--_000_4278D47A901B3041A737953BAA078ADE198088F1DGGEML532MBXchi_--

--_004_4278D47A901B3041A737953BAA078ADE198088F1DGGEML532MBXchi_
Content-Type: image/jpeg; name="image001.jpg"
Content-Description: image001.jpg
Content-Disposition: inline; filename="image001.jpg"; size=361;
 creation-date="Fri, 22 Jan 2021 06:23:25 GMT";
 modification-date="Fri, 22 Jan 2021 06:23:25 GMT"
Content-ID: <image001.jpg@01D6F0C9.DEBADFD0>
Content-Transfer-Encoding: base64

/9j/4AAQSkZJRgABAQEAeAB4AAD/2wBDAAoHBwkHBgoJCAkLCwoMDxkQDw4ODx4WFxIZJCAmJSMg
IyIoLTkwKCo2KyIjMkQyNjs9QEBAJjBGS0U+Sjk/QD3/wAALCAAXAGUBAREA/8QAHwAAAQUBAQEB
AQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1Fh
ByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZ
WmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXG
x8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/9oACAEBAAA/APZqKKKKKKKKKKKKKKKK
KKKKKKKKKKKKKKKKKKKKKK//2Q==

--_004_4278D47A901B3041A737953BAA078ADE198088F1DGGEML532MBXchi_--


From nobody Wed Jan 27 08:05:25 2021
Return-Path: <fredbaker.ietf@gmail.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 D11D53A0A8E for <v6ops@ietfa.amsl.com>; Wed, 27 Jan 2021 08:05:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2cB3QNO-MhpU for <v6ops@ietfa.amsl.com>; Wed, 27 Jan 2021 08:05:22 -0800 (PST)
Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27E393A0A65 for <v6ops@ietf.org>; Wed, 27 Jan 2021 08:05:22 -0800 (PST)
Received: by mail-pj1-x1036.google.com with SMTP id jx18so1629126pjb.5 for <v6ops@ietf.org>; Wed, 27 Jan 2021 08:05:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:mime-version:subject:message-id:date:to; bh=ACPPzUb6kItgpK+GJ7o5zrDOmXr6hlrefN5GrkRsXSo=; b=hVUFycrojY5ChwnfnQBAnAommMrnAZHH78/AYqTUnvVe+3rFKVyZXBmOj6gxgwyZOd y8yEq9+jh66ixFrCLFkPjhZz5BJvPUT87SP4j+jqTebThVzNeRwlIVpIW1vwSSa6qlLa Lp6IGDgOPnep8PXYQvS2MNKRccwoQJ2x/k+qzxM3cdjcXtokzTkqUHh++3VSvsVEV/ke bIQGlHL/Kd8tFnZs8qrixkAr3v3fzS9s31ORBCybHSBdGeUBTNzb4PU/+wwERC2vxg5a 7BWvXfkI9FjuPugsXJuEurPNg/BRWvA7quawd2DGKZui649DRWtJrSY4MrK5Arx+wroK 2PAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:date:to; bh=ACPPzUb6kItgpK+GJ7o5zrDOmXr6hlrefN5GrkRsXSo=; b=owVsm+JuizRhHbQPwHKer99BnzSOKr2fzjxsbJkPICLt4T1JhnXWEODpb0oOvNDLI6 3818FLMGYxBD436GP9kmHQ8JSmlOUPjS3UWFQGqPP9qjA0YTyXWSi/xCuyno/NL4KAcQ dSx6JiRfL3tOE4iuZoTVnl4u5dfiIIua5xWkG2AfIKYnugKsOw+5KRW67F0BQj6jXFi3 gaQoZhl1NEaEhBDVCMvFDmZS7W1K3Jj5COL6A/8HqUc/9GH4QjtZnTkw1rM4/qTwsQWo Y6sgGqZIRE6w0KR0kwoqPs7vNzbea1sruGFiOAbYe53SdudovptZavFxF5AzG+CtG//8 yZnA==
X-Gm-Message-State: AOAM533dCQzaXadwAnWrKoxhv00ri3uxHcjpCIVJw8ncjE8e188SdS1M or6Y72zeT6X+2WF2NP3gaDbQGjx7ssM=
X-Google-Smtp-Source: ABdhPJwzUFi3ZHWIm1r1piBsli7fgEriY41hGav/j9clDClH3P0vpAWknOUN+sajg4TEZEY5PU7hVQ==
X-Received: by 2002:a17:90a:f2c6:: with SMTP id gt6mr6393471pjb.35.1611763521517;  Wed, 27 Jan 2021 08:05:21 -0800 (PST)
Received: from ?IPv6:2601:648:8200:dd20:f521:6171:1eb5:db72? ([2601:648:8200:dd20:f521:6171:1eb5:db72]) by smtp.gmail.com with ESMTPSA id 184sm2797198pgi.92.2021.01.27.08.05.19 for <v6ops@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 27 Jan 2021 08:05:20 -0800 (PST)
From: Fred Baker <fredbaker.ietf@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_C783AB2C-187D-4422-ACD3-4836644EA7C2"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Message-Id: <D9F54CBC-1429-4AC0-8F47-435F09FC27C5@gmail.com>
Date: Wed, 27 Jan 2021 08:05:18 -0800
To: IPv6 Operations <v6ops@ietf.org>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/GMFu9CC0H-WKM68JvZnbO-SvUCs>
Subject: [v6ops] draft-ietf-v6ops-cpe-slaac-renum to BCP?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jan 2021 16:05:24 -0000

--Apple-Mail=_C783AB2C-187D-4422-ACD3-4836644EA7C2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

We discussed draft-ietf-v6ops-cpe-slaac-renum and sent it to the IESG, =
whose primary comment was that it seemed like it should be BCP. They =
asked for an additional WGLC, so let's take a week (e.g., closes Feb 3) =
and ask whether the working group has any issues with that. The posted =
document targets BCP, so I expect that it should be such.

--Apple-Mail=_C783AB2C-187D-4422-ACD3-4836644EA7C2
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEctjlJjQmVrp9uMq7EhdRnd2GP+AFAmARjz4ACgkQEhdRnd2G
P+Dh/w/+OAUn7rpqz9EHwIGNyuDJ1oXmbSK336OAIBTdMbGYAcmJl0dh55FqVANs
Z7AH60EdGb3QES/a5Gqx1y5bjbYFpKifxzI+BjUygWJfGyc55oti30iFU2Rj6iKQ
cpbcw2rSIZjm6tE5+7XtUc7XNzi3VF0kaVCgKetfOpyLf0J5NYgl7mfZK/tCzXMP
GYARUzrhSE3Ds8VeTv1yqWxIoqzUbial8bLrTRGIzIL9o2QaHRJDPv/QqtRgAL81
JyvmsYUfIXPWoFJpvC4Mx4jd7KGmNZIKYdHUaPYQe/fwpmHqF0dGgyeO1KOrrsP2
BAU1qDeplRKnx+hBegFDqj3mlyHI1GMrc40z6cPtEIxdNe+FjcT78wgVyqV4iSqZ
MAQoWDgSgTJPXfBk61OTvvTZeFWB/t6ipTYQIvHtYlbyPBKIpZWi8v+VyRGtUbcC
oXy8NFXEw97Rd/vGyUxIs3coERbUxAEiU85lIp1GAkrtm0Qd7C+mvgfz+6m6kGH0
Vuwc7VQTOjPWcURzoXH7ZR1eGZy8ofdemBrY4VHSckCY/EBJOWI497OKqW5i4Pvq
aCkLx+6Yn2s1cVLV+4u04sXXb9AI4EuG9cwD7XhlsMdKaXcexfCx8inHycmS+qUG
D1UPi1wCAd+4r5o//szNlYYSvDYr9PG+JiOvEOdfIM/4F10+1xc=
=a5o9
-----END PGP SIGNATURE-----

--Apple-Mail=_C783AB2C-187D-4422-ACD3-4836644EA7C2--


From nobody Wed Jan 27 08:52:28 2021
Return-Path: <warren@kumari.net>
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 294FF3A0C3B for <v6ops@ietfa.amsl.com>; Wed, 27 Jan 2021 08:52:27 -0800 (PST)
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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.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 ksWZo6t1pFOt for <v6ops@ietfa.amsl.com>; Wed, 27 Jan 2021 08:52:25 -0800 (PST)
Received: from mail-lj1-x22e.google.com (mail-lj1-x22e.google.com [IPv6:2a00:1450:4864:20::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 480D53A0C3A for <v6ops@ietf.org>; Wed, 27 Jan 2021 08:52:24 -0800 (PST)
Received: by mail-lj1-x22e.google.com with SMTP id t8so2873212ljk.10 for <v6ops@ietf.org>; Wed, 27 Jan 2021 08:52:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=bOpGhI75b2AxDNWPB3oxAw3tiWwk16ketHBaC3WAoyQ=; b=DnGw2rLv1yXeZMThL3TGFXliJ8HxUjYsuAQZkRxK8zOZ8BlZ1wIn5sa7Mid804QT0Q lC9ZA/Yjhah4sp9Ko+GQhHulvtSZMQAzHEaWSbmEE1sVpwvUvYNxIYMNQhfZ046GmS42 5zeT1QtKqPntNTLm1EX7ewE3k1KHJI7PXELST9R1A4S+RNKlI8BSM8ryzFkGGUqQPORm ncgFuR5AoHTyjrT0XjQ1AxAVcT4BU/WQPirQKJHN2WsPCHcb+R2hCi3r99X3Xbm6KZok wSLy1DPL1VUFQWLdFs/XrC+QHsEPpl6BJGUlOrUCwK8FLdPb4fdAhVNLpv2QnWT/y1ct Mz1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=bOpGhI75b2AxDNWPB3oxAw3tiWwk16ketHBaC3WAoyQ=; b=FSlSKAFp+6M3da077nqqgUeEo5AkVgoR9KScNECZZs2VJ58mRgVbqKMHhnjZDreGTI 9tk2DJVzEhY3OrEwy4lSjjxwSSaADjBJufj4MB/1rUUZVEDWdnugh+5V3DJJhr+LzIQf qncr0Ir7X1RG1IWns/U7qNGtb5Jj/7olG1V2SpeMWxY7N1Q4bw0YsxWfTKriBOpuOq2A u5ecu58PWYDxYc5TzYvrNMyGnATt74uDSD42czWeW/esdeAYA/l6lul67d9OEQ8pr/hc DihoVTBRy5pK/w7LboUexYqa/LBjpKGSlCCHlAMm8gqThiGUwgex4t5fU5YDtRJH1mZQ A51w==
X-Gm-Message-State: AOAM533y3gKHJ0WEDfiiB785fGz/Iu+O0JkzArLYnzrST957yC2JWVH8 Jk7IUumhL6B++fVXgMXkxANerZCMUEpM2R5fIRHprZHTewbsyI+V
X-Google-Smtp-Source: ABdhPJzH4sapfO3Gbyn8kIimBiY5KrE8jo8OGgzsemMPimXsrvs6YwALa5EWvxpczqjNX9hD+gS2Jg+9zrZ/2MSWm3k=
X-Received: by 2002:a05:651c:1b8:: with SMTP id c24mr3684421ljn.316.1611766342615;  Wed, 27 Jan 2021 08:52:22 -0800 (PST)
MIME-Version: 1.0
References: <D9F54CBC-1429-4AC0-8F47-435F09FC27C5@gmail.com>
In-Reply-To: <D9F54CBC-1429-4AC0-8F47-435F09FC27C5@gmail.com>
From: Warren Kumari <warren@kumari.net>
Date: Wed, 27 Jan 2021 11:51:43 -0500
Message-ID: <CAHw9_iK50KfC2_LwaPQyC+m5pyna8=rZ5CXxwevwBd-C3vG7gA@mail.gmail.com>
To: Fred Baker <fredbaker.ietf@gmail.com>
Cc: IPv6 Operations <v6ops@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/cmOAsQ7_Ubk2ldNf5DvSWdHbbdo>
Subject: Re: [v6ops] draft-ietf-v6ops-cpe-slaac-renum to BCP?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jan 2021 16:52:27 -0000

On Wed, Jan 27, 2021 at 11:05 AM Fred Baker <fredbaker.ietf@gmail.com> wrot=
e:
>
> We discussed draft-ietf-v6ops-cpe-slaac-renum and sent it to the IESG, wh=
ose primary comment was that it seemed like it should be BCP. They asked fo=
r an additional WGLC,

That has already occurred -- see the thread at:
https://mailarchive.ietf.org/arch/msg/v6ops/_seai5Rf5bU6AnPwc3bHqbAI_7M/

It was started on Thu, 17 December 2020, and Ron called it on 29 December 2=
020

The document had a second IETF LC:
https://mailarchive.ietf.org/arch/msg/ietf-announce/8ONmyVttm-4s5ebl6jJsME0=
Lots/

and I'm waiting on the authors to address the comments received during
the IETF LC and (prior) IESG eval.

W



>  so let's take a week (e.g., closes Feb 3) and ask whether the working gr=
oup has any issues with that. The posted document targets BCP, so I expect =
that it should be such.
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops



--=20
The computing scientist=E2=80=99s main challenge is not to get confused by =
the
complexities of his own making.
  -- E. W. Dijkstra


From nobody Wed Jan 27 11:17:37 2021
Return-Path: <fernando@gont.com.ar>
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 F2C8B3A0DE6 for <v6ops@ietfa.amsl.com>; Wed, 27 Jan 2021 11:17:35 -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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, 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 d2nWDzuZnd5i for <v6ops@ietfa.amsl.com>; Wed, 27 Jan 2021 11:17:31 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D322A3A0DDE for <v6ops@ietf.org>; Wed, 27 Jan 2021 11:17:24 -0800 (PST)
Received: from [IPv6:2800:810:464:2b9:69a9:e23f:a699:f848] (unknown [IPv6:2800:810:464:2b9:69a9:e23f:a699:f848]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id B85F528027F; Wed, 27 Jan 2021 19:17:20 +0000 (UTC)
To: Warren Kumari <warren@kumari.net>, Fred Baker <fredbaker.ietf@gmail.com>
Cc: IPv6 Operations <v6ops@ietf.org>
References: <D9F54CBC-1429-4AC0-8F47-435F09FC27C5@gmail.com> <CAHw9_iK50KfC2_LwaPQyC+m5pyna8=rZ5CXxwevwBd-C3vG7gA@mail.gmail.com>
From: Fernando Gont <fernando@gont.com.ar>
Message-ID: <a05d1707-c57d-5069-d76f-6f3d691e3f92@gont.com.ar>
Date: Wed, 27 Jan 2021 16:17:11 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CAHw9_iK50KfC2_LwaPQyC+m5pyna8=rZ5CXxwevwBd-C3vG7gA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/3XxAazAPCE1DM6fxsSbIr2EnSYQ>
Subject: Re: [v6ops] draft-ietf-v6ops-cpe-slaac-renum to BCP?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jan 2021 19:17:36 -0000

Hi, Warren,

On 27/1/21 13:51, Warren Kumari wrote:
> 
> The document had a second IETF LC:
> https://mailarchive.ietf.org/arch/msg/ietf-announce/8ONmyVttm-4s5ebl6jJsME0Lots/
> 
> and I'm waiting on the authors to address the comments received during
> the IETF LC and (prior) IESG eval.

I thought these had been addressed already.

I will review each of the IESG reviews and see if we have missed any 
comments.

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From nobody Wed Jan 27 13:22:08 2021
Return-Path: <fgont@si6networks.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 E4DB03A0AFB; Wed, 27 Jan 2021 13:22:01 -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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, 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 jo9UD-5q3hfd; Wed, 27 Jan 2021 13:21:59 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 628713A0AFD; Wed, 27 Jan 2021 13:21:54 -0800 (PST)
Received: from [IPv6:2800:810:464:2b9:69a9:e23f:a699:f848] (unknown [IPv6:2800:810:464:2b9:69a9:e23f:a699:f848]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id B3C48280482; Wed, 27 Jan 2021 21:21:50 +0000 (UTC)
From: Fernando Gont <fgont@si6networks.com>
To: Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>
Cc: draft-ietf-v6ops-cpe-slaac-renum@ietf.org, v6ops-chairs@ietf.org, v6ops@ietf.org, Owen DeLong <owen@delong.com>
References: <160325603610.17357.6914550111489766157@ietfa.amsl.com>
Message-ID: <cf025acf-5192-d9a3-a727-8716d9d7b232@si6networks.com>
Date: Wed, 27 Jan 2021 18:21:30 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <160325603610.17357.6914550111489766157@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/PkHLMxBkEQP-PM9t06uCgcpTDOM>
Subject: Re: [v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-cpe-slaac-renum-05: (with COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jan 2021 21:22:02 -0000

Hi, Ben,

Just me going through IESG reviews to find if there's anything I had 
missed. Please see in-line....

On 21/10/20 01:53, Benjamin Kaduk via Datatracker wrote:
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> I am not sure that we should avoid having the conversation about
> intended status; consider, for example, "CE Routers SHOULD override the
> default [...] values from [RFC4861]" (RFC 4861 is a Draft Standard).  (The
> question was raised in the genart review thread by virtue of skew between
> the datatracker state and the document header, but it looks like the WG chair
> changed the status in the datatracker and there was no further discussion of
> the topic on the list.)
> 
> The diff between Abstract and Introduction is interesting: there is a
> parenthetical "(such as when a Customer Edge Router crashes and reboots
> without knowledge of the previously-employed configuration information)"
> only in the abstract that might also be useful in the introduction, and
> the abstract uses 'hosts' where the introduction uses 'nodes'.  (There
> are a couple other incidental wording differences that the authors might
> wish to consider normalizing on one wording for, as well as the expected
> additional text in the introduction that is not appropriate for an
> abstract.)

What's the specific "text that is not appropriate for an abstract"?




> Section 3.1
> 
>                                                         This means that
>     the advertised "Preferred Lifetime" and "Valid Lifetime" MUST be
>     dynamically adjusted such that they never span past the remaining
>     preferred and valid lifetimes of the corresponding prefixes delegated
>     via DHCPv6-PD on the WAN-side.
> 
> (nitty/editorial) Perhaps it is obvious to most readers, but perhaps it
> is not universally clear that the "advertised" part refers to
> "advertised by the CPE in SLAAC PIOs"; if I wanted to reword to remove
> ambiguity, I might go with something like 'This means that the
> "Preferred Lifetime" and "Valid Lifetime" advertised in PIOs by the CE
> router MUST be dynamically adjusted [...]'.

Done.


> The next paragraph (for the DHCPv6 case) uses a similar wording, but the
> first paragraph of that sentence is a bit more clear about "employed
> with DHCPv6 on the LAN-side" that also serves to reduce the potential
> ambiguity.  I'm happy to see or propose a similar rewording for the
> DHCPv6 case if that would be useful, but don't mind if we leave both
> paragraphs unchnaged, either.

Fixed this one, too.



>     CE Routers providing stateful address configuration via DHCPv6 SHOULD
>     set the DHCPv6 IA Address Option preferred-lifetime to the lesser of
>     the remaining preferred lifetime and ND_PREFERRED_LIMIT, and the
>     valid-lifetime of the same option to the lesser of the remaining
>     valid lifetime and ND_VALID_LIMIT.
> 
> Is it worth mentioning that ND_PREFERRED_LIMIT and ND_VALID_LIMIT are
> defined in Section 4?

Done.



> Section 3.2
> 
>        *  CE Routers need not employ the (possibly long) DHCPv6-PD
>           lifetimes for the Valid Lifetime and Preferred Lifetime of PIOs
> 
> (nit) do we want "received" in there anywhere (e.g., "received DHCPv6-PD
> lifetimes")?
> 
>        *  Similarly, CE Routers need not employ the (possibly long)
>           DHCPv6-PD lifetimes for the valid-lifetime and preferred-
> 
> (Likewise, we could use "received" or "WAN-side" here.)

Applied both.



> Section 3.3
> 
>     In order to phase-out stale SLAAC configuration information:
>     [...]
>     If a CE Router provides LAN-side DHCPv6 (address assignment or prefix
>     delegation), then:
>     [...]
> 
> (editorial) Can/should these sentences use a parallel structure (e.g.,
> "If a CE Router provides SLAAC configuration information, then [...]")?

Done.


> 
>        *  In Replies to DHCPv6 Request, Renew, Rebind messages, send 0
>           lifetimes for any address assignments or prefix delegations for
>           the deprecated prefixes for at least the valid-lifetime
>           previously employed for them, or for a period of ND_VALID_LIMIT
>           if the recommended lifetimes from Section 3.2 are employed.
> 
> Is it deliberate to say nothing at all about Advertise messages (which
> are sent in response to Solicit messages, not any of the listed ones)?

I will double-check this one with my co-authors.


>        *  The requirement in this section is conveyed as a "SHOULD" (as
>           opposed to a "MUST"), since we acknowledge that the requirement
>           to store information on stable storage may represent a
>           challenge for some implementations.
> 
> (editorial/style) It's not entirely clear that we gain much from the use
> of the first person, here.  E.g., we could say 'conveyed as a "SHOULD"
> (as opposed to a "MUST"), since the requirement to store information on
> stable storage may represent a challenge for some implementations'.

Done.



> Section 6
> 
> I suggest noting that the security considerations from RFC 7084 continue
> to apply.  (Also, basically the same comment I had for
> draft-ietf-v6ops-slaac-renum applies, which still does not imply any
> changes to the text.)

Done. We've added that the security implications of rfc4861, rfc4862, 
rfc8415, and rfc7084 still apply.



> Section 8.2
> 
> It would feel more natural, at least to me, if RFC 7084 was listed as a
> normative reference.  (In the sense that we are Updating it to make
> incremental additions, but you need the whole combined assembly of both
> documents in order to have a functional setup.)

I would assume so. But it would be a downref. Is that possible?

Thanks!

Regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan 27 13:37:46 2021
Return-Path: <mellon@fugue.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 E00483A0B9B for <v6ops@ietfa.amsl.com>; Wed, 27 Jan 2021 13:37:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 y1OJPDI3pXhX for <v6ops@ietfa.amsl.com>; Wed, 27 Jan 2021 13:37:39 -0800 (PST)
Received: from mail-qv1-xf31.google.com (mail-qv1-xf31.google.com [IPv6:2607:f8b0:4864:20::f31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 427E03A0B3A for <v6ops@ietf.org>; Wed, 27 Jan 2021 13:37:39 -0800 (PST)
Received: by mail-qv1-xf31.google.com with SMTP id j4so1839697qvk.6 for <v6ops@ietf.org>; Wed, 27 Jan 2021 13:37:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=9+uLjGA67zDr7ZQTvYh2V6MwjV0yLI0bXnhaEfsQ/Cw=; b=pgm+4wNWrq71SPh4dSQANlr9Wxet1JAVW4H+pAqYkimETRHRgK4b4YpFponHJobBVZ qDJfW13YZHhgDRzuRJrNeiKqarS70QUpZnLn29TErsUqE4Bzn6oFfcF1HMZX+0R8sczW 504vydTKAwkwVDjrSl5TeO9rXscEJpgG7pz6rwR59o/kTNHgNpRFzt0WYFz0/li/KAs3 XBOfheVrGaDbkcguXscIFJgf0ACnYFPb/M5x1BULk1hIuclEuUI5Z6AiDpaQ9RmdrWWz Qp/i3ICPdOeRqnwm8Yrtv6yx+hlzH60YqGt9hupTQDUZLGDin1DDtCf29HcW3yKCqvg7 vdBg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=9+uLjGA67zDr7ZQTvYh2V6MwjV0yLI0bXnhaEfsQ/Cw=; b=NqTx95Bp2Fmn420nQVbNxf5ELw6DcxoiFn0yEYvgsTDd1n+c7MpQMWBJdf3Lz1jpno omanUqXlw4L6dUpFBgc6XNJgG4mI9dtrtpaf4ejjumgY0+vW40CVjGJSc4tEiUDVVcZn DA/bsQFqAqNdOhKLNVT0FYc47IJOVsT9qPkaQZJ7646zWQNifd5mYpqdGFJUBHH6+5EZ 7zz1PiOw3fpRLEr9/3iGhenl9ybEN4rvV4lFyWl3BGPMp0KiR8eWwOhR5qsHy1WNZmpv ywE81ttKNFoYVMF7ejh8tFYv8C+b8by4pP1hE08S4clg8mNXIFUm4ewv/LhSVOyTItik M06w==
X-Gm-Message-State: AOAM530XvrTxILPXMAnJfH78oLwIvmtDx+M5ZElGAvDaNFmGjaLP6aaA e+XkX/qhNbzsd0eIzYHDE/BLeQ==
X-Google-Smtp-Source: ABdhPJw9mTo72ng/g2Y67Bf/U+z0HpHt9poYcVEc2ev/lTCi+wsTgwdz6kLhPMmKatSLnLVolrvmvA==
X-Received: by 2002:a0c:8f09:: with SMTP id z9mr12274145qvd.25.1611783458218;  Wed, 27 Jan 2021 13:37:38 -0800 (PST)
Received: from [192.168.4.75] (c-24-91-177-160.hsd1.ma.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id v145sm2105474qka.27.2021.01.27.13.37.37 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 27 Jan 2021 13:37:37 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <C68DC427-85A4-4AE7-928A-C92AD2C4488A@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F4ACCDDD-192E-4821-A7BC-058401B43973"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Date: Wed, 27 Jan 2021 16:37:36 -0500
In-Reply-To: <cf025acf-5192-d9a3-a727-8716d9d7b232@si6networks.com>
Cc: Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>, v6ops-chairs@ietf.org, v6ops@ietf.org, draft-ietf-v6ops-cpe-slaac-renum@ietf.org
To: Fernando Gont <fgont@si6networks.com>
References: <160325603610.17357.6914550111489766157@ietfa.amsl.com> <cf025acf-5192-d9a3-a727-8716d9d7b232@si6networks.com>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/fUN8rM5HrYsnT7Ox6NBVx2mjjps>
Subject: Re: [v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-cpe-slaac-renum-05: (with COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jan 2021 21:37:44 -0000

--Apple-Mail=_F4ACCDDD-192E-4821-A7BC-058401B43973
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Jan 27, 2021, at 4:21 PM, Fernando Gont <fgont@si6networks.com> =
wrote:
> What's the specific "text that is not appropriate for an abstract=E2=80=9D=
?

The abstract should just say what topic the document covers and where =
it=E2=80=99s applicable. Anything more than that goes in the =
introduction. Otherwise you get these multi-paragraph abstracts that =
aren=E2=80=99t at all abstract, and don=E2=80=99t help the reader to =
decide whether or not to read the document.

Of course, usually you read the document because someone told you to, or =
because some other document references it, so maybe this isn=E2=80=99t =
that important=E2=80=A6 :)



--Apple-Mail=_F4ACCDDD-192E-4821-A7BC-058401B43973
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">On =
Jan 27, 2021, at 4:21 PM, Fernando Gont &lt;<a =
href=3D"mailto:fgont@si6networks.com" =
class=3D"">fgont@si6networks.com</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"caret-color: =
rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">What's the specific "text that is not appropriate for an =
abstract=E2=80=9D?</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Menlo-Regular; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""></div></blockquote><br =
class=3D""></div><div>The abstract should just say what topic the =
document covers and where it=E2=80=99s applicable. Anything more than =
that goes in the introduction. Otherwise you get these multi-paragraph =
abstracts that aren=E2=80=99t at all abstract, and don=E2=80=99t help =
the reader to decide whether or not to read the document.</div><div><br =
class=3D""></div><div>Of course, usually you read the document because =
someone told you to, or because some other document references it, so =
maybe this isn=E2=80=99t that important=E2=80=A6 :)</div><div><br =
class=3D""></div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_F4ACCDDD-192E-4821-A7BC-058401B43973--


From nobody Wed Jan 27 14:04:28 2021
Return-Path: <fgont@si6networks.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 ED3F73A0C66; Wed, 27 Jan 2021 14:04: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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, 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 mWc-EfJVJAUb; Wed, 27 Jan 2021 14:04:20 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4EB33A0C68; Wed, 27 Jan 2021 14:04:06 -0800 (PST)
Received: from [IPv6:2800:810:464:2b9:69a9:e23f:a699:f848] (unknown [IPv6:2800:810:464:2b9:69a9:e23f:a699:f848]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 12DFA2803F1; Wed, 27 Jan 2021 22:04:01 +0000 (UTC)
To: Ted Lemon <mellon@fugue.com>
Cc: draft-ietf-v6ops-cpe-slaac-renum@ietf.org, v6ops@ietf.org, v6ops-chairs@ietf.org, Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>
References: <160325603610.17357.6914550111489766157@ietfa.amsl.com> <cf025acf-5192-d9a3-a727-8716d9d7b232@si6networks.com> <C68DC427-85A4-4AE7-928A-C92AD2C4488A@fugue.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <9404f657-dbcb-877d-5a3f-1f3408c3b890@si6networks.com>
Date: Wed, 27 Jan 2021 19:01:50 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <C68DC427-85A4-4AE7-928A-C92AD2C4488A@fugue.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/pRJ7Vn3e8BjARc2YX4rV725csYg>
Subject: Re: [v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-cpe-slaac-renum-05: (with COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jan 2021 22:04:23 -0000

On 27/1/21 18:37, Ted Lemon wrote:
> On Jan 27, 2021, at 4:21 PM, Fernando Gont <fgont@si6networks.com 
> <mailto:fgont@si6networks.com>> wrote:
>> What's the specific "text that is not appropriate for an abstract”?
> 
> The abstract should just say what topic the document covers and where 
> it’s applicable.

Would this be a more concise Abstract?

This document specifies improvements to Customer Edge Routers that help 
mitigate the problems that may arise when network configuration 
information becomes invalid, without any explicit signaling of that 
condition to the affected nodes. This document updates RFC7084.


> Anything more than that goes in the introduction. 
> Otherwise you get these multi-paragraph abstracts that aren’t at all 
> abstract, and don’t help the reader to decide whether or not to read the 
> document.

I agree on that. At the same time, many times I have been asked to add 
*more* to the Abstract. :-)



> Of course, usually you read the document because someone told you to, or 
> because some other document references it, so maybe this isn’t that 
> important… :)

Agreed.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan 27 14:06:45 2021
Return-Path: <mellon@fugue.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 CF37F3A0C7A for <v6ops@ietfa.amsl.com>; Wed, 27 Jan 2021 14:06:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 114nmOJg3dYR for <v6ops@ietfa.amsl.com>; Wed, 27 Jan 2021 14:06:38 -0800 (PST)
Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF2493A0C7C for <v6ops@ietf.org>; Wed, 27 Jan 2021 14:06:37 -0800 (PST)
Received: by mail-qk1-x736.google.com with SMTP id n7so3413762qkc.4 for <v6ops@ietf.org>; Wed, 27 Jan 2021 14:06:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=9mWD0c1Ba7Pr3nof/C88Q96f1wgeVId6zk2f37ab9nc=; b=sWNCx78Bwym8BuhSOU/TxGTLtnji6CEqdjDbWstD8YBFyUtN5hqgwQGHnjLAyKG01Z ytmDeVkhzGeJGdNPgsN7o08gZEuhlZxocGXHCLt0l4Bo9shELwvnph6IFvR932me26yP Rk2vjH7BF6/F66lz3yyArYTcsytda4E8d5xfFqC4FXRoyNUS33C9O1KnUr+DgbmK4qx9 SR6nUVvvVqGXNbzUB6PF3mwK1kYqYwdrhjhF8BxRnHIjbhQqfqjvdpSiSXP2Q5jvaZHk gtqCJHdWviq5MfTU/RbG1aS4+CJ7qfZGNg6h24GQ7huyHTZYpfBboB+4c8DhbNq5Cvyv z/fg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=9mWD0c1Ba7Pr3nof/C88Q96f1wgeVId6zk2f37ab9nc=; b=C3b4JtmxQekkV8RsqkSd9xOdIFCQwI8wCfW5Tly7pCLMuEw5KoIBamGjJ/ZNKCJ9kE EmUw/7voxjt800uEF1x4OwZRJvF8eq+z3JdJt+IUWlH0TTYEVjCfuH02R+W1CMUBcRtV H15gwDzVUjWJ6qZdzAxN7/tNad/5Yng4VGHeMlaBH++o9f0W2jWH5ZyfUtIBxkwmWJyr 5xFJHJHlsNQNU3tGJknlAQEkKSzrXo/XYey32AjFrC1pGkcBI6VQpKYa8FN1KfkEcCRe vzYYmlrwBvzDVwRS3Y6fwd8WH5F38HMzr+aQRi0y0wBuVFNfIpe1Ie5n8JHy5Vu1U1LA SWrA==
X-Gm-Message-State: AOAM530dPQkuGbfYvWQymJAK5EpuDf4KHOoAeBv63Pzl5sEk1nXpcnMW q61izLfNd9KXMWCm35NAKikiHg==
X-Google-Smtp-Source: ABdhPJyvrnuWDWWftDf4SjBaJq9xMl30/XceYxhUW/B781wZiS92AhJleOBGq31+HBLRFEKriK42tg==
X-Received: by 2002:a37:a10c:: with SMTP id k12mr6238150qke.443.1611785196912;  Wed, 27 Jan 2021 14:06:36 -0800 (PST)
Received: from [192.168.4.75] (c-24-91-177-160.hsd1.ma.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id 77sm2119574qkk.29.2021.01.27.14.06.36 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 27 Jan 2021 14:06:36 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <DAA65B0F-38F7-4785-8C5B-2E8E323C57B3@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_1265B52E-19F6-4D7D-AE2B-FEFDD565C817"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Date: Wed, 27 Jan 2021 17:06:34 -0500
In-Reply-To: <9404f657-dbcb-877d-5a3f-1f3408c3b890@si6networks.com>
Cc: draft-ietf-v6ops-cpe-slaac-renum@ietf.org, IPv6 Operations <v6ops@ietf.org>, v6ops-chairs@ietf.org, Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>
To: Fernando Gont <fgont@si6networks.com>
References: <160325603610.17357.6914550111489766157@ietfa.amsl.com> <cf025acf-5192-d9a3-a727-8716d9d7b232@si6networks.com> <C68DC427-85A4-4AE7-928A-C92AD2C4488A@fugue.com> <9404f657-dbcb-877d-5a3f-1f3408c3b890@si6networks.com>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/iVhVmqd2f5vBS2KtNTNyWmmK9DM>
Subject: Re: [v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-cpe-slaac-renum-05: (with COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jan 2021 22:06:41 -0000

--Apple-Mail=_1265B52E-19F6-4D7D-AE2B-FEFDD565C817
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Jan 27, 2021, at 5:01 PM, Fernando Gont <fgont@si6networks.com> =
wrote:
> This document specifies improvements to Customer Edge Routers that =
help mitigate the problems that may arise when network configuration =
information becomes invalid, without any explicit signaling of that =
condition to the affected nodes. This document updates RFC7084.

=E2=80=9CStale=E2=80=9D rather than =E2=80=9Cinvalid=E2=80=9D perhaps? =
But otherwise, yeah. You have budget for another sentence if you want to =
say more. :)


--Apple-Mail=_1265B52E-19F6-4D7D-AE2B-FEFDD565C817
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">On =
Jan 27, 2021, at 5:01 PM, Fernando Gont &lt;<a =
href=3D"mailto:fgont@si6networks.com" =
class=3D"">fgont@si6networks.com</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"caret-color: =
rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">This document specifies improvements to Customer Edge Routers =
that help mitigate the problems that may arise when network =
configuration information becomes invalid, without any explicit =
signaling of that condition to the affected nodes. This document updates =
RFC7084.</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""></div></blockquote></div><br class=3D""><div =
class=3D"">=E2=80=9CStale=E2=80=9D rather than =E2=80=9Cinvalid=E2=80=9D =
perhaps? But otherwise, yeah. You have budget for another sentence if =
you want to say more. :)</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_1265B52E-19F6-4D7D-AE2B-FEFDD565C817--


From nobody Wed Jan 27 14:07:10 2021
Return-Path: <mellon@fugue.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 DEBA03A0CCA for <v6ops@ietfa.amsl.com>; Wed, 27 Jan 2021 14:06:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 0rcIXDsZSrvn for <v6ops@ietfa.amsl.com>; Wed, 27 Jan 2021 14:06:58 -0800 (PST)
Received: from mail-qk1-x72b.google.com (mail-qk1-x72b.google.com [IPv6:2607:f8b0:4864:20::72b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8686E3A0D2F for <v6ops@ietf.org>; Wed, 27 Jan 2021 14:06:57 -0800 (PST)
Received: by mail-qk1-x72b.google.com with SMTP id n15so3402695qkh.8 for <v6ops@ietf.org>; Wed, 27 Jan 2021 14:06:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=/9Kq60gZy4a3XAqTWKHY/yeaMjn+3KfQ++FncT1+6U8=; b=dOceKVUXZnokZVolf/Ke7tpPQ7YLJFcdkZtYD7eGIMrdAX0Qf2JJ4D94uTbKEaVv+P /5eO5s3Z6X1T88Is6WUoArw65ypCpetfEZFem6rarMbuV6ARiczLgh34ah0M/7HmLYEB x94grV7CylF4pWukIR8i89pkrFLz0AeRbzQbWobTGawS4CtP0LZGHmN9bI53AjIzf8id 0HmOGQBw4IKbuFb99x90aElJMG4AuvrstBLbJq+XhN1FToprAugtyJskY+z0dWJGRVyV 8uCKdDgshaN5kjSXwVsf8zZ9phnGNoNDmeFwWx3i3Z4twvhrx8yB2VBO4N9GgIWmgcM2 +8UA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=/9Kq60gZy4a3XAqTWKHY/yeaMjn+3KfQ++FncT1+6U8=; b=OwBvkXfpRN4j8HbPl3BAeMTy+LPzZind+Kf7UqpbevWWL/vH09Fkn/8gzYMj3Ni93z j/9JTMuR2rdet0hdjFR4MrYkik7Fyy6DtmMQ028dHfb1hQ6swkmOEpYYvp+mIRNtjSwa 1oq4qsVZnXCiL5yEQeBTzaMjxjuyiN/cFkYPWLmGz3WGFgL1pVpX8IEpCew52C8mGbbt b8AGgnpVkuhVOgKJqMy4rSr11cQweWsuHD9kM2QmUpDuxnXN9jqHPMeLb0HJtjRR0O8b Dd/Y4K2eKwhCDlKIaHETqXFJwLOE7TPjaej0yh0VlWQkK+fEsARgwGF8RKDT36BStjbt RqTg==
X-Gm-Message-State: AOAM531uoNCTS0r9vJDLyE3W766kEETyV7dBLg3gXlqpQkDmzZy28PI0 ye0PFoJ7O8ozganYVZFAJGLBhq+5VSV+bg==
X-Google-Smtp-Source: ABdhPJwvhA6BR4iBAzJjFM4nXX9b14mJBBmVlwrtmOdk/OfV4WOZK+RYujonujLAvLV5VqeeOLHVOg==
X-Received: by 2002:a37:b404:: with SMTP id d4mr12723255qkf.183.1611785216559;  Wed, 27 Jan 2021 14:06:56 -0800 (PST)
Received: from [192.168.4.75] (c-24-91-177-160.hsd1.ma.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id 77sm2119574qkk.29.2021.01.27.14.06.55 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 27 Jan 2021 14:06:56 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <30262C9F-D004-4452-9F40-A407D7B396D3@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_409FC32B-640D-476C-94F6-A203E08991BB"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Date: Wed, 27 Jan 2021 17:06:55 -0500
In-Reply-To: <9404f657-dbcb-877d-5a3f-1f3408c3b890@si6networks.com>
Cc: draft-ietf-v6ops-cpe-slaac-renum@ietf.org, v6ops@ietf.org, v6ops-chairs@ietf.org, Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>
To: Fernando Gont <fgont@si6networks.com>
References: <160325603610.17357.6914550111489766157@ietfa.amsl.com> <cf025acf-5192-d9a3-a727-8716d9d7b232@si6networks.com> <C68DC427-85A4-4AE7-928A-C92AD2C4488A@fugue.com> <9404f657-dbcb-877d-5a3f-1f3408c3b890@si6networks.com>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/6sAxXyG1nIKaWqZ-y1j8rRvKPa0>
Subject: Re: [v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-cpe-slaac-renum-05: (with COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jan 2021 22:07:06 -0000

--Apple-Mail=_409FC32B-640D-476C-94F6-A203E08991BB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Oh, you don=E2=80=99t need to say =E2=80=9Cupdates=E2=80=9D in the =
abstract because that=E2=80=99s in the header.

> On Jan 27, 2021, at 5:01 PM, Fernando Gont <fgont@si6networks.com> =
wrote:
>=20
> This document specifies improvements to Customer Edge Routers that =
help mitigate the problems that may arise when network configuration =
information becomes invalid, without any explicit signaling of that =
condition to the affected nodes. This document updates RFC7084.


--Apple-Mail=_409FC32B-640D-476C-94F6-A203E08991BB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Oh, =
you don=E2=80=99t need to say =E2=80=9Cupdates=E2=80=9D in the abstract =
because that=E2=80=99s in the header.<br class=3D""><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On Jan =
27, 2021, at 5:01 PM, Fernando Gont &lt;<a =
href=3D"mailto:fgont@si6networks.com" =
class=3D"">fgont@si6networks.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; =
font-size: 14px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">This document =
specifies improvements to Customer Edge Routers that help mitigate the =
problems that may arise when network configuration information becomes =
invalid, without any explicit signaling of that condition to the =
affected nodes. This document updates RFC7084.</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; =
font-size: 14px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""></div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_409FC32B-640D-476C-94F6-A203E08991BB--


From nobody Wed Jan 27 14:23:08 2021
Return-Path: <kaduk@mit.edu>
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 6A1243A0CAF; Wed, 27 Jan 2021 14:23:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 lh_zOlrZuBT7; Wed, 27 Jan 2021 14:23:01 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 061FE3A0CAC; Wed, 27 Jan 2021 14:23:00 -0800 (PST)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 10RMMpKC021599 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 27 Jan 2021 17:22:56 -0500
Date: Wed, 27 Jan 2021 14:22:50 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: Ted Lemon <mellon@fugue.com>
Cc: Fernando Gont <fgont@si6networks.com>, The IESG <iesg@ietf.org>, v6ops-chairs@ietf.org, v6ops@ietf.org, draft-ietf-v6ops-cpe-slaac-renum@ietf.org
Message-ID: <20210127222250.GN21@kduck.mit.edu>
References: <160325603610.17357.6914550111489766157@ietfa.amsl.com> <cf025acf-5192-d9a3-a727-8716d9d7b232@si6networks.com> <C68DC427-85A4-4AE7-928A-C92AD2C4488A@fugue.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <C68DC427-85A4-4AE7-928A-C92AD2C4488A@fugue.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/OQzzt6FGCtKZtAzMo_ooFp4bcEk>
Subject: Re: [v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-cpe-slaac-renum-05: (with COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jan 2021 22:23:04 -0000

Hi Ted, Fernando,

On Wed, Jan 27, 2021 at 04:37:36PM -0500, Ted Lemon wrote:
> On Jan 27, 2021, at 4:21 PM, Fernando Gont <fgont@si6networks.com> wrote:
> > What's the specific "text that is not appropriate for an abstract”?
> 
> The abstract should just say what topic the document covers and where it’s applicable. Anything more than that goes in the introduction. Otherwise you get these multi-paragraph abstracts that aren’t at all abstract, and don’t help the reader to decide whether or not to read the document.
> 
> Of course, usually you read the document because someone told you to, or because some other document references it, so maybe this isn’t that important… :)

I agree with everything you say, though I think there may have been some
miscommunication earlier in the thread.

In particular, I was just trying to say that:
I looked at the diff between abstract and introduction, and there were some
noteworthy bits and some non-noteworthy bits.  The non-noteworthy bits are
the several extra paragrpahs in the introduction, since that's a large part
of what the difference between abstract and introduction is supposed to be.

Specifically, the "text that is not appropriate for an abstract" is
referring to text that is already (and correctly) in the introduction.  (At
least, that's what I thought when I read it the first time; I didn't look
at it right now to check.)

-Ben


From nobody Wed Jan 27 14:27:28 2021
Return-Path: <fgont@si6networks.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 191993A0CCC; Wed, 27 Jan 2021 14:27:17 -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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, 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 H3qtcF_6IYiF; Wed, 27 Jan 2021 14:27:15 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A03F3A0D00; Wed, 27 Jan 2021 14:27:15 -0800 (PST)
Received: from [IPv6:2800:810:464:2b9:69a9:e23f:a699:f848] (unknown [IPv6:2800:810:464:2b9:69a9:e23f:a699:f848]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id EEB4F2803F1; Wed, 27 Jan 2021 22:27:11 +0000 (UTC)
To: Ted Lemon <mellon@fugue.com>
Cc: draft-ietf-v6ops-cpe-slaac-renum@ietf.org, v6ops@ietf.org, v6ops-chairs@ietf.org, Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>
References: <160325603610.17357.6914550111489766157@ietfa.amsl.com> <cf025acf-5192-d9a3-a727-8716d9d7b232@si6networks.com> <C68DC427-85A4-4AE7-928A-C92AD2C4488A@fugue.com> <9404f657-dbcb-877d-5a3f-1f3408c3b890@si6networks.com> <30262C9F-D004-4452-9F40-A407D7B396D3@fugue.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <85f2bc3f-51f5-a5b2-53cd-9b5a52ac227f@si6networks.com>
Date: Wed, 27 Jan 2021 19:27:02 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <30262C9F-D004-4452-9F40-A407D7B396D3@fugue.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/298GiNttNbjzNhbbfdulA_e5UDs>
Subject: Re: [v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-cpe-slaac-renum-05: (with COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jan 2021 22:27:23 -0000

On 27/1/21 19:06, Ted Lemon wrote:
> Oh, you don’t need to say “updates” in the abstract because that’s in 
> the header.

I added that to the Abstract because I was *asked* to. You see what I 
mean? :-)


-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan 27 14:33:25 2021
Return-Path: <mellon@fugue.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 0E3663A0CF9 for <v6ops@ietfa.amsl.com>; Wed, 27 Jan 2021 14:33:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 3QxGDSpO9cvk for <v6ops@ietfa.amsl.com>; Wed, 27 Jan 2021 14:33:21 -0800 (PST)
Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5197C3A0A1B for <v6ops@ietf.org>; Wed, 27 Jan 2021 14:33:01 -0800 (PST)
Received: by mail-qk1-x736.google.com with SMTP id t63so3498895qkc.1 for <v6ops@ietf.org>; Wed, 27 Jan 2021 14:33:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=N2TXqlzW5mG4vSaNTpR5Z2AeMT6UAI+3nlDCu0CpynU=; b=B86V9hymeL/CvOlK3pKnPiKHjkBWB41om0AJrfSfJl5Go+pDrUI9E9Zprwh6hqnfdr 9ZtDTKe7rdDuH7hgPW51fFkzNTvjrTk+30hWGHO+xQXLVeQVzO0xEe9jBv4znZVI9yFn pCs97hvpsL5hJZNK+z5ks4Nw/4cBXcaR57w+UWCWU0vreN88RveNY60ckd8gIYy5c2sy kuXfc+eB4URJierQgIV2+zd7gbQCMJSc2I+fTnUJ25/sGlMUuq5GhfxKnoLCD9ErAa5a FPVmi4aaI4r167PrLV9MCw9hiimW5867jTnxExEM633hKA+u2aJSj9DKhSfhl/r6QTzS 93Pw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=N2TXqlzW5mG4vSaNTpR5Z2AeMT6UAI+3nlDCu0CpynU=; b=QPmMVoRcw5X/91sD1IN+UgsVyLUUs8veTK8iTKbmUWVCWrAfcAeWXMw5yWAIhr6qMM UrFbtt94fjmYAplSyw+GlZWMcqJZDmlolPtKrYrN58lvIYbMKXEkHMnw6adOBzciHB8X EeberNW9aPaqtPZp7eFl5uQuN/eb81eREGj9od5CgcMr40BFiOcJTs0XoF4sYZAHHuqW 0Sm4c5JLzYLtsSt3ft+aiiSoXTFBLXdPnpA5WfBGY8XbEeEgputrJAyrs25wX1BY1mv4 7kaAPSdwqlFpGGD/7MPUQI8zIH9XLnE5QcaieMgiYfHg0r2E0ILEXnsHZ1UVKzZSX4hd QQlw==
X-Gm-Message-State: AOAM531aSG5K3/OeuO3oNNJjaWs5h4nxz3m2scEO9A0SAezn2RztQBDf 678MnxAoSViw6BJMegAGdtEKTg==
X-Google-Smtp-Source: ABdhPJz48y5EcngAXNxtywE6r08J0Eqy3bnnuRlXUdQOWUrMXm5rHYid8dTNQcF5vjXorM4aDBpfNg==
X-Received: by 2002:a05:620a:1398:: with SMTP id k24mr12996792qki.109.1611786779818;  Wed, 27 Jan 2021 14:32:59 -0800 (PST)
Received: from [192.168.4.75] (c-24-91-177-160.hsd1.ma.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id x20sm2305091qtb.16.2021.01.27.14.32.58 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 27 Jan 2021 14:32:59 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <D563B1C2-EDEE-4352-9096-8E5877046E28@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_EBFBDB80-248B-4F12-8A5B-428D3FB5FA3F"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Date: Wed, 27 Jan 2021 17:32:57 -0500
In-Reply-To: <85f2bc3f-51f5-a5b2-53cd-9b5a52ac227f@si6networks.com>
Cc: draft-ietf-v6ops-cpe-slaac-renum@ietf.org, v6ops@ietf.org, v6ops-chairs@ietf.org, Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>
To: Fernando Gont <fgont@si6networks.com>
References: <160325603610.17357.6914550111489766157@ietfa.amsl.com> <cf025acf-5192-d9a3-a727-8716d9d7b232@si6networks.com> <C68DC427-85A4-4AE7-928A-C92AD2C4488A@fugue.com> <9404f657-dbcb-877d-5a3f-1f3408c3b890@si6networks.com> <30262C9F-D004-4452-9F40-A407D7B396D3@fugue.com> <85f2bc3f-51f5-a5b2-53cd-9b5a52ac227f@si6networks.com>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Gtd_J2cMol3QwkMKf03ZzYWQhiM>
Subject: Re: [v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-cpe-slaac-renum-05: (with COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jan 2021 22:33:23 -0000

--Apple-Mail=_EBFBDB80-248B-4F12-8A5B-428D3FB5FA3F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Jan 27, 2021, at 5:27 PM, Fernando Gont <fgont@si6networks.com> =
wrote:
> I added that to the Abstract because I was *asked* to. You see what I =
mean? :-)

Huh. Well, it=E2=80=99s mostly harmless, so I wouldn=E2=80=99t waste any =
time trying to resolve this=E2=80=94just leave it in. But I don=E2=80=99t =
think it=E2=80=99s a best practice to do this, so next time it comes up =
I=E2=80=99d be tempted to argue the point.


--Apple-Mail=_EBFBDB80-248B-4F12-8A5B-428D3FB5FA3F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">On =
Jan 27, 2021, at 5:27 PM, Fernando Gont &lt;<a =
href=3D"mailto:fgont@si6networks.com" =
class=3D"">fgont@si6networks.com</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"caret-color: =
rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">I added that to the Abstract because I was *asked* to. You =
see what I mean? :-)</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Menlo-Regular; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""></div></blockquote></div><br =
class=3D""><div class=3D"">Huh. Well, it=E2=80=99s mostly harmless, so I =
wouldn=E2=80=99t waste any time trying to resolve this=E2=80=94just =
leave it in. But I don=E2=80=99t think it=E2=80=99s a best practice to =
do this, so next time it comes up I=E2=80=99d be tempted to argue the =
point.</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_EBFBDB80-248B-4F12-8A5B-428D3FB5FA3F--


From nobody Wed Jan 27 14:52:46 2021
Return-Path: <fgont@si6networks.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 DA75F3A0E06; Wed, 27 Jan 2021 14:52:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, 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 jwN0iGK5XO6o; Wed, 27 Jan 2021 14:52:31 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 922A33A0D8B; Wed, 27 Jan 2021 14:52:28 -0800 (PST)
Received: from [IPv6:2800:810:464:2b9:69a9:e23f:a699:f848] (unknown [IPv6:2800:810:464:2b9:69a9:e23f:a699:f848]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 91331280497; Wed, 27 Jan 2021 22:52:24 +0000 (UTC)
From: Fernando Gont <fgont@si6networks.com>
To: Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>
Cc: draft-ietf-v6ops-cpe-slaac-renum@ietf.org, v6ops-chairs@ietf.org, v6ops@ietf.org, Owen DeLong <owen@delong.com>
References: <160325603610.17357.6914550111489766157@ietfa.amsl.com> <cf025acf-5192-d9a3-a727-8716d9d7b232@si6networks.com>
Message-ID: <4fbc24c6-ef7b-5a99-3d04-69e6c9c3c90a@si6networks.com>
Date: Wed, 27 Jan 2021 19:49:01 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <cf025acf-5192-d9a3-a727-8716d9d7b232@si6networks.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/acyavcPSaRioJShgK0hmXM3Zb-o>
Subject: Re: [v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-cpe-slaac-renum-05: (with COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jan 2021 22:52:40 -0000

Hi, Ben,

On 27/1/21 18:21, Fernando Gont wrote:
[....]
>>        *  In Replies to DHCPv6 Request, Renew, Rebind messages, send 0
>>           lifetimes for any address assignments or prefix delegations for
>>           the deprecated prefixes for at least the valid-lifetime
>>           previously employed for them, or for a period of ND_VALID_LIMIT
>>           if the recommended lifetimes from Section 3.2 are employed.
>>
>> Is it deliberate to say nothing at all about Advertise messages (which
>> are sent in response to Solicit messages, not any of the listed ones)?
> 
> I will double-check this one with my co-authors.

Our plan is to add this note to the RATIONALE of Section 3.3:

    The above text does not include responses to DHCPv6 Solicit messages,
    since Section 18.3.9 of RFC8415 requires that a DHCPv6 server
    that is not going to assign an address or delegated prefix received
    as a hint in the Solicit message MUST NOT include that address or
    delegated prefix in the Advertise message. Additionally, any
    subsequent Solicit messages will trigger the response specified in
    this section, and therefore cause the address or prefix to be
    deprecated.

Would this address your comment?

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan 27 14:52:50 2021
Return-Path: <fgont@si6networks.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 3E5483A0E13; Wed, 27 Jan 2021 14:52:38 -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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, 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 fkdsKDZUT5Ly; Wed, 27 Jan 2021 14:52:35 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 761293A0DF8; Wed, 27 Jan 2021 14:52:33 -0800 (PST)
Received: from [IPv6:2800:810:464:2b9:69a9:e23f:a699:f848] (unknown [IPv6:2800:810:464:2b9:69a9:e23f:a699:f848]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 85923280510; Wed, 27 Jan 2021 22:52:29 +0000 (UTC)
To: Benjamin Kaduk <kaduk@mit.edu>, Ted Lemon <mellon@fugue.com>
Cc: The IESG <iesg@ietf.org>, v6ops-chairs@ietf.org, v6ops@ietf.org, draft-ietf-v6ops-cpe-slaac-renum@ietf.org
References: <160325603610.17357.6914550111489766157@ietfa.amsl.com> <cf025acf-5192-d9a3-a727-8716d9d7b232@si6networks.com> <C68DC427-85A4-4AE7-928A-C92AD2C4488A@fugue.com> <20210127222250.GN21@kduck.mit.edu>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <b277f085-eb94-60be-0228-c89dd6a09800@si6networks.com>
Date: Wed, 27 Jan 2021 19:51:46 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <20210127222250.GN21@kduck.mit.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/GrU3aSGutX9LN1Jq9rsX6eq68ds>
Subject: Re: [v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-cpe-slaac-renum-05: (with COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jan 2021 22:52:41 -0000

On 27/1/21 19:22, Benjamin Kaduk wrote:
[...]
> 
> I agree with everything you say, though I think there may have been some
> miscommunication earlier in the thread.
> 
> In particular, I was just trying to say that:
> I looked at the diff between abstract and introduction, and there were some
> noteworthy bits and some non-noteworthy bits.  The non-noteworthy bits are
> the several extra paragrpahs in the introduction, since that's a large part
> of what the difference between abstract and introduction is supposed to be.
> 
> Specifically, the "text that is not appropriate for an abstract" is
> referring to text that is already (and correctly) in the introduction.  (At
> least, that's what I thought when I read it the first time; I didn't look
> at it right now to check.)

How about this for the Abstract:

This document specifies improvements to Customer Edge Routers that help 
mitigate the problems that may arise when network configuration 
information becomes invalid, without any explicit signaling of that 
condition to the affected nodes. This document updates RFC7084.

.. at the end of the day, that's what the document is about.

(Note: I wouldn't have added the "This document updates RFC7084", but 
have been asked to. But won't argue about it either way :-) )

-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan 27 15:19:59 2021
Return-Path: <nick@foobar.org>
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 782D53A0D55; Wed, 27 Jan 2021 15:19:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 AOFwt5kxMEaL; Wed, 27 Jan 2021 15:19:54 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [46.182.8.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CA993A0D44; Wed, 27 Jan 2021 15:19:49 -0800 (PST)
X-Envelope-To: draft-ietf-v6ops-cpe-slaac-renum@ietf.org
Received: from crumpet.local (admin.ibn.ie [46.182.8.8]) (authenticated bits=0) by mail.netability.ie (8.16.1/8.16.1) with ESMTPSA id 10RNJi1S069015 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Jan 2021 23:19:45 GMT (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host admin.ibn.ie [46.182.8.8] claimed to be crumpet.local
To: Ted Lemon <mellon@fugue.com>
Cc: Fernando Gont <fgont@si6networks.com>, v6ops-chairs@ietf.org, v6ops@ietf.org, draft-ietf-v6ops-cpe-slaac-renum@ietf.org, Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>
References: <160325603610.17357.6914550111489766157@ietfa.amsl.com> <cf025acf-5192-d9a3-a727-8716d9d7b232@si6networks.com> <C68DC427-85A4-4AE7-928A-C92AD2C4488A@fugue.com> <9404f657-dbcb-877d-5a3f-1f3408c3b890@si6networks.com> <30262C9F-D004-4452-9F40-A407D7B396D3@fugue.com> <85f2bc3f-51f5-a5b2-53cd-9b5a52ac227f@si6networks.com> <D563B1C2-EDEE-4352-9096-8E5877046E28@fugue.com>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <b2937f86-eab8-f571-f64e-4c537d2a7b14@foobar.org>
Date: Wed, 27 Jan 2021 23:19:43 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:52.0) Gecko/20100101 PostboxApp/7.0.45
MIME-Version: 1.0
In-Reply-To: <D563B1C2-EDEE-4352-9096-8E5877046E28@fugue.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/20xOX3FYIZZr0VX-23i6VG5quUs>
Subject: Re: [v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-cpe-slaac-renum-05: (with COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jan 2021 23:19:58 -0000

Ted Lemon wrote on 27/01/2021 22:32:
> Huh. Well, it’s mostly harmless, so I wouldn’t waste any time trying to 
> resolve this—just leave it in. But I don’t think it’s a best practice to 
> do this, so next time it comes up I’d be tempted to argue the point.

as a general observation unrelated both to this draft and to this 
suggestion, at this stage of the ID process, it's often easier to update 
drafts with reviewers' suggestions even if authors don't feel that the 
suggestions are useful or particularly appropriate.

This is a human nature thing: you just want the draft off your to-do 
list and anything which slows this up, like minor quibbles, are easiest 
to deal with by just agreeing with a silent "meh, whatevs".

This also isn't a criticism of reviewers, whose thankless but critically 
important job is usually done to a very high standard, and is made more 
difficult by having to review content in areas which aren't necessarily 
their specialty.

I don't have a solution to this, but it's worth noting that it happens.

Nick


From nobody Wed Jan 27 15:55:35 2021
Return-Path: <fredbaker.ietf@gmail.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 E789B3A0DDC for <v6ops@ietfa.amsl.com>; Wed, 27 Jan 2021 15:55:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2UWWCP1kO75q for <v6ops@ietfa.amsl.com>; Wed, 27 Jan 2021 15:55:32 -0800 (PST)
Received: from mail-pj1-x102d.google.com (mail-pj1-x102d.google.com [IPv6:2607:f8b0:4864:20::102d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F5263A0DD7 for <v6ops@ietf.org>; Wed, 27 Jan 2021 15:55:32 -0800 (PST)
Received: by mail-pj1-x102d.google.com with SMTP id gx1so2811701pjb.1 for <v6ops@ietf.org>; Wed, 27 Jan 2021 15:55:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:content-transfer-encoding:mime-version:subject:date:message-id :references:cc:to; bh=Uj/64U4EEZOm1GlkXaiD2/gpHy1StmcTxBMGY1odLag=; b=dRmoxy4u11A5VRhMjVr8DrzuXM9TcI/PHT0ppuwmhe3XDtznbYKYrGt5iOI47k00EV mHGL+SMvcXZIXwVQlBP+qHum68w+KQz5JGXuZx8XsdLQRxrgXYjB7OIsLsgmcv9Bd0C8 AWBFP9PB1lrfKf2iq7L/upxJq7fG/MoeNYOR65adMjuAyLxEao+BabUQxykqyn9cQ5XY 6U+6Qy9Z4jJ5i7HV2G+hz4JH8qH4tFJJCNaZqozKTTpkebnHgGD+46B002LkECA1QP1B eVUB2nZD3Inx4ImnDsdfk9eNkSYVfprUCSHFKH4keoCClAb9ZrOTsJDzQsMnzJ5k20v8 u5LA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:message-id:references:cc:to; bh=Uj/64U4EEZOm1GlkXaiD2/gpHy1StmcTxBMGY1odLag=; b=mUEVLnDrtOlSmyzsAt4xNv9LAvDX+C5wyLH9uPnj480TE1Wx9Xc456LMyZOX4p1arM F1bSz+kBeazC9WBif5YSEwoAbme9D8oZTN4S7jram1/S23ylxrzRSDWx1a9WgcooVeoM mjDnTvQgRP4vdoR1Hy1eWg6ylcW3jFWk1XoUZoWBQUjomP3vx5pvT6nOvEy+SVXOwaqV o009/J01QEhHOK7PNXcRM0GM6Va+X4LCjHrJj0wbFD+2KC4E0i2PF61RcBh6mTG19GUH 4gOkrE5t2CtE+e+ArqnZ5ZFqDtxkXHgqR/8EJkPaSZb/XBFvw9ka6mS4N6dPD0YZUUmp DUSA==
X-Gm-Message-State: AOAM532dLeQe5yVN7g3uKd24t0e+pkMuKGbob7yWmL7fCCEmZFkfZB0L 5Y1sIjIoEQGxr5v581syiN7xzquEWVQ=
X-Google-Smtp-Source: ABdhPJxwojIKhU7mLNBbCmcH+v+GziiZjBM1QAne5XOytlW2tcNOOlMYpbQ1meC3IRhXnjkEUY84ZQ==
X-Received: by 2002:a17:90b:4005:: with SMTP id ie5mr8406137pjb.104.1611791732235;  Wed, 27 Jan 2021 15:55:32 -0800 (PST)
Received: from ?IPv6:2601:648:8200:dd20:c150:3bf2:f39f:5244? ([2601:648:8200:dd20:c150:3bf2:f39f:5244]) by smtp.gmail.com with ESMTPSA id c5sm3472829pfi.5.2021.01.27.15.55.31 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 27 Jan 2021 15:55:31 -0800 (PST)
From: Fred Baker <fredbaker.ietf@gmail.com>
X-Google-Original-From: Fred Baker <FredBaker.IETF@gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-A92B8EE0-DD4E-4E22-A7CC-195191280098
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Date: Wed, 27 Jan 2021 15:55:30 -0800
Message-Id: <9E421F9D-3D1D-4481-AC3B-3FC74FB76612@gmail.com>
References: <BL0PR05MB53162455614EC580E88C8306AEBB9@BL0PR05MB5316.namprd05.prod.outlook.com>
To: IPv6 Operations <v6ops@ietf.org>
X-Mailer: iPad Mail (18D52)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/s1NPDs_3hreWHm3Ivzie2n67Rr4>
Subject: [v6ops] Fwd: Disposition of draft-ietf-v6ops-cpe-slaac-renum-05
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jan 2021 23:55:34 -0000

--Apple-Mail-A92B8EE0-DD4E-4E22-A7CC-195191280098
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

My error. The WGLC call I thought had happened and I started this morning in=
 fact has happened. My error. So we=E2=80=99re closing that WGLC (which had e=
xpired), and asking the IESG to continue processing the draft as a BCP.

Sent from my iPad

Begin forwarded message:

> From: Ron Bonica <rbonica@juniper.net>
> Date: January 27, 2021 at 10:07:18 AM PST
> To: Fred Baker <fredbaker.ietf@gmail.com>
> Subject: RE: Disposition of draft-ietf-v6ops-cpe-slaac-renum-05
>=20
> =EF=BB=BFIt happened between December 17 and 29.
>=20
>                                                          Ron
>=20
>=20
>=20
> Juniper Business Use Only
>=20
> -----Original Message-----
> From: Fred Baker <fredbaker.ietf@gmail.com>=20
> Sent: Wednesday, January 27, 2021 10:54 AM
> To: Ron Bonica <rbonica@juniper.net>
> Subject: Re: Disposition of draft-ietf-v6ops-cpe-slaac-renum-05
>=20
>=20
>=20
>> On Dec 17, 2020, at 7:56 AM, Ron Bonica <rbonica@juniper.net> wrote:
>>=20
>> Didn't Warren say that we need another WGLC if we stay with BCP?
>=20
> He did, and I thought that happened. Looking up the mail, however, I guess=
 it didn't. So I'll ask the list.

--Apple-Mail-A92B8EE0-DD4E-4E22-A7CC-195191280098
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto">My error. The WGLC call I thought had happe=
ned and I started this morning in fact has happened. My error. So we=E2=80=99=
re closing that WGLC (which had expired), and asking the IESG to continue pr=
ocessing the draft as a BCP.<br><br><div dir=3D"ltr">Sent from my iPad</div>=
<div dir=3D"ltr"><br>Begin forwarded message:<br><br></div><blockquote type=3D=
"cite"><div dir=3D"ltr"><b>From:</b> Ron Bonica &lt;rbonica@juniper.net&gt;<=
br><b>Date:</b> January 27, 2021 at 10:07:18 AM PST<br><b>To:</b> Fred Baker=
 &lt;fredbaker.ietf@gmail.com&gt;<br><b>Subject:</b> <b>RE: Disposition of d=
raft-ietf-v6ops-cpe-slaac-renum-05</b><br><br></div></blockquote><blockquote=
 type=3D"cite"><div dir=3D"ltr">=EF=BB=BF<span>It happened between December 1=
7 and 29.</span><br><span></span><br><span> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;Ron</span><br><span></span><br><span></span><br><span></span><br><span=
>Juniper Business Use Only</span><br><span></span><br><span>-----Original Me=
ssage-----</span><br><span>From: Fred Baker &lt;fredbaker.ietf@gmail.com&gt;=
 </span><br><span>Sent: Wednesday, January 27, 2021 10:54 AM</span><br><span=
>To: Ron Bonica &lt;rbonica@juniper.net&gt;</span><br><span>Subject: Re: Dis=
position of draft-ietf-v6ops-cpe-slaac-renum-05</span><br><span></span><br><=
span></span><br><span></span><br><blockquote type=3D"cite"><span>On Dec 17, 2=
020, at 7:56 AM, Ron Bonica &lt;rbonica@juniper.net&gt; wrote:</span><br></b=
lockquote><blockquote type=3D"cite"><span></span><br></blockquote><blockquot=
e type=3D"cite"><span>Didn't Warren say that we need another WGLC if we stay=
 with BCP?</span><br></blockquote><span></span><br><span>He did, and I thoug=
ht that happened. Looking up the mail, however, I guess it didn't. So I'll a=
sk the list.</span><br></div></blockquote></body></html>=

--Apple-Mail-A92B8EE0-DD4E-4E22-A7CC-195191280098--


From nobody Wed Jan 27 16:16:50 2021
Return-Path: <fgont@si6networks.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 C78E23A0E21; Wed, 27 Jan 2021 16:16:43 -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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, 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 xvKSZtihpz7F; Wed, 27 Jan 2021 16:16:40 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38FB83A0E1D; Wed, 27 Jan 2021 16:16:23 -0800 (PST)
Received: from [IPv6:2800:810:464:2b9:69a9:e23f:a699:f848] (unknown [IPv6:2800:810:464:2b9:69a9:e23f:a699:f848]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 74DF228395A; Thu, 28 Jan 2021 00:16:19 +0000 (UTC)
To: =?UTF-8?Q?=c3=89ric_Vyncke?= <evyncke@cisco.com>, The IESG <iesg@ietf.org>
Cc: draft-ietf-v6ops-cpe-slaac-renum@ietf.org, v6ops-chairs@ietf.org, v6ops@ietf.org, Owen DeLong <owen@delong.com>, suresh@kaloom.com, jiangsheng@huawei.com
References: <160336543195.21161.17851078775777074492@ietfa.amsl.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <bae28190-9537-fed0-be43-9d1e1344c9b9@si6networks.com>
Date: Wed, 27 Jan 2021 21:15:47 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <160336543195.21161.17851078775777074492@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/52C9nlWVPfVqyKgf6Hq5Ef_IW5c>
Subject: Re: [v6ops]  =?utf-8?q?=C3=89ric_Vyncke=27s_Discuss_on_draft-ietf-v6o?= =?utf-8?q?ps-cpe-slaac-renum-05=3A_=28with_DISCUSS_and_COMMENT=29?=
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 00:16:44 -0000

Hi, Eric,

It seems that I somehow failed to respond to your message in time. My 
apologies for that. IN-line....

On 22/10/20 08:17, Éric Vyncke via Datatracker wrote:
[...]
> -- Abstract --
> I wonder why the word "IPv6" is never mentioned in the abstract while the whole
> document is about IPv6. OTOH, perhaps the default IP version in 2020 is indeed
> IPv6 ;-)

I've know included it :-)



> -- Section 3 --
> Should the L-13 of RFC 7084 be also updated ? Briefly discussed in section 3.3

Good grief. My take is that requirement L-13 is replaced with what's 
requirement L-17 in our document.

So, maybe in Section 3 we should say:

"Requirement L-13 from RFC7084 is replaced with:

    o  L-13: CE routers MUST signal stale configuration information as
       specified in Section 3.3.

And the renumber (! :-) ) our list, so the current L-18 becomes L-17?



> I wonder what is the actual structure of this section? There are 4 L-XX
> requirements followed by 3 subsections and mapping between L-15 with section
> 3.1 and the same for L-16, L-17 but not for L-18 ?

That's correct. Sections 3.1-3.3 essentially spell out the details for 
reqs L-15-17.

There's no much more to add, but, for the sake of consistency we could 
add a short Section 3.4 with something like:

---- cut here ----
3.4. Automatic DHCPv6 RELEASEs

Some CE Routers are known to automatically CE send DHCPv6-PD RELEASE 
messages upon reboot events. However, this may inadvertently trigger a 
flash-renumbering scenario, along with the associated problems discussed 
in [draft-ietf-v6ops-slaac-renum], that this document tries to mitigate.

As a result, L-18 specifies that CE routers SHOULD NOT automatically 
send DHCPv6-PD RELEASE messages upon reboot events.
---- cut here ----

?


> As noted in section 3.1, L-13 is actually Section 6.3 of [RFC8415] that is
> standard track

How about changing:
       *  The recommendations in this section expand from requirement
          L-13 in Section 4.3 of [RFC7084].

to

       *  The recommendations in this section expand from requirement
          L-13 in Section 4.3 of [RFC7084] and Section 6.3 of [RFC8415].

?



> 
> -- Section 3.2 --
> There is a reference to section 2.1 of this document but the authors probably
> meant section 3.1 of this document or Section 6.3 of [RFC8415].

Yep. Good grief! Fixed.




> Should the list of ND options include by default all options ? or at least
> indicate that this is not an exhaustive list to allow for future ND options ?

The thing is that not all options have lifetimes. (TBH, I just looked at 
https://www.iana.org/assignments/icmpv6-parameters/icmpv6-parameters.xhtml#icmpv6-parameters-5 
, and probably many of them wouldn't even apply).

So I'd leave "as is", or add a parenthetical note right after the second 
paragraph of Section 3.2 that says:

     NOTE:
     We note that the above text refers to the Neighbor Discovery Options
     that may typically be employed by CE Routers. A CE Router may need
     to apply the same policy for setting the lifetime of other Neighbor
     Discovery options it may employ, if and where applicable.

?



> -- Section 3.3 --
> I agree with "IPv6 network renumbering is expected to take place in a planned
> manner," but this sentence seems to contradict the premisses of
> draft-ietf-v6ops-slaac-renum. Unsure how to reconciliate the two I-D (sharing
> some authors ;-) ).

At least in my mental model, the two documents are reconciliated as follows:

"IPv6 network renumbering is expected to take place in a planned manner. 
Now, welcome to the real world" :-)




> " since we acknowledge " suggest to slightly rewrite this sentence to make it
> less personal.

Done.


> Suggestion to mention whether RA are sent only on received RS, multicasted
> immediately (the document mention periodically), or unicasted when possible
> (some CPE keeps the mapping of all its unicast client notably on the Wi-Fi
> side).

That's a good point. I wonder how to do it without getting into too much 
detail that might e.g. override good possible behavior such as the one 
you describe.

I wonder if we should add to this sentence:
"The aforementioned advertisement SHOULD be performed for at least the 
"Valid Lifetime" previously employed for such prefix."

Something like:
"The CE Router MUST advertise this information with unsolicited Router 
Advertisements as described in Section 6.2.4 of [RFC4861]. A CE Router 
MAY advertise this information via unicast Router Advertisement, when 
possible and applicable"

My rationale is that the unsolicted RAs are the catch-all case. Whereas 
the unicasted RAs are desirable.

Thoughts?

Thanks!

Regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan 27 16:43:24 2021
Return-Path: <brian.e.carpenter@gmail.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 AE4173A0E53; Wed, 27 Jan 2021 16:43:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SasnvzJi-Ub0; Wed, 27 Jan 2021 16:43:16 -0800 (PST)
Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 582F83A0E52; Wed, 27 Jan 2021 16:43:15 -0800 (PST)
Received: by mail-lf1-x12b.google.com with SMTP id a8so5304677lfi.8; Wed, 27 Jan 2021 16:43:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=UmLJEWVEON6EsWEiuhqxPAp0ORXgwmOfJhPtW/pnD3Y=; b=iUVxlj53fyEvkLSdq48bWDRIVcwLfag5TSF18Evei4V4vmwGs2LhWYieZw7Cx4SPvu URREXcUcjgMzuX45UzL7cZWWzQgkbmFMaMuVl+GAJY/5RpQflIzhEBBoA4d3+2EfQKRu KAeWVJ/igZHJDD/8+f4HmNF/ztH04aFReF0u5bho6PcV/yN270UlkXBMDx+2SQdujhG9 S9m0AxDQbGTtPsCWb/PrX7FWolXtdB1BTV5m7htN+LlrYW9sE1o6nvyMm+/mqWtL+N8w XspUQwrmsYc/q5GWBl+R5Im8DZeRZLkOImgKnP80JdADSfwhW8E278aDGkIE1kit6ora TCSw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=UmLJEWVEON6EsWEiuhqxPAp0ORXgwmOfJhPtW/pnD3Y=; b=IzgiC2DM31p5FwCdMBgYebixu34Z/VE8neioi3DptU2isN1EZae2S1RQ0IdDQOkn2n sWQETBXD8SnCx5e3VnXFSpKEK1GeKmrdTzZW9O5KYsbtZ/uKBadKirA1GxauALUKTcSU HHxDvhfrZSuSbSGBCXRxUIco3hVt+Qq2i+zRPF26clbMgztFZFaDyJbQ0aTgDtAblMSa if4aSeJloaqhwOm+s5DK+BzeAdbaa6APyc4hOiHqJzoZl1VwkLO+3SQdZGZ+FPdWv7Xl y8LMUHrcCK+wHBcO/SEtwbiQj2XfvOqfk7nZJK30ki0GdWpZLGYqohIBuy1KQ9/0n+Dx 7ARg==
X-Gm-Message-State: AOAM532BIPpKaM97YdeJaycG5z2uwdsVjbPKtOOK+hnu0U9NCLatkWp3 sPXBFk0pjNirn9ziWN4f0vzBKagPjXgxqkWCKHM=
X-Google-Smtp-Source: ABdhPJyQqqp2wc0uIV5mVMqg1oMoJWJvqWfuZJE/3zBe5c6XA6aCg4drs7NMB18ovAUREA8RA1iroSU/KVsrMgxJVeY=
X-Received: by 2002:ac2:55aa:: with SMTP id y10mr2250474lfg.156.1611794592918;  Wed, 27 Jan 2021 16:43:12 -0800 (PST)
MIME-Version: 1.0
References: <160325603610.17357.6914550111489766157@ietfa.amsl.com> <cf025acf-5192-d9a3-a727-8716d9d7b232@si6networks.com> <C68DC427-85A4-4AE7-928A-C92AD2C4488A@fugue.com> <9404f657-dbcb-877d-5a3f-1f3408c3b890@si6networks.com> <30262C9F-D004-4452-9F40-A407D7B396D3@fugue.com> <85f2bc3f-51f5-a5b2-53cd-9b5a52ac227f@si6networks.com>
In-Reply-To: <85f2bc3f-51f5-a5b2-53cd-9b5a52ac227f@si6networks.com>
From: Brian Carpenter <brian.e.carpenter@gmail.com>
Date: Thu, 28 Jan 2021 13:43:01 +1300
Message-ID: <CANMZLAZPWCGOvTbiD04eRrJ6WSZWYObBCiWUiStAKdQD=J6d8w@mail.gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Cc: Ted Lemon <mellon@fugue.com>, V6ops Chairs <v6ops-chairs@ietf.org>, v6ops@ietf.org,  draft-ietf-v6ops-cpe-slaac-renum@ietf.org, Benjamin Kaduk <kaduk@mit.edu>,  The IESG <iesg@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000296e8705b9eb2c33"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/mRF4onSP_11yHH_dM0Kng_b-ywM>
Subject: Re: [v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-cpe-slaac-renum-05: (with COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 00:43:18 -0000

--000000000000296e8705b9eb2c33
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Mentioning Updated & Obsoleted RFCs in the Abstract has been standard
practice for years now. I believe the logic was that although redundant the
warning increases the odds that people will take note.

Regards
    Brian
    (via tiny screen & keyboard)

On Thu, 28 Jan 2021, 11:28 Fernando Gont, <fgont@si6networks.com> wrote:

> On 27/1/21 19:06, Ted Lemon wrote:
> > Oh, you don=E2=80=99t need to say =E2=80=9Cupdates=E2=80=9D in the abst=
ract because that=E2=80=99s in
> > the header.
>
> I added that to the Abstract because I was *asked* to. You see what I
> mean? :-)
>
>
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>
>
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

--000000000000296e8705b9eb2c33
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Mentioning Updated &amp; Obsoleted RFCs in the Abstract h=
as been standard practice for years now. I believe the logic was that altho=
ugh redundant the warning increases the odds that people will take note.<br=
><br><div data-smartmail=3D"gmail_signature">Regards<br>=C2=A0=C2=A0=C2=A0 =
Brian<br>=C2=A0=C2=A0=C2=A0 (via tiny screen &amp; keyboard)</div></div><br=
><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, 2=
8 Jan 2021, 11:28 Fernando Gont, &lt;<a href=3D"mailto:fgont@si6networks.co=
m">fgont@si6networks.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex">On 27/1/21 19:06, Ted Lemon wrote:<br>
&gt; Oh, you don=E2=80=99t need to say =E2=80=9Cupdates=E2=80=9D in the abs=
tract because that=E2=80=99s in <br>
&gt; the header.<br>
<br>
I added that to the Abstract because I was *asked* to. You see what I <br>
mean? :-)<br>
<br>
<br>
-- <br>
Fernando Gont<br>
SI6 Networks<br>
e-mail: <a href=3D"mailto:fgont@si6networks.com" target=3D"_blank" rel=3D"n=
oreferrer">fgont@si6networks.com</a><br>
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org" target=3D"_blank" rel=3D"noreferrer">v6op=
s@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferrer n=
oreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a=
><br>
</blockquote></div>

--000000000000296e8705b9eb2c33--


From nobody Wed Jan 27 17:15:20 2021
Return-Path: <volz@cisco.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 7059A3A0FC0; Wed, 27 Jan 2021 17:15:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.62
X-Spam-Level: 
X-Spam-Status: No, score=-9.62 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=fi/Rmwla; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=bbdonbQi
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 3oWxtVSID1PD; Wed, 27 Jan 2021 17:15:13 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ECD1F3A0FBF; Wed, 27 Jan 2021 17:15:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2428; q=dns/txt; s=iport; t=1611796513; x=1613006113; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=X2INi0o02oq8iU7MU+fq5BhfwMev7jOr5Fg8oDmhB4U=; b=fi/RmwladDhGgR2D/Mc80JDuQz2gpWZ6xtqp7+GqnJ5TjPnd5OnhbQYo wNTB+v+YvCKUwxV5V0oY3HEybuvJNo60IGdGupC0wwQVBlLjUeW3ucLTL b+WlE0oazMfwocMGCLQ/UNoUyAxYHIrweOdu60nm0r0V/RCIXQSozdhTD M=;
X-IPAS-Result: =?us-ascii?q?A0CwAAAkDhJg/4UNJK1iHQEBAQEJARIBBQUBQIE8BwELA?= =?us-ascii?q?YFSUQeBUS8vCoQ2g0gDjhQDmRmBLoElA1QLAQEBDQEBLQIEAQGESgIXgV8CJ?= =?us-ascii?q?TUIDgIDAQEBAwIDAQEBAQUBAQECAQYEcYVhDIVzAQEBAQIBIxEMAQE3AQQLA?= =?us-ascii?q?gEIDgoCAiYCAgIwFRACBA4FgyaCVgMOIAGpKQKKJXaBMoMFAQEGhQoYghIJg?= =?us-ascii?q?Q4qAYJ2hAWGQiYbggCBOByCVj6EJoMxNIIsgVlzZoErgRIUAwMtGpJmP6U0C?= =?us-ascii?q?oJ2m3IDH6J7jyqiHoQ2AgQCBAUCDgEBBoFYATeBV3AVZQGCPlAXAg2OITeDO?= =?us-ascii?q?opYdDcCBgEJAQEDCXyKCAGBEAEB?=
IronPort-PHdr: =?us-ascii?q?9a23=3A+pDDLBGsvnzCUK4Fo3yT2p1GYnJ96bzpIg4Y7I?= =?us-ascii?q?YmgLtSc6Oluo7vJ1Hb+e401QebWITHrf9Ilrmev6PhXDkG5pCM+DAHfYdXXh?= =?us-ascii?q?AIwcMRg0Q7AcGDBEG6SZyibyEzEMlYElMw+Xa9PBtQGdq4alHP8TW+6DcIEU?= =?us-ascii?q?D5Mgx4bu3+Bo/ViZGx0Oa/s53eaglFnnyze7R3eR63tg7W8MIRhNhv?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.79,381,1602547200"; d="scan'208";a="634214053"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 28 Jan 2021 01:15:11 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by alln-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id 10S1F1Oa028518 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 28 Jan 2021 01:15:11 GMT
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 27 Jan 2021 19:15:07 -0600
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 27 Jan 2021 19:15:07 -0600
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Wed, 27 Jan 2021 20:15:06 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=odgVzwXh8VMxiSrr1cGxAEE1XsG5+wbN1bRXkn9JqYiFuewBddfz13z+I1O9zYCkjL4fAU83dd251aloZwPYwJdSn0keulFWdqPjhTniF3IvGvCEZTMYqrwjzkklyLkkW8IZ0GvAhTPtjdtBJxhg289w1nwHf1I1P73Z+ke8wOnCc/MOWVz3+INzhmqk3Gj4MTnSZ4HqSvFIEn5Ht/gWuKXvsXuE92Dw+uJ310w6dpcVhAypVdbizF83LsjLxh767oCL0R3j48+ErbT607HgBnxO66qoRp34IfJiwX3EuD8tTJqvK7KbUICbBD+Ua0XtmQaRhSO6+X0aBvJjvjMxwA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=X2INi0o02oq8iU7MU+fq5BhfwMev7jOr5Fg8oDmhB4U=; b=gIjlWaZ+hx/EUO6cNYQGRIu53SORGFC9TuM+uQJaNuWTohDWmTO6EW3bpwKzwVC+SwGtHpx7M1ryaLtykjHv214WYv5AluLRAH0EF+XK9k6PO3gzla2zRLTOYeA8NgTJd1LpYy7WGRCRnpRtmqe7YwstfL0OPX/wJ6mcO5amwmXkTmL8Hb8CqJDAuhuoT327u+40zzburNxw5HFCD1vIcOj3LafNGh/o+VUfVT8a3jWdGNOPNK6QDkMg3F9vCFFjw+NaU6DpzYMiv5xv0WpUvCDcQGOH8pBFED2VUHZ4V2MgbA/nJg2CNP1FQncufO7dti6NBWge0MYSAS2aCqbZwA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com;  s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=X2INi0o02oq8iU7MU+fq5BhfwMev7jOr5Fg8oDmhB4U=; b=bbdonbQiJLtijbhEgFQjmNC5h7sxfmtb16w8g5EGLoLVg1yIQU8HMX3PtiLvxZtVHY+HJBnqm8vyzfuP7yWF/mMtdHxyYllkcs0sOQHBRCKS1EOdwQzGSEEAkh5JnzLXlxVZrt/L7zCP268GxER5oQD2mbOD9zdJzvDQ31NfxLw=
Received: from BN7PR11MB2547.namprd11.prod.outlook.com (2603:10b6:406:af::18) by BN6PR11MB1234.namprd11.prod.outlook.com (2603:10b6:404:47::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3784.15; Thu, 28 Jan 2021 01:15:05 +0000
Received: from BN7PR11MB2547.namprd11.prod.outlook.com ([fe80::651c:70ca:fdc4:25eb]) by BN7PR11MB2547.namprd11.prod.outlook.com ([fe80::651c:70ca:fdc4:25eb%3]) with mapi id 15.20.3784.019; Thu, 28 Jan 2021 01:15:05 +0000
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Fernando Gont <fgont@si6networks.com>
CC: Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>, "draft-ietf-v6ops-cpe-slaac-renum@ietf.org" <draft-ietf-v6ops-cpe-slaac-renum@ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, Owen DeLong <owen@delong.com>
Thread-Topic: Benjamin Kaduk's No Objection on draft-ietf-v6ops-cpe-slaac-renum-05: (with COMMENT)
Thread-Index: AQHWp2YzWvQ6kbuC70ySnGuTJbb1bao8lfUAgAAYdICAACjPbg==
Date: Thu, 28 Jan 2021 01:15:05 +0000
Message-ID: <011245F3-558B-4F9D-97E5-56BBEE0419D2@cisco.com>
References: <160325603610.17357.6914550111489766157@ietfa.amsl.com> <cf025acf-5192-d9a3-a727-8716d9d7b232@si6networks.com>, <4fbc24c6-ef7b-5a99-3d04-69e6c9c3c90a@si6networks.com>
In-Reply-To: <4fbc24c6-ef7b-5a99-3d04-69e6c9c3c90a@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: mit.edu; dkim=none (message not signed) header.d=none;mit.edu; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [24.233.121.124]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: bae182e6-b5ff-46f2-8f59-08d8c32a2536
x-ms-traffictypediagnostic: BN6PR11MB1234:
x-microsoft-antispam-prvs: <BN6PR11MB1234265C61BFF0E527F0086BCFBA9@BN6PR11MB1234.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: f9w8pJR0+/vXHITeri6aKQ7hrvginOV6c4LZREFP04m+GEiLGrVol1T7ujMuIy8z/BdlHpO/xxb5R54oC0VngH0ZAdVhCclAnAxfocpUx8nuEYHjmTMsxvKdJOfXk8VwK7m8lohVFNAO+TUw4JslbrBD6e6zUH93hKJNoUCiSQxXDnHEExYllnoZDn4Y346j8SCg+/b1k07Gs09sk4wBJaMMaOdy0zSZ7iN/ec32LLcz3Bat1geIREBspFXDfj71GAbXYRYQgBb3H+P1l+QaBqN2VK5GNqF+TKU15JWs+P6v4FJR3w5KfavRsadpxl95LQpu09ggWg3NmrBgKHfbtsdKn5lwySvGr45YZC0QRUVX+0F1zl6iAHb0y7o07wvku8G3il9+HIuawv4z/NrEB9qvuxipOsbqZaRmXjde8uJ5F/9+pCjaxaC+s8aGp6/g6DG4ZR2um1d6P8Ituw3rcbGysjJF9gGNknpm1zZ9jq9zKIO1tYa8iMkGnHBd7tzUxHl9rTrFt6N3PIn02GBqjv0FtNjur0aSLb1lmUBHWF94/Myshukp39gClNeLS3z6
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:BN7PR11MB2547.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(136003)(376002)(366004)(396003)(346002)(39860400002)(6916009)(316002)(26005)(83380400001)(36756003)(6486002)(6506007)(86362001)(8936002)(71200400001)(91956017)(5660300002)(66556008)(54906003)(33656002)(2616005)(186003)(66446008)(6512007)(53546011)(66476007)(64756008)(2906002)(4326008)(76116006)(66946007)(8676002)(478600001)(45980500001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?VnFlVGYwd1pGcmpremg5eklxekFteEU4UnhwOUcveTBETzZxK3c4ZEFOYXRj?= =?utf-8?B?aUNIVUZYYmt5YlBIWTFvV2dITXVmOUx2L0hDYkxoVzZXT3FTdHJQc05QS1d6?= =?utf-8?B?U0JpdHF1bEkrSS9YK2xNVWhFeDc0TWREYnBocXNiQWhyckJReWpiSTRQbEtl?= =?utf-8?B?a21QRHFOTG9wY2hlcTZtYldlbFNFckE2U2JXRFluL0NHZG4vWDduaEhRZysv?= =?utf-8?B?ck1wZGQ3M2tGWGJ5NjhNT1Y2blNGRUl0NWc3RkxER2czemxEb21jck5YbnQ5?= =?utf-8?B?VDJqcUJKcmVTRXBQNGt2Q0NnYmZPS2pzZlBCYWQvNG5VZCtaVG5HUUM3SVVl?= =?utf-8?B?SzdxdXRiZEZJWCtjMW84Z1YxUi9DU2RVdFFhZ2hCS3NsVmFabzd1QnZ3SkFz?= =?utf-8?B?VDNqT3MzQjRqUmlEYnRJb2VselM2eVMzUWRQSmlPMVBnN0RPcDNYU1RVajJT?= =?utf-8?B?Tzl1Y1NJa0FlTCttTzFCS3VSTmhnMVdpbzI0MlRyd1ZkOU9SZTZ5NEZDZzJI?= =?utf-8?B?T1hLN2E1QmdvdVMrTmpvWkJnRkxyWFB0Z2xiaFpPdE5xNWFtTVlLSDhrZWRW?= =?utf-8?B?eWdNZ2d6Rk5QWnhnWmdLUi9nb3lwcWgxWXkvYmthMEE2QnpLRjVPWmNKUGxz?= =?utf-8?B?UHJoZEkrR1g1K0l6Wk9GTDQxNmdjcmxRZjVXeTZTT2VIdm5yNHdBNXVKTTdD?= =?utf-8?B?V3JGcGovMGZJZVdYWFpUaGQ4VVZYd1R4RTdHejlqZ1JKcWJKT3crM1J4RDl2?= =?utf-8?B?YTVYTFNqamtkc2xzMnZhRnFQRVZVcC83RGEyRmZlYkUyeDZ3MHRyU05IYzFJ?= =?utf-8?B?ZDBqSkV3RVd6NFBWaVE5cE5jNVF5dTVaY0RzdzFrSDJSN3FQTnNRMS9nTG9q?= =?utf-8?B?TUJ0cEhYQXBSak5tK0EybE41V0FyU2J2eGViYmYxdktpam1jVWVlb2REV0h5?= =?utf-8?B?bjFSZzhqZzMyZVdDYmpGd3NnY1dmYXEyRVJKUDVZK2N4WVBlcG5HeVhkcGRE?= =?utf-8?B?ZmFKenQ2Tyt1Y3pmTWpTTVhwTktiZDRHTmRDVmRkOEorMTRyRlU3aXNERUY5?= =?utf-8?B?akpDSGZ6RWxIS1lTUURMWko4VDZXUWh4VFFvZi9tYkVoMW5MeUtwRElndzhW?= =?utf-8?B?dExVd1pFWUszL0NXem9KWUczQ203eXNhOEdubSt6QWcyVVp0WHVpRXllUXo0?= =?utf-8?B?NkdiY0tWMVFSTjdSWWZkcUFTZ04wbWpEUHN5eWlaaGR0Z2VzNUlWN1pZWXBh?= =?utf-8?B?b0pKR1FoYnpkMTFjZ0RNMkR6VXFwWmhJZk8ycnRLWmhsdEFTZmhaU3ZtSWtk?= =?utf-8?B?dnROcXFFK3UvRXJFUHIxR2gxS3pNUFYyaFcxWkQwUG52dEIwZWRRbEZsR2pD?= =?utf-8?B?Qjk0YjdaQjNUOElyRFY2azhpY1lzZlJMSDlRM09LN052V1FMRS9vYjk5SENl?= =?utf-8?Q?51cUTc3V?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BN7PR11MB2547.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: bae182e6-b5ff-46f2-8f59-08d8c32a2536
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Jan 2021 01:15:05.2101 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: vPXwSAbrSipY1xTizv4sPqJq+dyS1ZBTvjUpuSvtBvNkZgToK2XMScz2KzurllTQ
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR11MB1234
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.15, xch-rcd-005.cisco.com
X-Outbound-Node: alln-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/dqPdgzgtctNgYP9l3-XVPaBu4I4>
Subject: Re: [v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-cpe-slaac-renum-05: (with COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 01:15:16 -0000

U2VlIGNvbW1lbnRzIGJlbG93IChCVj4pLg0KDQotIEJlcm5pZSAoZnJvbSBpUGFkKQ0KDQo+IE9u
IEphbiAyNywgMjAyMSwgYXQgNTo1MyBQTSwgRmVybmFuZG8gR29udCA8ZmdvbnRAc2k2bmV0d29y
a3MuY29tPiB3cm90ZToNCj4gDQo+IO+7v0hpLCBCZW4sDQo+IA0KPiBPbiAyNy8xLzIxIDE4OjIx
LCBGZXJuYW5kbyBHb250IHdyb3RlOg0KPiBbLi4uLl0NCj4+PiAgICAgICAgKiAgSW4gUmVwbGll
cyB0byBESENQdjYgUmVxdWVzdCwgUmVuZXcsIFJlYmluZCBtZXNzYWdlcywgc2VuZCAwDQo+Pj4g
ICAgICAgICAgIGxpZmV0aW1lcyBmb3IgYW55IGFkZHJlc3MgYXNzaWdubWVudHMgb3IgcHJlZml4
IGRlbGVnYXRpb25zIGZvcg0KPj4+ICAgICAgICAgICB0aGUgZGVwcmVjYXRlZCBwcmVmaXhlcyBm
b3IgYXQgbGVhc3QgdGhlIHZhbGlkLWxpZmV0aW1lDQo+Pj4gICAgICAgICAgIHByZXZpb3VzbHkg
ZW1wbG95ZWQgZm9yIHRoZW0sIG9yIGZvciBhIHBlcmlvZCBvZiBORF9WQUxJRF9MSU1JVA0KPj4+
ICAgICAgICAgICBpZiB0aGUgcmVjb21tZW5kZWQgbGlmZXRpbWVzIGZyb20gU2VjdGlvbiAzLjIg
YXJlIGVtcGxveWVkLg0KPj4+IA0KPj4+IElzIGl0IGRlbGliZXJhdGUgdG8gc2F5IG5vdGhpbmcg
YXQgYWxsIGFib3V0IEFkdmVydGlzZSBtZXNzYWdlcyAod2hpY2gNCj4+PiBhcmUgc2VudCBpbiBy
ZXNwb25zZSB0byBTb2xpY2l0IG1lc3NhZ2VzLCBub3QgYW55IG9mIHRoZSBsaXN0ZWQgb25lcyk/
DQo+PiBJIHdpbGwgZG91YmxlLWNoZWNrIHRoaXMgb25lIHdpdGggbXkgY28tYXV0aG9ycy4NCj4g
DQo+IE91ciBwbGFuIGlzIHRvIGFkZCB0aGlzIG5vdGUgdG8gdGhlIFJBVElPTkFMRSBvZiBTZWN0
aW9uIDMuMzoNCj4gDQo+ICAgVGhlIGFib3ZlIHRleHQgZG9lcyBub3QgaW5jbHVkZSByZXNwb25z
ZXMgdG8gREhDUHY2IFNvbGljaXQgbWVzc2FnZXMsDQpCVj4gQSBTb2xpY2l0IHdpdGggUmFwaWQg
Q29tbWl0IG1heSByZXR1cm4gYSBSZXBseS4gU28gdGhpcyBvbmx5IGFwcGxpZXMgdG8gQWR2ZXJ0
aXNlIHJlc3BvbnNlcy4NCj4gICBzaW5jZSBTZWN0aW9uIDE4LjMuOSBvZiBSRkM4NDE1IHJlcXVp
cmVzIHRoYXQgYSBESENQdjYgc2VydmVyDQo+ICAgdGhhdCBpcyBub3QgZ29pbmcgdG8gYXNzaWdu
IGFuIGFkZHJlc3Mgb3IgZGVsZWdhdGVkIHByZWZpeCByZWNlaXZlZA0KPiAgIGFzIGEgaGludCBp
biB0aGUgU29saWNpdCBtZXNzYWdlIE1VU1QgTk9UIGluY2x1ZGUgdGhhdCBhZGRyZXNzIG9yDQo+
ICAgZGVsZWdhdGVkIHByZWZpeCBpbiB0aGUgQWR2ZXJ0aXNlIG1lc3NhZ2UuIEFkZGl0aW9uYWxs
eSwgYW55DQo+ICAgc3Vic2VxdWVudCBTb2xpY2l0IG1lc3NhZ2VzIHdpbGwgdHJpZ2dlciB0aGUg
cmVzcG9uc2Ugc3BlY2lmaWVkIGluDQpCVj4gVGhlcmUgYXJlIHVzdWFsbHkgbm8g4oCcc3Vic2Vx
dWVudOKAnSBTb2xpY2l0cy4gVGhlcmUgaXMgYSBzdWJzZXF1ZW50IFJlcXVlc3QuDQo+ICAgdGhp
cyBzZWN0aW9uLCBhbmQgdGhlcmVmb3JlIGNhdXNlIHRoZSBhZGRyZXNzIG9yIHByZWZpeCB0byBi
ZQ0KPiAgIGRlcHJlY2F0ZWQuDQo+IA0KPiBXb3VsZCB0aGlzIGFkZHJlc3MgeW91ciBjb21tZW50
Pw0KPiANCj4gVGhhbmtzLA0KPiAtLSANCj4gRmVybmFuZG8gR29udA0KPiBTSTYgTmV0d29ya3MN
Cj4gZS1tYWlsOiBmZ29udEBzaTZuZXR3b3Jrcy5jb20NCj4gUEdQIEZpbmdlcnByaW50OiA2NjY2
IDMxQzYgRDQ4NCA2M0IyIDhGQjEgRTNDNCBBRTI1IDBENTUgMUQ0RSA3NDkyDQo+IA0KPiANCj4g
DQo+IA0K


From nobody Wed Jan 27 17:20:21 2021
Return-Path: <fgont@si6networks.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 5A6CF3A0FC2; Wed, 27 Jan 2021 17:20:16 -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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, 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 RRn0gswQz8-Q; Wed, 27 Jan 2021 17:20:13 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DB953A0E5A; Wed, 27 Jan 2021 17:20:10 -0800 (PST)
Received: from [IPv6:2800:810:464:2b9:69a9:e23f:a699:f848] (unknown [IPv6:2800:810:464:2b9:69a9:e23f:a699:f848]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id C5014280322; Thu, 28 Jan 2021 01:20:04 +0000 (UTC)
To: Erik Kline <ek.ietf@gmail.com>, Ted Lemon <mellon@fugue.com>
Cc: The IESG <iesg@ietf.org>, V6Ops Chairs <v6ops-chairs@ietf.org>, v6ops list <v6ops@ietf.org>, draft-ietf-v6ops-cpe-slaac-renum@ietf.org
References: <160334506239.20395.15102292380884503313@ietfa.amsl.com> <34783E29-F267-4A58-9C3E-5CC2C0D93B49@fugue.com> <CAMGpriWuqzpTn_YU0n6-ZU2ByBUNi_JgycdQzWk8WUqP1qPRaw@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <2252881e-c6a0-961b-22bb-7b86ff6c6d03@si6networks.com>
Date: Wed, 27 Jan 2021 22:17:57 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CAMGpriWuqzpTn_YU0n6-ZU2ByBUNi_JgycdQzWk8WUqP1qPRaw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/VipngR0ZYoxx23WhFr0rEJMLFl0>
Subject: Re: [v6ops] Erik Kline's Discuss on draft-ietf-v6ops-cpe-slaac-renum-05: (with DISCUSS and COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 01:20:17 -0000

Hi, Erik,

This one remained unresponded. Apologies for that.

On 22/10/20 11:28, Erik Kline wrote:
> I agree.  I just think then the text about "the lesser of two lifetime
> values" doesn't quite read correctly nor give the impression that this
> applies to things like ULA prefixes.  I think it's probably pretty
> easy to fix with minimal text.

What you say does indeed make sense.

How about this:

After this para in Section 3.1:
    CE Routers providing stateful address configuration via DHCPv6 SHOULD
    set the DHCPv6 IA Address Option preferred-lifetime to the lesser of
    the remaining preferred lifetime and ND_PREFERRED_LIMIT, and the
    valid-lifetime of the same option to the lesser of the remaining
    valid lifetime and ND_VALID_LIMIT.

Add (as a parenthetical note?) the following text:

    If the prefix employed for DHCPv6 stateful address configuration
    has been locally-generated (e.g., a locally-generated ULA prefix)
    or manually-configured on the CE router,
    the preferred-lifetime and the valid-lifetime of the
    corresponding DHCPv6 IA Address Option SHOULD be set to
    ND_PREFERRED_LIMIT, and ND_VALID_LIMIT, respectively.


Then, right after this para:
    CE Routers providing DHCPv6-PD on the LAN-side SHOULD set the DHCPv6
    IA Prefix Option preferred-lifetime to the lesser of the remaining
    preferred lifetime and ND_PREFERRED_LIMIT, and the valid-lifetime of
    the same option to the lesser of the remaining valid lifetime and
    ND_VALID_LIMIT.


Add this text (parenthetical note or main text?):
    If the prefix employed for DHCPv6-PD
    has been locally-generated  (e.g., a locally-generated ULA prefix)
    or manually-configured on the CE router,
    the preferred-lifetime and the valid-lifetime of the
    corresponding DHCPv6 IA Address Option SHOULD be set to
    ND_PREFERRED_LIMIT, and ND_VALID_LIMIT, respectively.

?


Since this resulting value is then used throughout Section 3.2, I wonder if:

* We can assume that it is clear what we mean by e.g. "lesser of
    the remaining preferred lifetime", or,

* Whether we should coin some term for the values resulting from Section 
3.1 (e.g. "effective preferred-lifetime" and "effective valid-lifetime", 
or something like ND_PREFERRED, and ND_VALID), and then use that 
throught Section 3.2.

Thoughts?

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan 27 18:10:39 2021
Return-Path: <fgont@si6networks.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 C6F533A1107; Wed, 27 Jan 2021 18:10:32 -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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, 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 kkMbSfvgoW4C; Wed, 27 Jan 2021 18:10:30 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D236E3A1103; Wed, 27 Jan 2021 18:10:28 -0800 (PST)
Received: from [IPv6:2800:810:464:2b9:69a9:e23f:a699:f848] (unknown [IPv6:2800:810:464:2b9:69a9:e23f:a699:f848]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 705E9280474; Thu, 28 Jan 2021 02:10:24 +0000 (UTC)
To: Erik Kline <ek.ietf@gmail.com>, The IESG <iesg@ietf.org>
Cc: draft-ietf-v6ops-cpe-slaac-renum@ietf.org, v6ops-chairs@ietf.org, v6ops@ietf.org, Owen DeLong <owen@delong.com>
References: <160334506239.20395.15102292380884503313@ietfa.amsl.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <2c297a30-73e3-1a36-0add-5e1204c9ff32@si6networks.com>
Date: Wed, 27 Jan 2021 23:10:09 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <160334506239.20395.15102292380884503313@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/d5rU-50aTvzoddLV6mb9foNbmao>
Subject: Re: [v6ops] Erik Kline's Discuss on draft-ietf-v6ops-cpe-slaac-renum-05: (with DISCUSS and COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 02:10:33 -0000

Hi, Erik,

In-line...

On 22/10/20 02:37, Erik Kline via Datatracker wrote:
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> [ section 3.2 ]
> 
> * I absolutely agree in principle at these other lifetimes should be updated
>    to the shorter of the two applicable lifetimes, but I'm worried that this
>    text is not sufficiently precise.  Specifically, this recommendation only
>    applies to options that depend in any way on the change in the delegated
>    prefix, yes?  Perhaps just this qualifier is sufficient?

How about tweaking the first paragraph of Section 3.2 as:

   CE Routers SHOULD override the default lifetime values of Neighbor 
Discovery options that depend in any way on the change delegated prefix, 
and employ shorter lifetime values to improve the robustness to 
renumbering events, while complying with the requirements from Section 
2.1 of this document and the recommendations in [RFC7772].

?

I wonder if we should s/delegated prefix/prefix employed for automatic 
address configuration/ . i.e., you don't want e.g. a default pio valid 
lifetime of 1 month, even if you have e.g. configured the prefix 
manually. Otherwise, if the CPE crashes and is replaced with a different 
box, the associated information will lying around forever.



>    For example, none of these comparative lifetime recommendations apply to
>    a stable ULA for a router that meets requirements ULA-[1..5] and chooses
>    to advertise a ULA /48 RIO and maybe even a ULA DNS server, I think.
> 
>    That being said, should this document also be saying that the ULA-derived
>    options SHOULD prefer the ND_{P,V}_LIMIT lifetime values, in case a reboot
>    causes a new ULA to be generated (i.e. the one supposedly in stable storage
>    is lost or otherwise unrecoverable)?

Indeed. FWIW, I've moved the discussion of this topic to a separate 
email (which I posted in the subthread where you discssed this with Ted).




> 
> [ section 3.1 ]
 >
> * With respect to the second bullet: the lifetimes need to be dynamically
>    *updateable*, not necessarily updated if, for example, the ND_{P,V}_LIMIT
>    values are always lower than the remaining PD lifetimes.  In this situation,
>    the requirement is still that the lifetimes can be updated, but to the
>    casual observer of the steady state the RA contents might appear static
>    (e.g., while the PD'd prefix is continuously renewed).
> 
>    Maybe there's no text required here, but I didn't want a reader to be left
>    with the impression that no two RAs could be identical

How about adding, at the end of the bullet:

In scenarios where the  valid-lifetime and the preferred-lifetime of the 
prefix leased via DHCPv6 on the WAN-side are always lower than 
ND_VALID_LIMIT and ND_PREFERRED_LIMIT, respectively, the lifetime values 
advertised on the LAN-side will see no changes during the lifetime of 
said prefix.

....or the like?



> [[ nits ]]
> 
> [ section 3.3 ]
> 
> * In the 2nd bullet's 2nd bullet (this might be easier if these lists were
>    numbered),

Change both lists (innet an outter) to numbered lists?


> it might be good to clarify that "the *deprecated* prefix can
>    simply be advertised..."

Done.

Thanks!

Regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan 27 18:10:43 2021
Return-Path: <fgont@si6networks.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 1BB663A1113; Wed, 27 Jan 2021 18:10:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, 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 xDA-GRm7DR0N; Wed, 27 Jan 2021 18:10:32 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F55F3A1106; Wed, 27 Jan 2021 18:10:27 -0800 (PST)
Received: from [IPv6:2800:810:464:2b9:69a9:e23f:a699:f848] (unknown [IPv6:2800:810:464:2b9:69a9:e23f:a699:f848]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 23236280407; Thu, 28 Jan 2021 02:10:18 +0000 (UTC)
To: "Bernie Volz (volz)" <volz@cisco.com>
Cc: Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>, "draft-ietf-v6ops-cpe-slaac-renum@ietf.org" <draft-ietf-v6ops-cpe-slaac-renum@ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, Owen DeLong <owen@delong.com>
References: <160325603610.17357.6914550111489766157@ietfa.amsl.com> <cf025acf-5192-d9a3-a727-8716d9d7b232@si6networks.com> <4fbc24c6-ef7b-5a99-3d04-69e6c9c3c90a@si6networks.com> <011245F3-558B-4F9D-97E5-56BBEE0419D2@cisco.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <b9c1e036-399c-e7d4-d46d-ef2f29530e00@si6networks.com>
Date: Wed, 27 Jan 2021 22:32:54 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <011245F3-558B-4F9D-97E5-56BBEE0419D2@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/EP6gWWPm6iniDjIO0GmxJWmNZPY>
Subject: Re: [v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-cpe-slaac-renum-05: (with COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 02:10:37 -0000

On 27/1/21 22:15, Bernie Volz (volz) wrote:
> See comments below (BV>).
> 
> - Bernie (from iPad)
> 
>> On Jan 27, 2021, at 5:53 PM, Fernando Gont <fgont@si6networks.com> wrote:
>>
>> ﻿Hi, Ben,
>>
>> On 27/1/21 18:21, Fernando Gont wrote:
>> [....]
>>>>         *  In Replies to DHCPv6 Request, Renew, Rebind messages, send 0
>>>>            lifetimes for any address assignments or prefix delegations for
>>>>            the deprecated prefixes for at least the valid-lifetime
>>>>            previously employed for them, or for a period of ND_VALID_LIMIT
>>>>            if the recommended lifetimes from Section 3.2 are employed.
>>>>
>>>> Is it deliberate to say nothing at all about Advertise messages (which
>>>> are sent in response to Solicit messages, not any of the listed ones)?
>>> I will double-check this one with my co-authors.
>>
>> Our plan is to add this note to the RATIONALE of Section 3.3:
>>
>>    The above text does not include responses to DHCPv6 Solicit messages,
> BV> A Solicit with Rapid Commit may return a Reply. So this only applies to Advertise responses.

Will fix this. Thanks!


>>    since Section 18.3.9 of RFC8415 requires that a DHCPv6 server
>>    that is not going to assign an address or delegated prefix received
>>    as a hint in the Solicit message MUST NOT include that address or
>>    delegated prefix in the Advertise message. Additionally, any
>>    subsequent Solicit messages will trigger the response specified in
> BV> There are usually no “subsequent” Solicits. There is a subsequent Request.

Oops. That was just me both sloppy and sleepy..

The resulting text is:
    The above text does not include DHCPv6 Advertise messages sent in
    response to DHCPv6 Solicit messages, since Section 18.3.9 of
    [RFC8415] requires that a DHCPv6 server
    that is not going to assign an address or delegated prefix received
    as a hint in the Solicit message MUST NOT include that address or
    delegated prefix in the Advertise message. Additionally, any
    subsequent Request messages will trigger the response specified in
    this section, and therefore cause the address or prefix to be
    deprecated.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan 27 22:34:14 2021
Return-Path: <kaduk@mit.edu>
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 409333A12F1; Wed, 27 Jan 2021 22:34:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level: 
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-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 ow7Q3ZrP0gPQ; Wed, 27 Jan 2021 22:34:05 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31C333A12E9; Wed, 27 Jan 2021 22:34:04 -0800 (PST)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 10S6XsNO029000 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 28 Jan 2021 01:34:01 -0500
Date: Wed, 27 Jan 2021 22:33:54 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: Fernando Gont <fgont@si6networks.com>
Cc: The IESG <iesg@ietf.org>, v6ops-chairs@ietf.org, v6ops@ietf.org, draft-ietf-v6ops-cpe-slaac-renum@ietf.org
Message-ID: <20210128063354.GS21@kduck.mit.edu>
References: <160325603610.17357.6914550111489766157@ietfa.amsl.com> <cf025acf-5192-d9a3-a727-8716d9d7b232@si6networks.com> <C68DC427-85A4-4AE7-928A-C92AD2C4488A@fugue.com> <20210127222250.GN21@kduck.mit.edu> <b277f085-eb94-60be-0228-c89dd6a09800@si6networks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <b277f085-eb94-60be-0228-c89dd6a09800@si6networks.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/8CPLa0zj8BlPOXjxLkmpxeb5i6Y>
Subject: Re: [v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-cpe-slaac-renum-05: (with COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 06:34:08 -0000

Hi Fernando,

Assuming you're interested in my opinion...

On Wed, Jan 27, 2021 at 07:51:46PM -0300, Fernando Gont wrote:
> On 27/1/21 19:22, Benjamin Kaduk wrote:
> [...]
> > 
> > I agree with everything you say, though I think there may have been some
> > miscommunication earlier in the thread.
> > 
> > In particular, I was just trying to say that:
> > I looked at the diff between abstract and introduction, and there were some
> > noteworthy bits and some non-noteworthy bits.  The non-noteworthy bits are
> > the several extra paragrpahs in the introduction, since that's a large part
> > of what the difference between abstract and introduction is supposed to be.
> > 
> > Specifically, the "text that is not appropriate for an abstract" is
> > referring to text that is already (and correctly) in the introduction.  (At
> > least, that's what I thought when I read it the first time; I didn't look
> > at it right now to check.)
> 
> How about this for the Abstract:
> 
> This document specifies improvements to Customer Edge Routers that help 
> mitigate the problems that may arise when network configuration 
> information becomes invalid, without any explicit signaling of that 
> condition to the affected nodes. This document updates RFC7084.
> 
> .. at the end of the day, that's what the document is about.

That looks pretty solid; thanks for iterating to get to it.

> (Note: I wouldn't have added the "This document updates RFC7084", but 
> have been asked to. But won't argue about it either way :-) )

I think Brian covered this part, though I think it is just something I
assimilated as institutional knowledge and I can't point to a reference for
it.

-Ben


From nobody Wed Jan 27 22:38:44 2021
Return-Path: <kaduk@mit.edu>
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 03ABC3A135B; Wed, 27 Jan 2021 22:38:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 IcZI0kfhy7kc; Wed, 27 Jan 2021 22:38:32 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8FBF83A1326; Wed, 27 Jan 2021 22:38:31 -0800 (PST)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 10S6cKbl032227 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 28 Jan 2021 01:38:24 -0500
Date: Wed, 27 Jan 2021 22:38:19 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: Fernando Gont <fgont@si6networks.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-v6ops-cpe-slaac-renum@ietf.org, v6ops-chairs@ietf.org, v6ops@ietf.org, Owen DeLong <owen@delong.com>
Message-ID: <20210128063819.GT21@kduck.mit.edu>
References: <160325603610.17357.6914550111489766157@ietfa.amsl.com> <cf025acf-5192-d9a3-a727-8716d9d7b232@si6networks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <cf025acf-5192-d9a3-a727-8716d9d7b232@si6networks.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/6-62Z7HjS91JE8jf8x6ayYOdndQ>
Subject: Re: [v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-cpe-slaac-renum-05: (with COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 06:38:40 -0000

Hi Fernando,

On Wed, Jan 27, 2021 at 06:21:30PM -0300, Fernando Gont wrote:
> Hi, Ben,
> 
> Just me going through IESG reviews to find if there's anything I had 
> missed. Please see in-line....
> 
> On 21/10/20 01:53, Benjamin Kaduk via Datatracker wrote:
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> > 
> > I am not sure that we should avoid having the conversation about
> > intended status; consider, for example, "CE Routers SHOULD override the
> > default [...] values from [RFC4861]" (RFC 4861 is a Draft Standard).  (The
> > question was raised in the genart review thread by virtue of skew between
> > the datatracker state and the document header, but it looks like the WG chair
> > changed the status in the datatracker and there was no further discussion of
> > the topic on the list.)
> > 
> > The diff between Abstract and Introduction is interesting: there is a
> > parenthetical "(such as when a Customer Edge Router crashes and reboots
> > without knowledge of the previously-employed configuration information)"
> > only in the abstract that might also be useful in the introduction, and
> > the abstract uses 'hosts' where the introduction uses 'nodes'.  (There
> > are a couple other incidental wording differences that the authors might
> > wish to consider normalizing on one wording for, as well as the expected
> > additional text in the introduction that is not appropriate for an
> > abstract.)
> 
> What's the specific "text that is not appropriate for an abstract"?

(As covered downthread, "the stuff that's in the introduction and not
present in the abstract", i.e., is present in the diff but is not
noteworthy.)

[...]
> > Section 8.2
> > 
> > It would feel more natural, at least to me, if RFC 7084 was listed as a
> > normative reference.  (In the sense that we are Updating it to make
> > incremental additions, but you need the whole combined assembly of both
> > documents in order to have a functional setup.)
> 
> I would assume so. But it would be a downref. Is that possible?

Most things are possible ... but with 7084 not listed at
https://datatracker.ietf.org/doc/downref/ it might mean another IETF LC.
Your responsible AD should probably be the one to make the call, and the
"don't change it" option has a fair bit of inertia going for it.

-Ben


From nobody Wed Jan 27 22:54:59 2021
Return-Path: <kaduk@mit.edu>
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 7587A3A1334; Wed, 27 Jan 2021 22:54:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 YQjYV5-6Z0t4; Wed, 27 Jan 2021 22:54:56 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFFF43A1332; Wed, 27 Jan 2021 22:54:55 -0800 (PST)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 10S6siDU011473 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 28 Jan 2021 01:54:49 -0500
Date: Wed, 27 Jan 2021 22:54:44 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: Fernando Gont <fgont@si6networks.com>
Cc: "Bernie Volz (volz)" <volz@cisco.com>, The IESG <iesg@ietf.org>, "draft-ietf-v6ops-cpe-slaac-renum@ietf.org" <draft-ietf-v6ops-cpe-slaac-renum@ietf.org>,  "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, Owen DeLong <owen@delong.com>
Message-ID: <20210128065444.GU21@kduck.mit.edu>
References: <160325603610.17357.6914550111489766157@ietfa.amsl.com> <cf025acf-5192-d9a3-a727-8716d9d7b232@si6networks.com> <4fbc24c6-ef7b-5a99-3d04-69e6c9c3c90a@si6networks.com> <011245F3-558B-4F9D-97E5-56BBEE0419D2@cisco.com> <b9c1e036-399c-e7d4-d46d-ef2f29530e00@si6networks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <b9c1e036-399c-e7d4-d46d-ef2f29530e00@si6networks.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/EaryEUp1TQ48r7V1MMnh1JAY1PY>
Subject: Re: [v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-cpe-slaac-renum-05: (with COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 06:54:58 -0000

Hi Fernando,

On Wed, Jan 27, 2021 at 10:32:54PM -0300, Fernando Gont wrote:
> On 27/1/21 22:15, Bernie Volz (volz) wrote:
> > See comments below (BV>).
> > 
> > - Bernie (from iPad)
> > 
> >> On Jan 27, 2021, at 5:53 PM, Fernando Gont <fgont@si6networks.com> wrote:
> >>
> >> ﻿Hi, Ben,
> >>
> >> On 27/1/21 18:21, Fernando Gont wrote:
> >> [....]
> >>>>         *  In Replies to DHCPv6 Request, Renew, Rebind messages, send 0
> >>>>            lifetimes for any address assignments or prefix delegations for
> >>>>            the deprecated prefixes for at least the valid-lifetime
> >>>>            previously employed for them, or for a period of ND_VALID_LIMIT
> >>>>            if the recommended lifetimes from Section 3.2 are employed.
> >>>>
> >>>> Is it deliberate to say nothing at all about Advertise messages (which
> >>>> are sent in response to Solicit messages, not any of the listed ones)?
> >>> I will double-check this one with my co-authors.
> >>
> >> Our plan is to add this note to the RATIONALE of Section 3.3:
> >>
> >>    The above text does not include responses to DHCPv6 Solicit messages,
> > BV> A Solicit with Rapid Commit may return a Reply. So this only applies to Advertise responses.
> 
> Will fix this. Thanks!
> 
> 
> >>    since Section 18.3.9 of RFC8415 requires that a DHCPv6 server
> >>    that is not going to assign an address or delegated prefix received
> >>    as a hint in the Solicit message MUST NOT include that address or
> >>    delegated prefix in the Advertise message. Additionally, any
> >>    subsequent Solicit messages will trigger the response specified in
> > BV> There are usually no “subsequent” Solicits. There is a subsequent Request.
> 
> Oops. That was just me both sloppy and sleepy..
> 
> The resulting text is:
>     The above text does not include DHCPv6 Advertise messages sent in
>     response to DHCPv6 Solicit messages, since Section 18.3.9 of
>     [RFC8415] requires that a DHCPv6 server
>     that is not going to assign an address or delegated prefix received
>     as a hint in the Solicit message MUST NOT include that address or
>     delegated prefix in the Advertise message. Additionally, any
>     subsequent Request messages will trigger the response specified in
>     this section, and therefore cause the address or prefix to be
>     deprecated.

This definitely addresses my comment, thanks.
Seeing it written out like that does make it seem like it would be a fine
choice to deliberately decide to not say anything about Advertise messages,
since the correct behavior is already required by the combination of what
we do say and the existing specs.  So, please do what you feel is right in
terms of adding this paragraph or leaving it out.

Thank you for working through it with me (and thanks Bernie for helping
out, too)!

-Ben


From nobody Wed Jan 27 23:45:37 2021
Return-Path: <fgont@si6networks.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 8DCC53A1374; Wed, 27 Jan 2021 23:45:27 -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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, 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 hDo3y7mhBmq5; Wed, 27 Jan 2021 23:45:24 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEAE43A1373; Wed, 27 Jan 2021 23:45:13 -0800 (PST)
Received: from [IPv6:2800:810:464:2b9:18e2:60b8:efab:c3f2] (unknown [IPv6:2800:810:464:2b9:18e2:60b8:efab:c3f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 8FED8283A33; Thu, 28 Jan 2021 07:45:00 +0000 (UTC)
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: The IESG <iesg@ietf.org>, v6ops-chairs@ietf.org, v6ops@ietf.org, draft-ietf-v6ops-cpe-slaac-renum@ietf.org
References: <160325603610.17357.6914550111489766157@ietfa.amsl.com> <cf025acf-5192-d9a3-a727-8716d9d7b232@si6networks.com> <C68DC427-85A4-4AE7-928A-C92AD2C4488A@fugue.com> <20210127222250.GN21@kduck.mit.edu> <b277f085-eb94-60be-0228-c89dd6a09800@si6networks.com> <20210128063354.GS21@kduck.mit.edu>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <9943afa1-043f-b734-3532-e1a7dec9b0b1@si6networks.com>
Date: Thu, 28 Jan 2021 04:44:49 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <20210128063354.GS21@kduck.mit.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/wXTnvsi2LNbew9bJFKL4r-PmfT4>
Subject: Re: [v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-cpe-slaac-renum-05: (with COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 07:45:28 -0000

On 28/1/21 03:33, Benjamin Kaduk wrote:
> Hi Fernando,
> 
> Assuming you're interested in my opinion...

I am, indeed :-)  Your reviews do make a difference in helping improve 
the quality of documents! (not just this one!)


[....]
>>> Specifically, the "text that is not appropriate for an abstract" is
>>> referring to text that is already (and correctly) in the introduction.  (At
>>> least, that's what I thought when I read it the first time; I didn't look
>>> at it right now to check.)
>>
>> How about this for the Abstract:
>>
>> This document specifies improvements to Customer Edge Routers that help
>> mitigate the problems that may arise when network configuration
>> information becomes invalid, without any explicit signaling of that
>> condition to the affected nodes. This document updates RFC7084.
>>
>> .. at the end of the day, that's what the document is about.
> 
> That looks pretty solid; thanks for iterating to get to it.

Done!



>> (Note: I wouldn't have added the "This document updates RFC7084", but
>> have been asked to. But won't argue about it either way :-) )
> 
> I think Brian covered this part, though I think it is just something I
> assimilated as institutional knowledge and I can't point to a reference for
> it.

I'm not sure if this would serve as the reference that you wanted, but I 
just found this one: 
https://www.ietf.org/chairs/document-writeups/document-writeup-working-group-documents/

Item 16) seems to ask for it, or explain why that's not the case. :-)

So even if just for that, I'd add it, and save some electrons :-)

-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan 27 23:52:21 2021
Return-Path: <fgont@si6networks.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 13CCB3A1387; Wed, 27 Jan 2021 23:52:14 -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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, 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 ffBL6IR5V22S; Wed, 27 Jan 2021 23:52:12 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4A7D3A1386; Wed, 27 Jan 2021 23:52:11 -0800 (PST)
Received: from [IPv6:2800:810:464:2b9:18e2:60b8:efab:c3f2] (unknown [IPv6:2800:810:464:2b9:18e2:60b8:efab:c3f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id A8E25283A33; Thu, 28 Jan 2021 07:52:07 +0000 (UTC)
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: "Bernie Volz (volz)" <volz@cisco.com>, The IESG <iesg@ietf.org>, "draft-ietf-v6ops-cpe-slaac-renum@ietf.org" <draft-ietf-v6ops-cpe-slaac-renum@ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, Owen DeLong <owen@delong.com>
References: <160325603610.17357.6914550111489766157@ietfa.amsl.com> <cf025acf-5192-d9a3-a727-8716d9d7b232@si6networks.com> <4fbc24c6-ef7b-5a99-3d04-69e6c9c3c90a@si6networks.com> <011245F3-558B-4F9D-97E5-56BBEE0419D2@cisco.com> <b9c1e036-399c-e7d4-d46d-ef2f29530e00@si6networks.com> <20210128065444.GU21@kduck.mit.edu>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <2193784e-1419-a1c2-6935-5153ca16f72d@si6networks.com>
Date: Thu, 28 Jan 2021 04:49:04 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <20210128065444.GU21@kduck.mit.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/V5iY9GW-R39xHC0jWHq5AWlHpK0>
Subject: Re: [v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-cpe-slaac-renum-05: (with COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 07:52:14 -0000

On 28/1/21 03:54, Benjamin Kaduk wrote:
[...]
>> The resulting text is:
>>      The above text does not include DHCPv6 Advertise messages sent in
>>      response to DHCPv6 Solicit messages, since Section 18.3.9 of
>>      [RFC8415] requires that a DHCPv6 server
>>      that is not going to assign an address or delegated prefix received
>>      as a hint in the Solicit message MUST NOT include that address or
>>      delegated prefix in the Advertise message. Additionally, any
>>      subsequent Request messages will trigger the response specified in
>>      this section, and therefore cause the address or prefix to be
>>      deprecated.
> 
> This definitely addresses my comment, thanks.
> Seeing it written out like that does make it seem like it would be a fine
> choice to deliberately decide to not say anything about Advertise messages,
> since the correct behavior is already required by the combination of what
> we do say and the existing specs.  So, please do what you feel is right in
> terms of adding this paragraph or leaving it out.

We can add it to the RATIONALE in that section. If you had that 
question, a reader of our document could possibly also have it. So it 
could be of help.


> Thank you for working through it with me (and thanks Bernie for helping
> out, too)!

Thank you!

Regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Jan 27 23:52:31 2021
Return-Path: <fgont@si6networks.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 6BB623A13C7; Wed, 27 Jan 2021 23:52:20 -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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, 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 XsGj7Po7XLys; Wed, 27 Jan 2021 23:52:16 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B98AE3A138D; Wed, 27 Jan 2021 23:52:16 -0800 (PST)
Received: from [IPv6:2800:810:464:2b9:18e2:60b8:efab:c3f2] (unknown [IPv6:2800:810:464:2b9:18e2:60b8:efab:c3f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 30D83283A41; Thu, 28 Jan 2021 07:52:12 +0000 (UTC)
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: The IESG <iesg@ietf.org>, draft-ietf-v6ops-cpe-slaac-renum@ietf.org, v6ops-chairs@ietf.org, v6ops@ietf.org, Owen DeLong <owen@delong.com>
References: <160325603610.17357.6914550111489766157@ietfa.amsl.com> <cf025acf-5192-d9a3-a727-8716d9d7b232@si6networks.com> <20210128063819.GT21@kduck.mit.edu>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <4f8eb79c-d646-a4cf-4e6e-69226e2643bd@si6networks.com>
Date: Thu, 28 Jan 2021 04:50:30 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <20210128063819.GT21@kduck.mit.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/_poh3X8xPHPWZa4gEwLdCMldeiY>
Subject: Re: [v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-cpe-slaac-renum-05: (with COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 07:52:26 -0000

On 28/1/21 03:38, Benjamin Kaduk wrote:
[...]
> [...]
>>> Section 8.2
>>>
>>> It would feel more natural, at least to me, if RFC 7084 was listed as a
>>> normative reference.  (In the sense that we are Updating it to make
>>> incremental additions, but you need the whole combined assembly of both
>>> documents in order to have a functional setup.)
>>
>> I would assume so. But it would be a downref. Is that possible?
> 
> Most things are possible ... but with 7084 not listed at
> https://datatracker.ietf.org/doc/downref/ it might mean another IETF LC.
> Your responsible AD should probably be the one to make the call, and the
> "don't change it" option has a fair bit of inertia going for it.

Agreed.

Thanks!
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Thu Jan 28 01:21:20 2021
Return-Path: <magnus.westerlund@ericsson.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 03A543A1439; Thu, 28 Jan 2021 01:21:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.351
X-Spam-Level: 
X-Spam-Status: No, score=-2.351 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 lj2BUwucX5se; Thu, 28 Jan 2021 01:21:09 -0800 (PST)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-eopbgr80082.outbound.protection.outlook.com [40.107.8.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 681E83A1436; Thu, 28 Jan 2021 01:21:09 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=YIDP95MzOyHA2uBekdxokSuAFnt9jtx+0jNhReY8P+FFhzLitDfQTc8y9lHRN/XWgjGV6OJedkN8uZbwWpV01tRhquvfNhYxK64UJADGXUBpEAIeENaJy+QKH9ady25D8yV7qga76GKB4hagEEwFPOBVZm92P6/8iRGUkr6PQaISe9cEOu2b/Zd4zdXieRgaMQ5FD4GGIbUPQZ6S5N0NsxC6AMw+6yF67lqr0eAQePfnuQzIPw2Qpfo+q7i8nTVNXhIbrtXkyM71HOT4hJFDuVGpv3mWKsrAkgJj2ZF/l5mxTWVGU+n8dIZtNXtUWCPNsTgiQHc6A4Zt1ae4NbaBRA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=156rr6w+8OG6+7eMub96YBMKICLLizcwdcI7c8rk+mc=; b=RAG2wc5z2Z1oKlcHWOUjNYhl2cpo3Qd8M9+FJ5tSB5dr4qnmTNpD9EgEFkBaaqFTc/e3EXB+q39s2Xoz9JGHlDE61T54XyPjJruSI6Zf5Yw+5cRA/HPe4KvoZco7ibGNvYLj8bDlq3VLu/MzCESnEYZY1psbwoPdpaF6p688jIFWB7KQ7OTtv4h5hvbHEeFvJk370nQLGhB+zctOn/WxSKQ5cfowUyzBhIOVW7MaFt/SXR3/4kgiYfYULO1iGBBlIniqpeFWtV4Rfpc/lNLTkCh4aMKSb0XiQHk4OKkLCTDG9VrRHynkaBfLnaYvkCquCBtIA1r6JLvxuUksaPnYBA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=156rr6w+8OG6+7eMub96YBMKICLLizcwdcI7c8rk+mc=; b=FvfVpraZfvMpjizC5ZYtN8WtSqk+lwMEIsTiUScaFGuTffy5WZy5gpeXjHtncqo3m3ghLDxYzOwy9I6WY+knX8eOdYwVBfPjDPI2UfEFWJrSc8McyrHdC21yVLsfAX9J20smFTuBfwGYJJuDR12QAVE62GhJyaOMNe6B8AfrKXY=
Received: from (2603:10a6:803:10::30) by VI1PR07MB6543.eurprd07.prod.outlook.com (2603:10a6:800:188::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3825.8; Thu, 28 Jan 2021 09:21:06 +0000
Received: from VI1PR0702MB3775.eurprd07.prod.outlook.com ([fe80::6cd2:247d:3389:381]) by VI1PR0702MB3775.eurprd07.prod.outlook.com ([fe80::6cd2:247d:3389:381%6]) with mapi id 15.20.3805.007; Thu, 28 Jan 2021 09:21:06 +0000
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
To: "fgont@si6networks.com" <fgont@si6networks.com>, "mellon@fugue.com" <mellon@fugue.com>
CC: "v6ops@ietf.org" <v6ops@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "draft-ietf-v6ops-cpe-slaac-renum@ietf.org" <draft-ietf-v6ops-cpe-slaac-renum@ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, "kaduk@mit.edu" <kaduk@mit.edu>
Thread-Topic: [v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-cpe-slaac-renum-05: (with COMMENT)
Thread-Index: AQHWp2Y9emnDFggpbkGtzvLbGFHQtao8lfUAgAAEgACAAAbFAIAAAWuAgAAFnwCAAAGngIAAtRUA
Date: Thu, 28 Jan 2021 09:21:06 +0000
Message-ID: <3ad7fd372aea1bd7245dc25607afc3d0ec638c6f.camel@ericsson.com>
References: <160325603610.17357.6914550111489766157@ietfa.amsl.com> <cf025acf-5192-d9a3-a727-8716d9d7b232@si6networks.com> <C68DC427-85A4-4AE7-928A-C92AD2C4488A@fugue.com> <9404f657-dbcb-877d-5a3f-1f3408c3b890@si6networks.com> <30262C9F-D004-4452-9F40-A407D7B396D3@fugue.com> <85f2bc3f-51f5-a5b2-53cd-9b5a52ac227f@si6networks.com> <D563B1C2-EDEE-4352-9096-8E5877046E28@fugue.com>
In-Reply-To: <D563B1C2-EDEE-4352-9096-8E5877046E28@fugue.com>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Evolution 3.28.5-0ubuntu0.18.04.2 
authentication-results: si6networks.com; dkim=none (message not signed) header.d=none;si6networks.com; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [158.174.130.243]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 329c4ead-4958-4dd1-5494-08d8c36e0ab7
x-ms-traffictypediagnostic: VI1PR07MB6543:
x-microsoft-antispam-prvs: <VI1PR07MB65434E548CB8C6DED87C8B1295BA9@VI1PR07MB6543.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:5236;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: d3xYUK+ndPppPFCKV2rXoJXx/ihR8e/cHzhfeMN7vWBfJTYObWYT810BYRyGrfLxiRa0+H86ucYNCq+Hh97ZeNRIk5H8XFrFxoOA3ooEvl6ZcMLXSJ0xJvEDRDprQ+m4HYHpZbMgCc1wEjG3zWcJyyPSfg8D74eqsg+ZoEcEp7UOARjhHUyYmTalw9VWct2fyc5Wk8PZw+DfKKWDbVdX71FftdRrnYpC67KuITOrC/Zp8Za//7C8R/o19S6QyTnreJqkHOFKdCvAl0OwsINuAgYkAMU8Sea46cuMiio5JjsekKG09pI9RvkWAUdC8Q9b166/yRqxx78JR0acypzOsWu1W/YbDyvZCrW6l9JtF4HMjfiuCwecevdotbYj9Zn141V5wZfuQEC10XXjfI+SkWFvRMYecw0+f7hTw9DhMLt9jZKtOwseRJroL1aZN7HdR9MBROFTDigZtDXUG8zKMH4woYEVd6Cy2D81X+c6udf6E8IdMLsc908wh+yIsdKsfZhLxdV53WVKg5LhRQQCtrchh3dcV1gjK2IqZrr2hOg/gfX2zigXCMbtKQhO0C051nKPmhoIjRndLNph3jdnIRx+MnX4EV4ay2kvuO5JvqHLz8F3QcVpFkEQWzC0ucBZEiKGe+fJ1wiYl4qVvYzcjw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:VI1PR0702MB3775.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(366004)(396003)(136003)(39860400002)(376002)(346002)(64756008)(2906002)(66446008)(66616009)(66476007)(66556008)(66946007)(83380400001)(4326008)(110136005)(26005)(66574015)(8676002)(5660300002)(44832011)(478600001)(76116006)(91956017)(8936002)(6486002)(4744005)(6512007)(36756003)(186003)(316002)(71200400001)(53546011)(54906003)(6506007)(966005)(86362001)(99936003)(2616005)(99106002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?Z0xwNDIyZjFPWHBjVGlyaTIrVWdkQ2gvb0NVVXJ3WFpEU0JOZzBOV1BySHJ6?= =?utf-8?B?TE9POW1Pc0hYN24weGpaeTlCb3o3cEtTd1NLWFh1aVJVT0p6MThtWExTSGZz?= =?utf-8?B?ck4zcUtLTlp0NTVBQ25OQUdwbTR2QUhJV0c0b1UzSVo2RmY4R2RtVXU1a2tL?= =?utf-8?B?VmRHbXdwZko5NFNHTERMZFg0eVdBRXY2THM2YmtjWUhLeFpBeTdZYVU2alNj?= =?utf-8?B?LzBKSHFWZ04yZm5SOWRBTTNzTWI2bXhGdXoyOC80Mi9RdFdQa3RUZUpKUVVE?= =?utf-8?B?TUpqY3RTaS8wN0ovMHJwd3hMY1AzVDdtZzM1SEJTSkFvNU1zOUdqTlVtMkNK?= =?utf-8?B?SXBIeFNubEEvMGZRSC9FUjlEdk41c1hxQ0tvdm9jUjlKR2tUV2JBQUVxOTB5?= =?utf-8?B?cFUwY0J3RjlIWGtrcFpaMDBLTWxXVURXSEFWNE8yaXEyZHdaMWhKOHdtWVJM?= =?utf-8?B?S3ZEVlBUcGZmMUtJb3REUjBlTG1kK2ZYaWpKWUlmcldrSmY1MXNmU01aT0pN?= =?utf-8?B?Y0ljRHNrREIrY2VKR1FzRjNkbzA5MWt2ZVh1TlY4U2tUOXhPVi9rTDBTdjlp?= =?utf-8?B?SVdvQW1qVHEwZ1JheEZVaHRZVzBzU2o2M2tYMlUrNm4xRHpDYSsxNGU1czVH?= =?utf-8?B?cjRhWUV3aFhoSzM2eHJxRktxOG1YcnZLTGhwUHhJOC9GVEJpU3hwTDJhdFZJ?= =?utf-8?B?MEd4ZmVkL0w5cVpvbXFLU2p3U2YwY0lQQW80eHdsT3k4ZWpoMTBITjNiNWJq?= =?utf-8?B?NGJMSjFwbGRrRjYwN0V4RlBWZGphbE16ZytEZ2NhMVhxTEJGSGNtSmpvc0Ix?= =?utf-8?B?djVjYVJlOHJhQzBRc2ZlN3dyK2xQRXlNUXFMTFo1TVBvZVRHQ3UzM3hIRTlh?= =?utf-8?B?WFIyYkJ4MXBSNjh2ODFncDY1aVMzdmVlb3ZXeExRNGFwK0xWS2xocldLRmJt?= =?utf-8?B?cTFCSEJPWm9tL3BRQlN0UVRSYUxDR09lRFQwSzJjRjNaYzExdDIrcnJOZ1ll?= =?utf-8?B?c3IvSXN1cG5hRmhBYjYrMTNXZURCU3BOUktabDNqelh2anZXUzFneHk5SktT?= =?utf-8?B?bWc0dmM5bkRIemZlNmtybTBuWEVvV2VDV1p5TkczNWZJUURYZnRNVkRuZXNL?= =?utf-8?B?WVgrMUVuOEIxbXAzckZXK0lhTjJUYkJFMDBGUFdnRlIzdWRJSlM1cUVJSi9I?= =?utf-8?B?SlNCSDRuL0lBM3pkMlFsZzlETzY4OGxjQVY2dUx6aGhVWHp1WnpoTkRBQ2Yy?= =?utf-8?B?N2I3NmlnMSsrRHdzcXM1eEJ3REgrWmdienBwdFM3eDllMHlBWlpuRGJzRzhm?= =?utf-8?B?aG4yTXArMjdzTlJyMWh5eU9qd0srbGx4TmN1ZmJFMGJOQnBqSGhLUXZzUEYz?= =?utf-8?B?UWtIdEFaZFZka2hTZHRYMnNVdTlwRkZpYS81dFk5MklraDRCS3ZuZm05MXZ4?= =?utf-8?B?V2JpbTN2Zy9vYnRCKy8rMUFWK2FlTTVTamNYbEZRPT0=?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/signed; micalg="sha-256"; protocol="application/x-pkcs7-signature"; boundary="=-9zBXfRYzXYOcKFiSe5PV"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: VI1PR0702MB3775.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 329c4ead-4958-4dd1-5494-08d8c36e0ab7
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Jan 2021 09:21:06.6041 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Mi87tq/T2ZFvDGrHR3CvOkvM6n6FaxFB2J6CG4HYWGEfyna6SD94UNMXx9fskzKiuFkLNi5g21BgxkXlc5R3CQ5YjoTwKHEKJZKfZSCE9pM=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB6543
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/DA6romVjiDJ63VrVQRyhm57PkcY>
Subject: Re: [v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-cpe-slaac-renum-05: (with COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 09:21:12 -0000

--=-9zBXfRYzXYOcKFiSe5PV
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, 2021-01-27 at 17:32 -0500, Ted Lemon wrote:
> On Jan 27, 2021, at 5:27 PM, Fernando Gont <fgont@si6networks.com> wrote:
> > I added that to the Abstract because I was *asked* to. You see what I m=
ean?
> > :-)
>=20
> Huh. Well, it=E2=80=99s mostly harmless, so I wouldn=E2=80=99t waste any =
time trying to
> resolve this=E2=80=94just leave it in. But I don=E2=80=99t think it=E2=80=
=99s a best practice to do
> this, so next time it comes up I=E2=80=99d be tempted to argue the point.
>=20

So having updates in abstract and in the other places is according to the
Internet Draft checklist:

https://www.ietf.org/standards/ids/checklist/

See section 3.

Cheers

Magnus Westerlund

--=-9zBXfRYzXYOcKFiSe5PV
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCCErYw
ggX0MIID3KADAgECAg8BdlE9InYZOYLl1zGep4IwDQYJKoZIhvcNAQELBQAwRzELMAkGA1UEBhMC
U0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENB
IHYzMB4XDTIwMTIxMTA5NTg0OVoXDTIzMTIxMjA5NTg0OVowXjERMA8GA1UECgwIRXJpY3Nzb24x
GjAYBgNVBAMMEU1hZ251cyBXZXN0ZXJsdW5kMS0wKwYJKoZIhvcNAQkBFh5tYWdudXMud2VzdGVy
bHVuZEBlcmljc3Nvbi5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCIT6U9ddUp
UCEryIA27xtF8WsRAIfc5jBavfu0OGDmwITYYRD2PaMEdEK+I4dqz0f6xcCrDnBk2Xj+JxjhaRkq
TAifJZima9WE2JoI/uq8UsS2HJWlhspAwKx1osARgtRiMjRZZyyfiRZLbgXHWYpnTt3i9QsuX/uo
9oZFWpDCbZee4Il9uldsUcuBLZx2PyZvBvC8KCUaBXsZX6bwV7hssRVn+BgFCuEievJMx0khTRVh
i9goObxu5Jl44RtwbZNYB1UE1IzRWEZw+b3cEvXiQjPl2e3ytMZSmhy+IaKmjxES6ODiuh51KAcm
PZfZIaX2djmD76YGi+ETmnb8Xm3dAgMBAAGjggHEMIIBwDAfBgNVHSMEGDAWgBQcexmel5x2rCA9
2NzjkWrj2y2mUzAdBgNVHQ4EFgQUICO/88T0EQvEUm5+HVt/d9Mm+Z8wDgYDVR0PAQH/BAQDAgWg
MFUGA1UdIAROMEwwSgYMKwYBBAGCDwIDAQESMDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3Np
dG9yeS50cnVzdC50ZWxpYXNvbmVyYS5jb20vQ1BTMCkGA1UdEQQiMCCBHm1hZ251cy53ZXN0ZXJs
dW5kQGVyaWNzc29uLmNvbTBIBgNVHR8EQTA/MD2gO6A5hjdodHRwOi8vY3JsLnRydXN0LnRlbGlh
LmNvbS9lcmljc3Nvbm5saW5kaXZpZHVhbGNhdjMuY3JsMB0GA1UdJQQWMBQGCCsGAQUFBwMEBggr
BgEFBQcDAjCBggYIKwYBBQUHAQEEdjB0MCgGCCsGAQUFBzABhhxodHRwOi8vb2NzcDIudHJ1c3Qu
dGVsaWEuY29tMEgGCCsGAQUFBzAChjxodHRwOi8vY2EudHJ1c3QudGVsaWFzb25lcmEuY29tL2Vy
aWNzc29ubmxpbmRpdmlkdWFsY2F2My5jZXIwDQYJKoZIhvcNAQELBQADggIBANRZXQy+lUW97uaL
uApOixnDKLpUoz+N/5Owd/9illmbxQDEY1/pPs4KJSvw88p+F3bmOzb+fLUNa6Mi/2Tw83FzEVmO
3RqzKtca+I9GDpRQ8oWL7hrUPJoNacidSZLmAP4L4kwHIhvGNX4f1c/oB4fAkP/xZsAAxYi7nKxd
XA2n/KMWNkezyB9BSsD8ZOS4pWU8UaZjd5r0fzqM5zQbU4EPqHa8jFMSMz1UrYXPKKxl6E4WA3TE
w1oLjcli0NWGQHyQ+3Kh7fe6zPoXfLd/2EQjr2o76ssgoqd2V1Mx5TRHdUyxjIMPEOVYpvcerNUB
hEBkaOQ9FugYcMhMc8BF7nQZq+hsL/T7idg4gE2sEfNdK9RBf/EVH10GMrmbadqTycztD1gUL3dV
Qxik4TCMxIctt9XqtTGHaMewZLQAXp/sHWlU/vmz9brcuzYQ9YVd5hTendGMUyGhWPV/KvxouKPK
zdrGeEqUQCeBwWgQASQNOrpTzMJwZAV/Ww3ExQCjHvflvUQzVuU0sC6AEVkgqMATIXS6h6rjLL31
pjt2JV84XRjF5afYkcRIHTsrtcoWeFtOu/GpZNhtq+tde0QvnkSsjczMWU0gKk0hXBmXwEGUimuD
Vq/Wvr0mr18d9mKA6xPNQOfn/VL5CWXa11OtOjj8WsTy3XUpyJ6dc9Z72TmKMIIF9DCCA9ygAwIB
AgIPAXZRPSJ2GTmC5dcxnqeCMA0GCSqGSIb3DQEBCwUAMEcxCzAJBgNVBAYTAlNFMREwDwYDVQQK
DAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MzAeFw0yMDEy
MTEwOTU4NDlaFw0yMzEyMTIwOTU4NDlaMF4xETAPBgNVBAoMCEVyaWNzc29uMRowGAYDVQQDDBFN
YWdudXMgV2VzdGVybHVuZDEtMCsGCSqGSIb3DQEJARYebWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nz
b24uY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAiE+lPXXVKVAhK8iANu8bRfFr
EQCH3OYwWr37tDhg5sCE2GEQ9j2jBHRCviOHas9H+sXAqw5wZNl4/icY4WkZKkwInyWYpmvVhNia
CP7qvFLEthyVpYbKQMCsdaLAEYLUYjI0WWcsn4kWS24Fx1mKZ07d4vULLl/7qPaGRVqQwm2XnuCJ
fbpXbFHLgS2cdj8mbwbwvCglGgV7GV+m8Fe4bLEVZ/gYBQrhInryTMdJIU0VYYvYKDm8buSZeOEb
cG2TWAdVBNSM0VhGcPm93BL14kIz5dnt8rTGUpocviGipo8REujg4roedSgHJj2X2SGl9nY5g++m
BovhE5p2/F5t3QIDAQABo4IBxDCCAcAwHwYDVR0jBBgwFoAUHHsZnpecdqwgPdjc45Fq49stplMw
HQYDVR0OBBYEFCAjv/PE9BELxFJufh1bf3fTJvmfMA4GA1UdDwEB/wQEAwIFoDBVBgNVHSAETjBM
MEoGDCsGAQQBgg8CAwEBEjA6MDgGCCsGAQUFBwIBFixodHRwczovL3JlcG9zaXRvcnkudHJ1c3Qu
dGVsaWFzb25lcmEuY29tL0NQUzApBgNVHREEIjAggR5tYWdudXMud2VzdGVybHVuZEBlcmljc3Nv
bi5jb20wSAYDVR0fBEEwPzA9oDugOYY3aHR0cDovL2NybC50cnVzdC50ZWxpYS5jb20vZXJpY3Nz
b25ubGluZGl2aWR1YWxjYXYzLmNybDAdBgNVHSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwgYIG
CCsGAQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNvbTBI
BggrBgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5saW5k
aXZpZHVhbGNhdjMuY2VyMA0GCSqGSIb3DQEBCwUAA4ICAQDUWV0MvpVFve7mi7gKTosZwyi6VKM/
jf+TsHf/YpZZm8UAxGNf6T7OCiUr8PPKfhd25js2/ny1DWujIv9k8PNxcxFZjt0asyrXGviPRg6U
UPKFi+4a1DyaDWnInUmS5gD+C+JMByIbxjV+H9XP6AeHwJD/8WbAAMWIu5ysXVwNp/yjFjZHs8gf
QUrA/GTkuKVlPFGmY3ea9H86jOc0G1OBD6h2vIxTEjM9VK2FzyisZehOFgN0xMNaC43JYtDVhkB8
kPtyoe33usz6F3y3f9hEI69qO+rLIKKndldTMeU0R3VMsYyDDxDlWKb3HqzVAYRAZGjkPRboGHDI
THPARe50GavobC/0+4nYOIBNrBHzXSvUQX/xFR9dBjK5m2nak8nM7Q9YFC93VUMYpOEwjMSHLbfV
6rUxh2jHsGS0AF6f7B1pVP75s/W63Ls2EPWFXeYU3p3RjFMhoVj1fyr8aLijys3axnhKlEAngcFo
EAEkDTq6U8zCcGQFf1sNxMUAox735b1EM1blNLAugBFZIKjAEyF0uoeq4yy99aY7diVfOF0YxeWn
2JHESB07K7XKFnhbTrvxqWTYbavrXXtEL55ErI3MzFlNICpNIVwZl8BBlIprg1av1r69Jq9fHfZi
gOsTzUDn5/1S+Qll2tdTrTo4/FrE8t11KcienXPWe9k5ijCCBsIwggSqoAMCAQICEFO4foPhnJko
k7CbSRzsuOswDQYJKoZIhvcNAQELBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmExHzAdBgNVBAMM
FlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTUxMDI3MTIxNjQ2WhcNMjUxMDI3MTIxNjQ2WjBH
MQswCQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nzb24xJTAjBgNVBAMMHEVyaWNzc29uIE5MIElu
ZGl2aWR1YWwgQ0EgdjMwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQDs8t8AALhQ8qe7
2FS3xpP348GqO9TDRjS0s85eQ7Y0LTLZdmSz2cl+lYqs0zfSTm+7meisbhkqUXkL7fFzoe4iIZCh
/VuYUaW407CZlDCXes4n4TqTSuoklN6uOPhY7EC9ZVbXILlLhRummTdDdxhVW4Leo0awEhfLf98M
vWxzwCHzMj8m6YOmNjx+f9TcJE3qaA0piuvSxlfpVdiCulPTlmsmV2RSBSAwqBshZYRcQBIDfqmd
vkaoP9EzNKAh7yjthC0hpgHZyZMIs0eNo4v2PUmE0rhu+Zs0nujnwhljPA2/8b8v9tGixD1zbtT7
zoM2Ot1menJpFp4zJVSfdKVgtoWqg5t2H/E0XY1LwJez89W07nscEocyBmpC+zJAmKxKhzEWqIyP
1UrZaEIFu+hO+s0Nm8sOUMa4TlG4rAUikc5U5TmUIGBRQGxulYhfAzqSYf8oLUMLky1DOa9eRu3s
p0FdQDEzQlnF/h1L4AK1MOkX1vS+fLgOvBo5LRU1fLPUZQ7FKrDXC6nl2ldvEtljHWstGBmqv25a
EvAA+yrrplCh/kYvSBjvZibz9Obbwx4yqS77/NHN1iyZyVP2s52B2BLdvo4yhzk6nRk8S/8zHaUU
kBUrrvijPDaGK5FNVSaioGvkC7IKioITKffYLtT9XuirKrHlh3VzkazG46pAVwIDAQABo4IBuDCC
AbQwgYoGCCsGAQUFBwEBBH4wfDAtBggrBgEFBQcwAYYhaHR0cDovL29jc3AudHJ1c3QudGVsaWFz
b25lcmEuY29tMEsGCCsGAQUFBzAChj9odHRwOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYXNvbmVy
YS5jb20vdGVsaWFzb25lcmFyb290Y2F2MS5jZXIwEgYDVR0TAQH/BAgwBgEB/wIBADBVBgNVHSAE
TjBMMEoGDCsGAQQBgg8CAwEBAjA6MDgGCCsGAQUFBwIBFixodHRwczovL3JlcG9zaXRvcnkudHJ1
c3QudGVsaWFzb25lcmEuY29tL0NQUzBLBgNVHR8ERDBCMECgPqA8hjpodHRwOi8vY3JsLTMudHJ1
c3QudGVsaWFzb25lcmEuY29tL3RlbGlhc29uZXJhcm9vdGNhdjEuY3JsMB0GA1UdJQQWMBQGCCsG
AQUFBwMCBggrBgEFBQcDBDAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFBx7GZ6XnHasID3Y3OOR
auPbLaZTMB8GA1UdIwQYMBaAFPCPWTgAs/WPmpYM1ev6e6oX6BMSMA0GCSqGSIb3DQEBCwUAA4IC
AQBQWGvx1Yw7tC6rV0PIjKfDyxaanIX+NZLEGOkdQLKGW2gVLtDUJQEPRs5QtaZiObNHCZ7mmSNM
Vek4lkt/0dqfVIFutVw/QkyFGwC99ZmNwXSX9z+OoMyoEBHGvw5RY6vRlZrj0uKvdASzYL4KMaB7
m3NwurNDmmNbG52suRIZ76wBOEOddRZcZiTy50ZkBqYnnl2t3D3oBX2NZCQysshUcqRdUbkS13HT
CIChMuTV9W0tzPXUOJoJlJlU9nd91IikhGEOrPwfixWms+C8sF0r9qN1uJGx6ELPOiFrLfNtcMNM
MbAqRHwpSLxe3wcNkJGxv9T8LswLi1UrRIQ85AKjqzBnLSsjRGgbMgJ+xKtngmvEA155JmoKfUD7
DRbP6Kp14/Y9XFbR/WuDj84bYNKXe4HdDc1P+UMYm16m2L6LkIIoRlx0A5mi+K7jewuGqzFKkaPN
mJ0RLCi+4d4/47Zs3DC3PUNOxdOEEHf4kkdWOaSIuj3TQYhNv+LsgF0uijiBmaz2zUFDa2bcIkKa
kDZfAFM4HoHz8K2BZRaHKWhd3dZua/tlSiqokUFX2DxmHmZ1n5HM9OiaAIXP/Zo2x10j/Yb1mM3i
0bqGahxlHYzl/QyEG/dujp3lewuVjCI0mPDkZGphvxyqp4Jo8qS94EnOqBvxOgftYug7OY9EKY+W
kDGCAsowggLGAgEBMFowRzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYzAg8BdlE9InYZOYLl1zGep4IwDQYJYIZIAWUD
BAIBBQCgggFBMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTIxMDEy
ODA5MjEwNFowLwYJKoZIhvcNAQkEMSIEIKE5unPePZdcv5zE4NfkkdjFcMWDzDFedO/+ZlXx9h07
MGkGCSsGAQQBgjcQBDFcMFowRzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYD
VQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYzAg8BdlE9InYZOYLl1zGep4IwawYLKoZI
hvcNAQkQAgsxXKBaMEcxCzAJBgNVBAYTAlNFMREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwc
RXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MwIPAXZRPSJ2GTmC5dcxnqeCMA0GCSqGSIb3DQEB
AQUABIIBAAIGAimicCUQfIU3t4ASMGA23p1OHHZzwV6+fmj4LpqZzq3gD2nU6ptTjuPpGLgFVR/o
g8QLcPTTRX0kZLWXGqmZsXqE+zJDxjbT62fre+0AjEXyYbiORU8cTwzVOZoqIV5Byx/hUFpc77ql
gP+ToKJDQ+bAi508w+iXHTrNVOdzd1ZYbonGXE9sGyUenhvJP0paTRmu7eotmyVMKArwz4/G212d
+75+3ElrNgUxDwnocsxy54k8UkACt/Cv/7l6jXssEXEOa1Rd9V+oroUG+CV1E8LfB1tzd2K+7p2W
EU/k4o4xRJhuf1vefohIIg/bFZcx+6iypeYXfBevm9IFn30AAAAAAAA=


--=-9zBXfRYzXYOcKFiSe5PV--


From nobody Fri Jan 29 11:19:56 2021
Return-Path: <session-request@ietf.org>
X-Original-To: v6ops@ietf.org
Delivered-To: v6ops@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E6B2C3A1245; Fri, 29 Jan 2021 11:19:53 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: lflynn@amsl.com, v6ops-chairs@ietf.org, v6ops@ietf.org, warren@kumari.net
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <161194799387.7892.9248556160147862725@ietfa.amsl.com>
Date: Fri, 29 Jan 2021 11:19:53 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/6A-l2ZpVbk_BvzGgBdsAhBt5gr0>
Subject: [v6ops] v6ops - Update to a Meeting Session Request for IETF 110
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2021 19:19:54 -0000

An update to a meeting session request has just been submitted by Liz Flynn, on behalf of the v6ops working group.


---------------------------------------------------------
Working Group Name: IPv6 Operations
Area Name: Operations and Management Area
Session Requester: Liz Flynn


Number of Sessions: 1
Length of Session(s):  2 Hours
Number of Attendees: 100
Conflicts to Avoid: 
 Chair Conflict: spring lsr 6man intarea idr bess tsvwg

 Key Participant Conflict: rtgwg panrg grow





People who must be present:
  Fred Baker
  Ron Bonica
  Warren &quot;Ace&quot; Kumari

Resources Requested:

Special Requests:
  
---------------------------------------------------------



From hayu8548@colorado.edu  Fri Jan 29 20:06:37 2021
Return-Path: <hayu8548@colorado.edu>
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 25E863A0A1C for <v6ops@ietfa.amsl.com>; Fri, 29 Jan 2021 20:06:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level: 
X-Spam-Status: No, score=-2.087 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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=colorado.edu
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 d2y7MUUI8Qvi for <v6ops@ietfa.amsl.com>; Fri, 29 Jan 2021 20:06:35 -0800 (PST)
Received: from mail-lf1-x144.google.com (mail-lf1-x144.google.com [IPv6:2a00:1450:4864:20::144]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 097C03A0A12 for <v6ops@ietf.org>; Fri, 29 Jan 2021 20:06:34 -0800 (PST)
Received: by mail-lf1-x144.google.com with SMTP id i187so15326459lfd.4 for <v6ops@ietf.org>; Fri, 29 Jan 2021 20:06:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=colorado.edu; s=google; h=mime-version:reply-to:from:date:message-id:subject:to; bh=zaCv7owCqEOCIDtoLeVGUBIjJ8i1uo/qMOSeQrd7Cww=; b=e8049fx337A0KPKBSWQHshZNOKMz66RvDP65w+7NS6iRC0ctEzsWUsBJiwvHSxn/GS wWhJz9AlbJVjne7f/IOJd7LtLFgJYupaNO8wAGXjp1GmAxCdzZfjLlkxoU+fC78vD9EU jLzBKrKlikJ3peEy2kDqdbFnaVjPHr4H2hPkdTRZlXQKwuq6Me0NaXbW4aXvFVxgtc5N /MFkeRZvuIG0jVWlloSVAcTXAxYcotGoB10MJuuCqaz0wo3vxNzpx6/TOw1O/VqwKmh6 Vzx31zxwIX1bcRk3el177cdWhZdjdxJN6wDnOsxPzKLObaLWfnHYNAop9p4IGeNZCFEV D32A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:from:date:message-id :subject:to; bh=zaCv7owCqEOCIDtoLeVGUBIjJ8i1uo/qMOSeQrd7Cww=; b=B+15vmLoH7FfQhwZOzNybTdZ9Ct+VM7YPEfGFPoiCxVRrlfP1ZnOs/UXeWfbvlAUUq YXzwZTpzhQsqE2/3Gs/xy7ONoHfWNrTZFdTBAS2CvJtAVokSjfkKL2Mffkje3v3vqMs8 kw++ux3cMrJAez0yktZgMP75Z1DeaR0jYrF9gkxylQ4YGOr0wzsqB2ArAb5UXZHs9xS7 kInITYatUnIr8Ya+wUJM+4DiyuRh75p5O6f+pidIkGYRiVIs25Eer8pApHr8UneJrMLS HNhz7jYwkYALewv+eM2JrrTHwzBU8pjhqJVQGv+2K6BfW6bK7/yUG+NA7XoEdFrVpK+h CTSA==
X-Gm-Message-State: AOAM533UhXQ8ltqTwHFFO2enGuDttznQLGbCISNZ48tuAExYqpcipTnL 0BRNXcL0AbLYfyeauuNTbcmADk0oKjDP0hUIdlMwrW0ywUzJ/JU4GuE9+SV/
X-Google-Smtp-Source: ABdhPJy+9MQxw1Auf+PYz6BBTSIr9FYZcCvapI3txxwEEFsAytWwZtnMe8DsPywwsaAYM8Ss/In2/avSOOfDdOtdOTg=
X-Received: by 2002:ac2:5612:: with SMTP id v18mr3567535lfd.515.1611979592564;  Fri, 29 Jan 2021 20:06:32 -0800 (PST)
MIME-Version: 1.0
Reply-To: Haisheng.Yu@colorado.edu
From: Haisheng Yu <Haisheng.Yu@colorado.edu>
Date: Sat, 30 Jan 2021 12:06:20 +0800
Message-ID: <CAAZtB7RFko+ppFqavDwWVZSJqOd2e70_jrW9a8ePg7Oe+WPzaA@mail.gmail.com>
To: v6ops@ietf.org
Content-Type: multipart/alternative; boundary="000000000000001c5905ba163fc1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/OeGvkryj7BHAc7919YnXaKQ8NKg>
Subject: Re: [v6ops] IETF 110 agenda development
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Jan 2021 04:12:53 -0000

--000000000000001c5905ba163fc1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi folks,

Thanks to the authors for this very well-written draft, which clearly
analyzed and stated the issues faced by the HBH options header. The logic
is very clear, and the derived requirements are also reasonable. This work
is very valuable and has the potential to be taken as a guidance especially
when the IPv6 is being widely deployed as well as the new services enabled
by IPv6. I hope the WG can consider to progress this work further and I
support it.

By the way, some of the IPv6-based innovations I am currently working on
also need the support of HBH.


Best Regards.


Haisheng Yu


On 1/22/2021 14:23=EF=BC=8CPengshuping (Peng Shuping)<pengshuping@huawei.co=
m>
<pengshuping@huawei.com> wrote=EF=BC=9A

Hi Fred, all,



Just to add a bit more information here.



Thanks to all the feedback we received after the presentation in IETF109,
we have updated the draft with the help of all the coauthors and
contributors. Please find the diff,
https://tools.ietf.org/rfcdiff?url2=3Ddraft-peng-v6ops-hbh-03.txt



It will be great if we continue to receiving your feedback and comments to
improve this work further.



Best regards,

Shuping







*From:* v6ops [mailto:v6ops-bounces@ietf.org] *On Behalf Of *Gyan Mishra
*Sent:* Friday, January 22, 2021 1:05 PM
*To:* Fred Baker <fredbaker.ietf@gmail.com>
*Cc:* IPv6 Operations <v6ops@ietf.org>
*Subject:* Re: [v6ops] IETF 110 agenda development



Hi Fred



I would like to request a 10-15 minute time slot for

HBH draft below:



https://tools.ietf.org/html/draft-peng-v6ops-hbh-03



Thank you



Gyan





On Sat, Jan 9, 2021 at 1:16 PM Fred Baker <fredbaker.ietf@gmail.com> wrote:

You can find the important dates for IETF 110 at
https://datatracker.ietf.org/meeting/important-dates/. It will be held
virtually, as the last several have. It was intended to be held in Prague
(and I was looking forward to Prague), and so will be timed as if it were
in that timezone.

I mention the dates page, as that page indicates that the draft cut-off is
2021-02-22. If you want to get a document in to discuss in March, it needs
to be in by then, and enough earlier to allow some discussion on the list
prior to Ron and I having to concoct and agenda.
_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops

--

[image: =E5=9B=BE=E5=83=8F=E5=B7=B2=E8=A2=AB=E5=8F=91=E4=BB=B6=E4=BA=BA=E5=
=88=A0=E9=99=A4=E3=80=82] <http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions Architect *



*M 301 502-134713101 Columbia Pike *Silver Spring, MD

--000000000000001c5905ba163fc1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div style=3D"color:rgb(49,53,59);font-family:=E5=BE=AE=E8=
=BD=AF=E9=9B=85=E9=BB=91,Verdana,&quot;Microsoft Yahei&quot;,SimSun,sans-se=
rif;font-size:14px;font-variant-numeric:normal;font-variant-east-asian:norm=
al;line-height:22.4px"><div><div style=3D"font-family:Verdana,&quot;Microso=
ft Yahei&quot;,SimSun,sans-serif;line-height:22.4px">Hi folks,</div><div st=
yle=3D"font-family:Verdana,&quot;Microsoft Yahei&quot;,SimSun,sans-serif;li=
ne-height:22.4px"><br></div><div style=3D"font-family:Verdana,&quot;Microso=
ft Yahei&quot;,SimSun,sans-serif;line-height:22.4px">Thanks to the authors =
for this very well-written draft, which clearly analyzed and stated the iss=
ues faced by the HBH options header. The logic is very clear, and the deriv=
ed requirements are also reasonable. This work is very valuable and has the=
 potential to be taken as a guidance especially when the IPv6 is being wide=
ly deployed as well as the new services enabled by IPv6.=C2=A0I hope the WG=
 can consider to progress this work further and I support it. =C2=A0</div><=
div style=3D"font-family:Verdana,&quot;Microsoft Yahei&quot;,SimSun,sans-se=
rif;line-height:22.4px"><br></div><font style=3D"line-height:22.4px;font-fa=
mily:Verdana,&quot;Microsoft Yahei&quot;,SimSun,sans-serif"></font><div sty=
le=3D"font-family:Verdana,&quot;Microsoft Yahei&quot;,SimSun,sans-serif;lin=
e-height:22.4px">By the way,=C2=A0some of the IPv6-based innovations I am c=
urrently working on also need the support of HBH.=C2=A0=C2=A0</div><div sty=
le=3D"font-family:Verdana,&quot;Microsoft Yahei&quot;,SimSun,sans-serif;lin=
e-height:22.4px"><br></div><div id=3D"gmail-ntes-pcmac-signature" style=3D"=
font-family:Verdana,&quot;Microsoft Yahei&quot;,SimSun,sans-serif;line-heig=
ht:22.4px"><div style=3D"padding:0px;margin:0px;line-height:14px"><br></div=
><div style=3D"padding:0px;margin:0px;line-height:14px">Best Regards.</div>=
<div style=3D"padding:0px;margin:0px;line-height:14px"><br></div><div style=
=3D"padding:0px;margin:0px;line-height:14px"><br></div><div style=3D"paddin=
g:0px;margin:0px">Haisheng Yu</div><div style=3D"padding:0px;margin:0px"><b=
r></div></div></div><div><br></div></div><div class=3D"gmail-J-reply" style=
=3D"color:rgb(49,53,59);font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,Ve=
rdana,&quot;Microsoft Yahei&quot;,SimSun,sans-serif;font-size:14px;font-var=
iant-numeric:normal;font-variant-east-asian:normal;line-height:22.4px;paddi=
ng-top:6px;padding-bottom:6px;border-radius:3px;margin-top:45px;margin-bott=
om:20px;background-color:rgb(242,242,242)"><div style=3D"font-size:12px;lin=
e-height:1.5;word-break:break-all;margin-left:10px;margin-right:10px">On=C2=
=A0<span class=3D"gmail-mail-date">1/22/2021 14:23</span>=EF=BC=8C<a class=
=3D"gmail-mail-to" href=3D"mailto:pengshuping@huawei.com" style=3D"color:rg=
b(42,131,242);text-decoration-line:none">Pengshuping (Peng Shuping)&lt;peng=
shuping@huawei.com&gt;</a>=C2=A0wrote=EF=BC=9A</div></div><blockquote id=3D=
"gmail-ntes-pcmail-quote" style=3D"color:rgb(49,53,59);font-family:=E5=BE=
=AE=E8=BD=AF=E9=9B=85=E9=BB=91,Verdana,&quot;Microsoft Yahei&quot;,SimSun,s=
ans-serif;font-size:14px;font-variant-numeric:normal;font-variant-east-asia=
n:normal;line-height:22.4px;margin:0px;padding:0px"><div class=3D"gmail-Wor=
dSection1"><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:1=
0.5pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Hi Fred, all,</s=
pan></p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5=
pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">=C2=A0</span></p><p=
 class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-fa=
mily:Calibri,sans-serif;color:rgb(31,73,125)">Just to add a bit more inform=
ation here.</span></p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"=
font-size:10.5pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">=C2=
=A0</span></p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-siz=
e:10.5pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Thanks to all=
 the feedback we received after the presentation in IETF109, we have update=
d the draft with the help of all the coauthors and contributors. Please fin=
d the diff,=C2=A0<a href=3D"https://tools.ietf.org/rfcdiff?url2=3Ddraft-pen=
g-v6ops-hbh-03.txt" style=3D"color:rgb(6,73,119)">https://tools.ietf.org/rf=
cdiff?url2=3Ddraft-peng-v6ops-hbh-03.txt</a></span></p><p class=3D"MsoNorma=
l"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:Calibri,sans-=
serif;color:rgb(31,73,125)">=C2=A0</span></p><p class=3D"MsoNormal"><span l=
ang=3D"EN-US" style=3D"font-size:10.5pt;font-family:Calibri,sans-serif;colo=
r:rgb(31,73,125)">It will be great if we continue to receiving your feedbac=
k and comments to improve this work further.</span></p><p class=3D"MsoNorma=
l"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:Calibri,sans-=
serif;color:rgb(31,73,125)">=C2=A0</span></p><p class=3D"MsoNormal"><span l=
ang=3D"EN-US" style=3D"font-size:10.5pt;font-family:Calibri,sans-serif;colo=
r:rgb(31,73,125)">Best regards,</span></p><p class=3D"MsoNormal"><span lang=
=3D"EN-US" style=3D"font-size:10.5pt;font-family:Calibri,sans-serif;color:r=
gb(31,73,125)">Shuping</span></p><p class=3D"MsoNormal"><span lang=3D"EN-US=
" style=3D"font-size:10.5pt;font-family:Calibri,sans-serif;color:rgb(31,73,=
125)">=C2=A0</span></p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D=
"font-size:10.5pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">=C2=
=A0</span></p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-siz=
e:10.5pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">=C2=A0</span>=
</p><div style=3D"border-style:none none none solid;border-left-width:1.5pt=
;border-left-color:blue;padding:0cm 0cm 0cm 4pt"><div><div style=3D"border-=
style:solid none none;border-top-width:1pt;border-top-color:rgb(225,225,225=
);padding:3pt 0cm 0cm"><p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=
=3D"font-size:11pt;font-family:Calibri,sans-serif">From:</span></b><span la=
ng=3D"EN-US" style=3D"font-size:11pt;font-family:Calibri,sans-serif">=C2=A0=
v6ops [mailto:<a href=3D"mailto:v6ops-bounces@ietf.org" style=3D"color:rgb(=
6,73,119)">v6ops-bounces@ietf.org</a>]=C2=A0<b>On Behalf Of=C2=A0</b>Gyan M=
ishra<br><b>Sent:</b>=C2=A0Friday, January 22, 2021 1:05 PM<br><b>To:</b>=
=C2=A0Fred Baker &lt;<a href=3D"mailto:fredbaker.ietf@gmail.com" style=3D"c=
olor:rgb(6,73,119)">fredbaker.ietf@gmail.com</a>&gt;<br><b>Cc:</b>=C2=A0IPv=
6 Operations &lt;<a href=3D"mailto:v6ops@ietf.org" style=3D"color:rgb(6,73,=
119)">v6ops@ietf.org</a>&gt;<br><b>Subject:</b>=C2=A0Re: [v6ops] IETF 110 a=
genda development</span></p></div></div><p class=3D"MsoNormal"><span lang=
=3D"EN-US">=C2=A0</span></p><div><p class=3D"MsoNormal"><span lang=3D"EN-US=
">Hi Fred</span></p></div><div><p class=3D"MsoNormal"><span lang=3D"EN-US">=
=C2=A0</span></p></div><div><p class=3D"MsoNormal"><span lang=3D"EN-US">I w=
ould like to request a 10-15 minute time slot for=C2=A0</span></p></div><di=
v><p class=3D"MsoNormal"><span lang=3D"EN-US">HBH draft below:</span></p></=
div><div><p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0</span></p></div=
><div><div><p class=3D"MsoNormal"><span lang=3D"EN-US"><a href=3D"https://t=
ools.ietf.org/html/draft-peng-v6ops-hbh-03" style=3D"color:rgb(6,73,119)">h=
ttps://tools.ietf.org/html/draft-peng-v6ops-hbh-03</a></span></p></div><p c=
lass=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0</span></p></div><div><p clas=
s=3D"MsoNormal"><span lang=3D"EN-US">Thank you=C2=A0</span></p></div><div><=
p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0</span></p></div><div><p c=
lass=3D"MsoNormal"><span lang=3D"EN-US">Gyan</span></p></div><div><p class=
=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0</span></p></div><div><p class=3D=
"MsoNormal"><span lang=3D"EN-US">=C2=A0</span></p></div><div><p class=3D"Ms=
oNormal"><span lang=3D"EN-US">On Sat, Jan 9, 2021 at 1:16 PM Fred Baker &lt=
;<a href=3D"mailto:fredbaker.ietf@gmail.com" style=3D"color:rgb(6,73,119)">=
fredbaker.ietf@gmail.com</a>&gt; wrote:</span></p></div><div><blockquote st=
yle=3D"margin-right:0cm;border-style:none none none solid;border-left-width=
:1pt;border-left-color:rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left=
:4.8pt"><p class=3D"MsoNormal"><span lang=3D"EN-US">You can find the import=
ant dates for IETF 110 at=C2=A0<a href=3D"https://datatracker.ietf.org/meet=
ing/important-dates/" target=3D"_blank" style=3D"color:rgb(6,73,119)">https=
://datatracker.ietf.org/meeting/important-dates/</a>. It will be held virtu=
ally, as the last several have. It was intended to be held in Prague (and I=
 was looking forward to Prague), and so will be timed as if it were in that=
 timezone.<br><br>I mention the dates page, as that page indicates that the=
 draft cut-off is 2021-02-22. If you want to get a document in to discuss i=
n March, it needs to be in by then, and enough earlier to allow some discus=
sion on the list prior to Ron and I having to concoct and agenda.<br>______=
_________________________________________<br>v6ops mailing list<br><a href=
=3D"mailto:v6ops@ietf.org" target=3D"_blank" style=3D"color:rgb(6,73,119)">=
v6ops@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/v6op=
s" target=3D"_blank" style=3D"color:rgb(6,73,119)">https://www.ietf.org/mai=
lman/listinfo/v6ops</a></span></p></blockquote></div><p class=3D"MsoNormal"=
><span lang=3D"EN-US">--</span></p><div><p style=3D"margin:0px"><span lang=
=3D"EN-US" style=3D"color:rgb(34,34,34)"><a href=3D"http://www.verizon.com/=
" target=3D"_blank" style=3D"color:rgb(6,73,119)"><span style=3D"color:rgb(=
17,85,204);border:1pt solid windowtext;padding:0cm;text-decoration-line:non=
e"><img border=3D"0" width=3D"81" height=3D"18" id=3D"gmail-_x0000_i1025" s=
rc=3D"http://mail.163.com/js6/s?func=3Dmbox:getMessageData&amp;mid=3D168:1t=
biqA8qsFc7TkxHIQABs0&amp;part=3D3" alt=3D"=E5=9B=BE=E5=83=8F=E5=B7=B2=E8=A2=
=AB=E5=8F=91=E4=BB=B6=E4=BA=BA=E5=88=A0=E9=99=A4=E3=80=82" style=3D"border:=
 0px;"></span></a></span></p><p style=3D"margin:0cm 0cm 0.0001pt"><b><span =
lang=3D"EN-US" style=3D"font-family:Arial,sans-serif">Gyan Mishra</span></b=
><span lang=3D"EN-US" style=3D"font-family:Arial,sans-serif"></span></p><p =
style=3D"margin:0cm 0cm 0.0001pt"><i><span lang=3D"EN-US" style=3D"font-fam=
ily:Georgia,serif">Network Solutions Architect=C2=A0</span></i><span lang=
=3D"EN-US" style=3D"color:rgb(34,34,34)"></span></p><p style=3D"margin:0cm =
0cm 0.0001pt"><i><span lang=3D"EN-US" style=3D"font-family:Georgia,serif">M=
 301 502-1347<br>13101 Columbia Pike=C2=A0<br></span></i><span lang=3D"EN-U=
S">Silver Spring, MD</span></p></div></div></div></blockquote></div>

--000000000000001c5905ba163fc1--

