IETF Logo Mail Archive

Re: [rfc-i] <seriesInfo>

Sandy Ginoza <sginoza@amsl.com> Mon, 28 February 2022 16:39 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AF533A0C3B; Mon, 28 Feb 2022 08:39:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.662
X-Spam-Level:
X-Spam-Status: No, score=-2.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NN87nwESFwNd; Mon, 28 Feb 2022 08:38:58 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DF0E3A0B02; Mon, 28 Feb 2022 08:38:58 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 080643BA85; Mon, 28 Feb 2022 08:38:58 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 30A9F3BA85 for <rfc-interest@rfc-editor.org>; Mon, 28 Feb 2022 08:38:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wj3eozPR-UeR for <rfc-interest@rfc-editor.org>; Mon, 28 Feb 2022 08:38:56 -0800 (PST)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) by rfc-editor.org (Postfix) with ESMTPS id 922043BA82 for <rfc-interest@rfc-editor.org>; Mon, 28 Feb 2022 08:38:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 8A537427C643; Mon, 28 Feb 2022 08:38:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LacZrIHMnFLD; Mon, 28 Feb 2022 08:38:56 -0800 (PST)
Received: from smtpclient.apple (2603-8000-9603-b513-bc5e-334b-c3a3-c211.res6.spectrum.com [IPv6:2603:8000:9603:b513:bc5e:334b:c3a3:c211]) by c8a.amsl.com (Postfix) with ESMTPSA id 6694A427C640; Mon, 28 Feb 2022 08:38:56 -0800 (PST)
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Sandy Ginoza <sginoza@amsl.com>
In-Reply-To: <c8b2346c-a514-469f-e00a-cb986e680b94@mozilla.com>
Date: Mon, 28 Feb 2022 08:38:55 -0800
Cc: Julian Reschke <julian.reschke@gmx.de>, rfc-interest@rfc-editor.org
Message-Id: <42CBFE97-A632-44CB-B07D-B9772356711F@amsl.com>
References: <b4fe646c-ea7c-eba0-70fd-0805d07e3fe8@mozilla.com> <620d425a-3842-8e65-114e-bc24eb0669e2@gmx.de> <c8b2346c-a514-469f-e00a-cb986e680b94@mozilla.com>
To: Peter Saint-Andre <stpeter@mozilla.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Subject: Re: [rfc-i] <seriesInfo>
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

Hi Peter, Julian,

> On Aug 4, 2021, at 11:09 AM, Peter Saint-Andre <stpeter@mozilla.com> wrote:
> 
>> If the use case is to augment a *reference* with more data - why hasn't
>> it be used for that? This really needs a proper design with clear use
>> cases, and the solution optimally should not ne specific for IETF
>> documents (hint: there's already <refcontent>).
> 
> Well, @stream hasn't been used in reference files, which is partly why I
> think we can remove it from seriesInfo entirely.

Stream info doesn’t currently appear in references, but it is proposed in draft-flanagan-7322bis.  
See <https://www.ietf.org/archive/id/draft-flanagan-7322bis-07.html#section-4.8.6.1>.

Thanks,
Sandy 


_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest

v2.23.0 | Report a Bug | By Email