IETF Logo Mail Archive

Re: Manual network access logins (Was: Re: [RAM] The mapping problem: rendezvous points?)

Leslie Daigle <leslie@thinkingcat.com> Wed, 23 May 2007 17:59 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 1Hqv7A-0004Gl-9E; Wed, 23 May 2007 13:59:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hqv79-00049B-21 for ram@iab.org; Wed, 23 May 2007 13:59:11 -0400
Received: from zeke.toscano.org ([69.31.8.124] helo=zeke.ecotroph.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hqv77-0003xN-Rk for ram@iab.org; Wed, 23 May 2007 13:59:11 -0400
Received: from dhcp-hrn-64-100-228-246.cisco.com ([::ffff:64.100.228.246]) (AUTH: PLAIN leslie, SSL: TLSv1/SSLv3,256bits,AES256-SHA) by zeke.ecotroph.net with esmtp; Wed, 23 May 2007 13:59:09 -0400 id 01588384.465480ED.000015E8
Message-ID: <465480E3.4040902@thinkingcat.com>
Date: Wed, 23 May 2007 13:58:59 -0400
From: Leslie Daigle <leslie@thinkingcat.com>
User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Manual network access logins (Was: Re: [RAM] The mapping problem: rendezvous points?)
References: <8F47F550-6224-4AFF-8359-CBA98D3F2FAB@muada.com> <271CF87FD652F34DBF877CB0CB5D16FC054EA470@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com> <62AFA8C7-FDD4-4FF2-B609-966081DDC0D1@cisco.com> <B79E458E-F18C-4617-B953-F311E5623E9A@cisco.com> <271CF87FD652F34DBF877CB0CB5D16FC054EA694@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com> <A590D37E-7DEC-4695-998E-DA12A205F306@cisco.com> <271CF87FD652F34DBF877CB0CB5D16FC054EA741@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com> <47DB1548-B91F-47A0-BF62-FACDA9E7706B@cisco.com> <20070518180916.GF69215@Space.Net> <3BD20378-6BEA-409D-A7E0-D170C0DF247D@cisco.com> <464E9D96.8070207@piuha.net> <4652E178.5080209@gmail.com> <4652FC8D.3090600@piuha.net> <6966E31B-F1D4-434B-9649-6C2B4B614F13@cisco.com> <4653F4AB.4070006@gmail.com> <4653FBB5.5000408@piuha.net>
In-Reply-To: <4653FBB5.5000408@piuha.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: Tony Li <tli@cisco.com>, 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


Jari Arkko wrote:
> We need to be careful with the word identifier here. Currently,
> network access is mostly based on either payment or subscriber
> identity. But those identities are very different from IP layer
> identifiers. Of course, the network access and IP layer setup
> processes can be (and has been) tied together for optimization
> reasons. Hopefully such optimizations do not create a 1-1
> permanent binding between the subscriber identities and your
> IP layer addressing or your future IP layer identifiers. This
> would be bad for privacy reasons, for instance.

Exactly -- so let's turn the point around and say that the
routing & addressing effort has to look at this problem to the
extent of expressing requirements for, and developing to,
the network entity identifier.

If that gets implemented as a 1-1 binding between subscribers
and network devices, that's probably a bad choice, but is
(IMO) beyond the scope of this work.

Leslie.

-- 

-------------------------------------------------------------------
"Reality:
      Yours to discover."
                                 -- ThinkingCat
Leslie Daigle
leslie@thinkingcat.com
-------------------------------------------------------------------

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

v2.23.0 | Report a Bug | By Email