[mif] Comments on draft-mouton-mif-dhcpv6-drlo-00

"Gaurav Halwasia (ghalwasi)" <ghalwasi@cisco.com> Mon, 12 September 2011 05:08 UTC

Return-Path: <ghalwasi@cisco.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C77B21F8AE1 for <mif@ietfa.amsl.com>; Sun, 11 Sep 2011 22:08:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.71
X-Spam-Level:
X-Spam-Status: No, score=-9.71 tagged_above=-999 required=5 tests=[AWL=0.888, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ea296xDrpfGG for <mif@ietfa.amsl.com>; Sun, 11 Sep 2011 22:08:57 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 0A62E21F8AD8 for <mif@ietf.org>; Sun, 11 Sep 2011 22:08:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ghalwasi@cisco.com; l=4198; q=dns/txt; s=iport; t=1315804260; x=1317013860; h=mime-version:subject:date:message-id:from:to; bh=IIUmSwrpM2bDw2AEYrOOxNl0Fa1z6mmqxPagkSJfwNQ=; b=VJo4CQ6ty6PhAck5TYePl9nj/fsps6MxkxTOnPLpnmBNrzXAHHMBmHdI e2wBtvt7L16ZGjA0AEocdUDXcyxgTleMaDFlXJIrf9V3yWftUEyFi8dwu k7vWUvLY52PqQLtg+29rhUo04J3Ug+OKVhdF4vXrm9eLO71JYCTCV+e5i Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: An8GAMKTbU5Io8UR/2dsb2JhbABBgk2WaI5NeIFUAQEDEgEJEQNbAQweBhgHVwEECxAangqBJgGcaIYOYASHa5BwjAY
X-IronPort-AV: E=Sophos; i="4.68,366,1312156800"; d="scan'208,217"; a="54137970"
Received: from bgl-core-2.cisco.com ([72.163.197.17]) by ams-iport-2.cisco.com with ESMTP; 12 Sep 2011 05:10:58 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by bgl-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p8C5AvvC019985 for <mif@ietf.org>; Mon, 12 Sep 2011 05:10:57 GMT
Received: from xmb-bgl-41e.cisco.com ([72.163.129.220]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 12 Sep 2011 10:40:57 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CC710A.5A997C2B"
Date: Mon, 12 Sep 2011 10:40:56 +0530
Message-ID: <3CF88B99A9ED504197498BC6F6F04B81040FBDA9@XMB-BGL-41E.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Comments on draft-mouton-mif-dhcpv6-drlo-00
Thread-Index: AcxxClosDL9zuhm1Q+CTqXShqzwWxA==
From: "Gaurav Halwasia (ghalwasi)" <ghalwasi@cisco.com>
To: <mif@ietf.org>
X-OriginalArrivalTime: 12 Sep 2011 05:10:57.0172 (UTC) FILETIME=[5AABC540:01CC710A]
Subject: [mif] Comments on draft-mouton-mif-dhcpv6-drlo-00
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Sep 2011 05:08:58 -0000

Hi,

 

I read this draft, I think similar issue is also being discussed/solved
by draft-dec-dhcpv6-route-option-05 as well.

 

I see that you are proposing to have lifetime and MAC address in the
route option. Why do we want to communicate the lifetime of the route in
this option and that too I guess you are proposing to have a upper limit
of 150 minutes (9000 seconds) on that. What is the reason behind that.
What should be done after the expiry of this 150 minutes..?
Information-Request..? or DHCP Renew.?

I don't think that router lifetime will be that short and even if router
lifetime expires, DHCPv6 server can just send RECONFIGURE.  Normally
IPv6 addres lease time will not usually be that less.  

 

Further, What's the real need of having MAC/link address in the route
list option as there already exists means to get it.

Thanks,

Gaurav