[Tools-discuss] draft submitted source versions

Tom Pusateri <pusateri@bangj.com> Fri, 22 November 2019 18:39 UTC

Return-Path: <pusateri@bangj.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCDAC120856 for <tools-discuss@ietfa.amsl.com>; Fri, 22 Nov 2019 10:39:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bangj.com
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 bXZspDw-hlNk for <tools-discuss@ietfa.amsl.com>; Fri, 22 Nov 2019 10:39:53 -0800 (PST)
Received: from oj.bangj.com (69-77-154-174.static.skybest.com [69.77.154.174]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F0E412089D for <Tools-discuss@ietf.org>; Fri, 22 Nov 2019 10:39:53 -0800 (PST)
Received: from [172.16.10.110] (mta-107-13-246-59.nc.rr.com [107.13.246.59]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id 8C3E82EF01 for <Tools-discuss@ietf.org>; Fri, 22 Nov 2019 13:39:52 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bangj.com; s=201907; t=1574447992; bh=wp963ONACBQLKAvfbp186w4XzrvQWuZvYiFbzRYObbs=; h=From:Subject:References:To:Date:From; b=U9/3fbXyhM0iFL9S02BSxEoUErBQ3mzbZcngLYAkiunbfhrjnxq45GFakry/CW3C9 5m4w5PIo4gYMBa6vU+Gxs6UHdILa4rhDQr8KBIwRol2eUEkWrOj5jygjz3oo27x/xi XKmQiG4hnsMyXzgSntUFgrzj1WSb/tKgcH9jgPe/FYv5yV81F9z9xOPVZtMv5G2ae+ Mbdlgp9MgU8EcQfJm6Z2Z+sJu4I/+dFYOc8Q51R4Poea23SmrqwwGe8e8EteRuAvg0 zba4I3eamKtXTxKGnxNctkXHv0bu9pP0KlfoIB+ed+Qizv5s3ztSfBm54mEv/tgagf w8/TDaufEH8YA==
From: Tom Pusateri <pusateri@bangj.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_279CEB94-B45D-4B22-B429-04935AFB4C2A"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Message-Id: <8811A5B6-AF57-458D-8F67-CEF314E2B107@bangj.com>
References: <20191122164625.6C831F406D4@rfc-editor.org>
To: Tools-discuss@ietf.org
Date: Fri, 22 Nov 2019 13:39:51 -0500
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/S3Wi6Xk_g8lV4eVtOjKDQ2PnVr8>
Subject: [Tools-discuss] draft submitted source versions
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Nov 2019 18:39:56 -0000

Is there anyway to tell if the TXT version was created from the submitted XML or was uploaded separately?

If an XML version is submitted, is there any reason to allow DRAFT AUTHORS to submit alternate versions still?

Thanks,
Tom


> Begin forwarded message:
> 
> From: rfc-editor@rfc-editor.org
> Subject: [RFC State] <draft-ietf-dnssd-push-25> has been added to the RFC Editor database
> Date: November 22, 2019 at 11:46:25 AM EST
> To: pusateri@bangj.com, cheshire@apple.com
> Cc: dnssd-ads@ietf.org, dnssd-chairs@ietf.org, rfc-editor@rfc-editor.org, tjw.ietf@gmail.com, evyncke@cisco.com
> 
> Author(s),
> 
> We have received notice that your document draft-ietf-dnssd-push-25 has
> been approved for publication as an RFC.  The document has
> been added to the RFC Editor queue and you can check the status at
> <https://www.rfc-editor.org/current_queue.php>
> 
> If you submitted your XML file using the I-D submission tool, we have
> already retrieved it.  If you did not submit the XML file via the I-D
> submission tool, or if you have an updated version (e.g., updated
> contact information), please send us the XML file at this time.  Please
> attach the file and specify any differences between the approved I-D 
> and the document that the XML produces.  We recommend using xml2rfc
> <http://xml2rfc.ietf.org/> to create your document.
> 
> This should help increase the pace with which documents move through
> the RFC Editor queue. 
> 
> Please let us know if you have any questions.
> 
> Thank you.
> 
> The RFC Editor Team
>