Re: I wonder what is being going on

Fred Baker <fredbaker.ietf@gmail.com> Wed, 13 March 2019 02:31 UTC

Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D6F812797A for <rtgwg@ietfa.amsl.com>; Tue, 12 Mar 2019 19:31:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fdHbe7Fx55mm for <rtgwg@ietfa.amsl.com>; Tue, 12 Mar 2019 19:31:08 -0700 (PDT)
Received: from mail-pf1-x435.google.com (mail-pf1-x435.google.com [IPv6:2607:f8b0:4864:20::435]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D1E01277DB for <rtgwg@ietf.org>; Tue, 12 Mar 2019 19:31:08 -0700 (PDT)
Received: by mail-pf1-x435.google.com with SMTP id n22so289253pfa.3 for <rtgwg@ietf.org>; Tue, 12 Mar 2019 19:31:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=FFFd26QYojAgK5CFOW3ZKkwSysu83/PzVvvnlafXCtQ=; b=gly3FjsbeibXVLkUe7MqPhOqUlUDSa594xR+FyXNc6Bpn3areAO9EQ9IsJsDq+81Ub pegqT0s+MmP/N0z8L4xJl05hCjgWLD6qXd9gzTlBExL0zBF+o47dJA/h2pM/KwIJYSZI Au4Hw50ww1e5rv1Sy886+dApIifSQdQr0pGoXbcGY8fWY7mV4meQaKsKmG8VgYi446aB PnklaJyoiRVDddBux6QhCXx+tjbFVd/fF0O1mSVSg4V9MsYWWlstNUK7Eh2m/6R2eA7W v0KoGHKj4vExEsrg1ixUEOC5Ce81zBuxNCXU1LjxIZUkXWlwxJQGdnkyYrjbz//7jhp8 Fz+Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=FFFd26QYojAgK5CFOW3ZKkwSysu83/PzVvvnlafXCtQ=; b=LmeNmRLPclktmnuFbMq1U7KRKAqZP25Fa4+nhxYB8b6yhQxzm87yrs5zFVB4tV45so USYprYec2gtgozxh1N9DgQDd98iB1L1q3Dyi1zyzD3grLZ74NcilKJtZv89KX9XHEnTc Gdk/NYhrSMAY0BDsWKmW+vpjSif0sdz/0BUFOCM9IWEa7S2fiez6ncrVHWTdG7QTlV4y C70VhxXszdxS/EOhzxCnW9se4HwciBeglk/tE+BWCO3AWDXCwUjHmr4cNR98uFAocbVY 7uPh+VfgeSTvRhejXU7asp8899PclRx9LhzMU27VQSOe2D7cG/PRmRpYk9J11ruXfFzT SXuw==
X-Gm-Message-State: APjAAAW/Eaj5QZmATbo0bIYzF/Jmx2pkLhv+Oi6N7tBaez31IkpDLwk9 FC6IJOOhXagGaGiUmQI9lrg=
X-Google-Smtp-Source: APXvYqyBaM5aUuh5dEl5TOGVU0MdgEq0kCzlMAYONNqNT41S/MrwmoQHLFFf8W0iQD8npCSgQSA+4A==
X-Received: by 2002:aa7:83ca:: with SMTP id j10mr41831070pfn.50.1552444267855; Tue, 12 Mar 2019 19:31:07 -0700 (PDT)
Received: from [172.20.10.3] ([172.56.30.156]) by smtp.gmail.com with ESMTPSA id f65sm1246857pfg.98.2019.03.12.19.31.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Mar 2019 19:31:06 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <AE84BD0A-EC90-4DF1-9285-AECC43737643@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_35E863A1-3DD9-4A5A-BC29-E088C920E0E5"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.2\))
Subject: Re: I wonder what is being going on
Date: Wed, 13 Mar 2019 11:31:01 +0900
In-Reply-To: <CAPTMOtKcPnwv9bD4xbRB1h=HwddDe1RznwApL-kf_NV1b0NbRA@mail.gmail.com>
Cc: rtgwg@ietf.org, Alissa Cooper <alissa@cooperw.in>
To: shyam bandyopadhyay <shyamb66@gmail.com>
References: <CAPTMOt+jvTbrH1_YOmXJ0YQpLB5LdePekwkd2HyvLMLfGbnpZQ@mail.gmail.com> <04F9E6B4-2398-400E-8BB9-21935AE14845@cooperw.in> <CAPTMOtKcPnwv9bD4xbRB1h=HwddDe1RznwApL-kf_NV1b0NbRA@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/A46wfUcpWBbrbu0RBV8g91zU5y8>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2019 02:31:10 -0000

On Mar 12, 2019, at 1:13 AM, shyam bandyopadhyay <shyamb66@gmail.com> 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.