Re: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-08.txt
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-08.txt



I agree with Alex.

Kent

-----Original Message-----
From: mip4-bounces at ietf.org [mailto:mip4-bounces at ietf.org] On Behalf Of Charles E. Perkins
Sent: Thursday, October 08, 2009 2:45 PM
To: Alexandru Petrescu
Cc: mip4 at ietf.org
Subject: Re: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-08.txt


Hello Alex,

Yes, I think it would be a better fit.
Do other people have opinions about this?

Regards,
Charlie P.


Alexandru Petrescu wrote:
> Charles,
>
> Do you think it could make sense to cite rfc5177 "Network Mobility
> (NEMO) Extensions for Mobile IPv4" in this 3344bis Mobile IPv4 draft?
>
> I am asking because (contrary to the Mobile IPv6 situation) the
> rfc3344bis draft makes explicit textual statements about "Mobile
> Router", which is a central entity of rfc5177.
>
> Alex
>
> Internet-Drafts at ietf.org a écrit :
>> A New Internet-Draft is available from the on-line Internet-Drafts 
>> directories. This draft is a work item of the Mobility for IPv4
>> Working Group of the IETF.
>>
>> Title        : IP Mobility Support for IPv4, revised Author(s)    : 
>> C. Perkins
>>  Filename    : draft-ietf-mip4-rfc3344bis-08.txt Pages        : 108 
>> Date        :
>> 2009-10-7  This document specifies protocol enhancements that allow
>> transparent routing of IP datagrams to mobile nodes in the Internet.
>> Each mobile node is always identified by its home address, regardless
>> of its current point of attachment to the Internet.  While situated
>> away from its home, a mobile node is also associated with a care-of 
>> address, which provides information about its current point of 
>> attachment to the Internet.  The protocol provides for registering 
>> the care-of address with a home agent.  The home agent sends 
>> datagrams destined for the mobile node through a tunnel to the 
>> care-of address.  After arriving at the end of the tunnel, each 
>> datagram is then delivered to the mobile node.
>>
>> A URL for this Internet-Draft is: 
>> http://www.ietf.org/internet-drafts/draft-ietf-mip4-rfc3344bis-08.txt
>>
>>
>> Internet-Drafts are also available by anonymous FTP at: 
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> Below is the data which will enable a MIME compliant mail reader 
>> implementation to automatically retrieve the ASCII version of the 
>> Internet-Draft.
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> _______________________________________________ I-D-Announce mailing
>> list I-D-Announce at ietf.org 
>> https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft
>> directories: http://www.ietf.org/shadow.html or
>> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>

--
Mip4 mailing list: Mip4 at ietf.org
    Web interface: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.