On Wed., 13 Mar. 2019, 14:03 William Atwood, <[email protected]> wrote:
> Shyam, > > Specifically: > > Marcelo Bagnulo, Alberto Garcia-Martinez, Juan Rodriguez, and Arturo > Azcorra, "The Case for Source Address Dependent Routing in Multihoming", > International Workshop on Quality of Future Internet Services (QofIS > 2004), Lecture Notes in Computer Science (LNCS, volume 3266). > > The authors were at Universidad Carlos III de Madrid, Leganes, Madrid, > Spain at the time of writing. > > This was published in 2004, so your claim to be the first one to put > forth this idea is incorrect. > "Policy Based Routing", which allowed creating static forwarding policies based on packet attributes other than the destination address, was a capability commercially available from one of the big router vendors earlier than that. For example, in 1999 I deployed PBR at a large hospital which selected the site egress link based on packet source address. I'm pretty sure Linux gained those sorts of capabilities in version 2.2.0, released in 1999. In 2001 or 2002 I used ingress source addresses to select the egress interface for response packets on a multihomed Linux host. Using a source address and possibly other packet attributes, other than the destination address, to make forwarding decisions is an old idea. Regards, Mark. > However, as Fred says, RFC citations are based on "need to know", not > academic precedence. > > Bill Atwood > > On 12/03/2019 10:31 p.m., Fred Baker wrote: > > 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. > > > > > > _______________________________________________ > > rtgwg mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/rtgwg > > > > -- > > Dr. J.W. Atwood, Eng. tel: +1 (514) 848-2424 x3046 > Distinguished Professor Emeritus fax: +1 (514) 848-2830 > Department of Computer Science > and Software Engineering > Concordia University EV 3.185 email:[email protected] > 1455 de Maisonneuve Blvd. West http://users.encs.concordia.ca/~bill > Montreal, Quebec Canada H3G 1M8 > > _______________________________________________ > rtgwg mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/rtgwg >
_______________________________________________ rtgwg mailing list [email protected] https://www.ietf.org/mailman/listinfo/rtgwg
