IETF Logo Mail Archive

Re: [RAM] (no subject)

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 12 June 2007 08:23 UTC

Return-path: <ram-bounces@iab.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hy1f2-0006hJ-3a; Tue, 12 Jun 2007 04:23:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hy1f1-0006hA-2f for ram@iab.org; Tue, 12 Jun 2007 04:23:31 -0400
Received: from ug-out-1314.google.com ([66.249.92.172]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hy1ez-0002tz-Oz for ram@iab.org; Tue, 12 Jun 2007 04:23:31 -0400
Received: by ug-out-1314.google.com with SMTP id m2so116468uge for <ram@iab.org>; Tue, 12 Jun 2007 01:23:26 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=kt7zYsV0ewvSAJG9d+3yAtSW/DZCI/aUNMMVIo4WdAf28DD9bGOR3nyom4tzMWSHeGonuSnm+PIqfD8BdKq/gVO+JUr2jhF5VWYNNPyjFor8b15REXLOf1epKMDvkfg2253mk4RRGxRSal1KeqA5aaaA7x6hytIVIS7XLMPMeRI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=lckZ5/VLSm+gjsBcdWqXtrih0xxIjQHWW0vAQOcKufb7GLIv+35gjn6f3Jfabw7rLvJWRnFhEQb63RcArShvZ5sMkUrpOQbFgbMqHbBS+G9nxjiQap2mmAxLRTNOPfAGHPEka0gwU0jQo2iMbz5V1nVu41BIBip5/ROOffY3Z+c=
Received: by 10.67.29.7 with SMTP id g7mr371914ugj.1181636606753; Tue, 12 Jun 2007 01:23:26 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1]) by mx.google.com with ESMTP id l40sm302064ugc.2007.06.12.01.23.25 (version=SSLv3 cipher=RC4-MD5); Tue, 12 Jun 2007 01:23:26 -0700 (PDT)
Message-ID: <466E57FC.6040007@gmail.com>
Date: Tue, 12 Jun 2007 10:23:24 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: rja@extremenetworks.com
Subject: Re: [RAM] (no subject)
References: <d39.b429a86.339f140c@aol.com>
In-Reply-To: <d39.b429a86.339f140c@aol.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: ram@iab.org
X-BeenThere: ram@iab.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing and Addressing Mailing List <ram.iab.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ram>
List-Post: <mailto:ram@iab.org>
List-Help: <mailto:ram-request@iab.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=subscribe>
Errors-To: ram-bounces@iab.org

...
>>  One for E.164 (instead of DNS mapping a la enum) ? Etc.  etc.
> 
> I believe that it might also be possible to  algorithmically
> place an E.164 into an NSAP and then into an IPv6  address
> using the special prefix that means an NSAP is in the  low-order
> bits of the IPv6 address.  It isn't clear to me  whether
> this is explicitly documented at present.

RFC 4048 obsoleted that possibility.

     Brian

_______________________________________________
RAM mailing list
RAM@iab.org
https://www1.ietf.org/mailman/listinfo/ram

v2.23.0 | Report a Bug | By Email