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

"JinHyeock Choi" <jinchoe@gmail.com> Fri, 12 January 2007 02:23 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H5C4a-0003BI-9A; Thu, 11 Jan 2007 21:23:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H5C4Y-0003A0-Is for 16ng@ietf.org; Thu, 11 Jan 2007 21:23:14 -0500
Received: from wr-out-0506.google.com ([64.233.184.228]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H5C1p-0001i0-Gp for 16ng@ietf.org; Thu, 11 Jan 2007 21:20:27 -0500
Received: by wr-out-0506.google.com with SMTP id 36so506706wra for <16ng@ietf.org>; Thu, 11 Jan 2007 18:20:25 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=RQVIc35WAhw9SX7PnFUjymySyUIVuF2K9/PkJC2hdthSreGFmoOi6Y8LZ3ip3RavEse+FokQDuR5iN4Cp8oF/2TG4z9l4DxXksjXahFpEg2pLu3qUHnw6gFlEaE710E0OkwI6HbE4QsodxQrO6jZvSAF3/bOErfJQ8vwOoV68vk=
Received: by 10.35.75.1 with SMTP id c1mr173842pyl.1168568425124; Thu, 11 Jan 2007 18:20:25 -0800 (PST)
Received: by 10.35.35.13 with HTTP; Thu, 11 Jan 2007 18:20:24 -0800 (PST)
Message-ID: <92e919fb0701111820k3aa970aft5001f778e8e46d93@mail.gmail.com>
Date: Fri, 12 Jan 2007 11:20:25 +0900
From: "JinHyeock Choi" <jinchoe@gmail.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
Subject: Re: [16NG] Resolutions to issues raised during 2nd WGLC of I-D draft-ietf-16ng-ipv6-over-ipv6cs-04 [1]
In-Reply-To: <45A6AA0C.7040508@motorola.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <C1CBFB73.2C040%basavaraj.patil@nokia.com> <45A6AA0C.7040508@motorola.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
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

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).

So RA interval won't affect movement detection (or DNA) delay.

Thanks for your kind consideration.

Best Regards

JinHyeock

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