[netext] Comments on I-D: draft-tu-netext-mn-status-option-02.txt
<Basavaraj.Patil@nokia.com> Mon, 23 July 2012 17:23 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 C77B421F85FC for <netext@ietfa.amsl.com>; Mon, 23 Jul 2012 10:23:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.576
X-Spam-Level:
X-Spam-Status: No, score=-106.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, 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 5QQw0hvnkvSf for <netext@ietfa.amsl.com>; Mon, 23 Jul 2012 10:23:56 -0700 (PDT)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by ietfa.amsl.com (Postfix) with ESMTP id 1FD3B21F861B for <netext@ietf.org>; Mon, 23 Jul 2012 10:23:55 -0700 (PDT)
Received: from vaebh102.NOE.Nokia.com (in-mx.nokia.com [10.160.244.23]) by mgw-da01.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q6NHNn7w012379 for <netext@ietf.org>; Mon, 23 Jul 2012 20:23:53 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.59]) by vaebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Mon, 23 Jul 2012 20:24:30 +0300
Received: from 008-AM1MPN1-072.mgdnok.nokia.com ([169.254.2.83]) by 008-AM1MMR1-004.mgdnok.nokia.com ([65.54.30.59]) with mapi id 14.02.0283.004; Mon, 23 Jul 2012 19:23:50 +0200
From: Basavaraj.Patil@nokia.com
To: netext@ietf.org
Thread-Topic: Comments on I-D: draft-tu-netext-mn-status-option-02.txt
Thread-Index: AQHNaPfsr+OVqfbzHEuWSUjuqpiZjg==
Date: Mon, 23 Jul 2012 17:23:49 +0000
Message-ID: <CC32F2DC.21AAE%basavaraj.patil@nokia.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: text/plain; charset="us-ascii"
Content-ID: <460B04D5E699B140B96D38D617FF6F0F@mgd.nokia.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 23 Jul 2012 17:24:30.0278 (UTC) FILETIME=[04A60660:01CD68F8]
X-Nokia-AV: Clean
Subject: [netext] Comments on I-D: draft-tu-netext-mn-status-option-02.txt
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 17:23:56 -0000
Hello, The proposal of sending additional information related to the MNs connectivity state is no doubt useful and can help the LMA make a more informed decision about switching flows. However I am trying to understand how the MAG gets such access/interface specific information. Do you expect the access network to provide such information on a per MN basis? There is an implicit assumption that the MAG has access to resource information that is maintained by nodes in the access network. Is that the case? -Raj
- [netext] Comments on I-D: draft-tu-netext-mn-stat… Basavaraj.Patil
- Re: [netext] Comments on I-D: draft-tu-netext-mn-… tu.yangwei
- Re: [netext] Comments on I-D: draft-tu-netext-mn-… Basavaraj.Patil