[Bgp-autoconf] New Non-WG Mailing List: bgp-autoconf

IETF Secretariat <ietf-secretariat@ietf.org> Wed, 29 January 2020 16:18 UTC

Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: bgp-autoconf@ietf.org
Delivered-To: bgp-autoconf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3869D1201B7; Wed, 29 Jan 2020 08:18:18 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Cc: jgs@juniper.net, shares@ndzh.com, gs@juniper.net, bgp-autoconf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.116.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org
Message-ID: <158031469816.2723.14757034395334094991.idtracker@ietfa.amsl.com>
Date: Wed, 29 Jan 2020 08:18:18 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/bgp-autoconf/5zPBybe8MUwphFs0ykgrN-W9x6M>
X-Mailman-Approved-At: Wed, 29 Jan 2020 10:26:37 -0800
Subject: [Bgp-autoconf] New Non-WG Mailing List: bgp-autoconf
X-BeenThere: bgp-autoconf@ietf.org
X-Mailman-Version: 2.1.29
List-Id: BGP autoconfiguration design team discussion list <bgp-autoconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bgp-autoconf>, <mailto:bgp-autoconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bgp-autoconf/>
List-Post: <mailto:bgp-autoconf@ietf.org>
List-Help: <mailto:bgp-autoconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bgp-autoconf>, <mailto:bgp-autoconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2020 16:18:18 -0000

A new IETF non-working group email list has been created.

List address: bgp-autoconf@ietf.org
Archive: https://mailarchive.ietf.org/arch/browse/bgp-autoconf/
To subscribe: https://www.ietf.org/mailman/listinfo/bgp-autoconf

Purpose:
IDR has set up a design team to explore BGP autoconfiguration. The design team’s initial charter is to propose requirements and solution space outline to guide our discussion as a WG in producing a solution. The design team isn’t forbidden from suggesting a solution, but it’s not one of our specific requests to them. As usual with IETF design teams (https://ietf.org/about/groups/iesg/statements/design-teams/), "The key point here is that the output of a design team is input to a working group, not a final document. Such a document must not be considered as more important than any other input to the working group.” 

This list belongs IETF area: Routing Area

For additional information, please contact the list administrators.