(sipp) E.164 mapping into IPv6

William Allen Simpson <bill.simpson@um.cc.umich.edu> Wed, 03 August 1994 16:17 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07488; 3 Aug 94 12:17 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa07484; 3 Aug 94 12:17 EDT
Received: from Sun.COM by CNRI.Reston.VA.US id aa09979; 3 Aug 94 12:17 EDT
Received: from Eng.Sun.COM (zigzag.Eng.Sun.COM) by Sun.COM (sun-barr.Sun.COM) id AA10397; Wed, 3 Aug 94 09:16:22 PDT
Received: from sunroof2.Eng.Sun.COM by Eng.Sun.COM (4.1/SMI-4.1) id AA05006; Wed, 3 Aug 94 09:16:31 PDT
Received: by sunroof2.Eng.Sun.COM (4.1/SMI-4.1) id AA00839; Wed, 3 Aug 94 09:18:24 PDT
Received: from Eng.Sun.COM (engnews1) by sunroof2.Eng.Sun.COM (4.1/SMI-4.1) id AA00824; Wed, 3 Aug 94 09:18:09 PDT
Received: from Sun.COM (sun-barr) by Eng.Sun.COM (4.1/SMI-4.1) id AA02314; Wed, 3 Aug 94 09:15:41 PDT
Received: from merit.edu by Sun.COM (sun-barr.Sun.COM) id AA10104; Wed, 3 Aug 94 09:15:24 PDT
Received: from pm002-12.dialip.mich.net (pm002-12.dialip.mich.net [35.1.48.93]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id MAA09057 for <sipp@sunroof.eng.sun.com>; Wed, 3 Aug 1994 12:15:22 -0400
Date: Wed, 3 Aug 94 15:33:04 GMT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: William Allen Simpson <bill.simpson@um.cc.umich.edu>
Message-Id: <2964.bill.simpson@um.cc.umich.edu>
To: sipp@sunroof.eng.sun.com
Subject: (sipp) E.164 mapping into IPv6
X-Orig-Sender: owner-sipp@sunroof.eng.sun.com
Precedence: bulk
Reply-To: sipp@sunroof.eng.sun.com

> From: Ran Atkinson <atkinson@sundance.itd.nrl.navy.mil>
> 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.
>
Actually, when there are no IEEE addresses assigned (the typical serial
link), an E.164 address would be very useful for creating a local-use
address.  An ISDN link will automatically learn it.  A dial-up link
could convert the dialing number into one.

It wouldn't occupy any more space than a IEEE address.  I'd like to have
a block assigned to local-use E.164 addresses.  (I had one in _my_ plan.)

Since there is no topological information in the E.164 address related
to _our_ nets, it should _only_ be local-use.

Bill.Simpson@um.cc.umich.edu
 ------------------------------------------------------------------------------
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