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

Shay Zadok <shay.zadok@broadcom.com> Wed, 01 February 2017 11:35 UTC

Return-Path: <shay.zadok@broadcom.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 70064129D18 for <ipv6@ietfa.amsl.com>; Wed, 1 Feb 2017 03:35:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=broadcom.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 vQLJM7FhLrlL for <ipv6@ietfa.amsl.com>; Wed, 1 Feb 2017 03:35:00 -0800 (PST)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0BD9126B6D for <ipv6@ietf.org>; Wed, 1 Feb 2017 03:34:59 -0800 (PST)
Received: by mail-wm0-x22f.google.com with SMTP id b65so34703196wmf.0 for <ipv6@ietf.org>; Wed, 01 Feb 2017 03:34:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=0Z5EbobMQFERs0aO4DjBlDnl1f/xULBJT8cMJ0nmWVU=; b=YvO8IYFhj38laGBFSQDTfZ+nAOJRChc7BTsSTdvJ17DD30VA0pDUF5cB2T28tn6/0r Q2XBCRvRR1RlZKurpwtNlTBl2JB2KIf7XyFDiINtzdkqImWGVFt8pODyn75SLyBnoYCE PpHLxWoyVtYu+heSnbxXAP0TbHYY3XpZ5SLic=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=0Z5EbobMQFERs0aO4DjBlDnl1f/xULBJT8cMJ0nmWVU=; b=smCvlgvezToOgoTUS8yODvFHnluXSzABSTUmKHY9jAwtX5dzV6cEwfutKj/txCtgzP 4KEHXT06Ze1KrikIa0esys2uHr706Fudvt8u2w4OuFeb4u2YaGahmwviK8fG2t8rRh3A oGHrA349izpZUULhl1RcWdjnIA6kxhMurvl0NPJCvNFLXG6gpynJVRcGfMaG+TIGpCV7 ONvWNrrvZaXUxAd044DZNgyp6ZgkmE+/iAinyGMD79EVYDY5UFFelBYC9JVjJLQ0WTAL D/dZDH+9JfSgH2MHOZFv28085fgRyLlOD2afqhiFY3kxylVhGh0CsKXYR3C8GX3Lm98L bxog==
X-Gm-Message-State: AIkVDXJ2bAlWmUEjFlyr0w9xOxaNflZ65xOnqbCO6wq6hIW5Rv6z99J5bBVoD90Id1wDsJAYKqwJCjGVS8CnnjEq
X-Received: by 10.28.188.9 with SMTP id m9mr2406692wmf.79.1485948897937; Wed, 01 Feb 2017 03:34:57 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.193.6 with HTTP; Wed, 1 Feb 2017 03:34:57 -0800 (PST)
From: Shay Zadok <shay.zadok@broadcom.com>
Date: Wed, 1 Feb 2017 13:34:57 +0200
Message-ID: <CA+X6GCQNLUfxPPOHC_XBU05-tsdb39CJwcigWiQ28pEL5t=FBw@mail.gmail.com>
Subject: Question on draft-ietf-6man-segment-routing-header-04 (not needed PHP-Style behavior)
To: ipv6@ietf.org
Content-Type: multipart/alternative; boundary=001a114b24d83802ae05477670be
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/hKhXMyZO4PqBCvnifpZPtKrZuqI>
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 11:35:01 -0000

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?
That is, last segment *always* get the SRH header.

Thanks,
Shay