IETF Logo Mail Archive

Re: [rfc-i] Citing internet drafts

S Moonesamy <sm+ietf@elandsys.com> Wed, 04 September 2019 10:29 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 BFEC51200CE for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Wed, 4 Sep 2019 03:29:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.751
X-Spam-Level:
X-Spam-Status: No, score=-4.751 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=4ZbtU/ju; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=Nu5gVu3/
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 3kM93EidmTuI for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Wed, 4 Sep 2019 03:28:59 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B97D012001B for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Wed, 4 Sep 2019 03:28:59 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 478E1B80C6D; Wed, 4 Sep 2019 03:28:38 -0700 (PDT)
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 49722B80C6D for <rfc-interest@rfc-editor.org>; Wed, 4 Sep 2019 03:28:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=4ZbtU/ju; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=Nu5gVu3/
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 XRxkMLJQlW75 for <rfc-interest@rfc-editor.org>; Wed, 4 Sep 2019 03:28:34 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by rfc-editor.org (Postfix) with ESMTP id A6941B80C6C for <rfc-interest@rfc-editor.org>; Wed, 4 Sep 2019 03:28:34 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.148.199]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id x84ASd7e005679 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 4 Sep 2019 03:28:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1567592932; x=1567679332; bh=QPqsz9ocuK5uRO1Zyytk6mkea2xJYTk1VNxOPb4AHfA=; h=Date:To:From:Subject:In-Reply-To:References; b=4ZbtU/juH+cs/8KHVMaXoi1zLEEjeYVLMbGQvt6HA1ZXJtxfHTlo0AnKTg2GKSC+z A5f+HMuTFPWre5RoKz8yecX/wgrKnw6gK0ha4Xdl30LZICz40jasKbmAlFMU8kV0yG JQT5pBq1XCPxsZBiZ6UMvLXZiM3bofL3Vt64n6kY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1567592932; x=1567679332; i=@elandsys.com; bh=QPqsz9ocuK5uRO1Zyytk6mkea2xJYTk1VNxOPb4AHfA=; h=Date:To:From:Subject:In-Reply-To:References; b=Nu5gVu3/+dQu9UbuVsr8uhbPNg3xmgHHODOKWjzdlqmaPdXSDcrL29EtfruO+92Xo /t2X7qs5UV0JgtgLz+l911U+33ByYes21xHcCAdDTo0s8ahPpqlZkCppaTOEskNRlE /d0bBGunmsRxZCoFGFIhk95Tkoc8X/+y0wEHKWCs=
Message-Id: <6.2.5.6.2.20190904030920.0ebad2a0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 04 Sep 2019 03:28:02 -0700
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, rfc-interest@rfc-editor.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <f9792cff-da1c-a779-629b-cd8b1480e63c@alum.mit.edu>
References: <9dca07bd-293c-7f1e-0cbc-c0a9907d09c2@gmx.de> <f9792cff-da1c-a779-629b-cd8b1480e63c@alum.mit.edu>
Mime-Version: 1.0
Subject: Re: [rfc-i] Citing internet drafts
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

Hi Paul,
At 08:01 AM 03-09-2019, Paul Kyzivat wrote:
>IIUC the restriction that references to drafts must be informational 
>only applies to *RFC*s? It is important that *drafts* be able to 
>normatively reference other drafts as they progress in parallel, 
>with the limitation that they will be forced to progress together, 
>at which point they will become references to RFCs. Right?

I'll use draft-ietf-pim-yang as an example.  The last normative 
reference is to
draft-ietf-bfd-yang.  The publication of draft-ietf-pim-yang as a RFC 
has to be delayed until draft-ietf-pim-yang is ready for publication.

Regards,
S. Moonesamy 

_______________________________________________
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