Re: [16NG] Resolutions to issues raised during 2nd WGLC of I-D draft-ietf-16ng-ipv6-over-ipv6cs-04 [1]
Alexandru Petrescu <alexandru.petrescu@motorola.com> Fri, 12 January 2007 11:06 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1H5KF5-0000Bg-9K; Fri, 12 Jan 2007 06:06:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1H5KF3-0000Bb-R9
for 16ng@ietf.org; Fri, 12 Jan 2007 06:06:37 -0500
Received: from mail119.messagelabs.com ([216.82.241.179])
by ietf-mx.ietf.org with smtp (Exim 4.43) id 1H5KF1-0004gR-JO
for 16ng@ietf.org; Fri, 12 Jan 2007 06:06:37 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-8.tower-119.messagelabs.com!1168599994!8429305!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 1207 invoked from network); 12 Jan 2007 11:06:34 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
by server-8.tower-119.messagelabs.com with SMTP;
12 Jan 2007 11:06:34 -0000
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l0CB6YsV012730;
Fri, 12 Jan 2007 04:06:34 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id l0CB6XBX016055;
Fri, 12 Jan 2007 05:06:33 -0600 (CST)
Message-ID: <45A76BB7.9070604@motorola.com>
Date: Fri, 12 Jan 2007 12:06:31 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: JinHyeock Choi <jinchoe@gmail.com>
Subject: Re: [16NG] Resolutions to issues raised during 2nd WGLC of I-D
draft-ietf-16ng-ipv6-over-ipv6cs-04 [1]
References: <C1CBFB73.2C040%basavaraj.patil@nokia.com>
<45A6AA0C.7040508@motorola.com>
<92e919fb0701111820k3aa970aft5001f778e8e46d93@mail.gmail.com>
In-Reply-To: <92e919fb0701111820k3aa970aft5001f778e8e46d93@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
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 JinHyeock,
JinHyeock Choi wrote:
> Dear Alex
>
> Thanks for your feedback. Kindly find my in-line comments.
>
>>> and there is no reason for the host to depend on RAs to detect if
>>> it has moved across ARs. Hence there is no reason for any change
>>> w.r.t 3775 and I do not see RFC3775 over-riding the values
>>> specified here.
>>
>> There is no other means for an IP stack on top of IPv6CS to know
>> that the subnet has changed. This is where MIP6 reacts, on subnet
>> change, not on PHY change. So the 802.16 BS, if it sends RAs, it
>> should send them quickly.
>
> Allow me to make is more clear.
>
> A 802.16 host doesn't have to rely on unsolicited PERIODIC RAs for
> movement detection. Upon network attachment, either 1) the access
> router sends an unsolicted RA as of FRD (draft-ietf-dna-frd-02) or 2)
> the host sends an RS to get a solicited RA as of DNAv6
> (draft-ietf-dna-protocol-03.txt).
I am not sure what you mean by 'network attachment'? I suppose you mean
the network entry procedure of 802.16? ('Attach' in 802.16 mostly means
to attach a part of message to another part, and only in one single
place a SS to a BS).
In the network entry procedure of the 802.16 document there is nothing
that suggests the behaviour you suggest above (DNA). Only ND is
suggested, not DNA.
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).
Alex
_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng
- [16NG] Resolutions to issues raised during 2nd WG… Basavaraj Patil
- Re: [16NG] Resolutions to issues raised during 2n… Alexandru Petrescu
- Re: [16NG] Resolutions to issues raised during 2n… JinHyeock Choi
- Re: [16NG] Resolutions to issues raised during 2n… Alexandru Petrescu
- Re: [16NG] Resolutions to issues raised during 2n… Basavaraj Patil
- Re: [16NG] Resolutions to issues raised during 2n… Alexandru Petrescu
- Re: [16NG] Resolutions to issues raised during 2n… Basavaraj Patil
- Re: [16NG] Resolutions to issues raised during 2n… gabriel montenegro
- Re: [16NG] Resolutions to issues raised during 2n… Basavaraj Patil
- Re: [16NG] Resolutions to issues raised during 2n… Alexandru Petrescu
- Re: [16NG] Resolutions to issues raised during 2n… Alexandru Petrescu
- Re: [16NG] Resolutions to issues raised during 2n… Syam Madanapalli
- Re: [16NG] Resolutions to issues raised during 2n… Alexandru Petrescu