IETF Logo Mail Archive

Re: Alissa Cooper's Discuss on draft-ietf-bfd-yang-16: (with DISCUSS and COMMENT)

Jeffrey Haas <jhaas@pfrc.org> Tue, 10 July 2018 23:34 UTC

Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE395130E67; Tue, 10 Jul 2018 16:34:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 wSEZgFRYZqla; Tue, 10 Jul 2018 16:34:27 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id AAB59130E23; Tue, 10 Jul 2018 16:34:27 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id AFEE01E28F; Tue, 10 Jul 2018 19:34:18 -0400 (EDT)
Date: Tue, 10 Jul 2018 19:34:18 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Martin Vigoureux <martin.vigoureux@nokia.com>
Cc: Alissa Cooper <alissa@cooperw.in>, The IESG <iesg@ietf.org>, rtg-bfd@ietf.org, draft-ietf-bfd-yang@ietf.org, bfd-chairs@ietf.org
Subject: Re: Alissa Cooper's Discuss on draft-ietf-bfd-yang-16: (with DISCUSS and COMMENT)
Message-ID: <20180710233418.GC12853@pfrc.org>
References: <153065271588.5091.13098454481458174550.idtracker@ietfa.amsl.com> <bb31e2ae-4d37-508a-64ad-1fdf02942488@nokia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <bb31e2ae-4d37-508a-64ad-1fdf02942488@nokia.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/5Yw5MFJyBLpY_NjuWFBTIC5YIgg>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2018 23:34:30 -0000

On Wed, Jul 04, 2018 at 06:33:16PM +0200, Martin Vigoureux wrote:
> Hello Alissa,
> 
> thanks for your review.
> I'm fine with discussing this but wonder if we should tie it to this draft.
> I would prefer that we collectively discuss that and once we reach a
> decision we start applying it.

It's also worth noting that some form of meta-syntactic name would be needed
for these sorts of contexts as well.  As noted elsewhere, IANA is a name
currently under IETF control.  Additionally, "IANA maintained" has long
tradition for these sorts of registries, certainly back to the MIB days.
You may wish to seek history on this matter from prior OPS chairs in that
context.


My suggestion is that this discuss be cleared and perhaps raise this during
the wgchairs session.


-- Jeff

v2.23.0 | Report a Bug | By Email