IETF Logo Mail Archive

Fwd: New Version Notification for draft-vyncke-6man-segment-routing-security-00.txt

"Stefano Previdi (sprevidi)" <sprevidi@cisco.com> Thu, 03 July 2014 14:56 UTC

Return-Path: <sprevidi@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 9A6E51A0162 for <ipv6@ietfa.amsl.com>; Thu, 3 Jul 2014 07:56:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level:
X-Spam-Status: No, score=-15.152 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, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, 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 08C_ZayYGHPW for <ipv6@ietfa.amsl.com>; Thu, 3 Jul 2014 07:56:07 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D59241A00F8 for <6man@ietf.org>; Thu, 3 Jul 2014 07:56:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2197; q=dns/txt; s=iport; t=1404399367; x=1405608967; h=from:to:subject:date:message-id:references:content-id: content-transfer-encoding:mime-version; bh=/uwVgJKDsF94XOweD1+7MkpHdfAOtXH56CoX+09EbMc=; b=TNm652VxyVI2Zxbne9vnitOLRtIPDKyWyxvB1+HL0+2B1OFmN7TmF2l1 cFaHBIhLL7GmhV4RmvaXNZYMMiuQAi556PdsfvretOHWP7ny0l4Lf/Ofx PjAvi4iSbPET9N8jBSE5OJQvAyf/emoT+1HY52UBQ57hdetcMiLgL3xI2 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMHAJ9utVOtJA2L/2dsb2JhbABagw1SWqswDAECAQEBBQECbAGZZoEKFnWEAwEBAQMBOj0HCwIBGQMBAh8QMhsCCAIEEwmIMQgNySEXhXCJP4MngRYFmm2BSJJCggGBQmyBRA
X-IronPort-AV: E=Sophos;i="5.01,595,1400025600"; d="scan'208";a="337525031"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by rcdn-iport-7.cisco.com with ESMTP; 03 Jul 2014 14:56:06 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s63Eu58c030290 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <6man@ietf.org>; Thu, 3 Jul 2014 14:56:06 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.27]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0123.003; Thu, 3 Jul 2014 09:56:05 -0500
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: 6MAN <6man@ietf.org>
Subject: Fwd: New Version Notification for draft-vyncke-6man-segment-routing-security-00.txt
Thread-Topic: New Version Notification for draft-vyncke-6man-segment-routing-security-00.txt
Thread-Index: AQHPlsVPZVl9C4Wq3k2v4OyZldAypg==
Date: Thu, 03 Jul 2014 14:56:04 +0000
Message-ID: <589E8AA0-B5D5-4E04-B339-7CA0DC3B85CF@cisco.com>
References: <20140703134709.19452.24677.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.61.207.174]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <81CC5A209FBD5D49B0C7402707279A1E@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/z0UdVCynKgxxILjwW28nIQRvQAk
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: Thu, 03 Jul 2014 14:56:12 -0000


Begin forwarded message:

> From: <internet-drafts@ietf.org>
> Subject: New Version Notification for draft-vyncke-6man-segment-routing-security-00.txt
> Date: July 3, 2014 3:47:09 PM GMT+02:00
> To: Eric Vyncke <evyncke@cisco.com>, Ida Leung <ida.leung@rci.rogers.com>, Brian Field <brian_field@cable.comcast.com>, Stefano Previdi <sprevidi@cisco.com>, Eric Vyncke <evyncke@cisco.com>, Stefano Previdi <sprevidi@cisco.com>, Brian Field <brian_field@cable.comcast.com>, Ida Leung <ida.leung@rci.rogers.com>
> 
> 
> A new version of I-D, draft-vyncke-6man-segment-routing-security-00.txt
> has been successfully submitted by Stefano Previdi and posted to the
> IETF repository.
> 
> Name:		draft-vyncke-6man-segment-routing-security
> Revision:	00
> Title:		IPv6 Segment Routing Header (SRH) Security Considerations
> Document date:	2014-07-03
> Group:		Individual Submission
> Pages:		11
> URL:            http://www.ietf.org/internet-drafts/draft-vyncke-6man-segment-routing-security-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-vyncke-6man-segment-routing-security/
> Htmlized:       http://tools.ietf.org/html/draft-vyncke-6man-segment-routing-security-00
> 
> 
> 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 draft
>   analyses the security aspects the Segment Routing Extension Header
>   Type 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
>

v2.23.0 | Report a Bug | By Email