[pim] FW: Last Call: <draft-ietf-mboned-maccnt-req-10.txt>

Adrian Farrel <Adrian.Farrel@huawei.com> Sat, 23 April 2011 14:16 UTC

Return-Path: <Adrian.Farrel@huawei.com>
X-Original-To: pim@ietfc.amsl.com
Delivered-To: pim@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 0088FE06FC for <pim@ietfc.amsl.com>; Sat, 23 Apr 2011 07:16:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.11
X-Spam-Level:
X-Spam-Status: No, score=-105.11 tagged_above=-999 required=5 tests=[AWL=1.489, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HTSJlCP+fAhA for <pim@ietfc.amsl.com>; Sat, 23 Apr 2011 07:16:56 -0700 (PDT)
Received: from usaga03-in.huawei.com (usaga03-in.huawei.com [206.16.17.220]) by ietfc.amsl.com (Postfix) with ESMTP id 6E3D2E069C for <pim@ietf.org>; Sat, 23 Apr 2011 07:16:56 -0700 (PDT)
Received: from huawei.com (usaga03-in [172.18.4.17]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LK300KW1ZO7PV@usaga03-in.huawei.com> for pim@ietf.org; Sat, 23 Apr 2011 09:16:56 -0500 (CDT)
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LK300A5LZO540@usaga03-in.huawei.com> for pim@ietf.org; Sat, 23 Apr 2011 09:16:55 -0500 (CDT)
Date: Sat, 23 Apr 2011 15:16:53 +0100
From: Adrian Farrel <Adrian.Farrel@huawei.com>
To: pim@ietf.org
Message-id: <0c7501cc01c1$1934d330$4b9e7990$@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Outlook 14.0
Content-type: text/plain; charset="us-ascii"
Content-language: en-gb
Content-transfer-encoding: 7bit
Thread-index: AcwBwMB3l9cltktbSH6SSUXLYqaqFA==
Subject: [pim] FW: Last Call: <draft-ietf-mboned-maccnt-req-10.txt>
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Adrian.Farrel@huawei.com
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Apr 2011 14:16:57 -0000

Hi PIM WG,

With your potential new role caring for IGMP/MLD, please be aware of the IETF
last call currently in progress for this document.

All review comments (favorable and otherwise) should be sent to the IETF mailing
list.

Thanks,
Adrian

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: 21 April 2011 22:55
> To: IETF-Announce
> Cc: mboned@ietf.org
> Subject: Last Call: <draft-ietf-mboned-maccnt-req-10.txt> (Requirements for
> Multicast AAA coordinated between Content Provider(s) and Network Service
> Provider(s)) to Informational RFC
> 
> 
> The IESG has received a request from the MBONE Deployment WG (mboned) to
> consider the following document:
> - 'Requirements for Multicast AAA coordinated between Content Provider(s)
>    and Network Service Provider(s)'
>   <draft-ietf-mboned-maccnt-req-10.txt> as an Informational RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2011-05-05. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-mboned-maccnt-req/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-mboned-maccnt-req/
> 
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce