RE: [MIPSHOP-MIH-DT] DNS SRV records

<Gabor.Bajko@nokia.com> Wed, 05 December 2007 20:32 UTC

Return-path: <mipshop-mih-dt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J00v3-0005vr-5z; Wed, 05 Dec 2007 15:32:33 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J00v1-0005o9-Vd for mipshop-mih-dt@ietf.org; Wed, 05 Dec 2007 15:32:32 -0500
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J00v1-0004FA-Ak for mipshop-mih-dt@ietf.org; Wed, 05 Dec 2007 15:32:31 -0500
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id lB5KW5xg015722; Wed, 5 Dec 2007 22:32:24 +0200
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 5 Dec 2007 22:32:01 +0200
Received: from daebe103.NOE.Nokia.com ([10.241.35.24]) by daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 5 Dec 2007 14:31:59 -0600
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MIPSHOP-MIH-DT] DNS SRV records
Date: Wed, 05 Dec 2007 14:31:56 -0600
Message-ID: <E5E76343C87BB34ABC6C3FDF3B31272701CCA523@daebe103.NOE.Nokia.com>
In-Reply-To: <4756F93C.1050409@azairenet.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [MIPSHOP-MIH-DT] DNS SRV records
Thread-Index: Acg3c5NLqMLBcNE6TTi6nMF/yC5TqwACN8DQ
References: <4756E9A9.6070300@azairenet.com> <E5E76343C87BB34ABC6C3FDF3B31272701C217A9@daebe103.NOE.Nokia.com> <4756F93C.1050409@azairenet.com>
From: Gabor.Bajko@nokia.com
To: vijay.devarapalli@AzaireNet.com
X-OriginalArrivalTime: 05 Dec 2007 20:31:59.0119 (UTC) FILETIME=[E289F1F0:01C8377D]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: mipshop-mih-dt@ietf.org
X-BeenThere: mipshop-mih-dt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: MIPSHOP Media Independent Handover Design Team List <mipshop-mih-dt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt>, <mailto:mipshop-mih-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www1.ietf.org/mailman/private/mipshop-mih-dt>
List-Post: <mailto:mipshop-mih-dt@ietf.org>
List-Help: <mailto:mipshop-mih-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt>, <mailto:mipshop-mih-dt-request@ietf.org?subject=subscribe>
Errors-To: mipshop-mih-dt-bounces@ietf.org

Vijay,


NAPTR records provide a mapping from a domain to the SRV record for
contacting a server with the specific transport protocol in the NAPTR
services field.

The NAPTR record lets you to look at a specific service in a specific
domain. The response will tell you if whether that domain has a server
or not, and if yes, what kind of transport protocol and the order of
preference. Once you have that information, you can construct an SRV
record to find the server which provides the service with the desired
transport.

In the example you gave you made the assumption that the domain hosts an
mih service using udp.

- gabor

-----Original Message-----
From: ext Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com] 
Sent: Wednesday, December 05, 2007 11:17 AM
To: Bajko Gabor (Nokia-SIR/MtView)
Cc: mipshop-mih-dt@ietf.org
Subject: Re: [MIPSHOP-MIH-DT] DNS SRV records

Gabor.Bajko@nokia.com wrote:
> We are using NAPTR records, SRV record is not enough for the 
> discovery, as we do not know the fqdn of the server(s).

I am probably missing some context then. I haven't really followed the
discussions so far. Sorry about that.

But a question on SRV records. You would be creating a label, something
like "_mih._udp.example.com". You would then set aside a new SRV record
for the above label. Then the mobile node would be configured to do a
DNS lookup based on the above label. example.com can be translated into
any realm.

Isn't this sufficient? Not clear why you need NAPTR records.

Vijay

> But thanks for the pointer.
> 
> - gabor
>  
> 
> -----Original Message-----
> From: ext Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> Sent: Wednesday, December 05, 2007 10:11 AM
> To: mipshop-mih-dt@ietf.org
> Subject: [MIPSHOP-MIH-DT] DNS SRV records
> 
> I was chatting with Telemaco this morning and he told me that you guys

> are writing a draft on reserving a new DNS SRV record.
> DNS SRV records are not maintained by the IANA (no IETF involvement).
> The SRV records are maintained at
> 
> http://www.dns-sd.org/ServiceTypes.html
> 
> You just need to send an email to add a new SRV record.
> 
> There is some discussion on using DNS SRV records for MIPv6 home agent

> lookup. See section 5.1.2 of RFC 5026.
> 
> Vijay
> 
> _______________________________________________
> MIPSHOP-MIH-DT mailing list
> MIPSHOP-MIH-DT@ietf.org
> https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt


_______________________________________________
MIPSHOP-MIH-DT mailing list
MIPSHOP-MIH-DT@ietf.org
https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt