Re: [v6ops] New Version Notification for draft-baker-v6ops-cpe-autoconfigure-00.txt

["STARK, BARBARA H" <[e-mail]>]

The BBF flow has simultaneous RS and DHCPv6 solicitation. This is at odds with what you suggest. Simultaneous and sequential are both allowed by RFC 7084. I realize many cable providers have expressed a preference for sequential RS and DHCPv6 solicit, but many telcos have expressed a preference for simultaneous.

IIRC the preference for simultaneous was for telco environments where the device had to emit a packet before the network would see it. The concern was that because the device only sent three RSes on startup, if those three RSes were dropped then it would never get an RA.

That concern is largely mitigated by resilient RS, which is now available on fairly recent versions of Linux (and was backported to Android kernels all the way back to 3.10, so CPE vendors can use it on older kernels too).

<bhs> I was recalling this happened because a certain guy, named Ole Troan, convinced us it was more efficient and there was no reason to wait. Without IA_PD, the connection is fairly useless. If know you need it, why wait. I recall no discussion of the access network architecture people asking for it, and can’t find this mentioned in TR-177 or TR-187 (access network architecture IPv6 docs).
Barbara