Re: [Idr] I-D Action: draft-ietf-idr-segment-routing-te-policy-08.txt

Nandan Saha <nandan@arista.com> Tue, 19 November 2019 16:46 UTC

Return-Path: <nandan@arista.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 E898D1200CD for <idr@ietfa.amsl.com>; Tue, 19 Nov 2019 08:46:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=arista.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 533ZwpzZN3tG for <idr@ietfa.amsl.com>; Tue, 19 Nov 2019 08:46:50 -0800 (PST)
Received: from mail-ot1-x333.google.com (mail-ot1-x333.google.com [IPv6:2607:f8b0:4864:20::333]) (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 B86E212007A for <idr@ietf.org>; Tue, 19 Nov 2019 08:46:50 -0800 (PST)
Received: by mail-ot1-x333.google.com with SMTP id f10so18473233oto.3 for <idr@ietf.org>; Tue, 19 Nov 2019 08:46:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arista.com; s=googlenew; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=It5B6bW9xVnHrLLiVho5uW8paHlOScVRBMkS/Pg3KKI=; b=HvXcJE7J7twpeSpXH1QvzkyxDlso9Te9zMK221rvXCGQ9MIougFx5f/g98D8R3TET+ xoOJT3yG4tKtK0EXpmonOQhORx2rSRORwgyxd1xBTSL57r3jZGm4v+NSzBEUqgQrg+Z8 Ehu7PEuXruMbwLuAXQjOJHPmQAwV9qmBIdv0taPY3alluXMfvLLqmI1r3UGq+HZNdD40 hdcdskpoykAlHWZ20WgM+JzkT4mcdcd6gWGvdoVKxB9J/LxdVAuEjexp6Ra/+ItZzel9 e0Cv3nH2JDiDIe1XuvLGQfTkdRTyugc7mSRbmZ9YtpflOe0GXzVo2BVtmxxT4Yep4F6s AhNQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=It5B6bW9xVnHrLLiVho5uW8paHlOScVRBMkS/Pg3KKI=; b=XgXiUW7fw6NzyQrNKza8U0np90RbKgjkL4tx1nNop0hgol+7ZdYqwfvyUUIwCSvwoM tdTJl5JF1XRAV6Ux6bDDtn6I6ZBLwi9B91DkYOT95jyMy68MLCGRER1ST6iBPyQZqgNa TSYzuBy4quVLBcEVjpMUoYR84O0ydoAg6R00jmY9mviKJYJ/llQmzkgn4FdGl8aS9Ksi xfNp1aNO+I3MJR/1wKBc8Jqj8aD31+MEXFZvstToZ3T8PZmnANVwx4x1nxhsIw+27H9a 0kl1EHBcjVRT41KFvu9uuT92LK1rNyEr0H3eh0QTBB5pp37AjMW2C4qgoFYT4rzpXmJb k9Dw==
X-Gm-Message-State: APjAAAXpVzZauv8uTJ3dA0cW7NtZoh4zwSJD+lZWigKII6ByLmCf9DdR Wl34fKqaxneBkmsV4lSCkDRG7YkHSXwPo7ZPsVR+Qw==
X-Google-Smtp-Source: APXvYqxuq3Ly9wPxmxSCS2RcrKsqX/ZGKWk+jFPLCvaFM1QK0IT7Wpb7ehkwmFU6DPBRYWm7avrYTNGUO91LU4D7unQ=
X-Received: by 2002:a9d:82e:: with SMTP id 43mr4621394oty.23.1574182009874; Tue, 19 Nov 2019 08:46:49 -0800 (PST)
MIME-Version: 1.0
References: <157414471256.14003.6244444687150312939@ietfa.amsl.com> <CY4PR11MB1541D63781E529E2B2613F05C14C0@CY4PR11MB1541.namprd11.prod.outlook.com>
In-Reply-To: <CY4PR11MB1541D63781E529E2B2613F05C14C0@CY4PR11MB1541.namprd11.prod.outlook.com>
From: Nandan Saha <nandan@arista.com>
Date: Tue, 19 Nov 2019 22:16:38 +0530
Message-ID: <CAE+itjeJzygag3K4bA=KpDQgNie7shG8Z47YpMjfjMFF7aq=Tg@mail.gmail.com>
To: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
Cc: "idr@ietf.org" <idr@ietf.org>, Prakash Badrinarayanan <prakash@arista.com>, Manoharan Sundaramoorthy <manoharan@arista.com>
Content-Type: multipart/alternative; boundary="00000000000082d8a60597b5cf71"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Yaw0XB8DCOnDbXpWEjjncPBkbHk>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-segment-routing-te-policy-08.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 19 Nov 2019 16:46:54 -0000

Hi Ketan,
 Thank you for the updated version. I'm still reviewing it, but spotted
something I wanted to quickly clarify.

ver-7 of section "4.2.1. Acceptance of an SR Policy NLRI" had text
mandating RFC7606 TAW if acceptance criteria fail. In ver-8 this has been
removed, and I can't quite tell what text in section "5 Error Handling"
covers this? I'm assuming we still want to do TAW if acceptance criteria
fail.
Please clarify.

Thanks,
Nandan


On Tue, Nov 19, 2019 at 1:39 PM Ketan Talaulikar (ketant) <ketant@cisco.com>;
wrote:

> Hi All,
>
> This update of the draft is to get it ready for the WG to review towards
> WGLC .
>
> The following is the high level overview of the changes:
>
> 1) Introduced Error Handling section where all these aspects have been
> consolidated.
>
> 2) Added the request for IANA registry for Color Extended Community
> reserved field. Changed the process to Specification Required and added DE
> guidelines since the flags and other space is too small for FCFS.
>
> 3) Added security consideration section.
>
> 4) Add the clarification for handling of route target during propagation
> as per the request and discussions on the mailer and also clarified the
> matching with BGP Router ID part.
>
> 5) Changed the segment type naming from numbers to alphabets to align with
> upcoming update in the draft-ietf-segment-routing-policy to remove
> confusion between the segment types and the protocol code-points as
> discussed on the Spring and IDR lists recently.
>
> Besides this, there are other minor and editorial changes to prepare for
> WGLC.
>
> We are also trying to capture all the implementation reports at the wiki
> below and would request WG members to help update the same as there are
> multiple shipping implementations of this specification:
>
>
> https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-segment-routing-te-policy%20implementations%20
>
> Also note that the draft is on IDR agenda for presentation on Thu in
> Singapore.
>
> Thanks,
> Ketan (on behalf of co-authors)
>
> -----Original Message-----
> From: Idr <idr-bounces@ietf.org>; On Behalf Of internet-drafts@ietf.org
> Sent: 19 November 2019 14:25
> To: i-d-announce@ietf.org
> Cc: idr@ietf.org
> Subject: [Idr] I-D Action: draft-ietf-idr-segment-routing-te-policy-08.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Inter-Domain Routing WG of the IETF.
>
>         Title           : Advertising Segment
>     Routing Policies in BGP
>         Authors         : Stefano Previdi
>                           Clarence Filsfils
>                           Ketan Talaulikar
>                           Paul Mattes
>                           Eric Rosen
>                           Dhanendra Jain
>                           Steven Lin
>         Filename        : draft-ietf-idr-segment-routing-te-policy-08.txt
>         Pages           : 38
>         Date            : 2019-11-18
>
> Abstract:
>    This document defines a new BGP SAFI with a new NLRI in order to
>    advertise a candidate path of a Segment Routing (SR) Policy.  An SR
>    Policy is a set of candidate paths, each consisting of one or more
>    segment lists.  The headend of an SR Policy may learn multiple
>    candidate paths for an SR Policy.  Candidate paths may be learned via
>    a number of different mechanisms, e.g., CLI, NetConf, PCEP, or BGP.
>    This document specifies the way in which BGP may be used to
>    distribute SR Policy candidate paths.  New sub-TLVs for the Tunnel
>    Encapsulation Attribute are defined for signaling information about
>    these candidate paths.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-idr-segment-routing-te-policy/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-idr-segment-routing-te-policy-08
>
> https://datatracker.ietf.org/doc/html/draft-ietf-idr-segment-routing-te-policy-08
>
> A diff from the previous version is available at:
>
> https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-segment-routing-te-policy-08
>
>
> Please note that it may take a couple of minutes from the time of
> submission until the htmlized version and diff are available at
> tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>