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

Behcet Sarikaya <behcetsarikaya@yahoo.com> Tue, 14 September 2010 19:36 UTC

Return-Path: <behcetsarikaya@yahoo.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 32A4D3A6A7E for <netlmm@core3.amsl.com>; Tue, 14 Sep 2010 12:36:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.982
X-Spam-Level:
X-Spam-Status: No, score=-1.982 tagged_above=-999 required=5 tests=[AWL=0.283, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 Vwsu5YTp5xtL for <netlmm@core3.amsl.com>; Tue, 14 Sep 2010 12:36:58 -0700 (PDT)
Received: from web111402.mail.gq1.yahoo.com (web111402.mail.gq1.yahoo.com [67.195.15.138]) by core3.amsl.com (Postfix) with SMTP id 100323A6A99 for <netlmm@ietf.org>; Tue, 14 Sep 2010 12:36:58 -0700 (PDT)
Received: (qmail 93003 invoked by uid 60001); 14 Sep 2010 19:37:23 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1284493043; bh=mIF1D3OscUDeTRA/rf+joRibV26+1FRpZNjmXOK1NPM=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=e+oda4Q0N55HP2uGnpZNYIGX0G7eSoAnmHIDLB6u94TYqQeLQIC5LLyN2k7Zk9zrVI9QL0fuwV2rIFGPYlJyS1d3Gq/YzM1L3d3L7sSjvVh0aN1kcFw056ko+a/vAAdyrXtrnjelRu8peTMY9bzMCy2W7Z/p+MoTQuDMXsTv9Z4=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=Adf5gweMznwHOYktdHPQJ1KmOOf+s3IBjBoVUjjDq1LKHZUQ1mmT6efvY/x69ABARy9X4F0sjczstQbX1Ke8Me3yczGC2oWRCQyFt780MvUE+IfyySkQ+v9AzkhsEtldt1yxIimewPZDM8Laviint8e/wP53l7UPE6M+1/9qoLQ=;
Message-ID: <83313.87762.qm@web111402.mail.gq1.yahoo.com>
X-YMail-OSG: SWXNOyYVM1lgImlCGAAVmRgJyWeuTNzZOY2cLpBY_voN3jf bW0JHAMRdtPNcHR642BFpFXPvngY8l1k1iYQmnYmxbteOtgYPnI3XqodUhS6 bpKos2PT18fvH5eJSTcA0p72CJqr3tA1d86Iysm_rRQ1sE2jBigkhMmfnU1C eV7KwJcX7_WGPoJiJY3mPjI1wTaEtd_onWME_zr1tEHbHQGhbXBrXcizx1bs 8daYmBFBURt_jk23E4lKs61nWzoAzCOxtuLZ8JY3bHzU1FwnrGCDwGru0fHl .29rjzQsphrUfupFktdmpkiVz4HB6vG5ttJiTfee8yS_rEaYSdrgsYYwunYD EdrLR8aoJcCTSxc_5zy1w.cF4G3qpYs.QvWj9tWs-
Received: from [206.16.17.212] by web111402.mail.gq1.yahoo.com via HTTP; Tue, 14 Sep 2010 12:37:22 PDT
X-Mailer: YahooMailRC/470 YahooMailWebService/0.8.105.279950
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>
Date: Tue, 14 Sep 2010 12:37:22 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: jouni korhonen <jouni.nospam@gmail.com>
In-Reply-To: <CE4ECD0E-F23F-4FB3-9CDB-BF33C46FCE23@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: 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
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
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: Tue, 14 Sep 2010 19:36:59 -0000

Hi Jouni,



----- Original Message ----
> From: jouni korhonen <jouni.nospam@gmail.com>
> To: Behcet Sarikaya <sarikaya@ieee.org>
> Cc: Vijay Devarapalli <dvijay@gmail.com>om>; netlmm@ietf.org
> Sent: Tue, September 14, 2010 11:43:27 AM
> Subject: Re: [netlmm] I-D Action:draft-ietf-netlmm-lma-discovery-05.txt
> 
> Hi Behcet,
> 
> 
> On Sep 14, 2010, at 6:52 PM, Behcet Sarikaya  wrote:
> 
> > 
> > ----- Original Message ----
> >> From: Vijay  Devarapalli <dvijay@gmail.com>
> >> To: Behcet  Sarikaya <sarikaya@ieee.org>
> >> Cc: Behcet  Sarikaya <behcetsarikaya@yahoo.com>om>; jouni  korhonen 
> >> <jouni.nospam@gmail.com>om>; netlmm@ietf.org
> >> Sent: Mon,  September 13, 2010 11:09:36 PM
> >> Subject: Re: [netlmm] I-D  Action:draft-ietf-netlmm-lma-discovery-05.txt
> >> 
> >> On  9/13/10 3:49 PM, Behcet Sarikaya wrote:
> >>> Hi  Jouni,
> >>>    Thanks for updating the  draft.
> >>> Reading it I noticed that in  Section 3.3on  Constructing the LMA FQDN from 
>
>a
> >>> Service   Name
> >>> 
> >>> 
> >>> 
> >>> can you  please mention a service name in  QNAME format:
> >>> "_pmip6_ipv6.example.com"
> >>>  where example.com can come  from MN's  NAI or the operator domain.
> >> 
> >> No, PMIPv6  is not a service. So we shouldn't  do this.
> > 
> > Why not? mip6  IS a service name. We do need pmip6 service name as well, 
>don't 
>
> > you  think?
> > 
> > Also reading the draft's Section 3.3 on service name  (Constructing the LMA 
>FQDN 
>
> > from a Service Name to be precise), it  totally sounds like a 3GPP document.
> > Remember this is IETF work. IETF  defined DNS and PMIPv6. 
> 
> I assume you did not notice the references that  were given as examples in 
>Section 3.3? They totally seem to point in 3GPP's  general direction.


Of course I did. I know that 3GPP does favor DNS discovery, in almost everything 

they use DNS discovery. 

> 
> > IETF can define a service name which is operator  and SDO independent. If 
>such a 
>
> > service name is defined, there is even  no need to standardize it in other 
>SDOs 
>
> > like 3GPP. Operators can use it  immediately.
> 
> 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.
> 

I guess you mean 
19.4.3    Service and Protocol service names for 3GPP 
in 23.003. Yes they defined service names for pmip like 3gpp-pgw:x-s8-pmip 
indicating s8 interface on a P-GW.

Of course this is good and maybe you should specifically mention this in Sec. 
3.3.

However the above service name is 3GPP specific. I think it is advisable to 
define an IETF service name so that everybody can use it.

These are my points.


Regards,

Behcet