A reference list is not an exhaustive list of possible related documents. It's only made from the most pertinent items referenced based on the author/s analysis. And if an item was never referenced in the creation of the document, it's 99% sure not to be listed in the reference.
A reference list is not meant to be all inclusive. If you are looking to get your document referenced more frequently, you can actively watch for draft documents and find the ones your document might influence and contact the author/s. Yet this still might not guarantee a reference listing if the list they already have is good enough as it is. -----Original Message----- From: rtgwg <[email protected]> On Behalf Of Fred Baker Sent: Tuesday, March 12, 2019 7:31 PM To: shyam bandyopadhyay <[email protected]> Cc: Alissa Cooper <[email protected]>; [email protected] Subject: Re: I wonder what is being going on ________________________________ WARNING: External email. Please verify sender before opening attachments or clicking on links. ________________________________ On Mar 12, 2019, at 1:13 AM, shyam bandyopadhyay <[email protected]> wrote: > I have said many times earlier that the basic principle based on > which RFC 8028, RFC 8043 and > draft-ietf-rtgwg-enterprise-pa-multihoming > are written, i. e. "default routing based on source address of > outgoing packets" was first introduced on draft-shyam-site-multi. Speaking for myself, having the position of a co-author on two of the documents you mention. I have not inserted a reference into the documents for the simple reason that I was unaware of draft-shyam-site-multi and my thinking didn't depend on it. When I insert a reference into a paper, it's not in the academic sense in which one lists all possible mention of a topic and comments to associate with it or differentiate from it; I refer to a document to help explain some aspect of my thinking, or to lead a reader to some other technology that my thinking depends on. To give an example in the context of another paper, I mention that someone should validate a DNSSEC signature at some point, and I refer to RFC 4035 because it discusses what that means and how one goes about it. The earliest mention of source-dependent routing that I know of is academic work done by Marcelo Bagnulo at (I believe) the University of Madrid, in Spain. I'm sorry if that is offensive; for my part, it is pragmatic. I'm not writing a thesis, I'm writing a specification. I don't pretend to know everything. I do try to state clearly what I mean when I write something, and give my readers the references they need to understand and use it. ________________________________ This communication is confidential. Frontier only sends and receives email on the basis of the terms set out at http://www.frontier.com/email_disclaimer. _______________________________________________ rtgwg mailing list [email protected] https://www.ietf.org/mailman/listinfo/rtgwg
