Re: [Idr] BGP autodiscovery design team

Job Snijders <job@ntt.net> Thu, 05 December 2019 13:50 UTC

Return-Path: <job@ntt.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 955C812004A for <idr@ietfa.amsl.com>; Thu, 5 Dec 2019 05:50:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=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 Uuu3v94z-7Mf for <idr@ietfa.amsl.com>; Thu, 5 Dec 2019 05:50:13 -0800 (PST)
Received: from mail3.mlpsca01.us.to.gin.ntt.net (mail3.mlpsca01.us.to.gin.ntt.net [IPv6:2001:418:1401:17::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80EEE120013 for <idr@ietf.org>; Thu, 5 Dec 2019 05:50:13 -0800 (PST)
Received: by mail3.mlpsca01.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92.3) (envelope-from <job@ntt.net>) id 1icrWH-0005Fu-23 (job@us.ntt.net) for idr@ietf.org; Thu, 05 Dec 2019 13:50:13 +0000
Received: by mail-oi1-f179.google.com with SMTP id i1so2750559oie.8 for <idr@ietf.org>; Thu, 05 Dec 2019 05:50:12 -0800 (PST)
X-Gm-Message-State: APjAAAUU/abH5fd1Wy/Hasl6pe7gw9DDRb9LehHvmQngPKhrpHmYFfmy YjDiBjLm/VmR7BD1HTtVcBraqBtMd82L8HCMsGcaOg==
X-Google-Smtp-Source: APXvYqx9Zw2FTAZIlIEBVsjNjD1szSbClXFHN7a/YNPIVQJopcNHjt/v7ijZ3cbf/FEv3yX9/PKIL+UKcuHElEumQfw=
X-Received: by 2002:a05:6808:24e:: with SMTP id m14mr1422454oie.168.1575553812429; Thu, 05 Dec 2019 05:50:12 -0800 (PST)
MIME-Version: 1.0
References: <E7E38075-54F2-4F16-97BE-EE24943B5BFE@juniper.net> <CAOj+MMG7d4H2R_aZU0xQoW+a=wvgqn1oaOPQb-L1NJ2qX_07cg@mail.gmail.com> <B17A6910EEDD1F45980687268941550F4DA2809D@MISOUT7MSGUSRCD.ITServices.sbc.com>
In-Reply-To: <B17A6910EEDD1F45980687268941550F4DA2809D@MISOUT7MSGUSRCD.ITServices.sbc.com>
From: Job Snijders <job@ntt.net>
Date: Thu, 5 Dec 2019 14:50:01 +0100
X-Gmail-Original-Message-ID: <CACWOCC805XugEgKT8diRb2zMQWaM=ydAo1k5pEW1YEOawGUx3A@mail.gmail.com>
Message-ID: <CACWOCC805XugEgKT8diRb2zMQWaM=ydAo1k5pEW1YEOawGUx3A@mail.gmail.com>
To: "UTTARO, JAMES" <ju1738@att.com>
Cc: John Scudder <jgs=40juniper.net@dmarc.ietf.org>, Robert Raszuk <robert@raszuk.net>, idr wg <idr@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005090a90598f535d1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/X9FzVJVTTdzve1qj-bkfwNVcUcU>
Subject: Re: [Idr] BGP autodiscovery design team
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 05 Dec 2019 13:50:16 -0000

On Thu, Dec 5, 2019 at 14:46 UTTARO, JAMES <ju1738@att.com> wrote:

> *I agree with Roberts’ point. Prior to crafting or selecting a draft as
> the basis for a proposal the design team should clearly articulate the
> scope, use cases and requirements that need to be addressed. IMO stating
> that in an informational RFC is a good way to ensure that all stakeholders
> are in agreement as to what the eventual specification/draft addresses, and
> as important does not address. When creating EVPN we first crafted an
> informational RFC https://tools.ietf.org/html/rfc7209
> <https://tools.ietf.org/html/rfc7209> that specified Active/Active
> Multi-homing, flooding and multicast optimization etc… which formed the
> basis for the RFC 7432. This focused the design team on realizing the
> requirements articulated there.*
>

I think the above is good feedback.

Also, it appears the entire working groep is interested to be part of the
design team. Perhaps the design team’s mailing list should be idr@ietf.org?
:-)

Kind regards,

Job