At 08:36 PM 8/30/00 -0400, Scott Bradner wrote: > > An informational RFC certainly meets these requirements. > >I don't think we want to say that any info RFC qualifies > >so how do we say just what we want to say and no more? Promote the info RFC to BCP? #g
- Standard Track dependencies on Informational RFCs Kurt D. Zeilenga
- Re: Standard Track dependencies on Informational RF... RJ Atkinson
- Re: Standard Track dependencies on Informationa... Brian E Carpenter
- Re: Standard Track dependencies on Informational RF... Scott Bradner
- Re: Standard Track dependencies on Informationa... Kurt D. Zeilenga
- Re: Standard Track dependencies on Informationa... Keith Moore
- RE: Standard Track dependencies on Informational RF... Christian Huitema
- RE: Standard Track dependencies on Informational RF... Scott Bradner
- RE: Standard Track dependencies on Informationa... Harald Alvestrand
- Re: Standard Track dependencies on Informationa... Graham Klyne
- Re: Standard Track dependencies on Informationa... Brian E Carpenter
- Re: Standard Track dependencies on Informat... RJ Atkinson
- Re: Standard Track dependencies on Informational RF... John Stracke
- Re: Standard Track dependencies on Informational RF... Scott Bradner
- Re: Standard Track dependencies on Informationa... Kurt D. Zeilenga
- Re: Standard Track dependencies on Informat... Harald Alvestrand
- RE: Standard Track dependencies on Informational RF... Christian Huitema
