Re: [Idr] Working group adoption call for draft-snijders-idr-deprecate-30-31-129

Jeffrey Haas <jhaas@pfrc.org> Tue, 01 November 2016 14:38 UTC

Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 392FF129705 for <idr@ietfa.amsl.com>; Tue, 1 Nov 2016 07:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.399
X-Spam-Level:
X-Spam-Status: No, score=-3.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 5uIIQutwMGgo for <idr@ietfa.amsl.com>; Tue, 1 Nov 2016 07:38:05 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 492961297BC for <idr@ietf.org>; Tue, 1 Nov 2016 07:38:05 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 551621E337; Tue, 1 Nov 2016 10:40:36 -0400 (EDT)
Date: Tue, 1 Nov 2016 10:40:36 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: "John G.Scudder" <jgs@juniper.net>
Message-ID: <20161101144036.GB10519@pfrc.org>
References: <169A4C1A-302E-4FE0-841A-ADA63E812E1F@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <169A4C1A-302E-4FE0-841A-ADA63E812E1F@juniper.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/bk7qcWLo24iOZNwummnHCWszM00>
Cc: IETF IDR Working Group <idr@ietf.org>
Subject: Re: [Idr] Working group adoption call for draft-snijders-idr-deprecate-30-31-129
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Nov 2016 14:38:08 -0000

On Mon, Oct 31, 2016 at 05:18:57PM -0400, John G.Scudder wrote:
> The author has asked for the WG to adopt  draft-snijders-idr-deprecate-30-31-129. 
> 
> If you support or oppose adoption please reply indicating so. Reasons for your position are helpful, as volunteering to review, comment, and/or shepherd. As an aside, I will note that I don't think the WG has the option of doing nothing, so if you oppose adoption please address what you think should be done instead.

I have a few points to raise here:
1. Do we actually need a draft published to request IANA to block out
allocation of these code points?  If so, we're going to end up with a number
of trivial drafts for these corrective actions.  I'm interested in hearing
the IESG's opinion on this point.

If we do need a draft, this draft is as fine as any.  Hopefully we don't
need one.

2. Much as it's tempting to try to use this process to try to be the clue
hammer and "punish" people for grabbing code points, you burn enough bridges
you eventually run out of wood.

We have a few issues code shipping with such use suggest:

2a. Some of these things are features in use.  If so, they're just going to
have to get a different official code point.  

IMO, the right answer here is to push the implementors to get their
registrations in order and officially request them.  The penalty on *them*
is the potential that someone else has already collided with them due to
different squatting.

2b. Some of these things are early implementations that are against drafts
that aren't fully mature.  This means there will be versioning issues.
Either the code point gets re-used and deals with the versioning problem or
the code point needs deprecation.

And even then, the fact that there's an early implementation means that
eventually a code point is needed.

---

It seems to me what is needed is some work to classify such early
deployments as 2a or 2b.  2a just involves getting some administrative
issues cleared.  2b means we should discuss how do we "clean" a code point
sooner than later.

Final observation:  Some of this is messy due to scope propagation issues of
internal features.  This is another wake-up to deal with that propblem.

-- Jeff