FW: New Version Notification for draft-vyncke-6man-segment-routing-security-02.txt
"Eric Vyncke (evyncke)" <evyncke@cisco.com> Fri, 27 February 2015 09:56 UTC
Return-Path: <evyncke@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C46F11A8874 for <ipv6@ietfa.amsl.com>; Fri, 27 Feb 2015 01:56:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 hC9s6v0XQ4PJ for <ipv6@ietfa.amsl.com>; Fri, 27 Feb 2015 01:56:20 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 384361A887A for <ipv6@ietf.org>; Fri, 27 Feb 2015 01:56:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2854; q=dns/txt; s=iport; t=1425030980; x=1426240580; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=+AveCk3hkHhtU2h1ObTQsv0ooCn8CyURYAkl6NzDHuc=; b=kwfHT3POh94Ht4LVU6wcKW/YoHrPf7Wmn+l11kgZJv1JBSLzPf0lzyc4 yZuxhoCEA5/HzuGZNDxphvmQltHGMpixdSqPA9W0R/foOTLpmKFiKeXdv 71KWymNJLt0TRRTuTgfEfUH0QTI2J1lvNtpCQ7RU0A8Pfn/7SJ9eNnZ4W Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0C9BQCNPvBU/5ldJa1bgwJSVQUEgwa/DIVuAhyBBE0BAQEBAQF8hBABAQQjEUMCEAIBCBoCJgICAjAVBgEGAwIEDgUJiCYIBbxXmhIBAQEBAQEBAQEBAQEBAQEBAQEBAQEXgSGJcYRTGweCaIFDBY90g2CFZoEbOYJljxgjgjKBPG+BRH8BAQE
X-IronPort-AV: E=Sophos;i="5.09,658,1418083200"; d="scan'208";a="399611332"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-6.cisco.com with ESMTP; 27 Feb 2015 09:56:19 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t1R9uJx1014399 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 27 Feb 2015 09:56:19 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.138]) by xhc-rcd-x04.cisco.com ([173.37.183.78]) with mapi id 14.03.0195.001; Fri, 27 Feb 2015 03:56:19 -0600
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: FW: New Version Notification for draft-vyncke-6man-segment-routing-security-02.txt
Thread-Topic: New Version Notification for draft-vyncke-6man-segment-routing-security-02.txt
Thread-Index: AQHQUm9hZx9CAiVS4kmhFOcY6G1cgZ0Et4YA
Date: Fri, 27 Feb 2015 09:56:18 +0000
Message-ID: <D115FD38.3E497%evyncke@cisco.com>
References: <20150227092546.25123.96782.idtracker@ietfa.amsl.com>
In-Reply-To: <20150227092546.25123.96782.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.6.141106
x-originating-ip: [10.55.185.73]
Content-Type: text/plain; charset="utf-8"
Content-ID: <97E4AEE802323C4DB6E09DCEA833AA90@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/LmyT9A05alnPoQ26wVtLBQP8H80>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Feb 2015 09:56:24 -0000
Please find below the links to a new version of the document which reflects the revised format for the new extension header as well as addressing comments received since -01. We also added more around RFC 5095 Comments are welcome of course :-) -éric On 27/02/15 10:25, "internet-drafts@ietf.org" <internet-drafts@ietf.org> wrote: > >A new version of I-D, draft-vyncke-6man-segment-routing-security-02.txt >has been successfully submitted by Eric Vyncke and posted to the >IETF repository. > >Name: draft-vyncke-6man-segment-routing-security >Revision: 02 >Title: IPv6 Segment Routing Security Considerations >Document date: 2015-02-25 >Group: Individual Submission >Pages: 13 >URL: >http://www.ietf.org/internet-drafts/draft-vyncke-6man-segment-routing-secu >rity-02.txt >Status: >https://datatracker.ietf.org/doc/draft-vyncke-6man-segment-routing-securit >y/ >Htmlized: >http://tools.ietf.org/html/draft-vyncke-6man-segment-routing-security-02 >Diff: >http://www.ietf.org/rfcdiff?url2=draft-vyncke-6man-segment-routing-securit >y-02 > >Abstract: > Segment Routing (SR) allows a node to steer a packet through a > controlled set of instructions, called segments, by prepending a SR > header to the packet. A segment can represent any instruction, > topological or service-based. SR allows to enforce a flow through > any path (topological, or application/service based) while > maintaining per-flow state only at the ingress node to the SR domain. > > Segment Routing can be applied to the IPv6 data plane with the > addition of a new type of Routing Extension Header. This document > analyzes the security aspects of the Segment Routing Extension Header > (SRH) and how it is used by SR capable nodes to deliver a secure > service. > > > > > > >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 >
- FW: New Version Notification for draft-vyncke-6ma… Eric Vyncke (evyncke)