Future of header insertion work in 6man

Suresh Krishnan <suresh.krishnan@gmail.com> Sat, 20 May 2017 03:50 UTC

Return-Path: <suresh.krishnan@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 4382B129451 for <ipv6@ietfa.amsl.com>; Fri, 19 May 2017 20:50:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.801
X-Spam-Level:
X-Spam-Status: No, score=-0.801 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 XvyJqkjvAnCl for <ipv6@ietfa.amsl.com>; Fri, 19 May 2017 20:50:05 -0700 (PDT)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::22c]) (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 A917B1293F4 for <ipv6@ietf.org>; Fri, 19 May 2017 20:50:05 -0700 (PDT)
Received: by mail-yw0-x22c.google.com with SMTP id b68so42236631ywe.3 for <ipv6@ietf.org>; Fri, 19 May 2017 20:50:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:message-id:date :cc:to; bh=wXp7830XuAyYYfANtZBQ9/7HAmP+WjU5td/GRmeixPo=; b=u8tsPhXZ482yvXxIHNGwSIqVESUGQg5Js3R+VKf1ccollajd8J7dn2jSYu1flpVUlh 18uHo6jVvwo52aWzAKuLfrWlLEKJkU6mZEwEh5sh7pIoH03Y92MwVwzE+sgGy59rdbF/ Kq4ExHl1FQSlB08X+wRH+og4Iu+4cn7mxfos+N/WVcvNex98t07kWvB2oEnfmfTYnyS+ MBqoB/WYDE2mflV9HCN+Wg7Y+zuFhRDzbkCS7LTwCeuM9L8PyU3mi/+qf0eIF1L6k9ZS LfXxDbiWitlVt7u9mWgCXX7sCCOzjaNKEzEZfpsXCe4Fh6B2FTHDvDduHT8hM2j2/3t6 259Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:cc:to; bh=wXp7830XuAyYYfANtZBQ9/7HAmP+WjU5td/GRmeixPo=; b=A8KhbrmpCnRUZyI8WqEL4gKfb7ndLmy8+YsTx4UkoHCQRMMowOrxIAZWp5dlmNGBTm Jmj6H9lzUZGF+ExME8vzhZl3GifTzuTSCSAPybYXDt+s403hLYUpIqUiR7eskJlLB+d8 Wek1+kOqAhZoxBpz4aTpr7FdnIi93Thv8FzndR807dN2NWm00YTCEMBk+KhPI1bli7lK GWrKrD7iKHLgdhOF54Ub2NhFXPDlWnRZuxh20E7nnoNgx8P4VNHaZHjXE/FngpvTjD8/ locnfflNJzjqbo+GfafSBGYiOGPL7yXPUasJ8VsWNohf2mHlu2NPSzlZ/NaHvGmlTiav wuSQ==
X-Gm-Message-State: AODbwcCjQcX9vHpqMWlYaTlVLnywVXSizKjrHqsprVGE78Xt9AzxnvLd R3vAHBsNAedkAg==
X-Received: by 10.129.84.67 with SMTP id i64mr10932508ywb.293.1495252204934; Fri, 19 May 2017 20:50:04 -0700 (PDT)
Received: from [10.0.0.2] (45-19-110-76.lightspeed.tukrga.sbcglobal.net. [45.19.110.76]) by smtp.gmail.com with ESMTPSA id q65sm4550938ywg.5.2017.05.19.20.50.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 19 May 2017 20:50:04 -0700 (PDT)
From: Suresh Krishnan <suresh.krishnan@gmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Future of header insertion work in 6man
Message-Id: <0819567D-4F46-4320-9F7D-53BF01A86ABF@gmail.com>
Date: Fri, 19 May 2017 23:50:02 -0400
Cc: Bob Hinden <bob.hinden@gmail.com>, Ole Trøan <otroan@employees.org>
To: IPv6 List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/4MevopH9_iQglUizhoT5Rl-TjRc>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 20 May 2017 03:50:07 -0000

Hi all,
  Now that 2460bis has been approved for publication, I would like to take this chance to emphasize something that has been said in multiple mails before by different WG participants, but it is worth mentioning in a separate mail. I have heard from several persons being concerned about the possibility of new text in 2460bis being blindly used to block header insertion work in the future. I just want to confirm that header insertion work can be considered in the future, and that it should be judged on its own merits and not be blocked solely based on the header insertion related text in 2460bis.

Thanks
Suresh