IETF Logo Mail Archive

RE: draft-chakrabarti-nordmark-6man-efficient-nd-00.txt

Samita Chakrabarti <samita.chakrabarti@ericsson.com> Thu, 01 November 2012 23:51 UTC

Return-Path: <samita.chakrabarti@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9947321F985D for <ipv6@ietfa.amsl.com>; Thu, 1 Nov 2012 16:51:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f2avpvDMkk9R for <ipv6@ietfa.amsl.com>; Thu, 1 Nov 2012 16:51:30 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 0714721F985C for <ipv6@ietf.org>; Thu, 1 Nov 2012 16:51:29 -0700 (PDT)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id qA1NthwR020082; Thu, 1 Nov 2012 18:55:44 -0500
Received: from EUSAAHC002.ericsson.se (147.117.188.78) by eusaamw0712.eamcs.ericsson.se (147.117.20.181) with Microsoft SMTP Server (TLS) id 8.3.279.1; Thu, 1 Nov 2012 19:51:20 -0400
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.02.0318.001; Thu, 1 Nov 2012 19:51:20 -0400
From: Samita Chakrabarti <samita.chakrabarti@ericsson.com>
To: Carsten Bormann <cabo@tzi.org>, Erik Nordmark <nordmark@acm.org>
Subject: RE: draft-chakrabarti-nordmark-6man-efficient-nd-00.txt
Thread-Topic: draft-chakrabarti-nordmark-6man-efficient-nd-00.txt
Thread-Index: AQHNuHfZXe5gm1S+5EWc2afhJUukHJfVyRMA///VjEA=
Date: Thu, 01 Nov 2012 23:51:19 +0000
Message-ID: <ECA43DA70480A3498E43C3471FB2E1F0E281@EUSAAMB103.ericsson.se>
References: <16D60F43CA0B724F8052D7E9323565D72ECE73F3B4@EUSAACMS0715.eamcs.ericsson.se> <653FE6CB-CBFF-4CF5-967B-3227B5295B46@tzi.org> <5092E983.7080108@acm.org> <5A9BFA32-5E5C-49EC-8926-1ABF173324D7@tzi.org>
In-Reply-To: <5A9BFA32-5E5C-49EC-8926-1ABF173324D7@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.135]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 6man Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 23:51:30 -0000

 
Hi Carsten,

Please see below in-line with ===> prefix.
-----Original Message-----
From: Carsten Bormann [mailto:cabo@tzi.org] 
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 <nordmark@acm.org> 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

v2.23.0 | Report a Bug | By Email