Subject: Re: RE: RE: [Mip6] I-D ACTION:draft-ietf-mip6-hiopt-03.txt

From: Heejin Jang <[email-masked]>
Date: Tue, 05 Jun 2007 07:55:37 +0000 (GMT)

Hi, Domagoj.
Kindly see the inline.

- Regards
Heejin. 

------- Original Message -------
Sender : Premec, Domagoj<[email-masked]>
Date   : 2007-06-04 17:30
Title  : RE: RE: [Mip6] I-D ACTION:draft-ietf-mip6-hiopt-03.txt

Hi Heejin,

> In my answer, "a single Home Network information option with 
> multiple sub-options" means per each a single Home Network 
> Identifier option.

OK, I misunderstood this sentence, I thought that there will be a total of 1 HN information option in the response.

> That is, the number of HN Information 
> option in the reply is the same as the number of HN 
> Information option in the request, and the "id-type" will be 
> added in an HN information option for mapping for each 
> option. We fixed this and the next version will cover this.

Mobile node can include several HN Identifier options with the same id-tpye (1) in its request. In this case including the id-type in an HN information option will not be enough to enable the matching. One possibility may be to require that the HN information options appear in the same order as HN Identifier options and that the matching is based on the sequential order of options.

Heejin >> Right. HN Information options with the same id-type without any mapping info could be problematic. 
Sequential ordering can be one way, and adding mapping identifier in HN info/identfier options can be another which
looks rather complicated. We'll reflect this point during udpate. Thanks for your helpful comments. :)

thanks
domagoj

> -----Original Message-----
> From: Heejin Jang [mailto:[email-masked]] 
> Sent: 04. lipanj 2007 03:35
> To: Premec, Domagoj; [email-masked]
> Cc: [email-masked]
> Subject: Re: RE: [Mip6] I-D ACTION:draft-ietf-mip6-hiopt-03.txt
> 
> Hi, Domagoj.
> Thanks for your comment.
>  
> A few days ago, I answered as follows for Kilian&#39;s question in ML.
>  
> Kilian&#39;s Q> What should the DHCP server do if the MIP6 relay 
> agent option contains multiple sub-options and one of the 
> sub-options matches the NAI&#39;s realm whereas another one does 
> not? This situation can happen if the AAAH sends home network 
> information for mutliple MSPs to the NAS (e.g., for home 
> MSP/MSA and other MSPs with trust relationship to MSA). 
> Should the server respond with multiple Home Network 
> Information Sub-options?
>  
> Heejin&#39;s A> A DHCP server extracts only the available HA info 
> among the info privided by NAS (finally from AAA) and 
> includes them in a single Home Network information option 
> with multiple sub-options. If the server has no info for the 
> specified id-type in Home Network, then it replies with 
> opt-len=0 in a Home Network Information option.
>  
> In my answer, "a single Home Network information option with 
> multiple sub-options" means per each a single Home Network 
> Identifier option. That is, the number of HN Information 
> option in the reply is the same as the number of HN 
> Information option in the request, and the "id-type" will be 
> added in an HN information option for mapping for each 
> option. We fixed this and the next version will cover this.
> Thanks.
>  
> - Best Regareds,
> Heejin
> 
> ------- Original Message -------
> Sender : Premec, Domagoj<[email-masked]>
> Date   : 2007-06-01 00:56
> Title  : RE: [Mip6] I-D ACTION:draft-ietf-mip6-hiopt-03.txt
> 
> Hi Heejin,
> 
> I have a clarification question: if the MN requests 
> information about several target networks it will include 
> several Home Network Identifier options. The following text 
> 
> >   Multiple sub-options may exist in a Home Network 
> Information option
> >   to carry more than one home information.
> 
> leaves impression that the response message contains only one 
> Home Network Information option which carries the addresses, 
> prefixes and/or FQDNs of all target networks. I could be 
> wrong, but I couldn&&#35;39;t find any text that is specific about this. 
> 
> If the information about multiple target networks is carried 
> in a single Home Network Information option, the MN may not 
> be able to match the info from the Home Network Information 
> option to a particular target network. For example, the MN 
> may ask for infomation about operator1.com and operator2.com, 
> and the Home Network Information option may contain the home 
> subnet prefix and the FQDN. How would the MN know if both 
> suboptions carry information about operator1.com or if subnet 
> belongs to operator1 and FQDN to operator 2?
> 
> thanks
> domagoj
> 
> 
> > -----Original Message-----
> > From: [email-masked] [mailto:[email-masked]]
> > Sent: 16. svibanj 2007 21:50
> > To: [email-masked]
> > Cc: [email-masked]
> > Subject: [Mip6] I-D ACTION:draft-ietf-mip6-hiopt-03.txt
> > 
> > A New Internet-Draft is available from the on-line Internet-Drafts 
> > directories.
> > This draft is a work item of the Mobility for IPv6 Working Group of 
> > the IETF.
> > 
> >     Title        : DHCP Option for Home Information 
> > Discovery in MIPv6
> >     Author(s)    : H. Jang, et al.
> >     Filename    : draft-ietf-mip6-hiopt-03.txt
> >     Pages        : 19
> >     Date        : 2007-5-16
> >     
> > This draft defines a DHCP-based scheme to enable dynamic 
> discovery of
> >    Mobile IPv6 home agent address, home agent FQDN and home 
> subnet.  
> > New
> >    DHCP options are defined to carry the information from a DHCP 
> > server
> >    to the DHCP client running on the mobile node.
> > 
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-mip6-hiopt-03.txt
> > 
> > To remove yourself from the I-D Announcement list, send a 
> message to 
> > [email-masked] with the word unsubscribe in 
> the body of 
> > the message.
> > You can also visit 
> https://www1.ietf.org/mailman/listinfo/I-D-announce
> > to change your subscription settings.
> > 
> > Internet-Drafts are also available by anonymous FTP. Login with the 
> > username "anonymous" and a password of your e-mail address. After 
> > logging in, type "cd internet-drafts" and then "get 
> > draft-ietf-mip6-hiopt-03.txt".
> > 
> > A list of Internet-Drafts directories can be found in 
> > http://www.ietf.org/shadow.html or 
> > ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> > 
> > Internet-Drafts can also be obtained by e-mail.
> > 
> > Send a message to:
> >     [email-masked].
> > In the body type:
> >     "FILE /internet-drafts/draft-ietf-mip6-hiopt-03.txt".
> >     
> > NOTE:    The mail server at ietf.org can return the document in
> >     MIME-encoded form by using the "mpack" utility.  To use this
> >     feature, insert the command "ENCODING mime" before the "FILE"
> >     command.  To decode the response(s), you will need "munpack" or
> >     a MIME-compliant mail reader.  Different MIME-compliant mail 
> > readers
> >     exhibit different behavior, especially when dealing with
> >     "multipart" MIME messages (i.e. documents which have been split
> >     up into multiple messages), so check your local documentation on
> >     how to manipulate these messages.
> > 
> > Below is the data which will enable a MIME compliant mail reader 
> > implementation to automatically retrieve the ASCII version of the 
> > Internet-Draft.
> > 
> 
> 
> 

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

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