Hi Dario,

Great thanks. I had asked as the reasoning for having the fe80::XXXX style
was that you could use it to assign easy-to-type link-local addresses to
nodes. So for example you could assign the address fe80::1 to a node, and
6lowpan could compress that nicely.

In real life I think most of the time we will see auto-configured link-local
addresses anyway, so I think it was also an unlikely case. But I couldn't
think of any fe80::ff:fe00:XXXX uses. So knowing there is a few out there,
even if they are unlikely, was my concern.

The hc-11 draft seems to solve all previous issues I've heard of or run into
during implementation of 6lowpan-hc. Thus I would support this draft's LC
and sending onward to the IETF.

Regards,

  -Colin

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf
Of Dario Tedeschi
Sent: September 2, 2010 12:45 AM
To: [email protected]
Subject: Re: [6lowpan] Fwd: New Version Notification for
draft-ietf-6lowpan-hc-11

  I can see four cases where SAM/DAM=2 might be used in stateless 
compression:
1) A manually configured link-local address.
2) A node acting as a proxy for a specific link-local address.
3) A link-local anycast address.
4) A redirect

Perhaps these are unlikely cases, but it's nice to have them covered.

Dario

On 01/09/2010 2:33 PM, Colin O'Flynn wrote:
> Hello,
>
> I noticed that -10 also changed the format of the link-local stateless
> compression to match the stateful global prefix compression.
>
> Is there a case where you'd want to use the fe80::ff:fe00:XXXX form, where
> the XXXX is not the 802.15.4 short address?
>
> At any rate that change is fine, as it somewhat simplifies the code since
> all addressing cases are then the same for the IID.
>
> Regards,
>
>   -Colin
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf
> Of Jonathan Hui
> Sent: September 1, 2010 10:25 PM
> To: 6lowpan 6lowpan
> Subject: [6lowpan] Fwd: New Version Notification for
> draft-ietf-6lowpan-hc-11
>
>
> By request of the chairs, I have made Dario's suggested change before
> submission to IESG.
>
>     This mapping from a short IEEE 802.15.4 address to 64-bit IIDs is
>     also used to reconstruct any part of an IID not covered by context
>     information when only 16 bits are carried in-line (SAC/DAC=10).
> -->
>     This mapping from a short IEEE 802.15.4 address to 64-bit IIDs is
>     also used to reconstruct any part of an IID not covered by context
>     information.
>
> --
> Jonathan Hui
>
> Begin forwarded message:
>
>> From: IETF I-D Submission Tool<[email protected]>
>> Date: September 1, 2010 2:22:17 PM PDT
>> To: [email protected]
>> Cc: [email protected]
>> Subject: New Version Notification for draft-ietf-6lowpan-hc-11
>>
>>
>> A new version of I-D, draft-ietf-6lowpan-hc-11.txt has been successfully
> submitted by Jonathan Hui and posted to the IETF repository.
>> Filename:     draft-ietf-6lowpan-hc
>> Revision:     11
>> Title:                Compression Format for IPv6 Datagrams in 6LoWPAN
> Networks
>> Creation_date:        2010-09-01
>> WG ID:                6lowpan
>> Number_of_pages: 23
>>
>> Abstract:
>> This document specifies an IPv6 header compression format for IPv6
>> packet delivery in 6LoWPAN networks.  The compression format relies
>> on shared context to allow compression of arbitrary prefixes.  How
>> the information is maintained in that shared context is out of scope.
>> This document specifies compression of multicast addresses and a
>> framework for compressing next headers.  UDP header compression is
>> specified within this framework.
>>
>>
>>
>> The IETF Secretariat.
>>
>>
> _______________________________________________
> 6lowpan mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/6lowpan
>
> _______________________________________________
> 6lowpan mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/6lowpan

_______________________________________________
6lowpan mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lowpan

_______________________________________________
6lowpan mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lowpan

Reply via email to