Re: [MEXT] RFC 6301
"Templin, Fred L" <[email protected]>
| Newsgroups | gmane.ietf.nemo,gmane.ietf.mext |
|---|---|
| Message-ID | <E1829B60731D1740BB7A0626B4FAF0A65C77323010@XCH-NW-01V.nw.nos.boeing.com> |
The survey seems to have missed IRON (RFC6179), which along with its supporting technologies (VET, SEAL, AERO) comprehensively addresses the mobility solution space. Thanks - Fred > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Ryuji Wakikawa > Sent: Wednesday, September 28, 2011 11:28 AM > To: [email protected] > Cc: [email protected] > Subject: Re: [MEXT] RFC 6301 > > Hi Behcet > > Thanks for the message. I believe there are plenty of > potential issues MEXT group can solve... > > ryuji > > On 2011/09/27, at 14:59, Behcet Sarikaya wrote: > > > Hi all, > > Have you seen this recently issued RFC 6301? I suggest > taking a look at it. Good survey from way back 1991 to this > date, thanks to Ryuji. > > It covers protocols like LISP and GTP (yes, GTP) and raises > the issue of interworking such as between Mobile IP and HIP, > I would add Mobile IP and SIP mobility. > > > > Regards, > > > > Behcet > > > > _______________________________________________ > > MEXT mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/mext > > _______________________________________________ > MEXT mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/mext >