[dtn] WG Subject Lines
"Birrane, Edward J." <Edward.Birrane@jhuapl.edu> Thu, 01 June 2023 18:41 UTC
Return-Path: <Edward.Birrane@jhuapl.edu>
X-Original-To: dtn@ietfa.amsl.com
Delivered-To: dtn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 931C8C14CE52 for <dtn@ietfa.amsl.com>; Thu, 1 Jun 2023 11:41:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.396
X-Spam-Level:
X-Spam-Status: No, score=-4.396 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_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=jhuapl.edu
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 r4x6fJj3KoGH for <dtn@ietfa.amsl.com>; Thu, 1 Jun 2023 11:41:16 -0700 (PDT)
Received: from aplegw02.jhuapl.edu (aplegw02.jhuapl.edu [128.244.251.169]) (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 0BC7EC14CEE3 for <dtn@ietf.org>; Thu, 1 Jun 2023 11:41:15 -0700 (PDT)
Received: from pps.filterd (aplegw02.jhuapl.edu [127.0.0.1]) by aplegw02.jhuapl.edu (8.17.1.19/8.17.1.19) with ESMTP id 351CCqEj030336; Thu, 1 Jun 2023 14:41:13 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jhuapl.edu; h=from : to : cc : subject : date : message-id : content-type : content-transfer-encoding : mime-version; s=JHUAPLDec2018; bh=9f9uL4oYWO7Fj1ejoAcG9RercuK4d79Syqe1GrJWJlI=; b=VjCJdyXwJfRPC9NMzAT1Ep1lUuM3kLm+6QwBSaRcatzscDhdqxMpBqsYNM2W3C7RZCh+ mIzmMpkbUJeguwoIFAQsIQxk5yBn0pSMFqDj8mlqGDRkHQyUuRR2AnWZiKEqEoizcyfh ymQt0A/fi/kQFpdh4B+Qg3wwj9LSo+a4nyPU5Tf7cucLX/38vTkNEqh8rsG4R0IjG4Xx wHjSTXNZt/2Vy80JPVE//NQtAZve/eosnA9RROh1FN9mx8j1ylB33PaE7s27BxOcglnR 8WDLZP/qh41JXBJmnP3qVpI9AcSBdkglzqFZiLZ7IgvLnkS7EwuZiZTvWQ4rv0Z/hG0W /Q==
Received: from aplex26.dom1.jhuapl.edu (aplex26.dom1.jhuapl.edu [10.114.162.11]) by aplegw02.jhuapl.edu (PPS) with ESMTPS id 3que2xn57a-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 01 Jun 2023 14:41:13 -0400
Received: from APLEX21.dom1.jhuapl.edu (10.114.162.6) by APLEX26.dom1.jhuapl.edu (10.114.162.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.26; Thu, 1 Jun 2023 14:41:13 -0400
Received: from APLEX21.dom1.jhuapl.edu ([fe80::20d7:9545:f01e:9b2]) by APLEX21.dom1.jhuapl.edu ([fe80::20d7:9545:f01e:9b2%5]) with mapi id 15.02.1118.026; Thu, 1 Jun 2023 14:41:13 -0400
From: "Birrane, Edward J." <Edward.Birrane@jhuapl.edu>
To: "scott@solarnetone.org" <scott@solarnetone.org>, Zaheduzzaman Sarker <zahed.sarker.ietf@gmail.com>
CC: Rick Taylor <rick@tropicalstormsoftware.com>, "dtn@ietf.org" <dtn@ietf.org>
Thread-Topic: WG Subject Lines
Thread-Index: AdmUuH0KRd5LRtjkQBS9BK2Oz3K3cw==
Date: Thu, 01 Jun 2023 18:41:12 +0000
Message-ID: <442feec0f6a6499dab4bf3437bd281c8@jhuapl.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.162.19]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CrossPremisesHeadersFilteredBySendConnector: APLEX26.dom1.jhuapl.edu
X-OrganizationHeadersPreserved: APLEX26.dom1.jhuapl.edu
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.254,Aquarius:18.0.957,Hydra:6.0.573,FMLib:17.11.176.26 definitions=2023-06-01_08,2023-05-31_03,2023-05-22_02
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/Q9lAsW1mrWYNpTR4wf9E8oPllvI>
Subject: [dtn] WG Subject Lines
X-BeenThere: dtn@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Delay Tolerant Networking \(DTN\) discussion list at the IETF." <dtn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtn>, <mailto:dtn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtn/>
List-Post: <mailto:dtn@ietf.org>
List-Help: <mailto:dtn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtn>, <mailto:dtn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jun 2023 18:41:20 -0000
Scott J., Moving the discussion on subject naming to an easier to track subject name. > As a matter of process, is it not general practice to notably and > prominently include [Last-Call] in the subject of any mail making a last > call announcement concerning a draft, as below, or is that a function of > datatracker for the ietf-announce list, or something that comes later in > the process? > > Subject: [Last-Call] Dnsdir last call review of draft-ietf-dnssd-srp-20 There is not a requirement for naming subjects in this way at the WG level. For example: Subject: WG Last Call: IPN URI Scheme (April 16th - May 4th, 2023) Subject: WGLC consensus on draft-ietf-dtn-ipn-update-04.txt Neither of these subject lines conform to that practice (and that is OK). The convention you are referring to is applied later in the process. The archive of IETF last calls can be found at: https://mailarchive.ietf.org/arch/browse/last-call/. If you search on bpbis or bpsec you can see the history of these documents after they left WG review. -Ed --- Edward J. Birrane, III, Ph.D. (he/him/his) Chief Engineer, Space Constellation Networking Supervisor, Embedded Applications Group Space Exploration Sector Johns Hopkins Applied Physics Laboratory (W) 443-778-7423 / (F) 443-228-3839
- [dtn] WG Subject Lines Birrane, Edward J.
- Re: [dtn] WG Subject Lines scott