Re: [rfc-i] I-D Action: draft-rpc-rfc7322bis-00.txt

Brian E Carpenter <> Thu, 04 May 2023 23:05 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 686D9C16B5A2 for <>; Thu, 4 May 2023 16:05:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Status: No, score=-2.099 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, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id KDS9SRFmkwXt for <>; Thu, 4 May 2023 16:05:35 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::436]) (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 (Postfix) with ESMTPS id B7434C151989 for <>; Thu, 4 May 2023 16:05:35 -0700 (PDT)
Received: by with SMTP id d2e1a72fcca58-6439e6f5a33so65501b3a.2 for <>; Thu, 04 May 2023 16:05:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20221208; t=1683241535; x=1685833535; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=rsBgGvdm+WI/12TSjEqEDQh/0PcWa7v0QXVrdG7Wmdw=; b=iB7SvHP25cRYjuOI9XhqmpTSXHBHc3gyd2lH3BWeOLYZVgF8RzWCGqZzDcc3DLqIru ci9D8RWx24foqt+3uhxVi7FMiTSXAAcY/BthRxhhtR+1O1mjYazAlqeH2Jtd4LvoLcJ9 6sgAQFFsasjkS9wFdGUwm7ae9K/PNApqWozHetzHhl6SKKBYqI6wDorN+9zUgodBdhVz ja6Xe62vJThx8N2zrX7uCE4NVHM7k7J8W1bJh8k1eNYu76yGZMQ86YG37KlEQN4g0HEp eUjDl7/XZqlHBoXM5JAN+rp+/e8ggoqUPFX2+//RyavCKK6Epzxlp404icfZVDV1VJ7K VTWw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20221208; t=1683241535; x=1685833535; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=rsBgGvdm+WI/12TSjEqEDQh/0PcWa7v0QXVrdG7Wmdw=; b=Mrjr+ghJjJTJYMpl5pfmRFAtr5krOKsROSpcPUum4VkxW1cpq6A9kZJxa/Wt1edsRL seg/N0t6n3yQOolWV3XXJBcWN7L/xpIvuR0qomiq5N4YI0nHU0E84bCkTYq0c8yejhKt meJOfLcjY4Wvy+3BDG904gk2/Am93fzAL7V6BymwWL38Ej4b8HTwGUTg1pHTwuEeUomc +DwIcxnxXHFPqk78wIGZiXU6NgFhjfE0Kp1AA5L+XQhnhT5aTWeDN4ebNOn5zCgEqTOz Nq241EYGxwPiUYmpzdoTBuUzVxHkrXhs1PqovX3jnlneSxKRax44lY4nkiazbF4abLyj /vZg==
X-Gm-Message-State: AC+VfDxzcmSiqhCU7HW1UEXdJFRNuaV0TlHPlcvMHPMmC2SMqhmBy8Vd 4MhU/6afmkocoCUOkZaXCEz06lv9pzBXHA==
X-Google-Smtp-Source: ACHHUZ4B/VdOiJHd6NcYbPP5z3wFpCft1vv16KFbifNZa41ymMbsuXVoim2KbJOP3hqcMtddbtTcGA==
X-Received: by 2002:a05:6a20:3d19:b0:ef:85a6:464b with SMTP id y25-20020a056a203d1900b000ef85a6464bmr4951328pzi.14.1683241534861; Thu, 04 May 2023 16:05:34 -0700 (PDT)
Received: from ?IPV6:2406:e003:1184:f001:9991:d1ad:8c20:42bd? ([2406:e003:1184:f001:9991:d1ad:8c20:42bd]) by with ESMTPSA id x4-20020a63db44000000b0050f93a3586fsm200869pgi.37.2023. (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 04 May 2023 16:05:34 -0700 (PDT)
Message-ID: <>
Date: Fri, 05 May 2023 11:05:29 +1200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: Jean Mahoney <>, RFC Interest <>
References: <> <> <> <>
From: Brian E Carpenter <>
In-Reply-To: <>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [rfc-i] I-D Action: draft-rpc-rfc7322bis-00.txt
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 04 May 2023 23:05:37 -0000

On 05-May-23 03:16, Jean Mahoney wrote:
> Hi all,
> The I-D draft-rpc-rfc7322bis replaces draft-flanagan-7322bis. 

Thanks Jean. I had a look at the diffs since RFC7322 itself and
most of them seem fine to me. Some quibbles, however:

> Angle brackets are strongly recommended around URIs [STD66], e.g.,	
> <>

I understand the need for a delimiter, but I have a use case where
the intent is to refer to a URI as a string, so ""
is much more appropriate. Could that be:

   Delimiters such as angle brackets are strongly recommended...

As a matter of fact, STD66 says this:

    In practice, URIs are delimited in a variety of ways, but usually
    within double-quotes "", angle brackets
    <>, or just by using whitespace:

so double quotes are just as "legal" as angle brackets.

> The use of HTTPS rather than HTTP is strongly encouraged.

I'm not sure that is an editorial or style issue. Also, it should
never lead to an editorial change, only to a query, since there
may be cases where HTTP is intended. Again, I have a use case in
a current draft.

> 7.  A citation may A) follow the subject to which the citation	
> applies or B) be read as part of the text.  For example:	
>  a.  As part of the transition to IPv6, NAT64 [RFC6146] and DNS64	
>      [RFC6147] technologies will be utilized by some access	
>      networks to provide IPv4 connectivity for IPv6-only nodes	
>      [RFC6144].	
>  b.  Note that SAVI raises a number of important privacy	
>      considerations that are discussed more fully in [RFC6959].	
> 8.  For a document referenced multiple times in running text, the	
>     citation anchor must be at first use outside the abstract.	
>     Additional citations are allowed at the author's discretion.	
> We recommend using A) and strongly recommend consistent use of one	
> style throughout.

A nit here is that the "We recommend" sentence should surely be part
of item 7, not after item 8. More substantively, I don't agree with
the *strong* recommendation for consistency. I agree that A) is generally
better practice, but in a long document, cases where B) leads to more
readable text can occur. Something like:

   We recommend using A) in most cases, and limiting B) to cases where
   it enhances readability.