[Int-area] Probably ignorant question about <http://www.ietf.org/id/draft-briscoe-intarea-ipv4-id-reuse-00.txt>

Andrew Sullivan <ajs@crankycanuck.ca> Tue, 29 March 2011 12:23 UTC

Return-Path: <ajs@crankycanuck.ca>
X-Original-To: int-area@core3.amsl.com
Delivered-To: int-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2D3283A67B6 for <int-area@core3.amsl.com>; Tue, 29 Mar 2011 05:23:40 -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=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zl-TS8XhvMX9 for <int-area@core3.amsl.com>; Tue, 29 Mar 2011 05:23:39 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 3B1523A6783 for <int-area@ietf.org>; Tue, 29 Mar 2011 05:23:39 -0700 (PDT)
Received: from shinkuro.com (unknown [130.129.99.131]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id F3D731ECB41D for <int-area@ietf.org>; Tue, 29 Mar 2011 12:25:15 +0000 (UTC)
Date: Tue, 29 Mar 2011 08:25:11 -0400
From: Andrew Sullivan <ajs@crankycanuck.ca>
To: int-area@ietf.org
Message-ID: <20110329122510.GG88058@shinkuro.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: [Int-area] Probably ignorant question about <http://www.ietf.org/id/draft-briscoe-intarea-ipv4-id-reuse-00.txt>
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Mar 2011 12:23:40 -0000

Hi,

I was going to ask a question about
draft-briscoe-intarea-ipv4-id-reuse-00.txt in the meeting today, but
we didn't have time.  This is probably a know-nothing question, so
feel free to point and laugh.

Over in DNS-land, we twist ourselves into funny shapes not to change
things because we always feel that we simply don't know what people
might be doing with things that were once legal.  There are plenty of
things we'd like to get rid of, and things we'd like to require, but
in all cases we can't because we don't know what people have relied
on.  Effectively, in the DNS, once something is defined we have to
live with it more or less forever, no matter how much better we know
we could make it.

As someone said in the meeting, the bit being proposed to reuse is in
fact set now.  So how do you know that changing the rules about that
bit won't break anything?  (This is not a rhetorical question.  This
topic isn't really my comfy place in the stack, and I don't know.)  I
guess this is partly addressed in section 6, but that's just facing
the middlebox case, I think.
          
Best regards,

A

-- 
Andrew Sullivan
ajs@crankycanuck.ca