Re: [v6ops] draft-taylor-v6ops-fragdrop WGLC

"Fred Baker (fred)" <fred@cisco.com> Mon, 19 August 2013 19:13 UTC

Return-Path: <fred@cisco.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCD9411E82E0 for <v6ops@ietfa.amsl.com>; Mon, 19 Aug 2013 12:13:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.187
X-Spam-Level:
X-Spam-Status: No, score=-110.187 tagged_above=-999 required=5 tests=[AWL=-0.188, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ssjc5zCWpxsi for <v6ops@ietfa.amsl.com>; Mon, 19 Aug 2013 12:13:46 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id E708911E82DE for <v6ops@ietf.org>; Mon, 19 Aug 2013 12:13:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2674; q=dns/txt; s=iport; t=1376939626; x=1378149226; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=kjzOGPJBPLmaqdMRb0MJkRToG2uDGE2jI6E+OTJ1+pE=; b=lrCWDB8gHe/IusY5i+UDEqqsTjZ/81sqnAKSXGTFvHEsb82CaNBVgBt9 6O6Vt3843aWbArGCRYIeK79Zq7VfM/xcPJRqNXvBEnWn5+HlKpfR8kJyI aNZHzQds/CRAA0lDQAVp+E3H/2QoJCDHXla+B6E7SRzBh7k6XVMww2f0D k=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgoFABJuElKtJV2Y/2dsb2JhbABaDoJ5NVG/MoEjFnSCJAEBAQMBAQEBawsFCwIBCBgKJCcLJQIEDgUIBod8Bgy2MJArMQeDG3cDkBaBLodNkCiCXT+CKg
X-IronPort-AV: E=Sophos; i="4.89,914,1367971200"; d="asc'?scan'208"; a="249111202"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-5.cisco.com with ESMTP; 19 Aug 2013 19:13:45 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r7JJDjI3010975 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 19 Aug 2013 19:13:45 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.28]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.02.0318.004; Mon, 19 Aug 2013 14:13:45 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Joe Touch <touch@isi.edu>
Thread-Topic: [v6ops] draft-taylor-v6ops-fragdrop WGLC
Thread-Index: AQHOnRA5eHCcTs451kadvEuCKo14UQ==
Date: Mon, 19 Aug 2013 19:13:44 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B9A92CB@xmb-rcd-x09.cisco.com>
References: <201308181800.r7II06mv003294@irp-view13.cisco.com> <521263D3.6070704@isi.edu>
In-Reply-To: <521263D3.6070704@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.19.64.119]
Content-Type: multipart/signed; boundary="Apple-Mail=_191333E8-C2B9-4943-8BF6-7DEEF684A61E"; protocol="application/pgp-signature"; micalg="pgp-sha1"
MIME-Version: 1.0
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>
Subject: Re: [v6ops] draft-taylor-v6ops-fragdrop WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 19:13:50 -0000

On Aug 19, 2013, at 11:28 AM, Joe Touch <touch@isi.edu>
 wrote:

> Hi, all,
> 
> I don't quite understand a WGLC on an individual submission. IMO, if it's a WG doc it needs to be opened up for substantial revision.
> 
> As an individual submission, I think it strays too far into the purview of this WG to be permitted.

I can see this both ways. v6ops has in the past sent individual documents this way when it agreed to them. My perspective is that the draft is largely agreed to and is close to being ready to move on. If we need to rework it in some way, we can have the reworked draft as a working group document. If we agree to it as it stands, I'm not sure I see the mechanical point.

> On the specific point of content, the paragraph at the end of the intro is disingenuous; Section 2.2 is far too brief to be considered anything but dismissive of the cons of dropping fragments, and the rest of the document reads like justification of that behavior.

Ack. Thanks.

> Joe
> 
> On 8/18/2013 11:00 AM, Fred Baker wrote:
>> This is to initiate a two week working group last call of
>> http://tools.ietf.org/html/draft-taylor-v6ops-fragdrop.  Please read it now. If you find nits
>> (spelling errors, minor suggested wording changes, etc), comment to the
>> authors; if you find greater issues, such as disagreeing with a
>> statement or finding additional issues that need to be addressed,
>> please post your comments to the list.
>> 
>> We are looking specifically for comments on the importance of the
>> document as well as its content. If you have read the document and
>> believe it to be of operational utility, that is also an important
>> comment to make.
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>> 

If at first the idea is not absurd, then there is no hope for it.  
Albert Einstein