Subject: [Mip6] Resolution: [issue66] Setting up forwarding for IPv4 HoA

From: "Soliman, Hesham" <[email-masked]>
Date: Tue, 31 Oct 2006 20:08:54 -0800

Ok with me too.

Folks, this issue is now closed.

Thanks for your feedback.

Hesham 

 > -----Original Message-----
 > From: RYUJI WAKIKAWA [mailto:[email-masked]] 
 > Sent: Wednesday, November 01, 2006 2:28 AM
 > To: Pascal Thubert ((pthubert))
 > Cc: Soliman, Hesham; Vijay Devarapalli; [email-masked]
 > Subject: Re: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
 > 
 > Hi Pascal,
 > 
 > I am fine with both texts.
 > And same for the option name.
 > 
 > ryuji
 > 
 > On 2006/10/30, at 21:54, Pascal Thubert ((pthubert)) wrote:
 > 
 > > Just to make sure on what the agreement is:
 > >
 > > 1) There are 2 paragraphs in the original text that we 
 > want to update
 > >
 > > "
 > > If the binding update is accepted for the IPv4 home 
 > address, the home
 > > agent MUST create a binding cache entry for the IPv4 home
 > > address/prefix. If a single IPv4 home address were requested, it  
 > > MAY be
 > > stored in the IPv4-mapped IPv6 address format. The home agent MUST
 > > include an IPv4 acknowledgement option in the mobility header  
 > > containing
 > > the binding acknowledgement.
 > >
 > > If the binding update is accepted for both IPv4 and IPv6 home  
 > > addresses,
 > > the home agent MUST create two separate binding cache 
 > entries, one for
 > > each home address. The care-of address is the one included in the
 > > binding update. If the care-of address is an IPv4- mapped IPv6  
 > > address,
 > > the home agent MUST setup a tunnel to the IPv4 care-of 
 > address of the
 > > mobile node.
 > > "
 > >
 > > 2) When Vijay says IPv4 HoA, we mean IPv4 Home 
 > Address/prefix since  
 > > that
 > > is the language used in the draft and we might set up a network  
 > > route as
 > > opposed to a host route for IPv4.
 > >
 > > So the text in 1) becomes:
 > >
 > >
 > >    The home agent MUST create a binding cache entry for 
 > IPv6 HoA and
 > >    MUST setup forwarding for the IPv4 HoA/prefix. The forwarding
 > > information
 > >    for the IPv4 HoA/prefix can be in the form of a routing 
 > table entry
 > > or a
 > >    separate binding cache entry.  But this information is 
 > tied to the
 > >    binding cache entry for the IPv6 HoA and is removed when the
 > >    binding cache entry expires.
 > >
 > >
 > >
 > > 3) The text seems to force the forwarding information to 
 > be either BCE
 > > or RIB. I'd suggest that these are only examples, since a NAT table
 > > could be useful too.
 > >
 > >
 > > So the text in 1) becomes:
 > >
 > >
 > >    The home agent MUST create a binding cache entry for 
 > IPv6 HoA and
 > >    MUST setup forwarding for the IPv4 HoA/prefix. The forwarding
 > > information
 > >    for the IPv4 HoA/prefix can be for instance in the form of a  
 > > routing
 > > table entry or a
 > >    separate binding cache entry.  In any case, this 
 > information is  
 > > tied
 > > to the
 > >    binding cache entry for the IPv6 HoA and is removed when the
 > >    binding cache entry expires.
 > >
 > >
 > > IS that OK?
 > >
 > >
 > > By the way, we seem to also have consensus on renaming the 
 > "IPv4 home
 > > address option". I did not see opposition to "IPv4 
 > addressing option".
 > >
 > > Any alternate proposal?
 > >
 > > Pascal
 > >
 > >> -----Original Message-----
 > >> From: Soliman, Hesham [mailto:[email-masked]]
 > >> Sent: Thursday, October 26, 2006 2:31 AM
 > >> To: Vijay Devarapalli; RYUJI WAKIKAWA
 > >> Cc: Pascal Thubert (pthubert); [email-masked]
 > >> Subject: RE: [Mip6] Re: [issue66] Setting up forwarding 
 > for IPv4 HoA
 > >>
 > >>
 > >>> building on your text, how about the following?
 > >>>
 > >>>    The home agent MUST create a binding cache entry for 
 > IPv6 HoA and
 > >>>    MUST setup forwarding for the IPv4 HoA. The forwarding
 > > information
 > >>>    for the IPv4 HoA can be in the form of a routing 
 > table entry or a
 > >>>    separate binding cache entry.  But this information is tied to
 > > the
 > >>>    binding cache entry for the IPv6 HoA and is removed when the
 > >>>    binding cache entry expires.
 > >>>
 > >>
 > >> => This text is perfectly fine with me, anyone has a 
 > problem with  
 > >> this?
 > >> If not, then it's in! No more please :)
 > >>
 > >> Hesham
 > 
 > 

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