IETF Logo Mail Archive

Re: [i2rs] Ignas Bagdonas' No Objection on draft-ietf-i2rs-rib-info-model-15: (with COMMENT)

"Susan Hares" <shares@ndzh.com> Thu, 05 April 2018 12:39 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E36A1273B1; Thu, 5 Apr 2018 05:39:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Level:
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, URIBL_BLOCKED=0.001] autolearn=no 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 k9E5L8uV-Qi4; Thu, 5 Apr 2018 05:39:08 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (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 1389E127201; Thu, 5 Apr 2018 05:39:08 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=166.170.24.89;
From: Susan Hares <shares@ndzh.com>
To: 'Ignas Bagdonas' <ibagdona@gmail.com>, 'The IESG' <iesg@ietf.org>
Cc: draft-ietf-i2rs-rib-info-model@ietf.org, i2rs-chairs@ietf.org, i2rs@ietf.org
References: <152292967776.25948.4861433804412654905.idtracker@ietfa.amsl.com>
In-Reply-To: <152292967776.25948.4861433804412654905.idtracker@ietfa.amsl.com>
Date: Thu, 05 Apr 2018 08:39:05 -0400
Message-ID: <03e101d3ccdb$1607a420$4216ec60$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQE0W70npgFU8mDNDZztarh3e5wFCaUw/nYg
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/SIhloMdD08PyHu67ZQrcV128_5k>
Subject: Re: [i2rs] Ignas Bagdonas' No Objection on draft-ietf-i2rs-rib-info-model-15: (with COMMENT)
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Apr 2018 12:39:10 -0000

Ignas:

Thank you for your comments.  I will check that these are addressed in the next version. 

Cheerily, Susan Hares

-----Original Message-----
From: Ignas Bagdonas [mailto:ibagdona@gmail.com] 
Sent: Thursday, April 5, 2018 8:01 AM
To: The IESG
Cc: draft-ietf-i2rs-rib-info-model@ietf.org; Susan Hares; i2rs-chairs@ietf.org; shares@ndzh.com; i2rs@ietf.org
Subject: Ignas Bagdonas' No Objection on draft-ietf-i2rs-rib-info-model-15: (with COMMENT)

Ignas Bagdonas has entered the following ballot position for
draft-ietf-i2rs-rib-info-model-15: No Objection

When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-i2rs-rib-info-model/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

A few nits:

Terminology: rib family vs address family. Address family term is more widely used in the industry.

VPLS is a subset of L2VPN.

ROUTER_ID usage is orthogonal to router virtualization. MUST restriction for the domain is factually incorrect - it is typically per source protocol, not per domain.

v2.23.0 | Report a Bug | By Email