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

Nick Buraglio <buraglio@forwardingplane.net> Tue, 21 November 2023 19: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 CD22FC151981 for <ipv6@ietfa.amsl.com>; Tue, 21 Nov 2023 11:13:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 4WzQQthtvxxi for <ipv6@ietfa.amsl.com>; Tue, 21 Nov 2023 11:13:49 -0800 (PST)
Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (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 3A374C14CE4B for <ipv6@ietf.org>; Tue, 21 Nov 2023 11:13:49 -0800 (PST)
Received: by mail-qt1-x82c.google.com with SMTP id d75a77b69052e-41ccd38eaa5so912531cf.0 for <ipv6@ietf.org>; Tue, 21 Nov 2023 11:13:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=forwardingplane.net; s=google; t=1700594028; x=1701198828; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=jTe0lur7RI/B6V4aAS12Tg86ldzn8ihhc9aAIPmixhU=; b=sL3oGCGfpsExyXufBNYmHf5alVHuADcqe2zGw4btQNpy+5X25wFO0WLXwpGU3bfXBL ydeHH7gyGAWUQynOVzNLwCmoT9GMlen0kAt2xANGg1JatTwbVaR6GVreTsyhk/8Al/1L ovRxw4DZBbekGExzZev0J9sds04relbXBvm2o=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700594028; x=1701198828; h=cc: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=jTe0lur7RI/B6V4aAS12Tg86ldzn8ihhc9aAIPmixhU=; b=P5o8bXN1JTackr7iuAoFVg7CVy0Lei/Tx9MdN/UC66oCQ7PSS3xTdJnXx67KrAkRur QzzJeuK6D3s5wdmK44nqLtzMoeSz0IvHu+huXEskcBSfgqfag2PPYSLz17Jk3JBgfI+V RgbD/nSjRHivr+JqVPsu4pgQKwrKMco8nONR82tAHaOxijNmx0YDtM1JJ90h99WqpuSQ 0KO+vbFsZ4wXK5ORIUbnGhFPreHviyz4BgSnrtJ9pR71I4y6u/I4u13TOTuUl9a4c7l1 +t5Rtv+TXivqtoBQkZRmh7xyr4OMVUXBRX6bGkzXlz6yiaDVeNKRLH6N4Gq1rJe9ij8K RxMA==
X-Gm-Message-State: AOJu0Yy50S7/k9HdzSsH+BZGvegJeFmQ8zBqErqVX2kdI7M1PY9piQnx F/fFPgWIdY2nTUhJcuyQ2pmHsbZaUCla1XNO1eG9VA==
X-Google-Smtp-Source: AGHT+IEIGqljzY+To86r//DPbVW+XmD8E2ohCoR9D9ZP6PRlGG30y2WAQ+lwXThOSaeprS1ikxEdhv2WcitxJFaZNDw=
X-Received: by 2002:ac8:7f13:0:b0:41e:7f76:57ec with SMTP id f19-20020ac87f13000000b0041e7f7657ecmr5622034qtk.15.1700594028384; Tue, 21 Nov 2023 11:13:48 -0800 (PST)
MIME-Version: 1.0
References: <170059183545.4282.16453796503536671445@ietfa.amsl.com>
In-Reply-To: <170059183545.4282.16453796503536671445@ietfa.amsl.com>
From: Nick Buraglio <buraglio@forwardingplane.net>
Date: Tue, 21 Nov 2023 13:13:37 -0600
Message-ID: <CACMsEX_RhsLq1eX5d6m0w93zjLdTNOmuK1-FqVvN3DRCoQkpVQ@mail.gmail.com>
To: 6man Chairs <6man-chairs@ietf.org>
Cc: 6man WG <ipv6@ietf.org>, Tim Chown <tjc.ietf@gmail.com>, Jeremy Duncan <jduncan@tachyondynamics.com>
Content-Type: multipart/alternative; boundary="000000000000f828ed060aae663f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/8lEDZuvHDW_FWmadFVOZxzJFvAM>
Subject: [IPv6] Fwd: I-D Action: draft-ietf-6man-rfc6724-update-04.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, 21 Nov 2023 19:13:52 -0000

Chairs,

We have updated our draft to reflect feedback from the list as well as from
IETF 118 and respectfully request consideration for WGLC. We believe this
addresses the input and the problems it is aimed at remedying.

Thanks,

Nick, Jeremy, Tim

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Tue, Nov 21, 2023 at 12:37 PM
Subject: [IPv6] I-D Action: draft-ietf-6man-rfc6724-update-04.txt
To: <i-d-announce@ietf.org>
Cc: <ipv6@ietf.org>


Internet-Draft draft-ietf-6man-rfc6724-update-04.txt is now available. It
is a
work item of the IPv6 Maintenance (6MAN) WG of the IETF.

   Title:   Preference for IPv6 ULAs over IPv4 addresses in RFC6724
   Authors: Nick Buraglio
            Tim Chown
            Jeremy Duncan
   Name:    draft-ietf-6man-rfc6724-update-04.txt
   Pages:   11
   Dates:   2023-11-21

Abstract:

   This document updates [RFC6724] based on operational experience
   gained since its publication over ten years ago.  In particular it
   updates the precedence of Unique Local Addresses (ULAs) in the
   default address selection policy table, which as originally defined
   by [RFC6724] has lower precedence than legacy IPv4 addressing.  The
   update places both IPv6 Global Unicast Addresses (GUAs) and ULAs
   ahead of all IPv4 addresses on the policy table to better suit
   operational deployment and management of ULAs in production.  In
   updating the [RFC6724] default policy table, this document also
   demotes the preference for 6to4 addresses.  These changes to default
   behavior improve supportability of common use cases such as, but not
   limited to, automatic / unmanaged scenarios.  It is recognized that
   some less common deployment scenarios may require explicit
   configuration or custom changes to achieve desired operational
   parameters.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-rfc6724-update/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-6man-rfc6724-update-04

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-6man-rfc6724-update-04

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


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