SRH insertion vs encapsulation (Re: Next steps on Extension Header Insertion)

神明達哉 <jinmei@wide.ad.jp> Fri, 04 November 2016 16:03 UTC

Return-Path: <jinmei.tatuya@gmail.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 71BB3129521 for <ipv6@ietfa.amsl.com>; Fri, 4 Nov 2016 09:03:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level:
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=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 (2048-bit key) header.d=gmail.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 7LCdKBso48ok for <ipv6@ietfa.amsl.com>; Fri, 4 Nov 2016 09:03:40 -0700 (PDT)
Received: from mail-qt0-x234.google.com (mail-qt0-x234.google.com [IPv6:2607:f8b0:400d:c0d::234]) (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 C6EEE129498 for <ipv6@ietf.org>; Fri, 4 Nov 2016 09:03:39 -0700 (PDT)
Received: by mail-qt0-x234.google.com with SMTP id p16so50805969qta.0 for <ipv6@ietf.org>; Fri, 04 Nov 2016 09:03:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to:cc :content-transfer-encoding; bh=G7fZcdJVximQj7ZQAK5uN4CNu1jy85dMUuUXFTWxcng=; b=JzpjtfUb17SZMhK130UQsp6n1S7I2p1MML8v6/oN4WEq2ANU1VLR/Oxrde/Nm/Gj0k ukPyhViDe5V/F2vnIPAPgGqOmW2k3v8tXuxqUA8QQ6TpMbdGvo969vpEMTFIkIVp/tnD jQlWud9VJhJXtHpDywUdJO8lnPek513vhQs8hz12t4A/jgnqwn2msz+QMDSZyow2HsNZ EOhcyCpEeZKmr4Rkmdy4Zv7jYnFFng/HKS0sv9l/cu+yyLpOwiD5GRT+tacsgYU1es95 j0vBGgrUfx5ox1s+Hpbpqe0uXIgJG0PtSDpHPfxizHEp2wOStaj2YbpmzcaiWlf4NHDk 27uw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to:cc:content-transfer-encoding; bh=G7fZcdJVximQj7ZQAK5uN4CNu1jy85dMUuUXFTWxcng=; b=KeLxkDj9ayFoFaFWFjyI4596uIx+6KvBX5REksSgXT5pDRzCnUDSppXqNWp66SA2jf h5KIsgylD664HWLzyG/v9F8DnBI/UX5FRpeuGUXRlezrSPj6KptJvK/VxgeiiaW5+hyS d9nFZPqiBjVc608yFq6Khb+70OQjIxsymCWguhZaHOhh2l+LLgb0Arig5FW45ZLEbQny /bCNRj+/o1+j2OpbISPjJqBcA3UXle6ho1g5QHRwIuScRnF3CBoUwE4KajdzUwvwMfIM KFTVAbh0XHKBrARV170SD/FIArMsWN0uR+FOaaAnEhEsvE7bdnd9jMvKe0OSMvDZ9wF9 eJCg==
X-Gm-Message-State: ABUngvf8q6FVdxhfzQozXOm1TJab8D78FdNSD3h8BISmCEWPsCppT6f+fe79mWi1W6EPvl5Dxn6/D8obvGVPKA==
X-Received: by 10.200.40.211 with SMTP id j19mr14726842qtj.72.1478275418910; Fri, 04 Nov 2016 09:03:38 -0700 (PDT)
MIME-Version: 1.0
Sender: jinmei.tatuya@gmail.com
Received: by 10.237.54.134 with HTTP; Fri, 4 Nov 2016 09:03:38 -0700 (PDT)
From: 神明達哉 <jinmei@wide.ad.jp>
Date: Fri, 04 Nov 2016 09:03:38 -0700
X-Google-Sender-Auth: aPaA_GB73yq8y_GsjYZn4_1yeJ8
Message-ID: <CAJE_bqebnwwDj_00=N-ZNffE++SaEMwA6vT+i-nb0C_vmZHCRA@mail.gmail.com>
Subject: SRH insertion vs encapsulation (Re: Next steps on Extension Header Insertion)
To: Tim Chown <Tim.Chown@jisc.ac.uk>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/vpStd1GQBYjuP4fIoLQJjdVIV4w>
Cc: Fernando Gont <fgont@si6networks.com>, 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
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: Fri, 04 Nov 2016 16:03:41 -0000

At Fri, 4 Nov 2016 11:16:34 +0000,
Tim Chown <Tim.Chown@jisc.ac.uk> wrote:

>> Huh? The segment routing header is far from imaginary.
>
> But what do you deduce is really being specified in the SRH drafts?
>
> In draft-ietf-6man-segment-routing-header-02 it says in section 2.2:
[...]
> which implies the SRH uses encapsulation, and doesn’t insert an EH
> in the existing header chain.

My understanding is that actual implementations don't follow what's
written in the draft and do insert an SRH:
https://www.ietf.org/mail-archive/web/ipv6/current/msg24236.html

(And my understanding is that the desire of some people to make the
"actual" behavior explicitly standard-compliant is one major
background motivation of why we are having this thread.)

--
JINMEI, Tatuya