[pim] WG Last Call - draft-ietf-pim-sm-bsr-08

To: pim at ietf.org
Subject: [pim] WG Last Call - draft-ietf-pim-sm-bsr-08
From: Mike McBride <mmcbride at cisco.com>
Date: Wed, 17 May 2006 14:05:44 -0700 (PDT)
Authentication-results: sj-dkim-2.cisco.com; header.From=mmcbride@cisco.com; dkim=pass ( sig from cisco.com verified; );
Dkim-signature: a=rsa-sha1; q=dns; l=260; t=1147899945; x=1148763945; c=relaxed/simple; s=sjdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mmcbride@cisco.com; z=From:Mike=20McBride=20<mmcbride@cisco.com> |Subject:[pim]=20WG=20Last=20Call=20-=20draft-ietf-pim-sm-bsr-08; X=v=3Dcisco.com=3B=20h=3DbCSUboB+QSRKGTd1PekBlE44hRI=3D; b=KFFsa3MCpTs0L2HjjZI+GQDs2O/zEIr1Z5KeFSp3alXaCncvYxpajBJ08JHSp+Mjll2dfTuh Mry78IMshcXs1OEnJs/crneOI82fW//4t5GQ2xzh9HHUAR1rH3RpqXqL;
List-help: <mailto:pim-request@ietf.org?subject=help>
List-id: Protocol Independent Multicast <pim.ietf.org>
List-post: <mailto:pim@ietf.org>
List-subscribe: <https://www1.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>

Today starts a two week wglc for the pim-sm-bsr draft. May 31st, 2006 will be the final day of this last call. Please review this document and send comments to the list.

http://www.ietf.org/internet-drafts/draft-ietf-pim-sm-bsr-08.txt

thanks,
mike

_______________________________________________
pim mailing list
pim at ietf.org
https://www1.ietf.org/mailman/listinfo/pim

Follow-Ups:
- Re: [pim] WG Last Call - draft-ietf-pim-sm-bsr-08
  - From: Mike McBride

Prev by Date: Re: [pim] PIM BSR semantic fragementation.
Next by Date: Re: [pim] Re: BSM: is it bidir or ASM
Previous by thread: [pim] About "draft-ietf-pim-sm-v2-new-12.txt" PIM register-stop message
Next by thread: Re: [pim] WG Last Call - draft-ietf-pim-sm-bsr-08
Index(es):
- Date
- Thread

[pim] WG Last Call - draft-ietf-pim-sm-bsr-08

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.