[Idr] FW: I-D Action: draft-ietf-idr-bgpls-segment-routing-epe-17.txt

"Susan Hares" <shares@ndzh.com> Fri, 19 October 2018 17:12 UTC

Return-Path: <shares@ndzh.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 89D8D12426A for <idr@ietfa.amsl.com>; Fri, 19 Oct 2018 10:12:12 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 Wad-audSUxPJ for <idr@ietfa.amsl.com>; Fri, 19 Oct 2018 10:12:11 -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 4F13B130DC1 for <idr@ietf.org>; Fri, 19 Oct 2018 10:12:11 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=166.170.26.143;
From: Susan Hares <shares@ndzh.com>
To: "'Ketan Talaulikar (ketant)'" <ketant@cisco.com>
Cc: idr@ietf.org
References: <153995947824.6550.6797438271064339339@ietfa.amsl.com>
In-Reply-To: <153995947824.6550.6797438271064339339@ietfa.amsl.com>
Date: Fri, 19 Oct 2018 13:12:06 -0400
Message-ID: <02a701d467ce$dd7715c0$98654140$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQK1AdeRtOqaEv4G84mHnuxn8qCgpKNll75A
Content-Language: en-us
X-Antivirus: AVG (VPS 181019-4, 10/19/2018), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/5sOlvHD7Izk7IUaqVbwElHQuE5s>
Subject: [Idr] FW: I-D Action: draft-ietf-idr-bgpls-segment-routing-epe-17.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: Fri, 19 Oct 2018 17:12:13 -0000

Ketan: 

I do not see any reference to a revised RFC7752 in the security section of
this draft.   

If you agree we need a revised RFC7752 draft, please add this text to the
security section.  

"RFC7752 security considerations may need to be expanded to cover the
extensions in this draft.   The need to extend the RFC7752 security is
common to many drafts that utilize BGP-LS defined in  RFC7752 so this work
is being undertaken in an RFC7752bis rather than this draft."  

If you add this, I can start the 1 week review on text.  

Cheerily,  Sue 


-----Original Message-----
From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of
internet-drafts@ietf.org
Sent: Friday, October 19, 2018 10:31 AM
To: i-d-announce@ietf.org
Cc: idr@ietf.org
Subject: [Idr] I-D Action: draft-ietf-idr-bgpls-segment-routing-epe-17.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           : BGP-LS extensions for Segment Routing BGP Egress
Peer Engineering
        Authors         : Stefano Previdi
                          Ketan Talaulikar
                          Clarence Filsfils
                          Keyur Patel
                          Saikat Ray
                          Jie Dong
	Filename        : draft-ietf-idr-bgpls-segment-routing-epe-17.txt
	Pages           : 23
	Date            : 2018-10-19

Abstract:
   Segment Routing (SR) leverages source routing.  A node steers a
   packet through a controlled set of instructions, called segments, by
   prepending the packet with an SR header.  A segment can represent any
   instruction, topological or service-based.  SR segments allow
   steering a flow through any topological path and service chain while
   maintaining per-flow state only at the ingress node of the SR domain.

   This document describes an extension to BGP Link State (BGP-LS) for
   advertisement of BGP Peering Segments along with their BGP peering
   node information so that efficient BGP Egress Peer Engineering (EPE)
   policies and strategies can be computed based on Segment Routing.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-bgpls-segment-routing-epe/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-idr-bgpls-segment-routing-epe-17
https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgpls-segment-routing-e
pe-17

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-bgpls-segment-routing-epe-1
7


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