
From pim-bounces@ietf.org  Sun Feb  1 18:07:28 2009
Return-Path: <pim-bounces@ietf.org>
X-Original-To: pim-archive@megatron.ietf.org
Delivered-To: ietfarch-pim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 24B7D3A6866; Sun,  1 Feb 2009 18:07:28 -0800 (PST)
X-Original-To: pim@core3.amsl.com
Delivered-To: pim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F24563A67BD for <pim@core3.amsl.com>; Sun,  1 Feb 2009 18:07:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.005
X-Spam-Level: **
X-Spam-Status: No, score=2.005 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, TRACKER_ID=2.003]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rjtxJlPe70ZE for <pim@core3.amsl.com>; Sun,  1 Feb 2009 18:07:26 -0800 (PST)
Received: from ctyaarimta01.yaariinvites.com (ctyaarimta01.yaariinvites.com [63.167.241.174]) by core3.amsl.com (Postfix) with ESMTP id 3155F3A6866 for <pim@ietf.org>; Sun,  1 Feb 2009 18:07:26 -0800 (PST)
Received: from strongmail ([63.167.241.220]) by ctyaarimta01.yaariinvites.com (StrongMail Enterprise 4.1.1.1(4.1.1-44827)); Sun, 01 Feb 2009 21:07:07 -0500
X-VirtualServer: Default, ctyaarimta01.yaariinvites.com, 63.167.241.174
X-VirtualServerGroup: Default
X-MailingID: 00000::00000::00000::00000::::5149529
X-SMHeaderMap: mid="X-MailingID"
X-Destination-ID: pim@ietf.org
X-SMFBL: cGltQGlldGYub3Jn
Date: Sun, 1 Feb 2009 21:07:07 -0500
To: pim@ietf.org
From: Arnab Bakshi <arnab.bakshi@gmail.com>
Message-ID: <db6abcef0db95219fbc2448702dd0280@localhost.localdomain>
X-Priority: 3
X-Mailer: PHPMailer (phpmailer.sourceforge.net) [version 2.0.0 rc1]
MIME-Version: 1.0
Subject: [pim] Arnab Bakshi sent you a Friend Request on Yaari
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: arnab.bakshi@gmail.com
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/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>
Content-Type: multipart/mixed; boundary="===============1411084119=="
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

--===============1411084119==
Content-Type: multipart/alternative;
	boundary="b1_db6abcef0db95219fbc2448702dd0280"


--b1_db6abcef0db95219fbc2448702dd0280
Content-Type: text/plain; charset = "iso-8859-1"
Content-Transfer-Encoding: 8bit

Arnab Bakshi wants you to join Yaari!

Is Arnab your friend?

<a href="http://yaari.com/?controller=user&action=mailregister&friend=1&sign=YaariIVH153MGA329NXO138SIK492">Yes, Arnab is my friend!</a> <a href="http://yaari.com/?controller=user&action=mailregister&friend=0&sign=YaariIVH153MGA329NXO138SIK492">No, Arnab isn't my friend.</a>

Please respond or Arnab may think you said no :(

Thanks,
The Yaari Team
____
If you prefer not to receive this email tell us <a href="http://yaari.com/?controller=absn&action=addoptout&email=pim@ietf.org">here</a>. If you have any concerns 
regarding the content of this message, please email abuse@yaari.com.  
Yaari LLC, 358 Angier Ave, Atlanta, GA 30312

YaariIVH153MGA329NXO138SIK492


--b1_db6abcef0db95219fbc2448702dd0280
Content-Type: text/html; charset = "iso-8859-1"
Content-Transfer-Encoding: 8bit

Arnab Bakshi wants you to join Yaari!<br />
<br />
Is Arnab your friend?<br />
<br />
<a href="http://yaari.com/?controller=user&action=mailregister&friend=1&sign=YaariIVH153MGA329NXO138SIK492">Yes, Arnab is my friend!</a> <a href="http://yaari.com/?controller=user&action=mailregister&friend=0&sign=YaariIVH153MGA329NXO138SIK492">No, Arnab isn't my friend.</a><br />
<br />
Please respond or Arnab may think you said no :(<br />
<br />
Thanks,<br />
The Yaari Team<br />
____<br />
If you prefer not to receive this email tell us <a href="http://yaari.com/?controller=absn&action=addoptout&email=pim@ietf.org">here</a>. If you have any concerns <br />
regarding the content of this message, please email abuse@yaari.com.  <br />
Yaari LLC, 358 Angier Ave, Atlanta, GA 30312<br />
<br />
YaariIVH153MGA329NXO138SIK492



--b1_db6abcef0db95219fbc2448702dd0280--



--===============1411084119==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
pim mailing list
pim@ietf.org
https://www.ietf.org/mailman/listinfo/pim

--===============1411084119==--



Return-Path: <root@core3.amsl.com>
X-Original-To: pim@ietf.org
Delivered-To: pim@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id B3A6A3A69E5; Wed,  4 Feb 2009 10:30:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090204183001.B3A6A3A69E5@core3.amsl.com>
Date: Wed,  4 Feb 2009 10:30:01 -0800 (PST)
Cc: pim@ietf.org
Subject: [pim] I-D Action:draft-ietf-pim-sm-linklocal-06.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/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: Wed, 04 Feb 2009 18:30:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Protocol Independent Multicast Working Group of the IETF.


	Title           : Authentication and Confidentiality in PIM-SM Link-local Messages
	Author(s)       : W. Atwood, et al.
	Filename        : draft-ietf-pim-sm-linklocal-06.txt
	Pages           : 32
	Date            : 2009-02-04

RFC 4601 mandates the use of IPsec to ensure authentication of the
link-local messages in the Protocol Independent Multicast - Sparse
Mode (PIM-SM) routing protocol.  This document specifies mechanisms
to authenticate the PIM-SM link local messages using the IP security
(IPsec) Encapsulating Security Payload (ESP) or (optionally) the
Authentication Header (AH).  It specifies optional mechanisms to
provide confidentiality using the ESP.  Manual keying is specified as
the mandatory and default group key management solution.  To deal
with issues of scalability and security that exist with manual
keying, an optional support for automated group key management
mechanism is provided.  However, the procedures for implementing
automated group key management are left to other documents.  This
document updates RFC 4601.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pim-sm-linklocal-06.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-pim-sm-linklocal-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-02-04102317.I-D@ietf.org>


--NextPart--


Return-Path: <arnab.bakshi@gmail.com>
X-Original-To: pim@core3.amsl.com
Delivered-To: pim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D96EC28C1B4 for <pim@core3.amsl.com>; Wed,  4 Feb 2009 18:08:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.579
X-Spam-Level: 
X-Spam-Status: No, score=0.579 tagged_above=-999 required=5 tests=[AWL=0.574,  BAYES_50=0.001, GB_I_INVITATION=-2, HTML_MESSAGE=0.001, TRACKER_ID=2.003]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TNsm972RXqjE for <pim@core3.amsl.com>; Wed,  4 Feb 2009 18:08:24 -0800 (PST)
Received: from ctyaarimta01.yaariinvites.com (ctyaarimta01.yaariinvites.com [63.167.241.174]) by core3.amsl.com (Postfix) with ESMTP id 0121128C1B0 for <pim@ietf.org>; Wed,  4 Feb 2009 18:08:23 -0800 (PST)
Received: from strongmail ([63.167.241.220]) by ctyaarimta01.yaariinvites.com (StrongMail Enterprise 4.1.1.1(4.1.1-44827)); Wed, 04 Feb 2009 21:08:04 -0500
X-VirtualServer: Default, ctyaarimta01.yaariinvites.com, 63.167.241.174
X-VirtualServerGroup: Default
X-MailingID: 00000::00000::00000::00000::::5838034
X-SMHeaderMap: mid="X-MailingID"
X-Destination-ID: pim@ietf.org
X-SMFBL: cGltQGlldGYub3Jn
Date: Wed, 4 Feb 2009 21:08:04 -0500
To: pim@ietf.org
From: Arnab Bakshi <arnab.bakshi@gmail.com>
Message-ID: <c53ab09abe326c8253c3aa00c406ab1b@localhost.localdomain>
X-Priority: 3
X-Mailer: PHPMailer (phpmailer.sourceforge.net) [version 2.0.0 rc1]
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="b1_c53ab09abe326c8253c3aa00c406ab1b"
Subject: [pim] Reminder: Please Respond to Arnab's Invitation
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: arnab.bakshi@gmail.com
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/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: Thu, 05 Feb 2009 02:08:24 -0000

--b1_c53ab09abe326c8253c3aa00c406ab1b
Content-Type: text/plain; charset = "iso-8859-1"
Content-Transfer-Encoding: 8bit

Arnab Bakshi wants you to join Yaari!

Is Arnab your friend?

<a href="http://yaari.com/?controller=user&action=mailregister&friend=1&sign=YaariIVH153MGA329NXO138SIK492">Yes, Arnab is my friend!</a> <a href="http://yaari.com/?controller=user&action=mailregister&friend=0&sign=YaariIVH153MGA329NXO138SIK492">No, Arnab isn't my friend.</a>

Please respond or Arnab may think you said no :(

Thanks,
The Yaari Team
____
If you prefer not to receive this email tell us <a href="http://yaari.com/?controller=absn&action=addoptout&email=pim@ietf.org">here</a>. If you have any concerns 
regarding the content of this message, please email abuse@yaari.com.  
Yaari LLC, 358 Angier Ave, Atlanta, GA 30312

YaariIVH153MGA329NXO138SIK492


--b1_c53ab09abe326c8253c3aa00c406ab1b
Content-Type: text/html; charset = "iso-8859-1"
Content-Transfer-Encoding: 8bit

Arnab Bakshi wants you to join Yaari!<br />
<br />
Is Arnab your friend?<br />
<br />
<a href="http://yaari.com/?controller=user&action=mailregister&friend=1&sign=YaariIVH153MGA329NXO138SIK492">Yes, Arnab is my friend!</a> <a href="http://yaari.com/?controller=user&action=mailregister&friend=0&sign=YaariIVH153MGA329NXO138SIK492">No, Arnab isn't my friend.</a><br />
<br />
Please respond or Arnab may think you said no :(<br />
<br />
Thanks,<br />
The Yaari Team<br />
____<br />
If you prefer not to receive this email tell us <a href="http://yaari.com/?controller=absn&action=addoptout&email=pim@ietf.org">here</a>. If you have any concerns <br />
regarding the content of this message, please email abuse@yaari.com.  <br />
Yaari LLC, 358 Angier Ave, Atlanta, GA 30312<br />
<br />
YaariIVH153MGA329NXO138SIK492



--b1_c53ab09abe326c8253c3aa00c406ab1b--




Return-Path: <suhaiyang@huawei.com>
X-Original-To: pim@core3.amsl.com
Delivered-To: pim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6002C28C0D9 for <pim@core3.amsl.com>; Sun,  8 Feb 2009 18:50:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.79
X-Spam-Level: ****
X-Spam-Status: No, score=4.79 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, J_CHICKENPOX_21=0.6, J_CHICKENPOX_27=0.6, J_CHICKENPOX_31=0.6, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vyoqe6cqAeqb for <pim@core3.amsl.com>; Sun,  8 Feb 2009 18:50:12 -0800 (PST)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 1462E3A67A2 for <pim@ietf.org>; Sun,  8 Feb 2009 18:50:12 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KES00LPT2JILQ@szxga03-in.huawei.com> for pim@ietf.org; Mon, 09 Feb 2009 10:50:06 +0800 (CST)
Received: from huawei.com ([172.24.1.12]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KES00IS42JICL@szxga03-in.huawei.com> for pim@ietf.org; Mon, 09 Feb 2009 10:50:06 +0800 (CST)
Received: from s33630C ([10.112.18.100]) by szxml05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KES00B5D2JH7X@szxml05-in.huawei.com> for pim@ietf.org; Mon, 09 Feb 2009 10:50:06 +0800 (CST)
Date: Mon, 09 Feb 2009 10:49:58 +0800
From: Su Haiyang <suhaiyang@huawei.com>
To: pim@ietf.org
Message-id: <015e01c98a61$1cddd290$8119fea9@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_2uJJr7iP74ZDG/1rU8ZZSw)"
Thread-index: AcmKYRiVLcbNn52FRxafuGqiqob7wA==
Subject: [pim] A doubt regarding about MSDP RPF rule
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/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: Mon, 09 Feb 2009 02:50:18 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_2uJJr7iP74ZDG/1rU8ZZSw)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Hi, 

     I have one doubt about the following rfc3618 discription.

 

     Suppose the router has three msdp peer: A, B, C. 

       A is RP(maching the first check condition)

       B is eBGP NEXT_HOP(maching the second check condition)

       C is iBGP advertiser(maching the third check condition)

     

     1. Which one is rpf peer? A, B, C, or all of them.

     Suppose all of them forward the same SA message, does the router accept
all of them or only one?

     

2. If above RPF Peer preference is A>B>C, What can we do if a SA is received
from lower preferred RPF Peer first and SA would be never received from the
highest preferred RPF Peer because of the highest one's SA advertising
policy.

 

     Thanks a lot.

 

 

 

10.1.3.  Peer-RPF Forwarding Rules

 

   An SA message originated by R and received by X from N is accepted if

   N is the peer-RPF neighbor for X, and is discarded otherwise.

 

              MPP(R,N)                 MP(N,X)

      R ---------....-------> N ------------------> X

              SA(S,G,R)                SA(S,G,R)

 

   MP(N,X) is an MSDP peering between N and X.  MPP(R,N) is an MSDP

   peering path (zero or more MSDP peers) between R and N, e.g.,

   MPP(R,N) = MP(R, A) + MP(A, B) + MP(B, N).  SA(S,G,R) is an SA

   message for source S on group G originated by an RP R.

 

   The peer-RPF neighbor N is chosen deterministically, using the first

   of the following rules that matches.  In particular, N is the RPF

   neighbor of X with respect to R if

 

   (i).    N == R (X has an MSDP peering with R).

 

   (ii).   N is the eBGP NEXT_HOP of the Peer-RPF route for R.

 

   (iii).  The Peer-RPF route for R is learned through a distance-vector

           or path-vector routing protocol (e.g., BGP, RIP, DVMRP) and N

           is the neighbor that advertised the Peer-RPF route for R

           (e.g., N is the iBGP advertiser of the route for R), or N is

           the IGP next hop for R if the route for R is learned via a

           link-state protocol (e.g., OSPF [RFC2328] or IS-IS

           [RFC1142]).

 

   (iv).   N resides in the closest AS in the best path towards R.  If

           multiple MSDP peers reside in the closest AS, the peer with

           the highest IP address is the rpf-peer.

 

   (v).    N is configured as the static RPF-peer for R.


--Boundary_(ID_2uJJr7iP74ZDG/1rU8ZZSw)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<html>

<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered)">

<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Dotum;
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:SimHei;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"MS UI Gothic";
	panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
	{font-family:DotumChe;
	panose-1:2 11 6 9 0 1 1 1 1 1;}
@font-face
	{font-family:KaiTi_GB2312;
	panose-1:2 1 6 9 3 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimHei;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:KaiTi_GB2312;
	panose-1:2 1 6 9 3 1 1 1 1 1;}
@font-face
	{font-family:"\@MS UI Gothic";
	panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
	{font-family:"\@Dotum";
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:"\@DotumChe";
	panose-1:2 11 6 9 0 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	line-height:150%;
	text-autospace:none;
	font-size:10.5pt;
	font-family:"Times New Roman";
	layout-grid-mode:line;}
h1
	{margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:12.0pt;
	margin-left:21.6pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-21.6pt;
	page-break-after:avoid;
	font-size:16.0pt;
	font-family:Arial;}
h2
	{margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:12.0pt;
	margin-left:28.8pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-28.8pt;
	page-break-after:avoid;
	font-size:12.0pt;
	font-family:Arial;
	font-weight:normal;}
h3
	{margin-top:13.0pt;
	margin-right:0cm;
	margin-bottom:13.0pt;
	margin-left:36.0pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-36.0pt;
	line-height:173%;
	page-break-after:avoid;
	font-size:12.0pt;
	font-family:"Times New Roman";
	layout-grid-mode:line;
	font-weight:normal;}
p.MsoHeader, li.MsoHeader, div.MsoHeader
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	layout-grid-mode:char;
	font-size:9.0pt;
	font-family:Arial;}
p.MsoFooter, li.MsoFooter, div.MsoFooter
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:9.0pt;
	font-family:Arial;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin:0cm;
	margin-bottom:.0001pt;
	line-height:150%;
	text-autospace:none;
	font-size:9.0pt;
	font-family:"Times New Roman";
	layout-grid-mode:line;}
p.a, li.a, div.a
	{margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:54.45pt;
	margin-bottom:.0001pt;
	text-align:center;
	text-indent:-18.45pt;
	font-size:9.0pt;
	font-family:Arial;}
p.a0, li.a0, div.a0
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Arial;}
p.a1, li.a1, div.a1
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:center;
	font-size:10.5pt;
	font-family:Arial;
	font-weight:bold;}
p.a2, li.a2, div.a2
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:12.0pt;
	margin-left:54.45pt;
	text-align:center;
	text-indent:-18.45pt;
	font-size:9.0pt;
	font-family:Arial;}
p.a3, li.a3, div.a3
	{margin-top:4.0pt;
	margin-right:0cm;
	margin-bottom:4.0pt;
	margin-left:0cm;
	text-align:center;
	line-height:150%;
	page-break-after:avoid;
	text-autospace:none;
	font-size:10.5pt;
	font-family:"Times New Roman";
	layout-grid-mode:line;}
p.a4, li.a4, div.a4
	{margin-top:15.0pt;
	margin-right:0cm;
	margin-bottom:15.0pt;
	margin-left:0cm;
	text-align:center;
	line-height:150%;
	text-autospace:none;
	font-size:18.0pt;
	font-family:Arial;
	layout-grid-mode:line;}
p.a5, li.a5, div.a5
	{margin:0cm;
	margin-bottom:.0001pt;
	line-height:150%;
	text-autospace:none;
	font-size:10.5pt;
	font-family:"Times New Roman";
	layout-grid-mode:line;}
p.a6, li.a6, div.a6
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	line-height:150%;
	text-autospace:none;
	border:none;
	padding:0cm;
	font-size:9.0pt;
	font-family:Arial;
	layout-grid-mode:line;}
p.a7, li.a7, div.a7
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:18.0pt;
	line-height:150%;
	text-autospace:none;
	border:none;
	padding:0cm;
	font-size:9.0pt;
	font-family:Arial;
	layout-grid-mode:line;}
p.a8, li.a8, div.a8
	{margin:0cm;
	margin-bottom:.0001pt;
	text-indent:21.0pt;
	line-height:150%;
	text-autospace:none;
	font-size:10.5pt;
	font-family:Arial;
	color:blue;
	layout-grid-mode:line;
	font-style:italic;}
span.a9
	{font-family:SimSun;
	color:black;
	font-weight:bold;}
span.aa
	{font-family:SimSun;
	color:black;
	font-weight:bold;}
span.EmailStyle34
	{font-family:Arial;
	color:windowtext;}
 /* Page Definitions */
 @page Section1
	{size:595.3pt 841.9pt;
	margin:65.6pt 90.0pt 72.0pt 90.0pt;
	layout-grid:15.6pt;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style>

</head>

<body lang=ZH-CN link=blue vlink=purple style='text-justify-trim:punctuation'>

<div class=Section1 style='layout-grid:15.6pt'>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black face=&#23435;&#20307;><span
lang=EN-US style='font-size:10.0pt;font-family:SimSun;color:black;layout-grid-mode:
both'>Hi, </span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black face=&#23435;&#20307;><span
lang=EN-US style='font-size:10.0pt;font-family:SimSun;color:black;layout-grid-mode:
both'>&nbsp;&nbsp;&nbsp;&nbsp; I have one doubt about the following rfc3618
discription.</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black face=&#23435;&#20307;><span
lang=EN-US style='font-size:10.0pt;font-family:SimSun;color:black;layout-grid-mode:
both'>&nbsp;</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black face=&#23435;&#20307;><span
lang=EN-US style='font-size:10.0pt;font-family:SimSun;color:black;layout-grid-mode:
both'>&nbsp;&nbsp;&nbsp;&nbsp; Suppose the router has three msdp peer: A, B, C.
</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black face=&#23435;&#20307;><span
lang=EN-US style='font-size:10.0pt;font-family:SimSun;color:black;layout-grid-mode:
both'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A is RP(maching the first check
condition)</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black face=&#23435;&#20307;><span
lang=EN-US style='font-size:10.0pt;font-family:SimSun;color:black;layout-grid-mode:
both'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B is </span></font><font size=2
color=black face="Courier New"><span lang=EN-US style='font-size:10.0pt;
font-family:"Courier New";color:black;layout-grid-mode:both'>eBGP NEXT_HOP</span></font><font
size=2 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:
10.0pt;font-family:SimSun;color:black;layout-grid-mode:both'>(maching the
second check condition)</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black face=&#23435;&#20307;><span
lang=EN-US style='font-size:10.0pt;font-family:SimSun;color:black;layout-grid-mode:
both'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C is </span></font><font size=2
color=black face="Courier New"><span lang=EN-US style='font-size:10.0pt;
font-family:"Courier New";color:black;layout-grid-mode:both'>iBGP advertiser</span></font><font
size=2 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:
10.0pt;font-family:SimSun;color:black;layout-grid-mode:both'>(maching the third
check condition)</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black face=&#23435;&#20307;><span
lang=EN-US style='font-size:10.0pt;font-family:SimSun;color:black;layout-grid-mode:
both'>&nbsp;&nbsp;&nbsp;&nbsp; </span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black face=&#23435;&#20307;><span
lang=EN-US style='font-size:10.0pt;font-family:SimSun;color:black;layout-grid-mode:
both'>&nbsp;&nbsp;&nbsp;&nbsp; 1. Which one is rpf peer? A, B, C, or all of
them.</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black face=&#23435;&#20307;><span
lang=EN-US style='font-size:10.0pt;font-family:SimSun;color:black;layout-grid-mode:
both'>&nbsp;&nbsp;&nbsp;&nbsp; Suppose all of them forward the same SA message,
does the router accept all of them or only one?</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black face=&#23435;&#20307;><span
lang=EN-US style='font-size:10.0pt;font-family:SimSun;color:black;layout-grid-mode:
both'>&nbsp;&nbsp;&nbsp;&nbsp; </span></font></p>

<p class=MsoNormal style='text-indent:20.0pt;line-height:12.0pt'><font size=2
color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:10.0pt;
font-family:SimSun;color:black;layout-grid-mode:both'>2. If above RPF Peer preference
is A&gt;B&gt;C, What can we do if a SA is received from lower preferred RPF Peer
first and SA would be never received from the highest preferred RPF Peer because
of the highest one</span></font><font size=2 color=black><span lang=EN-US
style='font-size:10.0pt;color:black;layout-grid-mode:both'>&#8217;</span></font><font
size=2 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:
10.0pt;font-family:SimSun;color:black;layout-grid-mode:both'>s SA advertising policy.</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black face=&#23435;&#20307;><span
lang=EN-US style='font-size:10.0pt;font-family:SimSun;color:black;layout-grid-mode:
both'>&nbsp;</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black face=&#23435;&#20307;><span
lang=EN-US style='font-size:10.0pt;font-family:SimSun;color:black;layout-grid-mode:
both'>&nbsp;&nbsp;&nbsp;&nbsp; Thanks a lot.</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black face=&#23435;&#20307;><span
lang=EN-US style='font-size:10.0pt;font-family:SimSun;color:black;layout-grid-mode:
both'>&nbsp;</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black face=&#23435;&#20307;><span
lang=EN-US style='font-size:10.0pt;font-family:SimSun;color:black;layout-grid-mode:
both'>&nbsp;</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black face=&#23435;&#20307;><span
lang=EN-US style='font-size:10.0pt;font-family:SimSun;color:black;layout-grid-mode:
both'>&nbsp;</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><b><font
 size=2 color="#002041" face="Courier New"><span lang=EN-US style='font-size:
 10.0pt;font-family:"Courier New";color:#002041;layout-grid-mode:both;
 font-weight:bold'>10.1.3</span></font></b><b><font size=2 color="#002041"
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:#002041;layout-grid-mode:both;font-weight:bold'>.&nbsp; Peer-RPF Forwarding
Rules</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt'><b><font size=2 color="#002041"
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:#002041;layout-grid-mode:both;font-weight:bold'>&nbsp;</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;&nbsp; An SA message originated by R
and received by X from N is accepted if</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;&nbsp; N is the peer-RPF neighbor for
X, and is discarded otherwise.</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font><font size=2 color=black face="Courier New"><span lang=PT-BR
style='font-size:10.0pt;font-family:"Courier New";color:black;layout-grid-mode:
both'>MPP(R,N)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MP(N,X)</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=PT-BR style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; R
---------....-------&gt; N ------------------&gt; X</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=PT-BR style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SA(S,G,R)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SA(S,G,R)</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=PT-BR style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=PT-BR style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;&nbsp; </span></font><font size=2
color=black face="Courier New"><span lang=EN-US style='font-size:10.0pt;
font-family:"Courier New";color:black;layout-grid-mode:both'>MP(N,X) is an MSDP
peering between N and X.&nbsp; MPP(R,N) is an MSDP</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;&nbsp; peering path (zero or more MSDP
peers) between R and N, e.g.,</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;&nbsp; </span></font><font size=2
color=black face="Courier New"><span lang=PT-BR style='font-size:10.0pt;
font-family:"Courier New";color:black;layout-grid-mode:both'>MPP(R,N) = MP(R,
A) + MP(A, B) + MP(B, N).&nbsp; </span></font><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>SA(S,G,R) is an SA</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;&nbsp; message for source S on group G
originated by an RP R.</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><b><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp; The peer-RPF
neighbor N is chosen deterministically, using the first</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt'><b><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp; of the
following rules that matches.&nbsp; In particular, N is the RPF</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt'><b><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp; neighbor of X
with respect to R if</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt'><b><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;&nbsp; (i).&nbsp;&nbsp;&nbsp; N == R
(X has an MSDP peering with R).</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;&nbsp; (ii).&nbsp;&nbsp; N is the eBGP
NEXT_HOP of the Peer-RPF route for R.</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;&nbsp; (iii).&nbsp; The Peer-RPF route
for R is learned through a distance-vector</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
or path-vector routing protocol (e.g., BGP, RIP, DVMRP) and N</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
is the neighbor that advertised the Peer-RPF route for R</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
(e.g., N is the iBGP advertiser of the route for R), or N is</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
the IGP next hop for R if the route for R is learned via a</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
link-state protocol (e.g., OSPF [RFC2328] or IS-IS</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
[RFC1142]).</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;&nbsp; (iv).&nbsp;&nbsp; N resides in
the closest AS in the best path towards R.&nbsp; If</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
multiple MSDP peers reside in the closest AS, the peer with</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
the highest IP address is the rpf-peer.</span></font></p>

<p class=MsoNormal style='line-height:12.0pt'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 color=black face="Courier New"><span
lang=EN-US style='font-size:10.0pt;line-height:150%;font-family:"Courier New";
color:black;layout-grid-mode:both'>&nbsp;&nbsp; (v).&nbsp;&nbsp;&nbsp; N is
configured as the static RPF-peer for R.</span></font></p>

</div>

</body>

</html>

--Boundary_(ID_2uJJr7iP74ZDG/1rU8ZZSw)--


Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: pim@ietf.org
Delivered-To: pim@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id C5A7D28C13D; Tue, 17 Feb 2009 08:08:32 -0800 (PST)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <20090217160832.C5A7D28C13D@core3.amsl.com>
Date: Tue, 17 Feb 2009 08:08:32 -0800 (PST)
Cc: Internet Architecture Board <iab@iab.org>, pim chair <pim-chairs@tools.ietf.org>, pim mailing list <pim@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [pim] Protocol Action: 'The RPF Vector TLV' to Proposed Standard
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/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: Tue, 17 Feb 2009 16:08:32 -0000

The IESG has approved the following document:

- 'The RPF Vector TLV '
   <draft-ietf-pim-rpf-vector-08.txt> as a Proposed Standard

This document is the product of the Protocol Independent Multicast 
Working Group. 

The IESG contact persons are David Ward and Ross Callon.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pim-rpf-vector-08.txt

Technical Summary
This document describes a use of the PIM Join Attribute which enables PIM
to build multicast trees through an MPLS-enabled network, even if that
network's IGP does not have a route to the source of the  tree.

Working Group Summary

   No issues.

Document Quality

 There are multiple known implementations.

Personnel

   Dave Ward is shepherd.



Return-Path: <root@core3.amsl.com>
X-Original-To: pim@ietf.org
Delivered-To: pim@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 86BDB28C303; Thu, 26 Feb 2009 13:00:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090226210001.86BDB28C303@core3.amsl.com>
Date: Thu, 26 Feb 2009 13:00:01 -0800 (PST)
Cc: pim@ietf.org
Subject: [pim] I-D Action:draft-ietf-pim-sm-linklocal-07.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/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: Thu, 26 Feb 2009 21:00:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Protocol Independent Multicast Working Group of the IETF.


	Title           : Authentication and Confidentiality in PIM-SM Link-local Messages
	Author(s)       : W. Atwood, et al.
	Filename        : draft-ietf-pim-sm-linklocal-07.txt
	Pages           : 31
	Date            : 2009-02-26

RFC 4601 mandates the use of IPsec to ensure authentication of the
link-local messages in the Protocol Independent Multicast - Sparse
Mode (PIM-SM) routing protocol.  This document specifies mechanisms
to authenticate the PIM-SM link-local messages using the IP security
(IPsec) Encapsulating Security Payload (ESP) or (optionally) the
Authentication Header (AH).  It specifies optional mechanisms to
provide confidentiality using the ESP.  Manual keying is specified as
the mandatory and default group key management solution.  To deal
with issues of scalability and security that exist with manual
keying, an optional support for automated group key management
mechanism is provided.  However, the procedures for implementing
automated group key management are left to other documents.  This
document updates RFC 4601.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pim-sm-linklocal-07.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-pim-sm-linklocal-07.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-02-26125508.I-D@ietf.org>


--NextPart--
