IETF Logo Mail Archive

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

Jared Mauch <jared@puck.nether.net> Tue, 01 November 2016 20:40 UTC

Return-Path: <jared@puck.nether.net>
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 2B0461294DD for <idr@ietfa.amsl.com>; Tue, 1 Nov 2016 13:40:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.699
X-Spam-Level:
X-Spam-Status: No, score=-5.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 2GpzgbVp7yGK for <idr@ietfa.amsl.com>; Tue, 1 Nov 2016 13:40:09 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 169531294D8 for <idr@ietf.org>; Tue, 1 Nov 2016 13:40:09 -0700 (PDT)
Received: from [IPv6:2603:3015:3603:8e00:51e0:59a6:676c:7860] (unknown [IPv6:2603:3015:3603:8e00:51e0:59a6:676c:7860]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 708A554075A; Tue, 1 Nov 2016 16:40:07 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\))
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <9b5c0c39c07c46c28a2aba52ea4b082d@XCH-ALN-014.cisco.com>
Date: Tue, 01 Nov 2016 16:40:06 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2D473D49-E8B2-4CD5-9A0B-EE9B1005B318@puck.nether.net>
References: <169A4C1A-302E-4FE0-841A-ADA63E812E1F@juniper.net> <20161101133240.GK1581@hanna.meerval.net> <9b5c0c39c07c46c28a2aba52ea4b082d@XCH-ALN-014.cisco.com>
To: "Jakob Heitz (jheitz)" <jheitz@cisco.com>
X-Mailer: Apple Mail (2.3251)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/EqsDpgJH99PHIwdgumx1Qn3_m7c>
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 20:40:10 -0000

> On Nov 1, 2016, at 3:32 PM, Jakob Heitz (jheitz) <jheitz@cisco.com> wrote:
> 
> I support it for all these attribute codes.
> However, we should give the users of 129, 241, 242 and 243 a chance to ask for a reservation of the codes they are using.
> At least give them the option to reserve them once they are deprecated by this document.

There seems to be carrot here, which I’m in favor of.  We can always remove items during WG LC if they attain their allocation through implementations.

- Jared

v2.23.0 | Report a Bug | By Email