From pim-bounces@ietf.org Sun Feb 1 18:07:28 2009 Return-Path: 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 ; 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 ; 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 ; 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 Message-ID: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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? Yes, Arnab is my friend! No, Arnab isn't my friend. Please respond or Arnab may think you said no :( Thanks, The Yaari Team ____ If you prefer not to receive this email tell us here. 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!

Is Arnab your friend?

Yes, Arnab is my friend! No, Arnab isn't my friend.

Please respond or Arnab may think you said no :(

Thanks,
The Yaari Team
____
If you prefer not to receive this email tell us here. 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-- --===============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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: 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 ; 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 ; 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 ; 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 Message-ID: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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? Yes, Arnab is my friend! No, Arnab isn't my friend. Please respond or Arnab may think you said no :( Thanks, The Yaari Team ____ If you prefer not to receive this email tell us here. 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!

Is Arnab your friend?

Yes, Arnab is my friend! No, Arnab isn't my friend.

Please respond or Arnab may think you said no :(

Thanks,
The Yaari Team
____
If you prefer not to receive this email tell us here. 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-- Return-Path: 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 ; 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 ; 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 ; 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 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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

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)-- Return-Path: 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 To: IETF-Announce Message-Id: <20090217160832.C5A7D28C13D@core3.amsl.com> Date: Tue, 17 Feb 2009 08:08:32 -0800 (PST) Cc: Internet Architecture Board , pim chair , pim mailing list , RFC Editor 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2009 16:08:32 -0000 The IESG has approved the following document: - 'The RPF Vector TLV ' 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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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--