[tao-discuss] Re: Further re-use of Tao content
Jay Daley <exec-director@ietf.org> Fri, 12 July 2024 15:56 UTC
Return-Path: <jay@staff.ietf.org>
X-Original-To: tao-discuss@ietfa.amsl.com
Delivered-To: tao-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8962C169422 for <tao-discuss@ietfa.amsl.com>; Fri, 12 Jul 2024 08:56:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=staff-ietf-org.20230601.gappssmtp.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 lsOApKkiRmsQ for <tao-discuss@ietfa.amsl.com>; Fri, 12 Jul 2024 08:56:38 -0700 (PDT)
Received: from mail-wm1-x32d.google.com (mail-wm1-x32d.google.com [IPv6:2a00:1450:4864:20::32d]) (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 481DDC1654F3 for <tao-discuss@ietf.org>; Fri, 12 Jul 2024 08:56:38 -0700 (PDT)
Received: by mail-wm1-x32d.google.com with SMTP id 5b1f17b1804b1-4277a5ed48bso15822005e9.2 for <tao-discuss@ietf.org>; Fri, 12 Jul 2024 08:56:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20230601.gappssmtp.com; s=20230601; t=1720799796; x=1721404596; darn=ietf.org; h=message-id:in-reply-to:to:references:date:subject:mime-version :content-transfer-encoding:from:from:to:cc:subject:date:message-id :reply-to; bh=BFgeJ+zINVeJpD5pSFdKDXsJFTfZlxsbwhHPkEFXMxU=; b=FDaH+b5cr2cwLk4hj7wZyur5209uZgGNcWhRTze1wJmBk/pmZhxlw45Ck42EyjyHfm J5OqLchxcHzv765kslzJzZflar7rciP0kHDD3M1HJte7XZZTNhaYtLVFzxyJTw35oDmV jZ+HHr6HXVo4I9llg1rrmvdGH80mm3nOSm5hPEhFJhS2286TRpZ2XwRFRPYd29BMDiEo 5KLy/TFTWw4Lzkv4v5D/jia7xBtYfiYXr7bQt4DMFmIzywZO1Udr+PDwIcqwItSZ5kUe yjqexuS6CsC/LyUWm+Ka1+UrZqxIIs0UndouyyOIL2p6OlnUMd9BRuJJobBtY0ZKQ3y9 5rWQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1720799796; x=1721404596; h=message-id:in-reply-to:to:references:date:subject:mime-version :content-transfer-encoding:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=BFgeJ+zINVeJpD5pSFdKDXsJFTfZlxsbwhHPkEFXMxU=; b=aA3kmckp8gIHGUtNPnC6LRXru7KiFzj0aUj7zk93YqPSAM5Wu+jQ/PIOs74yhTrOpA odFvGdv+HhfZipc1z3prgLyZyufJDPbfS6UUAnglvYe7KsYE8Ft/V8sKKk6UUfcFIn1L Pu7O3ZAUPfg6NYvRg+SLW1OIbEtzzUZxMdHxTkrNTdhYBB30SoD4io0wNdZEKGqhkWpt lj7WunlObZNbz4q7OpNsxUK93UxkOsVlr7Q7uZOD/ozPCip44XOieblxUV+4xcLvVJvh /t8CB1iMjkzFF8ATFAss0WqdBbOqgUwse3BuCVBVmRddAsTg1a1Ef9ldCZEpsoHrolqv oRoA==
X-Gm-Message-State: AOJu0YwbYxBAyVGJEdEaV/0b3gEKHG+9Zeb5/5X0kOsPXyhClalqRiR5 zJRWjZw4r+h9XJGNDGpHKTcyA56P7aW6UZNg+YYZHj+mwExKCl0zydDxO9YRsLPPE1WPpVyPeWR D2pKavg==
X-Google-Smtp-Source: AGHT+IEF9S951CVs5DrTkMx4DYoXGH35GZ71KdJk66N9GPDPJ6jxPWcx3lNA2tUcFKHpwU2AkdNNIg==
X-Received: by 2002:a05:600c:5349:b0:426:6861:a1ab with SMTP id 5b1f17b1804b1-426708f19a9mr76252195e9.39.1720799796182; Fri, 12 Jul 2024 08:56:36 -0700 (PDT)
Received: from smtpclient.apple ([92.27.125.209]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-4279f24901csm27892295e9.9.2024.07.12.08.56.35 for <tao-discuss@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 Jul 2024 08:56:35 -0700 (PDT)
From: Jay Daley <exec-director@ietf.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
Date: Fri, 12 Jul 2024 16:56:25 +0100
References: <23DC27E1-68C8-48AE-8768-1435AFC73B6C@ietf.org>
To: tao-discuss@ietf.org
In-Reply-To: <23DC27E1-68C8-48AE-8768-1435AFC73B6C@ietf.org>
Message-Id: <A235988F-7418-4E1D-9D2E-26C80563AFE1@ietf.org>
X-Mailer: Apple Mail (2.3774.600.62)
Message-ID-Hash: P6S2YF4RY5WC2ZJQGER25AWAH5CS2AJP
X-Message-ID-Hash: P6S2YF4RY5WC2ZJQGER25AWAH5CS2AJP
X-MailFrom: jay@staff.ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tao-discuss.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [tao-discuss] Re: Further re-use of Tao content
List-Id: Discussion of the Tao of the IETF <tao-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tao-discuss/d_cjDAbdBFcWPcolvzo06Fkvbg8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tao-discuss>
List-Help: <mailto:tao-discuss-request@ietf.org?subject=help>
List-Owner: <mailto:tao-discuss-owner@ietf.org>
List-Post: <mailto:tao-discuss@ietf.org>
List-Subscribe: <mailto:tao-discuss-join@ietf.org>
List-Unsubscribe: <mailto:tao-discuss-leave@ietf.org>
To follow up The page "About RFCs" (https://www.ietf.org/process/rfcs/) has now been updated with content drawn from primarily the Tao, and also including the previous "Getting Started" content and the previous content of that page. Jay > On 13 Jun 2024, at 22:13, Jay Daley <exec-director@ietf.org> wrote: > > As per previous emails, this is to update you on progress on reuse of Tao content in other pages. > > 1. The main revised page is "Bringing new work to the IETF" (was "Proposing new work") https://www.ietf.org/process/new-work/. This includes Tao content and content from multiple other pages that covered the same subject. > > One point to note though, the IETF Chair has questioned if the following bullet should still be included, particularly the part about XML, or if that needs to be made clearer: > >> * **Is this an Internet-layer protocol or related operational best practice?**. The IETF does not standardize transmission hardware (we leave that to organizations like the IEEE and the ITU) and does not standardize specialized application layer protocols. For example, we leave HTML and XML standards to the World-Wide Web Consortium. But the IETF does standardize all the protocol layers in between, from IP itself up to general applications like email and HTTP. > > 2. The content about IPR has now been included at the end of https://www.ietf.org/process/ipr/ > > 3. The entire section on WGs was included in https://www.ietf.org/process/wgs/ some time ago. > > 4. The liaison content has not been reused because https://www.ietf.org/about/liaisons/ already covers it. > > I expect to make one more update on the remaining Tao content to be reused and then that’s it. > > JAy > > -- > Jay Daley > IETF Executive Director > exec-director@ietf.org > -- Jay Daley IETF Executive Director exec-director@ietf.org