> Normative references to stable non-standards track documents > are indeed allowed when those documents are of the nature of > algorithm descriptions, mathematical theorems, and the like - there is no such topic-based dispensation in 2026 - the section that Brian referres to needs to be read in conjunction with sec 4.2.4 pp 2 there is little issue with referring to standards from elsewhere (see sec 7) even if the standard is published as an info rfc but just because somone says that a info RFC has a particular type of content does not mean that it gets any special treatment this is not to say that we do not need to figure out how to deal with this type of case but I do not agree that Brian's way is legit Scott
- 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
