[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(usagi-users 00282) Fw: USAGI IPv6 patches
- To: usagi-users@xxxxxxxxxxxxxx
- Subject: (usagi-users 00282) Fw: USAGI IPv6 patches
- From: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxxxxxx>
- Date: Fri, 16 Mar 2001 10:42:16 +0900
- List-subscribe: <mailto:usagi-users-ctl@linux-ipv6.org?body=subscribe>
- Reply-to: usagi-users@xxxxxxxxxxxxxx
- Sender: "Hideaki YOSHIFUJI" <yoshfuji@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Discussuions between netdev ip maintainers and debian-ipv6 people.
--
Hideaki YOSHIFUJI @ USAGI Project <yoshfuji@xxxxxxxxxxxxxx>
PGP5i FP: F731 6599 5EB2 BBA7 1515 1323 1806 A96F 5700 6B25
--- Begin Message ---
- To: bam@xxxxxxxxxx (Brian May)
- Subject: Re: USAGI IPv6 patches
- From: kuznet@xxxxxxxxxxxxx
- Date: Thu, 15 Mar 2001 23:34:34 +0300 (MSK)
- Cc: davem@xxxxxxxxxx, debian-ipv6@xxxxxxxxxxxxxxxx
- In-reply-to: <84vgpb7tny.fsf_-_@snoopy.apana.org.au> from "Brian May" at Mar 15, 1 11:38:41 am
- Resent-date: Fri, 16 Mar 2001 05:58:16 +0900 (JST)
- Resent-from: debian-ipv6@xxxxxxxxxxxxxxxx
- Resent-message-id: <dDt4oC.A.icG.wdSs6@murphy>
- Resent-sender: debian-ipv6-request@xxxxxxxxxxxxxxxx
Hello!
> I wondered if you could please tell me if there are any plans to merge
> the USAGI IPv6 patches[1] into the Linux source,
Partially.
> in order to make
> Linux comply with the latest IPv6 RFCs[2]?
It does.
USAGI patch contains some important things, but they are mixed
with of huge load of poorly cosmetic things and things, which
are difficult to accept.
Bug fixes are to be accepted. Unfortunately, it is not so easy
to separate really important pieces (I know only one to be honest:
reassembly of link local frames) of useless things sort of NI ICMP
and unadvertised change of macro names.
If USAGE people were more communicative at least about
core changes (bsdish binding rules) and real problems,
this would be great. Now it looks like a heap, where
it is not so easy to find real pearls.
Alexey
--
To UNSUBSCRIBE, email to debian-ipv6-request@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
--- End Message ---
--- Begin Message ---
- To: kuznet@xxxxxxxxxxxxx
- Subject: Re: USAGI IPv6 patches
- From: horape@xxxxxxxxxxxxxxxxxxxxxxxxxx
- Date: Thu, 15 Mar 2001 20:02:58 -0300
- Cc: Brian May <bam@xxxxxxxxxx>, davem@xxxxxxxxxx, debian-ipv6@xxxxxxxxxxxxxxxx
- In-reply-to: <200103152034.XAA31006@ms2.inr.ac.ru>; from kuznet@ms2.inr.ac.ru on Thu, Mar 15, 2001 at 11:34:34PM +0300
- References: <84vgpb7tny.fsf_-_@snoopy.apana.org.au> <200103152034.XAA31006@ms2.inr.ac.ru>
- Resent-date: Fri, 16 Mar 2001 08:03:14 +0900 (JST)
- Resent-from: debian-ipv6@xxxxxxxxxxxxxxxx
- Resent-message-id: <PVKVvD.A.lzC.qoUs6@murphy>
- Resent-sender: debian-ipv6-request@xxxxxxxxxxxxxxxx
- User-agent: Mutt/1.3.15i
(I!(BHola Alexey!
> > in order to make
> > Linux comply with the latest IPv6 RFCs[2]?
> It does.
Partially.
For the debian IPv6 project it's very important to have a good IPv6 stack
in mainstream linux kernel (because it'd be very hard to convince the
kernel package maintainer to use something else, and that's a good thing
IMHO)
> USAGI patch contains some important things, but they are mixed
> with of huge load of poorly cosmetic things and things, which
> are difficult to accept.
There are some things on USAGI that are very important for us (most glaring
probably is what USAGI names DOUBLE_BIND) and would like to see them in the
mainstream kernel.
> Bug fixes are to be accepted. Unfortunately, it is not so easy
> to separate really important pieces (I know only one to be honest:
> reassembly of link local frames) of useless things sort of NI ICMP
> and unadvertised change of macro names.
> If USAGE people were more communicative at least about
> core changes (bsdish binding rules) and real problems,
> this would be great. Now it looks like a heap, where
> it is not so easy to find real pearls.
Could we solve it like the Apache/SGI problem? Breaking the USAGI
differences in reasonably-sized patches and offering them to you?
Would you accept -for instance- a patch for the DOUBLE_BIND feature?
It's a real nuisance programming AF independant servers with the
mainstream linux behaviour. Yes, it probably breaks some IPv6 capable,
but not AF independant programs, but they'll be broken when the next
protocol arrives anyway...
> Alexey
HoraPe
---
Horacio J. Peña
horape@xxxxxxxxxxxxxxxxx
horape@xxxxxxxxxx
bofh@xxxxxxxxxxxxxx
horape@xxxxxxxxxxx
--
To UNSUBSCRIBE, email to debian-ipv6-request@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
--- End Message ---
--- Begin Message ---
- To: horape@xxxxxxxxxxxxxxxxxxxxxxxxxx
- Subject: Re: USAGI IPv6 patches
- From: "David S. Miller" <davem@xxxxxxxxxx>
- Date: Thu, 15 Mar 2001 15:05:51 -0800 (PST)
- Cc: kuznet@xxxxxxxxxxxxx, Brian May <bam@xxxxxxxxxx>, debian-ipv6@xxxxxxxxxxxxxxxx
- In-reply-to: <20010315200258.A21651@tinuviel.compendium.net.ar>
- References: <84vgpb7tny.fsf_-_@snoopy.apana.org.au> <200103152034.XAA31006@ms2.inr.ac.ru> <20010315200258.A21651@tinuviel.compendium.net.ar>
- Resent-date: Fri, 16 Mar 2001 08:06:10 +0900 (JST)
- Resent-from: debian-ipv6@xxxxxxxxxxxxxxxx
- Resent-message-id: <uPsG9C.A.JUE.crUs6@murphy>
- Resent-sender: debian-ipv6-request@xxxxxxxxxxxxxxxx
horape@xxxxxxxxxxxxxxxxxxxxxxxxxx writes:
> Could we solve it like the Apache/SGI problem? Breaking the USAGI
> differences in reasonably-sized patches and offering them to you?
>
> Would you accept -for instance- a patch for the DOUBLE_BIND feature?
This is exactly what we are asking for.
Later,
David S. Miller
davem@xxxxxxxxxx
--
To UNSUBSCRIBE, email to debian-ipv6-request@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
--- End Message ---
--- Begin Message ---
- To: "David S. Miller" <davem@xxxxxxxxxx>
- Subject: Re: USAGI IPv6 patches
- From: horape@xxxxxxxxxxxxxxxxxxxxxxxxxx
- Date: Thu, 15 Mar 2001 20:10:38 -0300
- Cc: kuznet@xxxxxxxxxxxxx, Brian May <bam@xxxxxxxxxx>, debian-ipv6@xxxxxxxxxxxxxxxx
- In-reply-to: <15025.19151.697869.845606@pizda.ninka.net>; from davem@redhat.com on Thu, Mar 15, 2001 at 03:05:51PM -0800
- References: <84vgpb7tny.fsf_-_@snoopy.apana.org.au> <200103152034.XAA31006@ms2.inr.ac.ru> <20010315200258.A21651@tinuviel.compendium.net.ar> <15025.19151.697869.845606@pizda.ninka.net>
- Resent-date: Fri, 16 Mar 2001 08:11:08 +0900 (JST)
- Resent-from: debian-ipv6@xxxxxxxxxxxxxxxx
- Resent-message-id: <UBHKAB.A.CvF.KwUs6@murphy>
- Resent-sender: debian-ipv6-request@xxxxxxxxxxxxxxxx
- User-agent: Mutt/1.3.15i
(I!(BHola!
> > Could we solve it like the Apache/SGI problem? Breaking the USAGI
> > differences in reasonably-sized patches and offering them to you?
> > Would you accept -for instance- a patch for the DOUBLE_BIND feature?
> This is exactly what we are asking for.
Great, i'll try to work on it tomorrow.
> Later,
> David S. Miller
> davem@xxxxxxxxxx
HoraPe
---
Horacio J. Peña
horape@xxxxxxxxxxxxxxxxx
horape@xxxxxxxxxx
bofh@xxxxxxxxxxxxxx
horape@xxxxxxxxxxx
--
To UNSUBSCRIBE, email to debian-ipv6-request@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
--- End Message ---