IETF Logo Mail Archive

Re: [Tools-discuss] draft submitted source versions

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 23 November 2019 00:01 UTC

Return-Path: <brian.e.carpenter@gmail.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 0DA9F120227 for <tools-discuss@ietfa.amsl.com>; Fri, 22 Nov 2019 16:01:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=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=gmail.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 W5pRvVWpPWnE for <tools-discuss@ietfa.amsl.com>; Fri, 22 Nov 2019 16:01:41 -0800 (PST)
Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com [IPv6:2607:f8b0:4864:20::531]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC77F12022C for <tools-discuss@ietf.org>; Fri, 22 Nov 2019 16:01:41 -0800 (PST)
Received: by mail-pg1-x531.google.com with SMTP id 207so4093326pge.8 for <tools-discuss@ietf.org>; Fri, 22 Nov 2019 16:01:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=YlWl+xI1wi/jTNrNqZiNekzz5oI0V2alMJjcTMK6WLI=; b=tHRhoc13mNKOFFq8l7cY2MGrSKOs82CEi750Hbtg5C4o9nPN7hj/AZbqvYuuFBVgZL vazgv2snAFVL1HiwerJQC0sw7/DPJ9YC0s5ZlJCfxzuw5vNT6IlaDgMZdeDMaWY2aQ6l U+R0i8VT7MEOs2zuptErF4UsJm6K+NiBYAjRjmSb0XboUzlP5zUmNq1YFZ4PnBg4Y+5F cleIR1Abu87zg3/lTFnTCh6uAtxSjEhZripaHA31ASlxMOjZFFmmggOCFwvganuNhPOC OWrb4oLTLXaGJr9YCZVZnq+g35VGcB6AQWvksPD0a+rHZN7z6Lea9DJ+M7oVXcvz1O19 9DBg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=YlWl+xI1wi/jTNrNqZiNekzz5oI0V2alMJjcTMK6WLI=; b=jxMMMOlxuLuh0f2OTLeyJSGfEv54Op1Tbx6lBzs9/byJszSn6Rr5cA86mSgS1Y+0A0 ImJQjpPYTHMIIiVyLuYjM3J6cfOmUZFnPRBhIwvoEHy+8Ldkt23JSAT1l/ut8RCvooFc Plh9rGUKevYPSKyehKD4JtFICiGbHcuWNtaB9BoDgN/X5d8C5OMVqnKp4LeMHMc3KM3W Ri3H1qsxg1IexATcbnHSHbzT/Uzhl53FnOY7SNYPe6KCwmlQX/Nh3z5c5FHcMlccw4gy HaXE2LWVPaRJnIQKOIuTBtcmUq84Fp3molc51zYVChdG1z/BkhQFJl29ymZMJS/V7hSs yh8Q==
X-Gm-Message-State: APjAAAUc0Z4cOef1NmAI02F/20IDj3AQ3XO/lQwZHF6wxgiwOReHIMxe mYG1KwxwMdXqPhuoo6Hfzl0jQFHY
X-Google-Smtp-Source: APXvYqyub4sFOlW+UYqMAOHtZeS/Ko4RP+UxjFpNGpI7/9ad2ZaDY41h42m42sTvQBn/98TjWtO09Q==
X-Received: by 2002:a62:8748:: with SMTP id i69mr20831876pfe.224.1574467300967; Fri, 22 Nov 2019 16:01:40 -0800 (PST)
Received: from [172.16.154.50] ([101.100.166.3]) by smtp.gmail.com with ESMTPSA id c9sm8443843pfn.65.2019.11.22.16.01.39 for <tools-discuss@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 Nov 2019 16:01:40 -0800 (PST)
To: tools-discuss@ietf.org
References: <20191122164625.6C831F406D4@rfc-editor.org> <8811A5B6-AF57-458D-8F67-CEF314E2B107@bangj.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <bfb1185f-dd96-b3ef-11dc-919f7657bf6e@gmail.com>
Date: Sat, 23 Nov 2019 13:01:39 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <8811A5B6-AF57-458D-8F67-CEF314E2B107@bangj.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/Y8nwtdkCa8dTkstKrp6iFEQ1I9I>
Subject: Re: [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: Sat, 23 Nov 2019 00:01:44 -0000

On 23-Nov-19 07:39, Tom Pusateri wrote:
> 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?

Well, before answering that, I have two supplementary questions.

1. What happens if the author submits a.xml and a.txt, but the xml file doesn't convert properly?

2. What happens if the author submits a.xml and a.txt, but the converted xml file is different from a.txt?

    Brian
> 
> Thanks,
> Tom
> 
> 
>> Begin forwarded message:
>>
>> *From: *rfc-editor@rfc-editor.org <mailto: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 <mailto:pusateri@bangj.com>, cheshire@apple.com <mailto:cheshire@apple.com>
>> *Cc: *dnssd-ads@ietf.org <mailto:dnssd-ads@ietf.org>, dnssd-chairs@ietf.org <mailto:dnssd-chairs@ietf.org>, rfc-editor@rfc-editor.org <mailto:rfc-editor@rfc-editor.org>, tjw.ietf@gmail.com <mailto:tjw.ietf@gmail.com>, evyncke@cisco.com <mailto: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
>>
> 
> 
> ___________________________________________________________
> Tools-discuss mailing list
> Tools-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-discuss
> 
> Please report datatracker.ietf.org and mailarchive.ietf.org
> bugs at http://tools.ietf.org/tools/ietfdb
> or send email to datatracker-project@ietf.org
> 
> Please report tools.ietf.org bugs at
> http://tools.ietf.org/tools/issues
> or send email to webmaster@tools.ietf.org
>

v2.23.0 | Report a Bug | By Email