Re: [IPv6] I-D Action: draft-ietf-6man-rfc6724-update-08.txt

Nick Buraglio <buraglio@forwardingplane.net> Tue, 09 April 2024 14:13 UTC

Return-Path: <buraglio@forwardingplane.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 239D1C14F695 for <ipv6@ietfa.amsl.com>; Tue, 9 Apr 2024 07:13:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level:
X-Spam-Status: No, score=-7.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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=forwardingplane.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xKOHys_ax7g8 for <ipv6@ietfa.amsl.com>; Tue, 9 Apr 2024 07:13:27 -0700 (PDT)
Received: from mail-oi1-x22a.google.com (mail-oi1-x22a.google.com [IPv6:2607:f8b0:4864:20::22a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FD51C14F60D for <ipv6@ietf.org>; Tue, 9 Apr 2024 07:13:26 -0700 (PDT)
Received: by mail-oi1-x22a.google.com with SMTP id 5614622812f47-3bbbc6b4ed1so3536491b6e.2 for <ipv6@ietf.org>; Tue, 09 Apr 2024 07:13:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=forwardingplane.net; s=google; t=1712672006; x=1713276806; darn=ietf.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=cUxIoAQQtNsC1/jj4yOEKW/zgu/RDLTeWTSU/zuTCOw=; b=Jg5sHVBHPCgWq8Tmqq38rGZSmATY06Lo258Mhm/XCaulNXnSJo+U+E5qE3cOIjdgeY 1KqDOcBwNLYnJp051WnN8RWiEnZwRy4Ww+WOhnUoxSzb9bR0uPxiej4uoIY+7ua+mxl6 HqKGCFTcWV3IYSXS1NgqcqoZeKmhrKQm7Tk6E=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712672006; x=1713276806; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=cUxIoAQQtNsC1/jj4yOEKW/zgu/RDLTeWTSU/zuTCOw=; b=eGEJoWiuPvS+FH+5gB+qfR0aNeSNmXPOWJgDiQLC5rwgYv4+XDygZ0X574/Mdq9XHt y798f++bMyoiyUDzhYFDHZxzXkevEWAPSZMRM2CULwhZeXGiLt4ulsEKlvPjPNG4HYFX uzxtYurHQ1Ws4fnNw6Jp2+PbKtS8ObZsYH+lAi6dGUwAcI35Tq7h5pu22pPlueySy/qw TfnqK2H69DlWnmql0qtnCkffCCV6AfU/WgaFx7lt4qg1A+q/NtJH8PoVT1p1+9jCaXB9 qC1IfYUkjx5UMeXANfIWWi3UZXvGgr7dIRyM7LP3dgOPu/dkdZa6vqxo2hsqFn1+nRHp 7m3A==
X-Gm-Message-State: AOJu0YzSzCQSvXONBARMTd8EQjZCJQeNVU0oZRIzko+OzxYEZ0yjMG5V /fqUYZXouykplW7TtSzm22YFKbnxrWIIE8AlbUc3mnkBK8ay+V963jnSXPWf23T4VMieRfT25E2 9HxHRmKFV4t2Y5NNaCNPDq499ro74bIj2u/vwQq0eNGlmThAq5Q==
X-Google-Smtp-Source: AGHT+IFYt7bemQ1aTvdXhH7Z+naigshAjOvGKefHHsh9rPflUpL+0+XfKUuJ/QdSpfjnQFHGIInrqT5UHqsFWizAYng=
X-Received: by 2002:a05:6808:1250:b0:3c3:de8e:5411 with SMTP id o16-20020a056808125000b003c3de8e5411mr12755803oiv.38.1712672005875; Tue, 09 Apr 2024 07:13:25 -0700 (PDT)
MIME-Version: 1.0
References: <171266895066.29309.10741453889474510706@ietfa.amsl.com>
In-Reply-To: <171266895066.29309.10741453889474510706@ietfa.amsl.com>
From: Nick Buraglio <buraglio@forwardingplane.net>
Date: Tue, 09 Apr 2024 09:13:15 -0500
Message-ID: <CACMsEX8oW3ezo3UUN4H0uZZ6iStL-R77ihWGBby0HkY2+eHy_w@mail.gmail.com>
To: ipv6@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Y7ZY2M0lS9TpyZqlCta9Nr9Les8>
Subject: Re: [IPv6] I-D Action: draft-ietf-6man-rfc6724-update-08.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2024 14:13:31 -0000

We have published -08 of the rfc6724 update, this fixes some
formatting and other typographical oversights
The following sections address comments from the lis (difft from -06
to -08 is the most useful comparison):
https://author-tools.ietf.org/iddiff?url1=draft-ietf-6man-rfc6724-update-06&url2=draft-ietf-6man-rfc6724-update-08&difftype=--html


Brief overview of the changes from -06:

Section 2:
Add terminology section and define known-local

Section 3:
Add section on elevating
upgrades the requirement in RFC 6724 for nodes to insert a higher
precedence entry in the policy table for observed ULA prefixes that
are known to be local, referred to in this document as "known-local"
ULAs, from a MAYto a SHOULD.

Section 4:
Changes the 6to4 prefix deprecation to match Teredo, adds further
clarity and reference to RFC6724 section 10.7

Section 5:
Add text to upgrade the requirement to automatically insert
known-local ULAs into a node's policy table from a MAY to a SHOULD.

Section 5.3
Further define insertion and removal parameters and requirements for
known-local ULA prefixes into table and associated values and label

Section 7.2:
Further clarify GUA-GUA preferred over ULA-ULA details

Section 7.3:
Further clarify ULA-ULA preferred over IPv4-IPv4 details

Section 8:
Housekeeping and formatting changes

Section 9.2:
Describe the new known-local interaction and how it addresses issues
with ULAs in global DNS



Further copy edit and housekeeping.

Thanks!