IETF Logo Mail Archive

[bgmp] Note for draft-ietf-bgmp-spec

Bill Fenner <fenner@research.att.com> Thu, 12 February 2004 23:06 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21796 for <bgmp-archive@odin.ietf.org>; Thu, 12 Feb 2004 18:06:01 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArPtm-0002X4-8Z for bgmp-archive@odin.ietf.org; Thu, 12 Feb 2004 18:05:34 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1CN5YWA009734 for bgmp-archive@odin.ietf.org; Thu, 12 Feb 2004 18:05:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArPtm-0002Wv-1N for bgmp-web-archive@optimus.ietf.org; Thu, 12 Feb 2004 18:05:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21739 for <bgmp-web-archive@ietf.org>; Thu, 12 Feb 2004 18:05:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ArPth-0000Wi-00 for bgmp-web-archive@ietf.org; Thu, 12 Feb 2004 18:05:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ArPsk-0000RF-00 for bgmp-web-archive@ietf.org; Thu, 12 Feb 2004 18:04:30 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1ArPsM-0000Ma-00 for bgmp-web-archive@ietf.org; Thu, 12 Feb 2004 18:04:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArPsI-0001uR-Ij; Thu, 12 Feb 2004 18:04:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArPro-0001eE-WE for bgmp@optimus.ietf.org; Thu, 12 Feb 2004 18:03:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21562 for <bgmp@ietf.org>; Thu, 12 Feb 2004 18:03:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ArPrk-0000M5-00 for bgmp@ietf.org; Thu, 12 Feb 2004 18:03:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ArPqo-0000Ho-00 for bgmp@ietf.org; Thu, 12 Feb 2004 18:02:31 -0500
Received: from mail-red.research.att.com ([192.20.225.110] helo=mail-white.research.att.com) by ietf-mx with esmtp (Exim 4.12) id 1ArPqV-0000D5-00 for bgmp@ietf.org; Thu, 12 Feb 2004 18:02:11 -0500
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by mail-white.research.att.com (Postfix) with ESMTP id E13FF66403C; Thu, 12 Feb 2004 18:00:31 -0500 (EST)
Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by mail-blue.research.att.com (Postfix) with ESMTP id 422F1F3B0D; Thu, 12 Feb 2004 17:56:00 -0500 (EST)
Received: (from fenner@localhost) by windsor.research.att.com (8.11.6+Sun/8.8.5) id i1CN1gA16070; Thu, 12 Feb 2004 15:01:42 -0800 (PST)
Message-Id: <200402122301.i1CN1gA16070@windsor.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
To: bgmp@ietf.org
Cc: dthaler@microsoft.com
Date: Thu, 12 Feb 2004 15:01:41 -0800
From: Bill Fenner <fenner@research.att.com>
Versions: dmail (solaris) 2.5a/makemail 2.9d
Subject: [bgmp] Note for draft-ietf-bgmp-spec
Sender: bgmp-admin@ietf.org
Errors-To: bgmp-admin@ietf.org
X-BeenThere: bgmp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bgmp>, <mailto:bgmp-request@ietf.org?subject=unsubscribe>
List-Id: Border Gateway Multicast Protocol <bgmp.ietf.org>
List-Post: <mailto:bgmp@ietf.org>
List-Help: <mailto:bgmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bgmp>, <mailto:bgmp-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

Folks,

  The IESG approved draft-ietf-bgmp-spec, with a request for a note
describing why it's going for informational instead of standards track.
I drafted the following; comments are appreciated.


NOTE:
  This specification is published for the general information of the
  Internet technical community and as an archival record of the work
  done.  Although the working group had consensus on this document,
  there was insufficient interest from the operational and vendor
  community to develop an implementation, which is a requirement for
  a routing protocol to enter the standards track.


Thanks,
  Bill

_______________________________________________
bgmp mailing list
bgmp@ietf.org
https://www1.ietf.org/mailman/listinfo/bgmp

v2.23.0 | Report a Bug | By Email