[Dime] draft-ietf-dime-pmip6-lr open issue

Qin Wu <sunseawq@huawei.com> Wed, 16 March 2011 02:19 UTC

Return-Path: <sunseawq@huawei.com>
X-Original-To: dime@core3.amsl.com
Delivered-To: dime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D07DE3A6B5B for <dime@core3.amsl.com>; Tue, 15 Mar 2011 19:19:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.916
X-Spam-Level:
X-Spam-Status: No, score=-3.916 tagged_above=-999 required=5 tests=[AWL=0.578, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ondxZB2FjYzp for <dime@core3.amsl.com>; Tue, 15 Mar 2011 19:19:47 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id C1D1D3A6B17 for <dime@ietf.org>; Tue, 15 Mar 2011 19:19:46 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LI400GBDP71PI@szxga03-in.huawei.com> for dime@ietf.org; Wed, 16 Mar 2011 10:21:01 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LI400GSUP71I1@szxga03-in.huawei.com> for dime@ietf.org; Wed, 16 Mar 2011 10:21:01 +0800 (CST)
Received: from w53375 ([10.138.41.70]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LI40011CP71SI@szxml06-in.huawei.com> for dime@ietf.org; Wed, 16 Mar 2011 10:21:01 +0800 (CST)
Date: Wed, 16 Mar 2011 10:21:01 +0800
From: Qin Wu <sunseawq@huawei.com>
To: dime@ietf.org
Message-id: <02b301cbe380$cb55d4b0$46298a0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Outlook Express 6.00.2900.3664
Content-type: multipart/alternative; boundary="Boundary_(ID_mmq3bZ11QoUuo5iWy6E/1g)"
X-Priority: 3
X-MSMail-priority: Normal
Subject: [Dime] draft-ietf-dime-pmip6-lr open issue
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Mar 2011 02:19:48 -0000

Hi,
The open issue discussed in the IETF 79 beijing meeting is described as follows:
In some cases (e.g., in figure 2,3,4), the Diameter Server need to return MN's LMA address while in some other case 
(e.g.,the authorization of the MAG location query in figure 5), the Diameter Server needs not return MN's LMA address.

I think it will good to keep AAA procedure in all cases exactly the same and also it does not hurt to return the LMA address in all cases. 
 If the receiver does not need that information, it can just ignore the AVP containing LMA. So we have two proposals:
Proposal 1: Does not need to differentiate different success cases, return the same AVP containing LMA address.

Propsoal 2: Differentiate different success cases using status code and return the same AVP containing LMA address

Any opinions?

Regards!
-Qin