Re: [RTG-DIR] Routing area directorate early (QA) review of draft-ietf-babel-applicability

Juliusz Chroboczek <jch@irif.fr> Tue, 31 January 2017 19:37 UTC

Return-Path: <jch@irif.fr>
X-Original-To: rtg-dir@ietfa.amsl.com
Delivered-To: rtg-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 776131299A7; Tue, 31 Jan 2017 11:37:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 oOwYtmSkicl2; Tue, 31 Jan 2017 11:37:09 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5198E129574; Tue, 31 Jan 2017 11:37:09 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56228) with ESMTP id v0VJavHH019122; Tue, 31 Jan 2017 20:36:57 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 72898D79B6; Tue, 31 Jan 2017 20:36:57 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id YowVrHp0xoXa; Tue, 31 Jan 2017 20:36:56 +0100 (CET)
Received: from lanthane.pps.univ-paris-diderot.fr (unknown [172.23.36.54]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id A383BD78B7; Tue, 31 Jan 2017 20:36:55 +0100 (CET)
Received: from localhost ([::1] helo=lanthane.irif.fr) by lanthane.pps.univ-paris-diderot.fr with esmtp (Exim 4.88) (envelope-from <jch@irif.fr>) id 1cYeEZ-00049o-BP; Tue, 31 Jan 2017 20:36:55 +0100
Date: Tue, 31 Jan 2017 20:36:55 +0100
Message-ID: <7i4m0fja20.wl-jch@irif.fr>
From: Juliusz Chroboczek <jch@irif.fr>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
In-Reply-To: <HE1PR0301MB22668B182167E8D7CD1F4E4A9D4A0@HE1PR0301MB2266.eurprd03.prod.outlook.com>
References: <BY2PR0201MB1910F03312F1A6360AB6790884640@BY2PR0201MB1910.namprd02.prod.outlook.com> <HE1PR0301MB22668B182167E8D7CD1F4E4A9D4A0@HE1PR0301MB2266.eurprd03.prod.outlook.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Tue, 31 Jan 2017 20:36:58 +0100 (CET)
X-Miltered: at korolev with ID 5890E759.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5890E759.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@irif.fr>
X-j-chkmail-Score: MSGID : 5890E759.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/TwJBP84exxxlEkjc_aPdVOPv4Vs>
Cc: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "'Zhangxian (Xian)'" <zhang.xian@huawei.com>, "russ@riw.us" <russ@riw.us>, "babel@ietf.org" <babel@ietf.org>, "<rtg-ads@ietf.org> (rtg-ads@ietf.org)" <rtg-ads@ietf.org>, Donald Eastlake <d3e3e3@gmail.com>, "Yemin (Amy)" <amy.yemin@huawei.com>, Jonathan Hardwick <Jonathan.Hardwick@metaswitch.com>, "Jon Hudson (jon.hudson@gmail.com)" <jon.hudson@gmail.com>
Subject: Re: [RTG-DIR] Routing area directorate early (QA) review of draft-ietf-babel-applicability
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-dir/>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jan 2017 19:37:11 -0000

Dear Sasha,

Thank you very much for your review.  These comments are very helpful, and
I wish I had had your guidance when I first drafted this document.

While there are some minor points I wish to discuss with you (I'll CC the
list when I do), I'll jump to the conclusions right now.  You suggest the
following three changes:

> - A reasonably detailed technical overview of BABEL in the draft based on a
> similar overview in the base spec

This sounds like a good idea, assuming that the technical introduction
does not need to be removed from 6126bis.  I like the technical
introduction in 6126bis.

> - Some level of detail about the networks where BABEL has been successfully
> deployed – where information is available and can be published without causing
> unnecessary conflicts

I'm not going to reply to this before I've at least attempted to gather
suitable data, but for now I'll just mention that:

  - in some cases, the data is easily available, or can be obtained
    without too much effort, and could be added to the document;
  - in some cases, the data is available in the peer-reviewed papers cited
    in the draft, and I'm not sure of the propriety of copy-pasting the
    results;
  - in other cases, the data is not easily available, or is available but
    cannot be published due to people having funny ideas about intellectual
    property (I'd name some names, but I'm not sure I'm allowed to);
  - in yet other cases, the data is simply not known, for many reasons, the
    main of which being that we haven't built an event-driven simulator
    for Babel yet.  (Let him who enjoys ns3 cast me the first stone.)

> - Information about actual impact of de-aggregation of routes on
> black-holing in existing BABEL deployments. If such impact has not been
> observed, a mere statement of the fact would suffice, of course.

As you justly guessed, we know that we don't know how to do automatic
aggregation/deaggregation in Babel, so we don't do it.  I'm planning to
work on that, since I believe it would be useful to at least three of the
major users of Babel.

Thanks again for your review,

-- Juliusz