[ppml] Proposed Policy: PI assignments for V6

[marcelo bagnulo braun]

Hi Ron,

That makes more sense to me, but the question is how is this considered 
when applying for address space on a rir? if a mobile operator claims 
that he needs a /48 for each handset, does he get the address space 
requested?

regards, marcelo

El 09/12/2004, a las 16:23, da Silva, Ron escribió:

>> so, i guess that the right thing to do would be to assign a /48 to
> each
>> mobile phone, right?
>>
>> since RFC 3177 states that:
>>        -  /48 in the general case, except for very large subscribers.
>>        -  /64 when it is known that one and only one subnet is needed
> by
>>           design.
>>        -  /128 when it is absolutely known that one and only one
> device
>>           is connecting.
>>
>> and since  we cannot be sure that a mobile phone will have a single
>> subnetwork behind, i guess that the /48 would be the proper choice
>>
>> I am sorry but i think this is a huge waste.
>> For the time being, most of mobile phones will not have a manet
> behind,
>> not one not many subnetworks. I think there must be something very
>> wrong if we assign a /48 to each mobile phone
>
> From a wireline connectivity perspective, the /48 would be assigned to
> the provider gateway (e.g. DSL/Cable router).  Any subnets downstream 
> of
> that connection would be allocated from the /48 pool.  If there was a
> device within the home (say a multi-modal handset with 802.11x, GSM and
> bluetooth) that needed a prefix (or two) for additional subnetting then
> there should be a mechanism to allocate multiple /64's to that device
> from the /48.
>
> For consistency, can someone extend that concept to a GSM/CDMA
> connectivity model?  Where is the /48 assigned?  Presumably, whatever
> gateway device is being employed for assigning IPv6 addresses to
> handsets would be assigned the /48 and then any further delegation 
> would
> be accomplished with downstream /64 assignments.
>
> Anyone have any URL's that detail current IPv4/IPv6 addressing plans 
> for
> GSM/CDMA architectures?
>
> -ron
>