Re: [6lo] FW: Generation of IPv6 IIDs

Hi, Randy,

Essentially, the two options seem to be:

1) Say that what 6lo currently does is a perfetly valid exception (with
no need to do anything in this area in the future)

2) Flag what 6lo is doing as "something that doesn't comply with
default-iids. You may still use this n the mean time, but a solution
should be engineered to comply with default-iids"

My understanding is that Erik is proposing "2)"... and I tend to like
that option.

Thoughts?

Thanks!

Best regards,
Fernando

On 07/24/2014 01:50 PM, Turner, Randy wrote:
> 
> 
> Ditto what Erik said....we operate AMI networks where most of the EUI-64 threats do not exist, and 6775 mechanisms are employed - it would be nice if EUI-64s were not "deprecated" but still allowed, with the existing alternative documents being available for those that need it.
> 
> Randy
> 
> -----Original Message-----
> From: 6lo [mailto:6lo-bounces@ietf.org] On Behalf Of Erik Nordmark
> Sent: Thursday, July 24, 2014 8:21 AM
> To: Jonathan Hui (johui); Erik Nordmark
> Cc: 6lo-chairs@tools.ietf.org; 6man Chairs (6man-chairs@tools.ietf.org); Erik Nordmark; Dave Thaler; Samita Chakrabarti; 6lo@ietf.org; Fernando Gont; draft-ietf-6man-default-iids@tools.ietf.org
> Subject: Re: [6lo] Generation of IPv6 IIDs
> 
> On 7/23/14, 10:25 PM, Jonathan Hui (johui) wrote:
>> Note that RFC 6282 already provides the option:
>> - If the IID can be derived from MAC address, great.
>> - If not, things will still work just with reduced efficiency.
>>
>> Section 10 of RFC 4944 also provides the same option, but has since been replaced by the encoding specified in RFC 6282.
>>
>> Also note that 802.15.4 interfaces have both a stable MAC address (EUI-64) and a locally-significant, dynamic MAC address (Short Address).  Many of the arguments against MAC-address-based IIDs may not apply when using Short Addresses.
>>
> 
> The issue I know about is in RFC 6775 which would fail to deliver errors to an ARO if the host doesn't have a link-local address with a EUI-64-based IID.
> 
> RFC 6775 (6lowpan-nd) makes the assumption that the host always has a link-local address configured with the EUI-64 of the host.
> That assumption is used in section 6.5.2 to send errors back to hosts.
> Note that we already know of a solution, which is local to the router implementation, which is already captured in section 9.7 in draft-chakrabarti-nordmark-6man-efficient-nd.
> 
>     Erik
> 
> 
> _______________________________________________
> 6lo mailing list
> 6lo@ietf.org
> https://www.ietf.org/mailman/listinfo/6lo
> 
> P PLEASE CONSIDER OUR ENVIRONMENT BEFORE PRINTING THIS EMAIL.
> 
> This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
> 
> _______________________________________________
> 6lo mailing list
> 6lo@ietf.org
> https://www.ietf.org/mailman/listinfo/6lo
> 

-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492