IETF Logo Mail Archive

Re: New Version Notification for draft-voyer-6man-extension-header-insertion-08.txt

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 27 November 2019 02:53 UTC

Return-Path: <brian.e.carpenter@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 ABB47120125 for <ipv6@ietfa.amsl.com>; Tue, 26 Nov 2019 18:53:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_HELO_NONE=0.001, 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 2c9UbuiYzi5y for <ipv6@ietfa.amsl.com>; Tue, 26 Nov 2019 18:53:37 -0800 (PST)
Received: from mail-pj1-x102f.google.com (mail-pj1-x102f.google.com [IPv6:2607:f8b0:4864:20::102f]) (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 D86EC1200F7 for <6man@ietf.org>; Tue, 26 Nov 2019 18:53:37 -0800 (PST)
Received: by mail-pj1-x102f.google.com with SMTP id y21so9228481pjn.9 for <6man@ietf.org>; Tue, 26 Nov 2019 18:53:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=kqSZRHMIWH+gHIWvNXgXTO4NrE7c2qQeiDD9qWaM2/8=; b=PA1MkCHEqBUOHbuD2Dxd1qRKwzVX+swkDfXvMLqA6s6x661BhUFrRAy9E7REncaDDh c+zyd2eRhxCNht7BcqpAZpY6x7kIIVpsIWyphXUYufNhK6aKX7kXCv96osIe7CzgNb/W 33gopsgr9AdZeqkYkzcwhJQg4LBlhTE+4ZH/B1mRDCM0AoEMvPBfYMnmCIgy4SmGed30 63fuodJWwg2SqNRa4r1X5i29ULwf5mz6JoIylZ76wv9Ne/1AffUVJ4qH41x3tPGbAQr6 vCy+iZgpRaa6SnwPD2lvGSRIqIxSpUsyS16RGcceS0Wz4KCApHAECQwuUg/cNJjsY4wN YWCQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=kqSZRHMIWH+gHIWvNXgXTO4NrE7c2qQeiDD9qWaM2/8=; b=cDJ0xBsrNr4Jip3crDTbiloVsxZBaxs6QjIj5PuKOeuHLkKYRT5/OjFGW6Zrb/tN5/ eBPTDb9q6EHSkOdYiOwqf1g+wcZbsMeIOu+8ao+ckjtGmy1oIB8eha6PNOnLgq2TKYND fPKqEq8QuMRSRJxk9lgkDktG8uSflhElqx4l8ZuIAU5dkCikGD0wREkLE0YyE79d8HnA Zel5q0bsQAzJqQKRqhIuc0uIZQiAkdWjSxnlt5BmSLCr7dvjlZgwoSHX6W5e2RvseQeo BaJ/LOY7ErI9Es/XEa9Pc5Bw3x1p8qf84Q7Sqj+Eu9oiPgZYCfcF4vRsZeIRt5LucMIH JugA==
X-Gm-Message-State: APjAAAWGkjPqKWiuwqsAUGpATN409XRwugb3CNzEk/Vryls9r2AQkDKu kkUuoUIroxyqkkhGZ1+z0I4UQfUf
X-Google-Smtp-Source: APXvYqxIuALzQeBE7Q8RD++ft3A/qjdNzf0F2Jy20vORxTX9ujiVzolvSHT8NFwNiwvkDNxJ0p4ZzQ==
X-Received: by 2002:a17:90a:fb8f:: with SMTP id cp15mr2915413pjb.3.1574823216850; Tue, 26 Nov 2019 18:53:36 -0800 (PST)
Received: from [192.168.178.30] (8.166.69.111.dynamic.snap.net.nz. [111.69.166.8]) by smtp.gmail.com with ESMTPSA id h4sm4273297pjs.24.2019.11.26.18.53.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 26 Nov 2019 18:53:36 -0800 (PST)
Subject: Re: New Version Notification for draft-voyer-6man-extension-header-insertion-08.txt
To: Tom Herbert <tom@herbertland.com>
Cc: Gyan Mishra <hayabusagsm@gmail.com>, 6man <6man@ietf.org>
References: <157422734071.5406.14331301768750185617.idtracker@ietfa.amsl.com> <851F7007-3DD5-42F3-8884-8842DA07EE53@cisco.com> <1cfd682f-d6bc-a697-38a7-933aa0485b8a@si6networks.com> <D4436EF5-2B97-44A4-915D-EF7611590B51@steffann.nl> <ccf6cbe6-c837-64e3-b25e-d3fa8e3b7bcb@si6networks.com> <E68CE93F-4C3E-44FB-B4B5-7C6FC6799E47@gmail.com> <554baf9b-2a7f-8098-8203-e7d3277b549b@gmail.com> <CALx6S36L5AWEaXmccpKoENxOEv-XRCmTsq1bCqi06J_YgJGZdg@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <ecb3c877-c347-fd3a-86de-8f05fe8b7459@gmail.com>
Date: Wed, 27 Nov 2019 15:53:34 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CALx6S36L5AWEaXmccpKoENxOEv-XRCmTsq1bCqi06J_YgJGZdg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/GHl8kVgXbkm4LOcN8VJCnN2JHW0>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 27 Nov 2019 02:53:43 -0000

Hi Tom,
On 27-Nov-19 15:01, Tom Herbert wrote:
> On Tue, Nov 26, 2019 at 5:19 PM Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>>
>> On 27-Nov-19 14:00, Gyan Mishra wrote:
>> ....
>>>
>>> I am in agreement with individual submission.
>>
>> Nobody has suggested an "individual submission" RFC, which means direct submission to the IESG for the IETF stream, sponsored by an AD.
>>
>> The alternatives that have been suggested are
>> 1) WG Informational submission to the IETF stream.
>> 2) Independent Submission (https://www.rfc-editor.org/about/independent/). Also see RFC 4846 and RFC 5744 if you are not familiar with the Independent Submission process.
>>
>> Personally, I'm in favour of documenting reality, as this draft does, and as long as it's Informational I really don't care which RFC Stream is used.
> 
> Brian,
> 
> To me, this "reality" would be akin to acknowledging a serious bug but
> simply marking it "will not fix" instead of actually fixing it. Both
> the detrimental consequences of EH insertion and conformant
> alternatives to it have been articulated several times on this list,
> but we've seen little effort from the extension header insertion
> proponents to take those into account or to work with WG to resolve
> the issues.

I don't think that's fair. The current version of the draft is utterly
different from the original, and the tone of the discussion at IETF 106
was constructive (http://ietf106.conf.meetecho.com/index.php/Recordings#6MAN_II).

The proposal by the WG chairs seems very balanced to me. Work on documenting
why header insertion that escapes a limited domain is harmful (Mark's draft)
and work on documenting existing practice in real products and real
networks. We often document existing practice, on the grounds that it's
better than ignoring it. That's what draft-voyer--08 does.

   Brian

v2.23.0 | Report a Bug | By Email