[netext] Comments on I-D: draft-bhandari-netext-pmipv6-dhcp-options
<Basavaraj.Patil@nokia.com> Mon, 23 July 2012 16:40 UTC
Return-Path: <Basavaraj.Patil@nokia.com>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52DED21F8564 for <netext@ietfa.amsl.com>; Mon, 23 Jul 2012 09:40:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.571
X-Spam-Level:
X-Spam-Status: No, score=-106.571 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 BJGkWefzcADk for <netext@ietfa.amsl.com>; Mon, 23 Jul 2012 09:40:38 -0700 (PDT)
Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by ietfa.amsl.com (Postfix) with ESMTP id 80F2D21F858D for <netext@ietf.org>; Mon, 23 Jul 2012 09:40:38 -0700 (PDT)
Received: from vaebh106.NOE.Nokia.com (in-mx.nokia.com [10.160.244.32]) by mgw-sa01.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q6NGeYEp003402 for <netext@ietf.org>; Mon, 23 Jul 2012 19:40:34 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.60]) by vaebh106.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Mon, 23 Jul 2012 19:41:12 +0300
Received: from 008-AM1MPN1-072.mgdnok.nokia.com ([169.254.2.83]) by 008-AM1MMR1-005.mgdnok.nokia.com ([65.54.30.60]) with mapi id 14.02.0283.004; Mon, 23 Jul 2012 18:40:16 +0200
From: Basavaraj.Patil@nokia.com
To: netext@ietf.org
Thread-Topic: Comments on I-D: draft-bhandari-netext-pmipv6-dhcp-options
Thread-Index: AQHNaPHWBFu37wgJmEONXE0MaJ3J3g==
Date: Mon, 23 Jul 2012 16:40:15 +0000
Message-ID: <CC32E7B0.21A7F%basavaraj.patil@nokia.com>
In-Reply-To: <CC327E29.16021%shwethab@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.1.120420
x-originating-ip: [172.19.40.54]
Content-Type: multipart/alternative; boundary="_000_CC32E7B021A7Fbasavarajpatilnokiacom_"
MIME-Version: 1.0
X-OriginalArrivalTime: 23 Jul 2012 16:41:12.0162 (UTC) FILETIME=[F80CFC20:01CD68F1]
X-Nokia-AV: Clean
Subject: [netext] Comments on I-D: draft-bhandari-netext-pmipv6-dhcp-options
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <netext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netext>, <mailto:netext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netext>
List-Post: <mailto:netext@ietf.org>
List-Help: <mailto:netext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 16:40:39 -0000
Regarding the dhcp-options I-D: 1. I think it would be better served if this I-D was presented in the DHC WG 2. The MAG may host a DHCPv4 server… However the details of how such a DHCPv4 server gets the options that are relevant to an MN are outside the scope of Netext and the PMIP6 protocol IMHO. You could just as well deliver the specific options like SIP server address etc. to the MAG in the AAA response and deliver them to the DHCPv4 server collocated at the MAG. 3. The idea of doing PMIP6 signaling to the LMA to get DHCPv4 options for the server collocated at the MAG does not make sense IMO. What does the LMA have to do with DHCPv4 options? -Raj
- [netext] Comments on I-D: draft-bhandari-netext-p… Basavaraj.Patil