IETF Logo Mail Archive

Re: [netlmm] I-D Action:draft-ietf-netlmm-lma-discovery-05.txt

"Laganier, Julien" <julienl@qualcomm.com> Wed, 15 September 2010 22:34 UTC

Return-Path: <julienl@qualcomm.com>
X-Original-To: netlmm@core3.amsl.com
Delivered-To: netlmm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AB1E83A69E5 for <netlmm@core3.amsl.com>; Wed, 15 Sep 2010 15:34:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.578
X-Spam-Level:
X-Spam-Status: No, score=-106.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 DOZMib1r9CsZ for <netlmm@core3.amsl.com>; Wed, 15 Sep 2010 15:34:44 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id 575E13A697F for <netlmm@ietf.org>; Wed, 15 Sep 2010 15:34:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=julienl@qualcomm.com; q=dns/txt; s=qcdkim; t=1284590110; x=1316126110; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: acceptlanguage:content-type:content-transfer-encoding: mime-version; z=From:=20"Laganier,=20Julien"=20<julienl@qualcomm.com> |To:=20Behcet=20Sarikaya=20<sarikaya@ieee.org>,=20jouni =20korhonen=0D=0A=09<jouni.nospam@gmail.com>|CC:=20"netlm m@ietf.org"=20<netlmm@ietf.org>|Date:=20Wed,=2015=20Sep =202010=2015:35:07=20-0700|Subject:=20RE:=20[netlmm]=20I- D=20Action:draft-ietf-netlmm-lma-discovery-05.txt |Thread-Topic:=20[netlmm]=20I-D=20Action:draft-ietf-netlm m-lma-discovery-05.txt|Thread-Index:=20ActVDZz4+imKogyjT4 OEeRc0OLq7iQABm0nw|Message-ID:=20<BF345F63074F8040B58C00A 186FCA57F1F6826E63C@NALASEXMB04.na.qualcomm.com> |References:=20<20100913094506.6B51C3A6954@core3.amsl.com >=0D=0A=09<890653.19874.qm@web111402.mail.gq1.yahoo.com> =09<4C8EF580.7070700@gmail.com>=0D=0A=09<47245.1688.qm@we b111415.mail.gq1.yahoo.com>=0D=0A=09<CE4ECD0E-F23F-4FB3-9 CDB-BF33C46FCE23@gmail.com>=0D=0A=09<83313.87762.qm@web11 1402.mail.gq1.yahoo.com>=0D=0A=09<D0B210ED-DA43-42DB-BF54 -45225F4AA253@gmail.com>=0D=0A=20<706576.39689.qm@web1114 09.mail.gq1.yahoo.com>|In-Reply-To:=20<706576.39689.qm@we b111409.mail.gq1.yahoo.com>|Accept-Language:=20en-US |Content-Language:=20en-US|X-MS-Has-Attach: |X-MS-TNEF-Correlator:|acceptlanguage:=20en-US |Content-Type:=20text/plain=3B=20charset=3D"us-ascii" |Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0; bh=4/m8qn8BUwEtJwIvwfbhEwwm3FHEkNvtblI4tC8Z/qM=; b=EIM4xSY1e28vvHlDVx8EhJVeuVU0e/xvC4vmTUdHgUu/YtqjPu40Tw2u E48shLzH9Rv1Z1wU+3VzI6OHPRCeweV2EQ/neq1bwNt4yhJRXlxoA2iz3 Ouk3cxXqqBqGNfGpOSAHjy4VRSfppyCjGQpfb31vPRDU5v7E9USCQI9gL g=;
X-IronPort-AV: E=McAfee;i="5400,1158,6107"; a="54616214"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine01.qualcomm.com with ESMTP; 15 Sep 2010 15:35:09 -0700
X-IronPort-AV: E=Sophos;i="4.56,371,1280732400"; d="scan'208";a="2807157"
Received: from nasanexhub01.na.qualcomm.com ([10.46.93.121]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-MD5; 15 Sep 2010 15:35:09 -0700
Received: from nasanexhc06.na.qualcomm.com (172.30.48.3) by nasanexhub01.na.qualcomm.com (10.46.93.121) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 15 Sep 2010 15:35:09 -0700
Received: from nalasexhub04.na.qualcomm.com (10.47.130.55) by nasanexhc06.na.qualcomm.com (172.30.48.3) with Microsoft SMTP Server (TLS) id 14.0.694.0; Wed, 15 Sep 2010 15:35:08 -0700
Received: from NALASEXMB04.na.qualcomm.com ([10.47.7.118]) by nalasexhub04.na.qualcomm.com ([10.47.130.55]) with mapi; Wed, 15 Sep 2010 15:35:08 -0700
From: "Laganier, Julien" <julienl@qualcomm.com>
To: Behcet Sarikaya <sarikaya@ieee.org>, jouni korhonen <jouni.nospam@gmail.com>
Date: Wed, 15 Sep 2010 15:35:07 -0700
Thread-Topic: [netlmm] I-D Action:draft-ietf-netlmm-lma-discovery-05.txt
Thread-Index: ActVDZz4+imKogyjT4OEeRc0OLq7iQABm0nw
Message-ID: <BF345F63074F8040B58C00A186FCA57F1F6826E63C@NALASEXMB04.na.qualcomm.com>
References: <20100913094506.6B51C3A6954@core3.amsl.com> <890653.19874.qm@web111402.mail.gq1.yahoo.com> <4C8EF580.7070700@gmail.com> <47245.1688.qm@web111415.mail.gq1.yahoo.com> <CE4ECD0E-F23F-4FB3-9CDB-BF33C46FCE23@gmail.com> <83313.87762.qm@web111402.mail.gq1.yahoo.com> <D0B210ED-DA43-42DB-BF54-45225F4AA253@gmail.com> <706576.39689.qm@web111409.mail.gq1.yahoo.com>
In-Reply-To: <706576.39689.qm@web111409.mail.gq1.yahoo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "netlmm@ietf.org" <netlmm@ietf.org>
Subject: Re: [netlmm] I-D Action:draft-ietf-netlmm-lma-discovery-05.txt
X-BeenThere: netlmm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NETLMM working group discussion list <netlmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netlmm>
List-Post: <mailto:netlmm@ietf.org>
List-Help: <mailto:netlmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Sep 2010 22:34:45 -0000

Behcet Sarikaya wrote:
> > >>
> > >> IETF  can.. but does not have to. I like the current content  of
> > >> Section 7.
> > >>
> > >> For the record, the 3GPP boat has already sailed. Not much to  do
> > >> there.
> 
> Who should take the responsibility for this?

I am happy to take my share of responsibility for this. (and I bet Jouni as well, and some other people, too)

The 3GPP system architecture required LMA discovery features that are specific to that system architecture.

Thus neither of 3GPP relying on an IETF specification of these features, nor the IETF specifying features that are specific to the 3GPP system architecture made sense.

> Look back at the mail archive, Julien and Christian pointed at the
> right direction on DNS discovery long time ago.

I did not point at the *right* direction. 

I used *once*, for the sake of discussion, a strawman of a stateless DNS-based LMA discovery scheme that would deterministically load balance different MNs onto different LMAs.
 
> I have been shouting since then what should be done and having a
> dialogue des sourds with you and Jonne.

Isn't it usually the case that the one who shouts is the one that is hearing impaired? ;-)
 
> Anyways, DNS discovery is mission not accomplished in this draft.

>From my perspective this informational document fulfils its goal.

--julien

v2.23.0 | Report a Bug | By Email