Re: [xml2rfc] new ID cited in another document

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Wed, 10 October 2018 20:02 UTC

Return-Path: <prvs=182158bea4=jordi.palet@consulintel.es>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5463B1277D2 for <xml2rfc@ietfa.amsl.com>; Wed, 10 Oct 2018 13:02:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es
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 puJqUpS6y3gZ for <xml2rfc@ietfa.amsl.com>; Wed, 10 Oct 2018 13:02:53 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F206D1277BB for <xml2rfc@ietf.org>; Wed, 10 Oct 2018 13:02:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1539201771; x=1539806571; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:CC:Message-ID:Thread-Topic:References: In-Reply-To:Mime-version:Content-type:Content-transfer-encoding; bh=MrfIWLJ+HMOxdlthoweZUx46LkljWHKLSPyvDOqIE7U=; b=kbZtHss9kQJ9C D8M/uTvubcJaWqrOZ4r+RACjHk9Oa+/LZ2yhP8cOSs9L0iUl71QnC+DWRD1ma+dA AJp+NfzJN86r4B4ilxX4qPycKGGIO5xodeV0zMVQMVnsGyyv96NhxowjTbeyUelx MkX8XieBvpV6VNf3J1dPy6vg7GkROM=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Wed, 10 Oct 2018 22:02:51 +0200
X-Spam-Processed: mail.consulintel.es, Wed, 10 Oct 2018 22:02:48 +0200
Received: from [10.10.10.129] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50005903587.msg for <xml2rfc@ietf.org>; Wed, 10 Oct 2018 22:02:48 +0200
X-MDRemoteIP: 2001:470:1f09:495:cca4:18ed:69ee:7fb7
X-MDHelo: [10.10.10.129]
X-MDArrival-Date: Wed, 10 Oct 2018 22:02:48 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=182158bea4=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: xml2rfc@ietf.org
User-Agent: Microsoft-MacOutlook/10.10.2.180910
Date: Wed, 10 Oct 2018 22:02:46 +0200
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: Henrik Levkowetz <henrik@levkowetz.com>
CC: xml2rfc@ietf.org
Message-ID: <9844EA49-58BA-4E88-B677-C85F565CAE35@consulintel.es>
Thread-Topic: [xml2rfc] new ID cited in another document
References: <36D5B8D0-9383-43E2-B34A-97A252B3D766@consulintel.es> <23fdab64-3a97-865d-46bf-461a4e2b3775@levkowetz.com>
In-Reply-To: <23fdab64-3a97-865d-46bf-461a4e2b3775@levkowetz.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/uSybtAo92eR1OxXCki2jUS0vvJE>
Subject: Re: [xml2rfc] new ID cited in another document
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Oct 2018 20:02:55 -0000

Hi Henrik,

It worked just waiting, thanks a lot!

Regards,
Jordi
 
 

-----Mensaje original-----
De: Henrik Levkowetz <henrik@levkowetz.com>
Fecha: miércoles, 10 de octubre de 2018, 21:50
Para: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Asunto: Re: [xml2rfc] new ID cited in another document

    Hi Jordi,
    
    On 2018-10-10 20:56, JORDI PALET MARTINEZ wrote:
    > Hi,
    > 
    > I've submitted some minutes ago a new document
    > (draft-bp-v6ops-ipv6-ready-dns-dnssec-00).
    > 
    > This document is being cited by another document, using <xref
    > target="I-D.bp-v6ops-ipv6-ready-dns-dnssec"/>
    > 
    > And I've, at Informative References section: <?rfc
    > include="reference.I-D.bp-v6ops-ipv6-ready-dns-dnssec.xml" ?>
    > 
    > I'm using the same format in the same and other documents and it
    > works, but in this case, when I use the xml2rfc to make a txt
    > version, I get:
    > 
    > INPUT: Line 1610: Unable to resolve external request:
    > "reference.I-D.bp-v6ops-ipv6-ready-dns-dnssec.xml"
    > 
    > If I try to submit it, get "An exception occurred when trying to
    > process the XML file:"
    > 
    > There is any delay so citations get indexed or something like?
    
    Yes.  New reference files are generated once per hour (unless the machine
    is heavily loaded; then there can be delays).
    
    I just checked, and the reference file has been generated and is available
    on the server now.
    
    Now, if xml2rfc tried to fetch the reference file before it was available,
    the local cache may remember that, and wait for the cache to time out.
    
    If you don't get better results now that the file is available on the
    server, you should ask xml2rfc to clear its local cache with the command:
    
      xml2rfc --clear-cache
    
    
    Best regards,
    
    	Henrik
    
    
    



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.