This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "c)"
- Previous message (by thread): [address-policy-wg] policy proposal status
- Next message (by thread): [address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "c)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hans Petter Holen
hpholen at tiscali.no
Wed Jul 13 23:29:21 CEST 2005
Sascha Luck wrote: > >Again, this seems to exclude mobile operators who may only want to assign /64s >to their customers' handsets... > > I dont se how that assumption can be made. My mobile handset is connected to the public internet so that I can get updated exchange rates and read my email trough IMAP and so on. (and not trough NAT as my mobile operator has offered my the choice of not using NAT.) Iff this had been IPv6 and Iff Bluetooth had worked seemlessly on my other toys they could have had seemless access to the internet also. -hph
- Previous message (by thread): [address-policy-wg] policy proposal status
- Next message (by thread): [address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "c)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]