Re: RFC2460bis and draft-previdi-6man-segment-routing-header-08

otroan@employees.org Mon, 05 October 2015 10:06 UTC

Return-Path: <otroan@employees.org>
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 189111B4F17 for <ipv6@ietfa.amsl.com>; Mon, 5 Oct 2015 03:06:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level:
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 RmhhQ62Ywszz for <ipv6@ietfa.amsl.com>; Mon, 5 Oct 2015 03:06:52 -0700 (PDT)
Received: from cowbell.employees.org (cowbell.employees.org [65.50.211.142]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 372881B4F26 for <ipv6@ietf.org>; Mon, 5 Oct 2015 03:06:52 -0700 (PDT)
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 8A14DD788E; Mon, 5 Oct 2015 03:06:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=fh3YkkBC1VkTJBiWDk/NmZbDrk4=; b= Gd0D9Ay7vaGo0kvuNukIItce0YXQ/zVW60RTZxiZxCarB1j/B4ewi+7B1I9phvyS 3FI5wfmL8keuYHO9zsS0U0FbEsFQaulL59EdYxUOkuFebDN7q0FF02I1hDvwZdZ+ Z6vz1RgCrYugK+Fd9xcAHVgXJ2XpbRMTXqSfOQvpGTs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=I/ALnQyeMvyFbnp9k0Vjk4G7d1 pYsR5wyGHBcfubFpP02gmhbuj/xJDUPCePputacaKgBmX80M42w5rv2LpkqZBA0J IErZahqy2ehUlBNYsmLBaBuZ2xNgqeKNQLPk+2Ej0RYxu9iUYa9bd/BsWjILN+eK NNAuxRhXaC3+HaPLk=
Received: from h.hanazo.no (unknown [173.38.220.57]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 502CAD7884; Mon, 5 Oct 2015 03:06:51 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 724DD4EA97C; Mon, 5 Oct 2015 12:06:48 +0200 (CEST)
Subject: Re: RFC2460bis and draft-previdi-6man-segment-routing-header-08
Mime-Version: 1.0 (Mac OS X Mail 9.0 \(3094\))
Content-Type: multipart/signed; boundary="Apple-Mail=_0555968E-59CF-46CD-93A8-0A44F6D01CA7"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <650138C4-2EBF-44D8-B423-F84976C7F652@gmail.com>
Date: Mon, 05 Oct 2015 12:06:47 +0200
Message-Id: <5BB4ECCA-6D7F-4F26-8855-822FD874742A@employees.org>
References: <560EDAF6.1030906@gmail.com> <773A174A-6313-4E98-AB98-09A004CA132C@gmail.com> <560F13AE.5010906@acm.org> <650138C4-2EBF-44D8-B423-F84976C7F652@gmail.com>
To: Bob Hinden <bob.hinden@gmail.com>
X-Mailer: Apple Mail (2.3094)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/l6BSMB3YerGuplKOkkXnEWA5JmI>
Cc: Erik Nordmark <nordmark@acm.org>, 6man WG <ipv6@ietf.org>
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: <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: Mon, 05 Oct 2015 10:06:54 -0000

>>> How about something like this:
>>> 
>>>    Extension headers are only allowed to be added to packets at
>>>    the source node.
>>> 
>>> I think that was always the intent and this would be a clarification to the specification.
>> Bob,
>> "source node" might not be sufficiently specific in the case of tunneling, and "added" can be read as their insertion is somehow independent and we want it to be coupled with the insertion of an IPv6 header.
>> 
>> I think what we want to say is that extension headers can only be placed in packets by the same node that is placing the base IPv6 header in the packet. Hence they can not be added unless a preceeding IPv6 header is also added.
> 
> Good suggestion.

what about:

   1.  If the SRH specifies the complete path from source to
        destination, the router places the SRH directly in the datagram
        itself.

   2.  If the SRH only specifies a subset of the path from source to
       destination, the router uses IPv6-in-IPv6 tunneling [RFC2473] and
       places the SRH in the outer IPv6 header.  Use of tunneling
       ensures that the datagram is delivered unmodified and that ICMP
       errors return to the source of the SRH rather than the source of
       the original datagram.


which is verbatim from RFC6554.

cheers,
Ole