Re: I-D Action: draft-ietf-6man-segment-routing-header-05.txt

"Stefano Previdi (sprevidi)" <sprevidi@cisco.com> Wed, 01 February 2017 20:17 UTC

Return-Path: <sprevidi@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBD7B129EBE for <ipv6@ietfa.amsl.com>; Wed, 1 Feb 2017 12:17:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.72
X-Spam-Level:
X-Spam-Status: No, score=-17.72 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=-3.199, 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 bcfFLC-VzyDI for <ipv6@ietfa.amsl.com>; Wed, 1 Feb 2017 12:17:06 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06E78129E9E for <ipv6@ietf.org>; Wed, 1 Feb 2017 12:17:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2576; q=dns/txt; s=iport; t=1485980226; x=1487189826; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=n3M+YWn4+dI/eKhL31Oml391B/C//1xut6ZZam+xyYU=; b=UeZUKziFkFOvWTMHxaoqhioH4TpbRY08nc81mAxLNo6mCsYyZKx1IIES K2ztexlOs+KrbhOshPI4l+lu94vWKTZKJ4NRT/1XTsA3ht5PX5uRmZtCz EfQ1WmMigmAtgVx736hUNOh6jPOkFVkS8GnJS8VQS5uAO/DiZeBeQMNHj w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0B+AQA0QZJY/4wNJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1NhgQkHjVmRaB+VNYINHw2FdgKCPz8YAQIBAQEBAQEBYiiEaQE?= =?us-ascii?q?BAQMBAQE4NBALAgEIGB4QJwslAgQTiWoIDq8UiysBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEdhkuCBQiCYoMQgT2DNIIxBYkFklcBhmaLHIF5U4RCiW+TAAEfOIFLFRg?= =?us-ascii?q?jEQGGMHWHXYEMAQEB?=
X-IronPort-AV: E=Sophos;i="5.33,321,1477958400"; d="scan'208";a="201266973"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 01 Feb 2017 20:17:05 +0000
Received: from XCH-RTP-009.cisco.com (xch-rtp-009.cisco.com [64.101.220.149]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v11KH4aN028974 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <ipv6@ietf.org>; Wed, 1 Feb 2017 20:17:05 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-009.cisco.com (64.101.220.149) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 1 Feb 2017 15:17:04 -0500
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; Wed, 1 Feb 2017 15:17:04 -0500
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: IPv6 List <ipv6@ietf.org>
Subject: Re: I-D Action: draft-ietf-6man-segment-routing-header-05.txt
Thread-Topic: I-D Action: draft-ietf-6man-segment-routing-header-05.txt
Thread-Index: AQHSfMgngwYyXShSLU2LF/b6cERqRA==
Date: Wed, 1 Feb 2017 20:17:04 +0000
Message-ID: <1A92A76A-4720-40BD-9BE7-4BF14C16D74A@cisco.com>
References: <148598009518.19292.2770227409401508798.idtracker@ietfa.amsl.com>
In-Reply-To: <148598009518.19292.2770227409401508798.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.225.205]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <31A2F39BC790104A97DF8CF4E319B1A0@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/TVgWgn06BJk5zWvTGLUzSZ5G-d4>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 01 Feb 2017 20:17:12 -0000

Minor changes:
. made the flag field to 8 bits 
. clarified the use of the flags in the HMAC computation

Thanks.
s.


> On Feb 1, 2017, at 9:14 PM, internet-drafts@ietf.org wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the IPv6 Maintenance of the IETF.
> 
>        Title           : IPv6 Segment Routing Header (SRH)
>        Authors         : Stefano Previdi
>                          Clarence Filsfils
>                          Brian Field
>                          Ida Leung
>                          Jen Linkova
>                          Ebben Aries
>                          Tomoya Kosugi
>                          Eric Vyncke
>                          David Lebrun
> 	Filename        : draft-ietf-6man-segment-routing-header-05.txt
> 	Pages           : 28
> 	Date            : 2017-02-01
> 
> Abstract:
>   Segment Routing (SR) allows a node to steer a packet through a
>   controlled set of instructions, called segments, by prepending an 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
>   describes the Segment Routing Extension Header Type and how it is
>   used by SR capable nodes.
> 
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6man-segment-routing-header/
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-05
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-segment-routing-header-05
> 
> 
> 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/
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------