[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Ltru] Re: [psg.com #938] should introduction allude tointendedbcp status?

From: "JFC (Jefsey) Morfin" <jefsey at jefsey.com>
To: "'LTRU Working Group'" <ltru at ietf.org>
Cc:
Date: Wed, 11 May 2005 23:17:28 +0200
In-reply-to: <20050511210359.BCFV10612.lakermmtao12.cox.net at A31P>
References: <634978A7DF025A40BFEF33EB191E13BC0B5A6C84 at irvmbxw01.quest.com> <20050511210359.BCFV10612.lakermmtao12.cox.net at A31P>

At 23:04 11/05/2005, Scott Hollenbeck wrote:

Ah, I see it in the rfc2629 DTD.  In the <rfc> element, add a 'category='
attribute.  Valid values: std|bcp|info|exp|historic.


Addison, did you try "historic"? If it worked it would save our vacations. jfc


_______________________________________________
Ltru mailing list
Ltru at lists.ietf.org
https://www1.ietf.org/mailman/listinfo/ltru

References:
- RE: [Ltru] Re: [psg.com #938] should introduction allude tointendedbcp status?
  - From: Addison Phillips
- RE: [Ltru] Re: [psg.com #938] should introduction allude tointendedbcp status?
  - From: Scott Hollenbeck

Prev by Date: Re: [Ltru] Re: [psg.com #951] extensibility via codes not maintained by ISO
Next by Date: [Ltru] Re: [psg.com #954] all aliases must be equally supported
Previous by thread: Re: xml2rfc category (was RE: [Ltru] Re: [psg.com #938] should introduction alludetointendedbcp status?)
Next by thread: RE: xml2rfc category (was RE: [Ltru] Re: [psg.com #938] shouldintroduction alludetointendedbcp status?)
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.