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

"Stefano Previdi (sprevidi)" <sprevidi@cisco.com> Thu, 16 February 2017 22:31 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 AF8E7129560 for <spring@ietfa.amsl.com>; Thu, 16 Feb 2017 14:31:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level:
X-Spam-Status: No, score=-14.523 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, 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 jbotzrX4HjQB for <spring@ietfa.amsl.com>; Thu, 16 Feb 2017 14:31:34 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01530129457 for <spring@ietf.org>; Thu, 16 Feb 2017 14:31:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3025; q=dns/txt; s=iport; t=1487284294; x=1488493894; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=PchapOTIFRcH1Li7a+ctfzOHxY1wLaK+GIAfH8MNjYk=; b=P2IiJM7Vc9Sh57jCaFC0w/9Mn9suKW1303JHA/k7AZHsaEhAPk4FWbxy 8a9TEMoj5YS6/uHCOiNjB/XbrwnCqfWNRrE8PKTKVS8t8lpSROEQ7p9sS brgleHPMLxZw7rK+fgh2yOeWQpHcUkSOuwbxCloD5U0rF/biD/2IEXkRi s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CJAQDaJ6ZY/5NdJa1eGQEBAQEBAQEBAQEBBwEBAQEBg1FhgQkHjVqRcB+VM4IMHwuFeAKCED8YAQIBAQEBAQEBYiiEcAEBAQMBAQE4NBALAgEIEgYeECcLFw4CBBMJiVsIDrJ0i1YBAQEBAQEBAQEBAQEBAQEBAQEBAQEdhkyCBQiCYoMXgT0ygwKCMQWbfwGGb4sngXtThESJdIpaiD0BHzg8RFEVGCURAYYydQGJKYENAQEB
X-IronPort-AV: E=Sophos;i="5.35,169,1484006400"; d="scan'208";a="385879795"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Feb 2017 22:31:33 +0000
Received: from XCH-RTP-008.cisco.com (xch-rtp-008.cisco.com [64.101.220.148]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id v1GMVWEh002873 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <spring@ietf.org>; Thu, 16 Feb 2017 22:31:32 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-008.cisco.com (64.101.220.148) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 16 Feb 2017 17:31:32 -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; Thu, 16 Feb 2017 17:31:31 -0500
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: SPRING WG <spring@ietf.org>
Thread-Topic: I-D Action: draft-ietf-spring-segment-routing-11.txt
Thread-Index: AQHSiKRDA7WrBPJiEU6hpQ2ZNv20NqFsi1wA
Date: Thu, 16 Feb 2017 22:31:31 +0000
Message-ID: <A5A327E3-40F3-45C1-9462-2DBC2BA3C475@cisco.com>
References: <148728420973.1067.1725012678592216776.idtracker@ietfa.amsl.com>
In-Reply-To: <148728420973.1067.1725012678592216776.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.209.26]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8C92044A5B8418469F00C60546C740F4@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/3Byzgj-SEVB1k-51XDI_-Vko4dE>
Subject: Re: [spring] I-D Action: draft-ietf-spring-segment-routing-11.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: Thu, 16 Feb 2017 22:31:36 -0000

Hi,

this version integrates various comments received during the WG last call and by the shepherd review.

Thanks.
s.


> On Feb 16, 2017, at 11:30 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 Architecture
>        Authors         : Clarence Filsfils
>                          Stefano Previdi
>                          Bruno Decraene
>                          Stephane Litkowski
>                          Rob Shakir
> 	Filename        : draft-ietf-spring-segment-routing-11.txt
> 	Pages           : 28
> 	Date            : 2017-02-16
> 
> 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.  A segment can have a semantic local to an SR node or
>   global within an SR domain.  SR allows to enforce a flow through any
>   topological path and service chain while maintaining per-flow state
>   only at the ingress nodes to the SR domain.
> 
>   Segment Routing can be directly applied to the MPLS architecture with
>   no change on the forwarding plane.  A segment is encoded as an MPLS
>   label.  An ordered list of segments is encoded as a stack of labels.
>   The segment to process is on the top of the stack.  Upon completion
>   of a segment, the related label is popped from the stack.
> 
>   Segment Routing can be applied to the IPv6 architecture, with a new
>   type of routing header.  A segment is encoded as an IPv6 address.  An
>   ordered list of segments is encoded as an ordered list of IPv6
>   addresses in the routing header.  The active segment is indicated by
>   the Destination Address of the packet.  The next active segment is
>   indicated by a pointer in the new routing header.
> 
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing/
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-spring-segment-routing-11
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-spring-segment-routing-11
> 
> 
> 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/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt