IETF Logo Mail Archive

Re: Next steps on advancing core IPv6 specifications to full Internet standard

Tom Herbert <tom@herbertland.com> Fri, 18 November 2016 08:45 UTC

Return-Path: <tom@herbertland.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 BA12F129575 for <ipv6@ietfa.amsl.com>; Fri, 18 Nov 2016 00:45:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.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 UQJDcf7brPXl for <ipv6@ietfa.amsl.com>; Fri, 18 Nov 2016 00:45:38 -0800 (PST)
Received: from mail-qk0-x22a.google.com (mail-qk0-x22a.google.com [IPv6:2607:f8b0:400d:c09::22a]) (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 CD75D12953C for <ipv6@ietf.org>; Fri, 18 Nov 2016 00:45:37 -0800 (PST)
Received: by mail-qk0-x22a.google.com with SMTP id x190so254012538qkb.0 for <ipv6@ietf.org>; Fri, 18 Nov 2016 00:45:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=zzQcFaAJMyD1S6lljcuNaxg6Jjpt1tSDQKJmCJVw4Js=; b=crllbz9PcAaX07KNFnPE0Gjmd9kXLZA+ieBrW1tvV8Y6w786OK1pdGRT0amBlG9eAO s60e6kN0U6jPOvNy294PKqiAW/qQHkWH+ykSHaizs0qcN0ssk61jMPYa6h8PD+ph+xTO Xd2W17kIn0L+NKHa+4+QiRb0AlVVuahtjS0+CceGt+62Tyv56XL2UZcc09IKMLToYEQS MWXzVIKiq8WUEZXwU/OhxEidqfAB38EfOFPfBUWO0sFRjwsnMKWOXoNqlQ/IseG1j5ce w8k8KG9CTbjr27OH+zZ7lP2sqDqqvlN0QjYWi+eSCLaTkfAqzTMT/YShKhfeKa3Xys6s i1Zg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=zzQcFaAJMyD1S6lljcuNaxg6Jjpt1tSDQKJmCJVw4Js=; b=ABo4895JjXrG0/kEYkMD4x7hSKLsbBj7QoNfdNp+xquVnvql3pgOywVEvp6JNGKqsr jkSNrE3AAKX+ama/ZtJqVWlCDWcJ+OEGcodhMLNbAqbfvLrk1JJt3ZZPkF8aKNWWFAZp /2+TWiryF8Xc7Nr7Zp4UaUoziod39uZMrpxRx1U7t1o7f8+riBO9YjhRCXkc+rBrW4Va xAopV98Ph66oLqnyIQcq/qxhLKRV6OCDHeJjLW+YvIAIue6XLkmx7o0295oKylxArGqF 1C/uTI/e6XZRlyx5JXTJlCvlIM3wVAtaen28cYWrCSKJ5A2aBQHAGJ0AMOpSpEXVDPP3 /JTA==
X-Gm-Message-State: AKaTC03NPqp7/B66zwLEcRaCcnQyrP/kyYCIcnbxTox4/czTU6S2IctHocyN7gLL8/X1FIMKiad032kBmLfIuQ==
X-Received: by 10.55.25.159 with SMTP id 31mr8598942qkz.267.1479458736937; Fri, 18 Nov 2016 00:45:36 -0800 (PST)
MIME-Version: 1.0
Received: by 10.200.58.197 with HTTP; Fri, 18 Nov 2016 00:45:36 -0800 (PST)
In-Reply-To: <CABdyVt5rhiR6TbvFw8m81R_7Hs3t4APrpdd5W-4U6En4dYq1WQ@mail.gmail.com>
References: <451D4151-B805-4A2E-8BAC-B6627C0B669C@employees.org> <CAJE_bqczRSZYWC3tDLXvxRMzqnV9nDjYjUddyRHtwfpGEXvm5w@mail.gmail.com> <CABdyVt5rhiR6TbvFw8m81R_7Hs3t4APrpdd5W-4U6En4dYq1WQ@mail.gmail.com>
From: Tom Herbert <tom@herbertland.com>
Date: Fri, 18 Nov 2016 17:45:36 +0900
Message-ID: <CALx6S35V=wAtSWp0_ksCX2emBZZADY+uiqBLPnyHST_q+vJgig@mail.gmail.com>
Subject: Re: Next steps on advancing core IPv6 specifications to full Internet standard
To: Hemant Singh <hemantietf@gmail.com>
Content-Type: multipart/alternative; boundary="001a1147f0b279b4f205418f54b7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/oVyzCYYiFnSbFVp1NvR6Ko5OBDg>
Cc: stephane.litkowski@orange.com, 6man WG <ipv6@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>, 神明達哉 <jinmei@wide.ad.jp>, 6man-chairs@ietf.org
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, 18 Nov 2016 08:45:40 -0000

On Thu, Nov 17, 2016 at 11:22 PM, Hemant Singh <hemantietf@gmail.com> wrote:

> I have cced to a few SR folks.  Why did the SR implementation in the Linux
> kernel go with add/delete EH rather than encapsulation?   Why wasn't
> encapsulation used first with SR for the Linux kernel implementation?
>
> The implementation doesn't distinguish between being a host and being a
router in this case. If the forwarding instructions are to insert a header
then that is what's done. Encapsulation is just an alternate method that
should already be supported and similarly would work for a host or router.
Basically, we are leaving it up to the user rather inserting EH in the
network is reasonable, however a warning about inserting EH based on the
proposed text will be added to the documentation.

Thanks,
Tom

Thanks,
>
> Hemant
>
>
> On Wed, Nov 16, 2016 at 2:18 PM, 神明達哉 <jinmei@wide.ad.jp> wrote:
>
>> At Tue, 15 Nov 2016 15:19:45 +0900,
>> otroan@employees.org wrote:
>>
>>
>> Assuming so, I'd like to say I still have a serious concern with this
>> text in that it's as "ambiguous" to the extent the original RFC2460
>> was ambiguous regarding whether the protocol intends (intended) to
>> allow such extension header insertion.  I'm concerned about this
>> because such ambiguity can lead to casual violation of the intent (we
>> know the intent was to not allow it) and casually dismissing the
>> stated problems and other issues that are not explicitly noted in the
>> text.  The existence of segment routing implementation for the Linux
>> kernel (a general purpose operating system) suggests it's not just an
>> imaginary concern: http://www.segment-routing.org/index.php/SR/SR-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