Re: [netlmm] Last call for draft-ietf-netlmm-lma-discovery-03
jouni korhonen <jouni.nospam@gmail.com> Wed, 12 May 2010 18:54 UTC
Return-Path: <jouni.nospam@gmail.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 88BD728C0E7 for <netlmm@core3.amsl.com>; Wed, 12 May 2010 11:54:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.697
X-Spam-Level:
X-Spam-Status: No, score=-0.697 tagged_above=-999 required=5 tests=[AWL=-0.698, BAYES_50=0.001]
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 Xhopr-s6DSOE for <netlmm@core3.amsl.com>; Wed, 12 May 2010 11:54:07 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 274EE3A67E5 for <netlmm@ietf.org>; Wed, 12 May 2010 11:38:29 -0700 (PDT)
Received: by fxm7 with SMTP id 7so425467fxm.31 for <netlmm@ietf.org>; Wed, 12 May 2010 11:38:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=DbbJdGM5ouYq7JL3soCX7kFxztfXJzPGqFpCIxQ2B20=; b=q/l9zBPzYwmPoNLvbJj7wSz9OQ6800SNcDHx5Nm1Wucx5qErHQbtfDVtY+So53mynI NVVZBR8LuKNj4sbunkgTBDFJjGPcS4WLb4g6aWmrLTvH1UiOeLfX7cXEMLckj8DROeYx VtTxOxL6L5ridJqqmSKa16mM3184lpLaabVF8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=o75te9a0ZfanMjrQObRiuGnR+0UIK65xw4bL8K6TZm5EzXjUQfv++CJy3iVeIamhof w/MSAU7f1uDPm/wEzDNrLzpamcfQXT5nyjANf29ZCUY4bsASvqAZxQyaCYq4Z+Eubz7w VNrPanXZ17irErfySjfzqQVp4UQBLIS0xyOL8=
Received: by 10.223.24.85 with SMTP id u21mr8805446fab.8.1273689494704; Wed, 12 May 2010 11:38:14 -0700 (PDT)
Received: from a88-114-68-242.elisa-laajakaista.fi (a88-114-68-242.elisa-laajakaista.fi [88.114.68.242]) by mx.google.com with ESMTPS id g10sm1902481fai.0.2010.05.12.11.38.11 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 12 May 2010 11:38:12 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset="us-ascii"
From: jouni korhonen <jouni.nospam@gmail.com>
In-Reply-To: <4BE310F7.9070800@earthlink.net>
Date: Wed, 12 May 2010 21:38:10 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <EF4AF00E-4DFC-43B7-8E6A-8AF0383A60A3@gmail.com>
References: <4BE310F7.9070800@earthlink.net>
To: "Charles E. Perkins" <charles.perkins@earthlink.net>, "jonne.soininen@nsn.com FI/Espoo) Soininen" <jonne.soininen@nsn.com>, Vijay Devarapalli <vijay@wichorus.com>
X-Mailer: Apple Mail (2.1078)
Cc: NETLMM Mailing List <netlmm@ietf.org>
Subject: Re: [netlmm] Last call for draft-ietf-netlmm-lma-discovery-03
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, 12 May 2010 18:54:08 -0000
Hi Charlie, Thanks a bunch for your detailed comment. See my responses inline. On May 6, 2010, at 9:56 PM, Charles E. Perkins wrote: > > -------- Original Message -------- > Subject: Re: [netlmm] Last call for draft-ietf-netlmm-lma-discovery-03 > Date: Thu, 06 May 2010 11:54:15 -0700 > From: Charles E. Perkins <charles.perkins@earthlink.net> > Organization: Wichorus Inc. > To: Soininen, Jonne (NSN-FI/Espoo) <Jonne.Soininen@nsn.com>, Jouni Korhonen <jouni.korhonen@teliasonera.com>, Vijay Devarapalli <vijay@wichorus.com> > CC: <netlmm@ietf.org> > > Hello Jonne, > > Below, please find some initial comments on this document. > I think it needs at least one more revision, which should > be preceded by close proofreading. I'll send more comments > later. But first I am curious about your sentence: > > On 4/29/2010 1:16 AM, Soininen, Jonne (NSN-FI/Espoo) wrote: > >> As it seems that new reviews are coming to the document, >> it would be time to get this document over with. > > Usually, when a document gets more and more comments, > it's not taken as any good indication that the time > has come to get it over with...(??) > > ======================================================== > > About the document: > > "selecting LMA" --> "selecting a LMA" > BUT: > "selecting {a} LMA based on desired services" > -- are these extensions defined anywhere in > IETF documents? If so, please provide > relevant citations. Within IETF scope we have RFC5149. I'll put in an informative reference here. > > "a number of" --> "several" Ok. > > "a number of different ways" --> "various ways" > -- anyway, in this context no one would > say "a number of identical ways" > -- and moreover the entire sentence should > be deleted. Ok to delete "This document describes a number of possible dynamic LMA discovery solutions." > > "discussed in this specification" --> > "discussed in this document" > > I don't think the document is really intended > to be a full-blown specification. Ok. > > "LMA Address" --> "LMA IP address" Hmm.. RFC513 terminology defines "LMA Address" as the "The global address that is configured on the interface.." I rather keep using the LMA Address terminology. > > "LMA FQDN or IP address received from the lower layers during the > network attachment followed by an optional DNS lookup." > -- This sentence is wrong, because if the lower layer provides > an IP address, the DNS lookup would not happen. And if the Good catch. Will fix. > lower layer provides the FQDN, it's an interesting discussion > about why the DNS lookup is suddenly optional. Because of local configuration i.e. the MAG knows the mapping from FQDN to IP address? > >> When a MN performs a handover from one MAG to another, the new MAG >> must use the same LMA that the old MAG was using. This is required >> for session continuity. The LMA discovery mechanism used by the new >> MAG should be able to return the information about the same LMA that >> was being used by the old MAG. This document also discusses >> solutions for LMA discovery during a handover. > > I'm surprised to see this. Wasn't it considered controversial? I did not understand the "controversial" part of this comment. > > "support PMIPv6 functionality" --> "support PMIPv6" Ok. > > I think this document does not need to use any > instances of the ?word? "functionality", which leads > to additional, extraneous, excessive, unwarranted > verbosity. A bit too much, eh? Oh, and did I > mention ...? ;) > > "to authenticate to the network access" --> > "to provide authentication for network access" Ok. > > "the mobility services" --> "mobility services" Ok. > > "the Policy Profile download" > (a) if you want this included, a citation is needed. Would a reference to RFC5213 Appendix A be ok? > (b) but why even bring up policy management? It's > not germane to the solution except tangentially > insofar as AAA is often also part of policy > management. In RFC5213 there are few places where it is indicated that policy profile contains the information what we are after for. > (c) it would be easy to argue that this procedure is > NOT very much like RFC 5447. How is this helping > to illustrate the solution? I have no problem to remove "The procedure for the Policy Profile download resembles largely the client Mobile IPv6 Integrated Scenario bootstrapping [RFC5447]." if that helps with your concern. > >> This solution is identical to the procedure described in Section 2.1. >> The difference is > > Well, it's either identical or it's not. How about > "similar"? Ok. > > "LMA IP address(es)": > -- Please describe in more detail. Is it proposed to > use DNS to supply IP addresses for multiple independent > hosts? What are the security implications? Shouldn't > this be done by use of an anycast address? Hmm.. a LMA may have multiple interfaces, thus multiple addresses. These all can be populated into DNS. PMIPv6 anycast support is still in under works in netext. > -- The following discussion indicates that any such > multiplicity of IP addresses supplied for the LMA > creates the need for a new selection algorithm to > find the "right" LMA. Why is this a good idea? It might not be the best idea. Rather something that just gets deployed. > >> ... For example, the AAA server might return a generic >> LMA FQDN during the MN initial attach and once the LMA gets selected, >> return the LMA IP address during the subsequent attachments to other >> MAGs in the PMIPv6 domain. In order for this to work, the resolved >> and selected LMA IP address must be updated to the remote Policy >> Store. For example, the LMA could perform the update once it >> receives the initial PBU from the MAG for the new mobility session. > > (a) It isn't at all clear why Policy Store updates are a > necessary precondition for this -- unless of course you > generalize the meaning of Policy Store beyond all useful > recognition > (b) And anyway why bring it up? Well.. this is more or less the way some infamous architectures are going to work. > (c) How does the LMA get selected? MAG picks up one from a set it got from DNS.. > (d) What update does the LMA perform? ..updates its IP address to the remote policy store, for this particular mobility session. > (e) Is this discussion in any way important for someone > to understand how to resolve a FQDN for the LMA? Imho it reflects how things are going to be done in real deployments. > > "Lower Layers based Discovery Solutions" --> > "Discovery Solutions based on Data from Lower Layers" OK. > > "These solution could essentially" --> > "These solutions could essentially" -->? OK. > "These solution could" > <why "essentially"??> Would it be better if I remove "essentially" from that sentence? I would be ok to rephrase. > > "without the AAA" ->> "without any AAA" OK. > > "mobile node Identity" --> "Mobile Node Identity" OK. > > "equals to the" --> "equals the" --> "is the same as" OK (going to use the "is the same as"). > > "MAG receives" --> "MAG may receive" OK. > >> (or actually the subscription identity >> but from now on we assume that the MN identity equals to the >> subscription identity, which is a rather broad simplification) > > Since the subscription identity _is_ one of the > identities of the MN, this parenthetical comment > is not needed. And, anyway, you didn't define > subscription identity. You don't need to do that. > I don't see how it would help the explanation. Right. I will remove "(or actually the subscription identity but from now on we assume that the MN identity equals to the subscription identity, which is a rather broad simplification)" ? > > "information elements that can be extracted and at > minimum used" > --> > "information that can be used" OK. > >> Thus the MN identity in this solution cannot be a "flat" >> identity without any structure and "clear text" parts containing the >> hosting entity information. > > This sentence should be deleted. And, anyway, it is > by no means required that the information which > identifies the hosting entity has to be in clear text. OK. > > "operator owning the given subscription" > -- I thought the subscriber owned the subscription. > O.K... perhaps operators act like they own the > subscriber, but still I must protest. ;) Now that I read it again after your "protest" it indeed sounds.. erm.. wrong. Do you have a better wording in mind? > > ========================================================================= > > Regards, > Charlie P. Thanks, Jouni > _______________________________________________ > netlmm mailing list > netlmm@ietf.org > https://www.ietf.org/mailman/listinfo/netlmm >
- [netlmm] Last call for draft-ietf-netlmm-lma-disc… Soininen, Jonne (NSN-FI/Espoo)
- Re: [netlmm] Last call for draft-ietf-netlmm-lma-… Frank Xia
- Re: [netlmm] Last call for draft-ietf-netlmm-lma-… Soininen, Jonne (NSN-FI/Espoo)
- Re: [netlmm] Last call for draft-ietf-netlmm-lma-… Frank Xia
- Re: [netlmm] Last call for draft-ietf-netlmm-lma-… Soininen, Jonne (NSN-FI/Espoo)
- Re: [netlmm] Last call for draft-ietf-netlmm-lma-… Frank Xia
- Re: [netlmm] Last call for draft-ietf-netlmm-lma-… Soininen, Jonne (NSN-FI/Espoo)
- [netlmm] Please evaluate DHCP LMA discovery scena… Frank Xia
- Re: [netlmm] Last call for draft-ietf-netlmm-lma-… Charles E. Perkins
- Re: [netlmm] Last call for draft-ietf-netlmm-lma-… Soininen, Jonne (NSN-FI/Espoo)
- Re: [netlmm] Last call for draft-ietf-netlmm-lma-… Charles E. Perkins
- Re: [netlmm] Last call for draft-ietf-netlmm-lma-… jouni korhonen
- Re: [netlmm] Last call for draft-ietf-netlmm-lma-… jouni korhonen
- Re: [netlmm] Last call for draft-ietf-netlmm-lma-… Behcet Sarikaya
- Re: [netlmm] Last call for draft-ietf-netlmm-lma-… Jouni