[spring] I-D Action: draft-ietf-spring-ipv6-use-cases-08.txt

internet-drafts@ietf.org Mon, 30 January 2017 22:04 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 29D19129BDD; Mon, 30 Jan 2017 14:04:34 -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.41.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148581387416.29775.17064865209518881482.idtracker@ietfa.amsl.com>
Date: Mon, 30 Jan 2017 14:04:34 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/rmcxte4lKemde4uOA_uuZZjoSCk>
Cc: spring@ietf.org
Subject: [spring] I-D Action: draft-ietf-spring-ipv6-use-cases-08.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: Mon, 30 Jan 2017 22:04:34 -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
                          Mark Townsley
                          Clarence Filsfils
                          Roberta Maglione
	Filename        : draft-ietf-spring-ipv6-use-cases-08.txt
	Pages           : 11
	Date            : 2017-01-30

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 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-08

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-spring-ipv6-use-cases-08


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/