tech-net archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: SoC 2009 Ayame MPLS

>the ldp at least is not fully RFC compliant
Why? In RFC5462 contained information about EXP field(on cisco it like
CoS), it's quality of service stuff switching labels via priority
traffic on top level like udp, tcp, http,... To implement that thing
on NetBSD it's quite hardwork:), I think. Because it needs use
pf-hooks so as to permit label in firewall and altq via queue cbq
frame prioriting. Or you mean something else?

On 05/03/2009, Mihai Chelaru <> wrote:
> basteon wrote:
>> g'day,
>> I'm a student from Russia. I've a tiny bit kernel-development for
>> netbsd, but not complete yet, it would be support new fxo hardware on
>> zaptel driver. And I would be to assist implement mpls stack into
>> NetBSD on Google SoC 2009 or it's not priority project? I can testing
>> it with cisco hardware.
> Hi,
> I think "implementing MPLS" sounds too generic and you have to refine
> your goals.
> Also, starting from Ayame implementation (I'd sugest you to stay away
> from Ayame btw), I wrote a small implementation [1] containing an
> in-kernel label switch engine and an userland ldp daemon. Although it's
> not nearly finished (the ldp at least is not fully RFC compliant) it
> enabled NetBSD to act as an LSR (including Edge-LSR) both in tests and
> production first interacting with Cisco routers but then tested against
> Juniper routers, too. It's a little rotten, patches are against -current
> from one year ago but integrating them into today HEAD should be trivial.
> At that time, there were some concerns regarding this approach, most
> notably the interaction and mixing between MPLS and IP stacks, so I
> suggest you write a new design and _DISCUSS_ it on tech-net@ prior to
> start coding.
> Hope I didn't discourage you :)
> [1] -
> --
> Mihai

Home | Main Index | Thread Index | Old Index