IETF Logo Mail Archive

Re: [DMM] WGLC #2 for draft-ietf-dmm-lma-controlled-mag-params-01

"Dhananjay Patki (dhpatki)" <dhpatki@cisco.com> Fri, 01 July 2016 04:04 UTC

Return-Path: <dhpatki@cisco.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A71312D0B3 for <dmm@ietfa.amsl.com>; Thu, 30 Jun 2016 21:04:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level:
X-Spam-Status: No, score=-15.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24gThQttmfGk for <dmm@ietfa.amsl.com>; Thu, 30 Jun 2016 21:03:59 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24E6412B049 for <dmm@ietf.org>; Thu, 30 Jun 2016 21:03:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3750; q=dns/txt; s=iport; t=1467345839; x=1468555439; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=3d5ts9Y7Wh/fB1gcPD3vqbN1knj/59EsSaNDCJKeqys=; b=Vxp+Om7sdBoguSoRemgWLrgfQWOiNtTQL+3ElNHM8MmzjnGfVXQOqsTT J3WMXhAYpEVZZDEHOhg5fGqnk9svUOY9f2VIaMljgKCODpApkh1SHDso+ gk/aTigT2JLyMoYarzC1ppvdBXFKxBXtwVF/lBratbLTCZz089ouG6v8i Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BtAgBP63VX/51dJa1bgz5WfAatPowQgXsihXYCHIEXOBQBAQEBAQEBZSeETAEBBQEBIQQNOgsMBAIBBgIRAwEBAQMCIwMCAgIfBgsUAQgIAgQBDQWIFgMXDpZanR2Lcw2EGwEBAQEBAQEBAQEBAQEBAQEBAQEBARcFgQGFJ4F3CIJOgkOBTxEBHIMBK4IvAQSYWTQBjDWCC4FqhFaDLoU8hlWBQIdyAR42g3Buhz82fwEBAQ
X-IronPort-AV: E=Sophos;i="5.26,555,1459814400"; d="scan'208";a="124584507"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Jul 2016 04:03:58 +0000
Received: from XCH-RTP-016.cisco.com (xch-rtp-016.cisco.com [64.101.220.156]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id u6143vBv004008 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 1 Jul 2016 04:03:58 GMT
Received: from xch-rtp-018.cisco.com (64.101.220.158) by XCH-RTP-016.cisco.com (64.101.220.156) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 1 Jul 2016 00:03:57 -0400
Received: from xch-rtp-018.cisco.com ([64.101.220.158]) by XCH-RTP-018.cisco.com ([64.101.220.158]) with mapi id 15.00.1210.000; Fri, 1 Jul 2016 00:03:57 -0400
From: "Dhananjay Patki (dhpatki)" <dhpatki@cisco.com>
To: Seil Jeon <seiljeon@gmail.com>, "dmm@ietf.org" <dmm@ietf.org>
Thread-Topic: [DMM] WGLC #2 for draft-ietf-dmm-lma-controlled-mag-params-01
Thread-Index: AQHRwN/4/qonvF22F0aWWuoy7u5RJZ/z+iCAgA++jgA=
Date: Fri, 01 Jul 2016 04:03:57 +0000
Message-ID: <1CEA0AB4-9209-488C-8053-0762A6EAA0D0@cisco.com>
References: <102c26e2-5916-e029-329d-d70efe1ebe88@gmail.com> <002f01d1cb9c$6c08d570$441a8050$@gmail.com>
In-Reply-To: <002f01d1cb9c$6c08d570$441a8050$@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/0.0.0.160109
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.86.9]
Content-Type: text/plain; charset="utf-8"
Content-ID: <0DDB2F55CB1B2743A299E65608DB33B6@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/eL0w98xgvyJ_J3dHfoX76AO0Bzg>
Cc: '成 鹏' <max.ldp@alibaba-inc.com>
Subject: Re: [DMM] WGLC #2 for draft-ietf-dmm-lma-controlled-mag-params-01
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jul 2016 04:04:01 -0000

Hi Siel,

Please see inline.
--
Regards,
Dhananjay

-----Original Message-----



From: dmm <dmm-bounces@ietf.org> on behalf of Seil Jeon <seiljeon@gmail.com>
Date: Tuesday, 21 June 2016 at 2:38 PM
To: "dmm@ietf.org" <dmm@ietf.org>
Cc: '成 鹏' <max.ldp@alibaba-inc.com>, "dmm@ietf.org" <dmm@ietf.org>
Subject: Re: [DMM] WGLC #2 for draft-ietf-dmm-lma-controlled-mag-params-01

>Hi,
>
>I have read this draft and some questions come to my mind. Let me know my
>understanding is correct or not first.
>
>Actually, this draft comes to a proposed container option to be delivered by
>a PBA message, enabling the LMA to put various parameters related to the MAG
>enforcement, not doing it individually for less signaling overhead(?)

[Dhananjay] By ‘doing it individually’ do you mean separate options (instead of sub-options) for Binding Update Control and Heartbeat Control? The idea is to keep all such LMA controlled parameters grouped into a single container option.


>
>And when I saw following sentence
>
>"Configuring aggressive values of parameters such as re-registration timeout
>and heartbeat interval can potentially create considerable signaling load on
>the LMA."
>
>I was expecting you would take care of it in terms of efficient transmission
>perspective as well. Is it out-of-scope, right?

[Dhananjay] This extension is only to communicate the values enforced by the LMA to the MAG. Tuning of the value for efficient transmission is out of scope of this extension. The above sentence is only to state a caution which is applicable even without using this extension.

>
>
>
>Two minor typos are,
>
>In Introduction, aggresive -> aggressive
>
>in 5.2, reveived -> received(?)

[Dhananjay] Thanks for pointing these out. I am correcting these in the next version.

Regards,
Dhananjay

>
>
>Regards,
>Seil Jeon
>
>
>
>-----Original Message-----
>From: dmm [mailto:dmm-bounces@ietf.org] On Behalf Of Jouni Korhonen
>Sent: Wednesday, June 08, 2016 2:14 AM
>To: dmm@ietf.org; Jouni; 成 鹏
>Subject: [DMM] WGLC #2 for draft-ietf-dmm-lma-controlled-mag-params-01
>
>Folks,
>
>This email starts the WGLC #2 for
>draft-ietf-dmm-lma-controlled-mag-params-01. Post your comment to the
>mailing list and also add your issues/correction requests/concerns etc into
>the Issue Tracker.
>
>     WGLC #2 Starts: 6/7/2016
>     WGLC #2 Ends: 6/21/2016 EOB PDT
>
>Regards,
>     Jouni & Dapeng
>
>_______________________________________________
>dmm mailing list
>dmm@ietf.org
>https://www.ietf.org/mailman/listinfo/dmm
>
>_______________________________________________
>dmm mailing list
>dmm@ietf.org
>https://www.ietf.org/mailman/listinfo/dmm

v2.23.0 | Report a Bug | By Email