From tools-discuss-bounces@ietf.org  Thu Apr 10 07:31:08 2008
Return-Path: <tools-discuss-bounces@ietf.org>
X-Original-To: tools-discuss-archive@megatron.ietf.org
Delivered-To: ietfarch-tools-discuss-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5E3743A6DA7;
	Thu, 10 Apr 2008 07:31:08 -0700 (PDT)
X-Original-To: tools-discuss@core3.amsl.com
Delivered-To: tools-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E7E173A6D34
	for <tools-discuss@core3.amsl.com>;
	Thu, 10 Apr 2008 07:31:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level: 
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[AWL=-0.680, 
	BAYES_05=-1.11]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Va4ytUfAG9qU for <tools-discuss@core3.amsl.com>;
	Thu, 10 Apr 2008 07:31:06 -0700 (PDT)
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2])
	by core3.amsl.com (Postfix) with ESMTP id 10B4D3A6F25
	for <tools-discuss@ietf.org>; Thu, 10 Apr 2008 07:31:06 -0700 (PDT)
Received: from list by ciao.gmane.org with local (Exim 4.43)
	id 1Jjxo9-0005ez-Fh
	for tools-discuss@ietf.org; Thu, 10 Apr 2008 14:31:22 +0000
Received: from hmbg-d9b88e17.pool.mediaways.net ([217.184.142.23])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <tools-discuss@ietf.org>; Thu, 10 Apr 2008 14:31:21 +0000
Received: from nobody by hmbg-d9b88e17.pool.mediaways.net with local (Gmexim
	0.1 (Debian)) id 1AlnuQ-0007hv-00
	for <tools-discuss@ietf.org>; Thu, 10 Apr 2008 14:31:21 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: tools-discuss@ietf.org
From: "Frank Ellermann" <nobody@xyzzy.claranet.de>
Date: Thu, 10 Apr 2008 16:33:56 +0200
Organization: <http://purl.net/xyzzy>
Lines: 15
Message-ID: <ftl8be$dgt$1@ger.gmane.org>
Mime-Version: 1.0
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: hmbg-d9b88e17.pool.mediaways.net
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1914
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914
Subject: [Tools-discuss] I-D.ietf-eai-dsn
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>,
	<mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tools-discuss-bounces@ietf.org
Errors-To: tools-discuss-bounces@ietf.org

Hi, <http://tools.ietf.org/wg/eai/> shows a tracker link for
<http://tools.ietf.org/wg/eai/draft-ietf-eai-dsn/>, but the
<http://tools.ietf.org/html/draft-ietf-eai-dsn-06.txt> page
doesn't.  

Trying to figure out what rfcmarkup does, this can't happen,
in <http://tools.ietf.org/draft/draft-ietf-eai-dsn/now> I
see a "docidnum", "docphase" doesn't begin with "ID-Exists":

Rfcmarkup 1.62 never run for this draft after the PubReq,
the old HTML page was apparently created by version 1.58.

Is the code calling rfcmarkup 1.62 also visible somewhere ?

 Frank

_______________________________________________
Tools-discuss mailing list
Tools-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss


From tools-discuss-bounces@ietf.org  Thu Apr 10 09:27:02 2008
Return-Path: <tools-discuss-bounces@ietf.org>
X-Original-To: tools-discuss-archive@megatron.ietf.org
Delivered-To: ietfarch-tools-discuss-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9881328C1C8;
	Thu, 10 Apr 2008 09:27:02 -0700 (PDT)
X-Original-To: tools-discuss@core3.amsl.com
Delivered-To: tools-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 579F63A6D3A
	for <tools-discuss@core3.amsl.com>;
	Thu, 10 Apr 2008 09:27:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.362
X-Spam-Level: 
X-Spam-Status: No, score=-2.362 tagged_above=-999 required=5 tests=[AWL=0.237, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ZkSvxH9lqmzw for <tools-discuss@core3.amsl.com>;
	Thu, 10 Apr 2008 09:26:56 -0700 (PDT)
Received: from merlot.tools.ietf.org (unknown
	[IPv6:2a01:3f0:0:31:214:22ff:fe21:bb])
	by core3.amsl.com (Postfix) with ESMTP id 2F9EE3A6D4A
	for <tools-discuss@ietf.org>; Thu, 10 Apr 2008 09:26:55 -0700 (PDT)
Received: from localhost ([127.0.0.1]:36982 helo=chardonnay.local)
	by merlot.tools.ietf.org with esmtp (Exim 4.69)
	(envelope-from <henrik@levkowetz.com>)
	id 1Jjzbw-00056R-WD; Thu, 10 Apr 2008 18:26:53 +0200
Message-ID: <47FE3FCC.3010103@levkowetz.com>
Date: Thu, 10 Apr 2008 18:26:52 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
References: <ftl8be$dgt$1@ger.gmane.org>
In-Reply-To: <ftl8be$dgt$1@ger.gmane.org>
X-Enigmail-Version: 0.95.6
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com,
	tools-discuss@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on merlot.tools.ietf.org);
	SAEximRunCond expanded to false
Cc: tools-discuss@ietf.org
Subject: Re: [Tools-discuss] I-D.ietf-eai-dsn
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>,
	<mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tools-discuss-bounces@ietf.org
Errors-To: tools-discuss-bounces@ietf.org

Hi Frank,

On 2008-04-10 16:33 Frank Ellermann said the following:
> Hi, <http://tools.ietf.org/wg/eai/> shows a tracker link for
> <http://tools.ietf.org/wg/eai/draft-ietf-eai-dsn/>, but the
> <http://tools.ietf.org/html/draft-ietf-eai-dsn-06.txt> page
> doesn't.  
> 
> Trying to figure out what rfcmarkup does, this can't happen,
> in <http://tools.ietf.org/draft/draft-ietf-eai-dsn/now> I
> see a "docidnum", "docphase" doesn't begin with "ID-Exists":
> 
> Rfcmarkup 1.62 never run for this draft after the PubReq,
> the old HTML page was apparently created by version 1.58.
> 
> Is the code calling rfcmarkup 1.62 also visible somewhere ?

What results in calling rfcmarkup is pretty convoluted; to
put it simply (hmm), there's the 404 script which generates the
html version if none exist, then there's a cron job which
removes old conversions after some time, to make the features
of new rfcmarkup versions gradually be applied, and finally
there are scripts which remove html versions when something
significant has happened, like publication of an RFC, which
should be reflected also in the htmlized version of the draft.

It's quite possible that I've simply missed setting up the
removal of htmlized drafts at the point when they are sent
to the IESG, and a [Tracker] link should appear -- I'll have
to go and look.

(Of course, the short answer to your question, which won't
be nearly as helpful, is `rsync rsync.tools.ietf.org::`. )


Regards,

	Henrik
_______________________________________________
Tools-discuss mailing list
Tools-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss


From tools-discuss-bounces@ietf.org  Thu Apr 10 09:57:54 2008
Return-Path: <tools-discuss-bounces@ietf.org>
X-Original-To: tools-discuss-archive@megatron.ietf.org
Delivered-To: ietfarch-tools-discuss-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9F63F3A6A8D;
	Thu, 10 Apr 2008 09:57:54 -0700 (PDT)
X-Original-To: tools-discuss@core3.amsl.com
Delivered-To: tools-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 431463A6B5D
	for <tools-discuss@core3.amsl.com>;
	Thu, 10 Apr 2008 09:57:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.56
X-Spam-Level: 
X-Spam-Status: No, score=-2.56 tagged_above=-999 required=5 tests=[AWL=0.039, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id C0hKb4pmaoZt for <tools-discuss@core3.amsl.com>;
	Thu, 10 Apr 2008 09:57:45 -0700 (PDT)
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2])
	by core3.amsl.com (Postfix) with ESMTP id 78C6E3A6A8D
	for <tools-discuss@ietf.org>; Thu, 10 Apr 2008 09:57:45 -0700 (PDT)
Received: from list by ciao.gmane.org with local (Exim 4.43)
	id 1Jk069-0005Td-8h
	for tools-discuss@ietf.org; Thu, 10 Apr 2008 16:58:05 +0000
Received: from hmbg-d9b88e17.pool.mediaways.net ([217.184.142.23])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <tools-discuss@ietf.org>; Thu, 10 Apr 2008 16:58:05 +0000
Received: from nobody by hmbg-d9b88e17.pool.mediaways.net with local (Gmexim
	0.1 (Debian)) id 1AlnuQ-0007hv-00
	for <tools-discuss@ietf.org>; Thu, 10 Apr 2008 16:58:05 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: tools-discuss@ietf.org
From: "Frank Ellermann" <nobody@xyzzy.claranet.de>
Date: Thu, 10 Apr 2008 19:00:36 +0200
Organization: <http://purl.net/xyzzy>
Lines: 20
Message-ID: <ftlguf$lmg$1@ger.gmane.org>
References: <ftl8be$dgt$1@ger.gmane.org> <47FE3FCC.3010103@levkowetz.com>
Mime-Version: 1.0
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: hmbg-d9b88e17.pool.mediaways.net
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1914
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914
Subject: Re: [Tools-discuss] I-D.ietf-eai-dsn
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>,
	<mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tools-discuss-bounces@ietf.org
Errors-To: tools-discuss-bounces@ietf.org

Henrik Levkowetz wrote:
 
>> Is the code calling rfcmarkup 1.62 also visible somewhere ?
[okay, bad question, see below]

> It's quite possible that I've simply missed setting up the
> removal of htmlized drafts at the point when they are sent
> to the IESG, and a [Tracker] link should appear -- I'll have
> to go and look.

It's not that simple, it worked for the two other EAI drafts.
 
> Of course, the short answer to your question, which won't
> be nearly as helpful, is `rsync rsync.tools.ietf.org::`.

I forgot to mention "visible for V.90 users", rsync won't
do, I don't want to start a fourth IETF tools server at home
for modem fans... ;-)

 Frank

_______________________________________________
Tools-discuss mailing list
Tools-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss


From tools-discuss-bounces@ietf.org  Wed Apr 23 15:40:19 2008
Return-Path: <tools-discuss-bounces@ietf.org>
X-Original-To: tools-discuss-archive@megatron.ietf.org
Delivered-To: ietfarch-tools-discuss-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D26583A6C07;
	Wed, 23 Apr 2008 15:40:19 -0700 (PDT)
X-Original-To: tools-discuss@core3.amsl.com
Delivered-To: tools-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5194A3A6C07
	for <tools-discuss@core3.amsl.com>;
	Wed, 23 Apr 2008 15:40:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id yPtRwuI-8LBv for <tools-discuss@core3.amsl.com>;
	Wed, 23 Apr 2008 15:40:17 -0700 (PDT)
Received: from mail203.messagelabs.com (mail203.messagelabs.com
	[216.82.254.243])
	by core3.amsl.com (Postfix) with ESMTP id 697D63A67A5
	for <tools-discuss@ietf.org>; Wed, 23 Apr 2008 15:40:17 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-10.tower-203.messagelabs.com!1208990414!7372682!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.128.141]
Received: (qmail 29324 invoked from network); 23 Apr 2008 22:40:15 -0000
Received: from sbcsmtp9.sbc.com (HELO flph161.enaf.ffdc.sbc.com)
	(144.160.128.141)
	by server-10.tower-203.messagelabs.com with AES256-SHA encrypted SMTP;
	23 Apr 2008 22:40:15 -0000
Received: from enaf.ffdc.sbc.com (localhost.localdomain [127.0.0.1])
	by flph161.enaf.ffdc.sbc.com (8.14.2/8.14.2) with ESMTP id
	m3NMeL5W006976
	for <tools-discuss@ietf.org>; Wed, 23 Apr 2008 15:40:22 -0700
Received: from klph001.kcdc.att.com (klph001.kcdc.att.com [135.188.3.11])
	by flph161.enaf.ffdc.sbc.com (8.14.2/8.14.2) with ESMTP id
	m3NMeH7Q006955
	for <tools-discuss@ietf.org>; Wed, 23 Apr 2008 15:40:17 -0700
Received: from kcdc.att.com (localhost.localdomain [127.0.0.1])
	by klph001.kcdc.att.com (8.14.0/8.14.0) with ESMTP id m3NMeHFM031836
	for <tools-discuss@ietf.org>; Wed, 23 Apr 2008 17:40:17 -0500
Received: from maillennium.att.com (dns.maillennium.att.com [135.25.114.99])
	by klph001.kcdc.att.com (8.14.0/8.14.0) with ESMTP id m3NMeCCO031584
	for <tools-discuss@ietf.org>; Wed, 23 Apr 2008 17:40:12 -0500
Received: from [135.210.32.184] (unknown[135.210.32.184](misconfigured sender))
	by maillennium.att.com (mailgw1) with ESMTP
	id <20080423224011gw100l7o6qe> (Authid: tony);
	Wed, 23 Apr 2008 22:40:11 +0000
Message-ID: <480FBB16.9020603@att.com>
Date: Wed, 23 Apr 2008 18:41:26 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: tools-discuss@ietf.org
X-Enigmail-Version: 0.95.6
Cc: Bill Fenner <fenner@gmail.com>, Henrik Levkowetz <henrik@levkowetz.com>,
	Glen Barney <glen@amsl.com>
Subject: [Tools-discuss] xml version of 1id-abstracts.txt/1id-index.txt and
	all_id.txt
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>,
	<mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tools-discuss-bounces@ietf.org
Errors-To: tools-discuss-bounces@ietf.org

There was some discussion recently of having an xml version of the 
internet-drafts files 1id-*.txt and all_id.txt.

Moving this further along, I'd like to make concrete proposals for the 
schema for such files. First off, for 1id-abstract, the schema would be 
(I'm not an expert at DTDs, so forgive any errors here):

<!ELEMENT internet-drafts (docs working-group-map)>
   <!ELEMENT docs (doc*)>
     <!ELEMENT doc (name, author, date, wg, file, abstract?)>
       <!ELEMENT name (#PCDATA)>
       <!ELEMENT author (#PCDATA)>
       <!ELEMENT date (#PCDATA)>
       <!ELEMENT wg (#PCDATA)>
       <!ELEMENT file (#PCDATA)>
       <!ELEMENT abstract (#PCDATA)>
   <!ELEMENT working-group-map (group*)>
     <!ELEMENT group (acronym, name)>
       <!ELEMENT acronym (#PCDATA)>
       <!ELEMENT name (#PCDATA)>

Translation:
   <internet-drafts> contains <docs> and <working-group-map>
   <docs> contains 1 or more <doc>
   <doc> contains a <name>, <author>, <date>, <wg>, <file> and <abstract>
   The <wg> contains a working group acronym.
   At the end is a map from working group acronyms to spelled out names.
   <working-group-map> contains 1 or more <group>
   Each <group> contains an <acronym> and <name>.

A sample would look like this:

     <?xml version='1.0' encoding='UTF-8'?>
     <internet-drafts>
     <docs>
     <doc>
      <name>Transmission of IP over Ethernet over IEEE
       802.16 Networks</name>	
      <author>HongSeok Jeon</author>
      <date>18-Apr-08</date>
      <wg>16ng</wg>
      <file>draft-ietf-16ng-ip-over-ethernet-over-802.16-06.txt</file>
      <abstract>
       This document describes the transmission of IPv4 over ...
     </doc>
     ...
     </docs>
     <working-group-map>
     <wg>
      <acronym>16ng</acronym>
      <name>IP over IEEE 802.16 Networks</name>
     </wg>
     <wg>
      <acronym>6man</acronym>
      <name>IPv6 Maintenance</name>
     </wg>
     ...
     </working-group-map>
     </internet-drafts>

A complete sample file can be seen at
    http://merlot.tools.ietf.org/~tonyh/internet-drafts/1id-abstracts.xml

For all_id.xml, I'm proposing this schema:

<!ELEMENT all-internet-drafts (id*)>
   <!ELEMENT id (file, date, status, tracker?, iesg?, by?, rfc?)>
     <!ELEMENT file (#PCDATA)>
     <!ELEMENT date (#PCDATA)>
     <!ELEMENT status (#PCDATA)>
     <!ELEMENT tracker (#PCDATA)>
     <!ELEMENT iesg (#PCDATA)>
     <!ELEMENT by (#PCDATA)>
     <!ELEMENT rfc (#PCDATA)>

Translation:
   <all-internet-drafts> contains one or more <id>
   Each <id> contains a <file>, a <date>, and a <status>
   Depending on the value of <status>, there may be a <tracker>, a
   <iesg>, a <by> and a <rfc>.

A sample would look like this:

   <all-internet-drafts>
     <id>
       <file>draft-adolf-dvb-urn-03</file>
       <date>2007-12-18</date>
       <status>In IESG processing</status>
       <iesg>Revised ID Needed</iesg>
     </id>
     <id>
       <file>draft-cain-post-inch-phishingextns-03</file>
       <date>2007-10-25</date>
       <status>In IESG processing</status>
       <tracker>Publication Requested</tracker>
     </id>
     <id>
       <file>draft-zorn-radius-port-type-04</file>
       <date>2006-04-04</date>
       <status>RFC</status>
       <rfc>4603</rfc>
     </id>
     <id><file>draft-yokota-mipshop-3gfh-02</file>
       <date>2008-03-03</date>
       <status>Replaced</status>
       <by>draft-ietf-mipshop-3gfh</by>
     </id>
   </all-internet-drafts>

A complete sample file can be seen at
    http://merlot.tools.ietf.org/~tonyh/internet-drafts/all_id.xml

Thoughts?

	Tony Hansen
	tony@att.com
_______________________________________________
Tools-discuss mailing list
Tools-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss


From tools-discuss-bounces@ietf.org  Wed Apr 23 17:02:53 2008
Return-Path: <tools-discuss-bounces@ietf.org>
X-Original-To: tools-discuss-archive@megatron.ietf.org
Delivered-To: ietfarch-tools-discuss-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8E6283A697E;
	Wed, 23 Apr 2008 17:02:53 -0700 (PDT)
X-Original-To: tools-discuss@core3.amsl.com
Delivered-To: tools-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 15F3B3A697E
	for <tools-discuss@core3.amsl.com>;
	Wed, 23 Apr 2008 17:02:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id neiGtNbTcTyl for <tools-discuss@core3.amsl.com>;
	Wed, 23 Apr 2008 17:02:52 -0700 (PDT)
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2])
	by core3.amsl.com (Postfix) with ESMTP id F3EB23A67B6
	for <tools-discuss@ietf.org>; Wed, 23 Apr 2008 17:02:50 -0700 (PDT)
Received: from list by ciao.gmane.org with local (Exim 4.43)
	id 1JoovK-0006WU-T2
	for tools-discuss@ietf.org; Thu, 24 Apr 2008 00:02:50 +0000
Received: from hmbg-d9b88e16.pool.mediaways.net ([217.184.142.22])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <tools-discuss@ietf.org>; Thu, 24 Apr 2008 00:02:50 +0000
Received: from nobody by hmbg-d9b88e16.pool.mediaways.net with local (Gmexim
	0.1 (Debian)) id 1AlnuQ-0007hv-00
	for <tools-discuss@ietf.org>; Thu, 24 Apr 2008 00:02:50 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: tools-discuss@ietf.org
From: "Frank Ellermann" <nobody@xyzzy.claranet.de>
Date: Thu, 24 Apr 2008 02:05:28 +0200
Organization: <http://purl.net/xyzzy>
Lines: 44
Message-ID: <fuoimv$7d4$1@ger.gmane.org>
References: <480FBB16.9020603@att.com>
Mime-Version: 1.0
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: hmbg-d9b88e16.pool.mediaways.net
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1914
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914
Subject: Re: [Tools-discuss] xml version of 1id-abstracts.txt/1id-index.txt
	andall_id.txt
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>,
	<mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tools-discuss-bounces@ietf.org
Errors-To: tools-discuss-bounces@ietf.org

Tony Hansen wrote:
 
>      <!ELEMENT doc (name, author, date, wg, file, abstract?)>

Maybe one or more <author>, and an optional <wg>.  Why is the
<abstract> optional ?

>      <!ELEMENT group (acronym, name)>
>        <!ELEMENT acronym (#PCDATA)>
>        <!ELEMENT name (#PCDATA)>

Matter of taste.  I'd use an attribute 'wg' as IDREF with an
attribute 'acronym' as ID, with that trick an undefined 'wg'
triggers a validation error.  

You have no intended status element, is that as it should be ?

>      <wg>
>       <acronym>6man</acronym>
>       <name>IPv6 Maintenance</name>
>      </wg>

ITYM <group> in this example.  With my idea you would get
<group acronym="6man"> IPv6 Maintenance </group> here.

===
>        <status>In IESG processing</status>
>        <iesg>Revised ID Needed</iesg>
[...]
>        <status>In IESG processing</status>
>        <tracker>Publication Requested</tracker>

I'm not sure about that.  Why not use the terminology
in <https://datatracker.ietf.org/idtracker/help/state/> ?

"PubReq" is no substate of "IESG evaluation", it comes
before "AD evaluation" and "Last Call", both before the
"IESG evaluation".

AFAIK "Revised ID needed" is a generic substate, it
can happen outside of "IESG evaluation", e.g., in the
"AD evaluation".

 Frank

_______________________________________________
Tools-discuss mailing list
Tools-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss


From tools-discuss-bounces@ietf.org  Thu Apr 24 10:06:54 2008
Return-Path: <tools-discuss-bounces@ietf.org>
X-Original-To: tools-discuss-archive@megatron.ietf.org
Delivered-To: ietfarch-tools-discuss-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5922B3A6CBD;
	Thu, 24 Apr 2008 10:06:54 -0700 (PDT)
X-Original-To: tools-discuss@core3.amsl.com
Delivered-To: tools-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 495CD3A6CEA
	for <tools-discuss@core3.amsl.com>;
	Thu, 24 Apr 2008 10:06:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.899
X-Spam-Level: 
X-Spam-Status: No, score=-4.899 tagged_above=-999 required=5
	tests=[AWL=-1.300, BAYES_00=-2.599, J_CHICKENPOX_22=0.6,
	J_CHICKENPOX_52=0.6, J_CHICKENPOX_62=0.6, J_CHICKENPOX_82=0.6,
	J_CHICKENPOX_92=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zYXieudKBmnZ for <tools-discuss@core3.amsl.com>;
	Thu, 24 Apr 2008 10:06:51 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id 26F2E3A6CBD
	for <tools-discuss@ietf.org>; Thu, 24 Apr 2008 10:06:50 -0700 (PDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m3OH6Xd1015952; Thu, 24 Apr 2008 20:06:36 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 24 Apr 2008 20:06:32 +0300
Received: from vaebe104.NOE.Nokia.com ([10.160.244.59]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 24 Apr 2008 20:06:31 +0300
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 24 Apr 2008 20:06:30 +0300
Message-ID: <1696498986EFEC4D9153717DA325CB7271D47E@vaebe104.NOE.Nokia.com>
In-Reply-To: <480FBB16.9020603@att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Tools-discuss] xml version of 1id-abstracts.txt/1id-index.txt
	andall_id.txt
Thread-index: Acilkwk/gknOyys+Q7WtuXdMrWDNPwAmHsZg
References: <480FBB16.9020603@att.com>
From: <Pasi.Eronen@nokia.com>
To: <tony@att.com>, <tools-discuss@ietf.org>
X-OriginalArrivalTime: 24 Apr 2008 17:06:31.0870 (UTC)
	FILETIME=[8B2BC5E0:01C8A62D]
X-Nokia-AV: Clean
Cc: fenner@gmail.com, henrik@levkowetz.com, glen@amsl.com
Subject: Re: [Tools-discuss] xml version of 1id-abstracts.txt/1id-index.txt
	andall_id.txt
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>,
	<mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tools-discuss-bounces@ietf.org
Errors-To: tools-discuss-bounces@ietf.org

Here's a sample from the code I currently have:

<id xml:id="draft-ietf-xcon-framework">
  <id>draft-ietf-xcon-framework</id>
  <documentInfo>
    <docValidity>Active</docValidity>
    <revision>10</revision>
    <revisionDate>2007-11-09</revisionDate>
    <idTrackerTag>13106</idTrackerTag>
    <fileTypes>.txt</fileTypes>
    <title>A Framework for Centralized Conferencing</title>
    <author>
      <email>mary.barnes@nortel.com</email>
      <name>Mary Barnes</name>
    </author>
    <author>
      <email>cboulton@avaya.com</email>
      <name>Chris Boulton</name>
    </author>
    <author>
      <email>oritl@microsoft.com</email>
      <name>Orit Levin</name>
    </author>
    <abstract>
This document defines the framework for Centralized Conferencing.<br />
The framework allows participants using various call signaling<br />
protocols, such as SIP, H.323, Jabber, Q.931 or ISUP, to exchange<br />
media in a centralized unicast conference.  The Centralized<br />
Conferencing Framework defines logical entities and naming<br />
conventions.  The framework also outlines a set of conferencing<br />
protocols, which are complementary to the call signaling protocols,<br />
for building advanced conferencing applications.  The framework binds<br />
all the defined components together for the benefit of builders of<br />
conferencing systems.</abstract>
    <group>xcon</group>
  </documentInfo>
  <stateInfo type="idTracker">
    <state>IESG Evaluation</state>
    <subState>Revised ID Needed</subState>
    <lastModifiedDate>2007-11-09</lastModifiedDate>
    <idTrackerToken>Cullen Jennings</idTrackerToken>
    <intendedStatus>Proposed Standard</intendedStatus>
  </stateInfo> 
</id>

Some explanation:

"docValidity" is one of: Active, Expired, RFC, Withdrawn by submitter, 
Withdrawn by IETF, and Replaced. All Internet-Drafts are in one of
these states.

The <stateInfo type="idTracker"> describes what IESG is doing 
with the document. A document could also have similar blocks
for <stateInfo type="rfcEditor"> and <stateInfo type="iana">.

Best regards,
Pasi

> -----Original Message-----
> From: tools-discuss-bounces@ietf.org 
> [mailto:tools-discuss-bounces@ietf.org] On Behalf Of ext Tony Hansen
> Sent: 24 April, 2008 01:41
> To: tools-discuss@ietf.org
> Cc: Bill Fenner; Henrik Levkowetz; Glen Barney
> Subject: [Tools-discuss] xml version of 
> 1id-abstracts.txt/1id-index.txt andall_id.txt
> 
> There was some discussion recently of having an xml version of the 
> internet-drafts files 1id-*.txt and all_id.txt.
> 
> Moving this further along, I'd like to make concrete 
> proposals for the 
> schema for such files. First off, for 1id-abstract, the 
> schema would be 
> (I'm not an expert at DTDs, so forgive any errors here):
> 
> <!ELEMENT internet-drafts (docs working-group-map)>
>    <!ELEMENT docs (doc*)>
>      <!ELEMENT doc (name, author, date, wg, file, abstract?)>
>        <!ELEMENT name (#PCDATA)>
>        <!ELEMENT author (#PCDATA)>
>        <!ELEMENT date (#PCDATA)>
>        <!ELEMENT wg (#PCDATA)>
>        <!ELEMENT file (#PCDATA)>
>        <!ELEMENT abstract (#PCDATA)>
>    <!ELEMENT working-group-map (group*)>
>      <!ELEMENT group (acronym, name)>
>        <!ELEMENT acronym (#PCDATA)>
>        <!ELEMENT name (#PCDATA)>
> 
> Translation:
>    <internet-drafts> contains <docs> and <working-group-map>
>    <docs> contains 1 or more <doc>
>    <doc> contains a <name>, <author>, <date>, <wg>, <file> 
> and <abstract>
>    The <wg> contains a working group acronym.
>    At the end is a map from working group acronyms to spelled 
> out names.
>    <working-group-map> contains 1 or more <group>
>    Each <group> contains an <acronym> and <name>.
> 
> A sample would look like this:
> 
>      <?xml version='1.0' encoding='UTF-8'?>
>      <internet-drafts>
>      <docs>
>      <doc>
>       <name>Transmission of IP over Ethernet over IEEE
>        802.16 Networks</name>	
>       <author>HongSeok Jeon</author>
>       <date>18-Apr-08</date>
>       <wg>16ng</wg>
>       <file>draft-ietf-16ng-ip-over-ethernet-over-802.16-06.txt</file>
>       <abstract>
>        This document describes the transmission of IPv4 over ...
>      </doc>
>      ...
>      </docs>
>      <working-group-map>
>      <wg>
>       <acronym>16ng</acronym>
>       <name>IP over IEEE 802.16 Networks</name>
>      </wg>
>      <wg>
>       <acronym>6man</acronym>
>       <name>IPv6 Maintenance</name>
>      </wg>
>      ...
>      </working-group-map>
>      </internet-drafts>
> 
> A complete sample file can be seen at
>     
> http://merlot.tools.ietf.org/~tonyh/internet-drafts/1id-abstracts.xml
> 
> For all_id.xml, I'm proposing this schema:
> 
> <!ELEMENT all-internet-drafts (id*)>
>    <!ELEMENT id (file, date, status, tracker?, iesg?, by?, rfc?)>
>      <!ELEMENT file (#PCDATA)>
>      <!ELEMENT date (#PCDATA)>
>      <!ELEMENT status (#PCDATA)>
>      <!ELEMENT tracker (#PCDATA)>
>      <!ELEMENT iesg (#PCDATA)>
>      <!ELEMENT by (#PCDATA)>
>      <!ELEMENT rfc (#PCDATA)>
> 
> Translation:
>    <all-internet-drafts> contains one or more <id>
>    Each <id> contains a <file>, a <date>, and a <status>
>    Depending on the value of <status>, there may be a <tracker>, a
>    <iesg>, a <by> and a <rfc>.
> 
> A sample would look like this:
> 
>    <all-internet-drafts>
>      <id>
>        <file>draft-adolf-dvb-urn-03</file>
>        <date>2007-12-18</date>
>        <status>In IESG processing</status>
>        <iesg>Revised ID Needed</iesg>
>      </id>
>      <id>
>        <file>draft-cain-post-inch-phishingextns-03</file>
>        <date>2007-10-25</date>
>        <status>In IESG processing</status>
>        <tracker>Publication Requested</tracker>
>      </id>
>      <id>
>        <file>draft-zorn-radius-port-type-04</file>
>        <date>2006-04-04</date>
>        <status>RFC</status>
>        <rfc>4603</rfc>
>      </id>
>      <id><file>draft-yokota-mipshop-3gfh-02</file>
>        <date>2008-03-03</date>
>        <status>Replaced</status>
>        <by>draft-ietf-mipshop-3gfh</by>
>      </id>
>    </all-internet-drafts>
> 
> A complete sample file can be seen at
>     http://merlot.tools.ietf.org/~tonyh/internet-drafts/all_id.xml
> 
> Thoughts?
> 
> 	Tony Hansen
> 	tony@att.com
> _______________________________________________
> Tools-discuss mailing list
> Tools-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-discuss
> 
_______________________________________________
Tools-discuss mailing list
Tools-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss


From tools-discuss-bounces@ietf.org  Thu Apr 24 10:33:15 2008
Return-Path: <tools-discuss-bounces@ietf.org>
X-Original-To: tools-discuss-archive@megatron.ietf.org
Delivered-To: ietfarch-tools-discuss-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 880513A6B3E;
	Thu, 24 Apr 2008 10:33:15 -0700 (PDT)
X-Original-To: tools-discuss@core3.amsl.com
Delivered-To: tools-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 167E03A6B3E
	for <tools-discuss@core3.amsl.com>;
	Thu, 24 Apr 2008 10:33:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.849
X-Spam-Level: 
X-Spam-Status: No, score=-6.849 tagged_above=-999 required=5
	tests=[AWL=-0.250, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id GUa5F0qGcvOT for <tools-discuss@core3.amsl.com>;
	Thu, 24 Apr 2008 10:33:14 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 0D9FB3A6971
	for <tools-discuss@ietf.org>; Thu, 24 Apr 2008 10:33:14 -0700 (PDT)
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 24 Apr 2008 10:33:19 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m3OHXJVh015497; 
	Thu, 24 Apr 2008 10:33:19 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m3OHXJNl014824;
	Thu, 24 Apr 2008 17:33:19 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 24 Apr 2008 10:33:19 -0700
Received: from [10.32.244.219] ([10.32.244.219]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 24 Apr 2008 10:33:18 -0700
In-Reply-To: <480FBB16.9020603@att.com>
References: <480FBB16.9020603@att.com>
Mime-Version: 1.0 (Apple Message framework v753)
X-Gpgmail-State: !signed
Message-Id: <ED1EB76D-4A1A-4AF5-B4C5-37EC089CCCF4@cisco.com>
From: Fred Baker <fred@cisco.com>
Date: Thu, 24 Apr 2008 10:33:20 -0700
To: Tony Hansen <tony@att.com>
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 24 Apr 2008 17:33:18.0846 (UTC)
	FILETIME=[4900D9E0:01C8A631]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5473; t=1209058399;
	x=1209922399; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[Tools-discuss]=20xml=20version=20of=20
	1id-abstracts.txt/1id-index.txt=20and=20all_id.txt |Sender:=20;
	bh=F8Bz4EonQG8Iom50C4Fx9fOrlxcH7sVTwRBfEfbaEvE=;
	b=JIiBjndYMdYq3K7S6bl8BRpfH8+R7J+0vZCJzFEiGdq6QHh1/8PDEcMWDj
	C3NQhUe1XDKrZpKw6DXO+7eNouuwxDZxljsp735zImzD4Lrps4Q7vR4GY5S7
	UXPq5z1chRedBUz6EgrKHOmfeulkrOwIBN33f7qW/mg8/t1Bq+bjY=;
Authentication-Results: sj-dkim-1; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: Bill Fenner <fenner@gmail.com>, Henrik Levkowetz <henrik@levkowetz.com>,
	tools-discuss@ietf.org, Glen Barney <glen@amsl.com>
Subject: Re: [Tools-discuss] xml version of 1id-abstracts.txt/1id-index.txt
	and all_id.txt
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>,
	<mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tools-discuss-bounces@ietf.org
Errors-To: tools-discuss-bounces@ietf.org

quite a few of our documents are not submitted to working groups. Did  
you intend to have "ietf" as a potential working group? How did you  
want to handle that?

Personally, I would like to find individual submissions to working  
groups as well as working group documents here, perhaps with an  
attribute distinguishing them. The way we do this now is that working  
group documents are named draft-ietf-<wg>-... while individual  
submissions to working groups are named draft-<author>-<wg>-...  
Submissions that are not to a working group are draft-<author>-...  
and don't name a WG. But the secretariat only keeps track of the one  
category. That's mostly a database question, but it raises the  
question of an attribute that indicates working group status.

In a tool/page that used this, I would appreciate having a mailto  
link that got me to the authors, as in
     <a href="mailto:draft-whatever@tools.ietf.org">authors</a>,
similar links that got me to the relevant working group chairs and  
ADs, and a link that got me to the ID tracker, as in
     <a href="https://datatracker.ietf.org/idtracker/? 
&search_filename=draft...">ID Status</a>

I don't think that has to be in the XML description of the doc, but  
is certainly derivable from the data and would be useful.


On Apr 23, 2008, at 3:41 PM, Tony Hansen wrote:

> There was some discussion recently of having an xml version of the
> internet-drafts files 1id-*.txt and all_id.txt.
>
> Moving this further along, I'd like to make concrete proposals for the
> schema for such files. First off, for 1id-abstract, the schema  
> would be
> (I'm not an expert at DTDs, so forgive any errors here):
>
> <!ELEMENT internet-drafts (docs working-group-map)>
>    <!ELEMENT docs (doc*)>
>      <!ELEMENT doc (name, author, date, wg, file, abstract?)>
>        <!ELEMENT name (#PCDATA)>
>        <!ELEMENT author (#PCDATA)>
>        <!ELEMENT date (#PCDATA)>
>        <!ELEMENT wg (#PCDATA)>
>        <!ELEMENT file (#PCDATA)>
>        <!ELEMENT abstract (#PCDATA)>
>    <!ELEMENT working-group-map (group*)>
>      <!ELEMENT group (acronym, name)>
>        <!ELEMENT acronym (#PCDATA)>
>        <!ELEMENT name (#PCDATA)>
>
> Translation:
>    <internet-drafts> contains <docs> and <working-group-map>
>    <docs> contains 1 or more <doc>
>    <doc> contains a <name>, <author>, <date>, <wg>, <file> and  
> <abstract>
>    The <wg> contains a working group acronym.
>    At the end is a map from working group acronyms to spelled out  
> names.
>    <working-group-map> contains 1 or more <group>
>    Each <group> contains an <acronym> and <name>.
>
> A sample would look like this:
>
>      <?xml version='1.0' encoding='UTF-8'?>
>      <internet-drafts>
>      <docs>
>      <doc>
>       <name>Transmission of IP over Ethernet over IEEE
>        802.16 Networks</name>	
>       <author>HongSeok Jeon</author>
>       <date>18-Apr-08</date>
>       <wg>16ng</wg>
>       <file>draft-ietf-16ng-ip-over-ethernet-over-802.16-06.txt</file>
>       <abstract>
>        This document describes the transmission of IPv4 over ...
>      </doc>
>      ...
>      </docs>
>      <working-group-map>
>      <wg>
>       <acronym>16ng</acronym>
>       <name>IP over IEEE 802.16 Networks</name>
>      </wg>
>      <wg>
>       <acronym>6man</acronym>
>       <name>IPv6 Maintenance</name>
>      </wg>
>      ...
>      </working-group-map>
>      </internet-drafts>
>
> A complete sample file can be seen at
>     http://merlot.tools.ietf.org/~tonyh/internet-drafts/1id- 
> abstracts.xml
>
> For all_id.xml, I'm proposing this schema:
>
> <!ELEMENT all-internet-drafts (id*)>
>    <!ELEMENT id (file, date, status, tracker?, iesg?, by?, rfc?)>
>      <!ELEMENT file (#PCDATA)>
>      <!ELEMENT date (#PCDATA)>
>      <!ELEMENT status (#PCDATA)>
>      <!ELEMENT tracker (#PCDATA)>
>      <!ELEMENT iesg (#PCDATA)>
>      <!ELEMENT by (#PCDATA)>
>      <!ELEMENT rfc (#PCDATA)>
>
> Translation:
>    <all-internet-drafts> contains one or more <id>
>    Each <id> contains a <file>, a <date>, and a <status>
>    Depending on the value of <status>, there may be a <tracker>, a
>    <iesg>, a <by> and a <rfc>.
>
> A sample would look like this:
>
>    <all-internet-drafts>
>      <id>
>        <file>draft-adolf-dvb-urn-03</file>
>        <date>2007-12-18</date>
>        <status>In IESG processing</status>
>        <iesg>Revised ID Needed</iesg>
>      </id>
>      <id>
>        <file>draft-cain-post-inch-phishingextns-03</file>
>        <date>2007-10-25</date>
>        <status>In IESG processing</status>
>        <tracker>Publication Requested</tracker>
>      </id>
>      <id>
>        <file>draft-zorn-radius-port-type-04</file>
>        <date>2006-04-04</date>
>        <status>RFC</status>
>        <rfc>4603</rfc>
>      </id>
>      <id><file>draft-yokota-mipshop-3gfh-02</file>
>        <date>2008-03-03</date>
>        <status>Replaced</status>
>        <by>draft-ietf-mipshop-3gfh</by>
>      </id>
>    </all-internet-drafts>
>
> A complete sample file can be seen at
>     http://merlot.tools.ietf.org/~tonyh/internet-drafts/all_id.xml
>
> Thoughts?
>
> 	Tony Hansen
> 	tony@att.com
> _______________________________________________
> Tools-discuss mailing list
> Tools-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-discuss

_______________________________________________
Tools-discuss mailing list
Tools-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss


From tools-discuss-bounces@ietf.org  Thu Apr 24 11:24:16 2008
Return-Path: <tools-discuss-bounces@ietf.org>
X-Original-To: tools-discuss-archive@megatron.ietf.org
Delivered-To: ietfarch-tools-discuss-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2D12E28C1A9;
	Thu, 24 Apr 2008 11:24:16 -0700 (PDT)
X-Original-To: tools-discuss@core3.amsl.com
Delivered-To: tools-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E45ED3A6C3A
	for <tools-discuss@core3.amsl.com>;
	Thu, 24 Apr 2008 11:24:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.401
X-Spam-Level: 
X-Spam-Status: No, score=0.401 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, J_CHICKENPOX_22=0.6, J_CHICKENPOX_52=0.6,
	J_CHICKENPOX_62=0.6, J_CHICKENPOX_82=0.6, J_CHICKENPOX_92=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5wT9j9VM1hpp for <tools-discuss@core3.amsl.com>;
	Thu, 24 Apr 2008 11:24:10 -0700 (PDT)
Received: from merlot.tools.ietf.org (unknown
	[IPv6:2a01:3f0:0:31:214:22ff:fe21:bb])
	by core3.amsl.com (Postfix) with ESMTP id 75CE53A6BF2
	for <tools-discuss@ietf.org>; Thu, 24 Apr 2008 11:24:08 -0700 (PDT)
Received: from localhost ([127.0.0.1]:42319 helo=chardonnay-2.local)
	by merlot.tools.ietf.org with esmtp (Exim 4.69)
	(envelope-from <henrik@levkowetz.com>)
	id 1Jp675-0005LN-Ps; Thu, 24 Apr 2008 20:24:08 +0200
Message-ID: <4810D046.10603@levkowetz.com>
Date: Thu, 24 Apr 2008 20:24:06 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: tony@att.com, tools-discuss@ietf.org
References: <480FBB16.9020603@att.com>
	<1696498986EFEC4D9153717DA325CB7271D47E@vaebe104.NOE.Nokia.com>
In-Reply-To: <1696498986EFEC4D9153717DA325CB7271D47E@vaebe104.NOE.Nokia.com>
X-Enigmail-Version: 0.95.6
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: tony@att.com, tools-discuss@ietf.org, Pasi.Eronen@nokia.com,
	fenner@gmail.com, glen@amsl.com, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on merlot.tools.ietf.org);
	SAEximRunCond expanded to false
Cc: fenner@gmail.com, Pasi.Eronen@nokia.com, glen@amsl.com
Subject: Re: [Tools-discuss] xml version of 1id-abstracts.txt/1id-index.txt
 andall_id.txt
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>,
	<mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tools-discuss-bounces@ietf.org
Errors-To: tools-discuss-bounces@ietf.org

And below is the format which is currently used in the state.xml
files available for all current and most old drafts at 
tools.ietf.org/draft/<DRAFTNAME>/state.xml.  I think a revision
of this format which uses Pasi's schema for the <author/> tag
would be good.

Note the <state/> tag which is more complex than the other
proposals -- this is in order to be able to handle the fact that
there may be multiple simultaneous states for various phases of
the document processing, such as the IESG, IANA, and RFC-Editor
queue states.

There's also additional state information of a type which both
in the IESG case and in the RFC-editor case can exist in multiple
instances (so it's not really state information) -- I've called
this <infotag/>, and there can be multiple infotags within a
<state/> element.


<ietfdoc version="0.92">
   <id>draft-ietf-dhc-paa-option</id>
   <state>
      <phase>IESG</phase>
      <stage>RFC-queue</stage>
   </state>
   <state>
      <phase>RFC-Editor</phase>
      <stage>Auth48</stage>
      <infotag>Dependency</infotag>
   </state>
   <info>
      <abstract>This document defines new DHCPv4 and DHCPv6 options that contain a\nlist of IP addresses to locate one or more of PANA Authentication\nAgents (PAA). This is one of the methods that a PANA Client (PaC) can\nuse to locate PANA Authentication Agents (PAA).</abstract>
      <areadir>Jari Arkko</areadir>
      <author>Lionel Morand &lt;lionel.morand@orange-ft.com&gt;</author>
      <author>Alper Yegin &lt;alper01.yegin@partner.samsung.com&gt;</author>
      <author>Suraj Kumar &lt;surajk@techmahindra.com&gt;</author>
      <author>Syam Madanapalli &lt;syam@samsung.com&gt;</author>
      <bytes>16022</bytes>
      <deststatus>Standards Track</deststatus>
      <idnum>13742</idnum>
      <pages>9</pages>
      <refs>draft-ietf-pana-pana[in-queue]</refs>
      <rev>05</rev>
      <source>Dynamic Host Configuration</source>
      <submitted>2006-12-18</submitted>
      <title>DHCP options for PANA Authentication Agents</title>
      <validity>Active</validity>
      <wg>dhc</wg>
   </info>
</ietfdoc>




On 2008-04-24 19:06 Pasi.Eronen@nokia.com said the following:
> Here's a sample from the code I currently have:
> 
> <id xml:id="draft-ietf-xcon-framework">
>   <id>draft-ietf-xcon-framework</id>
>   <documentInfo>
>     <docValidity>Active</docValidity>
>     <revision>10</revision>
>     <revisionDate>2007-11-09</revisionDate>
>     <idTrackerTag>13106</idTrackerTag>
>     <fileTypes>.txt</fileTypes>
>     <title>A Framework for Centralized Conferencing</title>
>     <author>
>       <email>mary.barnes@nortel.com</email>
>       <name>Mary Barnes</name>
>     </author>
>     <author>
>       <email>cboulton@avaya.com</email>
>       <name>Chris Boulton</name>
>     </author>
>     <author>
>       <email>oritl@microsoft.com</email>
>       <name>Orit Levin</name>
>     </author>
>     <abstract>
> This document defines the framework for Centralized Conferencing.<br />
> The framework allows participants using various call signaling<br />
> protocols, such as SIP, H.323, Jabber, Q.931 or ISUP, to exchange<br />
> media in a centralized unicast conference.  The Centralized<br />
> Conferencing Framework defines logical entities and naming<br />
> conventions.  The framework also outlines a set of conferencing<br />
> protocols, which are complementary to the call signaling protocols,<br />
> for building advanced conferencing applications.  The framework binds<br />
> all the defined components together for the benefit of builders of<br />
> conferencing systems.</abstract>
>     <group>xcon</group>
>   </documentInfo>
>   <stateInfo type="idTracker">
>     <state>IESG Evaluation</state>
>     <subState>Revised ID Needed</subState>
>     <lastModifiedDate>2007-11-09</lastModifiedDate>
>     <idTrackerToken>Cullen Jennings</idTrackerToken>
>     <intendedStatus>Proposed Standard</intendedStatus>
>   </stateInfo> 
> </id>
> 
> Some explanation:
> 
> "docValidity" is one of: Active, Expired, RFC, Withdrawn by submitter, 
> Withdrawn by IETF, and Replaced. All Internet-Drafts are in one of
> these states.
> 
> The <stateInfo type="idTracker"> describes what IESG is doing 
> with the document. A document could also have similar blocks
> for <stateInfo type="rfcEditor"> and <stateInfo type="iana">.
> 
> Best regards,
> Pasi
> 
>> -----Original Message-----
>> From: tools-discuss-bounces@ietf.org 
>> [mailto:tools-discuss-bounces@ietf.org] On Behalf Of ext Tony Hansen
>> Sent: 24 April, 2008 01:41
>> To: tools-discuss@ietf.org
>> Cc: Bill Fenner; Henrik Levkowetz; Glen Barney
>> Subject: [Tools-discuss] xml version of 
>> 1id-abstracts.txt/1id-index.txt andall_id.txt
>>
>> There was some discussion recently of having an xml version of the 
>> internet-drafts files 1id-*.txt and all_id.txt.
>>
>> Moving this further along, I'd like to make concrete 
>> proposals for the 
>> schema for such files. First off, for 1id-abstract, the 
>> schema would be 
>> (I'm not an expert at DTDs, so forgive any errors here):
>>
>> <!ELEMENT internet-drafts (docs working-group-map)>
>>    <!ELEMENT docs (doc*)>
>>      <!ELEMENT doc (name, author, date, wg, file, abstract?)>
>>        <!ELEMENT name (#PCDATA)>
>>        <!ELEMENT author (#PCDATA)>
>>        <!ELEMENT date (#PCDATA)>
>>        <!ELEMENT wg (#PCDATA)>
>>        <!ELEMENT file (#PCDATA)>
>>        <!ELEMENT abstract (#PCDATA)>
>>    <!ELEMENT working-group-map (group*)>
>>      <!ELEMENT group (acronym, name)>
>>        <!ELEMENT acronym (#PCDATA)>
>>        <!ELEMENT name (#PCDATA)>
>>
>> Translation:
>>    <internet-drafts> contains <docs> and <working-group-map>
>>    <docs> contains 1 or more <doc>
>>    <doc> contains a <name>, <author>, <date>, <wg>, <file> 
>> and <abstract>
>>    The <wg> contains a working group acronym.
>>    At the end is a map from working group acronyms to spelled 
>> out names.
>>    <working-group-map> contains 1 or more <group>
>>    Each <group> contains an <acronym> and <name>.
>>
>> A sample would look like this:
>>
>>      <?xml version='1.0' encoding='UTF-8'?>
>>      <internet-drafts>
>>      <docs>
>>      <doc>
>>       <name>Transmission of IP over Ethernet over IEEE
>>        802.16 Networks</name>	
>>       <author>HongSeok Jeon</author>
>>       <date>18-Apr-08</date>
>>       <wg>16ng</wg>
>>       <file>draft-ietf-16ng-ip-over-ethernet-over-802.16-06.txt</file>
>>       <abstract>
>>        This document describes the transmission of IPv4 over ...
>>      </doc>
>>      ...
>>      </docs>
>>      <working-group-map>
>>      <wg>
>>       <acronym>16ng</acronym>
>>       <name>IP over IEEE 802.16 Networks</name>
>>      </wg>
>>      <wg>
>>       <acronym>6man</acronym>
>>       <name>IPv6 Maintenance</name>
>>      </wg>
>>      ...
>>      </working-group-map>
>>      </internet-drafts>
>>
>> A complete sample file can be seen at
>>     
>> http://merlot.tools.ietf.org/~tonyh/internet-drafts/1id-abstracts.xml
>>
>> For all_id.xml, I'm proposing this schema:
>>
>> <!ELEMENT all-internet-drafts (id*)>
>>    <!ELEMENT id (file, date, status, tracker?, iesg?, by?, rfc?)>
>>      <!ELEMENT file (#PCDATA)>
>>      <!ELEMENT date (#PCDATA)>
>>      <!ELEMENT status (#PCDATA)>
>>      <!ELEMENT tracker (#PCDATA)>
>>      <!ELEMENT iesg (#PCDATA)>
>>      <!ELEMENT by (#PCDATA)>
>>      <!ELEMENT rfc (#PCDATA)>
>>
>> Translation:
>>    <all-internet-drafts> contains one or more <id>
>>    Each <id> contains a <file>, a <date>, and a <status>
>>    Depending on the value of <status>, there may be a <tracker>, a
>>    <iesg>, a <by> and a <rfc>.
>>
>> A sample would look like this:
>>
>>    <all-internet-drafts>
>>      <id>
>>        <file>draft-adolf-dvb-urn-03</file>
>>        <date>2007-12-18</date>
>>        <status>In IESG processing</status>
>>        <iesg>Revised ID Needed</iesg>
>>      </id>
>>      <id>
>>        <file>draft-cain-post-inch-phishingextns-03</file>
>>        <date>2007-10-25</date>
>>        <status>In IESG processing</status>
>>        <tracker>Publication Requested</tracker>
>>      </id>
>>      <id>
>>        <file>draft-zorn-radius-port-type-04</file>
>>        <date>2006-04-04</date>
>>        <status>RFC</status>
>>        <rfc>4603</rfc>
>>      </id>
>>      <id><file>draft-yokota-mipshop-3gfh-02</file>
>>        <date>2008-03-03</date>
>>        <status>Replaced</status>
>>        <by>draft-ietf-mipshop-3gfh</by>
>>      </id>
>>    </all-internet-drafts>
>>
>> A complete sample file can be seen at
>>     http://merlot.tools.ietf.org/~tonyh/internet-drafts/all_id.xml
>>
>> Thoughts?
>>
>> 	Tony Hansen
>> 	tony@att.com
>> _______________________________________________
>> Tools-discuss mailing list
>> Tools-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/tools-discuss
>>
> _______________________________________________
> Tools-discuss mailing list
> Tools-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-discuss
> 
_______________________________________________
Tools-discuss mailing list
Tools-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss


From tools-discuss-bounces@ietf.org  Wed Apr 30 09:33:52 2008
Return-Path: <tools-discuss-bounces@ietf.org>
X-Original-To: tools-discuss-archive@megatron.ietf.org
Delivered-To: ietfarch-tools-discuss-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 537FD3A6B8E;
	Wed, 30 Apr 2008 09:33:52 -0700 (PDT)
X-Original-To: tools-discuss@core3.amsl.com
Delivered-To: tools-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1E91D3A6767
	for <tools-discuss@core3.amsl.com>;
	Tue, 29 Apr 2008 13:44:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level: 
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id TaEP-KEMS7wZ for <tools-discuss@core3.amsl.com>;
	Tue, 29 Apr 2008 13:44:33 -0700 (PDT)
Received: from mail.jc-bell.com (mail.jc-bell.com [204.13.148.210])
	by core3.amsl.com (Postfix) with ESMTP id 054AD28C15D
	for <tools-discuss@ietf.org>; Tue, 29 Apr 2008 13:44:32 -0700 (PDT)
Received: from localhost (unknown [192.168.2.2])
	by mail.jc-bell.com (Postfix) with ESMTP id 3D39478CD2
	for <tools-discuss@ietf.org>; Tue, 29 Apr 2008 16:44:35 -0400 (EDT)
X-Virus-Scanned: amavisd-new at nw-ds.com
Received: from jcb (adsl-99-135-148-173.dsl.emhril.sbcglobal.net
	[99.135.148.173]) (using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by mail.jc-bell.com (Postfix) with ESMTP id 570CE78CC2
	for <tools-discuss@ietf.org>; Tue, 29 Apr 2008 16:44:27 -0400 (EDT)
From: "Jim Bell" <Jim@JC-Bell.com>
To: <tools-discuss@ietf.org>
Date: Tue, 29 Apr 2008 15:43:47 -0500
Organization: J. C. Bell & Associates, Inc.
Message-ID: <00d601c8aa39$b9b5db20$2d219160$@com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AciqObk3ZtBJxDD9Q/C1bZp4Pj1YtA==
Content-Language: en-us
X-Mailman-Approved-At: Wed, 30 Apr 2008 09:33:50 -0700
Subject: [Tools-discuss] Text in RFC 3986 breaks RFC-HTML tool
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>,
	<mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0303971185=="
Sender: tools-discuss-bounces@ietf.org
Errors-To: tools-discuss-bounces@ietf.org

This is a multipart message in MIME format.

--===============0303971185==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00D7_01C8AA0F.D0DFD320"
Content-Language: en-us

This is a multipart message in MIME format.

------=_NextPart_000_00D7_01C8AA0F.D0DFD320
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

To Whom It May Concern:



The RFC-HTML tool mangles RFC 3986 a little.

 

Appendix C in http://www.ietf.org/rfc/rfc3986.txt has this paragraph:

Yes, Jim, I found it under "http://www.w3.org/Addressing/",

      but you can probably pick it up from <ftp://foo.example.

      com/rfc/>.  Note the warning in <http://www.ics.uci.edu/pub/

      ietf/uri/historical.html#WARNING>.

 

That gets mangled in http://tools.ietf.org/html/rfc3986

 

Regards,

-Jim Bell

 

P.S.: The RFC-HTML tool overall is outstanding, and I appreciate it very
much.

 


------=_NextPart_000_00D7_01C8AA0F.D0DFD320
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt'>To Whom It May =
Concern:<br>
<br>
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt'>The RFC-HTML tool =
mangles RFC
3986 a little.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt'>Appendix C in <a
href=3D"http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3=
986.txt</a>
has this paragraph:<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Yes,
Jim, I found it under =
&quot;http://www.w3.org/Addressing/&quot;,<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
but you can probably pick it up from =
&lt;ftp://foo.example.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
com/rfc/&gt;.&nbsp; Note the warning in =
&lt;http://www.ics.uci.edu/pub/<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
ietf/uri/historical.html#WARNING&gt;.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt'>That gets mangled =
in <a
href=3D"http://tools.ietf.org/html/rfc3986">http://tools.ietf.org/html/rf=
c3986</a><o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:12.0pt'>Regards,<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt'>-Jim =
Bell<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt'>P.S.: The RFC-HTML =
tool
overall is outstanding, and I appreciate it very =
much.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></p>

</div>

</body>

</html>

------=_NextPart_000_00D7_01C8AA0F.D0DFD320--


--===============0303971185==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Tools-discuss mailing list
Tools-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

--===============0303971185==--



