Arnab Bakshi | 2 Feb 2009 03:07
Picon

Arnab Bakshi sent you a Friend Request on Yaari

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 <at> yaari.com.
Yaari LLC, 358 Angier Ave, Atlanta, GA 30312

YaariIVH153MGA329NXO138SIK492

_______________________________________________
pim mailing list
pim <at> ietf.org
https://www.ietf.org/mailman/listinfo/pim
Internet-Drafts | 4 Feb 2009 19:30
Picon
Favicon

I-D Action:draft-ietf-pim-sm-linklocal-06.txt

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.
Attachment (draft-ietf-pim-sm-linklocal-06.txt): message/external-body, 70 bytes
_______________________________________________
pim mailing list
pim <at> ietf.org
https://www.ietf.org/mailman/listinfo/pim
Arnab Bakshi | 5 Feb 2009 03:08
Picon

Reminder: Please Respond to Arnab's Invitation

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 <at> yaari.com.
Yaari LLC, 358 Angier Ave, Atlanta, GA 30312

YaariIVH153MGA329NXO138SIK492

_______________________________________________
pim mailing list
pim <at> ietf.org
https://www.ietf.org/mailman/listinfo/pim
Su Haiyang | 9 Feb 2009 03:49
Favicon

A doubt regarding about MSDP RPF rule

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 ones 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.

_______________________________________________
pim mailing list
pim <at> ietf.org
https://www.ietf.org/mailman/listinfo/pim
The IESG | 17 Feb 2009 17:08
Picon
Favicon

Protocol Action: 'The RPF Vector TLV' to Proposed Standard

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.
Internet-Drafts | 26 Feb 2009 22:00
Picon
Favicon

I-D Action:draft-ietf-pim-sm-linklocal-07.txt

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.
Attachment (draft-ietf-pim-sm-linklocal-07.txt): message/external-body, 70 bytes
_______________________________________________
pim mailing list
pim <at> ietf.org
https://www.ietf.org/mailman/listinfo/pim
Stig Venaas | 3 Mar 2009 07:42
Picon
Picon

pim wg last call on draft-ietf-pim-sm-linklocal-07

This message announces a pim wg last call on "Authentication and
Confidentiality in PIM-SM Link-local Messages"
<draft-ietf-pim-sm-linklocal-07.txt>.
The last call will conclude at 1700 UTC on Tue, 2009-03-17.

Please respond to this wg last call.  If you support acceptance of the
document without change, respond with a simple acknowledgment, so that
support for the document can be assessed.  Lack of discussion does not
represent positive support.

The draft is available at
http://www.ietf.org/internet-drafts/draft-ietf-pim-sm-linklocal-07.txt

Stig

Gmane