It's a minor nit but the text as it's written now assumes the context will be at least 64 bits. I don't see that written down anywhere - should it be?

Robert

Robert Cragie (Pacific Gas & Electric)

Gridmerge Ltd.
89 Greenfield Crescent,
Wakefield, WF4 4WA, UK
+44 1924 910888
+1 415 513 0064
http://www.gridmerge.com <http://www.gridmerge.com/>


On 21/09/2010 4:28 PM, Jonathan Hui wrote:
Added text to specify that the 16-bit to IID mapping is used to derive IID bits 
when SAC/DAC=1 and the context does not cover those bits.

--
Jonathan Hui

Begin forwarded message:

From: IETF I-D Submission Tool<[email protected]>
Date: September 21, 2010 8:27:11 AM PDT
To: [email protected]
Cc: [email protected]
Subject: New Version Notification for draft-ietf-6lowpan-hc-12


A new version of I-D, draft-ietf-6lowpan-hc-12.txt has been successfully 
submitted by Jonathan Hui and posted to the IETF repository.

Filename:        draft-ietf-6lowpan-hc
Revision:        12
Title:           Compression Format for IPv6 Datagrams in 6LoWPAN Networks
Creation_date:   2010-09-21
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

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

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

Reply via email to