Re: RFC2460bis and draft-previdi-6man-segment-routing-header-08
Erik Nordmark <nordmark@acm.org> Fri, 02 October 2015 23:31 UTC
Return-Path: <nordmark@acm.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 10D5A1A0406 for <ipv6@ietfa.amsl.com>; Fri, 2 Oct 2015 16:31:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level:
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no
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 OW7GTW4iuMoY for <ipv6@ietfa.amsl.com>; Fri, 2 Oct 2015 16:31:01 -0700 (PDT)
Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (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 B580E1A036C for <ipv6@ietf.org>; Fri, 2 Oct 2015 16:31:01 -0700 (PDT)
Received: from [172.22.227.238] ([162.210.130.3]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id t92NUuIC001350 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 2 Oct 2015 16:30:56 -0700
Subject: Re: RFC2460bis and draft-previdi-6man-segment-routing-header-08
To: Bob Hinden <bob.hinden@gmail.com>, Brian Carpenter <brian.e.carpenter@gmail.com>
References: <560EDAF6.1030906@gmail.com> <773A174A-6313-4E98-AB98-09A004CA132C@gmail.com>
From: Erik Nordmark <nordmark@acm.org>
Message-ID: <560F13AE.5010906@acm.org>
Date: Fri, 02 Oct 2015 16:30:54 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <773A174A-6313-4E98-AB98-09A004CA132C@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Sonic-CAuth: UmFuZG9tSVZEhIOqSDcuEWugbK6ibOvuSyavXdBMGTCjGOj37jRzX7klqYgfztOFag9tZlCHcG38GAL0NoqWDccubYp+Ssad
X-Sonic-ID: C;IJh1oV1p5RGO370U9jFv0A== M;rE+RoV1p5RGO370U9jFv0A==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/TfoaA8fKQlhmUwjOZN_N5rm6u1c>
Cc: IPv6 List <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: Fri, 02 Oct 2015 23:31:03 -0000
On 10/2/15 2:49 PM, Bob Hinden wrote: > > 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. Regards, Erik > > Bob > > >> Brian >> >> -------------------------------------------------------------------- >> IETF IPv6 working group mailing list >> ipv6@ietf.org >> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 >> -------------------------------------------------------------------- > > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > --------------------------------------------------------------------
- RFC2460bis and draft-previdi-6man-segment-routing… Brian E Carpenter
- Re: RFC2460bis and draft-previdi-6man-segment-rou… Bob Hinden
- Re: RFC2460bis and draft-previdi-6man-segment-rou… joel jaeggli
- Re: RFC2460bis and draft-previdi-6man-segment-rou… Erik Nordmark
- Re: RFC2460bis and draft-previdi-6man-segment-rou… Bob Hinden
- Re: RFC2460bis and draft-previdi-6man-segment-rou… otroan
- Re: RFC2460bis and draft-previdi-6man-segment-rou… otroan
- Re: RFC2460bis and draft-previdi-6man-segment-rou… C. M. Heard