Re: [spring] I-D Action: draft-ietf-spring-segment-routing-mpls-07.txt

"Stefano Previdi (sprevidi)" <sprevidi@cisco.com> Tue, 07 February 2017 13:52 UTC

Return-Path: <sprevidi@cisco.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE089129C23 for <spring@ietfa.amsl.com>; Tue, 7 Feb 2017 05:52:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 10Mibis0NvyH for <spring@ietfa.amsl.com>; Tue, 7 Feb 2017 05:52:44 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDBE9129C24 for <spring@ietf.org>; Tue, 7 Feb 2017 05:52:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2566; q=dns/txt; s=iport; t=1486475535; x=1487685135; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=ms/drDRTSGgjpf8Nu23f6XiNqb5YMtH3TMHitzzZNIk=; b=PryF1BkkA/XM/uR5BdoYY/PiRsk4xcvcivLF/2nLmX+wvQHcU3IVFw9I n+qtjt+EZXtAW9sfCiZD08bjjS7gvCRREHQIXTmRBkp6qIdL5d3nHigT0 yJ7YTsrlbTZMv8khMFwZkCJOEhjLECpASZBbsxRrto2VkbjRbK5qkd2Er I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AVAQDpz5lY/4wNJK1dGQEBAQEBAQEBAQEBBwEBAQEBg1FhgQkHjVmSD5U2ggwfDYUsSgKCTj8YAQIBAQEBAQEBYiiEaQEBAQMBAQE4NBALAgEIEgYeECcLFw4CBBOJawgOsguLVQEBAQEBAQEBAQEBAQEBAQEBAQEBAR2GTIIFgmqDF4E9gzSCMQWbawGGaYskgXtThESJcZMOAR84fk8VGCQRAYYwdYgSgQwBAQE
X-IronPort-AV: E=Sophos;i="5.33,346,1477958400"; d="scan'208";a="380984875"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 07 Feb 2017 13:52:14 +0000
Received: from XCH-RTP-006.cisco.com (xch-rtp-006.cisco.com [64.101.220.146]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v17DqERC013157 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <spring@ietf.org>; Tue, 7 Feb 2017 13:52:14 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-006.cisco.com (64.101.220.146) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 7 Feb 2017 08:52:13 -0500
Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1210.000; Tue, 7 Feb 2017 08:52:13 -0500
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: SPRING WG <spring@ietf.org>
Thread-Topic: [spring] I-D Action: draft-ietf-spring-segment-routing-mpls-07.txt
Thread-Index: AQHSgUk6r/++7U/1Sk6pHVXs6WjioKFd5AOA
Date: Tue, 07 Feb 2017 13:52:13 +0000
Message-ID: <879DE4A5-E494-41A0-A6C4-335CA1A622FB@cisco.com>
References: <148647545948.16284.8360784393021155625.idtracker@ietfa.amsl.com>
In-Reply-To: <148647545948.16284.8360784393021155625.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.213.28]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <22AF0CF2F2C5774F813AD34248277EC8@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/Fe2vyYf-B0uRzjD6tcfKYWvL4Jw>
Subject: Re: [spring] I-D Action: draft-ietf-spring-segment-routing-mpls-07.txt
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 13:52:46 -0000

this is the updated version after all received comments.

Thanks.
s.


> On Feb 7, 2017, at 2:50 PM, 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 Source Packet Routing in Networking of the IETF.
> 
>        Title           : Segment Routing with MPLS data plane
>        Authors         : Clarence Filsfils
>                          Stefano Previdi
>                          Ahmed Bashandy
>                          Bruno Decraene
>                          Stephane Litkowski
>                          Martin Horneffer
>                          Rob Shakir
>                          Jeff Tantsura
>                          Edward Crabbe
> 	Filename        : draft-ietf-spring-segment-routing-mpls-07.txt
> 	Pages           : 16
> 	Date            : 2017-02-07
> 
> Abstract:
>   Segment Routing (SR) leverages the source routing paradigm.  A node
>   steers a packet through a controlled set of instructions, called
>   segments, by prepending the packet with an SR header.  In the MPLS
>   dataplane, the SR header is instantiated through a label stack.  A
>   segment can represent any instruction, topological or service-based.
>   Additional segments can be defined in the future.  SR allows to
>   enforce a flow through any topological path and/or service chain
>   while maintaining per-flow state only at the ingress node to the SR
>   domain.
> 
>   Segment Routing can be directly applied to the MPLS architecture with
>   no change in the forwarding plane.  This drafts describes how Segment
>   Routing operates on top of the MPLS data plane.
> 
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing-mpls/
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-spring-segment-routing-mpls-07
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-spring-segment-routing-mpls-07
> 
> 
> 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/
> 
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring