[rfc-i] draft-iab-streams-headers-boilerplates-01 -- third paragraph

[Bob Braden]

  *> From rfc-ed at ISI.EDU  Thu Oct 16 14:02:29 2008
  *> X-Spam-Status: No, score=-0.7 required=5.0 tests=AWL,BAYES_05,
  *> 	DNS_FROM_SECURITYSAGE autolearn=no version=3.1.0
  *> DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
  *> 	h=message-id:date:from:organization:user-agent:mime-version:to:cc
  *> 	:subject:references:in-reply-to:content-type
  *> 	:content-transfer-encoding;
  *> 	b=D6qVCp0Q8QboyPh/UN6A40CdXhcA2E4PLjsjAaRfFceeDLHNJmLzF6Cnk34VIipaBJ
  *> 	GgtAj28p5Iv6/pL7gXeWWRm2P0kRYkUBqHdp6AmsGovsjzs6kv8E6pW9aDd9D6bQxnZk
  *> 	UpJ45P0GhUJIs6s8jXsWT58IqSwcWUdHdf8is=
  *> Date: Fri, 17 Oct 2008 09:30:09 +1300
  *> From: Brian E Carpenter <brian.e.carpenter at gmail.com>
  *> User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
  *> To: Olaf Kolkman <olaf at NLnetLabs.nl>
  *> X-ISI-4-43-8-MailScanner: Found to be clean, Found to be clean
  *> Cc: rfc-interest at rfc-editor.org
  *> Subject: Re: [rfc-i] draft-iab-streams-headers-boilerplates-01 --
  *> 	third	paragraph
  *> List-Id: "A list for discussion of the RFC series and RFC Editor functions."
  *> 	<rfc-interest.rfc-editor.org>
  *> Content-Transfer-Encoding: 7bit
  *> 
  *> > Personally, I would think that it makes sense to add a line into the acknowledgment section: This document is based on work chartered in the IETF BLAFOO  working group. 
  *> 
  *> No objection, but this, and the traceback to the draft name, sound like
  *> metatdata to me. Myabe a better approach is to ask the RFC Publisher
  *> to make such metadata readily available on line (including a link
  *> to the I-D tracker).
  *> 
  *>     Brian
  *> _______________________________________________
  *> rfc-interest mailing list
  *> rfc-interest at rfc-editor.org
  *> http://mailman.rfc-editor.org/mailman/listinfo/rfc-interest
  *>