Additional Last Call (References): 'Multicast Source Discovery Protocol (MSDP) Deployment Scenarios' to BCP

The IESG <iesg-secretary@ietf.org> Fri, 16 July 2004 18:09 UTC

Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20380 for <ietf-announce-archive@ietf.org>; Fri, 16 Jul 2004 14:09:28 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BlX9C-0000cS-2D for ietf-announce-archive@ietf.org; Fri, 16 Jul 2004 14:09:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BlX8H-0000I7-00 for ietf-announce-archive@ietf.org; Fri, 16 Jul 2004 14:08:29 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx with esmtp (Exim 4.12) id 1BlX7m-0007kN-00; Fri, 16 Jul 2004 14:07:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BlX3y-0006rE-VE; Fri, 16 Jul 2004 14:04:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BlX0J-0006NM-U4 for ietf-announce@megatron.ietf.org; Fri, 16 Jul 2004 14:00:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19719 for <ietf-announce@ietf.org>; Fri, 16 Jul 2004 14:00:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BlX0G-0005Jp-Si for ietf-announce@ietf.org; Fri, 16 Jul 2004 14:00:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BlWzI-0004wc-00 for ietf-announce@ietf.org; Fri, 16 Jul 2004 13:59:13 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx with esmtp (Exim 4.12) id 1BlWyJ-0004IC-00 for ietf-announce@ietf.org; Fri, 16 Jul 2004 13:58:11 -0400
Received: from apache by megatron.ietf.org with local (Exim 4.32) id 1BlWvQ-0005dT-Qf; Fri, 16 Jul 2004 13:55:12 -0400
X-test-idtracker: no
To: ietf-announce@ietf.org
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1BlWvQ-0005dT-Qf@megatron.ietf.org>
Date: Fri, 16 Jul 2004 13:55:12 -0400
Cc: mboned@network-services.uoregon.edu
Subject: Additional Last Call (References): 'Multicast Source Discovery Protocol (MSDP) Deployment Scenarios' to BCP
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg@ietf.org
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60

The IESG has received a request from the MBONE Deployment WG to consider 
'Multicast Source Discovery Protocol (MSDP) Deployment Scenarios' 
<draft-ietf-mboned-msdp-deploy-06.txt> as a BCP. 

This document has been reviewed by the IESG and the following issue was
found:
                                                                                
The document has a normative reference to an experimental protocol:
                                                                                
RFC3618  Meyer, D. and W. Fenner (Editors), "The Multicast
         Source Discovery Protocol (MSDP)", RFC 3618, October, 2003.
                                                                                
IETF procedures generally require that a standards track RFC may not
have a normative reference to a document at a lower standards level.
                                                                                
However, according to:
                                                                                
http://www.ietf.org/internet-drafts/draft-ymbk-downref-02.txt

an exception can be made by explicitly mentioning this issue during
the last call. This procedure was not available when the original last
call was made.
                                                                                
The IESG plans to make a decision on whether to accept the reference
in the next few weeks, and solicits final comments. Please send any
comments to the iesg@ietf.org or ietf@ietf.org mailing lists by
2003-07-29.
                                                                                
File(s) can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-mboned-msdp-deploy-06.txt


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce