Hi Carsten, Please see below in-line with ===> prefix. -----Original Message----- From: Carsten Bormann [mailto:[email protected]] Sent: Thursday, November 01, 2012 2:55 PM To: Erik Nordmark Cc: Samita Chakrabarti; 6man Mailing List Subject: Re: draft-chakrabarti-nordmark-6man-efficient-nd-00.txt
On Nov 1, 2012, at 22:28, Erik Nordmark <[email protected]> wrote: >> -- I'm not too wild about the E-bit. Maybe we should extract the 6CIO from >> draft-bormann-6lowpan-ghc and use this? > > I don't understand the relationship. > The E-bit is there to specify that the router supports AROs. That way the > hosts can tell whether it makes sense to try ARO. > How does this relate to compression context? Not at all. I'm not talking about 6CO, but about 6CIO from draft-bormann-6lowpan-ghc. This is a capability indication option. ===> E-bit is to distinguish between classic-ND and efficient-ND operation. If you are concerned about flag bit shortage in RFC 4861 RA format, then the solution exists. It is RFC 5175 (IPv6 Router Adv Flags option). As mentioned in bormann-6lowpan-ghc that 6CIO (6lowpan Capability Indication) is used for capabilty advertisements for 6lowpan nodes. It could be useful for advertising for different other capabilities in 6lowpan environment where different types of 6lowpan nodes might be active in a network ( HC capable, Low-memory vs buffering capable, specific app-support capable etc. ) while I cannot see a need for additional 8 bytes of 6CIO in order for simple enahncement of IPv6 RA mechanism with registration when 1 existing bit can suffice. Thanks, -Samita -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
