[spring] I-D Action: draft-ietf-spring-ipv6-use-cases-09.txt
internet-drafts@ietf.org Fri, 10 February 2017 14:13 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: spring@ietf.org
Delivered-To: spring@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CA741129979; Fri, 10 Feb 2017 06:13:52 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148673603282.29317.17522709252166613216.idtracker@ietfa.amsl.com>
Date: Fri, 10 Feb 2017 06:13:52 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/8KhIWZc95OL9tZZUAoKdyY0OhQ4>
Cc: spring@ietf.org
Subject: [spring] I-D Action: draft-ietf-spring-ipv6-use-cases-09.txt
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 10 Feb 2017 14:13:53 -0000
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 : IPv6 SPRING Use Cases Authors : John Brzozowski John Leddy Clarence Filsfils Roberta Maglione Mark Townsley Filename : draft-ietf-spring-ipv6-use-cases-09.txt Pages : 12 Date : 2017-02-10 Abstract: Source Packet Routing in Networking (SPRING) architecture leverages the source routing paradigm. A node steers a packet through a controlled set of instructions, called segments, by prepending the packet with SPRING header. A segment can represent any instruction, topological or service-based. A segment can have a local semantic to the SPRING node or global within the SPRING domain. SPRING allows to enforce a flow through any topological path and service chain while maintaining per-flow state only at the ingress node to the SPRING domain. The objective of this document is to illustrate some use cases that need to be taken into account by the Source Packet Routing in Networking (SPRING) architecture. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-spring-ipv6-use-cases/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-spring-ipv6-use-cases-09 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-spring-ipv6-use-cases-09 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] I-D Action: draft-ietf-spring-ipv6-use-c… internet-drafts