Re: [Lsvr] Opsdir Early assignment: draft-ietf-lsvr-bgp-spf

"Acee Lindem (acee)" <acee@cisco.com> Fri, 03 August 2018 20:04 UTC

From: "Acee Lindem (acee)" <acee@cisco.com>
To: Fred Baker <fredbaker.ietf@gmail.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>
CC: "draft-ietf-lsvr-bgp-spf@ietf.org" <draft-ietf-lsvr-bgp-spf@ietf.org>, "lsvr@ietf.org" <lsvr@ietf.org>
Thread-Topic: Opsdir Early assignment: draft-ietf-lsvr-bgp-spf
Thread-Index: AQHUKd/7qJaZCpnX/E+g6+bnqGlvjqSudpWA
Date: Fri, 03 Aug 2018 20:04:22 +0000
Message-ID: <D6367239-80E9-4F62-BF42-F9E83581E1F8@cisco.com>
References: <153314620920.21810.13467365891728774868.idtracker@ietfa.amsl.com> <2253FE00-AC17-4D7D-8B85-F8FF7293FFE3@gmail.com>
In-Reply-To: <2253FE00-AC17-4D7D-8B85-F8FF7293FFE3@gmail.com>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.201]
Content-Type: text/plain; charset="utf-8"
Content-ID: <3F3B5CF2DA020B4CAB281807DEF44824@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 64.101.220.151, xch-rtp-011.cisco.com
X-Outbound-Node: alln-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsvr/KZJARSRgggV5CJwtJo9QQ-N-B74>
Subject: Re: [Lsvr] Opsdir Early assignment: draft-ietf-lsvr-bgp-spf
X-BeenThere: lsvr@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Link State Vector Routing <lsvr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsvr>, <mailto:lsvr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsvr/>
List-Post: <mailto:lsvr@ietf.org>
List-Help: <mailto:lsvr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsvr>, <mailto:lsvr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2018 20:04:27 -0000

Hi Fred, 
Thanks for reviewing. I've just started working on the -02 revision and will correct this error when I publish.
Thanks,
Acee


On 8/1/18, 5:38 PM, "Fred Baker" <fredbaker.ietf@gmail.com> wrote:

    
    
    > On Aug 1, 2018, at 10:56 AM, Gunter Van de Velde <gunter@vandevelde.cc> wrote:
    > 
    > 
    > Early review of: draft-ietf-lsvr-bgp-spf (rev. 01)
    > Deadline: 2018-08-24
    > Requested by: Gunter Van de Velde
    > 
    > https://datatracker.ietf.org/doc/draft-ietf-lsvr-bgp-spf/reviewrequest/10797/
    > 
    > Gunter Van de Velde has assigned you as a reviewer for this document.
    
    
    Reviewer: Fred Baker
    Review Result: Ready
    
    I have reviewed this document as part of the Operational directorate's
    ongoing effort to review all IETF documents being processed by the IESG.  These
    comments were written with the intent of improving the operational aspects of the
    IETF drafts. Comments that are not addressed in last call may be included in AD reviews
    during the IESG review.  Document editors and WG chairs should treat these comments
    just like any other last call comments.
    
    I read the draft in some detail. My big catch was, in section 5.4:
    
       Given the fact that SPF algorithms are based on the assumption that
       all routers in the routing domain calculate the precisely the same
       SPF tree and install the same set of routers
    
    The assumption is that all such routers install the same set of *routes*, not *routers*.
    
    And frankly, if that was my biggest issue, the draft is in pretty good shape.
    
    --------------------------------------------------------------------------------
    The fact that there is a highway to hell and a stairway to heaven is an interesting comment on projected traffic volume...

Re: [Lsvr] Opsdir Early assignment: draft-ietf-ls… Acee Lindem (acee)