Gnus development mailing list
 help / color / mirror / Atom feed
* bug testing: first digest
@ 1999-03-31  8:27 Vladimir Volovich
  0 siblings, 0 replies; only message in thread
From: Vladimir Volovich @ 1999-03-31  8:27 UTC (permalink / raw)



Topics:
   Re: PF_INET6 on non-ipv6 kernels
   Re: PF_INET6 on non-ipv6 kernels
   Re: PF_INET6 on non-ipv6 kernels


----------------------------------------------------------------------

Date: Tue, 30 Mar 1999 23:28:28 +0400 (MSK DST)
From: kuznet@ms2.inr.ac.ru
Subject: Re: PF_INET6 on non-ipv6 kernels

Hello!

> > This would be reasonable if some IPv6 API really existed. 8)
> 
> It does exist, and is published as RFC 2133.

Alas, this standard is obsolete. And our stack is obsolete 8)

Alexey Kuznetsov

Please read the FAQ at http://www.tux.org/lkml/

------------------------------

Date: Tue, 30 Mar 1999 16:51:14 -0300
From: =?iso-8859-1?Q?Horacio_J=2E_Pe=F1a?= <horape@tinuviel.compendium.com.ar>
Subject: Re: PF_INET6 on non-ipv6 kernels

 Hola!

> > This would be reasonable if some IPv6 API really existed. 8)
> It does exist, and is published as RFC 2133.
The IPv6 people considers RFC 2133 obsolete.

> > It must work equally over TCP/IP, TCP/IPv6,
> > ISO stack or some another connection-oriented protocol.
> No it does not.  In order to interoperate, applications need only work
> with internet standard protocols.  ISO stacks and non-standard transport
> layer protocols are irrelevant.
Ok, write your code to be used only in ipv6/ipv4. When we move to ipv7 you'll
have to recode it... The ones coding protocol-independant code will be laughing
at you.

					HoraPe
- --
Horacio J. PeЯa
horape@compendium.com.ar
horape@uninet.edu
bofh@puntoar.net.ar
horape@hcdn.gov.ar

Please read the FAQ at http://www.tux.org/lkml/

------------------------------

Date: Tue, 30 Mar 1999 12:30:06 -0800
From: jgmyers@netscape.com (John Myers)
Subject: Re: PF_INET6 on non-ipv6 kernels

Horacio J. PeЯa wrote:
> The IPv6 people considers RFC 2133 obsolete.

Care to provide a reference to back your claim?  I cannot find any
relevant internet drafts, other than
draft-ietf-ipngwg-dns-lookups-03.txt which is not a kernel issue.

> Ok, write your code to be used only in ipv6/ipv4. When we move to ipv7 you'll
> have to recode it... The ones coding protocol-independant code will be laughing
> at you.

Name one "protocol independent" networking program written before IPv6
which required no modification to work over IPv6.

Please read the FAQ at http://www.tux.org/lkml/

------------------------------

End of forward16464_N Digest
****************************




^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~1999-03-31  8:27 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-03-31  8:27 bug testing: first digest Vladimir Volovich

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).