(sipp) NSAPA mapping into IPv6

Ran Atkinson <atkinson@sundance.itd.nrl.navy.mil> Wed, 03 August 1994 03:15 UTC

To: sipp@sunroof2.eng.sun.com
Subject: (sipp) NSAPA mapping into IPv6
Date: Tue, 02 Aug 1994 16:09:53 +0000
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Ran Atkinson <atkinson@sundance.itd.nrl.navy.mil>
Message-Id: <9408021609.aa14982@sundance.itd.nrl.navy.mil>
Precedence: bulk
Reply-To: sipp@sunroof.eng.sun.com

Brian,
  I also would like to see the G bit disappear.  If/when CLNP
multicasting gets completely sorted out, it can be addressed further
at that time.  My preferance would be to map CLNP multicast groups
into the IPv6 multicast group address space and not consume additional
IPv6 address space.

All,
  A general comment, not particularly directed at Brian's work, is
that the community needs to be careful to reserve most of the IPv6
address space for future use and minimise the amount of address space
that is initially allocated to any use.  I agree with Steve Deering's
observation that there is a natural tendency to think we have lots of
address space and so some folks erroneously believe that we don't need
to be as careful in allocating it.  

  I think that mappings from IPX addresses and currently-in-use NSAPAs
are useful.  It is not at all clear to me that mappings from E.164
addresses (that is, telephone numbers) into IPv6 addresses is a wise
use of IPv6 address space.

Regards,

  Ran
  atkinson@itd.nrl.navy.mil

 ------------------------------------------------------------------------------
IETF SIPP Working Group - Archives:  parcftp.xerox.com:/pub/sipp
Unsubscribe:	unsubscribe sipp		(as message body, not subject)
Direct all administrative requests to majordomo@sunroof.eng.sun.com

(sipp) NSAPA mapping into IPv6 Ran Atkinson