[spring] Fwd: New Version Notification for draft-filsfils-spring-sr-recursing-info-04.txt

"Stefano Previdi (sprevidi)" <sprevidi@cisco.com> Tue, 11 April 2017 07:06 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 963961292C5 for <spring@ietfa.amsl.com>; Tue, 11 Apr 2017 00:06:50 -0700 (PDT)
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 pMNuZdrFjPzr for <spring@ietfa.amsl.com>; Tue, 11 Apr 2017 00:06:49 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0510126B6E for <spring@ietf.org>; Tue, 11 Apr 2017 00:06:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2227; q=dns/txt; s=iport; t=1491894408; x=1493104008; h=from:to:subject:date:message-id:references:content-id: content-transfer-encoding:mime-version; bh=TUCXVrO4FcBf4CSLEuhv5yz+Xsgkny2YpEACxqLryl4=; b=hXCxGuXWmfxnD+6GlH4c7JtCHbiK0HRRRxs+udi2A4lHaKpgDu/3mkvA m62ZTjcr0jnvQ7exrz9EgOhOEpuxvTiw7EMSXsThj9gplHC8qVB0MOO9L Fu/2Og2Ehg1uaewk0eiK1YH0XABQpGiiXbpY7zcavm0dMonfzWfBmxoIr 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AbAQCjf+xY/4wNJK1bGQEBAQEBAQEBAQEBBwEBAQEBg1NhgQsHjXKRSZVYgg8uhXYCg2k/GAECAQEBAQEBAWsohRUBAQICATo9BwsCARkDAQIfEDIbAggCBBOKCAgOqx2LAAEBAQEBAQEDAQEBAQEBAQEBH4ZQggWCa4MXhHOCMQWPbI0RAYZ/gyuIMIF/VYRZihWTfwEfOIEFWxUYOgGESRwZgUp1AYhHgQ0BAQE
X-IronPort-AV: E=Sophos;i="5.37,184,1488844800"; d="scan'208";a="229610601"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 Apr 2017 07:06:47 +0000
Received: from XCH-RTP-008.cisco.com (xch-rtp-008.cisco.com [64.101.220.148]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v3B76lbo021849 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <spring@ietf.org>; Tue, 11 Apr 2017 07:06:47 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; Tue, 11 Apr 2017 03:06:46 -0400
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, 11 Apr 2017 03:06:46 -0400
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: SPRING WG <spring@ietf.org>
Thread-Topic: New Version Notification for draft-filsfils-spring-sr-recursing-info-04.txt
Thread-Index: AQHSspHtBep1vgKVwUum7Ad5x+reUQ==
Date: Tue, 11 Apr 2017 07:06:46 +0000
Message-ID: <9FB153C8-4D13-40BA-94A9-290F3872D04C@cisco.com>
References: <149189429415.15800.5467116753076877527.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.83.87]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A5D86BB63A9D0C4280399329C5E5797D@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/PpHeC-Re3QwfyLMwS70Rg0d3O-g>
Subject: [spring] Fwd: New Version Notification for draft-filsfils-spring-sr-recursing-info-04.txt
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.22
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, 11 Apr 2017 07:06:50 -0000

All, 

this is a refresh of draft-filsfils-spring-sr-recursing-info.

The authors believe this document is ready for WG adoption and would like to request the chairs to initiate the call.

Thanks.
s.



> Begin forwarded message:
> 
> From: <internet-drafts@ietf.org>
> Subject: New Version Notification for draft-filsfils-spring-sr-recursing-info-04.txt
> Date: April 11, 2017 at 9:04:54 AM GMT+2
> To: Clarence Filsfils <cfilsfil@cisco.com>, Peter Psenak <ppsenak@cisco.com>, Stefano Previdi <sprevidi@cisco.com>, Les Ginsberg <ginsberg@cisco.com>
> 
> 
> A new version of I-D, draft-filsfils-spring-sr-recursing-info-04.txt
> has been successfully submitted by Stefano Previdi and posted to the
> IETF repository.
> 
> Name:		draft-filsfils-spring-sr-recursing-info
> Revision:	04
> Title:		Segment Routing Recursive Information
> Document date:	2017-04-11
> Group:		spring
> Pages:		8
> URL:            https://www.ietf.org/internet-drafts/draft-filsfils-spring-sr-recursing-info-04.txt
> Status:         https://datatracker.ietf.org/doc/draft-filsfils-spring-sr-recursing-info/
> Htmlized:       https://tools.ietf.org/html/draft-filsfils-spring-sr-recursing-info-04
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-filsfils-spring-sr-recursing-info-04
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-filsfils-spring-sr-recursing-info-04
> 
> Abstract:
>   Segment Routing (SR) allows for a flexible definition of end-to-end
>   paths within IGP topologies by encoding paths as sequences of
>   topological sub-paths, called "segments".  These segments are
>   advertised by the link-state routing protocols (IS-IS and OSPF).
> 
>   There are use cases where it is desirable to utilize a SID associated
>   with a given node in order to transport traffic destined to different
>   local services supported by such node.  This document defines the
>   mechanism to do so and illustrates it.
> 
> 
> 
> 
> 
> 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
>