Re: 6MAN WG Last Call: draft-shore-icmp-aup

Ray Hunter <v6ops@globis.net> Sat, 14 December 2013 12:18 UTC

Return-Path: <v6ops@globis.net>
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 2239C1AE11E for <ipv6@ietfa.amsl.com>; Sat, 14 Dec 2013 04:18:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level:
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779] 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 vUfSJvF9uhki for <ipv6@ietfa.amsl.com>; Sat, 14 Dec 2013 04:18:49 -0800 (PST)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0D85F1AE11A for <ipv6@ietf.org>; Sat, 14 Dec 2013 04:18:49 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 48D3F870FC0; Sat, 14 Dec 2013 13:18:37 +0100 (CET)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ECF52OHZaSiJ; Sat, 14 Dec 2013 13:18:37 +0100 (CET)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 022DC87006F; Sat, 14 Dec 2013 13:18:36 +0100 (CET)
Message-ID: <52AC4C9B.40007@globis.net>
Date: Sat, 14 Dec 2013 13:18:35 +0100
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Ole Troan <otroan@employees.org>
Subject: Re: 6MAN WG Last Call: draft-shore-icmp-aup
References: <4E36B3A8-5B6B-4EE8-BAC7-4378F81BADC0@employees.org>
In-Reply-To: <4E36B3A8-5B6B-4EE8-BAC7-4378F81BADC0@employees.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, 6man WG <ipv6@ietf.org>, draft-shore-icmp-aup@tools.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: <http://www.ietf.org/mail-archive/web/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, 14 Dec 2013 12:18:56 -0000
X-List-Received-Date: Sat, 14 Dec 2013 12:18:56 -0000

Ole Troan wrote:
> All,
>
> Our AD has requested that the 6MAN working group review this document. This is part of our chartered work
> to review documents produced outside of 6MAN, that may extend or change the IPv6 protocol.
>
> This message starts a one week 6MAN Working Group Last Call for a review of:
>
> 	Title           : An Acceptable Use Policy for New ICMP Types and Codes
> 	Author(s)   : M. Shore, C. Pignataro
> 	Filename   : draft-shore-icmp-aup-07
> 	Pages        : 9
> 	Date          : 2013-12-05
>
>
>     http://tools.ietf.org/html/draft-shore-icmp-aup-07
>
> as a BCP.  Substantive comments and statements of support for advancing this document should be directed to the mailing list.
> Editorial suggestions can be sent to the authors.  This last call will end on December 20, 2013.
>
> As with our regular working group last calls, the chairs would like to solicit one or two people in the working group
> to do a detailed review of the document.
>
> Regards,
>
> Bob Hinden & Ole Trøan

I read the draft. It is pretty easy to read and straight forward.

I don't understand the underlying concerns. The motivation is not
included in the draft (I guess I'd have to go to the WG mailing list to
get that information)

Why should ICMP be limited?

Does ICMPv6 really need to be so limited if it is only used for on-link
communication using link-local addresses?

-- 
Regards,
RayH