Subject: RE: [Mip6] [draft-ietf-mip6-bootstrapping-split-00] Issue 53

From: Gerardo Giaretta <[email-masked]>
Date: Mon, 10 Oct 2005 22:06:03 +0200

Based on discussion among authors, the proposed text for section 5.1.1 to solve this issue is the following:

-------------------------------------------

5.1.1. DNS lookup by Home Agent Name

In this case, the Mobile Node is configured with the Fully Qualified Domain Name of the Home Agent. As an example, the Mobile Node could be configured with the name "ha1.example.com", where "example.com" is the domain name of the MSP granting the mobility service. 

The Mobile Node constructs a DNS request, by setting the QNAME to the name of the Home Agent. The request has QTYPE set to 'AAAA', so that the DNS server sends the IPv6 address of the Home Agent. Once the DNS server replies to this query, the Mobile Node knows its Home Agent address and can run IKEv2 in order to set up an IPsec SA and get a Home Address.

Additionally, the ability to provide a mobile node with a localized home agent (e.g. on the visited link) can help to optimize handover signaling. There are a variety of ways this can be achieved in an interoperable way. One way is to provision the mobile node with an FQDN for a local home agent when it configures for the local link. Another way is to specify an interoperable naming convention for constructing home agent FQDNs based on location. For example, an operator might assign the FQDN "ha.locationA.operator.com" to the Home Agent located in "location A" and the FQDN "ha.locationB.operator.com" to the Home Agent located in "location B". If the Mobile Node wants to use a Home Agent located in "location A", it will set the QNAME to "ha.locationA.operator.com" in the DNS request. The exact way in which localized Home Agents are configured is out of scope for this draft.

-------------------------------------------

I think we can consider the issue closed now. Please let me know if you have problem with that.

--Gerardo

> -----Original Message-----
> From: Yoshihiro Ohba [mailto:[email-masked]] 
> Sent: giovedì 6 ottobre 2005 2.05
> To: Vijay Devarapalli
> Cc: Yoshihiro Ohba; Gerardo Giaretta; [email-masked]
> Subject: Re: [Mip6] [draft-ietf-mip6-bootstrapping-split-00] Issue 53
> 
> Hi Vijay,
> 
> On Wed, Oct 05, 2005 at 04:33:58PM -0700, Vijay Devarapalli wrote:
> > Yoshihiro Ohba wrote:
> > > As I don't believe we can come up with an acceptable 
> canonical name
> > > for local HA naming, I prefer solution 1.  Also, does the 
> following
> > > example in the first paragraph of section 5.1.1 give much 
> insights to
> > > implementors to understand how to configure an HA name?  
> If not, I'd
> > > prefer just removing it.
> > > 
> > > "
> > >   As an example, the Mobile Node could be configured with the name
> > >   "ha1.example.com", where "example.com" is the domain 
> name of the MSP
> > >   granting the mobility service.
> > 
> > just to make sure. Yoshi, you are saying the entire
> > section 5.1.1 needs to be removed. 
> 
> No.  My opinion is:
> 
> - Section 5.1.1 should exist.
> 
> - The last paragraph of section 5.1.1 is not needed.
> 
> - Importance of the last sentence of the first paragraph (quoted
> above) of section 5.1.1 is questionable.  (I know this part is not
> what is being discussed here, but just a comment.)
> 
> Regards,
> 
> Yoshihiro Ohba
> 
> 
> > not just the last
> > paragraph which describes HA lookup by location (which
> > is what is being discussed here).
> > 
> > Vijay
> > 
> > > "
> > > 
> > > Regards,
> > > 
> > > Yoshihiro Ohba
> > > 
> > > On Wed, Oct 05, 2005 at 07:29:24PM +0200, Gerardo Giaretta wrote:
> > > 
> > >>I would like to hear your thoughts about issue #53 in
> > >>draft-ietf-mip6-bootstrapping-split-00. 
> > >>
> > >>The current version of the draft states:
> > >>
> > >>        Additionally, it could be useful to provide an 
> ability for the
> > >>Mobile 
> > >>        Node to discover a Home Agent placed in a 
> particular location
> > >>(e.g. 
> > >>        on the visited link). In order to achieve this, 
> the Mobile Node
> > >>must 
> > >>        be able to construct a DNS request such that the 
> DNS server will
> > >>be 
> > >>        able to reply with a Home Agent from the 
> requested location.
> > >>This can 
> > >>        be accomplished by using a specific  naming 
> convention for the
> > >>FQDNs 
> > >>        of the Home Agents. As an example, an operator 
> might assign the
> > >>FQDN 
> > >>        "ha.locationA.operator.com" to the Home Agent located in
> > >>"location A" 
> > >>        and the FQDN "ha.locationB.operator.com" to the Home Agent
> > >>located in 
> > >>        "location B". If the Mobile Node wants to use a Home Agent
> > >>located in 
> > >>        "location A", it will set the QNAME to
> > >>"ha.locationA.operator.com" in 
> > >>        the DNS request.         
> > >>
> > >>In his review, Jari mentioned:
> > >>"Possible, but the description is mostly handwaving and 
> would probably
> > >>benefit from a more generic solution in any case. Suggest
> > >>removing this"
> > >>
> > >>Based on the discussion we've had so far, we have two 
> possible options:
> > >>
> > >>1. remove the text and do not provide a way in
> > >>draft-ietf-mip6-bootstrapping-split to identify whether 
> or not the HA is
> > >>local (based on Jari comment)
> > >>
> > >>2. define a canonical local HA naming convention for 
> interoperability
> > >>
> > >>Please provide your comments.
> > >>
> > >>
> > >>--Gerardo
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>Gruppo Telecom Italia - Direzione e coordinamento di 
> Telecom Italia S.p.A.
> > >>
> > 
> >>====================================================================
> > >>CONFIDENTIALITY NOTICE
> > >>This message and its attachments are addressed solely to 
> the persons
> > >>above and may contain confidential information. If you 
> have received
> > >>the message in error, be informed that any use of the 
> content hereof
> > >>is prohibited. Please return it immediately to the sender 
> and delete
> > >>the message. Should you have any questions, please send 
> an e_mail to 
> > >>[email-masked]. Thank you
> > 
> >>====================================================================
> > >>
> > >>_______________________________________________
> > >>Mip6 mailing list
> > >>[email-masked]
> > >>https://www1.ietf.org/mailman/listinfo/mip6
> > >>
> > >>
> > > 
> > > 
> > > _______________________________________________
> > > Mip6 mailing list
> > > [email-masked]
> > > https://www1.ietf.org/mailman/listinfo/mip6
> > 
> > 
> > 
> 

Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A.

====================================================================
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
[email-masked]. Thank you
====================================================================

_______________________________________________
Mip6 mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/mip6