Re: [Idr] I-D Action: draft-ietf-idr-bgp-prefix-sid-27.txt

"Acee Lindem (acee)" <acee@cisco.com> Tue, 26 June 2018 19:26 UTC

Return-Path: <acee@cisco.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 BF1C8131111 for <idr@ietfa.amsl.com>; Tue, 26 Jun 2018 12:26:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.087
X-Spam-Level:
X-Spam-Status: No, score=-12.087 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_COMMENT_SAVED_URL=1.391, HTML_MESSAGE=0.001, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, T_HTML_ATTACH=0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 qI6gVaDnCMYQ for <idr@ietfa.amsl.com>; Tue, 26 Jun 2018 12:26:43 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FED813110E for <idr@ietf.org>; Tue, 26 Jun 2018 12:26:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=51209; q=dns/txt; s=iport; t=1530041203; x=1531250803; h=from:cc:subject:date:message-id:references:in-reply-to: mime-version; bh=bwyTaXWLjfZTafgM+LCWRR3OEoFnsI4MTFTq/rXQRCI=; b=FvtB4cICXdxqQoIEHGVP4Z6tG2S89y/Yv9WbeTPmvPJ7ZEZCgi6YjldJ Fk4AHion+sZ944kPCfDgjfdas17rqucs8g1wSYRixUkueWhgpuR2o+aC1 pRjCVLjXAxFoQa5ZaRcxJp/CJm///mCPUIkAwQFu9s2xL7+LeZ4U2OK/A s=;
X-Files: Diff_ draft-ietf-idr-bgp-prefix-sid-26.txt - draft-ietf-idr-bgp-prefix-sid-27.txt.htm : 34003
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DZAAC9kjJb/5pdJa1cGQEBAQEBAQEBAQEBAQcBAQEBAYMbDwEBAQEhYn8ZDwqDb4FfhiWOGASHS416FIFjAwsYAQyDEIE3AhcMgnAhNBgBAgEBAQEBAQJtHAyFLgkCBAEBIQpBCxACAQgSJgEJAgICJQsXDgISBQ5OgkkBgX8PrUeCHIRbg2+BDQ+GOIEegReCFYEPJ4Jogw0LAQECAQEWgQsIARIBXYJDFB2CJAKQTYJohXwJAoNUgiuFVIM/gUAdJYNFhm2BFoomhyQCERMBgSQdOGFxcBUaISoBcgqBQgmBajAXiFmFPm8BjUaBH4EaAQ
X-IronPort-AV: E=Sophos;i="5.51,275,1526342400"; d="htm'217?scan'217,208,217";a="413682596"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Jun 2018 19:26:41 +0000
Received: from XCH-RTP-013.cisco.com (xch-rtp-013.cisco.com [64.101.220.153]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id w5QJQfHr021901 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <idr@ietf.org>; Tue, 26 Jun 2018 19:26:41 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-013.cisco.com (64.101.220.153) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 26 Jun 2018 15:26:40 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1320.000; Tue, 26 Jun 2018 15:26:40 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
CC: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] I-D Action: draft-ietf-idr-bgp-prefix-sid-27.txt
Thread-Index: AQHUDYMsziyE5ypOtEmu3SaiJ3vfj6Ry7C4A
Date: Tue, 26 Jun 2018 19:26:40 +0000
Message-ID: <8C2AF03B-82D5-476F-B00A-8B519138480B@cisco.com>
References: <153004094312.18770.2314154950613624277@ietfa.amsl.com>
In-Reply-To: <153004094312.18770.2314154950613624277@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.202]
Content-Type: multipart/mixed; boundary="_002_8C2AF03B82D5476FB00A8B519138480Bciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/YhGujRaI4rPKD0kQzeRWrArKE7Q>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-bgp-prefix-sid-27.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.26
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, 26 Jun 2018 19:26:46 -0000

Hi, 

We've had some 13th hour discussions related to the SRGB E-mail thread that Sue started. I've added some clarifications to this version of the draft. The diff is attached. Hopefully no one is opposed to these or feels the draft require further delays.  

Thanks,
Acee 

On 6/26/18, 3:23 PM, "Idr on behalf of internet-drafts@ietf.org" <idr-bounces@ietf.org on behalf of internet-drafts@ietf.org> wrote:

    
    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           : Segment Routing Prefix SID extensions for BGP
            Authors         : Stefano Previdi
                              Clarence Filsfils
                              Acee Lindem
                              Arjun Sreekantiah
                              Hannes Gredler
    	Filename        : draft-ietf-idr-bgp-prefix-sid-27.txt
    	Pages           : 17
    	Date            : 2018-06-26
    
    Abstract:
       Segment Routing (SR) leverages the source routing paradigm.  A node
       steers a packet through an ordered list of instructions, called
       segments.  A segment can represent any instruction, topological or
       service-based.  The ingress node prepends an SR header to a packet
       containing a set of segment identifiers (SID).  Each SID represents a
       topological or a service-based instruction.  Per-flow state is
       maintained only on the ingress node of the SR domain.  An SR domain
       is defined as a single administrative domain for global SID
       assignment.
    
       This document defines an optional, transitive BGP attribute for
       announcing BGP Prefix Segment Identifiers (BGP Prefix-SID)
       information and the specification for SR-MPLS SIDs.
    
    
    
    The IETF datatracker status page for this draft is:
    https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-prefix-sid/
    
    There are also htmlized versions available at:
    https://tools.ietf.org/html/draft-ietf-idr-bgp-prefix-sid-27
    https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-prefix-sid-27
    
    A diff from the previous version is available at:
    https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-bgp-prefix-sid-27
    
    
    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