Re: "Deprecate"

RJ Atkinson <rja.lists@gmail.com> Fri, 02 August 2013 12:35 UTC

Return-Path: <rja.lists@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 20C7A11E833C for <ipv6@ietfa.amsl.com>; Fri, 2 Aug 2013 05:35:42 -0700 (PDT)
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=[AWL=0.000, BAYES_00=-2.599]
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 rRpyMsEUp-Bi for <ipv6@ietfa.amsl.com>; Fri, 2 Aug 2013 05:35:41 -0700 (PDT)
Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 8615B11E8319 for <ipv6@ietf.org>; Fri, 2 Aug 2013 05:34:32 -0700 (PDT)
Received: by mail-qc0-f173.google.com with SMTP id z10so283633qcx.18 for <ipv6@ietf.org>; Fri, 02 Aug 2013 05:34:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=UKQ1iZOfKCBMImODAtUdj8GOniYaeUKZFXxxLbcip0s=; b=p/7Zv9sW1MVt3n/d+xISFO/FEd5aD1/rOj2OyNvChBYuLyruBv5j2SmJte1pFRwknz CkH/rPkAKd71+gVeN4nXzGwhgbOIPWCLJs1sdjIniubRZ/ElYOMjeisZPga7y/Xrb1XE KUkFdWzDVQ02zcpGzYIufg9vNrzq1lUqnnSvHh6uybv3rlJS5UAnCXRkpsZ7cY8k0jJ+ rAz7/1m9Yu9IdKLtBZNt0+jAuZvihO1KdV3qH3SUMDs0BcKEVCVQ1NdPNHe7PDKJAbwY e402S2zGCuqFh5W/dYnRv1OVl9Hb4Xru9N0km3IsdsxmlND8tTt4ocejD3x1aACt2VeK Ynnw==
X-Received: by 10.224.53.196 with SMTP id n4mr10551954qag.104.1375446868919; Fri, 02 Aug 2013 05:34:28 -0700 (PDT)
Received: from [10.30.20.15] (pool-96-255-149-117.washdc.fios.verizon.net. [96.255.149.117]) by mx.google.com with ESMTPSA id e8sm1358018qai.1.2013.08.02.05.34.28 for <ipv6@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 02 Aug 2013 05:34:28 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Apple Message framework v1283)
Subject: Re: "Deprecate"
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <2CF4CB03E2AA464BA0982EC92A02CE25127193F1@BY2PRD0511MB428.namprd05.prod.outlook.com>
Date: Fri, 02 Aug 2013 08:34:27 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0DFABCA9-79D3-4287-978E-5F7F7BBC13A8@gmail.com>
References: <C780A80A-33B5-46C2-BADE-B19B653562DA@gmail.com> <2CF4CB03E2AA464BA0982EC92A02CE25127193F1@BY2PRD0511MB428.namprd05.prod.outlook.com>
To: ipv6@ietf.org
X-Mailer: Apple Mail (2.1283)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 02 Aug 2013 12:35:42 -0000

On 02  Aug 2013, at 03:58 , Ronald Bonica wrote:
> Furthermore, we can now make clear that the two following
> statements regarding *New* applications offer practical
> alternatives.
> 
> These are:
> a) PMTUD/PLMTUD
> and b) short PDUs

Agree.  I am reluctant to say that any of those are sufficient
in all deployments, because there are too many IPv6 deployments
to evaluate, but clearly each of those mechanisms can be useful.

> How about:
>    MUST support PMTUD and SHOULD support PLMTUD,
> just in case ICMP PTB is filtered.

Fine.  "MUST support PMTUD" and "SHOULD support PLMTUD".

>> I would change s/MUST NOT/SHOULD NOT/.
>> 
>> I'd delete the phrase "of 1280 bytes" as well, mainly because it is
>> redundant, and partly so that this BCP would not need updating if the
>> 1280 number changed in future.  (It has already changed from
>> unspecified to 576 to 1280 over time.)
> 
> I think that MUST is OK, so long as we are clear that we are talking
> about an application for which IP fragmentation has already been
> ruled out.

I'd like to read the draft text in an I-D first.

> I would say that ICMP PTB messages MUST never be blocked,
> even if the MTU is small. RFC 2460 specifies one corner case
> where the MTU can be small.

Agree.  Fernando has identified some scenarios where the advertised 
MTU will be smaller than 1280.  Additionally, I've seen some other 
real-world scenarios where it happens.

So, I'd suggest that the document outline several scenarios where
the MTU can be small, so that implementers and operators reading
the document will realise that smaller MTUs can appear in the wild.

> Yes. Currently the section on Tunnels contains one word of text,
> "TBD".  I will fix that in the next revision.

From an implementation perspective, most often it is expensive
& complex for a tunnel endpoint reassemble transit fragments.  

In the current global Internet, few router implementers are 
comfortable trying to reassemble anywhere in the middle of the 
path,  in part because of the additional attack surface that
reassembling transit traffic would create.

Instead, at tunnel egress, any fragments are likely to be 
merely decapsulated and then forwarded.  So, it is critical 
that end systems be able to reassemble fragments as fragments 
will continue to exist in the real world.

Yours,

Ran