Version Dated:   10/1/97

Merit GateD Consortium Agreement for Gold Members


This Agreement is made and entered into on this____________________ day of________________ between_________________________________________ (hereinafter referred to as "Gold Member") and Merit at the University of Michigan (hereinafter referred to as "Lead Institution"), acting for and on behalf of the Merit GateD Consortium (hereinafter referred to as "Consortium".) The Gold Member hereby joins the Consortium and shall be entitled to Consortium benefits and accepts the limitations and responsibilities herein.

1. Consortium Purpose

The Consortium is a group of institutions and corporations which provides ongoing support to expand the development of the GateD software, an implementation of several routing protocols as a daemon to run on various versions of Unix.

The Consortium will...

2. GateD Project

The Merit GateD project produces GateD (pronounced "gate-dee"), a software program which is used by individuals and organizations around the world. GateD is used as a platform for new network routing protocol prototyping and a source of routing protocol implementations for use in testing. The complete set of routing protocols and function provided by GateD can provide the core for development of future products.

3. Gold Membership Benefits

Gold Membership in the Consortium is open to all organizations interested in support of the development of routing protocols. The Consortium will provide the following benefits to Gold Members:

Technical

Consortium

4. Gold Membership Requirements

Gold Members shall make annual membership contributions to the Lead Institution of:

An "existing GateD member" is defined as a member who is current a member of the GateD Consortium in a product line as either a Gold member, a Commercial member, a Small Commercial member, a Service member, or a Small Member.

Gold members are GateD members for two product lines, and thus an existing Gold member is an "existing GateD member" for two product lines. If a Gold member wishes to renew the Gold membership and specify the same two (2) product lines, the cost is $45,000. If the Gold member wishes to select one (1) new product line and renew one (1) existing product line, the cost for the Gold membership is $75,000.

Membership for the categories Commercial, Small Commercial, Service, Small Service is a membership for a product line. Product lines are: GateD Unicast (Version 4), GateD Multicast (Version 5), and GateD IPv6 (Version 6). If a member wishes to upgrade to a Gold membership and the member is an "existing GateD member" in both of the two (2) product lines selected for Gold membership, the "existing GateD member" in one (1) of the product lines select for the Gold membership, the cost of the Gold membership is $75,000.

New Members who purchase a Gold Membership will receive
Two (2) Product Lines.

1st Year-

Product

Line 1

1st Year-

Product

Line 2

Extra

Benefits

Total

New Members

$50,000

$50,000

$10,000

$110,000

New Gold Members shall receive unlimited distribution of binaries for Two (2) Product Lines. Their membership fee also includes many other additonal benefits.

Renewal

of Product

Line 1

1st Year-

Product

Line 2

Extra

Benefits

Total

Existing Member in

One (1) Product Line

 

$15,000

$50,000

$10,000

$75,000

An existing GateD Member in a single product line who wants to become a Gold Member shall pay the Lead Institution a fee of $75,000. This will entitle them to unlimited distribution of binaries for Two (2) Product Lines. A Gold Membership fee includes their renewal fee, an additonal fee for the use of a 2nd Product Line, plus many other benefits.


An existing GateD Member who currently has Two (2) Product Lines
shall purchase a renewal membership for Product Line 1 and
Product Line 2 for $45,000.

Renewal

of Product

Line 1

Renewal

Product

Line 2

Extra

Benefits

Total

Existing Member in

Two (2) Product Lines

$15,000

$15,000

$15,000

$45,000

An existing GateD Member who currently receives unlimited distribution of binaries for Two (2) Product Lines shall pay the Lead Institution a fee of $45,000 for renewal of their Gold Membership. Gold Membership for existing members with Two (2) current Product Lines will include the addtitional Development Project for the Interns. (The training costs of these Interns account for the increase in the cost of the Additional Benefits.)




Upon execution of this Agreement, and during each year of paid-up membership, Members shall be entitled to the benefits of Consortium membership in accordance with the terms of this Agreement Membership contributions will be used to support the research and development of the programs and activities of the GateD Consortium.

Annual membership fees shall cover 12 months of Consortium participation commencing with execution of this Agreement. The Lead Institution shall consult with Members prior to implementing any change in membership fees, and shall provide Members ninety (90) days written notice prior to commencement of the membership period for which the fee change would take effect.

Membership fees shall become due to the Lead Institution upon execution of this Agreement. Checks shall be made payable to Merit and submitted to:

Merit GateD Consortium
Attn:  Michele Dotson 
Merit Network, Inc.
4251 Plymouth Rd, Suite C 
Ann Arbor, MI 48105-2785.

At its option, the Lead Institution may accept equipment or other in-kind contribution of an equivalent value to the membership fee in lieu of cash payment.

5. Use of Names

Neither party to this Agreement shall make use of this Agreement, or use the other's name or that of any member of the other's staff for purposes of advertising or promotion without prior written approval of the other party.

6. Publications

The parties to this Agreement shall have the right, at their discretion, to release written information or to publish material which they have developed under this Agreement, provided that information release or publication is given to the Lead Institution for distribution to or review by Members at Lead Institution's option. Members agree to provide an advance copy if so requested by Lead Institution.

7. GateD Copyright and Licensing

Background

The GateDaemon Project at Merit at the University of Michigan ("Merit") produces the GateD software, an implementation of several routing protocols as a daemon to run on various versions of Unix. GateDaemon was originated and developed through release 3.0 by Cornell University and its collaborators with funding from the National Science Foundation and other sources and with important contributions of code, testing, and documentation from a number of organizations. Merit has developed release 4.0, 5.0, and 6.0 as part of the Merit GateD consortium. Merit provides copies of GateD to Gold Members for:


Redistribution of GateD

Those who wish to redistribute GateD may do so under this agreement. Anyone wishing to may transfer GateD or any part of GateD to any third party. Third parties are not authorized to sublicense or further redistribute GateD or any part of GateD. Third parties wishing to do so may be referred to Merit for information concerning memberships and licensing.

Members are required to submit to Merit for distribution to the user community certain modifications and enhancements which they create or are created on their behalf using GateD. Such distribution of member-developed enhancements is for the benefit of the GateD user community and subject only to the GateD source file restrictions and, if applicable, to the appropriate GateD Redistribution License.

The organizations which have shared in the ongoing development of GateD have done so in part based on their confidence that others in the user community will contribute on the same terms. The requirement to share GateD enhancements, however, may conflict with an organization's effort to develop products for commercial use which may overlap GateD in function. The attached version of the GateD Redistribution License defines in greater detail the enhancements or modifications which are required to be returned for the benefit of the user community. As well, the agreement provides for certain cases which may be legitimately excluded from the requirement to return enhancements. GateD enhancements which entail third party proprietary materials, for example, are not required to be returned. Further, a provision has been added to allow a monetary contribution in lieu of return of particular enhancements. This provision allows GateD to be utilized in contexts which may become proprietary to a Member while ensuring that such use contributes to the continued development, enhancement, support, and public availability of the software.

Please note that Merit's continued ability to make GateD available to the research and academic community at the current fee structure is contingent upon the University's incurring no additional liability from Member's use of the software. Accordingly, the attached GateD Redistribution License holds Merit harmless from liability arising from Member's use of GateD under the agreement. As written, the scope of liability protection reserved by Merit is limited to only that which would not have arisen but for a Member's use of GateD. In addition, the indemnification of Merit is further qualified to exclude liability resulting from University negligence.

The rights conveyed to Members under this agreement for GateD Product Line 1 and Product
Line 2
are non-transferable.

Lead Institution provides copies of GateD upon request to Members and use as permitted by the copyright and subject to other restrictions contained in the GateD source files.

Those who wish to redistribute GateD may do so by becoming a member and executing a GateD Membership and Redistribution License with the Lead Institution.

8. GateD Redistribution

The Regents of the University of Michigan on behalf of its operating unit, Merit, (Merit) agrees to grant and does hereby grant to _____________ (Gold Member) a non-exclusive, non-transferable, royalty-free, worldwide, revocable license to use, reproduce, modify and redistribute the software entitled "Gateway Daemon, Product Line 1" and "Gateway Daemon, Product Line 2" (GateD) with Licensee's products, subject to the following terms:

9. Proprietary Information

The Consortium exists to continue development of GateD in an open, collaborative, non-proprietary environment in order to ensure its continued broad applicability and availability to the Internet community.

Accordingly, all Proprietary Information including proprietary research, trade secrets or other confidential or sensitive information should not be disclosed by Members under this Agreement nor in any way become embodied in or restrict the use of GateD-related software or Consortium materials.

10. Intellectual Property

The Consortium has been created to foster broad collaboration in the implementation of routing protocols. However, the Consortium may lead to interest in new areas of research or application. If so, such activities shall be pursued via separate agreements in order to establish the necessary collaborative and financial terms among the interested parties.

Discoveries which may be subject to intellectual property protection are not anticipated to arise from the Consortium activities under this Agreement. As a result, and to facilitate the freest possible exchange of information among Members, this Agreement conveys no intellectual property rights between the Lead Institution and Members.

11. Staff Agreements

Each Member shall, as a condition of its participation, represent and warrant that it has or shall obtain, prior to the commencement of Consortium activities under this Agreement, appropriate agreements with its employees/students or others who may participate in Consortium activities sufficient to ensure compliance with all the terms of this Agreement.

12. Term

The Agreement shall become effective upon execution of this Agreement and shall continue in force for additional one-year periods, subject to Gold Member's payment of annual membership fees at the level established for each membership year.

While this agreement is in force, the Gold Member is an "existing GateD member" for the product lines specified in this agreement. A "paid-up" membership in the GateD Consortium is membership in which the member has paid the annual membership fees for the one-year period.

Gold Member may terminate this Agreement upon sixty (60) days prior written notice to the Lead Institution. Upon such termination by member, all Member obligations and benefits shall cease.

The Lead Institution may terminate this Agreement upon sixty (60) days prior written notice to Member. In the event of termination by Lead Institution, Gold Member shall be refunded a pro-rata share of any fees paid for membership periods not concluded as of notice of termination. Upon such termination, all Member obligations and benefits shall cease.

13. Notices

All notices shall be in writing and effective upon receipt. Notices shall be sent to the following addresses:

Merit GateD Consortium
Attn:  Michele Dotson                                   (Tel) 313-763-6061
Merit Network, Inc.                                     (Fax) 313-647-3185
4251 Plymouth Road, Ste. C
Ann Arbor, MI 48105-2785








To Member:
Contractual                             Technical



















14. Survival of Terms

If the Merit GateD Consortium Project is terminated by Merit, the license to the GateD software granted herein will survive Merit. Merit may, at its sole discretion, negotiate with another entity to provide continued access to the modifications or enhancements of the source code for the modules listed in Appendix B.

15. Entire Agreement

This Agreement contains the entire agreement between the parties. No amendments or changes to this Agreement shall be effective unless made in writing and signed by authorized representatives of the parties hereto.

In Witness Whereof, the parties have caused these presents to be executed in duplicate on the dates indicated below.

Lead Institution                                Member



_________________________________________       ___________________________
                                        

                                        
_________________________________________       ___________________________
        Date                                    Date

Appendix A

GateD Copyright Notices

Copyright notices and other restrictions as they currently appear in the
GateD source files include one or more of the following: 

        Copyright (c) 1995 The Regents of the University of Michigan
        All rights reserved.
        Gate Daemon was originated and developed through release 3.0 by
        Cornell University and its collaborators.

THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

Royalty-free licenses to redistribute GateD Release 2 in whole or in part may
be obtained by writing to:

        Gate Daemon Project
        The University of Michigan
        Merit
        4251 Plymouth Road, Suite C
        Ann Arbor, MI 48105-2785
        (313)936-9430

GateD is based on Kirton's EGP, UC Berkeley's routing daemon (routed), and
DCN's HELLO routing Protocol.   Development of GateD has been supported in
part by the National Science Foundation.

Please forward bug fixes, enhancements and questions to the GateD mailing
list:  gated-bug@gated.merit.edu.

Cornell Authors: 
Jeffrey C. Honig  
Scott W. Brim 
Portions of this software may fall under the following copyrights:

        Copyright (c) 1988 Regents of the University of California.
        All rights reserved.

Redistribution and use in source and binary forms are permitted provided that
the above copyright notice and this paragraph are duplicated in all such forms
and that any documentation, advertising materials, and other materials related
to such distribution and use acknowledge that the software was developed by
the University of California, Berkeley.  The name of the University may not be
used to endorse or promote products derived from this software without
specific prior written permission.  THIS SOFTWARE IS PROVIDED "AS IS" AND
WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
         Copyright 1991 D.L.S. Associates

Permission to use, copy, modify, distribute, and sell this software and its
documentation for any purpose is hereby granted without fee, provided that the
above copyright notice appear in all copies and that both that copyright
notice and this permission notice appear in supporting documentation, and that
the name of D.L.S. not be used in advertising or publicity pertaining to
distribution of the software without specific, written prior permission. 
D.L.S. makes no representations about the suitability of this software for any
purpose.  It is provided "as is" without express or implied warranty.

D.L.S. DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL D.L.S. BE
LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION
OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

        Authors:  Robert Hagens and Dan Schuh


 
        U    U   M        M   DDDD     OOOOO  SSSSS  PPPPP   FFFFF
        U    U   MM MM   D      D     O         O  S              P        P 
F
        U    U   M   M  M  D      D     O         O     SSS     PPPPP   FFFF
        U    U   M   M  M  D      D     O         O             S   P 
    F
          UU     M   M  M  DDDD     OOOOO  SSSS     P             F

        Copyright 1989, 1990, 1991
        The University of Maryland, College Park, Maryland.
        All rights reserved.

The University of Maryland College Park ("UMCP") is the owner of all right,
title and interest in and to UMD OSPF (the "Software").  Permission to use,
copy and modify the Software and its documentation solely for non-commercial
purposes is granted subject to the following terms and conditions:

1.      This copyright notice and these terms shall appear in all copies of
the Software and its supporting documentation.

2.      The Software shall not be distributed, sold or used in any way in a
commercial product, without UMCP's prior written consent.

3.      The origin of this Software may not be misrepresented, either by
explicit claim or by omission.

4.      Modified or altered versions must be plainly marked as such, and must
not be misrepresented as being the original software.

5.      The Software is provided "AS IS".  User acknowledges that the Software
has been developed for research purposes only.  User agrees that use of the
Software is at user's own risk.  UMCP disclaims all warranties, express and
implied, including but not limited to, the implied warranties of
merchantability and fitness for a particular purpose.


Royalty-free licenses to redistribute UMD OSPF are available from the
University of Maryland, College Park.

        For details contact:

        Office of Technology Liaison
        4312 Knox Road
        University of Maryland
        College Park, Maryland  20742
        (301) 405-4209
        (301) 314-9871 (fax)

        This software was written by Rob Coltun.
        rcoltun@ni.umd.edu


Appendix B

Definition of an Enhancement for Unicast

Section 8-8 of these agreement specifies the Gold member Enhancements which are subject to this agreement. For the purpose of this agreement, we are further defining an "Enhancement" to the Unicast code as a group of source code modules that combined together either support:

  1. A routing protocol,
  2. A host protocol, and
  3. Unicast core code.

Unicast core code is defined as "non-protocol" code which includes gated task code, timer code, routing table, kernel handing, and interface handling. Multicast core code includes Multicast Border Router interface to kernel.

Light weight host-based protocols such as redirect, router-discovery will be included in the GateD core code. SNMP support is also included in the GateD core code. Substantial host based protocols such as DHCP will not be included in the GateD core code, but will listed as a unique protocol.

The following routing protocols are included in the GateD Unicast release

An option exists to purchase an older version of the DVMRP version 1 source which is no longer supported by GateD Multicast via the unicast source license.

If the Gold member decides to not return any enhancements for the GateD core code and all the protocol modules of the GateD source code, a total purchase plan will be available for $350,000. The Gold member may elect not to return a single enhancement, and return $50,000 to the Lead Institution of the Merit GateD Consortium to fund additional work.

Should the Gold member elect to purchase the GateD Unicast Core code, and develop new protocols or new modules for existing protocols which are not based on existing protocol modules, the new protocol modules would not be deemed an enhancement as defined by section 8-8 above. Any modules falling under this category will need to be reviewed by the the Lead Institution to determine if the work is indeed original. If the University via Lead Institution (Merit) determines that the code is not original work, the parties will appoint an independent arbitrator to review the code. If the arbitrator determines that the code is not an original work, the Gold member will pay Merit the $50,000 enhancement fee.

List of Modules Included in Each Category:

Unicast Core Code Modules

  1. checksum.c
  2. config.h
  3. defs.h
  4. gdc.c
  5. gii.c
  6. gii.h
  7. grand.c
  8. icmp.c
  9. icmp.h
  10. if.c
  11. if.h
  12. include.h
  13. inet.c
  14. inet.h
  15. iso.c
  16. iso.h
  17. ip_icmp.h
  18. krt.c
  19. krt.h
  20. krt_ifread_ioctl.c
  21. krt_ifread_kinfo.c
  22. krt_ipmulti.c
  23. krt_ipmulti.h
  24. krt_ipmulti_nocache.c
  25. krt_ipmulti_rtsock.c
  26. krt_ipmulti_ttl0.c
  27. krt_lladdr_kmem.c
  28. krt_lladdr_linux.c
  29. krt_lladdr_sioc.c
  30. krt_lladdr_sunos4.c
  31. krt_lladdr_sunos5.c
  32. krt_netopts.c
  33. krt_rt_ioctl.c
  34. krt_rt_sock.c
  35. krt_rtread_kinfo.c
  36. krt_rtread_kmem.c
  37. krt_rtread_proc.c
  38. krt_rtread_radix.c
  39. krt_rtread_sioc.c
  40. krt_rtread_sunos5.c
  41. krt_symbols_proc.c
  42. krt_symbols_sunos5.c
  43. krt_symbols_sysctl.c
  44. krt_var.h
  45. lexer.l
  46. parse.c
  47. parse.h
  48. parser.y
  49. paths.h
  50. policy.c
  51. policy.h
  52. rdisc.c
  53. rdisc.h
  54. rt_aggregate.c
  55. rt_mib.c
  56. rt_radix.c
  57. rt_redirect.c
  58. rt_static.c
  59. rt_table.c
  60. rt_table.h
  61. rt_var.h
  62. scram.c
  63. scram.h
  64. snmp_isode.c
  65. snmp_isode.h
  66. smi.my
  67. smi.defs
  68. mib.my
  69. mib.defs
  70. rt.my
  71. rt.defs
  72. gated.defs
  73. sockaddr.c
  74. sockaddr.h
  75. standalone.c
  76. str.c
  77. str.h
  78. targets.c
  79. targets.h
  80. task.c
  81. task.h
  82. trace.c
  83. trace.h
  84. unix.h
  85. compatiblity library sources which include
    1. herrs.c
    2. h_errno.c
    3. ffs.c
    4. flock.c
    5. inet_aton.c
    6. kvm.c
    7. setvbuf.c
    8. strcasecmp.c
    9. strerror.c
    10. sysconf.c
    11. unsetenv.c
    12. IETFBR14.c

bgp

  1. asmatch.c
  2. asmatch.h
  3. aspath.c
  4. aspath.h
  5. bgp.c
  6. bgp.h
  7. bgp_med.c
  8. bgp_mib.c
  9. bgp_proto.h
  10. bgp_rt.c
  11. bgp_sync.c
  12. bgp_var.h
  13. bgp.my
  14. bgp.defs
  15. rr_suppress.c
  16. rr_suppress.h

egp

  1. egp.c
  2. egp.h
  3. egp_init.c
  4. egp_mib.c
  5. egp_param.h
  6. egp_rt.c

Hello

  1. hello.c
  2. hello.h

isis

  1. isis.h
  2. isis_base.h
  3. isis_adjacency.c
  4. isis_circuit.c
  5. isis_common.c
  6. isis_dll.h
  7. isis_dual.c
  8. isis_events.c
  9. isis_flood.c
  10. isis_flood.h
  11. isis_gated_util.c
  12. isis_globals.c
  13. isis_globals.h
  14. isis_includes.h
  15. isis_lanhello.c
  16. isis_lsp.c
  17. isis_lsp.h
  18. isis_main.c
  19. isis_mib.c
  20. isis_mib.h
  21. isis_mib_tables.c
  22. isis_p2phello.c
  23. isis_parms.c
  24. isis_parseutil.c
  25. isis_pdus.h
  26. isis_pktdispatch.c
  27. isis_prototypes.h
  28. isis_rtrace.h
  29. isis_snp.c
  30. isis_spf.c
  31. isis_spf.h
  32. isis_spf_iter.c
  33. isis_spf_print.c
  34. isis_test.h
  35. isis_timer.c
  36. isis_troll.h
  37. isis_trollutil.c

rip

  1. rip.c
  2. rip.h
  3. rip_mib.c
  4. ripquery.c

current ospf

Please note the OSPF modules in "current" OSPF include the copyright based on the University of Maryland Copyright. Please note that the "new" OSPF modules only include the University of Michigan copyright.

  1. ospf_build_dbsum.c
  2. ospf_build_ls.c
  3. ospf_choose_dr.c
  4. ospf_conf.c
  5. ospf_flood.c
  6. ospf_gated.h
  7. ospf_gated_mem.h
  8. ospf_init.c
  9. ospf_log.c
  10. ospf_log.h
  11. ospf_lsdb.c
  12. ospf_lsdb.h
  13. ospf_mib.c
  14. ospf_monitor.c
  15. ospf_newq.c
  16. ospf_pkts.h
  17. ospf_rt.c
  18. ospf_rtab.c
  19. ospf_rtab.h
  20. ospf_rxlinkup.c
  21. ospf_rxmon.c
  22. ospf_rxpkt.c
  23. ospf_spf.c
  24. ospf_spf_leaves.c
  25. ospf_states.c
  26. ospf_timer_calls.h
  27. ospf_tqhandle.c
  28. ospf_trace.c
  29. ospf_txpkt.c
  30. ospf_monitor.c

"new" ospf

  1. new_ospf.c
  2. new_ospf.h
  3. new_ospf_ls.c
  4. new_ospf_ls.h
  5. new_ospf_exch.c
  6. new_ospf_spf.c
  7. new_ospf_tree.c
  8. new_ospf_trace.c
  9. ospf_monitor.c

slsp

  1. slsp_init.c
  2. slsp_io.c
  3. slsp_nbr.c
  4. slsp_rt.c
  5. slsp_db.c
  6. slsp.h
  7. slsp_var.h
  8. slsp_proto.h
  9. slsp_mib.c
  10. slsp.my
  11. slsp.defs

dvrmp

  1. dvrmp.c
  2. dvmrp.h
  3. dvmrp_targets.c
  4. dvmrp_targets.h

Appendix C


Definition of an Enhancement for Multicast

Section 8-8 of these agreement specifies the Gold member Enhancements which are subject to this agreement. For the purpose of this agreement, we are defining an "Enhancement"to the Multicast code as a group of source code modules that combined together either support:

  1. A routing protocol
  2. A host protocol , or,
  3. Multicast core code

Multicast core code s defined as "non-protocol" code which includes GateD task code, timer code, routing table, kernel handling, and interface handling. Multicast core code includes Multicast Border Router interface to kernel.

Light weight host-based protocols such as redirect, router-discovery will be included in the GateD core code. SNMP support is also included in the GateD core code. Substantial host based protocols such as DHCP will not be included in the GateD core code, but will listed as a unique protocol.

The following routing protocols are included in the GateD Multicast release:

  1. igmp
  2. dvmrp
  3. pim-sm
  4. pim-dm
  5. gum
  6. cbt
  7. bgp with multicasting

An option exists to purchase an older version of the DVMRP version 1 source which is no longer supported by GateD Multicast via the unicast source license.

If the Gold member decides to not return any enhancements for the GateD core code and all the protocol modules of the GateD source code, a total purchase plan will be available for $350,000. The Gold member may elect not to return a single enhancement, and return $50,000 to the Lead Institution of the Merit GateD Consortium to fund additional work.

Should the Gold member elect to purchase the GateD Multicast Core code, and develop new protocols or new modules for existing protocols which are not based on existing protocol modules, the new protocol modules would not be deemed an enhancement as defined by section 8-8 above. Any modules falling under this category will need to be reviewed by the the Lead Institution to determine if the work is indeed original. If the University via Lead Institution (Merit) determines that the code is not original work, the parties will appoint an independent arbitrator to review the code. If the arbitrator determines that the code is not an original work, the Gold member will pay Merit the $50,000 enhancement fee.


List of Modules Included in Each Category:

Multicast Core Code Modules

  1. checksum.c
  2. config.h
  3. defs.h
  4. gdc.c
  5. filter..c
  6. gii.c
  7. gii.h
  8. grand.c
  9. icmp.c
  10. icmp.h
  11. if.c
  12. if.h
  13. include.h
  14. inet.c
  15. inet.h
  16. inet_multi.c
  17. inet_multi.h
  18. iso.c
  19. iso.h
  20. ip_icmp.h
  21. krt.c
  22. krt.h
  23. krt_ifread_ioctl.c
  24. krt_ifread_kinfo.c
  25. krt_ipmulti.c
  26. krt_ipmulti.h
  27. krt_ipmulti_nocache.c
  28. krt_ipmulti_rtsock.c
  29. krt_ipmulti_ttl0.c
  30. krt_lladdr_hpstreams.c
  31. krt_lladdr_kmem.c
  32. krt_lladdr_linux.c
  33. krt_lladdr_sioc.c
  34. krt_lladdr_sunos4.c
  35. krt_lladdr_sunos5.c
  36. krt_netopts.c
  37. krt_rt_ioctl.c
  38. krt_rt_sock.c
  39. krt_rtread_hp10x.c
  40. krt_rtread_hpstreams.c
  41. krt_rtread_kinfo.c
  42. krt_rtread_kmem.c
  43. krt_rtread_proc.c
  44. krt_rtread_radix.c
  45. krt_rtread_sioc.c
  46. krt_rtread_sunos5.c
  47. krt_symbols_proc.c
  48. krt_symbols_sunos5.c
  49. krt_symbols_sysctl.c
  50. krt_var.h
  51. lexer.l
  52. mbr.c
  53. mbr.h
  54. mrt.c
  55. multicast_mib.c
  56. parse.c
  57. parse.h
  58. parser.y
  59. paths.h
  60. policy.c
  61. policy.h
  62. rdisc.c
  63. rdisc.h
  64. rt_aggregate.c
  65. rt_mib.c
  66. rt_radix.c
  67. rt_redirect.c
  68. rt_static.c
  69. rt_table.c
  70. rt_table.h
  71. rt_var.h
  72. scram.c
  73. scram.h
  74. snmp_cmu.c
  75. snmp_cmu.h
  76. sockaddr.c
  77. sockaddr.h
  78. stamp-h
  79. stamp-h.in
  80. standalone.c
  81. str.c
  82. str.h
  83. targets.c
  84. targets.h
  85. task.c
  86. task.h
  87. trace.c
  88. trace.h
  89. unix.h

m-bgp

  1. asmatch.c
  2. asmatch.h
  3. aspath.c
  4. aspath.h
  5. bgp.c
  6. bgp.h
  7. bgp_med.c
  8. bgp_mib.c
  9. bgp_proto.h
  10. bgp_rt.c
  11. bgp_sync.c
  12. bgp_var.h
  13. bgp.my
  14. bgp.defs
  15. rr_suppress.c
  16. rr_suppress.h

igmp

  1. igmp.c
  2. igmp.h
  3. igmp_mib.c

dvmrp

  1. dvmrp.c
  2. dvmrp.h
  3. dvmrp_routing.h
  4. dvmrp_targets.h
  5. dvmrp_targets.c

pim-sm

  1. pim.c
  2. pim.h
  3. pimsm.c
  4. pimsm.h
  5. pim_mib.c

pim-dm

  1. pimdm.c
  2. pimdm.h

cbt

  1. cbt.c
  2. cbt.h




    Appendix D

Definition of an Enhancement for IPv6

Section 8-8 of these agreement specifies the Gold member Enhancements which are subject to this agreement. For the purpose of this agreement, we are defining an "Enhancement"to the IPv6 code as a group of source code modules that combined together either support:

  1. A routing protocol
  2. A host protocol , or,
  3. IPv6 core code

IPv6 core code is defined as "non-protocol" code which includes GateD task code, timer code, routing table, kernel handling, and interface handling. IPv6 core code includes IPv6 Border Router interface to kernel.

Light weight host-based protocols such as redirect, router-discovery will be included in the GateD core code. SNMP support is also included in the GateD core code. Substantial host based protocols such as DHCPv6 will not be included in the GateD core code, but will listed as a unique protocol.

The following routing protocols are included in the GateD IPv6 release:

  1. RIPng
  2. ospf-v6
  3. bgp-4++
  4. idrpv6
  5. pim-sm (v6 additions)
  6. pim-dm (v6 additions)

If the Gold member decides to not return any enhancements for the GateD core code and all the protocol modules of the GateD source code, a total purchase plan will be available for $350,000. The Gold member may elect not to return a single enhancement, and return $50,000 to the Lead Institution of the Merit GateD Consortium to fund additional work.

Should the Gold member elect to purchase the GateD IPv6 Core code, and develop new protocols or new modules for existing protocols which are not based on existing protocol modules, the new protocol modules would not be deemed an enhancement as defined by section 8-8 above. Any modules falling under this category will need to be reviewed by the the Lead Institution to determine if the work is indeed original. If the University via Lead Institution (Merit) determines that the code is not original work, the parties will appoint an independent arbitrator to review the code. If the arbitrator determines that the code parties will appoint an independent arbitrator to review the code. If the arbitrator determines that the code is not an original work, the Gold member will pay Merit the $50,000 enhancement. fee.

List of Modules Included in Each Category:

IPv6 Core Code Modules

  1. checksum.c
  2. config.h  
  3. defs.h
  4. gdc.c
  5. filter..c
  6. gii.c
  7. gii.h
  8. grand.c
  9. icmp.c
  10. icmp.h
  11. if.c
  12. if.h
  13. include.h
  14. inet.c
  15. inet.h
  16. inet6.c
  17. inet6.h
  18. inet_multi.c
  19. inet_multi.h
  20. iso.c
  21. iso.h
  22. ip_icmp.h
  23. krt.c
  24. krt.h
  25. krt_ifread_ioctl.c
  26. krt_ifread_kinfo.c
  27. krt_ipmulti.c
  28. krt_ipmulti.h
  29. krt_ipmulti_nocache.c
  30. krt_ipmulti_rtsock.c
  31. krt_ipmulti_ttl0.c
  32. krt_lladdr_hpstreams.c
  33. krt_lladdr_kmem.c
  34. krt_lladdr_linux.c
  35. krt_lladdr_sioc.c
  36. krt_lladdr_sunos4.c
  37. krt_lladdr_sunos5.c
  38. krt_netopts.c
  39. krt_rt_ioctl.c
  40. krt_rt_sock.c
  41. krt_rtread_hp10x.c
  42. krt_rtread_hpstreams.c
  43. krt_rtread_kinfo.c
  44. krt_rtread_kmem.c
  45. krt_rtread_proc.c
  46. krt_rtread_radix.c
  47. krt_rtread_sioc.c
  48. krt_rtread_sunos5.c
  49. krt_symbols_proc.c
  50. krt_symbols_sunos5.c
  51. krt_symbols_sysctl.c
  52. krt_var.h
  53. lexer.l
  54. mbr.c
  55. mbr.h
  56. mrt.c
  57. multicast_mib.c
  58. parse.c
  59. parse.h
  60. parser.y
  61. paths.h
  62. policy.c
  63. policy.h
  64. rdisc.c
  65. rdisc.h
  66. rt_aggregate.c
  67. rt_mib.c
  68. rt_radix.c
  69. rt_redirect.c
  70. rt_static.c
  71. rt_table.c
  72. rt_table.h
  73. rt_var.h
  74. scram.c
  75. scram.h
  76. snmp_cmu.c
  77. snmp_cmu.h
  78. sockaddr.c
  79. sockaddr.h
  80. stamp-h
  81. stamp-h.in
  82. standalone.c
  83. str.c
  84. str.h
  85. targets.c
  86. targets.h
  87. task.c
  88. task.h
  89. trace.c
  90. trace.h
  91. unix.h

ripng

  1. ripng.h
  2. ripng_dump.c
  3. ripng_init.c
  4. ripng_internal.h
  5. ripng_recv.c
  6. ripng_send.c
  7. ripng_targets.c

bgp-4++

  1. asmatch.c
  2. asmatch.h
  3. aspath.c
  4. aspath.h
  5. bgp.c
  6. bgp.h
  7. bgp_med.c
  8. bgp_mib.c
  9. bgp_proto.h
  10. bgp_rt.c
  11. bgp_sync.c
  12. bgp_var.h
  13. bgp.my
  14. bgp.defs
  15. rr_suppress.c
  16. rr_suppress.h

ospf v2 with Multicast

  1. new_ospf.c
  2. new_ospf.h
  3. new_ospf_ls.c
  4. new_ospf_ls.h
  5. new_ospf_exch.c
  6. new_ospf_spf.c
  7. new_ospf_tree.c
  8. new_ospf_trace.c
  9. ospf_monitor.c

idrp

(supports ISO and IPv6)

  1. idrp.h
  2. idrp_proto_parse.h
  3. idrp_globals.h
  4. idrp_prototypes.h
  5. idrp_macros.h
  6. idrp_qos.h
  7. idrp_policy.h
  8. idrp_proto.h
  9. idrp.c
  10. idrp_attr_rec.c
  11. idrp_attrib.c
  12. idrp_dump.c
  13. idrp_events.c
  14. idrp_globals.c
  15. idrp_ps_print.c
  16. idrp_rt_phase3.c
  17. idrp_ps_rtmatch.c
  18. idrp_rt_phase_util.c
  19. idrp_ps_set.c
  20. idrp_rt_policy.c
  21. idrp_rdi_list.c
  22. idrp_rt_qos.c
  23. idrp_events.c
  24. idrp_init.c
  25. idrp_init_parse.c
  26. idrp_init_ribs.c
  27. idrp_init_sock.c
  28. idrp_parse_pdu.c
  29. idrp_out_list.c
  30. idrp_pdus.c
  31. idrp_policy.c
  32. idrp_ps_dstmatch.c
  33. idrp_ps_free.c
  34. idrp_rdpath.c
  35. idrp_ribs.c
  36. idrp_rt.c
  37. idrp_rt_ext_info.c
  38. idrp_rt_gated.c
  39. idrp_rt_iso.c
  40. idrp_rt_local.c
  41. idrp_rt_minadv.c
  42. idrp_rt_peer.c
  43. idrp_rt_phase1.c
  44. idrp_rt_phase2.c
  45. idrp_rt_phase3.c
  46. idrp_rt_ribs.c
  47. idrp_rt_util.c
  48. idrp_sock.c
  49. idrp_sm.c
  50. idrp_timers.c
  51. idrp_transport.c
  52. idrp_utils.c
  53. idrp_validate.c

igmp

  1. igmp.c
  2. igmp.h
  3. igmp_mib.c

dvmrp

  1. dvmrp.c
  2. dvmrp.h
  3. dvmrp_routing.h
  4. dvmrp_targets.h
  5. dvmrp_targets.c

pim-sm

  1. pim.c
  2. pim.h
  3. pimsm.c
  4. pimsm.h

cbt

  1. cbt.c
  2. cbt.h