Re: IGMPv3 (was Re: pim6sd)

From: SUZUKI Shinsuke (suz_at_kame.net)
Date: 04/29/04

  • Next message: SUZUKI Shinsuke: "Re: pim6sd"
    Date: Thu, 29 Apr 2004 14:12:02 +0900
    To: aswan@cs.berkeley.edu
    
    

    >>>>> On Wed, 28 Apr 2004 13:49:52 -0700
    >>>>> aswan@cs.berkeley.edu(Andrew Swan) said:

    > as of last fall, kame was waiting for the igmpv3 sockets api to
    > be published as an rfc (it was an internet-draft at the time) to
    > merge igmpv3 into the core bsd distributions.
    > (see http://www.kame.net/roadmap-2003.html).
    >
    > in january, the api draft was published as rfc 3678. what is
    > the process by which code is merged from kame to freebsd? is
    > it just a matter of somebody extracting the appropriate patches
    > and submitting them?

    I know MSF API has been published as an RFC, but I have to wait until
    the IPR issue raised by Apple has been closed, because Apple requires
    some fee for SSM-related implementations, which is against
    BSD-license.
            http://www.ietf.org/ietf/IPR/APPLE-SSM.txt

    I'm not sure if this IPR is really valid or this IPR is applicable to
    IGMPv3/MLDv2, but I think it's dangerous to MFC IGMPv3/MLDv2 without
    any clarification.

    As far as I know some Apple engineers have been aware of the issue,
    but I don't know if Apple's legal staffs know it.
    I really hope that this issue has been peacefully solved...

    _______________________________________________
    freebsd-net@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-net
    To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"


  • Next message: SUZUKI Shinsuke: "Re: pim6sd"

    Relevant Pages

    • Re: Query a DNS in C
      ... |> Can anyone point any explicit doc, or the ... in RFC 1035) and lets the caller use a simple API to send queries and read ... Whether that API would simply be a "build and breakdown" API ... for DNS datagrams, or a more sophisticated system that waits for multiple ...
      (comp.unix.programmer)
    • Re: AES_128 in RFC 4493
      ... I find that there is an API called as AES_128. ... used in the RFC 4493. ... i am unable to find the source code for AES_128 in the RFC 4493. ... The call AES_128(k, in, out) is pseudo code for AES - if you want to use the ...
      (sci.crypt)
    • Re: AES_128 in RFC 4493
      ... > In the RFC 4493, i find the source code in C language for AEC CMAC ... > I find that there is an API called as AES_128. ... The call AES_128(k, in, out) is pseudo code for AES - if you want to use the RFC code you will have to find an AES implementation and build an API around it to match the RFC 4493. ...
      (sci.crypt)
    • Re: Interface index hack in IP_ADD_MEMBERSHIP
      ... RFC 3678 specifies a protocol independent API for socket group ... I'm not sure if they have switched to another API. ... Quagga still uses it, too, if its configure script detects FreeBSD ...
      (freebsd-net)