IETF Logo Mail Archive

Re: Question on draft-ietf-6man-segment-routing-header-04 (not needed PHP-Style behavior)

"Stefano Previdi (sprevidi)" <sprevidi@cisco.com> Wed, 01 February 2017 20:12 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 AC6CD1299A3 for <ipv6@ietfa.amsl.com>; Wed, 1 Feb 2017 12:12:48 -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 bAsUIBer2MFv for <ipv6@ietfa.amsl.com>; Wed, 1 Feb 2017 12:12:46 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8848812956E for <ipv6@ietf.org>; Wed, 1 Feb 2017 12:12:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1602; q=dns/txt; s=iport; t=1485979966; x=1487189566; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=aqw9kJeWm54UlyPJveZZso4CliG2xaNKxI+3ExT/V/s=; b=NLq8rDMc0elGc2q1nCKv9ogHqEsOnVGddNujInNtKavmlkYHQyJiMoPT mNmFz67QuGqc84Eilyl1Mh3u9zBH9MwDkHD5DpqsH5Lo0z3ziXtUxsjNw SLoX1otczaV+hiv3omQSJQ6hE24gU/TwrKgAtLyl5So8I1NroFz6YNQd9 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A3AQB8QJJY/5tdJa1cGQEBAQEBAQEBAQEBBwEBAQEBgygrYYEJB4NQigmSB5U1gg0fC4V4AhqCJT8YAQIBAQEBAQEBYiiEaQEBAQMBAQEhEToLBQsCAQgYAgImAgICJQsVEAIEDgWJaggOrG2CJYsrAQEBAQEBAQEBAQEBAQEBAQEBAQEBGAWBC4VAggWCaoRNgwYugjEBBIkFklcBigKIAJB9kwABHzg6gREVOxEBhGiBSHWHXYEMAQEB
X-IronPort-AV: E=Sophos;i="5.33,321,1477958400"; d="scan'208";a="380122561"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Feb 2017 20:12:45 +0000
Received: from XCH-RTP-010.cisco.com (xch-rtp-010.cisco.com [64.101.220.150]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v11KCjjJ028651 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 1 Feb 2017 20:12:45 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-010.cisco.com (64.101.220.150) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 1 Feb 2017 15:12:44 -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:12:44 -0500
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: Shay Zadok <shay.zadok@broadcom.com>
Subject: Re: Question on draft-ietf-6man-segment-routing-header-04 (not needed PHP-Style behavior)
Thread-Topic: Question on draft-ietf-6man-segment-routing-header-04 (not needed PHP-Style behavior)
Thread-Index: AQHSfMeMh1P1g8McqUeMKCRj0FQL7A==
Date: Wed, 01 Feb 2017 20:12:44 +0000
Message-ID: <4B338C4A-FCBB-4F80-8DDF-F645C6B38FD3@cisco.com>
References: <CA+X6GCQNLUfxPPOHC_XBU05-tsdb39CJwcigWiQ28pEL5t=FBw@mail.gmail.com>
In-Reply-To: <CA+X6GCQNLUfxPPOHC_XBU05-tsdb39CJwcigWiQ28pEL5t=FBw@mail.gmail.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="utf-8"
Content-ID: <FC438926ED10694F8A974C86FAF9760E@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/KH1CFEDdpso7c58E-dSEygPWl6A>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
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:12:48 -0000

Hi,


> On Feb 1, 2017, at 12:34 PM, Shay Zadok <shay.zadok@broadcom.com> wrote:
> 
> Hi,
> 
> As 'Clean-up flag' is omitted from segment-routing-header-04, does this means that no need to support PHP-Style behavior in the segment before the last one?


the clean-up flag was used when an SRH was “inserted” underneath the IPv6 header by a transit node. In order to be able to deliver the packet without the SRH you needed an indication for the penultimate segment in order to remove the SRH prior to send the packet to the destination (last segment).

The behavior described in draft-04 is different and consists of the addition of both an outer IPv6 header and an SRH (i.e.: encapsulation instead of insertion). In that context, the PHP behavior (cleanup bit) is no longer needed.

s.


> That is, last segment *always* get the SRH header.
> 
> Thanks,
> Shay
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email