Subject: [spring] Fwd: New Version Notification for draft-ietf-spring-problem-statement-02.txt

From: "Stefano Previdi (sprevidi)" <[email-masked]>
Date: Wed, 1 Oct 2014 12:17:10 +0000

FYI,

very minor fixes and removed from the EPE section any reference to a possible solution (so to remain in line with what a problem statement should be).

Thanks.
s.

Begin forwarded message:
> From: <[email-masked]>
> Subject: New Version Notification for draft-ietf-spring-problem-statement-02.txt
> Date: October 1, 2014 2:15:34 PM GMT+02:00
> To: Stefano Previdi <[email-masked]>, Bruno Decraene <[email-masked]>, Martin Horneffer <[email-masked]>, Rob Shakir <[email-masked]>, Stephane Litkowski <[email-masked]>, Clarence Filsfils <[email-masked]>, Bruno Decraene <[email-masked]>, Stefano Previdi <[email-masked]>, Clarence Filsfils <[email-masked]>, Rob Shakir <[email-masked]>, Martin Horneffer <[email-masked]>, "Stephane Litkowski" <[email-masked]>
> 
> 
> A new version of I-D, draft-ietf-spring-problem-statement-02.txt
> has been successfully submitted by Stefano Previdi and posted to the
> IETF repository.
> 
> Name:		draft-ietf-spring-problem-statement
> Revision:	02
> Title:		SPRING Problem Statement and Requirements
> Document date:	2014-10-01
> Group:		spring
> Pages:		18
> URL:            http://www.ietf.org/internet-drafts/draft-ietf-spring-problem-statement-02.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-spring-problem-statement/
> Htmlized:       http://tools.ietf.org/html/draft-ietf-spring-problem-statement-02
> Diff:           http://www.ietf.org/rfcdiff?url2=draft-ietf-spring-problem-statement-02
> 
> Abstract:
>   The ability for a node to specify a forwarding path, other than the
>   normal shortest path, that a particular packet will traverse,
>   benefits a number of network functions.  Source-based routing
>   mechanisms have previously been specified for network protocols, but
>   have not seen widespread adoption.  In this context, the term
>   'source' means 'the point at which the explicit route is imposed'.
> 
>   This document outlines various use cases, with their requirements,
>   that need to be taken into account by the Source Packet Routing in
>   Networking (SPRING) architecture for unicast traffic.  Multicast use-
>   cases and requirements are out of scope of this document.
> 
> 
> 
> 
> 
> 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.
> 
> The IETF Secretariat
>