Re: [Idr] WG LC for draft-ietf-idr-bgp-ls-segment-routing-ext-04 (March 7 to March 21)

Robert Raszuk <robert@raszuk.net> Thu, 08 March 2018 09:36 UTC

Return-Path: <rraszuk@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99466124BE8 for <idr@ietfa.amsl.com>; Thu, 8 Mar 2018 01:36:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 ErKTuP1PHX2X for <idr@ietfa.amsl.com>; Thu, 8 Mar 2018 01:36:09 -0800 (PST)
Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::232]) (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 A0B061205F0 for <idr@ietf.org>; Thu, 8 Mar 2018 01:36:08 -0800 (PST)
Received: by mail-wr0-x232.google.com with SMTP id f14so4949272wre.8 for <idr@ietf.org>; Thu, 08 Mar 2018 01:36:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=BEZqicl78zjMUq6SqKM2s3HJvrGwWbcnS7q2rPjYcDo=; b=a/53RM+cxGI1M43thku1iovanqVRRD8xjKkcjInpT9/c4yIc1TcxQY4w9gNjzMeI/0 S5/pQhQro1ZntOODsC/nbExNLI2lyFyUyee1FTZezWanjK7CMKWMUWX2UF8GsskMLQo+ /X4cB5CFFJYS44annrlsbnQXVwV4Y40YopaYJLWIRl2OPySEKJtjwBEO5H6M/6WRkV6y Q3URJ0IhGugHnpTwxziz33chU7HYniWTHacHOAENLe4e8zRsHZFYyaX7ocp2bBLsR+E7 dA6SQ/OkHxP0Aw4RzPYgOBwqphhWu0b+mh80yyLOK76IjdRpVd2iYSJT9IWJmFn4yLSi nHLg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=BEZqicl78zjMUq6SqKM2s3HJvrGwWbcnS7q2rPjYcDo=; b=sxNko7hKJ+cDhnLqodl9mU3L1PhXWcpm2DoXUrcf5kH7Jq39d0kpKXhKorQwj91JyQ OSZpd60tROWYf0D+qSQl7rjcqzR4raMhjuL8BKbjKkb0afok19nDkwk3yHL5dJaRA5vV QhwDuQaGbCr5KsgQCfp7p6YRUaaY+PiBl1lKkT3o48n1en1SOUFQbbz8nTTuvu3EiwXs 7DyMag6T4HJWk9Y/VwwGLb1AfFwuISujQCC5icZt2k5QYtlwpwT3rpdry3zXZBlJteqC LQoU+7iS5SdGV+ctjX9PMBZhTnmZdN78ZYeQ3RCNyfv2MIBv0ltpvUuN27ptBSDaU623 pPvg==
X-Gm-Message-State: APf1xPAQVqQ4Sflu+ONqcgRFE4EUcp1IfXwQWta6bXVwDjHAQJTW5lk+ TphdTagP1zr+eqmiGfzEm+f3y2GZUvyRwaCcz2x7Afmy
X-Google-Smtp-Source: AG47ELtTUvjZOwHalhWpEajyYmj1lHYYmJVGnJzWyKsbPMyGqA7Infon1xVgXj4ydX2uMdkvf9YEbcUFYKDlp8DUjEM=
X-Received: by 10.223.157.22 with SMTP id k22mr20629461wre.208.1520501766933; Thu, 08 Mar 2018 01:36:06 -0800 (PST)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.28.66.2 with HTTP; Thu, 8 Mar 2018 01:36:06 -0800 (PST)
In-Reply-To: <011201d3b633$0b5fee60$221fcb20$@ndzh.com>
References: <011201d3b633$0b5fee60$221fcb20$@ndzh.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Thu, 8 Mar 2018 10:36:06 +0100
X-Google-Sender-Auth: dSLLdVbmhWtvLAHZn7uCnphmxCg
Message-ID: <CA+b+ERkNB_94SmA4Dm3qpreywtACqWC8JyeR6Z9KQQXw6G6RUg@mail.gmail.com>
To: Susan Hares <shares@ndzh.com>
Cc: idr wg <idr@ietf.org>
Content-Type: multipart/alternative; boundary="f40304389254b2d37e0566e36714"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/A1s5lp_6fESKh2ePil1R_nLtUew>
Subject: Re: [Idr] WG LC for draft-ietf-idr-bgp-ls-segment-routing-ext-04 (March 7 to March 21)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2018 09:36:11 -0000

Hello Susan,

> ​1​
> )      Do you think BGP should carry these link state information
> regarding segment routing,
>
> ​If BGP already has been extended ​to carry link state information by RFC
7752 there is no question if it should be extended to also carry SR
information. The answer is clearly - Yes.

/* Said this IMHO RFC 7752 itself is a mistake on its own ... BGP is a
great p2mp transport of routing information and information discussed is
used primarily in p2p fashion. So allowing RFC 7752 to go forward just to
reuse BGP transport and sessions to carry link state information only delays
  us to work and widely deploy much proper alternative transport(s) for
those kind of information. */

> 2)      Are there any technical issues with this draft?
>
​Don't think so. ​

> 3)      Is this draft is ready for publication?
>
​Yes.

Cheers,
Robert.​




>  For your quick access to this draft, click on the link below:
>
>
>
> https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-
> segment-routing-ext/
>
>
>
>
>
> Susan Hares
>
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>
>