From ashishkarpe at gmail.com Sun Sep 24 13:10:55 2006 From: ashishkarpe at gmail.com (Ashish Karpe) Date: Mon, 25 Sep 2006 01:40:55 +0530 Subject: [Xorp-hackers] Want to contribute !!!!! Message-ID: Hi all, we are team of 4 members doing our Engineering project (Academic Project). So we want to contribute to this project !!! Is PIM-BIDIR & Anycast-RP been implemented in XORP ? If not can it be done ? If we give this support to Xorp how much will it be benificial for Xorp project ? please reply , ashish From kristian at spritelink.se Sun Sep 24 23:38:44 2006 From: kristian at spritelink.se (Kristian Larsson) Date: Mon, 25 Sep 2006 08:38:44 +0200 Subject: [Xorp-hackers] Want to contribute !!!!! In-Reply-To: References: Message-ID: <20060925063843.GA20336@spritelink.se> On Mon, Sep 25, 2006 at 01:40:55AM +0530, Ashish Karpe wrote: > Hi all, > we are team of 4 members doing our Engineering project > (Academic Project). So we want to contribute to this project !!! > Is PIM-BIDIR & Anycast-RP been implemented in XORP ? If > not can it be done ? If we give this support to Xorp how much will it > be benificial for Xorp project ? No, neither BIDIR-PIM or Anycasted RPs are implemented in XORP today but it certainly can be done. If you look at http://www.xorp.org/roadmap.html you may see that BIDIR-PIM is on the roadmap for early 2007. I don't think that's a realistic goal as the work on OSPFv3 hasn't started yet (please correct me if I'm wrong) with about a month to go. Anyway, the project sure needs a few extra hands so if you're willing, go right ahead. It's hard to approximate just how much XORP may benefit from this, it's kinda up to you :) A step on the way towards Anycasted RPs would be adding MSDP support, for which I just added a bug yesterday to the BugZilla. I recommend reading the papers at http://www.xorp.org/design_docs.html before getting to work :) Regards, Kristian. -- Kristian Larsson KLL-RIPE Network Engineer Net at Once [AS35706] +46 704 910401 kristian at spritelink.se From pavlin at icir.org Mon Sep 25 17:10:10 2006 From: pavlin at icir.org (Pavlin Radoslavov) Date: Mon, 25 Sep 2006 17:10:10 -0700 Subject: [Xorp-hackers] Want to contribute !!!!! In-Reply-To: Message from Kristian Larsson of "Mon, 25 Sep 2006 08:38:44 +0200." <20060925063843.GA20336@spritelink.se> Message-ID: <200609260010.k8Q0AAOk057023@possum.icir.org> Kristian Larsson wrote: > On Mon, Sep 25, 2006 at 01:40:55AM +0530, Ashish Karpe wrote: > > Hi all, > > we are team of 4 members doing our Engineering project > > (Academic Project). So we want to contribute to this project !!! > > Is PIM-BIDIR & Anycast-RP been implemented in XORP ? If > > not can it be done ? If we give this support to Xorp how much will it > > be benificial for Xorp project ? > No, neither BIDIR-PIM or Anycasted RPs are > implemented in XORP today but it certainly can be > done. > If you look at http://www.xorp.org/roadmap.html > you may see that BIDIR-PIM is on the roadmap for > early 2007. I don't think that's a realistic goal > as the work on OSPFv3 hasn't started yet (please > correct me if I'm wrong) with about a month to go. > Anyway, the project sure needs a few extra hands > so if you're willing, go right ahead. It's hard to > approximate just how much XORP may benefit from > this, it's kinda up to you :) > > A step on the way towards Anycasted RPs would be > adding MSDP support, for which I just added a bug > yesterday to the BugZilla. > I recommend reading the papers at > http://www.xorp.org/design_docs.html before > getting to work :) Indeed, currently XORP doesn't have Bidir PIM-SM and Anycast-RP support, but as Kristian mentions above we are planning to implement them anyway. However, I would advice against taking on the task of implementing Bidir-PIM or Anycast-RP. Both mechanisms require detailed understanding of the PIM-SM internals (as implemented in XORP), and lots of your effort might be spent reading the source code or doing things are not very productive from the perspective of your project (e.g., making sure that your implementation logic is consistent with the PIM-SM internals, coding style, etc). Instead, I'd recommend that you consider implementing MSDP, because it is not on our TODO list. By doing so, you will have much more freedom (and fun :) designing the implementatation on your own, and at the end you will learn much more about protocol implementation. Pavlin From kristian at spritelink.se Mon Sep 25 22:55:26 2006 From: kristian at spritelink.se (Kristian Larsson) Date: Tue, 26 Sep 2006 07:55:26 +0200 Subject: [Xorp-hackers] Want to contribute !!!!! In-Reply-To: <200609260010.k8Q0AAOk057023@possum.icir.org> References: <20060925063843.GA20336@spritelink.se> <200609260010.k8Q0AAOk057023@possum.icir.org> Message-ID: <20060926055525.GG20336@spritelink.se> On Mon, Sep 25, 2006 at 05:10:10PM -0700, Pavlin Radoslavov wrote: > However, I would advice against taking on the task of implementing > Bidir-PIM or Anycast-RP. Both mechanisms require detailed > understanding of the PIM-SM internals (as implemented in XORP), and > lots of your effort might be spent reading the source code or doing > things are not very productive from the perspective of your project > (e.g., making sure that your implementation logic is consistent with > the PIM-SM internals, coding style, etc). Forgive me if I'm wrong, I have little or no understanding of MSDP / PIMs internals, but isn't Anycast RP just normal PIM with MSDP configured between your RPs? I've configured it a few times but never bothered figuring out how it actually works but I reckon it's no different than two ASs talking MSDP between each other, this time it's just Intra-AS. So do you actually need to do modifications to the PIM stack to allow anycast RPs? Perhaps I should go read som RFCs ;) > Instead, I'd recommend that you consider implementing MSDP, because > it is not on our TODO list. By doing so, you will have much more > freedom (and fun :) designing the implementatation on your own, > and at the end you will learn much more about protocol > implementation. I second that, since the XORP development team hasn't this on the TODO it will probably take some time before it ends up on their TODO and when it does it'll probably end up last anyway since there are other more "important" goals (such as IS-IS, to which I fully agree should be more prioritzed than MSDP). Regards, Kristian. -- Kristian Larsson KLL-RIPE Network Engineer Net at Once [AS35706] +46 704 910401 kristian at spritelink.se From pavlin at icir.org Tue Sep 26 00:20:50 2006 From: pavlin at icir.org (Pavlin Radoslavov) Date: Tue, 26 Sep 2006 00:20:50 -0700 Subject: [Xorp-hackers] Want to contribute !!!!! In-Reply-To: Message from Kristian Larsson of "Tue, 26 Sep 2006 07:55:26 +0200." <20060926055525.GG20336@spritelink.se> Message-ID: <200609260720.k8Q7KoI2060628@possum.icir.org> > > However, I would advice against taking on the task of implementing > > Bidir-PIM or Anycast-RP. Both mechanisms require detailed > > understanding of the PIM-SM internals (as implemented in XORP), and > > lots of your effort might be spent reading the source code or doing > > things are not very productive from the perspective of your project > > (e.g., making sure that your implementation logic is consistent with > > the PIM-SM internals, coding style, etc). > Forgive me if I'm wrong, I have little or no > understanding of MSDP / PIMs internals, but isn't > Anycast RP just normal PIM with MSDP configured > between your RPs? > I've configured it a few times but never bothered > figuring out how it actually works but I reckon > it's no different than two ASs talking MSDP > between each other, this time it's just Intra-AS. > So do you actually need to do modifications to the > PIM stack to allow anycast RPs? > Perhaps I should go read som RFCs ;) Probably what you have in mind is RFC 3446: "Anycast Rendevous Point (RP) mechanism using Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP)". This solution eventually requires minor (if any) additional coding/changes (if you have PIM-SM and MSDP implemented of course). What I had in mind with regard to Anycast RP is RFC 4610: "Anycast-RP Using Protocol Independent Multicast (PIM)". This solution requires changes to the PIM-SM implementation itself, but does not need/use MSDP. Regards, Pavlin From kristian at spritelink.se Tue Sep 26 00:45:06 2006 From: kristian at spritelink.se (Kristian Larsson) Date: Tue, 26 Sep 2006 09:45:06 +0200 Subject: [Xorp-hackers] Want to contribute !!!!! In-Reply-To: <200609260720.k8Q7KoI2060628@possum.icir.org> References: <20060926055525.GG20336@spritelink.se> <200609260720.k8Q7KoI2060628@possum.icir.org> Message-ID: <20060926074505.GH20336@spritelink.se> On Tue, Sep 26, 2006 at 12:20:50AM -0700, Pavlin Radoslavov wrote: > > > > However, I would advice against taking on the task of implementing > > > Bidir-PIM or Anycast-RP. Both mechanisms require detailed > > > understanding of the PIM-SM internals (as implemented in XORP), and > > > lots of your effort might be spent reading the source code or doing > > > things are not very productive from the perspective of your project > > > (e.g., making sure that your implementation logic is consistent with > > > the PIM-SM internals, coding style, etc). > > Forgive me if I'm wrong, I have little or no > > understanding of MSDP / PIMs internals, but isn't > > Anycast RP just normal PIM with MSDP configured > > between your RPs? > > I've configured it a few times but never bothered > > figuring out how it actually works but I reckon > > it's no different than two ASs talking MSDP > > between each other, this time it's just Intra-AS. > > So do you actually need to do modifications to the > > PIM stack to allow anycast RPs? > > Perhaps I should go read som RFCs ;) > > Probably what you have in mind is RFC 3446: > "Anycast Rendevous Point (RP) mechanism using Protocol Independent > Multicast (PIM) and Multicast Source Discovery Protocol (MSDP)". That's the one. > This solution eventually requires minor (if any) additional > coding/changes (if you have PIM-SM and MSDP implemented of course). > What I had in mind with regard to Anycast RP is RFC 4610: > "Anycast-RP Using Protocol Independent Multicast (PIM)". > This solution requires changes to the PIM-SM implementation itself, > but does not need/use MSDP. Aha! :) Got some RFC catching up to do then ;) Thanks Regards, Kristian -- Kristian Larsson KLL-RIPE Network Engineer Net at Once [AS35706] +46 704 910401 kristian at spritelink.se