IETF Logo Mail Archive

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

Bob Hinden <bob.hinden@gmail.com> Fri, 02 October 2015 23:38 UTC

Return-Path: <bob.hinden@gmail.com>
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 3A0621A046D for <ipv6@ietfa.amsl.com>; Fri, 2 Oct 2015 16:38:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 W7pN0G5n5bN1 for <ipv6@ietfa.amsl.com>; Fri, 2 Oct 2015 16:38:16 -0700 (PDT)
Received: from mail-qk0-x22d.google.com (mail-qk0-x22d.google.com [IPv6:2607:f8b0:400d:c09::22d]) (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 A1C841A0250 for <ipv6@ietf.org>; Fri, 2 Oct 2015 16:38:16 -0700 (PDT)
Received: by qkcf65 with SMTP id f65so49522852qkc.3 for <ipv6@ietf.org>; Fri, 02 Oct 2015 16:38:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=9WUePNgIuDMcP1kn4xgX/zobPUNS8192qAD9C5r07ew=; b=qotDdxntLhplogDu8v4RNjElOzkIBy57h4R9VAnJ2x4thzQf2dG4yINaAATx3p899+ kQUiQn99Bgvzvhs5pWkNR9RtfrvkHxremg+e0+y+G9Y7JZuI7eYFQe9FKNrgmTkvN129 bmtJL25WddAN6EdmxLGrj656VBhbUxVeTAeOcXPF94UAjdYDW11Fc1ZXJZZJ5U6VHMwy 2f3TC2uD5c1qVNOlaUFbBr0AKSpYeW3YmRIUiIWnbmWFsX4xsrvDLnN243GhYq5ZxNRq gPTVrfEEyratsuelSc3JbtSYSZfouSCJHbaIWsgsAbp5HNx3NCK1elTPz2ZX/f0fnNT1 CS5w==
X-Received: by 10.55.197.139 with SMTP id k11mr23246378qkl.11.1443829095821; Fri, 02 Oct 2015 16:38:15 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id s88sm5683094qks.23.2015.10.02.16.38.14 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 02 Oct 2015 16:38:15 -0700 (PDT)
Subject: Re: RFC2460bis and draft-previdi-6man-segment-routing-header-08
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_EC4FECB9-E23E-4181-B371-4D286C6ACAC1"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail 2.5.1
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <560F13AE.5010906@acm.org>
Date: Fri, 02 Oct 2015 16:38:11 -0700
Message-Id: <650138C4-2EBF-44D8-B423-F84976C7F652@gmail.com>
References: <560EDAF6.1030906@gmail.com> <773A174A-6313-4E98-AB98-09A004CA132C@gmail.com> <560F13AE.5010906@acm.org>
To: Erik Nordmark <nordmark@acm.org>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ywLbrLNWmsa62cQ23NQY5vVEjqI>
Cc: IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
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:38:18 -0000

Erik,

> On Oct 2, 2015, at 4:30 PM, Erik Nordmark <nordmark@acm.org> wrote:
> 
> 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.

Good suggestion.

Thanks,
Bob


> 
> 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
>> --------------------------------------------------------------------
>

v2.23.0 | Report a Bug | By Email