Re: [16NG] Resolutions to issues raised during 2nd WGLC of I-D draft-ietf-16ng-ipv6-over-ipv6cs-04 [1]

Basavaraj Patil <basavaraj.patil@nokia.com> Fri, 12 January 2007 17:35 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H5QJU-0002Rx-14; Fri, 12 Jan 2007 12:35:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H5QJT-0002QW-Ay for 16ng@ietf.org; Fri, 12 Jan 2007 12:35:35 -0500
Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H5QHY-0002UA-9K for 16ng@ietf.org; Fri, 12 Jan 2007 12:33:37 -0500
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l0CHV7dX008167; Fri, 12 Jan 2007 19:31:37 +0200
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 12 Jan 2007 19:33:26 +0200
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 12 Jan 2007 11:33:23 -0600
Received: from 172.19.244.117 ([172.19.244.117]) by daebe101.NOE.Nokia.com ([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; Fri, 12 Jan 2007 17:33:22 +0000
User-Agent: Microsoft-Entourage/11.3.2.061213
Date: Fri, 12 Jan 2007 11:35:02 -0600
Subject: Re: [16NG] Resolutions to issues raised during 2nd WGLC of I-D draft-ietf-16ng-ipv6-over-ipv6cs-04 [1]
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: ext Alexandru Petrescu <alexandru.petrescu@motorola.com>, JinHyeock Choi <jinchoe@gmail.com>
Message-ID: <C1CD22E6.2C115%basavaraj.patil@nokia.com>
Thread-Topic: [16NG] Resolutions to issues raised during 2nd WGLC of I-D draft-ietf-16ng-ipv6-over-ipv6cs-04 [1]
Thread-Index: Acc2b/0pO4HewqJjEduv0AARJNUNiA==
In-Reply-To: <45A76BB7.9070604@motorola.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 12 Jan 2007 17:33:23.0473 (UTC) FILETIME=[C26FE010:01C7366F]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: 16ng@ietf.org
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
Errors-To: 16ng-bounces@ietf.org

Hi Alex,

On 1/12/07 5:06 AM, "ext Alexandru Petrescu"
<alexandru.petrescu@motorola.com> wrote:

> 
> Periodic RA is in widespread use for movement detection.  I do not
> understand the opposition to use periodic RAs as allowed by rfc3775.
> What breaks if we use periodic RAs with a frequency higher than 1/4s?
> (remark arguments of air interface gains are different on high-bandwidth
> links).

The fact is that sending periodic RAs on an air interface irrespective of BW
capacity is suboptimal.
A host in Idle mode is not listening for periodic RAs. Listening for
periodic RAs would prevent the host from transitioning to idle mode which
has an adverse impact on battery life. 802.16 has defined paging and Idle
mode support. In air-interfaces that do not support such capability, sending
of very frequent RAs is possible but IMO still not the most efficient usage
of the bandwidth. 
In licensed spectrum the optimization and efficiency of the air interface is
critical. Periodic RAs are unavoidable at this time. The best that we can do
without breaking backward compatibility is to send it with large time
intervals as the I-D suggests.
Movement detection can be done be accomplished by other means. If the host
is only relying on RAs for movement detection (at the IP layer), then it
could just as well send a Rtr solicitation. This is not prevented.

In Unlicensed spectrum you may have a bit more liberty about how the
air-interface is used but even in those cases, optimizing it is a better
choice.

-Raj

> 
> Alex


_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng