[IPv6] Second Working Group Last Call for <draft-ietf-6man-rfc6724-update>

Bob Hinden <bob.hinden@gmail.com> Wed, 10 April 2024 15:29 UTC

Return-Path: <bob.hinden@gmail.com>
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 0A5C7C14F68A for <ipv6@ietfa.amsl.com>; Wed, 10 Apr 2024 08:29:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.094
X-Spam-Level:
X-Spam-Status: No, score=-7.094 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_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 (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rcL-juqhbb5P for <ipv6@ietfa.amsl.com>; Wed, 10 Apr 2024 08:29:12 -0700 (PDT)
Received: from mail-yw1-x112f.google.com (mail-yw1-x112f.google.com [IPv6:2607:f8b0:4864:20::112f]) (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 3B7A8C14F616 for <ipv6@ietf.org>; Wed, 10 Apr 2024 08:29:12 -0700 (PDT)
Received: by mail-yw1-x112f.google.com with SMTP id 00721157ae682-61814e68cfcso34055967b3.0 for <ipv6@ietf.org>; Wed, 10 Apr 2024 08:29:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712762951; x=1713367751; darn=ietf.org; h=message-id:to:cc:references:date:subject:mime-version:from:from:to :cc:subject:date:message-id:reply-to; bh=rzFrMfUxAjJ3Yu/9673azmQB3Pd/vt3WnyULHosV96E=; b=EmjMqOMXDJ0SJSFVgSYUTVBjQ81MZKJJpM4K79mVE4+93P2it2aWjkYa/TBTnPqfsN jUXV9woA/TiyiI+/BIcic31m4DzPCDheipVsD6aFq0HLz5AUOYV7FNMRkEhziS18pHS9 QbGBq7bK6hprk15m5ejl5AQZJoSDX3wdQnCMbwbkaMXJsUcz7rDifGDLspuruNBVvHS9 6LI8gPYRpD179zo0Ao6+3Xgtgj7kiGckHs4oVfr3pdbXBbtqzu55ocqXv65DVGw9vwzs k4cmpm55EcTltYfFV7DuBCGyZTTyC4tIIFI+g0GyjMQjtwzKmAUDC8p8VF0ecWQrZCro oG5Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712762951; x=1713367751; h=message-id:to:cc:references:date:subject:mime-version:from :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=rzFrMfUxAjJ3Yu/9673azmQB3Pd/vt3WnyULHosV96E=; b=seRkKL9yz7eVcQvvUb0yIJS5jKPvOwKnU2UDOsljQo4OIM5+YTqxRFoNLIWS5HQp4k lioFM4e0PWlXQlPGuE01FcIg9B+/RVWR50QY1IJmItRL51lQxebT8TR7SbcDQwle3hXl MQxDakH30Ee0lNME9pmQs/lGmL1E/uAEOAdK+IefnOzxFAY9JFFoW0edovOwCrYeRD/7 3WyC5VcrDqsmO2PYu83JLeTvlz+eiR9Jqx/886I0WykfvkNx+GDscL3vDF7AzECtJhXB LhVx437n6zNTdDqA6LrcYVqU+DT/jkJJLKpPTgyZ2whjrTLJjq1m7JfqnGzYl+PswOnm e4rg==
X-Gm-Message-State: AOJu0YxjqUhB7KAtyAd2s261XrtjMCiFG5gDXUnqBN/NpteptecTXOn4 UyUdzRg9jzdD2oIlEhXiQZ2dYbEfm9eiOPW9adPV/n/qFI2P4LAZv61WRWM1
X-Google-Smtp-Source: AGHT+IELTcnnVIMHHOgJMCTfpOhzx8fS6BzXxvicLWlmdKR2JLeXqgPv5tr2eaOhu936UWuy+CUv4Q==
X-Received: by 2002:a0d:e692:0:b0:614:3042:6364 with SMTP id p140-20020a0de692000000b0061430426364mr3137766ywe.19.1712762950553; Wed, 10 Apr 2024 08:29:10 -0700 (PDT)
Received: from smtpclient.apple (99-31-208-116.lightspeed.sntcca.sbcglobal.net. [99.31.208.116]) by smtp.gmail.com with ESMTPSA id j9-20020a81fe09000000b006156ced7476sm2674132ywn.62.2024.04.10.08.29.09 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Apr 2024 08:29:10 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4B3931FE-1415-4BAB-99D7-3F010E7E8228"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
Date: Wed, 10 Apr 2024 08:28:48 -0700
References: <6A5E5F35-B35F-4358-8EE1-3BD82329141E@jisc.ac.uk>
Cc: Bob Hinden <bob.hinden@gmail.com>, Jen Linkova <furry13@gmail.com>, Ole Trøan <otroan@employees.org>
To: IPv6 List <ipv6@ietf.org>
Message-Id: <6FBC1B5A-BF28-4B05-B2B2-A60DA4707755@gmail.com>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/rsOANfXJLox4G_8c_8eIbxDqf2E>
Subject: [IPv6] Second Working Group Last Call for <draft-ietf-6man-rfc6724-update>
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: Wed, 10 Apr 2024 15:29:16 -0000

Given the number of changes since the first w.g. last call, the chairs, in consultation with the authors, are staring a second 6MAN working group last call for this document.

This email starts a second two week 6MAN Working Group Last Call on advancing "Preference for IPv6 ULAs over IPv4 addresses in RFC6724" document

    https://datatracker.ietf.org/doc/draft-ietf-6man-rfc6724-update/

 as a Standards Track document.

A summary of changes since the -06 version is below.   A good diff to review is:

https://author-tools.ietf.org/iddiff?url1=draft-ietf-6man-rfc6724-update-08&url2=draft-ietf-6man-rfc6724-update-06&difftype=--html

[New draft on left due to line length problem with old draft]

Substantive comments and statements of support for publishing this document should be directed to the ipv6@ietf.org mailing list. Editorial suggestions can be sent to the authors.  This last call will end on 24 April 2024 23:59 UTC.

Also, one issue the authors would like feedback on is if the requirement is a SHOULD or MUST for inserting known-local ULA prefixes into their policy table with a precedence above both GUAs and IPv4, while leaving all other general ULAs at a lower precedence.  It is a SHOULD in the -08 draft, but there has been support for a MUST in the discussion. 

Bob, Jen, Ole
6MAN chairs


> Begin forwarded message:
> 
> From: Tim Chown <Tim.Chown=40jisc.ac.uk@dmarc.ietf.org>
> Subject: Re: [IPv6] I-D Action: draft-ietf-6man-rfc6724-update-08.txt
> Date: April 9, 2024 at 7:47:57 AM PDT
> To: IPv6 List <ipv6@ietf.org>
> 
> Hi,
> 
> Actually it works better I notice with 08 on the left and 06 on the right, as -06 has the broken formatting, so please check the diff from -06 to the current -08 using:
> 
> https://author-tools.ietf.org/iddiff?url1=draft-ietf-6man-rfc6724-update-08&url2=draft-ietf-6man-rfc6724-update-06&difftype=--html
> 
> The changes are largely around making the MAY insert local entries into a SHOULD insert known-locals, with a little more text on how we’d determine those.
> 
> Tim
> 
>> On 9 Apr 2024, at 15:13, Nick Buraglio <buraglio@forwardingplane.net> wrote:
>> 
>> 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!
>> 
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------