Le 09/10/2014 21:17, Brian E Carpenter a écrit :
On 09/10/2014 22:29, Alexandru Petrescu wrote:
Thanks for updating.
Le 09/10/2014 11:26, Pierre Pfister a écrit :
Hello,
I’m proposing this change then.
1. In case the provided prefix is 64, the default consist in assigning
prefixes of length 64 first.
2. I’m adding a reference to 6man-why64.
When the algorithm decides to make a new assignment, it first needs
to specify the desired size of the assigned prefix. Although this
algorithm intends to remain generic, it was observed in
[I-D.ietf-6man-why64] that hosts may malfunction when the prefix
length is not 64. Therefore, prefixes of length 64 are RECOMMENDED.
With this text above, operators will be encouraged to read and give /64
to end user sites.
Huh? This text is discussing internal subnets inside the homenet; it
has nothing to do with the ISP allocation, which is discussed in the
homenet architecture (and RFC 6177).
Yes, I looked at RFC 6177 and I agree in a sense. It is the ISP
out-of-ones-homenet that is concerned by RFC6177 to assign more than /64
to homenet.
But, ISPs may be interested in populating one's homenet with more than
just 1 or 2 boxes currently. Theyd will rather use this HNCP document
to build one's homenets, rather than an architecture document.
At that point that ISP may become an internal-subnet-ISP in one's
homenet. And will tend to allocate only /64s for anything one wants to
do in one's homenet beyond the subnets ISP builds. And that will forbid
one again to go beyond what ISP allows.
Which may end up in the same /64 limit.
(I speculate that however many devices ISPs put in a homenet there will
always be some other devices they forgot but need to be there).
(one recent announcement of many devices in home is from Orange, and one
deployed practice of always-2 boxes is from Free).
Alex
Brian
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
