Hello; I am new to Free Range Routing and I am trying to find a compliance statement so that I can compare the FRR stack with the stack that we are currently using but I can't seem to find anything on this topic. Can anyone out there point me to such a list? Thanks, Mike Mezeul Michael J. Mezeul Senior Director R&D ADVA Optical Networking Inc., NA 2301 North Greenville Avenue, Suite 300 Richardson, Texas 75082 T: +1 972.759.1216 F: +1 972.759.1201 M: +1 214.448.9239 mmezeul@advaoptical.com<mailto:mmezeul@advaoptical.com> www.advaoptical.com<http://www.advaoptical.com/>
Mike - Can you explain what you mean by `compliance statement`? donald On Mon, Aug 13, 2018 at 2:43 PM, Mike Mezeul <MMezeul@advaoptical.com> wrote:
Hello;
I am new to Free Range Routing and I am trying to find a compliance statement so that I can compare the FRR stack with the stack that we are currently using but I can’t seem to find anything on this topic.
Can anyone out there point me to such a list?
Thanks, Mike Mezeul
Michael J. Mezeul
Senior Director R&D
ADVA Optical Networking Inc., NA
2301 North Greenville Avenue, Suite 300
Richardson, Texas 75082
T: +1 972.759.1216
F: +1 972.759.1201
M: +1 214.448.9239
mmezeul@advaoptical.com
www.advaoptical.com
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
Compliant to RFC XYZ
On Aug 13, 2018, at 12:33, Donald Sharp <sharpd@cumulusnetworks.com> wrote:
Mike -
Can you explain what you mean by `compliance statement`?
donald
On Mon, Aug 13, 2018 at 2:43 PM, Mike Mezeul <MMezeul@advaoptical.com> wrote:
Hello;
I am new to Free Range Routing and I am trying to find a compliance statement so that I can compare the FRR stack with the stack that we are currently using but I can’t seem to find anything on this topic.
Can anyone out there point me to such a list?
Thanks, Mike Mezeul
Michael J. Mezeul
Senior Director R&D
ADVA Optical Networking Inc., NA
2301 North Greenville Avenue, Suite 300
Richardson, Texas 75082
T: +1 972.759.1216
F: +1 972.759.1201
M: +1 214.448.9239
mmezeul@advaoptical.com
www.advaoptical.com
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
Jeff - The documentation lists a bunch of supported RFC's http://docs.frrouting.org/en/latest/overview.html#system-architecture . But we really have not made a concerted effort to keep this list up to date at all. If someone were to spend time doing this and updating the documentation we would be greatly appreciative. Additionally on the frrouting.org website we have ANVL results of testing against the main protocols people are using. donald On Mon, Aug 13, 2018 at 5:25 PM, Jeff Tantsura <jefftant@gmail.com> wrote:
Compliant to RFC XYZ
On Aug 13, 2018, at 12:33, Donald Sharp <sharpd@cumulusnetworks.com> wrote:
Mike -
Can you explain what you mean by `compliance statement`?
donald
On Mon, Aug 13, 2018 at 2:43 PM, Mike Mezeul <MMezeul@advaoptical.com> wrote:
Hello;
I am new to Free Range Routing and I am trying to find a compliance statement so that I can compare the FRR stack with the stack that we are currently using but I can’t seem to find anything on this topic.
Can anyone out there point me to such a list?
Thanks, Mike Mezeul
Michael J. Mezeul
Senior Director R&D
ADVA Optical Networking Inc., NA
2301 North Greenville Avenue, Suite 300
Richardson, Texas 75082
T: +1 972.759.1216
F: +1 972.759.1201
M: +1 214.448.9239
mmezeul@advaoptical.com
www.advaoptical.com
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
Donald In telco world pretty much mandatory... an RFQ/RFI would always have this section, and depending on the services also MEF compliance On Tue, Aug 14, 2018 at 05:11 Donald Sharp <sharpd@cumulusnetworks.com> wrote:
Jeff -
The documentation lists a bunch of supported RFC's http://docs.frrouting.org/en/latest/overview.html#system-architecture . But we really have not made a concerted effort to keep this list up to date at all. If someone were to spend time doing this and updating the documentation we would be greatly appreciative.
Additionally on the frrouting.org website we have ANVL results of testing against the main protocols people are using.
donald
On Mon, Aug 13, 2018 at 5:25 PM, Jeff Tantsura <jefftant@gmail.com> wrote:
Compliant to RFC XYZ
On Aug 13, 2018, at 12:33, Donald Sharp <sharpd@cumulusnetworks.com> wrote:
Mike -
Can you explain what you mean by `compliance statement`?
donald
On Mon, Aug 13, 2018 at 2:43 PM, Mike Mezeul <MMezeul@advaoptical.com> wrote:
Hello;
I am new to Free Range Routing and I am trying to find a compliance statement so that I can compare the FRR stack with the stack that we are currently using but I can’t seem to find anything on this topic.
Can anyone out there point me to such a list?
Thanks, Mike Mezeul
Michael J. Mezeul
Senior Director R&D
ADVA Optical Networking Inc., NA
2301 North Greenville Avenue, Suite 300
Richardson, Texas 75082
T: +1 972.759.1216
F: +1 972.759.1201
M: +1 214.448.9239
mmezeul@advaoptical.com
www.advaoptical.com
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
Jeff - We are not a vendor selling support. If a vendor selling support wants to provide the legwork for a RFQ/RFI then they can. I see this as part of the value add here that they provide. You have to remember that for many years the documentation we had was in shambles, only in the last year have we put some serious effort into fixing it up. Quite frankly we still have a non-trivial amount of work here for a group of people who traditionally are not any good at this type of work( document writing ). If you or Mike(or anyone for that matter ) would like to spend time helping us in this regards how can I help make this happen? donald On Tue, Aug 14, 2018 at 11:53 AM, Jeff Tantsura <jefftant@gmail.com> wrote:
Donald
In telco world pretty much mandatory... an RFQ/RFI would always have this section, and depending on the services also MEF compliance
On Tue, Aug 14, 2018 at 05:11 Donald Sharp <sharpd@cumulusnetworks.com> wrote:
Jeff -
The documentation lists a bunch of supported RFC's http://docs.frrouting.org/en/latest/overview.html#system-architecture . But we really have not made a concerted effort to keep this list up to date at all. If someone were to spend time doing this and updating the documentation we would be greatly appreciative.
Additionally on the frrouting.org website we have ANVL results of testing against the main protocols people are using.
donald
On Mon, Aug 13, 2018 at 5:25 PM, Jeff Tantsura <jefftant@gmail.com> wrote:
Compliant to RFC XYZ
On Aug 13, 2018, at 12:33, Donald Sharp <sharpd@cumulusnetworks.com> wrote:
Mike -
Can you explain what you mean by `compliance statement`?
donald
On Mon, Aug 13, 2018 at 2:43 PM, Mike Mezeul <MMezeul@advaoptical.com> wrote:
Hello;
I am new to Free Range Routing and I am trying to find a compliance statement so that I can compare the FRR stack with the stack that we are currently using but I can’t seem to find anything on this topic.
Can anyone out there point me to such a list?
Thanks, Mike Mezeul
Michael J. Mezeul
Senior Director R&D
ADVA Optical Networking Inc., NA
2301 North Greenville Avenue, Suite 300
Richardson, Texas 75082
T: +1 972.759.1216
F: +1 972.759.1201
M: +1 214.448.9239
mmezeul@advaoptical.com
www.advaoptical.com
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
Donald, On Tue, 14 Aug 2018 at 18:15, Donald Sharp <sharpd@cumulusnetworks.com> wrote:
If you or Mike(or anyone for that matter ) would like to spend time helping us in this regards how can I help make this happen?
Do there exists a list of sections in the documentation we know is in the most serious need of being updated? I am asking. Because I know documentation writing is one thing I can help you with. If I have some general guide lines for which sections needs being updated.
Just off the top of my head: 1) Pretty much all command documentation is a simple `This does X` without any discussion of what the feature is trying to do. Actual work done to expand on what the commands are actually trying to do would be more than useful. 2) We are missing a non-trivial number of commands from the documentation. These need to be filled in at a `This does X` level of documentation at the very least (see #1, and this is especially true for BGP ) 3) EVPN is not well documented at all, this could use some serious help. 4) route-maps documentation should be cleaned up and consolidated across all daemons that use them, spelling out the supported sub commands on a per daemon basis 5) Deployment guides would be useful. 6) ripng does not have any documentation 7) OSPFv3 is missing large swaths of documentation donald On Tue, Aug 14, 2018 at 12:38 PM, Christoffer Hansen <netravnen@gmail.com> wrote:
Donald,
On Tue, 14 Aug 2018 at 18:15, Donald Sharp <sharpd@cumulusnetworks.com> wrote:
If you or Mike(or anyone for that matter ) would like to spend time helping us in this regards how can I help make this happen?
Do there exists a list of sections in the documentation we know is in the most serious need of being updated?
I am asking. Because I know documentation writing is one thing I can help you with. If I have some general guide lines for which sections needs being updated.
Hi Donald, On Tue, 14 Aug 2018 at 19:22, Donald Sharp <sharpd@cumulusnetworks.com> wrote:
1) Pretty much all command documentation is a simple `This does X` without any discussion of what the feature is trying to do. Actual work done to expand on what the commands are actually trying to do would be more than useful. 2) We are missing a non-trivial number of commands from the documentation. These need to be filled in at a `This does X` level of documentation at the very least (see #1, and this is especially true for BGP ) 3) EVPN is not well documented at all, this could use some serious help. 4) route-maps documentation should be cleaned up and consolidated across all daemons that use them, spelling out the supported sub commands on a per daemon basis 5) Deployment guides would be useful. 6) ripng does not have any documentation 7) OSPFv3 is missing large swaths of documentation
Hmm. Would it be possible I could document this in a project at https://github.com/FRRouting/frr/projects ? (And having edit access ONLY to relevant project concerning updating documentation)
Donald, I’m in no way suggesting what you should do, merely explaining meaning of what has been asked. It is however a good practice to document level of compliance to a standard at the time feature is being delivered, it is pain in the $$ to go thru code afterwords, trying to figure out, what has actually been implemented :-) Cheers, Jeff
On Aug 14, 2018, at 09:14, Donald Sharp <sharpd@cumulusnetworks.com> wrote:
Jeff -
We are not a vendor selling support. If a vendor selling support wants to provide the legwork for a RFQ/RFI then they can. I see this as part of the value add here that they provide. You have to remember that for many years the documentation we had was in shambles, only in the last year have we put some serious effort into fixing it up. Quite frankly we still have a non-trivial amount of work here for a group of people who traditionally are not any good at this type of work( document writing ). If you or Mike(or anyone for that matter ) would like to spend time helping us in this regards how can I help make this happen?
donald
On Tue, Aug 14, 2018 at 11:53 AM, Jeff Tantsura <jefftant@gmail.com> wrote:
Donald
In telco world pretty much mandatory... an RFQ/RFI would always have this section, and depending on the services also MEF compliance
On Tue, Aug 14, 2018 at 05:11 Donald Sharp <sharpd@cumulusnetworks.com> wrote:
Jeff -
The documentation lists a bunch of supported RFC's http://docs.frrouting.org/en/latest/overview.html#system-architecture . But we really have not made a concerted effort to keep this list up to date at all. If someone were to spend time doing this and updating the documentation we would be greatly appreciative.
Additionally on the frrouting.org website we have ANVL results of testing against the main protocols people are using.
donald
On Mon, Aug 13, 2018 at 5:25 PM, Jeff Tantsura <jefftant@gmail.com> wrote:
Compliant to RFC XYZ
On Aug 13, 2018, at 12:33, Donald Sharp <sharpd@cumulusnetworks.com> wrote:
Mike -
Can you explain what you mean by `compliance statement`?
donald
On Mon, Aug 13, 2018 at 2:43 PM, Mike Mezeul <MMezeul@advaoptical.com> wrote:
Hello;
I am new to Free Range Routing and I am trying to find a compliance statement so that I can compare the FRR stack with the stack that we are currently using but I can’t seem to find anything on this topic.
Can anyone out there point me to such a list?
Thanks, Mike Mezeul
Michael J. Mezeul
Senior Director R&D
ADVA Optical Networking Inc., NA
2301 North Greenville Avenue, Suite 300
Richardson, Texas 75082
T: +1 972.759.1216
F: +1 972.759.1201
M: +1 214.448.9239
mmezeul@advaoptical.com
www.advaoptical.com
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
Hi Don; Thanks for your feedback. Right now we're still in the assessment phase and thus that's why I was interested in the compliance. Should we decide to move forward with FRR then perhaps at that time we could look to see what contributions we might be able to make in this area. Thanks, Mike -----Original Message----- From: Donald Sharp <sharpd@cumulusnetworks.com> Sent: Tuesday, August 14, 2018 11:15 AM To: Jeff Tantsura <jefftant@gmail.com> Cc: Mike Mezeul <MMezeul@advaoptical.com>; dev@lists.frrouting.org Subject: Re: [dev] RFC compliance Jeff - We are not a vendor selling support. If a vendor selling support wants to provide the legwork for a RFQ/RFI then they can. I see this as part of the value add here that they provide. You have to remember that for many years the documentation we had was in shambles, only in the last year have we put some serious effort into fixing it up. Quite frankly we still have a non-trivial amount of work here for a group of people who traditionally are not any good at this type of work( document writing ). If you or Mike(or anyone for that matter ) would like to spend time helping us in this regards how can I help make this happen? donald On Tue, Aug 14, 2018 at 11:53 AM, Jeff Tantsura <jefftant@gmail.com> wrote:
Donald
In telco world pretty much mandatory... an RFQ/RFI would always have this section, and depending on the services also MEF compliance
On Tue, Aug 14, 2018 at 05:11 Donald Sharp <sharpd@cumulusnetworks.com> wrote:
Jeff -
The documentation lists a bunch of supported RFC's http://docs.frrouting.org/en/latest/overview.html#system-architecture . But we really have not made a concerted effort to keep this list up to date at all. If someone were to spend time doing this and updating the documentation we would be greatly appreciative.
Additionally on the frrouting.org website we have ANVL results of testing against the main protocols people are using.
donald
On Mon, Aug 13, 2018 at 5:25 PM, Jeff Tantsura <jefftant@gmail.com> wrote:
Compliant to RFC XYZ
On Aug 13, 2018, at 12:33, Donald Sharp <sharpd@cumulusnetworks.com> wrote:
Mike -
Can you explain what you mean by `compliance statement`?
donald
On Mon, Aug 13, 2018 at 2:43 PM, Mike Mezeul <MMezeul@advaoptical.com> wrote:
Hello;
I am new to Free Range Routing and I am trying to find a compliance statement so that I can compare the FRR stack with the stack that we are currently using but I can’t seem to find anything on this topic.
Can anyone out there point me to such a list?
Thanks, Mike Mezeul
Michael J. Mezeul
Senior Director R&D
ADVA Optical Networking Inc., NA
2301 North Greenville Avenue, Suite 300
Richardson, Texas 75082
T: +1 972.759.1216
F: +1 972.759.1201
M: +1 214.448.9239
mmezeul@advaoptical.com
www.advaoptical.com
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
Thanks a bunch for this info Jeff. Can you please send me the link to the ANVL test results? Thanks, Mike -----Original Message----- From: Donald Sharp <sharpd@cumulusnetworks.com> Sent: Tuesday, August 14, 2018 7:11 AM To: Jeff Tantsura <jefftant@gmail.com> Cc: Mike Mezeul <MMezeul@advaoptical.com>; dev@lists.frrouting.org Subject: Re: [dev] RFC compliance Jeff - The documentation lists a bunch of supported RFC's http://docs.frrouting.org/en/latest/overview.html#system-architecture . But we really have not made a concerted effort to keep this list up to date at all. If someone were to spend time doing this and updating the documentation we would be greatly appreciative. Additionally on the frrouting.org website we have ANVL results of testing against the main protocols people are using. donald On Mon, Aug 13, 2018 at 5:25 PM, Jeff Tantsura <jefftant@gmail.com> wrote:
Compliant to RFC XYZ
On Aug 13, 2018, at 12:33, Donald Sharp <sharpd@cumulusnetworks.com> wrote:
Mike -
Can you explain what you mean by `compliance statement`?
donald
On Mon, Aug 13, 2018 at 2:43 PM, Mike Mezeul <MMezeul@advaoptical.com> wrote:
Hello;
I am new to Free Range Routing and I am trying to find a compliance statement so that I can compare the FRR stack with the stack that we are currently using but I can’t seem to find anything on this topic.
Can anyone out there point me to such a list?
Thanks, Mike Mezeul
Michael J. Mezeul
Senior Director R&D
ADVA Optical Networking Inc., NA
2301 North Greenville Avenue, Suite 300
Richardson, Texas 75082
T: +1 972.759.1216
F: +1 972.759.1201
M: +1 214.448.9239
mmezeul@advaoptical.com
www.advaoptical.com
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
ANVL test results are on the frrouting.org website. You can grab them from there. donald On Wed, Aug 15, 2018 at 12:05 PM, Mike Mezeul <MMezeul@advaoptical.com> wrote:
Thanks a bunch for this info Jeff. Can you please send me the link to the ANVL test results?
Thanks, Mike
-----Original Message----- From: Donald Sharp <sharpd@cumulusnetworks.com> Sent: Tuesday, August 14, 2018 7:11 AM To: Jeff Tantsura <jefftant@gmail.com> Cc: Mike Mezeul <MMezeul@advaoptical.com>; dev@lists.frrouting.org Subject: Re: [dev] RFC compliance
Jeff -
The documentation lists a bunch of supported RFC's http://docs.frrouting.org/en/latest/overview.html#system-architecture . But we really have not made a concerted effort to keep this list up to date at all. If someone were to spend time doing this and updating the documentation we would be greatly appreciative.
Additionally on the frrouting.org website we have ANVL results of testing against the main protocols people are using.
donald
On Mon, Aug 13, 2018 at 5:25 PM, Jeff Tantsura <jefftant@gmail.com> wrote:
Compliant to RFC XYZ
On Aug 13, 2018, at 12:33, Donald Sharp <sharpd@cumulusnetworks.com> wrote:
Mike -
Can you explain what you mean by `compliance statement`?
donald
On Mon, Aug 13, 2018 at 2:43 PM, Mike Mezeul <MMezeul@advaoptical.com> wrote:
Hello;
I am new to Free Range Routing and I am trying to find a compliance statement so that I can compare the FRR stack with the stack that we are currently using but I can’t seem to find anything on this topic.
Can anyone out there point me to such a list?
Thanks, Mike Mezeul
Michael J. Mezeul
Senior Director R&D
ADVA Optical Networking Inc., NA
2301 North Greenville Avenue, Suite 300
Richardson, Texas 75082
T: +1 972.759.1216
F: +1 972.759.1201
M: +1 214.448.9239
mmezeul@advaoptical.com
www.advaoptical.com
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
participants (5)
-
Christoffer Hansen -
Donald Sharp -
Jeff Tantsura -
Mike Mezeul -
netravnen＠gmail.com