<<<
Chronological Index
>>> <<<
Thread Index
>>>
[ga] "...IPv6 is NOT a new protocol, it is only a new version of the IP protocol..."
- To: <Francis.Dupont@enst-bretagne.fr>
- Subject: [ga] "...IPv6 is NOT a new protocol, it is only a new version of the IP protocol..."
- From: "Jim Fleming" <JimFleming@ameritech.net>
- Date: Fri, 30 Aug 2002 10:28:15 -0500
- Cc: <chandley@ntia.doc.gov>, <censslin@ntia.doc.gov>, <DEvans@doc.gov>, <nvictory@ntia.doc.gov>, <RLayton@ntia.doc.gov>, <takashi@arano.jp>, <hph@online.no>, <smlee@i-names.co.kr>, <huangk@alum.sinica.edu>, <broseman@ix.netcom.com>, <cjw@remarque.org>, <cire@deckerstone.net>, <Woeber@CC.UniVie.ac.at>, <Sabine.Jaume@renater.fr>, <mouhamet@next.sn>, <rbeca@ctc.cl>, <yann@id.mu>, <chris@idsc.net.eg>, <gvaldez@nic.mx>, <glaser@fapesp.br>, <ga@dnso.org>
- Sender: owner-ga-full@dnso.org
From: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>
"...IPv6 is NOT a new protocol, it is only a new version of the IP protocol..."
How come the IPv4 Header has 160-bits and the IPv6 Header has 320-bits ?
Is VHS the same as BETAmax ?
Mars is not a new planet, it is just a suburb of planet Earth...
http://www.ActiveWorlds.com
Jim Fleming
2002:[IPv4]:000X:03DB:...IPv8 is closer than you think...
http://www.iana.org/assignments/ipv4-address-space
http://www.ntia.doc.gov/ntiahome/domainname/130dftmail/unir.txt
----- Original Message -----
From: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>
To: <itojun@iijlab.net>
Cc: <ipng@sunroof.eng.sun.com>
Sent: Friday, August 30, 2002 6:10 AM
Subject: Re: another input to IPv6 addressing architecture
> In your previous mail you wrote:
>
> 4. Suggested protocol change
>
> o In IPv4 address architecture document [Hinden, 1998] explicitly state
> that IPv4 mapped address is for use within basic API [Gilligan, 1999]
> , and basic API only. Forbid any other uses.
>
> => I don't like at all SIIT so I have no concern with this proposal.
>
> o Move any document that suggests the use of IPv4 mapped address on wire
> to historic, due to security reasons.
>
> => you are a bit hard: these mechanisms should simply use other
> injections of the IPv4 address space into the IPv6 address space
> (there are many ways to inject a 2^32 space into a 2^128 one :-).
>
> The above change will remove the threat due to the use of IPv4 mapped
> address on wire.
>
> => I agree this should be simpler so safer.
>
> Another way is to deprecate RFC2553 section 3.7, however, due to the
> wide deployment of applications that use IPv6 basic API, the option is
> not feasible.
>
> => I strongly object to this part of your proposal. IMHO IPv6 is NOT
> a new protocol, it is only a new version of the IP protocol. So the
> right target is to provide an "all version" API, as it is easy to inject
> IPv4 into IPv6, the section 3.7 is the right idea!
>
> Regards
>
> Francis.Dupont@enst-bretagne.fr
> --------------------------------------------------------------------
> IETF IPng Working Group Mailing List
> IPng Home Page: http://playground.sun.com/ipng
> FTP archive: ftp://playground.sun.com/pub/ipng
> Direct all administrative requests to majordomo@sunroof.eng.sun.com
> --------------------------------------------------------------------
--
This message was passed to you via the ga-full@dnso.org list.
Send mail to majordomo@dnso.org to unsubscribe
("unsubscribe ga-full" in the body of the message).
Archives at http://www.dnso.org/archives.html
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|